cancel
Showing results for 
Search instead for 
Did you mean: 

Table inconsistency at DB level while creating new fields

0 Kudos

Hello All

We are receiving the runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB. The error description says:SQL error 904 when accessing table "PRPS". with additional text of Error Text of the Database: "ORA-00904: "ZZPS_EXPENSE": invalid identifier". whenever we try to access and display data from PRPS table.

We identified that the error is due to non-activation of fields, so we went to SE14 and clicked on Activate and adjust database. The table was successfully activated, but on accessing the table PRPS we received the error message mentioned again.

On checking the database object we could see the inconsistency, kindly find the below screenshot for reference:

The fields mentioned in the above screenshot are the newly added fields to the table.

We asked our basis team to check at DB level, and found that the fields do not exist at Oracle level:

We have tried to activate and adjust (in SE14) a lot of times but no solution. We checked the tablespace in which the table resides and it has sufficient amount of free space. The tablespaces PSAPTEMP and PSAPUNDO also have sufficient space with Autoextend ON.

PS: The problem does not exist in development system. When we move to Quality system the table is behaving normally with no issue, but the problem is happening only in the Pre-Production system (all the system have entries in the table PRPS). The TRs containing the definition are moved in the same order in both Quality and Pre-Production system and we do not require to manually activate and adjust in the Quality system after the transport of the requests.

Request all SAP Gurus to kindly help for the resolution of this issue.

 
 

Accepted Solutions (0)

Answers (3)

Answers (3)

Reagan
Advisor
Advisor
0 Kudos

There is inconsistency at the DB level.

Check if the transport was successfully imported and if not try to import it again.

Call Tx SE11 and check the status of the table.

Try activating the table. If the activation fails check the activation log (in detail).

What was the output/return code when you ran "Activate and Adjust" from Tx SE14.

If the activation is failing then look out for the logs in SM21 and also the Oracle alert log.

Sriram2009
Active Contributor
0 Kudos

Hi

For any table transports do the full system restart, lock all the end user id's and then do the transport.

BR

SS

manish_singh13
Active Contributor
0 Kudos

Hello,

Please check the transport request logs related to PRPS table in your pre-production system and see if the transport objects were imported/generated/activated successfully.

Also please compare the same SE11 & desc SAPSR3.PRPS from your QA to Pre-Prod system because as per details given by you these extra Z* fields doesn't exists at either level (ABAP or DB).

Thanks,

Manish