SEO

Hello,

I would like to get a consensus of what is currently being used to
start Oracle 10g databases upon a Sun UNIX system boot.

Like many, in the past I used the legacy /etc/init.d/dbora (which
calls dbstart\dbshut) and requires entries in the /var/opt/oracle
file.

At present with approx. 25 databases I use what is found in the
scripts section here: www.michael-elliott.com (dbctl.sh)

What do you use and why do you prefer it?


Thanks for your feedback,

Michael

On Jun 11, 5:19 pm, Michael42 <melliot...@yahoo.com> wrote:
> Hello,
>
> I would like to get a consensus of what is currently being used to
> start Oracle 10g databases upon a Sun UNIX system boot.
>
> Like many, in the past I used the legacy /etc/init.d/dbora (which
> calls dbstart\dbshut) and requires entries in the /var/opt/oracle
> file.
>
> At present with approx. 25 databases I use what is found in the
> scripts section here:www.michael-elliott.com (dbctl.sh)
>
> What do you use and why do you prefer it?
>
> Thanks for your feedback,
>
> Michael

We like to use our own scripts that start/stop Oracle via SQLPlus
because we pin certain packages in the shared pool on instance startup
as well as run a verification routine that reports the status of
specific items. What we do varies by database so using our own script
gives us better control.

You can run your own script via rcd for auto-start/shutdown or
manually as needed. If you have no special needs then the oratab file
along with rcd is all you need.

HTH -- Mark D Powell --

On Jun 11, 2:19 pm, Michael42 <melliot...@yahoo.com> wrote:
> Hello,
>
> I would like to get a consensus of what is currently being used to
> start Oracle 10g databases upon a Sun UNIX system boot.
>
> Like many, in the past I used the legacy /etc/init.d/dbora (which
> calls dbstart\dbshut) and requires entries in the /var/opt/oracle
> file.
>
> At present with approx. 25 databases I use what is found in the
> scripts section here:www.michael-elliott.com (dbctl.sh)
>
> What do you use and why do you prefer it?
>
> Thanks for your feedback,
>
> Michael

Most every place I've been at for any length of time has had some
dummy electrician or electric company repeatedly bounce servers
without realizing it, in spite of UPS and operations procedures and
blast-proof steel doors. Fortunately, the last one (last week) was
death to the SQL-Servers, not the Oracle stuff. This often results in
management decrees of no autostart scripts for databases.

Haven't been on Sun in a while, though the worst bouncy-bouncy
corruption I ever saw was on one in the 8.0 era. The stock dbora
seems ok for a basic hp-ux system. Still can hang on dbshut without a
reboot (some do periodic cold backup for certain DR).

jg
--
@home.com is bogus.
http://www.youtube.com/watch?v=yctEEDWXXmU

Michael42 <melliott42@yahoo.com> wrote in news:1181596771.710045.258720
@q75g2000hsh.googlegroups.com:

> Hello,
>
> I would like to get a consensus of what is currently being used to
> start Oracle 10g databases upon a Sun UNIX system boot.
>
> Like many, in the past I used the legacy /etc/init.d/dbora (which
> calls dbstart\dbshut) and requires entries in the /var/opt/oracle
> file.
>
> At present with approx. 25 databases I use what is found in the
> scripts section here: www.michael-elliott.com (dbctl.sh)
>
> What do you use and why do you prefer it?
>
>
> Thanks for your feedback,
>
> Michael
>

I worked on the database startup scripts for our HP-UX servers. Some
dev servers had over 50 instances most of them started but idled all
day. The total number of instances was over 300. We had 5 operations
DBAS. Everything was automated so we used our own scripts calling
SQL*Plus. They used dbstart as a starting point. The startup script
read the oratab file to get the list of databases.

The scripts could be hardened against every new problem that came up.
When 60 databases took too long to start and stop, we ran them in
parallel, three at a time. When a startup failed, an email was sent to
the DBAS and a priority problem was sent to the problem tracking system
and a DBA was paged.

The scripts evolved over several versions of Oracle and HP-UX, but the
prime directives remained. The scripts only changed because of an
operational problem or a problem with a new version of software. DBAS
did not modify scripts to add a new database.

HTH

Andy

On Jun 11, 5:19 pm, Michael42 <melliot...@yahoo.com> wrote:
> Hello,
>
> I would like to get a consensus of what is currently being used to
> start Oracle 10g databases upon a Sun UNIX system boot.
>
> Like many, in the past I used the legacy /etc/init.d/dbora (which
> calls dbstart\dbshut) and requires entries in the /var/opt/oracle
> file.
>
> At present with approx. 25 databases I use what is found in the
> scripts section here:www.michael-elliott.com (dbctl.sh)
>
> What do you use and why do you prefer it?
>
> Thanks for your feedback,
>
> Michael

While prevailing opinions do blow back and forth like the pirates and
Captain Jack many of us who have been around a while don't especially
like automated start operations whether it's under unix or windows or
whatever.

There are 2 primary complications. First, if you are having power
supply problems of any kind ( on UPS bypass with the clock ticking, on
generator but gas running empty, substation instability etc ) you
don't really want to get partway thru attempted restarts ... get the
system bounced again ... start again etc.

Second maybe there are some problems with storage devices whether they
are directed attached, NAS, SAN etc and the stability of storage needs
to be checked out and diagnosed before attempts are made to use
potentially corrupt or unavailable storage.

I think Nuno Suoto ( sp? apologies ) had a fairly recent posting in
this area that you may want to look up.

Personally I want to know if and when a database server was re-booted
and want to get involved in any assessment of whether we are ready to
restart the oracle that any specific server was responsible for.

At the minimum maybe you want to script out some kind of "checking"
routine that looks and verifies that all necessary storage appears to
be available and ready before invoking any kind of mass restart.

On Mon, 11 Jun 2007 16:44:38 -0700, Mark D Powell wrote:

> We like to use our own scripts that start/stop Oracle via SQLPlus
> because we pin certain packages in the shared pool on instance startup
> as well as run a verification routine that reports the status of
> specific items. What we do varies by database so using our own script
> gives us better control.

I don't want to nag, but a startup trigger is an ideal thing for
DBMS_SHARED_POOL.KEEP. No need for a special script.


--
http://www.mladen-gogala.com

Guys,

Thanks for the feed back on your experiences with startup scripts. It
is always good to see how others approach simliar technical
challenges. Sure beats operating in an intellectual black hole.

Michael