Skip to main content

DBIF_RSQL_SQL_ERROR dump, ORA-14400 error FAQ





Symptom

  • DBIF_RSQL_SQL_ERROR short dump in ST22 (exception CX_SY_OPEN_SQL_DB, form routine INSERT_ODS)
  • "ORA-14400: inserted partition key does not map to any partition"
  • The dump & error can occur when writing/inserting to PSA or F-fact tables or when DSO objects are activated.
  • PSA loads fail.
  • Unable to activate DSO requests.
  • DSO activation fails.
  • Activation job BI_ODS..... dumps

Environment

  • SAP NetWeaver 7.0
  • SAP enhancement package 1 for SAP NetWeaver 7.0
  • SAP enhancement package 2 for SAP NetWeaver 7.0
  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP Business Information Warehouse (SAP_BW)

Reproducing the Issue

Dump occuring during DSO activation:
  1. Run tcode RSA1 
  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 occuring 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.
For your information: 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' -> 'Consistency Between PSA Partitions and SAP Administration Information'
  3. enter the relevant PSA table (you'll get it from the short dump, in the 'How to correct the error' section) & click 'execute' (F8)
  4. if you get any error, then use the "Correct error" option of transaction RSRV to correct it. SAP Note 339896 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, DataStore Object
Product
Product or Product Version
SAP NetWeaver 7.0
SAP NetWeaver 7.3
SAP NetWeaver 7.4
SAP enhancement package 1 for SAP NetWeaver 7.0
SAP enhancement package 1 for SAP NetWeaver 7.3
SAP enhancement package 2 for SAP NetWeaver 7.0
Attributes
NameValue
Other ComponentsBW-WHM-DST-PSA Persistent Staging Area
Labels:

Comments

Post a Comment

Popular posts from this blog

SAP Data Domains

SAP Data Domains Double-click the entry ('ZEENUM') in the Domain area, and agree to save the changes made. Now, the 'Create Object Directory Entry' window will re-appear and again it is important to save this development to the '$TMP' development class, via the 'save' or 'local object' button visible in this window. After doing this, a window will appear stating that the new Domain 'ZEENUM' does not exist. Choose 'Yes' to create the Domain, and in the window which appears, type into the 'Short text' box a description of the Domain. In this example, 'Employee Domain': The 'Definition' tab, which, as shown above, opens automatically. The first available field here is 'Data type', click inside the box and select the drop-down menu, and a number of generic data types already existing within the ABAP dictionary will appear. The 'NUMC' type is the one to be used here for the Emplo...
Post a Comment
Read more

SAP Technical Settings

SAP Technical Settings Once this has been saved, the next step is to move on to maintaining the technical settings of the Table. Before creating the final Database table, SAP will need some more information about the table being created. Select 'Technical settings' via the toolbar above the table, through the 'Go to' menu, or with the shortcut CTRL+SHIFT+F9. Here, it is important to tell the system what Data class is to be used, so select the drop down button. There are five different options, with accompanying descriptions. For this table, select the first, labelled 'APPL0', and double-click it: For the 'Size category' field, again click the drop-down button. Here, you have to make an estimate as to the amount of data records which will be held within the table so that the system has some idea of how to create the tables in the underlying database. In this instance, it will be a relatively small amount of information, so select the...
Post a Comment
Read more