command the shutdown Oracle 10g R2 from Toad

Dear all,

I read this:
http://www.oracle-base.com/articles/10g/auditing-10gr2.php

to enable the server audit feature,  we need to do this:

"ALTER SYSTEM SET audit_trail=db SCOPE=SPFILE;"

then we need to restart the Oracle in this way:
1)SHUTDOWN
2)STARTUP


But as Oracle as stopped once we issue shutdown from Toad, is it possible to issue startup again from Toad to start the Oracle server ?

or we type both and hightlight them in Toad and then press F5 so that they run as a batch ?
LVL 1
marrowyungSenior Technical architecture (Data)Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Geert GOracle dbaCommented:
if you can run shutdown from toad, run "startup force" instead

personally i think restarting a database from toad is a BAD IDEA.

i always login on the server so i'm sure i'm on the right database
and then still check v$instance to verify i'm restarting a production database
a tnsnames alias can point to any database and be changed by a dba ...

you wouldn't want anybody restarting your db whenever they feel like it
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
marrowyungSenior Technical architecture (Data)Author Commented:
"if you can run shutdown from toad, run "startup force" instead

personally i think restarting a database from toad is a BAD IDEA."

so must be from Console you means?

you tried the startup force before and it works ?

"you wouldn't want anybody restarting your db whenever they feel like it "

yes, only DBA can !!

"
i always login on the server so i'm sure i'm on the right database"

Toad can't help you to make sure that ?

"then still check v$instance to verify i'm restarting a production database"

what is the scirpt for this and I am wondering why we should do thsi as from Toad, it will show you where you are, right ?
0
Geert GOracle dbaCommented:
if you use the tnsnames then you are using an alias
here we have a system where 3 people can modify the tnsnames.ora on a global scale

after testing : toad can't execute startup

why use it anyway ?
dba's usually avoid toad, it's a help but does things in background some dba's are suspicious off, like starting a second connection to check access
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

DavidSenior Oracle Database AdministratorCommented:
An obvious problem with scripting it, is the need to ensure there's a clean (recoverable) shutdown BEFORE you restart it.  E-E has many examples on how to do so.

If you're running on an Enterprise edition of the database, please try to use OEM / Grid Control instead of a third-party product.
0
marrowyungSenior Technical architecture (Data)Author Commented:
"if you use the tnsnames then you are using an alias
here we have a system where 3 people can modify the tnsnames.ora on a global scale"

yes, we are using tnsnames.

"here we have a system where 3 people can modify the tnsnames.ora on a global scale"

you mean there are more than 3 x DBA in your firm ?

"
after testing : toad can't execute startup "

excellent, thanks for this, that's why I am thinking about how to connect to it ONCE it was shutdown and issue command startup .

OEM can do this however?

"dba's usually avoid toad, it's a help but does things in background some dba's are suspicious off, like starting a second connection to check access "

ok, got it, but it provide a lot of help.

dvz,

"An obvious problem with scripting it, is the need to ensure there's a clean (recoverable) shutdown BEFORE you restart it.  "

what is no clean ? once shutdown, everything should be clean?

from your point of view, OEM is better than Toad ?
0
Geert GOracle dbaCommented:
OEM / Grid Control is way expensive ... and not necessary

sqlplus is adequate and can come installed with oracle client

if the database is stopped or halted, by for example firing an AK47 at the server, it's  possible it's corrupted

or it may have a tablespace in backup mode during shutdown abort
> this requires recovery of the database before opening.

the biggest question
> why do you need to stop/start the database

i only do this because of the windows patching and for changing parameters
or when it's gone wild ... which has only happened once or twice with orphaned threads.
0
DavidSenior Oracle Database AdministratorCommented:
Geert (39542545), the value of any tool is proportional to it being the right tool for the job.  IMO OEM/Grid is indeed "necessary" in the right circumstances -- please keep an open mind about Grid when you're migrating to 12c.

marrowyung (39542041), regarding OEM vs TOAD, my point to Geert applies.  Most of the time, when I'm working on a single node (instance), the command line interface (CLI) from SQL*Plus is all I need.  For some, typing out command syntax is burdensome.  My personal preference is Oracle's SQL*Developer (free) before TOAD -- depending upon which I think is the better tool.  When I come in each day, however, I begin with my Grid console to monitor job results and the enterprise health at a glance.

In regard to recoverability, it's said if something can go wrong, it will.  Say you're using archivelogmode, so that there's a record of all committed transactions in log files.  You restore from your last good backup -- intending to use the log files to apply all transactions since that backup.  If your system burped and corrupted a log's integrity, you may lose all subsequent transactions.  Moral: keep redundant log copies on multiple systems.  When we back up, RMAN writes to a disk, after which the disk image is copied to offline storage (tape).  Moral:  redundant points of recovery, minimal single points of failure.

Does that help explain my points?
dvz
0
marrowyungSenior Technical architecture (Data)Author Commented:
"If your system burped and corrupted a log's integrity, you may lose all subsequent transactions.  Moral: keep redundant log copies on multiple systems.  When we back up, RMAN writes to a disk, after which the disk image is copied to offline storage (tape).  Moral:  redundant points of recovery, minimal single points of failure."

This is good. some compliance will require that.

From Toad I see this, might be it is enought instead of command prompt:

restart Oracle
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.