Solution : https://service.sap.com/sap/support/notes/13655 (SAP Service marketplace login required)
Summary :
Long runtimes (>10 hours) may occur when exporting or importing tables (e.g., ATAB, APQD) with SAPDBA. Key issues include the absence of expst/impst, presence of LONG columns with "commit = Y", data mirroring, and ARCHIVELOG mode. Solutions involve using single task versions expst/impst from ORACLE if available, modifying SAPDBA import scripts to "commit=N", handling rollback segments, and selectively placing large tables in separate tablespaces. Data mirroring should ideally not increase reorganization time significantly, and proactive measures should be taken to manage ARCHIVELOG space and prevent archiver stack issues.
Key words :
sqldba> shutdown sqldba> startup mount sqldba> alter database noarchivelog, scripts $oracle_home/sapreorg/<timestamp>/exp<tsp>, cd $oracle_home/bin touch expst impst, sqldba> shutdown sqldba> startup mount, sqldba> connect internal sqldba> startup, touch sqldbast touch sqlldrst cd, sqldba> shutdown sqldba> exit sapdba, sqldba> alter system switch logfile, sqldba> alter database open, sqldba> alter database archivelog
Related Notes :
| 130345 | Singletask not longer supported on Oracle8 |
| 88081 | export import sqlldr singletask in Oracle 7.3.3 |
| 60233 | Oracle rollback segments, more information. |
| 43487 | Collective note: SAPDBA - Reorgnztn/Space/Structure |