Page 1 of 1
Posted: Fri Apr 22, 2011 9:23 am
by chulett
A deadlock in the XMETA repository? I would involve your official support provider.
ORA-00060: Deadlock detected
Posted: Fri Apr 22, 2011 10:11 am
by Nagaraj
official support provider contacted them, waiting for the response.
Posted: Fri Apr 22, 2011 2:53 pm
by ray.wurlod
What exact version are you running? What fix packs?
Posted: Fri Apr 22, 2011 5:34 pm
by Nagaraj
IBM Information Server 8.1 (with Fix Pack 1)
on Redhat Linux
with Oracle as the XMETA
Posted: Fri Apr 22, 2011 11:09 pm
by ray.wurlod
Having read through the fixes for that version on Fix Central (I'm installing the same this weekend), I can't see one that addresses this issue. Therefore I'll be curious to hear what your support provider has to say.
(I am presuming, in all of this, that no-one is hacking the XMETA database at your site.)
Update from support
Posted: Sat Apr 23, 2011 6:35 am
by Nagaraj
As of now, what they say is
See if there are any orphaned processes and kill them and recycle the server and check if the issue arises again.
Posted: Sat Apr 23, 2011 5:03 pm
by ray.wurlod
That smacks of addressing the symptom rather than the cause, but you probably should do that anyway just so that you get your XMETA back.
Posted: Sat Apr 23, 2011 7:39 pm
by Nagaraj
xmeta ????
nothing has stopped working, when this issue occured.
scheduled jobs are running fine and the server is doing fine.
everyday this stuff happens at mid night, so there will be no one who is logging in or trying something on the server.