Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Which first? Listener stop or DB Shutdown?

Status
Not open for further replies.

MCubitt

Programmer
Mar 14, 2002
1,081
GB
Can someone please advise which I should do first?

Do I stop the listener (to stop folk accessing the running DB) and THEN shut down the DB...

or do I shutdown the DB first?

I am presuming this is correct:
LSNRCTL STOP
SHUTDOWN DBs

Do maintenance

STARTUP DBs
LSNRCTL START

Thank you




There's no need for sarcastic replies, we've not all been this sad for that long!
 
You should stop DB first. Issuing shuttdown command prevents new connections of ordinary users. BTW single listener may serve a number of instances.

Regards, Dima
 
Thanks Sem.

I will shutdown all DBs (dbshut script) and then stop the listener.

regards

There's no need for sarcastic replies, we've not all been this sad for that long!
 
Martin,

I think you missed Sem's point: You don't need to shutdown the listener just because you shutdown a database. Shutting down the listener can negatively impact otherwise "disinterested" databases. So, unless you must shutdown the listener for some reason.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA @ 16:28 (21Sep04) UTC (aka "GMT" and "Zulu"), 09:28 (21Sep04) Mountain Time)
 
Santa,

I need to "kill" Oracle for both a flat file backup and patch upgrade.

Will shutting down all DBs be enough, of course I plan to check any left over processes anyway but just wish to make sure.

My understanding (was) that the listener was used to "listen" for new connection attempts to the DB(s) and therefore stopping it allows DBs to shutdown without anyone attempting access. Of course this could be legacy methodology or just utterly wrong!

Thanks

There's no need for sarcastic replies, we've not all been this sad for that long!
 
Martin,

There is no penalty against Oracle for unsuccessful connection attempts via the listener. If the database is down but the listener is up, the only effect resulting from an unsuccessful connection attempt is a negative TNS-failure message to the attempted connector.

Similarly, you can do completely successful cold backups against a downed database with the listener up. The issue of upgrading Oracle software is, however, a different story. Oracle database-version upgrades usually involve LISTENER upgrades, which require the listener to be down.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA @ 16:46 (21Sep04) UTC (aka "GMT" and "Zulu"), 09:46 (21Sep04) Mountain Time)
 
Santa,

Ahhh... that must be it then. I guess a belt & braces approach is to end the listener regardless, in this case.

Thanks for your explanations.

There's no need for sarcastic replies, we've not all been this sad for that long!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top