-
alert log error
DBAs,
This morning we saw a lot of the following errors in the alert log.
Thu Nov 10 09:00:01 CST 2005
ORA-02050: transaction 10.44.117686 rolled back, some remote DBs may be in-doubt
ORA-03106: fatal two-task communication protocol error
ORA-02063: preceding line from INFOTECP
ORA-02068: following severe error from INFOTECP
ORA-03113: end-of-file on communication channel
Basically, what does it mean? What is 10.44.117686?
How to resolve this error?
Thanks!
-
Means you got a distributed transaction that has failed. You will probably have to clean it up. Look at metalink, there's about 100 notes on how to do it...
Jeff Hunter
-
10.44.117686 is the transaction ID, If I am not mistaken.
Next time you get an error, query from
select * from DBA_2PC_PENDING;
select * from sys.PENDING_TRANS$;
And post the result here.
Tamil
-
Never mind, I just wrote something stupid, so I deleted it myself...
Last edited by jmodic; 11-10-2005 at 05:14 PM.
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
-
Thanks for the input.
The results from two queries are as follows:
SQL> exec p ( ' select * from dba_2pc_pending where LOCAL_TRAN_ID = ''10.44.117686''');
LOCAL_TRAN_ID :10.44.117686
GLOBAL_TRAN_ID :PROD.WORLD.355ec77f.10.44.117686
STATE :collecting
MIXED :no
ADVICE :
TRAN_COMMENT :
FAIL_TIME :10-NOV-05
FORCE_TIME :
RETRY_TIME :10-NOV-05
OS_USER :MurphE
OS_TERMINAL :TY25300
HOST :CORPORATE\TY25300
DB_USER :NMTCB
COMMIT# :1947647425
PL/SQL procedure successfully completed.
SQL>
SQL> exec p ( ' select * from sys.pending_trans$ where LOCAL_TRAN_ID = ''10.44.117686''');
LOCAL_TRAN_ID :10.44.117686
GLOBAL_TRAN_FMT :306206
GLOBAL_ORACLE_ID :PROD.WORLD.355ec77f.10.44.117686
GLOBAL_FOREIGN_ID :
TRAN_COMMENT :
STATE :collecting
STATUS :P
HEURISTIC_DFLT :
SESSION_VECTOR :00000001
RECO_VECTOR :00000001
TYPE# :0
FAIL_TIME :10-NOV-05
HEURISTIC_TIME :
RECO_TIME :10-NOV-05
TOP_DB_USER :NMTCB
TOP_OS_USER :MurphE
TOP_OS_HOST :CORPORATE\TY25300
TOP_OS_TERMINAL :TY25300
GLOBAL_COMMIT# :1947647425
SPARE1 :
SPARE2 :
SPARE3 :
SPARE4 :
PL/SQL procedure successfully completed.
I have some questions:
1)The error in the alert log says the transaction roll back. but the query shows the commit# is 947647425. Does this mean it already committed?
2)This transaction is still in the sys.pending_trans$, does this mean
this transaction is still pending?
3) Our current practice is that we just jgnore the alert errors and do nothing. Is this practice good or bad? What should we dba do?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|