Onbar and PSM
Posted in 2016
Frank (IDS 12.10.FC4, PSM) ran onsmsync to expire old backups; it worked but the bar log showed errors -43231/-43259 about missing /usr/informix/lib/ibsad001.so, plus PSM log errors (C-ISAM dsmFetchDetail error 17). Rafael suggested setting BAR_BSALIB_PATH to the real library (libtxbsa.so) or creating a symlink ibsad001.so -> libtxbsa.so. Setting the parameter to libtxbsa.so instead failed (missing libApiTSM64.so, the TSM library), while leaving it unset worked via onbar's fallback to PSM. John Miller explained onbar tries the configured/system path first then falls back to PSM, and that a valid BAR_BSALIB_PATH avoids the message; he also noted onbar's advantage is parallel dbspace backups. The thread ends with Rafael suggesting the symlink approach, with no confirmed resolution recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Backup & Restore, Versions, Editions & End-of-Life
HI,
IDS 12.10 FC4
I was testing onbar and using onsmsync to clean older backup files.
When I run the onsmsync -i "3 00:00:00" , the following are logs of BAR and
PSM.
Both logs have error lines, but the it seems the old backup files were
cleaned up as expected.
Any comments to have a error-free log ?
Thanks
Frank
==========BAR log
2016-08-09 19:10:32 34596 54555 onsmsync -i 3 00:00:00
2016-08-09 19:10:34 34596 54555 Syncing sysutils and bootfile...
2016-08-09 19:10:35 34596 54555 (-43231) An unexpected error occurred:
/usr/informix/lib/ibsad001.so: can
not open shared object file: No such file or directory .
2016-08-09 19:10:35 34596 54555 (-43259) Could not open XBSA library
/usr/informix/lib/ibsad001.so, so try
ing default path.
2016-08-09 19:10:35 34596 54555 Using IBM's PSM version 12.10.FC4W1XU as
the Storage Manager. XBSA API ver
sion is 1.0.3.
2016-08-09 19:10:35 34596 54555 Successfully connected to Storage Manager.
2016-08-09 19:10:35 34596 54555 Querying for backups expired at Storage
Manager...
2016-08-09 19:10:35 34596 54555 Building current timeline...
2016-08-09 19:10:35 34596 54555 Applying expiration policies...
2016-08-09 19:10:47 34596 54555 Regenerating sysutils and bootfile...
2016-08-09 19:10:47 34596 54555 (-43050) Copy of old emergency bootfile
saved in /usr/informix/etc/ixbar.2
5.20160809.191047 .
2016-08-09 19:10:47 34596 54555 onsmsync complete, returning 0 (0x00)
=========PSM log
2016-08-09 19:10:35 34596 54555 smdbopen.c:117 nsmOpenDatabase: Count:
opened = 8, missing = 0.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 dsm_obj.c:658 dsmMakeObjectCursorList: No
more records from object table.
2016-08-09 19:10:35 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:37 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:38 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:38 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:41 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:41 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:42 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:42 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:42 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:43 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:43 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:44 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchDetail' returned error (17).
2016-08-09 19:10:44 34596 54555 smobject.c:1580 Error -88001: C-ISAM
function 'dsmFetchD
Hi Frank. First, I would recommend you to solve the library issue: /usr/informix/lib/ibsad001.so: can not open shared object file: No such file or directory . Could not open XBSA library /usr/informix/lib/ibsad001.so Maybe a symbolic link missing because newest releases of IDS doesn't create it. To diagnose the problem: - Check ONCONFIG parameter BAR_BSALIB_PATH - ls -l (value of parameter BAR_BSALIB_PATH) - If file does not exist, create a symbolic link pointing the parameter value to the actual file. Then try backup again Best regards.
Hi, Rafael.
It seems it is OK for me to use onbar to backup or restore the whole
system . Both onbar and PSM seems working OK for full backup or full
restore.
There would be some errors in the log if I try to run other tasks,
e.g., time-point restore, clean older expired backup files ...
Our BAR_BSALIB_PATH is not set in configuration file( so use default).
# BAR_BSALIB_PATH - The shared library for ON-Bar and the
The following is the list of the lib directory,
What link I need create ? or what I need do ?
Thanks
Frank
[informix@walter ~]$ cd /usr/informix/lib
[informix@walter lib]$ ll
total 42088
drwxr-xr-x 2 informix informix 4096 Feb 23 2015 c++
drwxr-xr-x 2 informix informix 4096 Feb 23 2015 cli
drwxr-xr-x 3 informix informix 4096 Feb 23 2015 client
drwxr-xr-x 2 informix informix 4096 Feb 23 2015 csm
drwxr-xr-x 2 informix informix 4096 Feb 23 2015 dmi
drwxr-xr-x 2 informix informix 4096 Feb 23 2015 esql
-rwxr-xr-x 3 informix informix 325577 Jun 4 2014 iasfs09b.so
-rwxr-xr-x 3 informix informix 325982 Jun 4 2014 iasft09b.so
-rwxr-xr-x 2 informix informix 5713 Jun 4 2014 icsss09a.so
-rwxr-xr-x 1 informix informix 8978 Feb 19 2015 iosm11a.so
-rwxr-xr-x 1 informix informix 15658 Feb 19 2015 ipldd11a.so
-rwxr-xr-x 1 informix informix 317625 Feb 19 2015 libAPI.jar
-rw-r--r-- 2 informix informix 461970 Jun 4 2014 libasf.a
-rwxr-xr-x 1 informix informix 171047 Feb 19 2015 libastool.so
-rwxr-xr-x 1 informix informix 14273 Feb 19 2015 libbsanull.so
-r-xr-xr-x 1 informix informix 1882019 Feb 19 2015 libbsapsm.so
-rw-r--r-- 1 informix informix 754432 Jun 4 2014 libdrda.a
-rwxr-xr-x 1 informix informix 11764626 Feb 19 2015 libdwa.udr
-rw-r--r-- 2 informix informix 461970 Jun 4 2014 libifasf.a
-rwxr-xr-x 3 informix informix 325577 Jun 4 2014 libifasf.so
-rw-r--r-- 1 informix informix 1534 Jun 4 2014 libifcss.a
-rwxr-xr-x 2 informix informix 5713 Jun 4 2014 libifcss.so
-rwxr-xr-x 3 informix informix 325577 Jun 4 2014 libixasf.so
-rwxr-xr-x 1 informix informix 232029 Feb 19 2015 libnativeAPI.so
-rwxr-xr-x 1 informix informix 8657 Jun 4 2014 libnetstub.so
-rwxr-xr-x 3 informix informix 325982 Jun 4 2014 libtasf.so
-rw-r--r-- 1 informix informix 463326 Jun 4 2014 libthasf.a
-rwxr-xr-x 3 informix informix 325982 Jun 4 2014 libthasf.so
-r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so
-rwxr-xr-x 1 informix informix 24322746 Feb 19 2015 libxml.udr
-rw-r--r-- 1 informix informix 4960 Jun 4 2014 netstub.a
[informix@walter lib]$
On Wed, Aug 10, 2016 at 1:32 AM, RAFAEL GOMEZ <rgomezs@gmail.com> wrote:
> Hi Frank.
>
> First, I would recommend you to solve the library issue:
>
> /usr/informix/lib/ibsad001.so: can not open shared object file: No such
> file
> or directory .
> Could not open XBSA library /usr/informix/lib/ibsad001.so
>
> Maybe a symbolic link missing because newest releases of IDS doesn't create
> it.
>
> To diagnose the problem:
> - Check ONCONFIG parameter BAR_BSALIB_PATH
> - ls -l (value of parameter BAR_BSALIB_PATH)
> - If file does not exist, create a symbolic link pointing the parameter
> value
> to the actual file.
>
> Then try backup again
>
> Best regards.
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a1143f7ae53729b0539bcd650
Hi Frank. You have the library in your lib directory, it's: -r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so There are two options: - Create symbolic link: ln -s /usr/informix/lib/libtxbsa.so /usr/informix/lib/ibsad001.so - Change ONCONFIG parameter: BAR_BSALIB_PATH /usr/informix/lib/libtxbsa.so Best regards.
Rafael,
I set the parameter,
BAR_BSALIB_PATH /usr/informix/lib/libtxbsa.so
The lib file is,
[informix@walter onbar]$ ll /usr/informix/lib/libtxbsa.so
-r-xr-xr-x 1 informix informix 58585 Feb 19 2015
/usr/informix/lib/libtxbsa.so
But when I run onsmsync -i "1 00:00:00" to clean old file, Online
log shows,
2016-08-11 15:11:59 21982 18193 onsmsync -i 1 00:00:00
2016-08-11 15:12:02 21982 18193 Syncing sysutils and bootfile...
2016-08-11 15:12:02 21982 18193 (-43231) An unexpected error occurred:
libApiTSM64.so: cannot open shared object file: No such file or directory .
2016-08-11 15:12:02 21982 18193 (-43259) Could not open XBSA library
/usr/informix/lib/libtxbsa.so, so trying default path.
2016-08-11 15:12:02 21982 18193 onsmsync complete, returning 133 (0x85)
Any idea?
Thanks
Frank
On Thu, Aug 11, 2016 at 6:50 AM, RAFAEL GOMEZ <rgomezs@gmail.com> wrote:
> Hi Frank.
>
> You have the library in your lib directory, it's:
>
> -r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so
>
> There are two options:
>
> - Create symbolic link:
>
> ln -s /usr/informix/lib/libtxbsa.so /usr/informix/lib/ibsad001.so
>
> - Change ONCONFIG parameter:
>
> BAR_BSALIB_PATH /usr/informix/lib/libtxbsa.so
>
> Best regards.
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--94eb2c192314d0ff480539cd4bae
Interesting thing is, if I reset BAR_BSALIB_PATH to undefined, The
command can be run successfully ( even though there are different errors
in BAR log, see below).
2016-08-11 15:23:39 27121 18193 onsmsync -i 1 00:00:00
2016-08-11 15:23:41 27121 18193 Syncing sysutils and bootfile...
2016-08-11 15:23:41 27121 18193 (-43231) An unexpected error occurred:
/usr/informix/lib/ibsad001. so: cannot open shared object file:
No such file or directory .
2016-08-11 15:23:41 27121 18193 (-43259) Could not open XBSA library
/usr/informix/lib/ibsad001.so, so trying default path.
2016-08-11 15:23:41 27121 18193 Using IBM's PSM version 12.10.FC4W1XU as
the Storage Manager. XBSA API version is 1.0.3.
2016-08-11 15:23:41 27121 18193 Successfully connected to Storage Manager.
2016-08-11 15:23:41 27121 18193 Querying for backups expired at Storage
Manager...
2016-08-11 15:23:41 27121 18193 Building current timeline...
2016-08-11 15:23:41 27121 18193 Applying expiration policies...
2016-08-11 15:23:51 27121 18193 Regenerating sysutils and bootfile...
2016-08-11 15:23:51 27121 18193 (-43050) Copy of old emergency bootfile
saved in /usr/informix/etc/ ixbar.25.20160811.152351 .
2016-08-11 15:23:51 27121 18193 onsmsync complete, returning 0 (0x00)
Wish more tips here , Want to be error-free .
Thanks
Frank
On Thu, Aug 11, 2016 at 11:19 AM, FRANK <yunyaoqu@gmail.com> wrote:
> Rafael,
>
> I set the parameter,
>
> BAR_BSALIB_PATH /usr/informix/lib/libtxbsa.so
>
> The lib file is,
> [informix@walter onbar]$ ll /usr/informix/lib/libtxbsa.so
> -r-xr-xr-x 1 informix informix 58585 Feb 19 2015
> /usr/informix/lib/libtxbsa.so
>
> But when I run onsmsync -i "1 00:00:00" to clean old file, Online
> log shows,
>
> 2016-08-11 15:11:59 21982 18193 onsmsync -i 1 00:00:00
> 2016-08-11 15:12:02 21982 18193 Syncing sysutils and bootfile...
> 2016-08-11 15:12:02 21982 18193 (-43231) An unexpected error occurred:
> libApiTSM64.so: cannot open shared object file: No such file or directory .
> 2016-08-11 15:12:02 21982 18193 (-43259) Could not open XBSA library
> /usr/informix/lib/libtxbsa.so, so trying default path.
> 2016-08-11 15:12:02 21982 18193 onsmsync complete, returning 133 (0x85)
>
> Any idea?
>
> Thanks
> Frank
>
> On Thu, Aug 11, 2016 at 6:50 AM, RAFAEL GOMEZ <rgomezs@gmail.com> wrote:
>
> > Hi Frank.
> >
> > You have the library in your lib directory, it's:
> >
> > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so
> >
> > There are two options:
> >
> > - Create symbolic link:
> >
> > ln -s /usr/informix/lib/libtxbsa.so /usr/informix/lib/ibsad001.so
> >
> > - Change ONCONFIG parameter:
> >
> > BAR_BSALIB_PATH /usr/informix/lib/libtxbsa.so
> >
> > Best regards.
> >
> >
> > ************************************************************
> > *******************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --94eb2c192314d0ff480539cd4bae
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a1144ba528826080539cd77de
Yes, onbar and psm try to be very friendly.
It tries the system library location first, then if it fails falls back to
the location it knows PSM is installed at.
Now if you wanted to use another product which is not PSM and an accident
change to your config happened, then this fall back would be a problem.
John F. Miller III
miller3@us.ibm.com
503-747-1366
ids-bounces@iiug.org wrote on 08/11/2016 08:32:11 AM:
> From: "FRANK" <yunyaoqu@gmail.com>
> To: ids@iiug.org
> Date: 08/11/2016 08:33 AM
> Subject: Re: Onbar and PSM [37578]
> Sent by: ids-bounces@iiug.org
>
> Interesting thing is, if I reset BAR=5FBSALIB=5FPATH to undefined, The
> command can be run successfully ( even though there are different errors
> in BAR log, see below).
>
> 2016-08-11 15:23:39 27121 18193 onsmsync -i 1 00:00:00
> 2016-08-11 15:23:41 27121 18193 Syncing sysutils and bootfile...
> 2016-08-11 15:23:41 27121 18193 (-43231) An unexpected error occurred:
> /usr/informix/lib/ibsad001. so: cannot open shared object file:
> No such file or directory .
> 2016-08-11 15:23:41 27121 18193 (-43259) Could not open XBSA library
> /usr/informix/lib/ibsad001.so, so trying default path.
> 2016-08-11 15:23:41 27121 18193 Using IBM's PSM version 12.10.FC4W1XU as
> the Storage Manager. XBSA API version is 1.0.3.
> 2016-08-11 15:23:41 27121 18193 Successfully connected to Storage
Manager.
> 2016-08-11 15:23:41 27121 18193 Querying for backups expired at Storage
> Manager...
> 2016-08-11 15:23:41 27121 18193 Building current timeline...
> 2016-08-11 15:23:41 27121 18193 Applying expiration policies...
> 2016-08-11 15:23:51 27121 18193 Regenerating sysutils and bootfile...
> 2016-08-11 15:23:51 27121 18193 (-43050) Copy of old emergency bootfile
> saved in /usr/informix/etc/ ixbar.25.20160811.152351 .
> 2016-08-11 15:23:51 27121 18193 onsmsync complete, returning 0 (0x00)
>
> Wish more tips here , Want to be error-free .
>
> Thanks
> Frank
>
> On Thu, Aug 11, 2016 at 11:19 AM, FRANK <yunyaoqu@gmail.com> wrote:
>
> > Rafael,
> >
> > I set the parameter,
> >
> > BAR=5FBSALIB=5FPATH /usr/informix/lib/libtxbsa.so
> >
> > The lib file is,
> > [informix@walter onbar]$ ll /usr/informix/lib/libtxbsa.so
> > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015
> > /usr/informix/lib/libtxbsa.so
> >
> > But when I run onsmsync -i "1 00:00:00" to clean old file, Online
> > log shows,
> >
> > 2016-08-11 15:11:59 21982 18193 onsmsync -i 1 00:00:00
> > 2016-08-11 15:12:02 21982 18193 Syncing sysutils and bootfile...
> > 2016-08-11 15:12:02 21982 18193 (-43231) An unexpected error occurred:
> > libApiTSM64.so: cannot open shared object file: No such file or
directory .
> > 2016-08-11 15:12:02 21982 18193 (-43259) Could not open XBSA library
> > /usr/informix/lib/libtxbsa.so, so trying default path.
> > 2016-08-11 15:12:02 21982 18193 onsmsync complete, returning 133 (0x85)
> >
> > Any idea?
> >
> > Thanks
> > Frank
> >
> > On Thu, Aug 11, 2016 at 6:50 AM, RAFAEL GOMEZ <rgomezs@gmail.com>
wrote:
> >
> > > Hi Frank.
> > >
> > > You have the library in your lib directory, it's:
> > >
> > > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so
> > >
> > > There are two options:
> > >
> > > - Create symbolic link:
> > >
> > > ln -s /usr/informix/lib/libtxbsa.so /usr/informix/lib/ibsad001.so
> > >
> > > - Change ONCONFIG parameter:
> > >
> > > BAR=5FBSALIB=5FPATH /usr/informix/lib/libtxbsa.so
> > >
> > > Best regards.
> > >
> > >
> > > ************************************************************
> > > *******************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> > --94eb2c192314d0ff480539cd4bae
> >
> >
> > ************************************************************
> > *******************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --001a1144ba528826080539cd77de
>
>
>
***************************************************************************=
****
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Thank you John!
Two questions,
1) This is first time we try Onbar, PSM might be our only option .
Can we avoid these error lines in BAR log? ( I do not like any error
in the log)
2) We have been using ONTAPE from the beginning , as data and
transaction volume get bigger and busier , We experienced ONTAPE could
be significantly impacted by application's busy IO work. For example,
backup time could be varied in roller-coaster way from 2 hours to 5 hours
( possibly more next when more volumes get in).
Generally speaking, ONBAR should be much more faster than ONTAPE , is
that basically true ? ( like to hear more experiences of onbar...)
On Thu, Aug 11, 2016 at 11:50 AM, John Miller iii <miller3@us.ibm.com>
wrote:
> Yes, onbar and psm try to be very friendly.
> It tries the system library location first, then if it fails falls back to
> the location it knows PSM is installed at.
>
> Now if you wanted to use another product which is not PSM and an accident
> change to your config happened, then this fall back would be a problem.
>
> John F. Miller III
> miller3@us.ibm.com
> 503-747-1366
>
> ids-bounces@iiug.org wrote on 08/11/2016 08:32:11 AM:
>
> > From: "FRANK" <yunyaoqu@gmail.com>
> > To: ids@iiug.org
> > Date: 08/11/2016 08:33 AM
> > Subject: Re: Onbar and PSM [37578]
> > Sent by: ids-bounces@iiug.org
> >
> > Interesting thing is, if I reset BAR=5FBSALIB=5FPATH to undefined, The
> > command can be run successfully ( even though there are different errors
> > in BAR log, see below).
> >
> > 2016-08-11 15:23:39 27121 18193 onsmsync -i 1 00:00:00
> > 2016-08-11 15:23:41 27121 18193 Syncing sysutils and bootfile...
> > 2016-08-11 15:23:41 27121 18193 (-43231) An unexpected error occurred:
> > /usr/informix/lib/ibsad001. so: cannot open shared object file:
> > No such file or directory .
> > 2016-08-11 15:23:41 27121 18193 (-43259) Could not open XBSA library
> > /usr/informix/lib/ibsad001.so, so trying default path.
> > 2016-08-11 15:23:41 27121 18193 Using IBM's PSM version 12.10.FC4W1XU as
> > the Storage Manager. XBSA API version is 1.0.3.
> > 2016-08-11 15:23:41 27121 18193 Successfully connected to Storage
> Manager.
> > 2016-08-11 15:23:41 27121 18193 Querying for backups expired at Storage
> > Manager...
> > 2016-08-11 15:23:41 27121 18193 Building current timeline...
> > 2016-08-11 15:23:41 27121 18193 Applying expiration policies...
> > 2016-08-11 15:23:51 27121 18193 Regenerating sysutils and bootfile...
> > 2016-08-11 15:23:51 27121 18193 (-43050) Copy of old emergency bootfile
> > saved in /usr/informix/etc/ ixbar.25.20160811.152351 .
> > 2016-08-11 15:23:51 27121 18193 onsmsync complete, returning 0 (0x00)
> >
> > Wish more tips here , Want to be error-free .
> >
> > Thanks
> > Frank
> >
> > On Thu, Aug 11, 2016 at 11:19 AM, FRANK <yunyaoqu@gmail.com> wrote:
> >
> > > Rafael,
> > >
> > > I set the parameter,
> > >
> > > BAR=5FBSALIB=5FPATH /usr/informix/lib/libtxbsa.so
> > >
> > > The lib file is,
> > > [informix@walter onbar]$ ll /usr/informix/lib/libtxbsa.so
> > > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015
> > > /usr/informix/lib/libtxbsa.so
> > >
> > > But when I run onsmsync -i "1 00:00:00" to clean old file, Online
> > > log shows,
> > >
> > > 2016-08-11 15:11:59 21982 18193 onsmsync -i 1 00:00:00
> > > 2016-08-11 15:12:02 21982 18193 Syncing sysutils and bootfile...
> > > 2016-08-11 15:12:02 21982 18193 (-43231) An unexpected error occurred:
> > > libApiTSM64.so: cannot open shared object file: No such file or
> directory .
> > > 2016-08-11 15:12:02 21982 18193 (-43259) Could not open XBSA library
> > > /usr/informix/lib/libtxbsa.so, so trying default path.
> > > 2016-08-11 15:12:02 21982 18193 onsmsync complete, returning 133 (0x85)
>
> > >
> > > Any idea?
> > >
> > > Thanks
> > > Frank
> > >
> > > On Thu, Aug 11, 2016 at 6:50 AM, RAFAEL GOMEZ <rgomezs@gmail.com>
> wrote:
> > >
> > > > Hi Frank.
> > > >
> > > > You have the library in your lib directory, it's:
> > > >
> > > > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so
> > > >
> > > > There are two options:
> > > >
> > > > - Create symbolic link:
> > > >
> > > > ln -s /usr/informix/lib/libtxbsa.so /usr/informix/lib/ibsad001.so
> > > >
> > > > - Change ONCONFIG parameter:
> > > >
> > > > BAR=5FBSALIB=5FPATH /usr/informix/lib/libtxbsa.so
> > > >
> > > > Best regards.
> > > >
> > > >
> > > > ************************************************************
> > > > *******************
> > > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >
> > > >
> > >
> > > --94eb2c192314d0ff480539cd4bae
> > >
> > >
> > > ************************************************************
> > > *******************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> > --001a1144ba528826080539cd77de
> >
> >
> >
> ************************************************************
> ***************=
> ****
>
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--94eb2c1244b6c92a750539d161db
If you put a valid path name in the onconfig file for BAR=5FBASLIB=5FPATH t=
hen
this error should
not be seen.
onbar can run in parallel across your dbspaces. This is one of its large
advantages.
If you only have a single dbspace then onbar and ontape will run vary close
to the
same speed, because there would not be any parallelism seen.
Also onpsm and onsmsync help you clean up old backup automatically. There
are database scheduler tasks which have been setup to do all of this
automatically
which can be configure by hand or by use OAT.
Hope this helps,
John F. Miller III
miller3@us.ibm.com
503-747-1366
ids-bounces@iiug.org wrote on 08/11/2016 01:12:27 PM:
> From: "FRANK" <yunyaoqu@gmail.com>
> To: ids@iiug.org
> Date: 08/11/2016 01:13 PM
> Subject: Re: Onbar and PSM [37584]
> Sent by: ids-bounces@iiug.org
>
> Thank you John!
>
> Two questions,
>
> 1) This is first time we try Onbar, PSM might be our only option .
> Can we avoid these error lines in BAR log? ( I do not like any error
> in the log)
>
> 2) We have been using ONTAPE from the beginning , as data and
> transaction volume get bigger and busier , We experienced ONTAPE could
> be significantly impacted by application's busy IO work. For example,
> backup time could be varied in roller-coaster way from 2 hours to 5 hours
> ( possibly more next when more volumes get in).
>
> Generally speaking, ONBAR should be much more faster than ONTAPE , is
> that basically true ? ( like to hear more experiences of onbar...)
>
> On Thu, Aug 11, 2016 at 11:50 AM, John Miller iii <miller3@us.ibm.com>
> wrote:
>
> > Yes, onbar and psm try to be very friendly.
> > It tries the system library location first, then if it fails falls back
to
> > the location it knows PSM is installed at.
> >
> > Now if you wanted to use another product which is not PSM and an
accident
> > change to your config happened, then this fall back would be a problem.
> >
> > John F. Miller III
> > miller3@us.ibm.com
> > 503-747-1366
> >
> > ids-bounces@iiug.org wrote on 08/11/2016 08:32:11 AM:
> >
> > > From: "FRANK" <yunyaoqu@gmail.com>
> > > To: ids@iiug.org
> > > Date: 08/11/2016 08:33 AM
> > > Subject: Re: Onbar and PSM [37578]
> > > Sent by: ids-bounces@iiug.org
> > >
> > > Interesting thing is, if I reset BAR=3D5FBSALIB=3D5FPATH to undefined,
The
> > > command can be run successfully ( even though there are different
errors
> > > in BAR log, see below).
> > >
> > > 2016-08-11 15:23:39 27121 18193 onsmsync -i 1 00:00:00
> > > 2016-08-11 15:23:41 27121 18193 Syncing sysutils and bootfile...
> > > 2016-08-11 15:23:41 27121 18193 (-43231) An unexpected error
occurred:
> > > /usr/informix/lib/ibsad001. so: cannot open shared object file:
> > > No such file or directory .
> > > 2016-08-11 15:23:41 27121 18193 (-43259) Could not open XBSA library
> > > /usr/informix/lib/ibsad001.so, so trying default path.
> > > 2016-08-11 15:23:41 27121 18193 Using IBM's PSM version 12.10.FC4W1XU
as
> > > the Storage Manager. XBSA API version is 1.0.3.
> > > 2016-08-11 15:23:41 27121 18193 Successfully connected to Storage
> > Manager.
> > > 2016-08-11 15:23:41 27121 18193 Querying for backups expired at
Storage
> > > Manager...
> > > 2016-08-11 15:23:41 27121 18193 Building current timeline...
> > > 2016-08-11 15:23:41 27121 18193 Applying expiration policies...
> > > 2016-08-11 15:23:51 27121 18193 Regenerating sysutils and bootfile...
> > > 2016-08-11 15:23:51 27121 18193 (-43050) Copy of old emergency
bootfile
> > > saved in /usr/informix/etc/ ixbar.25.20160811.152351 .
> > > 2016-08-11 15:23:51 27121 18193 onsmsync complete, returning 0 (0x00)
> > >
> > > Wish more tips here , Want to be error-free .
> > >
> > > Thanks
> > > Frank
> > >
> > > On Thu, Aug 11, 2016 at 11:19 AM, FRANK <yunyaoqu@gmail.com> wrote:
> > >
> > > > Rafael,
> > > >
> > > > I set the parameter,
> > > >
> > > > BAR=3D5FBSALIB=3D5FPATH /usr/informix/lib/libtxbsa.so
> > > >
> > > > The lib file is,
> > > > [informix@walter onbar]$ ll /usr/informix/lib/libtxbsa.so
> > > > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015
> > > > /usr/informix/lib/libtxbsa.so
> > > >
> > > > But when I run onsmsync -i "1 00:00:00" to clean old file, Online
> > > > log shows,
> > > >
> > > > 2016-08-11 15:11:59 21982 18193 onsmsync -i 1 00:00:00
> > > > 2016-08-11 15:12:02 21982 18193 Syncing sysutils and bootfile...
> > > > 2016-08-11 15:12:02 21982 18193 (-43231) An unexpected error
occurred:
> > > > libApiTSM64.so: cannot open shared object file: No such file or
> > directory .
> > > > 2016-08-11 15:12:02 21982 18193 (-43259) Could not open XBSA
library
> > > > /usr/informix/lib/libtxbsa.so, so trying default path.
> > > > 2016-08-11 15:12:02 21982 18193 onsmsync complete, returning 133
(0x85)
> >
> > > >
> > > > Any idea?
> > > >
> > > > Thanks
> > > > Frank
> > > >
> > > > On Thu, Aug 11, 2016 at 6:50 AM, RAFAEL GOMEZ <rgomezs@gmail.com>
> > wrote:
> > > >
> > > > > Hi Frank.
> > > > >
> > > > > You have the library in your lib directory, it's:
> > > > >
> > > > > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so
> > > > >
> > > > > There are two options:
> > > > >
> > > > > - Create symbolic link:
> > > > >
> > > > > ln -s /usr/informix/lib/libtxbsa.so /usr/informix/lib/ibsad001.so
> > > > >
> > > > > - Change ONCONFIG parameter:
> > > > >
> > > > > BAR=3D5FBSALIB=3D5FPATH /usr/informix/lib/libtxbsa.so
> > > > >
> > > > > Best regards.
> > > > >
> > > > >
> > > > > ************************************************************
> > > > > *******************
> > > > > Forum Note: Use "Reply" to post a response in the discussion
forum.
> > > > >
> > > > >
> > > >
> > > > --94eb2c192314d0ff480539cd4bae
> > > >
> > > >
> > > > ************************************************************
> > > > *******************
> > > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >
> > > >
> > >
> > > --001a1144ba528826080539cd77de
> > >
> > >
> > >
> > ************************************************************
> > ***************=3D
> > ****
> >
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> >
> >
> > ************************************************************
> > *******************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --94eb2c1244b6c92a750539d161db
>
>
>
***************************************************************************=
****
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Hi Frank. You've tried setting your actual lib to BAR_BSALIB_PATH. Now, could yo try making the symbolic link? Best regards.
Thank you John ! Frank
On Thu, Aug 11, 2016 at 7:19 PM, John Miller iii <miller3@us.ibm.com> wrote:
> If you put a valid path name in the onconfig file for BAR=5FBASLIB=5FPATH
> t=
> hen
> this error should
> not be seen.
>
> onbar can run in parallel across your dbspaces. This is one of its large
> advantages.
> If you only have a single dbspace then onbar and ontape will run vary close
> to the
> same speed, because there would not be any parallelism seen.
>
> Also onpsm and onsmsync help you clean up old backup automatically. There
> are database scheduler tasks which have been setup to do all of this
> automatically
> which can be configure by hand or by use OAT.
>
> Hope this helps,
>
> John F. Miller III
> miller3@us.ibm.com
> 503-747-1366
>
> ids-bounces@iiug.org wrote on 08/11/2016 01:12:27 PM:
>
> > From: "FRANK" <yunyaoqu@gmail.com>
> > To: ids@iiug.org
> > Date: 08/11/2016 01:13 PM
> > Subject: Re: Onbar and PSM [37584]
> > Sent by: ids-bounces@iiug.org
> >
> > Thank you John!
> >
> > Two questions,
> >
> > 1) This is first time we try Onbar, PSM might be our only option .
> > Can we avoid these error lines in BAR log? ( I do not like any error
> > in the log)
> >
> > 2) We have been using ONTAPE from the beginning , as data and
> > transaction volume get bigger and busier , We experienced ONTAPE could
> > be significantly impacted by application's busy IO work. For example,
> > backup time could be varied in roller-coaster way from 2 hours to 5 hours
>
> > ( possibly more next when more volumes get in).
> >
> > Generally speaking, ONBAR should be much more faster than ONTAPE , is
> > that basically true ? ( like to hear more experiences of onbar...)
> >
> > On Thu, Aug 11, 2016 at 11:50 AM, John Miller iii <miller3@us.ibm.com>
> > wrote:
> >
> > > Yes, onbar and psm try to be very friendly.
> > > It tries the system library location first, then if it fails falls back
> to
> > > the location it knows PSM is installed at.
> > >
> > > Now if you wanted to use another product which is not PSM and an
> accident
> > > change to your config happened, then this fall back would be a problem.
>
> > >
> > > John F. Miller III
> > > miller3@us.ibm.com
> > > 503-747-1366
> > >
> > > ids-bounces@iiug.org wrote on 08/11/2016 08:32:11 AM:
> > >
> > > > From: "FRANK" <yunyaoqu@gmail.com>
> > > > To: ids@iiug.org
> > > > Date: 08/11/2016 08:33 AM
> > > > Subject: Re: Onbar and PSM [37578]
> > > > Sent by: ids-bounces@iiug.org
> > > >
> > > > Interesting thing is, if I reset BAR=3D5FBSALIB=3D5FPATH to
> undefined,
> The
> > > > command can be run successfully ( even though there are different
> errors
> > > > in BAR log, see below).
> > > >
> > > > 2016-08-11 15:23:39 27121 18193 onsmsync -i 1 00:00:00
> > > > 2016-08-11 15:23:41 27121 18193 Syncing sysutils and bootfile...
> > > > 2016-08-11 15:23:41 27121 18193 (-43231) An unexpected error
> occurred:
> > > > /usr/informix/lib/ibsad001. so: cannot open shared object file:
> > > > No such file or directory .
> > > > 2016-08-11 15:23:41 27121 18193 (-43259) Could not open XBSA library
> > > > /usr/informix/lib/ibsad001.so, so trying default path.
> > > > 2016-08-11 15:23:41 27121 18193 Using IBM's PSM version 12.10.FC4W1XU
> as
> > > > the Storage Manager. XBSA API version is 1.0.3.
> > > > 2016-08-11 15:23:41 27121 18193 Successfully connected to Storage
> > > Manager.
> > > > 2016-08-11 15:23:41 27121 18193 Querying for backups expired at
> Storage
> > > > Manager...
> > > > 2016-08-11 15:23:41 27121 18193 Building current timeline...
> > > > 2016-08-11 15:23:41 27121 18193 Applying expiration policies...
> > > > 2016-08-11 15:23:51 27121 18193 Regenerating sysutils and bootfile...
>
> > > > 2016-08-11 15:23:51 27121 18193 (-43050) Copy of old emergency
> bootfile
> > > > saved in /usr/informix/etc/ ixbar.25.20160811.152351 .
> > > > 2016-08-11 15:23:51 27121 18193 onsmsync complete, returning 0 (0x00)
>
> > > >
> > > > Wish more tips here , Want to be error-free .
> > > >
> > > > Thanks
> > > > Frank
> > > >
> > > > On Thu, Aug 11, 2016 at 11:19 AM, FRANK <yunyaoqu@gmail.com> wrote:
> > > >
> > > > > Rafael,
> > > > >
> > > > > I set the parameter,
> > > > >
> > > > > BAR=3D5FBSALIB=3D5FPATH /usr/informix/lib/libtxbsa.so
> > > > >
> > > > > The lib file is,
> > > > > [informix@walter onbar]$ ll /usr/informix/lib/libtxbsa.so
> > > > > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015
> > > > > /usr/informix/lib/libtxbsa.so
> > > > >
> > > > > But when I run onsmsync -i "1 00:00:00" to clean old file, Online
> > > > > log shows,
> > > > >
> > > > > 2016-08-11 15:11:59 21982 18193 onsmsync -i 1 00:00:00
> > > > > 2016-08-11 15:12:02 21982 18193 Syncing sysutils and bootfile...
> > > > > 2016-08-11 15:12:02 21982 18193 (-43231) An unexpected error
> occurred:
> > > > > libApiTSM64.so: cannot open shared object file: No such file or
> > > directory .
> > > > > 2016-08-11 15:12:02 21982 18193 (-43259) Could not open XBSA
> library
> > > > > /usr/informix/lib/libtxbsa.so, so trying default path.
> > > > > 2016-08-11 15:12:02 21982 18193 onsmsync complete, returning 133
> (0x85)
> > >
> > > > >
> > > > > Any idea?
> > > > >
> > > > > Thanks
> > > > > Frank
> > > > >
> > > > > On Thu, Aug 11, 2016 at 6:50 AM, RAFAEL GOMEZ <rgomezs@gmail.com>
> > > wrote:
> > > > >
> > > > > > Hi Frank.
> > > > > >
> > > > > > You have the library in your lib directory, it's:
> > > > > >
> > > > > > -r-xr-xr-x 1 informix informix 58585 Feb 19 2015 libtxbsa.so
> > > > > >
> > > > > > There are two options:
> > > > > >
> > > > > > - Create symbolic link:
> > > > > >
> > > > > > ln -s /usr/informix/lib/libtxbsa.so /usr/informix/lib/ibsad001.so
>
> > > > > >
> > > > > > - Change ONCONFIG parameter:
> > > > > >
> > > > > > BAR=3D5FBSALIB=3D5FPATH /usr/informix/lib/libtxbsa.so
> > > > > >
> > > > > > Best regards.
> > > > > >
> > > > > >
> > > > > > ************************************************************
> > > > > > *******************
> > > > > > Forum Note: Use "Reply" to post a response in the discussion
> forum.
> > > > > >
> > > > > >
> > > > >
> > > > > --94eb2c192314d0ff480539cd4bae
> > > > >
> > > > >
> > > > > ************************************************************
> > > > > *******************
> > > > > Forum Note: Use "Reply" to post a response in the discussion forum.
>
> > > > >
> > > > >
> > > >
> > > > --001a1144ba528826080539cd77de
> > > >
> > > >
> > > >
> > > ************************************************************
> > > ***************=3D
> > > ****
> > >
> > > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >
> > >
> > >
> > > ************************************************************
> > > *******************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
Rafael, I reconfigured BAR_BSALIB_PATH it to point to , BAR_BSALIB_PATH /usr/informix/lib/libbsapsm.so Which seems working well with no errors . Thanks Frank On Fri, Aug 12, 2016 at 1:31 AM, RAFAEL GOMEZ <rgomezs@gmail.com> wrote: > Hi Frank. > > You've tried setting your actual lib to BAR_BSALIB_PATH. Now, could yo try > making the symbolic link? > > Best regards. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a11c0097e46ae09053a21bf2d