Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SQL error "-904" when accessing table .....

skaamin
Newcomer
0 Kudos

Hi,

We are facing this issue in our ECC 6.0 EHP5 system.

Kindly help me how to resolve this issue. here is dump.

Category Installation Errors Runtime Errors DBIF_RSQL_SQL_ERROR Except. CX_SY_OPEN_SQL_DB Date and Time 17.07.2019 11:56:59 ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Short text | | SQL error "-904" when accessing table "ZVATPR". | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |What happened? | | Error Text of the Database: "Resource limit exceeded. MSGID= | | Job=792406/ERP00/WP37" | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |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. | | | | 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. | | | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Error analysis | | An exception occurred that is explained in detail below. | | The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught | | in | | procedure "SALES_UPDATE" "(FORM)", nor was it propagated by a RAISING clause. | | Since the caller of the procedure could not have anticipated that the | | exception would occur, the current program is terminated. | | The reason for the exception is: | | Error Text of the Database: "Resource limit exceeded. MSGID= | | Job=792406/ERP00/WP37" | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |How to correct the error | | Internal call code.........: "[RSQL/OPEN/ZVATPR ]" | | 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" | | "ZMME0001" or "ZMME0001_FD" | | "SALES_UPDATE" | | | | If you cannot solve the problem yourself and want to send an error | | notification to SAP, include the following information: | | | | 1. The description of the current problem (short dump) | | | | To save the description, choose "System->List->Save->Local File | | (Unconverted)". | | | | 2. Corresponding system log | | | | Display the system log by calling transaction SM21. | | Restrict the time interval to 10 minutes before and five minutes | | after the short dump. Then choose "System->List->Save->Local File | | (Unconverted)". | | | | 3. If the problem occurs in a problem of your own or a modified SAP | | program: The source code of the program | | In the editor, choose "Utilities->More | | Utilities->Upload/Download->Download". | | | | 4. Details about the conditions under which the error occurred or which | | actions and input led to the error. | | | | | | 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" | | "ZMME0001" or "ZMME0001_FD" | | "SALES_UPDATE" | | | | If you cannot solve the problem yourself and want to send an error | | notification to SAP, include the following information: | | | | 1. The description of the current problem (short dump) | | | | To save the description, choose "System->List->Save->Local File | | (Unconverted)". | | | | 2. Corresponding system log | | | | Display the system log by calling transaction SM21. | | Restrict the time interval to 10 minutes before and five minutes | | after the short dump. Then choose "System->List->Save->Local File | | (Unconverted)". | | | | 3. If the problem occurs in a problem of your own or a modified SAP | | program: The source code of the program | | In the editor, choose "Utilities->More | | Utilities->Upload/Download->Download". | | | | 4. Details about the conditions under which the error occurred or which | | actions and input led to the error. | | | | The exception must either be prevented, caught within proedure | | "SALES_UPDATE" "(FORM)", or its possible occurrence must be declared in the | | RAISING clause of the procedure. | | To prevent the exception, note the following: | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |System environment | | SAP Release..... 702 | | SAP Basis Level. 0003 | | | | Application server... "SPDR3PRD" | | Network address...... "10.32.2.130" | | Operating system..... "OS400" | | Release.............. "7.1" | | Hardware type........ "0006000E754P" | | Character length.... 16 Bits | | Pointer length....... 64 Bits | | Work process number.. 37 | | Shortdump setting.... "full" | | | | Database server... "SPDR3PRD" | | Database type..... "DB400" | | Database name..... "ERP" | | Database user ID.. "R3ERPDATA" | | | | Terminal.......... "ssco" | | | | Char.set.... "C" | | | | SAP kernel....... 720 | | created (date)... "Mar 22 2012 10:02:58" | | create on........ "AIX 2 5 00092901D600 (IBM i with OS400)" | | Database version. "DB4_53" | | | | Patch level. 201 | | Patch text.. " " | | | | Database............. "V5R3, V5R4, V6R1, V7R1" | | SAP database version. 720 | | Operating system..... "OS400 4 5, OS400 1 6, OS400 1 7" | | | | Memory consumption | | Roll.... 0 | | EM...... 16759168 | | Heap.... 0 | | Page.... 40960 | | MM Used. 7317568 | | MM Free. 1059120 | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |User and Transaction | | Client.............. 500 | | User................ "RBST01" | | Language key........ "E" | | Transaction......... "ZVAT " | | Transaction ID...... "5D2E52D00B1940DCE10080000A200282" | | | | EPP Whole Context ID.... "5D2E32921EDA4091E10080000A200282" | | EPP Connection ID....... 00000000000000000000000000000000 | | EPP Caller Counter...... 0 | | | | Program............. "ZMME0001" | | Screen.............. "SAPLSLVC_FULLSCREEN 0500" | | Screen Line......... 6 | | Debugger Active..... "none" | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Information on where terminated | | Termination occurred in the ABAP program "ZMME0001" - in "SALES_UPDATE". | | The main program was "ZMME0001 ". | | | | In the source code you have the termination point in line 2698 | | of the (Include) program "ZMME0001_FD". | | The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in | | procedure "SALES_UPDATE" "(FORM)", but it was neither handled locally nor | | declared | | in the RAISING clause of its signature. | | | | The procedure is in program "ZMME0001 "; its source code begins in line | | 2294 of the (Include program "ZMME0001_FD ". | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Source Code Extract | ---------------------------------------------------------------------------------------------------- |Line |SourceCde | ---------------------------------------------------------------------------------------------------- | 2668| | | 2669| selopt_d-sign = 'I'. | | 2670| selopt_d-option = 'BT'. | | 2671| | | 2672| CLEAR: unlimited | |=> Heap address = 0x1875c55a0 | |=> Stack address = 0xfffffffffff59d0 | |=> Stack low = 0xfffffffffff59d0 | |=> Stack high = 0xffffffffffff390 | |=> Stack Trace: | |AixStack() at 0x1001472e4 | |CTrcStack2() at 0x100147404 | |CTrcStack() at 0x100147494 | |rabax_CStackSave__Fv@AF171_21() at 0x100159aa0 | |ab_rabax() at 0x10014ab68 | |ab_rsqlerr__FPCUsiT1P11RS_HEADER94T1Pv() at 0x10073be04 | ######|InvokeTargetPgm__FP11qp0z_pcp_cb 103 | |QSYS ######|QP0ZPCPN |QP0ZPCPN ######|Qp0zNewProcess 264 | |QSYS ######|QP0ZPCP2 |QP0ZPCP2 ######|_CXX_PEP__Fv *N | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Database Interface Information | ---------------------------------------------------------------------------------------------------- |C|1|=== TRACE VAR 17 === [dbsldb4dbi.cpp#1601] | |C|1|sqlvar: 17, sqtype 0, sqllen 0, sqlname.data 0 [dbsldb4dbi.cpp#1627] | |C|1|sqlname (hex): [dbsldb4dbi.cpp#1637] | |C|1|0000000000000000 0000000000000000 0000000000000000 0000000000000000 [dbsldb4utl.cpp#2449]| |C|1|=== TRACE VAR 18 === [dbsldb4dbi.cpp#1601] | |C|1|sqlvar: 18, sqtype 0, sqllen 0, sqlname.data 0 [dbsldb4dbi.cpp#1627] | |C|1|sqlname (hex): [dbsldb4dbi.cpp#1637] | |C|1|0000000000000000 0000000000000000 0000000000000000 0000000000000000 [dbsldb4utl.cpp#2449]| |C|1|=== TRACE VAR 19 === [dbsldb4dbi.cpp#1601] | |C|1|sqlvar: 19, sqtype 0, sqllen 0, sqlname.data 0 [dbsldb4dbi.cpp#1627] | |C|1|sqlname (hex): [dbsldb4dbi.cpp#1637] | |C|1|0000000000000000 0000000000000000 0000000000000000 0000000000000000 [dbsldb4utl.cpp#2449]| |C|1|=== TRACE VAR 20 === [dbsldb4dbi.cpp#1601] | |C|1|sqlvar: 20, sqtype 0, sqllen 0, sqlname.data 0

  • SAP Managed Tags:
1 REPLY 1

0 Kudos

HI Amin,

Is the issue is resolved. I am also facing same issue.

Please let me know the solution if it resolved.

  • SAP Managed Tags: