DBSQL_DUPLICATE_KEY_ERROR short dump

SAPSQL_ARRAY_INSERT_DUPREC 

Hi All,

When I run a transaction code SE38 enter report RSDS_DATASOURCE_ACTIVATE_ALL and execute, enter relevant source system and the problematic DataSource name and execute.

Short dump Occur:

SAPSQL_ARRAY_INSERT_DUPREC

Please help in solving the problem 

Solution

To resolve the SAPSQL_ARRAY_INSERT_DUPREC short dump when activating a DataSource, follow these steps:

1. Identify the Affected Table

• Check the Short Dump Details: Open the dump (ST22) to find the specific database table causing the duplicate entry. Look for lines like INSERT <TABLE_NAME> or DBIF_DSQL2_ARRAY_INSERT in the error details. Common tables include ROOSOURCE, RSDODSO, or other BW metadata tables.

2. Check for Duplicate Entries

• Use SE11 or SE16 to inspect the table identified in the dump. For example:

  • If the table is ROOSOURCE, check entries for the DataSource (OBJID) and source system (S_SYSTEM) combination.

  • Execute a query like:

    SELECT * FROM <TABLE_NAME> 
    WHERE OBJID = '<DataSource>' AND S_SYSTEM = '<SourceSystem>'.

• If duplicates exist, note their keys.

3. Resolve Duplicates

Option A: Use Standard Tools

• Deactivate/Reactivate via RSA5:

  1. Go to t-code RSA5 (DataSources in BW).

  2. Find the DataSource, deactivate it, and reactivate it. This may clean up metadata automatically.

Option B: Manual Cleanup (Proceed with Caution!)

• Delete Duplicates:

  • Use SE16 (with display mode changed to edit via &SAP_EDIT in the command field).

  • Delete duplicate entries only if you confirm they are obsolete.

  • Example for ROOSOURCE

    DELETE FROM ROOSOURCE 
    WHERE OBJID = '<DataSource>' 
      AND S_SYSTEM = '<SourceSystem>'
      AND VERSION = '000'.

• Important: Backup the table or consult SAP support before manual deletion.

4. Retry Activation

• Run RSDS_DATASOURCE_ACTIVATE_ALL again after resolving duplicates.

5. Apply SAP OSS Notes

• Search SAP OSS for notes related to:

  • SAPSQL_ARRAY_INSERT_DUPREC

  • RSDS_DATASOURCE_ACTIVATE_ALL errors

  • Example: SAP Document 123456 (replace with actual note number if found).

6. Prevent Future Issues

• Ensure transports for DataSources are correctly imported.

• Avoid manual edits to BW metadata tables.

• Regularly check for BW support pack updates.

If the issue persists, contact SAP Support and provide:

• The short dump details.

• The table name and key fields causing duplicates.

• Steps you’ve already tried.