Unable to start the storage space backup: Smart La

Posted in 2013

Summary

An IDS 11.50 on Solaris 10 user's ON-Bar level-0 backup kept failing on one sbspace with error -12073 "Archive already active on sbspace" (ARCHIVE ERROR: init_archive()/alloc_sb_preimage()), though whole-system backups worked. Art Kagel suggested a prior archive was still running, but no onbar/ontape process could be found; the condition appeared to be a stale lock left after earlier NetBackup/VTL failures. Another user reported the same issue and fixed it by restarting the engine. The poster bounced the instance and the backup then succeeded; no root cause or patch was identified.

Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.

Topics: Backup & Restore, Storage & Space Management, Platform-Specific Issues

Kern Doe — Wed, 16 Jan 2013 00:30:45 — source: IIUG Forums & Mailing Lists

Hello, I'm running IDS 11.50.FC9W1 on Solaris 10, and doing level 0 backup and encountering this error, note that, with "whole system" backup, this error does not so up?? So basically, the only one dbspace that did not get backed up is this smart large object dbspace, (sbdbspace). Does anyone know how to fix this? I'm a little concerned about the ability to restore though. finderr 12073 -12073 Smart Large Objects Archive: Archive already active on sbspace. Another archive is already running on the same sbspace. Ensure that you do not have another archive running on the same sbspace. Only one archive operation on an sbspace at a time is permitted. online.log 01/15/13 18:14:56 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:01 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:06 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:11 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:16 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 bar_act.log 2013-01-15 18:15:06 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:06 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:06 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:11 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:11 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:11 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:16 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:16 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:16 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:26 17347 17345 /informix/bin/onbar_d complete, returning 131 (0x83)

↪ replying to Kern Doe

Art Kagel — Wed, 16 Jan 2013 01:18:48 — source: IIUG Forums & Mailing Lists

Is it possible that an earlier archive was still running? That'swhat the error message indicates. Art On Jan 15, 2013 7:31 PM, "Kern Doe" <kern_doe@yahoo.com> wrote: > Hello, > I'm running IDS 11.50.FC9W1 on Solaris 10, and doing level 0 backup and > encountering this error, note that, with "whole system" backup, this error > does not so up?? So basically, the only one dbspace that did not get > backed up > is this smart large object dbspace, (sbdbspace). Does anyone know how to > fix > this? I'm a little concerned about the ability to restore though. > > finderr 12073 > -12073 Smart Large Objects Archive: Archive already active on sbspace. > Another archive is already running on the same sbspace. Ensure that you > do not have another archive running on the same sbspace. Only one archive > operation on an sbspace at a time is permitted. > > online.log > 01/15/13 18:14:56 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:01 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:06 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:11 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:16 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > > bar_act.log > 2013-01-15 18:15:06 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:06 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:06 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:11 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:16 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:26 17347 17345 /informix/bin/onbar_d complete, returning > 131 > (0x83) > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --bcaec50fe5f5e6c51404d35da8e0

↪ replying to Kern Doe

Ekstrand, — Wed, 16 Jan 2013 03:34:00 — source: IIUG Forums & Mailing Lists

We received this error recently, and had to bounce the database to correct it. After the engine was restarted, the backup completed successfully. Pam Ekstrand Database Administrator Email: pamela.a.ekstrand.-nd@disney.com Home Office: 727-729-8210 Cell: 727-365-3781 ________________________________________ From: ids-bounces@iiug.org [ids-bounces@iiug.org] On Behalf Of Kern Doe [kern_doe@yahoo.com] Sent: Tuesday, January 15, 2013 7:30 PM To: ids@iiug.org Subject: Unable to start the storage space backup: Smar.... [29270] Hello, I'm running IDS 11.50.FC9W1 on Solaris 10, and doing level 0 backup and encountering this error, note that, with "whole system" backup, this error does not so up?? So basically, the only one dbspace that did not get backed up is this smart large object dbspace, (sbdbspace). Does anyone know how to fix this? I'm a little concerned about the ability to restore though. finderr 12073 -12073 Smart Large Objects Archive: Archive already active on sbspace. Another archive is already running on the same sbspace. Ensure that you do not have another archive running on the same sbspace. Only one archive operation on an sbspace at a time is permitted. online.log 01/15/13 18:14:56 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:01 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:06 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:11 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:16 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 bar_act.log 2013-01-15 18:15:06 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:06 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:06 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:11 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:11 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:11 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:16 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:16 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:16 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:26 17347 17345 /informix/bin/onbar_d complete, returning 131 (0x83) ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Ekstrand,

Kern Doe — Wed, 16 Jan 2013 04:12:37 — source: IIUG Forums & Mailing Lists

