![]() ![]() That means when lsnrctl start is executed after the sqlplus-startup command then the Pro*C/OCI program still complains about an unavailable TNS-listener.Īnd this is exactly the problem with the command sequence in the question - where the emctl start just workarounds the wrong order because it fixes the TNS-listener setup part.Īlso note that for executing Pro*C/OCI programs the EMCTL service is not needed. Note that the order of the commands is important. (you can verify if everything is shutdown via ps aux | grep 'tnsl\|ora') $ echo -e 'connect / as sysdba\nshutdown\nquit'| sqlplus /nolog You can also use Recovery Manager to execute STARTUP and SHUTDOWN commands. $ echo -e 'connect / as sysdba\nstartup\nquit'| sqlplus /nologĪnd a dbshut $ORACLE_HOME$ is basically equivalent to: $ lsnrctl stop Or below command for both downtime and startup time. To start up a database or an instance from the command line, use SQLPlus to connect to Oracle with administrator privileges and then issue the STARTUP command. (times on a Core i7/2.8GHz system, slow spinning hard disk.) How dbstart/dbshut workĪ dbstart $ORACLE_HOME$ call is basically equivalent to: $ lsnrctl start For startup time in alertlog - grep 'Starting ORACLE instance (normal)' alert.log For shutdown - grep 'Completed: ALTER DATABASE CLOSE NORMAL' alert.log Unless of course it crashes, then there won't be a shutdown in the alertlog. Using dbstart/ dbshut is an improvement above the custom method mentioned in the question: method time called tools ![]() Then you can use the scripts like this: $ whoamiĭbstart brings all up which is needed for Pro*C/OCI programs. They are available under $ORACLE_HOME/bin.Īfter a fresh install you have to edit the /etc/oratab file: # cat /etc/oratab You can use the dbstart/ dbshut scripts which come with an Oracle install. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |