Occasionally Serious Logs Problem

Dear Anyone/Everyone We run "continuous logging" on our box with this software: OS: HP-UX B.11.00 Database: RSAM Version 5.10.UC2 4GL: INFORMIX-4GL Version 4.20.UC2 Just today we had a problem with locking. Users getting SQL -271 and ISAM -154 errors. Then the whole application seemed to freeze, with many users locking many tables. As strange as it seems to fix this: We stopped the "continuous logging" on tbmonitor and re-started it again. All our locking problems went away. The logs were far from full when this action was taken, although they were filling up and the continuous logging did not seem to be backing up the log, even though it is running. This has happened 3 times in the last 6 months usually at a time when we have the most activity (month end). Could someone please explain to me: * Is there a bug in this version of the log backup program that sometimes causes it not backup logs? * What does this have to do with locking? * Is it to do with the rollback transaction high and log water marks? If these questions could be answered. It would be greatly appreciated. Brett Schubert Auspine Ltd

Not a bug a feature. Looks like tbtape was looking for you to change the tape. When that happened in OL5.xx the engine would stop at the next checkpoint and applications would receive errors as you experienced. This behavior was required because of the way the physical log was handled in OL5.xx and was changed in IDS7.xx. In OL5.xx it is critical to change tapes IMMEDIATELY when prompted to do so. It is one reason why so many OL5.xx shops used to send logs to /dev/null. Art S. Kagel Brett Schubert wrote: > > Dear Anyone/Everyone > > We run "continuous logging" on our box with this software: > > OS: HP-UX B.11.00 > Database: RSAM Version 5.10.UC2 > 4GL: INFORMIX-4GL Version 4.20.UC2 > > Just today we had a problem with locking. Users getting SQL -271 and > ISAM -154 errors. Then the whole application seemed to freeze, with many > users locking many tables. > > As strange as it seems to fix this: > We stopped the "continuous logging" on tbmonitor and re-started it again. > All our locking problems went away. The logs were far from full when this > action was taken, although they were filling up and the continuous logging > did not seem to be backing up the log, even though it is running. This has > happened 3 times in the last 6 months usually at a time when we have the > most activity (month end). > > Could someone please explain to me: > * Is there a bug in this version of the log backup program that sometimes > causes it not backup logs? > * What does this have to do with locking? > * Is it to do with the rollback transaction high and log water marks? > > If these questions could be answered. It would be greatly appreciated. > > Brett Schubert > Auspine Ltd