Stopping services for backup

[efrijters]

Hello.

Probably this question has been answered before, but I searched the forum and I can't find the topic anymore.

Here's the question:

A customer has bought a tape unit and uses a special program to backup the network. The database must be stopped or else the backup will fail. So the database is backupped cold.

The tape software starts a script that stops the database and NT services, backups the volume and starts a script that restarts everything.

My questions are:
1. Is there a example of which NT Services I must stop?
2. Is it enough to only stop the database-services and not the - for example - Agent- and Management Server-service?

Help would be appreciated.

Erik

[SANJAY_G]

Only database service i.e. OracleServicesid need to be stopped.

[efrijters]

Okay, Thanks!!

[jmodic]

No need to stop any service, just stop the database.

[SANJAY_G]

Originally posted by jmodic
No need to stop any service, just stop the database.

yes jmodic, not necessary but Oracle do recommend to stop this service.

http://metalink.oracle.com/metalink/...p_id=91251.996
http://metalink.oracle.com/metalink/...p_id=96745.999

[efrijters]

Now I'm confused...
The last links brings you to a page with an actual example of a command file. But this also stops all the services...

A piece of the script:
Net Stop OracleAgent
svrmgr23 command=@c:\shutdbs.sql
net stop OracleStartXXXX
net stop OracleServiceXXXX
net stop OracleTNSListener
type i:\orant\network\log\listener.log >> listener.bak
del I:\orant\network\log\listener.log

shutdbs.sql:
spool c:\shutdbs.log
set echo on
connect internal/password@xxxx
shutdown immediate;
startup pfile=e:\oracle\pfile\initxxxx.ora restrict
shutdown normal;
disconnect


They 'shutdown immediate' first and restart the db in restrict-mode so they can stop it with 'normal'. Isn't this strange, because the db was already consistently stopped with 'immediate'??

And they restart the TNSListener after the db's. So in my humble opinion, the db's cannot dynamically register with the listener (if wanted).

The response from Oracle support states that this is an excellent way to stop the db.

So, who is right here?

(The article at metalink is posted in the year 2000. Is this information outdated perhaps?)

Thanks sofar!

[DaPi]

I set up my NT script under 7.3.4, so what I found might not be valid under vns8 etc . . .
I found that if I did not stop the NT services, there were some OS locks left on some files - sorry can't remember the details (it was pre-2000).

[jmodic]

Originally posted by efrijters
They 'shutdown immediate' first and restart the db in restrict-mode so they can stop it with 'normal'. Isn't this strange, because the db was already consistently stopped with 'immediate'??

Yes, that is totaly superflous, shutdown immediate is more than enough.

The response from Oracle support states that this is an excellent way to stop the db.

Don't belive everything that is signed by someone who happens to work for Oracle Corp. There (as in any other company) they have some briliant minds, some good ones, some avarage and some that don't have a clue about how their products work.