We are testing the Het. Sys copy procedure for a BW31C system in order to move it on a new hardware.
We are following the standard R3load procedure, so export/import by mean of the Sapinst tool.
According the note 777024 the level of the SAP_BASIS components should be at least 58 to perform the export-import procedure
Our BW31C system instead has SAP_BASIS level 40, and it's not foresee to apply furtehr support packag es here, as the sistem is planned to be upgraded soon to BI.
So we went ahead anyway with our migration test.
As for note 777024 we should run the report SMIGR_CREATE_DDL on the
source system, but this report is not present into our source BW,
probabily because the SAP_BASIS patch level is too low, (but we are not sure of that, please confirm).
Also if the SMIGR_CREATE_DDL did not run on the source system we went ahead with the export of the database.
THe export terminated successfully, and we started the installation and the import on the target system.
During the import we are encontering errors Ora-1452 on some customer table into the PSAPDFACT tablespace (tables like /BIC/......):
As we can see these are customer tables. The error occurs because the sapinst is trying to create the ^0 index as "UNIQUE INDEX" but it fail as these tables contains a lot of duplicated records (thousands for each).
On the source system the ^0 index exist in the Sap data dictionary (we see it on SE14) but does not exist in the database (there is the msg "! MUST NOT CREATED IN THE DB")
So we find out that the error is occuring because the Sapinst is trying to create on the target system an UNIQUE INDEX that should not be created, as these tables contains duplicated records.
We do not why it's occurring, but we suspect because we did not run the SMIGR_CREATE_DDL report.
But we are not sure this report is supposed to create special .sql
statement for the definition of these customer tables and their
indexes, so to skip the creation of the ^0 index.
Another possibility should be to apply the note 11369, but in our
opinion is not an error the presence of these duplicated records.
So they should not deleted at all.
In which way we can continue the import, skipping this error ?
For example, if SMIGR_CREATE_DDL is supposed to be the right solution, can we upload this report from another system ?
If so from which kind of system we can dowload it ? (BW31C, R/3 47 , Enterprise,...)
Or we can modify by hand the .EXT files or other files produced by the export in order to avoid the creation of the ^0 index for these tables ?If so which files are supposed to be modified ?