SQL error in the database when accessing a table

[Former Member]

Hi,

Need help correcting the error below, this happen when i executed the report again the system but was able to execute it before, i was thinking that i might be due to server patches of i would need to apply an OSS note but not sure what note should be used.

Runtime Errors DBIF_RSQL_SQL_ERROR

Except. CX_SY_OPEN_SQL_DB

Date and Time 20.07.2010 05:20:49

Short text

SQL error in the database when accessing a table.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

How to correct the error

Database error text........: "ORA-20001: Table Change not allowed during

upgrade#ORA-06512: at "SAPR3.00160553FRI", line 1#ORA-04088: error during

execution of trigger 'SAPR3.00160553FRI'"

Internal call code.........: "[RSQL/INSR/ZTXXCTCDET ]"

Please check the entries in the system log (Transaction SM21).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"

"ZTXXC161" or "ZTXXC161"

"F4000_INSERT_RECORDS"

Information on where terminated

Termination occurred in the ABAP program "ZTXXC161" - in

"F4000_INSERT_RECORDS".

The main program was "ZTXXC161 ".

In the source code you have the termination point in line 1841

of the (Include) program "ZTXXC161".

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "F4000_INSERT_RECORDS" "(FORM)", but it was neither handled locally

nor declared

in the RAISING clause of its signature.

Error is particular in the insert line of the code

INSERT into ztxxctcdet

values e_ztxxctcdet.

Edited by: Dendoy23 on Jul 20, 2010 4:13 PM

[Former Member]

>ORA-20001: Table Change not allowed during upgrade

Doesn't that answer your question??

Rob

[Former Member]

Thanks Rob,

Seems to be an upgrade problem indeed, problem is that there was no communication of the upgrade.