SAP Knowledge Base Article

1814621 - FAQ: DBIF_RSQL_SQL_ERROR short dump, ORA-14400 error

Version 1 Validity: 25.01.2013 - active Language English

Symptom
l DBIF_RSQL_SQL_ERROR dump in ST22 (exception CX_SY_OPEN_SQL_DB, form routine INSERT_ODS)
l "ORA-14400: inserted partition key does not map to any partition"
l Thedump&errorcanoccurwhenwriting/insertingtoPSAorF-fact tables or when DSO objects are activated.
l PSA loads fail.
l Unable to activate DSO requests.
l DSO activation fails.
l Activation job BI_ODS..... dumps

Environment
l SAP Business Warehouse (BW)

Reproducing the Issue

DumpduringDSOactivation:

1. RuntcodeRSA1
2. Find the problematic DSO & click manage
3. Enter the activation log to view the returned error msg which will enable you to jump to tcode ST22 & view the related
DBIF_RSQL_SQL_ERROR dump.

Dump during PSA or F-fact table inserts:

1. Run tcode RSA1

2. Find the failing load by searching for the relevant InfoPackage used
3. Click on the monitor button to view the recent runs of that InfoPackage.

Cause
The ORA-14400 error is normally caused by an inconsistency in the partition numbers for the PSA. This inconsistency then causes the data load or
the DSO activation to fail.

The system displays the ORA-14400 error message if you want to load data into a partitioned table where the partitions have not been defined
correctly.
Partitioned tables store data in different "parts" where every dataset, depending on the defined partitioning key, is assigned to one of these parts.
The partitioning key is the value that can be found in a specific column of the table. The table being partitioned can improve the performance
considerably, in particular if the single partitions are on different hard disks.

FYI: the PSA is partitioned by the PARTNO field, the F-fact table is partitioned based on the Request and the E-fact table can be partitioned based
on any time characteristic.

Another cause for these symptoms has in many cases been too many uncompressed requests in the F-fact table of the corresponding InfoCube.

Resolution
The correction program in transaction code RSRV normally provides a quick solution. Therefore, please do the following:

1. run transaction code RSRV

2. choose 'All Elementary Tests' -> 'PSA Tables' ->'ConsistencyBetweenPSAPartitionsandSAPAdministrationInformation'
3. entertherelevantPSAtable(you'llgetitfromtheshortdump,inthe'Howtocorrecttheerror'section)&click'execute'(F8)
4. ifyougetanyerror,thenusethe"Correcterror"optionoftransactionRSRVtocorrectit.SAPNote339896 describes this "repair" procedure
in more detail.

If there are too many uncompressed requests in the F-fact table of the corresponding InfoCube, then you should compress the cube on a regular
basis per SAP Note 590370.

Also, if your system is SAP_BW 7.XX, then apply SAP Note 1807028 - 700SP31:ORA 14400 error during ODS Activation / PSA Loading.

Keywords
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" "INSERT_ODS", RSODSACT1, ORA14400, RSDDCVER_PSA_PARTITION,
SAP_DROP_EMPTY_FPARTITIONS, compression
Header Data
Released On 20.03.2013 14:44:57
Release Status Released to Customer
Component BW-WHM-DBA-ODS DataStore Object (classic)
Other Components BW-WHM-DST-PSA Persistent Staging Area
Priority Normal
Category Problem

Product
Product Product Version
SAP NetWeaver SAP enhancement package 1 for SAP NetWeaver 7.0

References
This document refers to:
CSS SAP Notes
1807028 700SP31:ORA 14400 error during ODS Activation / PSA Loading
1236334 Runtime error DBIF_RSQL_SQL_ERROR during load to PSA
590370 Too many uncompressed request (f table partitions)
509660 ORACLE ERROR 14400 during update to the InfoCube
407260 FAQs: Compression of InfoCubes
339896 ORACLE ERROR 14400 when writing to PSA tables