Re: ADSM and Informix

Greg,
  It actually is an INFORMIX problem.  You need to upgrade to INFORMIX
7.30.UC5 or later.  I had the same problems when I was running 7.30.UC3 and
UC4.  INFORMIX couldn't recreate the problem so they declared it an ADSM
problem.  My installation was actually crashing when I tried to perform a
parallel backup.  For some reason INFORMIX is not managing its memory
correctly in these versions of 7.30.  If you can't upgrade, try onbar -b -w
instead.  This makes onbar act like ontape, with a single threaded backup.
Performance is not great, but it will work.  If possible though, upgrade
your database as there are other problems with 7.30.UC3, primarily the
alter table command.

Scott Crockford

At 09:39 AM 5/18/99 -0600, you wrote:
>We have a Sun Solaris 2.6 server with ADSM client 3.1.0.5 installed.  The
>servers also has Informix 7.30 installed.  We are backing up the Informix
server
>to a NT ADSM server (3.1.2.0).  The problem is that the backup does not
complete
>successfully.  Informix tech support is stating it is an ADSM problem and
not an
>Informix or Onbar backup problem.  I included part of the onbar log.
>
>The XBSA and ADSM client was setup according to the procedures in the
README.API
>as well as the latest Redbook.
>
>Any help is appreciated.
>
>Thanks
>Greg
>
>===================================================================
>ONBAR BACKUP STARTED - Thu May  6 22:17:06 PDT 1999
>ONCONFIG = onconfig.cf
>INFORMIXDIR = /usr/informix/7.30.UC3
>INFORMIXSERVER = spmtcp
>INFXBSA_SERVER =
>INFXBSA_SCHEDULED =
>INFXBSA_USER_INITIATED =
>INFXBSA_FULL =
>INFXBSA_INCR =
>INFXBSA_CLASS =
>EXECUTING PARALLEL FULL BACKUP (onbar -b)
> 1999-05-06 22:17:08 10519  10518 /usr/informix/7.30.UC3/bin/onbar_d -b -f
>/export/home/informix/dba/onbar_specs.txt
> 1999-05-06 22:17:09 10519  10518 Begin level 0 backup rootdbs.
> 1999-05-06 22:17:09 10519  10518 Successfully connected to Storage Manager.
> 1999-05-06 22:17:10 10519  10518 Completed level 0 backup rootdbs.
> 1999-05-06 22:17:11 10529  10519 Process 10529  10519 successfully forked.
> 1999-05-06 22:17:11 10530  10519 Process 10530  10519 successfully forked.
> 1999-05-06 22:17:11 10531  10519 Process 10531  10519 successfully forked.
> 1999-05-06 22:17:11 10532  10519 Process 10532  10519 successfully forked.
> 1999-05-06 22:17:11 10533  10519 Process 10533  10519 successfully forked.
> 1999-05-06 22:17:12 10529  10519 Begin level 0 backup dbs_llog.
> 1999-05-06 22:17:12 10532  10519 Begin level 0 backup dbs_test.
> 1999-05-06 22:17:12 10529  10519 Successfully connected to Storage Manager.
> 1999-05-06 22:17:12 10530  10519 Begin level 0 backup dbs_plog.
> 1999-05-06 22:17:12 10529  10519 Completed level 0 backup dbs_llog.
> 1999-05-06 22:17:12 10530  10519 Successfully connected to Storage Manager.
> 1999-05-06 22:17:12 10532  10519 Successfully connected to Storage Manager.
> 1999-05-06 22:17:12 10530  10519 Completed level 0 backup dbs_plog.
> 1999-05-06 22:17:12 10531  10519 Begin level 0 backup dbs_dev.
> 1999-05-06 22:17:12 10531  10519 Successfully connected to Storage Manager.
> 1999-05-06 22:17:13 10532  10519 Completed level 0 backup dbs_test.
> 1999-05-06 22:17:13 10533  10519 Begin level 0 backup workdbs.
> 1999-05-06 22:17:14 10533  10519 Successfully connected to Storage Manager.
> 1999-05-06 22:17:14 10529  10519 Process 10529  10519 completed.
> 1999-05-06 22:17:14 10530  10519 Process 10530  10519 completed.
> 1999-05-06 22:17:14 10532  10519 Process 10532  10519 completed.
> 1999-05-06 22:19:16 10533  10519 Completed level 0 backup workdbs.
> 1999-05-06 22:19:19 10533  10519 Process 10533  10519 completed.
> 1999-05-06 22:23:16 10531  10519 Completed level 0 backup dbs_dev.
> 1999-05-06 22:23:24 10531  10519 Process 10531  10519 completed.
> 1999-05-06 22:23:24 10519  10518 Begin backup logical log 1315.
> 1999-05-06 22:23:24 10519  10518 Successfully connected to Storage Manager.
> 1999-05-06 22:23:27 10519  10518 XBSA Error (BSAQueryObject): Backup object
>does not exist in Storage Manager.
> 1999-05-06 22:23:27 10519  10518 ERROR: Missing data for bar_instance set
>clause.
> 1999-05-06 22:23:32 10519  10518 SQL   -25582     Network connection is
broken.
> 1999-05-06 22:23:32 10519  10518 ISAM        9    Bad file number
>### 05/06 22:23 FAILURE 139 IN EXECUTING PARALLEL FULL BACKUP (onbar -b)
> 1999-05-06 22:23:33 10632  10631 /usr/informix/7.30.UC3/bin/onbar_d -l
> 1999-05-06 22:23:33 10632  10631 Begin backup logical log 1315.
> 1999-05-06 22:23:33 10632  10631 Successfully connected to Storage Manager.
> 1999-05-06 22:23:35 10632  10631 XBSA Error (BSAQueryObject): Backup object
>does not exist in Storage Manager.
> 1999-05-06 22:23:35 10632  10631 ERROR: Missing data for bar_instance set
>clause.
> 1999-05-06 22:23:40 10632  10631 SQL   -25582     Network connection is
broken.
> 1999-05-06 22:23:40 10632  10631 ISAM        9    Bad file number
> 1999-05-06 22:26:48 10680  10679 /usr/informix/7.30.UC3/bin/onbar_d -l
> 1999-05-06 22:26:48 10680  10679 Begin backup logical log 1315.
> 1999-05-06 22:26:48 10680  10679 Successfully connected to Storage Manager.
> 1999-05-06 22:26:50 10680  10679 XBSA Error (BSAQueryObject): Backup object
>does not exist in Storage Manager.
> 1999-05-06 22:26:51 10680  10679 ERROR: Missing data for bar_instance set
>clause.
> 1999-05-06 22:26:56 10680  10679 SQL   -25582     Network connection is
broken.
> 1999-05-06 22:26:56 10680  10679 ISAM        9    Bad file number
> 1999-05-06 22:34:03 10743  10742 /usr/informix/7.30.UC3/bin/onbar_d -l
> 1999-05-06 22:34:03 10743  10742 Begin backup logical log 1315.
> 1999-05-06 22:34:03 10743  10742 Successfully connected to Storage Manager.
> 1999-05-06 22:34:05 10743  10742 XBSA Error (BSAQueryObject): Backup object
>does not exist in Storage Manager.
> 1999-05-06 22:34:05 10743  10742 ERROR: Missing data for bar_instance set
>clause.
> 1999-05-06 22:34:10 10743  10742 SQL   -25582     Network connection is
broken.
> 1999-05-06 22:34:10 10743  10742 ISAM        9    Bad file number
>
>