DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

ashit_mehra1 — Thu, 28 Nov 2013 07:38:41 GMT

Hi,

Pls help me with the following dump.....

Category               Installation Errors
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          27.11.2013 15:51:45

Short text

SQL error 60 when accessing table "/BIC/FCC_DAR2".

What happened?

Error Text of the Database: "ORA-00060: deadlock detected while waiting for

resource"

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

procedure "WRITE_ICFACT" "(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: "ORA-00060: deadlock detected while waiting for

resource"

How to correct the error

Internal call code.........: "[RSQL/INSR//BIC/FCC_DAR2 ]"

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"

"GP4PGEVK50SM8L2O5YNRJY0AAFM" or "GP4PGEVK50SM8L2O5YNRJY0AAFM"

"WRITE_ICFACT"

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"

"GP4PGEVK50SM8L2O5YNRJY0AAFM" or "GP4PGEVK50SM8L2O5YNRJY0AAFM"

"WRITE_ICFACT"

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

"WRITE_ICFACT" "(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..... 731

SAP Basis Level. 0005

Application server... "KBIAPP"

Network address...... "172.31.11.92"

Operating system..... "SunOS"

Release.............. "5.10"

Hardware type........ "sun4v"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 31

Shortdump setting.... "full"

Database server... "KBIDBP"

Database type..... "ORACLE"

Database name..... "GBP"

Database user ID.. "SAPSR3"

Terminal.......... " "

Char.set.... "C"

SAP kernel....... 720

created (date)... "Jul 8 2012 19:47:31"

create on........ "SunOS 5.10 Generic_141444-09 sun4us"

Database version. "OCI_112, 11.2.0.2.0, V1, default"

Patch level. 300

Patch text.. " "

Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"

SAP database version. 720

Operating system..... "SunOS 5.10, SunOS 5.11"

Memory consumption

Roll.... 6228560

EM...... 0

Heap.... 197703872

Page.... 32768

MM Used. 166103328

MM Free. 37396400

User and Transaction

Client.............. 780

User................ "ALEREMOTE"

Language key........ "E"

Transaction......... " "

Transaction ID...... "52956F7AB821046FE1000000AC1F0B5C"

EPP Whole Context ID.... "80C0DD10B1491EE2A3E667E707C10E02"

EPP Connection ID....... 00000000000000000000000000000000

EPP Caller Counter...... 0

Program............. "GP4PGEVK50SM8L2O5YNRJY0AAFM"

Screen.............. "SAPMSSY0 1000"

Screen Line......... 6

Debugger Active..... "none"

Information on where terminated

Termination occurred in the ABAP program "GP4PGEVK50SM8L2O5YNRJY0AAFM" - in

"WRITE_ICFACT".

The main program was "RSBATCH_EXECUTE_PROZESS ".

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

of the (Include) program "GP4PGEVK50SM8L2O5YNRJY0AAFM".

The program "GP4PGEVK50SM8L2O5YNRJY0AAFM" was started as a background job.

Job Name....... "BIDTPR_443592_1"

Job Initiator.. "ALEREMOTE"

Job Number..... 14512700

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

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

declared

in the RAISING clause of its signature.

The procedure is in program "GP4PGEVK50SM8L2O5YNRJY0AAFM "; its source code

begins in line

2492 of the (Include program "GP4PGEVK50SM8L2O5YNRJY0AAFM ".

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Former Member — Thu, 28 Nov 2013 08:00:02 GMT

Can you explain when does this error comes?

Any screenshot or the activity done before it?

Regards,

Himanshu

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Former Member — Thu, 28 Nov 2013 08:42:30 GMT

Hi,

As per the dump message, it looks like you are loading data in BW to infocube
This looks like issue in the infocube or issue due to parallel loading leading to table issue.

1. Please wait for the other load in parallel to complete and repeat the step if through process chain or if manual load trigger the load again.

If the error still exists.

Please activate infocube manually or using the program and trigger the load again..

Regards

Jerry

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Former Member — Thu, 28 Nov 2013 08:50:49 GMT

Hi,

Have you checked this note.

1860199 - P31:DTP:BATCH:DBIF_RSQL_INVALID_RSQL: No resources DB conn.

Thanks

Rishi Abrol

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

ashit_mehra1 — Thu, 28 Nov 2013 08:52:22 GMT

Hi jerry,

I consulted the BW consultant.She said she is not loading any data.The error just came suddenly today.

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

S_Sriram — Thu, 28 Nov 2013 09:27:18 GMT

Before that just restart the system and then try once if thing are failed again Kindly refer the SAP Note

1946893 - ORA-00060 Deadlock in Cube load

84348 - Oracle deadlocks, ORA-00060

Regards

Ram

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Former Member — Fri, 29 Nov 2013 08:15:22 GMT

Hi,

The term "WRITE_ICFACT" refers to the writing of the data in the backend using a job which causes deadlock when the same table is accessed by many other loads.

Hence, ask the team to wait for any job to complete or long running job due to various other issues. else follow the action informed above

Thanking you in advance.

Regards

Jerry

Question Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB in Technology Q&A

DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB

Re: DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB