"whenever sqlerror exit 1" does not work on Linux Post: 84148

Sponsored Content

Top Forums Shell Programming and Scripting "whenever sqlerror exit 1" does not work on Linux Post 84148 by nir_s on Thursday 22nd of September 2005 03:54:03 AM

09-22-2005

Registered User

"whenever sqlerror exit 1" does not work on Linux

Hi folks,

I have the following functions in my Installation script:

Code:

create_roles()
{
export rollback=yes
echo "\nCreating roles ..." >> $installLog

    errMsg="ERROR: Failed to create roles!\nCheck the details in ${logDir}/create_roles.log"
    validMsg="-> VALID: roles were created."

${PLUS} -s sys/${SYS_PASS}@${CONNECT_STRING} as sysdba << EOF 
spool ${logDir}/create_roles.log
@${InstallObjDir}/CORE.roles ${SCHEMA_NAME}
spool off
EOF
confirm_return
}
#------------------------------------------------------------------------
confirm_return()
{
if [[ $? -ne 0 ]] ; then
  $stars | tee -a $installLog
  echo $errMsg | tee -a $installLog
  echo "EXITING: Please fix and rerun ${InstallDir}/Install_RiGHTv.ksh\n" | tee -a $installLog
  clean_up
  exit 1
else
  echo $validMsg >> $installLog
fi
}
#------------------------------------------------------------------------
clean_up()
{
${cdromPath}/cleanup.ksh
}
#-----------------------------------------------------------------------

If sqlerror is detected ,the script cleanup.ksh will be run (rollback process).

When I ran the Installation,I forgot to clean some roles from the database ,and I've got the following error:

Code:

Creating role PLATOR81_BO_ROLE ...
old   1: create role &SCHEMA_NAME._BO_ROLE
new   1: create role PLATOR81_BO_ROLE
create role PLATOR81_BO_ROLE
            *
ERROR at line 1:
ORA-01921: role name 'PLATOR81_BO_ROLE' conflicts with another user or role name

The installation was suppose to get status 1 and run cleanup.ksh script.
The current situation is that the installation was stuck and doing nothing!
This problem occurs only on Linux platform. On Solaris and HP-UX I haven't encountered with this problem.
Our Linux version is Red Hat 2.1

Any advises will be gratefully accepted.

Thanks in advance,
Nir

nir_s

View Public Profile for nir_s

Find all posts by nir_s

LEARN ABOUT MINIX

ppmtosixel

ppmtosixel(1)                                                 General Commands Manual                                                ppmtosixel(1)

NAME

       ppmtosixel - convert a portable pixmap into DEC sixel format

SYNOPSIS

       ppmtosixel [-raw] [-margin] [ppmfile]

DESCRIPTION

       Reads  a  portable  pixmap  as input.  Produces sixel commands (SIX) as output.  The output is formatted for color printing, e.g. for a DEC
       LJ250 color inkjet printer.

       If RGB values from the PPM file do not have maxval=100, the RGB values are rescaled.  A printer control header and a color assignment table
       begin the SIX file.  Image data is written in a compressed format by default.  A printer control footer ends the image file.

OPTIONS

       -raw   If  specified,  each  pixel  will  be explicitly described in the image file.  If -raw is not specified, output will default to com-
              pressed format in which identical adjacent pixels are replaced by "repeat pixel" commands.  A raw file is often an order  of  magni-
              tude larger than a compressed file and prints much slower.

       -margin
              If  -margin  is not specified, the image will be start at the left margin (of the window, paper, or whatever).  If -margin is speci-
              fied, a 1.5 inch left margin will offset the image.

PRINTING

       Generally, sixel files must reach the printer unfiltered.  Use the lpr -x option or cat filename > /dev/tty0?.

BUGS

       Upon rescaling, truncation of the least significant bits of RGB values may result in poor color conversion.  If the original PPM maxval was
       greater  than  100,  rescaling  also reduces the image depth.  While the actual RGB values from the ppm file are more or less retained, the
       color palette of the LJ250 may not match the colors on your screen.  This seems to be a printer limitation.

SEE ALSO

       ppm(5)

AUTHOR

       Copyright (C) 1991 by Rick Vinci.

                                                                   26 April 1991                                                     ppmtosixel(1)