hi gurus after all that trace and error stack, oracle has finally conculed that this is a bug and job queue coordinator messes up shared memory so badly it starts throwing 4031 errors for a few hours and eventaully dbwr terminates the instance.
if jobs are the heart beat of ur system,please be aware of this and try to make the number of jobs in the queue less to avoid this issue,rather prolong the time until db crashes. otherwise ina big soup. suggestions: 1. increase job_queue_processes 2. flush share pool frequentl 3. bounce db everyday and i am telling the truth when i say the above were suggested by oracle until the patch is available. thanks sai -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Sai Selvaganesan 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).
