Here is part of my shutdown/startup instructions for Operations: 1. When the Oracle server is to be taken down, using PUTTY, logon in as oracle 2. emctl stop dbconsole 3. sqlplus ‘/ as sysdba’ 4. sql> shutdown 5. exit 6. lsnrctl stop
6. After the Oracle Server is brought up, using PUTTY, logon in as oracle 7. lsnrctl start 8. sqlplus ‘/ as sysdba’ 9. sql> startup 10. sql> select name from v$database; 11. exit 12. emctl start dbconsole I have had the above command in an autostart/shutdown process, which is fairly easy to do. The problem was, if Oracle didn't start due to some problem, which so far has been the recovery area being full, the bad startup wasn't caught. Having Operations do the above command, sometimes (only sometimes), results in a phone call if the messages don't look right. Not a 100% solution either. Tom Duerbusch THD Consultinig Law of Dinner Table Attendance Cats must attend all meals when anything good is served. >>> "Martin, Terry R. (CMS/CTR) (CTR)" <[EMAIL PROTECTED]> 10/19/2008 7:08 PM >>> Hi, Lately we have had some problems with Oracle corruption that we are being told it is because the way we are shutting down our z/Linux guest. What is the cleanest and safest way to shutdown a z/Linux guest? Should we be issuing a separate Oracle shutdown of some sort before shutting down the whole guest? We are running REDHAT REL4 under z/VM 5.3 Thanks in advance! Terry
