ORA-00060: Deadlock detected

chulett · Post by **chulett** » Fri Apr 22, 2011 9:23 am

A deadlock in the XMETA repository? I would involve your official support provider.

Nagaraj · Post by **Nagaraj** » Fri Apr 22, 2011 10:11 am

official support provider contacted them, waiting for the response.

ray.wurlod · Post by **ray.wurlod** » Fri Apr 22, 2011 2:53 pm

What exact version are you running? What fix packs?

Nagaraj · Post by **Nagaraj** » Fri Apr 22, 2011 5:34 pm

IBM Information Server 8.1 (with Fix Pack 1)

on Redhat Linux

with Oracle as the XMETA

ray.wurlod · Post by **ray.wurlod** » Fri Apr 22, 2011 11:09 pm

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.)

Nagaraj · Post by **Nagaraj** » Sat Apr 23, 2011 6:35 am

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.

ray.wurlod · Post by **ray.wurlod** » Sat Apr 23, 2011 5:03 pm

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.

Nagaraj · Post by **Nagaraj** » Sat Apr 23, 2011 7:39 pm

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.

DSXchange

ORA-00060: Deadlock detected

ORA-00060: Deadlock detected

Update from support