is "No according data found in the database. (OpC50-3)" the only error in the sytem.txt? or is followed by another error message that could provide more hints to the root cause of the problem. Also, does this happen for a particualr node only?. does it happen with a particular template only as well?.
Please let us know.
HP Support If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution. If you liked it I would appreciate KUDOs.
For the first error we will need more information like already asked. The best option is to enable tracing to get full details.
For the second issue, put the following into a file (say '/tmp/tfsulock.sql'):
set echo off
set pagesize 60
Column SID FORMAT 999 heading "Sess|ID "
COLUMN OBJECT_NAME FORMAT A17 heading "OBJ NAME or|TRANS_ID" Trunc
COLUMN OSUSER FORMAT A10 heading "Op Sys|User ID"
COLUMN USERNAME FORMAT A8
COLUMN TERMINAL FORMAT A8 trunc
select B.SID, C.USERNAME, C.OSUSER, C.TERMINAL,
DECODE(B.ID2, 0, A.OBJECT_NAME,
5,'Sha Row Exc',
'Other') "Lock Mode",
5,'Sha Row Exc',
'Other') "Req Mode"
from DBA_OBJECTS A, V$LOCK B, V$SESSION C
where A.OBJECT_ID(+) = B.ID1
and B.SID = C.SID
and C.USERNAME is not null
order by B.SID, B.ID2;
select SID, SERIAL# from v$session;
SELECT s.process, s.program, p.spid, p.pid, sid FROM v$session s, v$process p WHERE s.paddr = p.addr;
Then as user "oracle" run:
sqlplus system @/tmp/tfsulock.sql
It will ask you for the password of this Oracle user (this is the password that's also needed during the OMU/OML installation). This will show locks at the moment, but keep in mind that locks are often temporary in nature so you need to run this as soon as possible after you get the ORA-00054 warning (even this does not guaranteee you will catch it). Also, killing the session is usually not a good idea - it's better to understand why it occurs.
In general the ORA-00054 is a warning message and the processes will retry the same request several times before giving up - you will get a different error if this occurs.