RFC Communication Error while executing DB13 ...

[Former Member]

Dear All,

We are unable to execute Check DB and Update stat from DB13 , we are getting RFC error while executing DB13 .

Access to system SR3 failed

Function Unit ENQUEUE_E_DB6ADMLOCK

Reason OK

Status Complete/Active

RFC Destination

Schema SAPSR3

Component Version 700

Database Host xxxxxLCYS016

Database Release 10.2.0.2.0

while double clicking Check DB or update stat , no further screes are not popup ...

Kindly suggest

Edited by: satheesh0812 on Jan 30, 2012 8:20 AM

[Former Member]

Issue resolved after Restart both SAP and DB

[Former Member]

Satheesh,

I am still confused as you have said you have Oracle and Windows as OS.. then why you have got a lock and unable to run Check DB and stats from DB13..

Let me give some idea on DB6ADMLOCK, is a standard SAP table (structure basically) available within R/3 SAP systems depending on your version and release level. DB6ADMLOCK is the table name and S means shared, E is exclusive In your case ENQUEUE_E_DB6ADMLOCK is a Exclusive lock which has to be there in SM12.. also if you have anything (broken updates in SM13)

DB6ADMLOCK structure is for DB6: Performance-Monitor (UNIX/Windows). Goto DB24 and click on Technical Settings.. and check what DB you have got there ... ??

PY

[Former Member]

Satheesh,

I am still confused as you have said you have Oracle and Windows as OS.. then why you have got a lock and unable to run Check DB and stats from DB13..

Let me give some idea on DB6ADMLOCK, is a standard SAP table (structure basically) available within R/3 SAP systems depending on your version and release level. DB6ADMLOCK is the table name and S means shared, E is exclusive In your case ENQUEUE_E_DB6ADMLOCK is a Exclusive lock which has to be there in SM12.. also if you have anything (broken updates in SM13)

DB6ADMLOCK structure is for DB6: Performance-Monitor (UNIX/Windows). Goto DB24 and click on Technical Settings.. and check what DB you have got there ... ??

PY

[Former Member]

As Orkun said it seems you are on Oracle but you are getting the error which says related to DB2 LUW... however one thing is common which I want you to check if there is any lock is there in SM12..

Go to SM12 . Extras --> Diagnosis and Extras --> Diagnosis in Update just in case if your lock mgmt is working fine in your system.

Also there is a SAPnote which is related to app 7.0 for DB6... Please have a look.. if it helps you..

SAP note: 1314750 : DB6: DBA Cockpit Correction Collection SAP Basis 7.00 / 7.10

Regards

PY

[Former Member]

Due to this any down time will create like Servers are not able to accessable .???

bcoz in SM50 , workprocess are shows running but reason shows ENQ.

Thanks

Edited by: satheesh0812 on Jan 30, 2012 10:04 AM

[Former Member]

No it wont create any kind of System Downtime.. for your current issue ... have a look @

Note 1384191 - SM50: Many processes in status "holds ENQ"

Please mention your Database/SAP/OS name and version...

[Former Member]

DB : Oracle , OS : Windows , SAP : SRM 5.00

we are unable to perform SM12 -> extras -> Diagnotics as well dialognictics in update (It takes more time but still not complete the transaction) .

Regards

Edited by: satheesh0812 on Jan 30, 2012 10:28 AM

[Former Member]

HI all,

now we are getting Time out error as we we have checked SM12 -> Extras -> Statistics .Pls check below log .

Enqueue Operations 0

rejected 0

Error occured 0

Dequeue Operations 0

Error occured 0

Dequeue All Operations 0

Cleanup Operations 0

Backup Operations 0

Read Operations 0

Compress Operations 0

Verify Operations 0

Records written 0

to the backup file 0

Maximum Number of Lock Owners 0

Maximum Fill level 0

Current Fill Level 0

Maximum Number of Lock Arguments 0

Maximum Fill level 0

Current Fill Level 0

Maximum Number of Lock Entries 0

Maximum Fill level 0

Current Fill Level 0

Update; Fill Level at Maximum 0

Current Fill Level 0

Time in Lock Table /Seconds 0.000000s

Wait for Lock Table /Seconds 0.000000s

Time in Lock Server /Seconds 0.000000s

Kindly advise

[former_member204080]

Hi,

Did u restart the server before this.Because in SM12 -> Extras -> Statistics details will be present from when the server is started

[Former Member]

>> bcoz in SM50 , workprocess are shows running but reason shows ENQ.

Ok. I just want understand that the system is running without any problem, but only problem is occured on DB13, isnt it right? This is because, according to your statement, I understand all the workprocesses are waiting for ENQ resource, at the "running" state.

Secondly, I am not sure but, I remember that I faced with that kind of problem, previously. And solved with a note that I can't remember

At this stage, if you are facing with this problem only on DB13, open a ticket to SAP AGS. This is because, it requires an on-site investigation.

Best regards,

Orkun Gedik

[Former Member]

Hi,

>> Access to system SR3 failed

>> Function Unit ENQUEUE_E_DB6ADMLOCK

>> Reason OK

Are you sure that this issue is related by Oracle? Could you check the configuration on DBACOCKPIT?

Best regards,

Orkun Gedik