RE: after upgrading to 12.1 log back script not wo
Posted in 2015
Well, maybe more of the psm is setup than I first thought, I found the onpsm
command and did a list of the devices, objects and pools. Since I'm getting
objects I assume the logs are being backed up, but because of something when I
do a onstat -l the logs do not show they are backed up. Which I assume is
because of the error -88303. If I run a ontape -a this does show the logs
being backed up when I do a onstat -l.
informix cars: onpsm -O list
Informix Primary Storage Manager Object List
Object ID Date Created Size (MB) Logical path (name.version)
1 2015-11-27 08:41:57 8.0 /zoom/0/325029/zoom.1
2 2015-11-27 09:38:44 8.0 /zoom/0/325030/zoom.1
3 2015-11-27 12:41:58 8.0 /zoom/0/325031/zoom.1
. . . lots more . . .
206 2015-11-28 03:21:48 8.0 /zoom/0/325234/zoom.1
207 2015-11-28 03:21:51 8.0 /zoom/0/325235/zoom.1
208 2015-11-28 03:21:54 8.0 /zoom/0/325236/zoom.1
209 2015-11-28 03:21:56 8.0 /zoom/0/325237/zoom.1
informix cars: onpsm -D list
Informix Primary Storage Manager Device List
Type Prio Block/Size (MB) Pool Name Device Name
FILE LOW --/-- DBSPOOL /opt/informix/backups
FILE READ-ONLY --/-- LOGPOOL /opt/informix/backups
informix cars: onpsm -P list
Informix Primary Storage Manager Pool List
Pool Id Name
1 DBSPOOL
2 LOGPOOL
3 EXTPOOL
Since IDS 7.34 we have used the below simple script to back up logs
automatically and that is all we used onbar for. We handle the database backup
using ontape to tape separately.
---BEGIN SCRIPT ---
PROG=`basename $0`
USER_LIST=informix
BACKUP_CMD="onbar -b -l"
EXIT_STATUS=0
EVENT_SEVERITY=$1
EVENT_CLASS=$2
EVENT_MSG="$3"
EVENT_ADD_TEXT="$4"
EVENT_FILE="$5"
case "$EVENT_CLASS" in
23)
# onbar assumes no operator is present,
# so all messages are written to the activity
# log and there shouldn't be any output, but
# send everything to /dev/null just in case
$BACKUP_CMD 2>&1 >> /dev/null
EXIT_STATUS=$?
;;
# One program is shared by all event alarms. If this ever gets expanded to
# handle more than just archive events, uncomment the following:
*)
# EXIT_STATUS=1
;;
esac
exit $EXIT_STATUS
---END SCRIPT ---
The current log would be put into informix/tlog and after backing up moved to
informix/tlog/hold then a nightly script would purge old logs after I think a
week. Not the fanciest or greatest but worked for us.
Now with PSM it seems we need to do something different. Can I get a crash
course in what I need to do with psm to get an alarmprogram script to backup
logs when full? And secondly does psm cleanup old logs (Objects) or do I have
to purge them? (/opt/informix/backups/...)
John
-----Original Message-----
From: John Adamski (Work Account)
Sent: Saturday, November 28, 2015 7:37 PM
To: 'ids@iiug.org'
Subject: after upgrading to 12.1 log back script not working
HPUX 11.31 (11iv3)
HP BL870c Integrity server
IDS 12.10.FC5
Friday I upgraded our ERP with the latest-ish opensource products and
Informixto IDS 12.10.FC5 and missed the note about ISM_DATA_POOL and
ISM_LOG_POOL being removed. Silly me listened to our ERP that there is nothing
extra to the Informix upgrade.
It seems the new config items are PSM_DBS_POOL and PSM_LOG_POOL, which got set
to the defaults of DBSPOOL and LOGPOOL are in the onconf file.
However when our log full scripts runs and tried to do the backup (onbar -b
-l) it gets this error
2015-11-28 18:36:56 22642 22640 Using IBM's PSM version 12.10.FC5 as the
Storage Manager. XBSA API version is 1.0.3.
2015-11-28 18:36:56 22642 22640 Begin backup logical log 325288.
2015-11-28 18:36:56 22642 22640 The PSM is ready.
2015-11-28 18:36:56 22642 22640 Informix Primary Storage Manager session 251
opened.
2015-11-28 18:36:56 22642 22640 Successfully connected to Storage Manager.
2015-11-28 18:36:56 22642 22640 Error -88035: No Device is available to mount
in pool 'LOGPOOL'.
2015-11-28 18:36:56 22642 22640 XBSA Error: (BSACreateObject) Exceeded
available resources.
2015-11-28 18:36:56 22642 22640 Informix Primary Storage Manager session 251
closed
2015-11-28 18:36:58 22619 22617 /opt/informix/bin/onbar_d complete, returning
19 (0x13)
Which seems to me I missed a step as the LOGPOOL can't be found. Anyone have
an idea of what I need to do?
A simple ontape -a does work and backup the logs but want to get the
automagical script working again.
John David Adamski, Sr. Network Specialist Graceland University, 1 University
Place, Lamoni, IA 50140 adamski@graceland.edu
641.784.5267