resetting the sysutils database
Admin unable to run onbar -b backup due to failed Commvault client test data in sysutils database. Solutions provided: completely reset sysutils by dropping it and running bldutil.sh (with optional ixbar file handling), or use less drastic onsmsync commands with -O and -g flags to clean backup history without dropping the database.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi,
this is on a brand new production system:
the backup team of my customer has been trying (on their side) for weeks to
plug a xbsa based backup tool called commvault client onto the informix
instance 12.10FC8W1.
Since we have now run into production for about a week, and that the backup
with commvault is still not operational, I have been thinking in temporarily
use PSM instead. The problem is that sysutils contains data from the tests and
attempts to connect commvault, which are apparently unsuccessful, and those
data prevent from running onbar successfully because backup objects are
missing (ERROR 2) . sysutils has some records in the objects table and other
tables too.
Is there a simple and trusted way to reset all those data, which prevent me to
run onbar -b successfully?
I have my ideas, but I do not want to break it all :-)
TIA
Eric
Hi Eric,
I've used this procedure on 11.70.
# Make sure there are no DB or logical log backups running.
# Take a dbexport of the current sysutils database as a backup:
cd /some_backup_dir
dbexport sysutils -ss
# If you want to retain some history of backups, take a copy then edit your
ixbar file to include DB and logical logs you want to keep. Rename the file if
you want to discard all previous backup info. For example:
cp $INFORMIXDIR/etc/ixbar.1 $INFORMIXDIR/etc/ixbar.1.bkp
vi $INFORMIXDIR/etc/ixbar.1
# edit accordingly and save the file
# OR if you want to discard all previous backup history, rename the file:
mv $INFORMIXDIR/etc/ixbar.1 $INFORMIXDIR/etc/ixbar.1.bkp
# Drop the current sysutils database
echo "drop database sysutils" | dbaccess sysmaster
# If you want to recreate sysutils in another dbspace (not rootdbs), edit
$INFORMIXDIR/etc/sysutils.sql and modify the "create database sysutils with
log;" line near the top with the required dbspace storage clause. Otherwise
just continue with the next step.
# Recreate database sysutils
$INFORMIXDIR/etc/bldutil.sh
# If you wanted to keep some backup history from earlier, populate the new
sysutils database with ixbar entries using Informix onsmsync tool. Otherwise
you should be finished.
onsmsync -b
Stuart
---
Ardenta Limited is ISO/IEC 20000-1 certified. We are proud to be named IT
Supplier Of The Year 2014 and 2013 at eGR B2B Awards.
Ardenta Limited is a company registered in England and Wales. Registered
number: 4181041. Registered office: Saxon House, Downside, Sunbury on Thames,
Middlesex, TW16 6RT.
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of ERIC
VERCELLETTO
Sent: 20 May 2017 11:00
To: ids@iiug.org
Subject: resetting the sysutils database [39264]
Hi,
this is on a brand new production system:
the backup team of my customer has been trying (on their side) for weeks to
plug a xbsa based backup tool called commvault client onto the informix
instance 12.10FC8W1.
Since we have now run into production for about a week, and that the backup
with commvault is still not operational, I have been thinking in temporarily
use PSM instead. The problem is that sysutils contains data from the tests and
attempts to connect commvault, which are apparently unsuccessful, and those
data prevent from running onbar successfully because backup objects are
missing (ERROR 2) . sysutils has some records in the objects table and other
tables too.
Is there a simple and trusted way to reset all those data, which prevent me to
run onbar -b successfully?
I have my ideas, but I do not want to break it all :-) TIA Eric
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Less dastic would be
onsmsync -b
onsmsync -g 0
Regrds,
David.
> On 20 May 2017 at 13:30 Stuart Brooks <stuart.brooks@ardenta.com> wrote:
>
>
> Hi Eric,
>
> I've used this procedure on 11.70.
>
> # Make sure there are no DB or logical log backups running.
>
> # Take a dbexport of the current sysutils database as a backup:
> cd /some_backup_dir
> dbexport sysutils -ss
>
> # If you want to retain some history of backups, take a copy then edit your
> ixbar file to include DB and logical logs you want to keep. Rename the file
if
> you want to discard all previous backup info. For example:
> cp $INFORMIXDIR/etc/ixbar.1 $INFORMIXDIR/etc/ixbar.1.bkp
> vi $INFORMIXDIR/etc/ixbar.1
> # edit accordingly and save the file
>
> # OR if you want to discard all previous backup history, rename the file:
> mv $INFORMIXDIR/etc/ixbar.1 $INFORMIXDIR/etc/ixbar.1.bkp
>
> # Drop the current sysutils database
> echo "drop database sysutils" | dbaccess sysmaster
>
> # If you want to recreate sysutils in another dbspace (not rootdbs), edit
> $INFORMIXDIR/etc/sysutils.sql and modify the "create database sysutils with
> log;" line near the top with the required dbspace storage clause. Otherwise
> just continue with the next step.
>
> # Recreate database sysutils
> $INFORMIXDIR/etc/bldutil.sh
>
> # If you wanted to keep some backup history from earlier, populate the new
> sysutils database with ixbar entries using Informix onsmsync tool. Otherwise
> you should be finished.
> onsmsync -b
>
> Stuart
>
> ---
>
> Ardenta Limited is ISO/IEC 20000-1 certified. We are proud to be named IT
> Supplier Of The Year 2014 and 2013 at eGR B2B Awards.
>
> Ardenta Limited is a company registered in England and Wales. Registered
> number: 4181041. Registered office: Saxon House, Downside, Sunbury on Thames,
> Middlesex, TW16 6RT.
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of ERIC
> VERCELLETTO
> Sent: 20 May 2017 11:00
> To: ids@iiug.org
> Subject: resetting the sysutils database [39264]
>
> Hi,
>
> this is on a brand new production system:
> the backup team of my customer has been trying (on their side) for weeks to
> plug a xbsa based backup tool called commvault client onto the informix
> instance 12.10FC8W1.
>
> Since we have now run into production for about a week, and that the backup
> with commvault is still not operational, I have been thinking in temporarily
> use PSM instead. The problem is that sysutils contains data from the tests
and
> attempts to connect commvault, which are apparently unsuccessful, and those
> data prevent from running onbar successfully because backup objects are
> missing (ERROR 2) . sysutils has some records in the objects table and other
> tables too.
>
> Is there a simple and trusted way to reset all those data, which prevent me
to
> run onbar -b successfully?
>
> I have my ideas, but I do not want to break it all :-) TIA Eric
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Yes David but you are not allowed to onsmsync -g 0 ... smallest value allowed is 1, which makes sense too
onsmsync -O -g 0 https://www.ibm.com/support/knowledgecenter/SSGU8G_12.1.0/com.ibm.bar.doc/ids_ba r_273.htm OR Delete the records from the storage manager and run onsmsync with no options. https://www.ibm.com/support/knowledgecenter/SSGU8G_12.1.0/com.ibm.bar.doc/ids_ba r_435.htm Regards, David. > On 20 May 2017 at 16:07 ERIC VERCELLETTO <eric.vercelletto@begooden-it.com> wrote: > > > Yes David > > but you are not allowed to onsmsync -g 0 ... smallest value allowed is 1, > which makes sense too > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
Hi Eric,
resetting sysutils simply is dropping sysutils. This is what, for=20
instance, would also occur during an upgrade.
There's nothing in sysutils you'd want to keep across a reset.
Of course you'd no longer be able to (warm) restore from a backup before=20
this reset, but at the point of moving to production this probably isn't=20
intended anyway.
Don't forgot to also treat ixbar file similarly (delete or rename it).
Andreas
From: "ERIC VERCELLETTO" <eric.vercelletto@begooden-it.com>
To: ids@iiug.org
Date: 20.05.2017 12:00
Subject: resetting the sysutils database [39264]
Sent by: ids-bounces@iiug.org
Hi,=20
this is on a brand new production system:=20
the backup team of my customer has been trying (on their side) for weeks=20
to=20
plug a xbsa based backup tool called commvault client onto the informix=20
instance 12.10FC8W1.=20
Since we have now run into production for about a week, and that the=20
backup=20
with commvault is still not operational, I have been thinking in=20
temporarily=20
use PSM instead. The problem is that sysutils contains data from the tests =
and=20
attempts to connect commvault, which are apparently unsuccessful, and=20
those=20
data prevent from running onbar successfully because backup objects are=20
missing (ERROR 2) . sysutils has some records in the objects table and=20
other=20
tables too.=20
Is there a simple and trusted way to reset all those data, which prevent=20
me to=20
run onbar -b successfully?=20
I have my ideas, but I do not want to break it all :-)=20
TIA=20
Eric=20
***************************************************************************=
****=20
Forum Note: Use "Reply" to post a response in the discussion forum.=20