Oracle Settings For R3load Based System
Oracle Settings For R3load Based System
Oracle Settings For R3load Based System
Symptom
Other Terms
Solution
After the migration has been completed the database and parametrization should
be changed back to the recommended production settings of the Oracle database
for R/3 and BW.
The following list contains the necessary steps to achieve the best database
throughput during a system copy with R3load:
2. Create Oracle Data Dictionary statistics for source database (Only relevant for Oracle 9.2.x
systems. Details in OSS note 558746)
This will reduce substantially the runtime of the R3szchk utility.
WARNING: In a R/3 system you must remove the statistics explained
in note 558746 after the R3szchk has run successfully !!!
• filesystemio_options = setall
• disk_asynch_io = true
• parallel_execution_message_size = 16384
• parallel_threads_per_cpu = 1
4. Database configuration
• Put redo log files on raw devices if OS and filesystem do not support async,
direct and concurrent IO (see also OSS note 834343 or 999524)
• Disable redo log mirroring, use only one redo log member per redo group.
5. Network configuration
The following changes are designed to optimize network traffic between database
server and the server(s) running the R3Load processes
• SQL*Net configuration:
6. DDLORA.TPL changes
The utility R3ldctl will add PARALLEL, NOLOGGING and COMPUTE STATISTICS clauses
to create primary key (crepky) and create index (creind) sections in DDLORA.TPL
template files. To use this new functionality you need to use at least the
following R3ldctl versions:
940561 ORACLE DIRECT PATH LOAD DOES NOT LOAD PARALLEL SINGLE TABLE
575280 Add info about upgrade to SAP Web AS 6.20 ORACLE 9.2.0
940561 ORACLE DIRECT PATH LOAD DOES NOT LOAD PARALLEL SINGLE TABLE
575280 Add info about upgrade to SAP Web AS 6.20 ORACLE 9.2.0