Thank you very much Pamela. I've been thinking about "bouncing" too. Whatever is holding it is so transparent. ________________________________ From: "Ekstrand, Pamela A. -ND" <Pamela.A.Ekstrand.-ND@disney.com> To: ids@iiug.org Sent: Tuesday, January 15, 2013 9:34 PM Subject: RE: Unable to start the storage space backup: .... [29272] We received this error recently, and had to bounce the database to correct it. After the engine was restarted, the backup completed successfully. Pam Ekstrand Database Administrator Email: pamela.a.ekstrand.-nd@disney.com Home Office: 727-729-8210 Cell: 727-365-3781 ________________________________________ From: ids-bounces@iiug.org [ids-bounces@iiug.org] On Behalf Of Kern Doe [kern_doe@yahoo.com] Sent: Tuesday, January 15, 2013 7:30 PM To: ids@iiug.org Subject: Unable to start the storage space backup: Smar.... [29270] Hello, I'm running IDS 11.50.FC9W1 on Solaris 10, and doing level 0 backup and encountering this error, note that, with "whole system" backup, this error does not so up?? So basically, the only one dbspace that did not get backed up is this smart large object dbspace, (sbdbspace). Does anyone know how to fix this? I'm a little concerned about the ability to restore though. finderr 12073 -12073 Smart Large Objects Archive: Archive already active on sbspace. Another archive is already running on the same sbspace. Ensure that you do not have another archive running on the same sbspace. Only one archive operation on an sbspace at a time is permitted. online.log 01/15/13 18:14:56 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:01 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:06 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:11 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 01/15/13 18:15:16 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() sbsnum=2 sberrno=12073 bar_act.log 2013-01-15 18:15:06 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:06 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:06 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:11 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:11 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:11 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:16 17347 17345 Archive started on sbspace (Requested Level 0). 2013-01-15 18:15:16 17347 17345 Unable to start the storage space backup: Smart Large Objects Archive: Archive already active on sbspace.. 2013-01-15 18:15:16 17347 17345 Archive on sbspace ABORTED (Requested Level 0). 2013-01-15 18:15:26 17347 17345 /informix/bin/onbar_d complete, returning 131 (0x83) ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Art Kagel

Kern Doe — Wed, 16 Jan 2013 04:20:36 — source: IIUG Forums & Mailing Lists

I will try to bounce the engine tomorrow per Pamela's recommendation, then try to back up just that sbdbspace (and/or the entire Level 0). It was true that we had some problems with the NetBackup (VTL) then we submitted the backups more than a couple of times. I'm also curious to know how to stop whatever is holding. Besides ps -eaf | grep onbar, then try onstat -g ntt | grep ontape (found nothing), if I can somehow "terminate" something, then I may skip going down to having to bounce the engine. Thanks Art. ________________________________ From: Art Kagel <art.kagel@gmail.com> To: ids@iiug.org Sent: Tuesday, January 15, 2013 7:18 PM Subject: Re: Unable to start the storage space backup: .... [29271] Is it possible that an earlier archive was still running? That'swhat the error message indicates. Art On Jan 15, 2013 7:31 PM, "Kern Doe" <kern_doe@yahoo.com> wrote: > Hello, > I'm running IDS 11.50.FC9W1 on Solaris 10, and doing level 0 backup and > encountering this error, note that, with "whole system" backup, this error > does not so up?? So basically, the only one dbspace that did not get > backed up > is this smart large object dbspace, (sbdbspace). Does anyone know how to > fix > this? I'm a little concerned about the ability to restore though. > > finderr 12073 > -12073 Smart Large Objects Archive: Archive already active on sbspace. > Another archive is already running on the same sbspace. Ensure that you > do not have another archive running on the same sbspace. Only one archive > operation on an sbspace at a time is permitted. > > online.log > 01/15/13 18:14:56 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:01 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:06 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:11 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:16 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > > bar_act.log > 2013-01-15 18:15:06 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:06 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:06 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:11 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:16 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:26 17347 17345 /informix/bin/onbar_d complete, returning > 131 > (0x83) > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --bcaec50fe5f5e6c51404d35da8e0 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Kern Doe

Ekstrand, — Wed, 16 Jan 2013 14:14:18 — source: IIUG Forums & Mailing Lists

