SM:SELFDIAGNOSIS background job getting failed in Solution manager

[Former Member]

Hi All,

SM:SELFDIAGNOSIS background job getting failed in Solution manger server :

Job Log:

2-22-2012 16:44:02 Job started 00 516 S

2-22-2012 16:44:02 Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000000324, user ID BASISUSER) 00 550 S

2-22-2012 16:45:07 Internal session terminated with a runtime error (see ST22) 00 671 A

2-22-2012 16:45:07 Job cancelled 00 518 A

ST22: Dump:

Runtime Errors ITAB_DUPLICATE_KEY

Date and Time 02-22-2012 16:45:07

-

---

-

---

Short text

A row with the same key already exists.

-

---

-

---

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

-

---

-

---

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

-

---

-

---

Error analysis

An entry was to be entered into the table

"\CLASS=CL_DSWP_SD_DIAGNOSE_CONSISTENT\METHOD=CHECK_USERS_BP\DATA=LT_USCP"

(which should have

had a unique table key (UNIQUE KEY)).

However, there already existed a line with an identical key.

The insert-operation could have ocurred as a result of an INSERT- or

MOVE command, or in conjunction with a SELECT ... INTO.

The statement "INSERT INITIAL LINE ..." cannot be used to insert several

initial lines into a table with a unique key.

-

---

-

---

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"ITAB_DUPLICATE_KEY" " "

"CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" or "CL_DSWP_SD_DIAGNOSE_CONSISTENTCM00M"

"CHECK_USERS_BP"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

KIndly Suggest to resolve the above issue

Thanks

Nekkalapu

[Former Member]

please let me know your support pack version detail including component ST

[Former Member]

HI,

Deatils:

SAP EHP 1 for SAP Solution Manager 7.0

SAP_ABA 701 0006 SAPKA70106

SAP_BASIS 701 0006 SAPKB70106

PI_BASIS 701 0006 SAPK-70106INPIBASI

ST-PI 2008_1_700 0002 SAPKITLRD2

CRMUIF 500 0004 SAPK-50004INCRMUIF

SAP_BW 701 0006 SAPKW70106

SAP_AP 700 0019 SAPKNA7019

BBPCRM 500 0016 SAPKU50016

BI_CONT 704 0007 SAPK-70407INBICONT

CPRXRPM 400 0016 SAPK-40016INCPRXRP

ST 400 0024 SAPKITL434

ST-A/PI 01M_CRM570 0000 -

ST-ICO 150_700 0009 SAPK-15079INSTPL

ST-SER 701_2010_1 0002 SAPKITLOS2

Thanks

Nekkalapu