Home » RDBMS Server » Server Administration » ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt (Oracle10g(10.2.0.1.0))
ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402915] Wed, 13 May 2009 01:59 Go to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Hi,all
I am using dblink to connect one of my remote DB.
It`s working fine.But after some time,due to the network failure the following errors ocured.

This is from 9.2.0.1.0 version.

ERROR:
ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt
ORA-02068: following severe error from PRODUCT
ORA-03113: end-of-file on communication channel


ERROR:
ORA-02050: transaction 7.18.20700 rolled back, some remote DBs may be in-doubt
ORA-02068: following severe error from PRODUCT
ORA-03135: connection lost contact

Quote:
ORA-02050: "transaction %s rolled back, some remote DBs may be
in-doubt"
Cause: Network or remote failure in 2PC.
Action: Notify operations; remote DBs will automatically re-sync
when the failure is repaired.

I Googled for this Error,But thats not clear for me.Please Explain.
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402916 is a reply to message #402915] Wed, 13 May 2009 02:08 Go to previous messageGo to next message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
What is not clear for you? What don't you understand?

Regards
Michel
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402918 is a reply to message #402916] Wed, 13 May 2009 02:29 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Do i need to take any action for this Error(IN-DOUBT Condition)?

ARE they (transactions rolled back) from this node only(error occured?)

Thanks
Sriram
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402919 is a reply to message #402918] Wed, 13 May 2009 02:47 Go to previous messageGo to next message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
Do i need to take any action for this Error(IN-DOUBT Condition)?

Not on the database that receives this message. Maybe in the other interested one.

Quote:
ARE they (transactions rolled back) from this node only(error occured?)

Yes or no, both cases can happen.

Do you know what is the two-phase commit?

Regards
Michel
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402930 is a reply to message #402919] Wed, 13 May 2009 04:08 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Not completely.But i have one doubt, what are the exact conditions for this kind of errors? If it only because of Network Error,does it repaired auto matically (Action: Notify operations; remote DBs will automatically re-sync
when the failure is repaired.)when the problem solved.Database open and running in another session perfectly. Is this error because of "connection lost contact".

Thanks
Sriram
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402935 is a reply to message #402930] Wed, 13 May 2009 04:19 Go to previous messageGo to next message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
what are the exact conditions for this kind of errors?

Any interconnect error: when a database cannot reach the transaction coordinator.
How the error can be or not solved is defined in the 2-phase commit protocol.

Regards
Michel

[Updated on: Wed, 13 May 2009 04:20]

Report message to a moderator

Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402945 is a reply to message #402935] Wed, 13 May 2009 04:35 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
ERROR:
ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt
ORA-02068: following severe error from PRODUCT
[B]ORA-03113: end-of-file on communication channel[/B]


Is the Bold one cause this error? or atleast do we know which transaction rollbacked based on transaction number ....8.5.5627
Thanks
Sriram



Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402952 is a reply to message #402945] Wed, 13 May 2009 04:48 Go to previous messageGo to next message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
Is the Bold one cause this error?

Yes but this is a generic error telling "there is a problem".

Quote:
or atleast do we know which transaction rollbacked based on transaction number ....8.5.5627

Can we know your name based on your name?
A transaction is defined by its transaction number, so yes you can know the transaction by the transaction number.

Regards
Michel

Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402977 is a reply to message #402952] Wed, 13 May 2009 05:45 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Michel,
Sorry for my English ..
I mean how we can know the transaction type(Which kind of dml or ddl on which object) based on transaction number.

Thanks
Sriram

[Updated on: Wed, 13 May 2009 05:45]

Report message to a moderator

Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #402991 is a reply to message #402977] Wed, 13 May 2009 06:14 Go to previous messageGo to next message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
A transaction is not of any type.
A transaction is a set of SQL statements or to quote Oracle doc:
Quote:
A transaction is a logical unit of work that contains one or more SQL statements.

This can't be a DDL here.

I recommend you to read Database Concepts, at least the part about transactions.

Regards
Michel
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403019 is a reply to message #402991] Wed, 13 May 2009 08:46 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Hi,Michel thanks for your reply.
I know that
Quote:
Quote:
A transaction is a logical unit of work that contains one or more SQL statements.



Quote:
I mean how we can know the transaction type(Which kind of dml or ddl on which object) based on transaction number

But what i mean is that,
Is there any way to find the transaction types(N Number) based on the transaction number.

Lets say for Example

If I am executing some group of sql statements,and not committed,then after some time, due to the network failure, the error occured. Now i want those statements based on the transaction number, which are rollbacked because of the Error.For this kind of Task, is there any way from Oracle?

Thanks& Regards
Sriram

[Updated on: Wed, 13 May 2009 08:50]

Report message to a moderator

Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403020 is a reply to message #403019] Wed, 13 May 2009 09:04 Go to previous messageGo to next message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
If I am executing some group of sql statements,and not committed,then after some time, due to the network failure, the error occured. Now i want those statements based on the transaction number, which are rollbacked because of the Error.For this kind of Task, is there any way from Oracle?

Only Log Miner can do it for you in your version and even then you will not have the original statements but equivalent ones that to the same modifications. Of course, you will not have remote modifications.

Regards
Michel

[Updated on: Wed, 13 May 2009 09:16]

Report message to a moderator

Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403024 is a reply to message #403020] Wed, 13 May 2009 09:18 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Thank you Michel Smile
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403059 is a reply to message #403024] Wed, 13 May 2009 10:32 Go to previous messageGo to next message
babuknb
Messages: 1734
Registered: December 2005
Location: NJ
Senior Member

>>Now i want those statements based on the transaction number, which are rollbacked because of the Error.For this kind of Task, is there any way from Oracle?

Try to find using DBA_2PC_PENDING.

Babu
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403160 is a reply to message #403059] Thu, 14 May 2009 00:12 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
SQL> select count(*) from DBA_2PC_PENDING;

  COUNT(*)
----------
         0

SQL> select * from DBA_2PC_PENDING;

no rows selected

SQL> select * from DBA_2PC_NEIGHBORS;

no rows selected

SQL> 


But i can say one thing.Before error there are 6205 records in one table @my local DB which is populated through my script (not committed records) But after Error there are 0 rows in the same table@local DB so only the insert statements are roll backed.Each and every transaction is different from each session right?even though we are using db links....so if any thing goes wrong with the current session,then current sessions transactions should be roll backed.So there is no chance of rollback at remote, As we are only selecting records from remote and insert at local Db.Is my assumption correct?

Thanks
Sriram

[Updated on: Thu, 14 May 2009 00:14]

Report message to a moderator

Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403172 is a reply to message #403160] Thu, 14 May 2009 00:53 Go to previous messageGo to next message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Don't make any assumptions, read the concepts about distributed transactions.

By the way, of course there is nothing in the local 2PC views, Oracle told you it has rolled back the transaction. But it MAY have something in the remote one(s) (as the message tells it).

Regards
Michel
Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403179 is a reply to message #403172] Thu, 14 May 2009 01:51 Go to previous messageGo to next message
ramoradba
Messages: 2454
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...
Senior Member
Thanks Michel For your Reply.
I will follow your suggestion "Read concept & Database Administrator's Guide" As i missed some topics.

& one more there is nothing at the remote server`s 2PC views also.
Thanks
Sriram.

Re: ORA-02050: transaction 8.5.5627 rolled back, some remote DBs may be in-doubt [message #403187 is a reply to message #403179] Thu, 14 May 2009 02:22 Go to previous message
Michel Cadot
Messages: 64109
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
there is nothing at the remote server`s 2PC views also.

So this means that the transaction has been completed on these databases too which is not surprising if there were only read accesses on these ones.

Regards
Michel
Previous Topic: .dbf file modified date
Next Topic: Undo TBS full, does transaction rollback or hang?
Goto Forum:
  


Current Time: Mon Dec 05 10:45:24 CST 2016

Total time taken to generate the page: 0.21709 seconds