Hello All, 8.0.6.2.0 Parallel Server on Solaris 2.6 nodes. We have intermittent outages, once every 2 days, here on a production database. What happens is that all DML transactions dont get committed or rolled back, and start filling up the transaction slots in the rollback segments. On a normal day, I am lucky to find 1 transaction in the rollback segments, but when this happens, the transactions start queing up, and the number of transactions occupying the rollback segment keeps on increasing. These transactions dont get commited or rolled back, and the session status is shown as ACTIVE. There are many layers to this application, viz app servers, web servers and weblogic and connection pools, SRDF to a disaster site. The only resolution is to recycle the whole environment.
The first time this happened, system state dumps were taken, and is still being looked into by Metalink. Any clues as to why this could happen? Thanks Raj -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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).
