Solution : https://service.sap.com/sap/support/notes/1039120 (SAP Service marketplace login required)
Summary :
This SAP Note discusses utilizing R3ta for reducing package sizes during system copies or Unicode conversions specifically for large tables. It highlights an issue with tablespaces created using LOCKSIZE TABLESPACE causing SQL -911 errors and advises changing LOCKSIZE to ROW. The detailed fix involves verifying and modifying tablespaces' LOCKSIZE in SQL files generated by SAPinst and ABAP functions, ensuring proper handling when tables contain lob columns without partitioned tablespaces. Recommendations include procedural steps for adjusting the LOCKSIZE parameter to PAGE in the CREATE TABLESPACE statements to prevent insertion timeouts during simultaneous data loads.
Key words :
terms r3tamigrationsyscopysystem copytable splitting reason, sapinst custom mode find, /sapdmc/lsorul /sapdmc/lsorul 1, verify create tablespace statements, table '/sapdmc/lsorul', db2 catalog query, query returns rows, abap function smigr_create_ddl, create tablespace statement, base table space
Related Notes :
| 1296510 | DB2-z/OS: fast load with load utility BatchPipes/MVSDS |
| 1062976 | DB2-z/OS: fast load with load utility and USS fifos |