We could never find any indication of anything still running either, so did resort to bouncing the database. I wonder if it may be a bug in versions of 11.50. We are running 11.50.FC5XL. This has only happened twice to us in the last two years. If it happens again, I will call it in to tech support. Good luck. ________________________________________ From: ids-bounces@iiug.org [ids-bounces@iiug.org] On Behalf Of Kern Doe [kern_doe@yahoo.com] Sent: Tuesday, January 15, 2013 11:20 PM To: ids@iiug.org Subject: Re: Unable to start the storage space backup: .... [29274] I will try to bounce the engine tomorrow per Pamela's recommendation, then try to back up just that sbdbspace (and/or the entire Level 0). It was true that we had some problems with the NetBackup (VTL) then we submitted the backups more than a couple of times. I'm also curious to know how to stop whatever is holding. Besides ps -eaf | grep onbar, then try onstat -g ntt | grep ontape (found nothing), if I can somehow "terminate" something, then I may skip going down to having to bounce the engine. Thanks Art. ________________________________ From: Art Kagel <art.kagel@gmail.com> To: ids@iiug.org Sent: Tuesday, January 15, 2013 7:18 PM Subject: Re: Unable to start the storage space backup: .... [29271] Is it possible that an earlier archive was still running? That'swhat the error message indicates. Art On Jan 15, 2013 7:31 PM, "Kern Doe" <kern_doe@yahoo.com> wrote: > Hello, > I'm running IDS 11.50.FC9W1 on Solaris 10, and doing level 0 backup and > encountering this error, note that, with "whole system" backup, this error > does not so up?? So basically, the only one dbspace that did not get > backed up > is this smart large object dbspace, (sbdbspace). Does anyone know how to > fix > this? I'm a little concerned about the ability to restore though. > > finderr 12073 > -12073 Smart Large Objects Archive: Archive already active on sbspace. > Another archive is already running on the same sbspace. Ensure that you > do not have another archive running on the same sbspace. Only one archive > operation on an sbspace at a time is permitted. > > online.log > 01/15/13 18:14:56 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:01 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:06 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:11 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:16 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > > bar_act.log > 2013-01-15 18:15:06 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:06 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:06 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:11 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:16 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:26 17347 17345 /informix/bin/onbar_d complete, returning > 131 > (0x83) > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --bcaec50fe5f5e6c51404d35da8e0 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Ekstrand,

Kern Doe — Thu, 17 Jan 2013 03:05:03 — source: IIUG Forums & Mailing Lists

FYI. Bouncing the instance worked. It doesn't happen so frequently so I'm ok with it for now. Thank you ! ________________________________ From: "Ekstrand, Pamela A. -ND" <Pamela.A.Ekstrand.-ND@disney.com> To: ids@iiug.org Sent: Wednesday, January 16, 2013 8:14 AM Subject: RE: Unable to start the storage space backup: .... [29279] We could never find any indication of anything still running either, so did resort to bouncing the database. I wonder if it may be a bug in versions of 11.50. We are running 11.50.FC5XL. This has only happened twice to us in the last two years. If it happens again, I will call it in to tech support. Good luck. ________________________________________ From: ids-bounces@iiug.org [ids-bounces@iiug.org] On Behalf Of Kern Doe [kern_doe@yahoo.com] Sent: Tuesday, January 15, 2013 11:20 PM To: ids@iiug.org Subject: Re: Unable to start the storage space backup: .... [29274] I will try to bounce the engine tomorrow per Pamela's recommendation, then try to back up just that sbdbspace (and/or the entire Level 0). It was true that we had some problems with the NetBackup (VTL) then we submitted the backups more than a couple of times. I'm also curious to know how to stop whatever is holding. Besides ps -eaf | grep onbar, then try onstat -g ntt | grep ontape (found nothing), if I can somehow "terminate" something, then I may skip going down to having to bounce the engine. Thanks Art. ________________________________ From: Art Kagel <art.kagel@gmail.com> To: ids@iiug.org Sent: Tuesday, January 15, 2013 7:18 PM Subject: Re: Unable to start the storage space backup: .... [29271] Is it possible that an earlier archive was still running? That'swhat the error message indicates. Art On Jan 15, 2013 7:31 PM, "Kern Doe" <kern_doe@yahoo.com> wrote: > Hello, > I'm running IDS 11.50.FC9W1 on Solaris 10, and doing level 0 backup and > encountering this error, note that, with "whole system" backup, this error > does not so up?? So basically, the only one dbspace that did not get > backed up > is this smart large object dbspace, (sbdbspace). Does anyone know how to > fix > this? I'm a little concerned about the ability to restore though. > > finderr 12073 > -12073 Smart Large Objects Archive: Archive already active on sbspace. > Another archive is already running on the same sbspace. Ensure that you > do not have another archive running on the same sbspace. Only one archive > operation on an sbspace at a time is permitted. > > online.log > 01/15/13 18:14:56 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:01 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:06 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:11 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > 01/15/13 18:15:16 ARCHIVE ERROR: init_archive()/alloc_sb_preimage() > sbsnum=2 > sberrno=12073 > > bar_act.log > 2013-01-15 18:15:06 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:06 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:06 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:11 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:11 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Archive started on sbspace (Requested Level > 0). > 2013-01-15 18:15:16 17347 17345 Unable to start the storage space backup: > Smart Large Objects Archive: Archive already active on sbspace.. > 2013-01-15 18:15:16 17347 17345 Archive on sbspace ABORTED (Requested Level > 0). > 2013-01-15 18:15:26 17347 17345 /informix/bin/onbar_d complete, returning > 131 > (0x83) > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --bcaec50fe5f5e6c51404d35da8e0 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Unable to start the storage space backup: Smart La

Related threads

Glossary

Your privacy choices