Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
A DBA on IDS 7.31 took a production database out of logging, dropped tables/dbspaces, reloaded data, then couldn't switch it back to unbuffered logging — ondblog returned 18 (0x12). The poster solved it by running 'ontape -s -U dbname'. Art Kagel explained why: ondblog only flags the database for the mode change, and an actual archive via ontape or onbar is required to complete it, so repeating the (preferably real, not fake) backup does the job.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
We have IDS V 7.31 UD8 , the db is unbuff log mode , we had put thye db on
nolog mode , then droped four tables , droped releted dbspace ,taken a false
backup ( onbar -b -F), created new dbspace , created the table loaded the data
, created index , constaraints , tried to put the database in unbuff log mode
, it is returning , ONDBLOG COMPLETE ,returning 18 (0x12), I understand this
means It has
failed to put the db in log mode. what is reason, how do I put the db into log
mode again.It is a prod db ,I NEED URGENT HELP
You have to use ontape or onbar to change the logging mode from non-logged
to a logged mode database. Ondblog just marks the DB so that it will be
changed with the next archive, even when it succeeds. Just do the false
backup again, though it would be a good idea to do a real backup that
includes all of the newly loaded data.
Art
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do
those opinions reflect those of other individuals affiliated with any entity
with which I am affiliated nor those of the entities themselves.
On Thu, Jun 18, 2009 at 1:02 AM, SUJIT ROY <roysujit@hotmail.com> wrote:
> We have IDS V 7.31 UD8 , the db is unbuff log mode , we had put thye db on
> nolog mode , then droped four tables , droped releted dbspace ,taken a
> false
> backup ( onbar -b -F), created new dbspace , created the table loaded the
> data
> , created index , constaraints , tried to put the database in unbuff log
> mode
> , it is returning , ONDBLOG COMPLETE ,returning 18 (0x12), I understand
> this
> means It has
> failed to put the db in log mode. what is reason, how do I put the db into
> log
> mode again.It is a prod db ,I NEED URGENT HELP
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001636c594e5ca0698046ca06eb8
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.