Is anyone having deadlocking issues with the 8.1.7.2 release of Oracle? If you are, how serious are these errors? What are the consequences of the deadlock error messages. How long does it actually take to clean up the deadlocks? Does one of the transactions roll back? Does it then reissue later? I've opened a TAR but support seems unable to answer these questions to my satisfaction and I can't find this particular problem documented on Metalink. Maybe I'm not searching on the right thing. The error number seems to have very little information associated with it.
We are doing some advance testing of an upgrade from 8.0.4 to 8.1.7.2 of a data warehouse. We are using partitioning, the STAR_TRANSFORMATION set to true, otherwise, a fairly typical database. We are using version 2.6 of Sun Solaris, EMC disk, and Veritas volume manager. During testing of two data load scripts, we get recurring deadlock errors on the 8.1.7.2 test database. We can reproduce these errors every time we run these scripts togethe In our current 8.0.4 database, we run the two scripts together and it is not an option to run them sequentially, instead of concurrently, since we don't have a long enough window to run them concurrently. Thanks in advance for any help. Cherie Machler Oracle DBA Gelco Information Network -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).