SAP system copy installation stucked at Import ABAP phase

[former_member1326975]

I tried to installed SAP using the system copy method. However, it was stuck at Import ABAP phase, import monitor Job 9. The process will stuck here forever will proceed further. If I check those SAP*** log, it will have the error shown in bold below:

(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed:[Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint '/SAPDMC/LSORUL~0'.>

I have doubt, what is wrong, I already tried every possible method. However, the process still stuck at this phase. Can anyone provide any assistance or suggestion? Attached is one of the sample of error log.

SAPUSER.txt.zip

[paul_power]

Hi,

Sorry, I just saw the log you posted.

Its failing on tables

T5BPBS01 and T5BPBS02

You can use the following statements to identify the duplicate entries
on table T5BPBS01 which is affecting the index:

-> Index T5BPBS02~0:
SELECT <index key field 1>, <index key field 2>, count(*)
FROM <SID>.<sid>.T5BPBS02
GROUP BY <index key field1>, <index key field2>
HAVING count(*) > 1

-> Index T5BPBS01~1:
SELECT <index key field1>, <index key field 2>, count(*)
FROM <SID>.<sid>.T5BPBS01
GROUP BY <index key field1>, <index key field2>
HAVING count(*) > 1

This will show any rows that are duplicates of the primary key.

The steps to remove the duplicated keys can be found under:

http://support.microsoft.com/kb/139444/en

Check if these duplicate exist on source as well.

(I can rewruite the sql to be clearer if you update with the key fields of the 2 mentioned indexes and the DB and instance sid)

regards,

Paul

[former_member1326975]

Hi Paul,

I would like to have the clearer SQL on what is the key fields that you mentioned. What is the 2 mentioned indexes because I can find many field in the table, so I'm not sure how the SQL statement should work.

[former_member189725]

Can you please check in the installation directory the file import_monitor_cmd.properties .

Edit the file

in the loadargs section , change -loadprocedure fast to -loadprocedure dbsl

The retry the import.

Regards

Ratnajit

[former_member1326975]

Hi Ratnajit,

I changed as per your suggestion and retry to run the job. The job will continue to run, but the jobs are all failed and not completed. So, how should I continue to rectify this problem?

[former_member189725]

Did all the jobs fail as before , can you paste the SAPUSER.log file .

Regards

Ratnajit

[paul_power]

Hi,

If you open these two tables in se11/se14 in the source system, you will see which fields make up the primary key, these are the field names you put in for

<index key field 1>, <index key field 2>, ......

the sid will be the system and db sid, for example if qas and lets say the table T5BPBS02~0 has primary key consisting of fields, cust num, order num

then they sql would be:

-> Index T5BPBS01~1:

SELECT custnum, orderid, count(*)

FROM QAS.qas.T5BPBS01

GROUP BYcustnum, orderid

HAVING count(*) > 1

This would show us if we have 2 or more rows with same custnum and orderid, and so this violates the primary key.

The rows would need to be checked on source system to see if duplicate there also.

Then dicuss with application team responsible for these tables to decide which is the duplicate that needs to be removed.

when there is no duplicate, then this error wont occur

(if duplicate exists on source you may have to export this package again after removing duplicate on source)

regards,

Paul

[former_member1326975]

Hi All,

I tried to follow the steps suggested, but it is still having error. Attached is the log for your reference.

import_monitor.txt.zip

sapinst.txt.zip

[former_member189725]

It seems 13 jobs have failed and only 5 have completed .

Can you paste the SAPCLUST.log

Also update the kernel and then try running the SAPINST.

Regards

Ratnajit

[former_member1326975]

HI,

Here is the log file.

SAPCLUST.txt.zip

[former_member189725]

Did you run the SMIGR_CREATE_DDL in the source system. It seems lot of tables has the same issue . Cannot create primary index <table>~0 .

You may have to apply Note 1471193 - SMIGR_CREATE_DDL creates non-unique P-Index on APO facttable

and then run SMIGR_CREATE_DDL on the source system and do the export again.

Regards

Ratnajit

[former_member1326975]

Hi Ratnajit,

I already tried the method mentioned. However, it still giving me the same error and the process is still stuck at job monitor, abap process 9. Any other way to solve this problem?

[paul_power]

Hi,

From note 942540 we can see:

{quote}
...
These <TABART>.SQL files must be created manually on the source system
by running a report SMIGR_CREATE_DDL. The resulting files must be copied
to the directory <export directory>/DB/<DBSYS> of the target system.
If this step was forgotten, on import duplicate key errors (violations
of primary key constraint) could occur. If fastload is used you only see
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed>(IMP) ERROR:
ExeFastload: rc = 2

Solution
The SMIGR_CREATE_DDL report must be executed as described in note
771209.
The resulting DFACT.SQL file must be copied to  the <export
directory>/DB/MSS of the target system.
The SAPDFACT-import must be rerun completely as follows:
...
{quote}

Did you run the SMIGR_CREATE_DDL (note 771209) in the source system?

regards,

Paul