Go Back

User login

Frontpage Sponsor


Google search

How big is your Baan-DB (just Data AND Indexes)
0 - 200 GB
200 - 500 GB
500 - 800 GB
800 - 1200 GB
1200 - 1500 GB
1500 - 2000 GB
> 2000 GB
Total votes: 36

Baanboard at LinkedIn

Reference Content

Items for 'English' (by date)
By Date  
Alphabetically By Date  


You are browsing all items of this content category sorted by date (most recent first). Note that forum posts/threads are not included here.


If you would like to search through the content then please refer to the Site Search page.


Programmers Manual BaanERP - Topic List -C-
By patvdv at 26 Feb 2008 - 21:56

Programmers Manual BaanERP: Full Topic List
By patvdv at 26 Feb 2008 - 21:56

BaanERP Programmers's Manual: Full Topic List

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • <
    No votes yet

Programmers Manual BaanERP: Topic List -7-
By patvdv at 26 Feb 2008 - 21:56

Programmers Manual BaanERP: Topic List -4-
By patvdv at 26 Feb 2008 - 21:56

How to create Oracle users/roles manually
By Markus Schmitz at 23 Feb 2008 - 23:44

You can create all needed users/roles manually, but you have to keep the same passwords, because you have only one ora_users file for all databases.


Here we go:


1) You need to create the schema owner. In Unix this is normally baan and in NT often baandb:


No votes yet

Redo & Rollback: After activating a standby rhe primary requires recopying to become the standby
By patvdv at 23 Feb 2008 - 23:29

When switching to a standby database, there are two basic scenarios. In one scenario, the switchover is undertaken in an emergency, and due to the unavailability of the primary host or the storage, the final one or two redologs are not available, and therefore cannot be applied to the standby. In such a case, the standby must be activated after incomplete recovery, without applying the last changes from the primary. This scenario is extremely rare.


Redo & Rollback: No logging turns off redo logging
By patvdv at 23 Feb 2008 - 23:25

Many people believe that by setting a segment to NOLOGGING mode, no redo will be generated for DML performed against that segment. In fact, only a limited number of operations can be performed NOLOGGING. According to the Oracle 8i Concepts Guide, only the following operations may take advantage of the NOLOGGING feature:


Redo & Rollback: Checkpoint not complete misguided solutions
By patvdv at 23 Feb 2008 - 23:23

A common problem for people with very active systems who use filesystems to store their datafiles is the error, Thread cannot allocate new log, sequence ; Checkpoint not complete. The most commonly recommended remedies for this situation are either to use larger or more online redologs.


Unfortunately, if checkpoint not complete is a chronic problem, neither of these solutions will eliminate the problem. They may forestall, or even reduce the frequency of the error, but the problem will not be solved.

Redo & Rollback: Big batch jobs should use a dedicated rollback segment
By patvdv at 23 Feb 2008 - 23:15

A common habit among DBAs is to assign large batch jobs that make many changes, or have very large transactions, to a dedicated rollback segment, using the set transaction use rollback segment; command. Many databases have a rollback segment called rbs_large or something similar for this purpose.


Redo & Rollback: Snapshot too old can be avoided by using set transaction use rollback segment
By patvdv at 23 Feb 2008 - 23:12

It is often asserted that if you get the ubiquitous ORA-01555: Snapshot too old: Rollback segment with name too small, you are running out of rollback segment. This misconception is partially the fault of the misleading error text. The rollback segment mentioned is not necessarily too small. This error is actually a failure to obtain read consistency.


All times are GMT +2. The time now is 15:46.

©2001-2018 - -