onbar -b -F waiting fot one writable backup tape
Hi, all
I'm new to Informix.
I am trying to install a product combining with IDS 7.31.UC3
into my Ultra5 (SunOS 5.5.1). During the installation, several
dbspaces will be created, and after that, "onbar -b -F" be run.
But the installation procedure is hang on "onbar -b -F".
The following is the ptree of the installation processes,
3613 admintool
3812 sh -c /usr/openwin/bin/cmdtool -display
acrux:0.0 -title "Admintool: Add Softwa
3813 /usr/openwin/bin/cmdtool -display acrux:0.0 -title
Admintool: Add Software -ico
3815 /bin/sh /var/tmp/adpkgFAAa000sT
3898 /usr/sbin/pkgadd -a /etc/EAAa000sT -d
/products/resolve/illusion/current/cdrom
3899 /usr/sadm/install/bin/pkginstall -a
/etc/EAAa000sT -N pkgadd /products/resolve/
4070 /sbin/sh
/var/sadm/pkg/CKTATMCfg/install/postinstall
4125 /bin/sh
/opt/resolve/thirdparty/informix/bin/onbar -b -F
4127
/opt/resolve/thirdparty/informix/bin/ism_catalog -create_bootstrap -pool
ISMDat
4128 savegrp -O ISMData
4133
/opt/resolve/thirdparty/informix/bin/nsrexec -T 1800 -- acrux:index
and messages in ${INFORMIXDIR}/ism/logs/daemon.log :
12/06/99 14:50:53 nsrd: media waiting event: backup to pool 'ISMData'
waiting for 1 writable backup tape(s)
...
12/07/99 10:11:59 nsrd: media waiting event: backup to pool 'ISMData'
waiting for 1 writable backup tape(s)
But the "onbar" manual says I can execute the "-F" option
wether or not a storage manager is running. The following
is the script of ${INFORMIXDIR}/bin/onbar. You know
the purpose of "onbar -b -F" here. Is it the same here
if I launch "onbar_d -b -F" instead of "onbar -b -F" here ?
or is there any side effect ?
Any advice will be greatly appreciated.
Harry.
---------------------------------------------
#!/bin/sh
###########################################################################
#
# INFORMIX SOFTWARE, INC.
#
# Title: onbar
# Description: Wrapper script for Informix Backup and Restore (ON-Bar).
# Users may edit this script to customize backup and
# restore operations, including specific Storage Manager
# setup and cleanup procedures.
#
###########################################################################
onbar_d_return=0
#############################
# add startup processing here
#############################
#############################
# end startup processing here
#############################
# Run the onbar driver
onbar_d_pid=
# HUP=01, TERM=15, INT=02, QUIT=03
# relay the HUP and TERM signals to the onbar_d as a SIGTERM
trap '
[ -z "$onbar_d_pid" ] && exit 1
kill -TERM $onbar_d_pid 2> /dev/null
wait $onbar_d_pid
exit $?
' 01 15
# relay the INT and QUIT signal to the onbar_d as a SIGQUIT
trap '
[ -z "$onbar_d_pid" ] && exit 1
kill -QUIT $onbar_d_pid 2> /dev/null
wait $onbar_d_pid
exit $?
' 02 03
${INFORMIXDIR}/bin/onbar_d "$@" &
onbar_d_pid=$!
wait $onbar_d_pid
onbar_d_return=$?
trap 01 02 15 03
#############################
# add cleanup processing here
#############################
# Default cleanup processing for the ISM:
# If we've just done a backup with the ISM, back up the ISM catalogs.
# It's safe to check $1 because onbar commands must start with -[blr].
# We ignore ism_catalog errors because we're not sure that the ISM
# is being used at this site or on a particular coserver.
# NOTE: If you do not have a pool named 'ISMData', be sure to change
# the pool name in the ism_catalog command below.
if [ $onbar_d_return -eq 0 -a \\( "$1" = -b -o "$1" = -l \\) -a -x
${INFORMIXDIR}/bin/ism_catalog ] ; then
${INFORMIXDIR}/bin/ism_catalog -create_bootstrap -pool ISMData >
/dev/null 2>&1
fi
#############################
# end cleanup processing here
#############################
exit $onbar_d_return # return the error from onbar_d