Solution : https://service.sap.com/sap/support/notes/22941 (SAP Service marketplace login required)
Summary :
The SAP Note addresses the requirement for reorganizing an Informix database, highlighting scenarios where reorganization becomes necessary, including extensive table extents, storage limits, and unoptimized disk space usage. Important warnings are provided against the use of 'unload' and 'load' methods due to an Informix bug in version 7.20 which could result in data loss. Instead, safer methods using SAPDBA and 'insert into select from ...' are advocated. Recommendations are made for system monitoring and careful intervention via tools like SAPDBA and CC didn’t occur. General best practices for conducting reorganizations, such as ensuring sufficient temporary dbspace and shutting down the R/3 system to avoid locks, are emphasized to ensure a successful operation.
Key words :
$ dbaccess <sid> <<eofselect tabnamefrom sysmaster, onmonitor -> logical-logs -> tape-parameters, generate shell script files 9, su - informix start sapdba version 3, allocatedin large delete actions, reconfigure disks/dbspaces/chunksif, find 'change storage options', $viewname -ss view_$viewname, hard disk dbspaces/chunks, additional key words reorganization
Related Notes :
548943 | FAQ: Avoiding disk space problems |
387700 | Usage of Informix HPL in the SAP environment |
208919 | CC-INFO: Performance as of Release 4.6 |
96296 | CC-ERROR: Database problem in client copy |
70643 | CC-TOPIC: Client Deletion (SCC5) |
67911 | Reorganization of dbspaces after upgrade |
52252 | Change the Logging Mode (no/unbuffered log.) |
51400 | Problems in reorganization: INFORMIX 7.20 |
50164 | SAPDBA:Value for 'max. number of extents' too high |
38401 | Download the latest SAPDBA version |
33839 | Reorg. of Dbspaces after upgrade 2.x -> 3.x/4.x |