Skip to Content
Actions

“ORA-14400: inserted partition key does not map to any partition” – Resolution Doc

December 31, 2013 | 1,214 Views |
Follow

DSO Activation error troubleshooting document

Error message: “ORA-14400: inserted partition key does not map to any partition”

Details

Error: Failure of activation of a request in DSO

Error message:

“ORA-14400: inserted partition key does not map to any partition”

Dump DBIF_RSQL_SQL_ERROR

What caused this?

Invalid characters were posted in ECC for some values of a field which were causing one of the transaction loads to fail. To correct this, PSA maintenance had to be done. Each time error was showing up for a different value for which requests from the targets needed to be deleted for each error which resulted in the change log table of the DSO to get inconsistent and the activation kept failing

The screenshot below shows the dumps from ST22 created due tothe failed activation

Untitled.png

From the dump, we can see the technical name of the Change log table of the DSO; /BIC/B0001230000 in this case (circled in the screenshot below)

Untitled.png

Untitled.png

Solution:

Use test for PSA partition consistency in transaction RSRV.
Any found error should be corrected in RSRV itself.

Upon the RSRV test execution, we see that the table is inconsistent

Untitled.png

We can repair the PSA partition with RSRV or we can ask Basis team to do a consistency check

Carry out repair in RSRV with the error correction option. Click on yes and the error will be corrected.

Untitled.png

Reload of data and activation now will be successful

Note:

This error might also occur when there is huge amount of data

Check OSS note 339896

SAP note 509660 – ORACLE ERROR 14400 during update to the InfoCube

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Antony Jerald J

    Hi,

    Thanks for sharing 🙂  Really useful…Even I faced the error msg in my past so I left this as a Basis issue 😛

    Now got a little idea on what to do for such a DB SQL errors !!!

    But here you’ve mentioned only one specific case(changelog data)  Will the note be applicable to any such DB error of same kind?

    Regards,

    Antony Jerald.

    (0) 
    1. Sadaf Faheem Post author

      Hi,

      The notes apply to cases where you face certain ORA-**** errors. You may refer to the note 509660. This note applies when faced with this error while loading data to cube/PSA or during ODS activation. Analysis of dumps would be helpful.

      I do not think this applies to all DB errors. DB errors also occur due to a deadlock issue while parallel data loading or when you are loading huge volumes of data to cubes for which indices already exist.

      Glad that you found it helpful.

      Regards,

      Sadaf

      (0) 

Leave a Reply