cancel
Showing results for 
Search instead for 
Did you mean: 

"d0_vatta", "volume '%s' locked by other process

Former Member
0 Kudos

Hello ,

We performed successfull backup recovery and log recovery and teh system was up.

But once we stopped system and try starting SAP again .

It gave error while DB start. Saying Disk not accessible .While checking for logs in krnldiag file .

I found this error .

***************************************************************************************************************************************************

ERR 11000 d0_vatta vattach (DEV0): error in fcntl, Resource temporarily unavailable

2011-01-07 09:37:18 14334 ERR 11000 d0_vatta volume '/sapdb/KBP/sapdata1/DISKD0001' locked by process 0

2011-01-07 09:37:18 14325 ERR 11000 vattach dev0_vattach returned FALSE

2011-01-07 09:37:18 14325 ERR 20027 IOMan Attach error on data volume 1: Could not lock volume

2011-01-07 09:37:18 14325 ERR 3 Admin Database state: OFFLINE

2011-01-07 09:37:18 14325 ERR 6 KernelCo + Internal errorcode, Error code 9050 "disk_not_accessible"

2011-01-07 09:37:18 14325 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2011-01-07 09:37:19 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL)

2011-01-07 09:37:19 ___ Stopping GMT 2011-01-07 14:37:19 7.6.06 Build 015-123-238-621

2011-01-07 09:47:19 --- Starting GMT 2011-01-07 14:47:19 7.6.06 Build 015-123-238-621

****************************************************************************************************************************************************

Please suggest what we can do to solve this .

Thanks & Regards,

Garima

Accepted Solutions (0)

Answers (2)

Answers (2)

lbreddemann
Active Contributor
0 Kudos

Ok, so besides opening a support message for that, why don't you tell us what kind of filesystem is '/sapdb/KBP/sapdata1/' ?

Does it happen to be a NFS share?

Have you checked whether the NFS lock daemon is still up'n'running?

Or have you checked with 'lsof' which processes may currently have access to this file?

I remember a case, where a customer tried to create a system copy via file copy and did not understand what paths need to be changed - so he ended up with two instances trying to access the same files... I hope this is not the case for you...!?

regards,

Lars

Former Member
0 Kudos

Hello Lars ,

Thanks for reply , The file system SAPDATA1 is a NFS mount on the system from SAN .

I checked via lsof but din't got any clue . One thing which i think have to do with this may be the hostname.

We used a virtual hostname for installation . But the physical hostaname is different and both of them are pointing to same IP .

so first time we started SAP was with command startsap HOSTNAME .

Also there r no multiple instances on the system . there is only single instance.

So could you suggest any further steps so as to analyse the problem .

Thanks & Regards,

Former Member
0 Kudos

It would be really helpful if you could tell how to check NFS deamon .

Thanks

Garima

Former Member
0 Kudos

I am closing this question , but we were not able to find the solution . Even we created SAP OSS message but no help .

We deleted DB instance nad recreated it .

Regards,

Garima

Former Member
0 Kudos

We already Rebooted the server . But that doesn't work .

Please suggest