Thursday, September 17, 2009

Shordump DBIF_RSQL_INVALID_REQUEST

Here is some info from the shordump:

Short text
Invalid request.
What happened?
The current ABAP/4 program terminated due to an internal error in the database interface.
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.
Error analysis
An invalid request was made to the SAP database interface in a statement in which the table "EDID4 " was accessed.

Keywords
"DBIF_RSQL_INVALID_REQUEST"
"SAPLEDI1" or "LEDI1F09"
"F09_IDOC_INSERT_WITH_NUMBER"

The Keywords did confuse me a bit. This shortdump recommend to check transaction SM21. Thats a very importen clue. Remember to check more than just the red lights in SM21.
Under a warning in SM21 I found this information:
ORA-01653: unable to extend table SAPR3.EDI40 by 46075 in tablespace PSAPCLUD
 So the answer is to extend tablespace PSAPCLUD.






I had over 400MB of free space in the mentioned tablespace. It was 95% full.
I did not think it was a problem related to tablespace. Anyway.... a shortdump with the header "DBIF_RSQL_INVALID_REQUEST" can be a tablespace-problem even if the keywords indicate something else.
Please send me a message if you need help to extend tablespace (harald.v@epost.no).

Picture is from: http://img.pte.at/lowrespics/1096894834i23327.jpg
I love sap-commercial ;)
Posted by at

6 comments:

  1. AnonymousNovember 4, 2009 at 1:37 PM

    Hello.

    Have you solved this issue?

    Best regards,

    ReplyDelete
  2. AnonymousNovember 16, 2009 at 8:51 AM

    Harald answered by email november 4:
    Hello.
    In my case it was tablespace. I had to manually extend one tablespace.
    Check SM21 and see if you have any ora-messages.
    I had this message in SM21 (a yellow light):
    ORA-01653: unable to extend table SAPR3.EDI40 by 46075 in tablespace PSAPCLUD

    Let me know if this is not the case at your site.
    best regards
    Harald Vedvik

    ReplyDelete
  3. AnonymousNovember 16, 2009 at 8:52 AM

    Hello Harald.

    Thank you for answering so quickly. I have solved my issue with a SAP System restart.

    I checked all tablespaces before I wrote you and there were no tablespaces with space problem.

    Best regards and thank you.

    ReplyDelete
  4. Panagiotis PapaspyridakosMarch 28, 2016 at 4:23 PM

    well...it certainly was my problem...and your solution worked perfectly...(thanx even some years after) Pan

    ReplyDelete
  5. Panagiotis PapaspyridakosMarch 28, 2016 at 4:23 PM

    well...it certainly was my problem...and your solution worked perfectly...(thanx even some years after) Pan

    ReplyDelete
  6. Kaushik GAugust 21, 2017 at 5:59 PM

    spot on!! :)

    ReplyDelete

Subscribe to: Post Comments (Atom)