ARCHIVE ERROR: init_archive()/alloc_sb_preimage()
On IDS 11.50.FC4 (Linux) with ON-Bar/NetBackup, a whole-system level-0 backup aborted when the media server ran out of disk space, and every subsequent archive (onbar and ontape) then failed with "ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=33 sberrno=12073". Art Kagel and IBM's Martin Fuerderer advised contacting Tech Support, suggesting a dbspace flag was left set by the aborted archive. Others identified it as APAR IC63442 (failed whole-system backup causes sberrno=12073), fixed in 11.50.xC5; bouncing the engine clears the sbspace error, and using onbar -b instead of onbar -b -w is a workaround. The poster planned to apply the workaround and upgrade.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi All,
IDS 11.50.FC4
Redhat Linux 2.6.9-42.ELsmp #1 SMP x86_64
NetBackup-RedHat2.6 6.5.4
We use onbar with NetBackup (storage manager). Unfortunately, media server ran
out of disk space and onbar Level 0 archive had been aborted with the
following error in OnLine message log. Since then every time cron kicks off
Level 0 archive, we get the same error. We tried ontape with no luck and got
the same error. Onbar is backing up logical logs nicely. From my past
experience, restarting the engine had resolved the issue but one of our senior
guys told that restart wouldnt work and only way is to restore last successful
Level 0 archive and roll forward the logs. Being a production server (24X7)
and having so many interface connected, its make life more difficult for an
outage window. My objective to have only one outage to bounce the engine and
if does not work then try whatever you all suggest before I go back to IBM
support. Restore would be the last choice. I think IDS 11.50.FC5 has got a fix
for similar issue but not 100% sure. Is there any
work around to avoid this situation in future as chances are there that media
server may run out of disk space again?
Prompt response would be HIGHLY appreciated.
ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=33 sberrno=12073
TIA
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
Call IBM Tech support.
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, Dec 3, 2009 at 7:50 PM, H.G <hariog@yahoo.com> wrote:
> Hi All,
> IDS 11.50.FC4
> Redhat Linux 2.6.9-42.ELsmp #1 SMP x86_64
> NetBackup-RedHat2.6 6.5.4
>
> We use onbar with NetBackup (storage manager). Unfortunately, media server
> ran
> out of disk space and onbar Level 0 archive had been aborted with the
> following error in OnLine message log. Since then every time cron kicks off
> Level 0 archive, we get the same error. We tried ontape with no luck and
> got
> the same error. Onbar is backing up logical logs nicely. From my past
> experience, restarting the engine had resolved the issue but one of our
> senior
> guys told that restart wouldnt work and only way is to restore last
> successful
> Level 0 archive and roll forward the logs. Being a production server (24X7)
> and having so many interface connected, its make life more difficult for an
> outage window. My objective to have only one outage to bounce the engine
> and
> if does not work then try whatever you all suggest before I go back to IBM
> support. Restore would be the last choice. I think IDS 11.50.FC5 has got a
> fix
> for similar issue but not 100% sure. Is there any
> work around to avoid this situation in future as chances are there that
> media
> server may run out of disk space again?
>
> Prompt response would be HIGHLY appreciated.
>
> ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=33 sberrno=12073
>
> TIA
>
> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> http://in.yahoo.com/
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--0023545bdaacc8b95b0479dc85bd
Hi,
as already adviced by Art: Please contact IBM Informix
Technical Support.
My guess is, that for some dbspace a flag that gets
set during the archive operation has not been
reset due to the abort of the archive operation.
Tech Support should be able to find out, whether my
thought is correct. If it is, then
a) this is a defect that should be fixed ... i.e. to reset
the flag(s) properly in case of such an archive abort.
b) Tech Support may well be able to logon to your
machine and correct the flag setting by patching
it on disk. This would then require only a rather
short downtime of the system. Whether it would be
possible to patch something like this while the system
keeps running - I don't know. But they will tell you. :)
For both items it is necessary that you contact
Tech Support. So it really is the best advice that
I can give.
Regards, Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martin Jetter
Board of Management: Dirk Wittkopp
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
ids-bounces@iiug.org wrote on 12/04/2009 01:50:06 AM:
>
> Hi All,
> IDS 11.50.FC4
> Redhat Linux 2.6.9-42.ELsmp #1 SMP x86_64
> NetBackup-RedHat2.6 6.5.4
>
> We use onbar with NetBackup (storage manager). Unfortunately,
> media server ran
> out of disk space and onbar Level 0 archive had been aborted with the
> following error in OnLine message log. Since then every time cron kicks
off
> Level 0 archive, we get the same error. We tried ontape with no
> luck and got
> the same error. Onbar is backing up logical logs nicely. From my past
> experience, restarting the engine had resolved the issue but one
> of our senior
> guys told that restart wouldnt work and only way is to restore
> last successful
> Level 0 archive and roll forward the logs. Being a production server
(24X7)
> and having so many interface connected, its make life more difficult for
an
> outage window. My objective to have only one outage to bounce the
> engine and
> if does not work then try whatever you all suggest before I go back to
IBM
> support. Restore would be the last choice. I think IDS 11.50.FC5
> has got a fix
> for similar issue but not 100% sure. Is there any
> work around to avoid this situation in future as chances are there
> that media
> server may run out of disk space again?
>
> Prompt response would be HIGHLY appreciated.
>
> ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=33
sberrno=12073
>
> TIA
>
> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> http://in.yahoo.com/
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Thanks Martin & Art for your prompt response. We have organised an outage this
weekend to bounce the server BUT now I am almost certain recycling of engine
will not resolve the issue as both of you have adviced to contact IBM tech
support.
I am also assuming engine will not allow drop/recreate this Smart Blobspace
(33) which we don't use otherwise you would have suggested this earlier. Is
this correct?
Once again, thank you very much for your help.
HG
________________________________
From: Martin Fuerderer <MARTINFU@de.ibm.com>
To: ids@iiug.org
Sent: Fri, 4 December, 2009 8:13:55 PM
Subject: Re: ARCHIVE ERROR: init_archive()/alloc_sb_pre.... [18271]
Hi,
as already adviced by Art: Please contact IBM Informix
Technical Support.
My guess is, that for some dbspace a flag that gets
set during the archive operation has not been
reset due to the abort of the archive operation.
Tech Support should be able to find out, whether my
thought is correct. If it is, then
a) this is a defect that should be fixed ... i.e. to reset
the flag(s) properly in case of such an archive abort.
b) Tech Support may well be able to logon to your
machine and correct the flag setting by patching
it on disk. This would then require only a rather
short downtime of the system. Whether it would be
possible to patch something like this while the system
keeps running - I don't know. But they will tell you. :)
For both items it is necessary that you contact
Tech Support. So it really is the best advice that
I can give.
Regards, Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martin Jetter
Board of Management: Dirk Wittkopp
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
ids-bounces@iiug.org wrote on 12/04/2009 01:50:06 AM:
>
> Hi All,
> IDS 11.50.FC4
> Redhat Linux 2.6.9-42.ELsmp #1 SMP x86_64
> NetBackup-RedHat2.6 6.5.4
>
> We use onbar with NetBackup (storage manager). Unfortunately,
> media server ran
> out of disk space and onbar Level 0 archive had been aborted with the
> following error in OnLine message log. Since then every time cron kicks
off
> Level 0 archive, we get the same error. We tried ontape with no
> luck and got
> the same error. Onbar is backing up logical logs nicely. From my past
> experience, restarting the engine had resolved the issue but one
> of our senior
> guys told that restart wouldnt work and only way is to restore
> last successful
> Level 0 archive and roll forward the logs. Being a production server
(24X7)
> and having so many interface connected, its make life more difficult for
an
> outage window. My objective to have only one outage to bounce the
> engine and
> if does not work then try whatever you all suggest before I go back to
IBM
> support. Restore would be the last choice. I think IDS 11.50.FC5
> has got a fix
> for similar issue but not 100% sure. Is there any
> work around to avoid this situation in future as chances are there
> that media
> server may run out of disk space again?
>
> Prompt response would be HIGHLY appreciated.
>
> ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=33
sberrno=12073
>
> TIA
>
> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> http://in.yahoo.com/
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
Hi,
you can try engine bounce, but my guess is,
that it will not improve the situation. But try.
Also, try drop and re-create of the dbspace.
As I don't know what exactly (e.g. which flag)
causes the problem, I don't know whether
drop and re-create will be possible.
Still, I think involvement of Technical Support
would also help to find out the root cause and
getting this fixed - to prevent future occurance
of the problem ...
Regards, Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martin Jetter
Board of Management: Dirk Wittkopp
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
ids-bounces@iiug.org wrote on 12/04/2009 11:20:46 AM:
>
> Thanks Martin & Art for your prompt response. We have organised an
> outage this
> weekend to bounce the server BUT now I am almost certain recyclingof
engine
> will not resolve the issue as both of you have adviced to contact IBM
tech
> support.
>
> I am also assuming engine will not allow drop/recreate this Smart
Blobspace
> (33) which we don't use otherwise you would have suggested this earlier.
Is
> this correct?
>
> Once again, thank you very much for your help.
>
> HG
>
> ________________________________
> From: Martin Fuerderer <MARTINFU@de.ibm.com>
> To: ids@iiug.org
> Sent: Fri, 4 December, 2009 8:13:55 PM
> Subject: Re: ARCHIVE ERROR: init_archive()/alloc_sb_pre.... [18271]
>
> Hi,
>
> as already adviced by Art: Please contact IBM Informix
> Technical Support.
>
> My guess is, that for some dbspace a flag that gets
> set during the archive operation has not been
> reset due to the abort of the archive operation.
>
> Tech Support should be able to find out, whether my
> thought is correct. If it is, then
> a) this is a defect that should be fixed ... i.e. to reset
> the flag(s) properly in case of such an archive abort.
> b) Tech Support may well be able to logon to your
> machine and correct the flag setting by patching
> it on disk. This would then require only a rather
> short downtime of the system. Whether it would be
> possible to patch something like this while the system
> keeps running - I don't know. But they will tell you. :)
>
> For both items it is necessary that you contact
> Tech Support. So it really is the best advice that
> I can give.
>
> Regards, Martin
> --
> Martin Fuerderer
> IBM Informix Development Munich, Germany
> Information Management
>
> IBM Deutschland Research & Development GmbH
> Chairman of the Supervisory Board: Martin Jetter
> Board of Management: Dirk Wittkopp
> Corporate Seat: Boeblingen, Germany
> Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
>
> ids-bounces@iiug.org wrote on 12/04/2009 01:50:06 AM:
> >
> > Hi All,
> > IDS 11.50.FC4
> > Redhat Linux 2.6.9-42.ELsmp #1 SMP x86_64
> > NetBackup-RedHat2.6 6.5.4
> >
> > We use onbar with NetBackup (storage manager). Unfortunately,
> > media server ran
> > out of disk space and onbar Level 0 archive had been aborted with the
> > following error in OnLine message log. Since then every time cron
kicks
> off
> > Level 0 archive, we get the same error. We tried ontape with no
> > luck and got
> > the same error. Onbar is backing up logical logs nicely. From my past
> > experience, restarting the engine had resolved the issue but one
> > of our senior
> > guys told that restart wouldnt work and only way is to restore
> > last successful
> > Level 0 archive and roll forward the logs. Being a production server
> (24X7)
> > and having so many interface connected, its make life more difficult
for
> an
> > outage window. My objective to have only one outage to bounce the
> > engine and
> > if does not work then try whatever you all suggest before I go back to
> IBM
> > support. Restore would be the last choice. I think IDS 11.50.FC5
> > has got a fix
> > for similar issue but not 100% sure. Is there any
> > work around to avoid this situation in future as chances are there
> > that media
> > server may run out of disk space again?
> >
> > Prompt response would be HIGHLY appreciated.
> >
> > ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=33
> sberrno=12073
> >
> > TIA
> >
> > The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> > http://in.yahoo.com/
> >
> >
> >
>
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> http://in.yahoo.com/
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Once again thanks Martin for an excellent information on this issue. This
information not only helped me for my understanding but also helped to explain
this to senior management.
________________________________
From: Martin Fuerderer <MARTINFU@de.ibm.com>
To: ids@iiug.org
Sent: Fri, 4 December, 2009 10:03:10 PM
Subject: Re: ARCHIVE ERROR: init_archive()/alloc_sb_pre.... [18273]
Hi,
you can try engine bounce, but my guess is,
that it will not improve the situation. But try.
Also, try drop and re-create of the dbspace.
As I don't know what exactly (e.g. which flag)
causes the problem, I don't know whether
drop and re-create will be possible.
Still, I think involvement of Technical Support
would also help to find out the root cause and
getting this fixed - to prevent future occurance
of the problem ...
Regards, Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland Research & Development GmbH
Chairman of the Supervisory Board: Martin Jetter
Board of Management: Dirk Wittkopp
Corporate Seat: Boeblingen, Germany
Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
ids-bounces@iiug.org wrote on 12/04/2009 11:20:46 AM:
>
> Thanks Martin & Art for your prompt response. We have organised an
> outage this
> weekend to bounce the server BUT now I am almost certain recyclingof
engine
> will not resolve the issue as both of you have adviced to contact IBM
tech
> support.
>
> I am also assuming engine will not allow drop/recreate this Smart
Blobspace
> (33) which we don't use otherwise you would have suggested this earlier.
Is
> this correct?
>
> Once again, thank you very much for your help.
>
> HG
>
> ________________________________
> From: Martin Fuerderer <MARTINFU@de.ibm.com>
> To: ids@iiug.org
> Sent: Fri, 4 December, 2009 8:13:55 PM
> Subject: Re: ARCHIVE ERROR: init_archive()/alloc_sb_pre.... [18271]
>
> Hi,
>
> as already adviced by Art: Please contact IBM Informix
> Technical Support.
>
> My guess is, that for some dbspace a flag that gets
> set during the archive operation has not been
> reset due to the abort of the archive operation.
>
> Tech Support should be able to find out, whether my
> thought is correct. If it is, then
> a) this is a defect that should be fixed ... i.e. to reset
> the flag(s) properly in case of such an archive abort.
> b) Tech Support may well be able to logon to your
> machine and correct the flag setting by patching
> it on disk. This would then require only a rather
> short downtime of the system. Whether it would be
> possible to patch something like this while the system
> keeps running - I don't know. But they will tell you. :)
>
> For both items it is necessary that you contact
> Tech Support. So it really is the best advice that
> I can give.
>
> Regards, Martin
> --
> Martin Fuerderer
> IBM Informix Development Munich, Germany
> Information Management
>
> IBM Deutschland Research & Development GmbH
> Chairman of the Supervisory Board: Martin Jetter
> Board of Management: Dirk Wittkopp
> Corporate Seat: Boeblingen, Germany
> Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294
>
> ids-bounces@iiug.org wrote on 12/04/2009 01:50:06 AM:
> >
> > Hi All,
> > IDS 11.50.FC4
> > Redhat Linux 2.6.9-42.ELsmp #1 SMP x86_64
> > NetBackup-RedHat2.6 6.5.4
> >
> > We use onbar with NetBackup (storage manager). Unfortunately,
> > media server ran
> > out of disk space and onbar Level 0 archive had been aborted with the
> > following error in OnLine message log. Since then every time cron
kicks
> off
> > Level 0 archive, we get the same error. We tried ontape with no
> > luck and got
> > the same error. Onbar is backing up logical logs nicely. From my past
> > experience, restarting the engine had resolved the issue but one
> > of our senior
> > guys told that restart wouldnt work and only way is to restore
> > last successful
> > Level 0 archive and roll forward the logs. Being a production server
> (24X7)
> > and having so many interface connected, its make life more difficult
for
> an
> > outage window. My objective to have only one outage to bounce the
> > engine and
> > if does not work then try whatever you all suggest before I go back to
> IBM
> > support. Restore would be the last choice. I think IDS 11.50.FC5
> > has got a fix
> > for similar issue but not 100% sure. Is there any
> > work around to avoid this situation in future as chances are there
> > that media
> > server may run out of disk space again?
> >
> > Prompt response would be HIGHLY appreciated.
> >
> > ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=33
> sberrno=12073
> >
> > TIA
> >
> > The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> > http://in.yahoo.com/
> >
> >
> >
>
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> http://in.yahoo.com/
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/
You mentioned it in your initial post - this sure smells like: IC63442 AN ONBAR BACKUP WILL FAIL WITH SBERRNO=12073 IF A PREVIOUS ONBAR WHOLE SYSTEM BACKUP FAILED. Fixed in UC/FC5 Dunno if you were doing the whole system backup earlier or not, or if the bug really requires a failed whole system backup to rear its head... anyhoo support will hook you up or my name ain't Nathan Arizona.
Hi HG,
I encountered the same problem earlier, it is related to the following
APAR
APAR IC63442 - AN ONBAR BACKUP WILL FAIL WITH SBERRNO=12073 IF A
PREVIOUS ONBAR WHOLE SYSTEM BACKUP FAILED.
Bouncing the IDS will resolve the sbspace error.
Pls contact Tech Support for the fix.
The workaround is to use onbar -b instead of onbar -b -w.
Rgds.
Alex
H.G wrote:
Once again thanks Martin for an excellent information on this issue. This
information not only helped me for my understanding but also helped to explain
this to senior management.
________________________________
From: Martin Fuerderer [1]<MARTINFU@de.ibm.com>
To: [2]ids@iiug.org
Sent: Fri, 4 December, 2009 10:03:10 PM
Subject: Re: ARCHIVE ERROR: init_archive()/alloc_sb_pre.... [18273]
Hi,
you can try engine bounce, but my guess is,
that it will not improve the situation. But try.
Also, try drop and re-create of the dbspace.
As I don't know what exactly (e.g. which flag)
causes the problem, I don't know whether
drop and re-create will be possible.
Still, I think involvement of Technical Support
would also help to find out the root cause and
getting this fixed - to prevent future occurance
of the problem ...
Regards, Martin
--
Alex Kwan
References
1. mailto:MARTINFU@de.ibm.com
2. mailto:ids@iiug.org
Thanks a ton Mike & Alex. Yes, we do whole system backup.
Alex thanks for sharing the work around. I will use -b instead of -w until we
get proper response from IBM Tech Support on Monday. It sounds like we need to
plan for upgrade (IDS 11.50.FC5).
Once again, thanks to this forum for this support.
________________________________
From: Alex Kwan <kwanacs@gmail.com>
To: ids@iiug.org
Sent: Sat, 5 December, 2009 12:35:40 PM
Subject: Re: ARCHIVE ERROR: init_archive()/alloc_sb_pre.... [18281]
Hi HG,
I encountered the same problem earlier, it is related to the following
APAR
APAR IC63442 - AN ONBAR BACKUP WILL FAIL WITH SBERRNO=12073 IF A
PREVIOUS ONBAR WHOLE SYSTEM BACKUP FAILED.
Bouncing the IDS will resolve the sbspace error.
Pls contact Tech Support for the fix.
The workaround is to use onbar -b instead of onbar -b -w.
Rgds.
Alex
H.G wrote:
Once again thanks Martin for an excellent information on this issue. This
information not only helped me for my understanding but also helped to explain
this to senior management.
________________________________
From: Martin Fuerderer [1]<MARTINFU@de.ibm.com>
To: [2]ids@iiug.org
Sent: Fri, 4 December, 2009 10:03:10 PM
Subject: Re: ARCHIVE ERROR: init_archive()/alloc_sb_pre.... [18273]
Hi,
you can try engine bounce, but my guess is,
that it will not improve the situation. But try.
Also, try drop and re-create of the dbspace.
As I don't know what exactly (e.g. which flag)
causes the problem, I don't know whether
drop and re-create will be possible.
Still, I think involvement of Technical Support
would also help to find out the root cause and
getting this fixed - to prevent future occurance
of the problem ...
Regards, Martin
--
Alex Kwan
References
1. mailto:MARTINFU@de.ibm.com
2. mailto:ids@iiug.org
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
http://in.yahoo.com/