HP3000-L Archives

March 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bob Walker <[log in to unmask]>
Reply To:
Date:
Fri, 10 Mar 2000 10:07:45 PST8PDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
I asked:

> Any ideas what this error message means, and how to recover
> from it??
> Thanks, Bob.
> TURBOIMAGE ERROR AT %022666; RETURN STATUS = -110
> DBOPEN, MODE 1, ON REGDB.PUB.R
> OPENLOG RETURNED ERROR NUMBER 6 TO DBOPEN

Thanks to all that responded, I had already tried most of that stuff.
This one was a bit more involved, so here's the scoop to add to
your repertoire of tricks

- LOG had been stopped the previous night prior to the backup
  and restarted after the backup
- SHOWLOGSTATUS showed the log was running.
- users could get into the database for read but not for write.
- Looking at the database in question with MPEX listf ,access
  showed that an ODBC client via ODBCSE was in the database.
  It turns out that this session was still in from the previous day.
- stopping the ODBC listener stopped the log, the stop had been
pending since the previous night, and was preventing any new
sessions from getting in.
- at this point it was a simple matter of LOG XXX,RESTART and
restarting the ODBC listener to allow everyone back in for write
access.

We already have a procedure in place to logoff all sessions before
backups, looks like we should also stop the ODBC listener job.

Bob

--=--=--
Bob Walker, Computer Centre  --  [log in to unmask]
Capilano College, North Vancouver, BC, CANADA.
------
'No one is listening until you make a mistake.'

ATOM RSS1 RSS2