cancel
Showing results for 
Search instead for 
Did you mean: 

DBIF_RSQL_SQL_ERROR

Former Member
0 Kudos

Dear Experts,

i am facing the error "DBIF_RSQL_SQL_ERROR" when i am loading the data from DSO to Cube.

i am doing this in Quality system.

i am getting the below message from short dump analysis.

Runtime Errors DBIF_RSQL_SQL_ERROR

Except. CX_SY_OPEN_SQL_DB

"Short text*

SQL error in the database when accessing a table.

What happened?

The database system detected a deadlock and avoided it by rolling back

your transaction.

What can you do?

If possible (and necessary), repeat the last database transaction in the

hope that locking the object will not result in another deadlock."

Please provide me the inputs to solver the issue.

Regards,

Sunil Kumar.B

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Sunil,

please ensure that the index is deleted before loading,and also please remove the semantic key in dtp.

Thanks

Former Member
0 Kudos

Ensure the target cube to which you are trying to load data is not being locked. This could be a possible if 2 or more chains are updating to target or any other target is pulling data from cube while the dso data is being currently added to the cube via dtp.

Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB

Note 1606565 - - Deadlock:DBIF_RSQL_SQL_ERROR on table trfcqout or arfcsstate

Edited by: Arun Bala G on Feb 14, 2012 5:54 AM

Former Member
0 Kudos

Dear All,

There was no other load going on to the Cube.

i have deleted the data from the cube before running the DTP because i have created the new BI 7.0 flow,i have not deleted the indexes since i thought the data has got deleted there will not be any indexes existing.

even i checked DTP settings GOto>settings for batch manage>no of parallel process are 3.

i will change this to 1 and even i will delete the indexes and will try to run the DTP once again.

Regards,

Sunil Kumar.B

Former Member
0 Kudos

Hi Sunil,

We had the similar issue and it was resolved by applying the note suggested above. There are some settings which need to be changed for the affected table by BASIS team in the data base level as per the note. After that this issue was resolved.

Ask BASIS team to increase INITTRANS / MAXTRANS values of the affected table as per the note 84348.

Navesh

Former Member
0 Kudos

Hi Navesh,

Thanks,Sure i will request the Basis team regarding the issue.

Regards,

Sunil Kumar.B

Former Member
0 Kudos

Hi Navesh,

is there any transaction to see the dead locks like SM12 for loack entries.

Regards,

Sunil Kumar.B

Former Member
0 Kudos

you can use Function Module 'ENQUE_READ"

also see TCode DB01 -- Contain Dead Locks in Database level

http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/2d7037ecc92a7ee10000009b38f8cf/frameset.htm

Former Member
0 Kudos

Dear All,

The issue has been resolved where i deleted the indexes and started the DTP.

The load was successfull.

Regards,

Sunil Kumar.B

Former Member
0 Kudos

Hi,

Try applying OSS note 84348 for the table which is causing the dealock. You can find the table name from the Short Dump Log.

Navesh

Former Member
0 Kudos