Abap Runtime Error DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

[former_member604827]

Runtime Errors         DBIF_RSQL_SQL_ERROR

Exception              CX_SY_OPEN_SQL_DB

Date and Time          15.07.2015 08:34:58

What happened?

     An exceptional situation has occurred in the ORACLE software,

     possibly due to an error.

     This is not an error in an application program.

What can you do?

     You cannot eliminate this error yourself.

     Please inform your database administrator.

     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.

to correct the error

Database error text........: "ORA-00600: internal error code, arguments:

  [qertbFetchByRowID], [], [], [], [], [], [], []"

Internal call code.........: "[RSQL/FTCH/VBRK ]"

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"

"ZSA_SD_SALES_RPT1" or "ZSA_SD_SALES_RPT1"

"START-OF-SELECTION"

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)

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"

"ZSA_SD_SALES_RPT1" or "ZSA_SD_SALES_RPT1"

"START-OF-SELECTION"

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".

[divyanshu_srivastava3]

Where are you getting this error ? is it for some Z* program ?

Can you explain more on what is happening and upload the full dump in a zipped text file ?

Also, have a look at Oracle's alert log.

Regards,

[bl_vijaykumar]

Oracle Apps DBA & SYSADMIN: How to resolve ORA-00600: [qertbFetchByRowID]

https://scn.sap.com/thread/1639043

ask your DB team to check for indexes and check SCN link

Thanks

Vijay

[bl_vijaykumar]

Hi Syed,

If your program contains any DML statements then possible reason of this problem would be Archive logs.

So please ask your basis team to check for these logs and enough memory is available.

Thanks

vijay

[former_member604827]

Hi Vijay,

their is enough memory for archive logs.

but still getting same error.

[bl_vijaykumar]

may i know what exactly your abap program doing?

I feel like "arguments" you are passing throw your report are causing this error check for the argument where and which a record is fetching.

try to use try and exception concept to find the error record.

Thanks

Vijay

[Sriram2009]

Hi Syed

Could you refer this SAP KBA

1765347 - ORA-00600: internal error code, arguments: [qks3tAllocIDL:1]

1868324 - Handling ORA-600/ORA-7445 error

Regards

SS