Larry, > I haven't seen any, but don't UNDO 1555s get written to >alert log >now? > >!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >This is no doubt dependent on environment. If we get ORa-1555, >they're never reported to me. > >I don't manage RBS. I don't do anything with them, they seem >to work fine as is. 1555s (and 4031 and 1652s as well) do not get automatically written into alert log, as they are considered 'User errors' (for whatever clueless reason!). You can enable that though by inserting the following 'event' entries into your init.ora event="1555 trace name errorstack level 3" event="4031 trace name errorstack level 3" event="1652 trace name processstate level 10" Note though, that you will have to keep *all* event lines TOGETHER in the init.ora lines, otherwise only the last ones will take effect. (Same problem with multiple utl_file_dir lines!) Hth, John Kanagaraj <>< DB Soft Inc Phone: 408-970-7002 (W) Disappointment is inevitable, but Discouragement is optional! ** The opinions and facts contained in this message are entirely mine and do not reflect those of my employer or customers ** ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------