We are busy exporting a SRM system with sapinst/R3load
We do not use database specific tools as this is a ABAP+JAVA dual stack
At first we did try to start the export only with the option "Split STR" which was ok
except for one huge table, there we discovered that R3load has a limitation in the number
of exported data files, the maximum for a group export is 256, in our case the group SAPAPPL1
reached file SAPAPPL1.256 and ended in error with the attempt to have the next file (257)
in the LOG we had:
LOG:
(WTF) ERROR: too many data file entries for table CFF_CONT
(TFH) ERROR: Unable to close /sapmnt/PSR/export/ABAP/DATA/SAPAPPL1.257
(TFH) ERROR: OS error message: Bad file number
(DB) INFO: disconnected from DB
We saw here that the total size of this SRM database is 340 GB,
and the cluster table CFF_CONT alone is about 270 GB, thus without that table the system is only about 70 GB
The table itself (CFF_CONT) looks like just above 1GB but using LOB segment for about 270 GB
Now this huge table required that we restart the Export with different parameters
and unsing the Table Splitting Preparation
with a file like: SplitTable.TXT containing 1 line: CFF_CONT%4 and the option ROWID
this split in 4 (4 WHR files) and would avoid to reach the 256 limitation of R3load
Our question : is that the best recommend option for that table ?
Would also be nice to know what that table is for, and if it could be archived or clean up by business
Regards.