cancel
Showing results for 
Search instead for 
Did you mean: 

Lots of ABAP Dump DBIF_REPO_SQL_ERROR

Former Member
0 Kudos

Hi Experts,

Our system is running on Ibm i series(OS400/DB2). We developed a new program and tcode coppied from ME55(yme55) to do collective PR Release. Now we are getting ABAP dumps sometimes while use this tcode. Dump text is

Database error text........: "Resource limit exceeded. MSGID=

Job=104421/PVT00/WP02"

Internal call code.........: "[RSQL/OPEN/EBAN ]"

Always showing above error but with different different WP.

But this dump is not coming every time while executing yme55.

Can you please help me to resolve it?

Thanks

Asad

Accepted Solutions (1)

Accepted Solutions (1)

Sriram2009
Active Contributor
0 Kudos

Hi

1. On your IBM-i any one having access the SAP table from OS level (related to transaction code ME55) or Any SAP Z program creating locks? Check the lock enters in transaction code SM12

2. Check the SAP kernel level ? if it is low upgrade the kernel

3. Could you share the full dump details as attachment?

4. If possible do stop the SAP instance , IPL, delete the Sql packages as mention by Henry

5. Check this SAP note 1966949 - IBM i: Runtime error DBIF_DSQL2_SQL_ERROR in RSDB4UPD

Regards

Sriram

Former Member
0 Kudos

The full dump is attached here.

Asad

Sriram2009
Active Contributor
0 Kudos

Hi

Thanks for your info

1. Could you check the any lock enters are there in transaction code SM12? related to your custom transaction, if it is yes just clear the enters and than try again.

2. You can check the custom transaction YME55 with help of ABAPer and enabling the trace by using transaction code ST12 over all ABAP & DB performance

BR

SS

Former Member
0 Kudos

Dear Asaduzzaman;

You could review the following SAP note "54028 - IBM i: SQL0 904 reason code 7, overflow in SQL package".

Please delete SQL Package of your system to solve the dump.

Regards.

Henry Orellana

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Asad,

Resource limit exceeded. MSGID=

Job=104421/PVT00/WP02"

Resource limit exceeded means SQL0904 error, and it has different reason code.

--------------------------------------------------------------------------------------------------------------

Message ID . . . . . . . . . :   SQL0904                                    

Message file . . . . . . . . :   QSQLMSG                                    

  Library  . . . . . . . . . :     QSYS                                     

                                                                            

Message . . . . :   Resource limit exceeded.                                

Cause . . . . . :   Resource limit type &1 exceeded with reason code &2.  A 

  list of the limit types follows:                                          

    -- Type 1 indicates that the user profile storage limit or the machine  

  storage limit was exceeded.                                               

    -- Type 2 indicates that the machine lock limit was exceeded.           

    -- Type 3 indicates that the query resource limit was exceeded.  For more

  information see the previously listed message CPD4365.                    

    -- Type 4 indicates that a journal error has occurred.                  

    -- Type 5 indicates that the commit lock limit was exceeded.            

    -- Type 6 indicates that the maximum size of the table has been reached.

    -- Type 7 indicates that the maximum size of the prepared statement area

  has been reached.   

...  

--------------------------------------------------------------------------------------------------------------

For SAP environment, this error usually happens with type 7. And in this case you should follow sap note "54028 - IBM i: SQL0 904 reason code 7, overflow in SQL package" to resolve the issue.

You can find the reason code in os job log, in your case it is 104421/PVT00/WP02.

However sometimes it is with other types, in this case you should report a ticket to SAP or IBM or further check.

Best regards,

Daniel

SAP on IBM i team                                 

Former Member
0 Kudos

Hi Asaduzzaman;

You try to delete the SQL Package. To do this, you must disable your SAP system and run the command DLTR3PKG SID(<SID>) with <SID>ADM or <SID>OFR user.