Re: onbar error message

Thanks for suggestions. But, I cannot see how could update statistics create long transactions. To be more precise: I have a script located on a server that cron executes every morning at 4:15. The script looks like this: update statistics for table <table_name1> update statistics for table <table_name2>... update statistics for procedure <procedure_name1> update statistics for procedure <procedure_name2>... There is one "update statistics for table/procedure" command for every table/procedure in database. There are 2133 tables and procedures in database. Another point is that only 50-60 logs are used during execution of this script and even if all of them were used but not backed up and ready for reuse, there are another 200 +/- 10 logs ready for reuse at that time (I have 256 logical logs configured at the moment). Maybe it's not a long transaction in question? "Art S. Kagel" <kagel@bloomberg.net> wrote in message news:pan.2004.05.28.11.33.13.43292.19086@bloomberg.net... > On Wed, 26 May 2004 10:00:51 -0400, Davorin Kremenjas wrote: > > It may be that during that time, there is a long transaction running which is > not permitting the backed up logical logs to be released for reuse. If you > can determine that this is the case (run onstat -l perhaps from a cron > periodically or using the -r option to see if this is happening) then you > need to do two things: > > - Increase the size or number of logical logs to accomodate these large > transactions, and/or > > - Recode the tasks that are performing these huge transactions to break them > into smaller logical pieces to reduce the dependency on log space and reduce > recovery time in case of a crash. > > Art S. Kagel