I had a similar problem once, turned out it was caused by the DBA's not
utilizing the autostart feature in the oratab file. If you have the
autostart column set to 'n' in oratab, roracle will ignore the entry.
Probably the easiest way to fix this is to copy the oratab file to another
directory (BBHOME/etc makes sense), modify the roracle script to find the
new file, and then edit the new oratab file so that there are 'y's next to
all the active databases.
Thanks,
Larry Barber
On 6/20/06, user-bb3e9041f07f@xymon.invalid <user-bb3e9041f07f@xymon.invalid> wrote:
Hello,
I'm asking your help on the setting up of the Roracle script from deadcat.
I've been looking at the documentation, setting up my variables but I only
get one column : orasys. I got this message too, under Oracle Instance
Check :
"Instances specified in LOCAL_SIDS (HALI01) do not match those found in
/etc/oratab (HALI01 HALS00 ....)"
Normally, I should get another column called oratab with databases
properties. If someone got this script running and could give me some help
to configure it properly, I would be happy !
Thanks !
Thomas
Ce message (et toutes ses pieces jointes eventuelles) est confidentiel et
etabli a l'intention exclusive de ses destinataires.
Toute utilisation de ce message non conforme a sa destination, toute
diffusion ou toute publication, totale ou partielle, est
interdite, sauf autorisation expresse.
L'internet ne permettant pas d'assurer l'integrite de ce message, CNP
Assurances et ses filiales declinent toute responsabilite
au titre de ce message, s'il a ete altere, deforme ou falsifie.
*****
This message and any attachments (the "message") are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
E-mails are susceptible to alteration.
Neither CNP Assurances nor any of its subsidiaries or affiliates shall be
liable for the message if altered, changed or falsified.