ORA-600[18129] WHEN OPENING DATABASE.

PROBLEM:
 
 1. Clear description of the problem encountered:
 
	you are trying to migrate the database from 7.3.4 to 8i. 
	and you have just finished all the steps detailed in the migration manual.
	when you opent he database using resetlogs option, it reutrns an 
ora-600[18129].
 
 2. Pertinent configuration information (MTS/OPS/distributed/etc)
 
	distributed database configuration is being used.
 
 3. Indication of the frequency and predictability of the problem  
	
	Always
 
 4. Sequence of events leading to the problem  
 
	Migration has been complete and you are trying to issue an alter database 
open resetlogs.
 
 5. Technical impact on the customer. Include persistent after effects.
 
	The migration procedure needs to be re-done.
 
=========================    
DIAGNOSTIC ANALYSIS:
 
	When the migration is completed successfully and "alter database open 
resetlogs" 
	statement is given, all the online rollback segments get
	converted to the Oracle8i format and the online redo logs are recreated.  
 
	Now, there might be cases where the customer is using distributed 
transactions and in case there are any pending transactions, alter database 
open restelogs results in an ora-600[18129].
 
 
	This needs to be documented in the Migration guide...the best place would 
possibly be in 
chapter 4: 
Preparing the Oracle7 database for migration as :
point 12: 
	" checking of dba_2pc_pending for pending transactions is mandatory in case 
distributed transactions are being used	"
 
=========================   
WORKAROUND:
 
the only solution here is as follows:
Manual resolution of these in-doubt transactions through "commit force" or 
"rollback force" sql commands before starting the migration exercise should 
lead to its completion without errors.
 
=========================   
RELATED BUGS:
 
=========================   
REPRODUCIBILITY:
 
 1. State if the problem is reproducible; indicate where and predictability
 
	yes. reproducible at will if the workaround is not followed:
 
 2. List the versions in which the problem has reproduced
	8.1.5
 
 3. List any versions in which the problem has not reproduced
 
=========================