Monitoring script

Question

I created a monitoring script which would run from crontab....Would anyone tell me how I would export Oracle SID in crontab script instead of hard coded it. Thanks.

Answer 1

I do some simple checks for correct number of arguments using "if [[ $# -lt 1 ]]; then..."
This is very simple and doesn't confirm that the arguments are valid.
Example:
if [[ $# -lt 1 ]]; then
  print "\n ERROR:  You did not specify an Oracle SID."
  print "\n Please enter which Oracle SID to import into. \n"
  exit 1
else
  echo "\n  ORACLE_SID = $1 \n"
  echo "Do you wish to continue? \n "
    read REPLY
     case $REPLY in
        y|Y) echo "\n test good \n";;
        n|N) echo "\n exiting... \n"; return 1;;
        echo "Invalid response (Bozo).  Exiting..."
        echo ""
        return 2;
     esac
fiBut my point was to show a quick and easy solution to the OP for his purposes.
Using "echo $1 |. oraenv" passes the variable to oraenv and sets everything he needs for his purposes.
From the sounds of the OP's question, it didn't seem to have the skills to develop more complex scripts.
Personally, I like to use a special file that I keep updated on all servers.
I call the file 'localsids' and place it in the /var/opt/oracle directory.
I have a similar file called 'allsids', which contains a list of all sids on all servers for when I want to check all databases (e.g., such as for users having DBA role, or something like that).
Then, I check for validity (and can add and remove SIDs from the file at will, (depending on purposes such as blackouts).
I like using a loop for this purpose (SIDFILE='var/opt/oracle/localsids' cat $SIDFILE |while read SID... do....)
Example:
# ==================================================
# check input given against valid sids on this machine
# ==================================================
export SIDFILE='/var/opt/oracle/localsids'
SID=`grep $1 $SIDFILE`
if [ "$SID" = "$1" ]; then
print "\n \"$SID\" verified... \n"
else
print "\n ERROR... \"$1\" is not a valid SID for this machine. \n"
exit 1
fiI have a couple other variations as well.
I think it would be nice if OTN had a more appropriate forum for people like us who like scripting and/or what to share unix skills.