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 SQL> set lines 200 SQL> col instancename for a50 SQL> select from ( select STARTUPTIME FROM dbahistdatabaseinstance ORDER BY startuptime DESC) WHERE rownum < 10 STARTUPTIME - 03-SEP-20 03.24.43.000 AM 03-SEP-20 03.24.27.000 AM 01-SEP-20 02.32. $ echo -e 'connect / as sysdba\nstartup\nquit'| sqlplus /nologĪnd a dbshut $ORACLE_HOME$ is basically equivalent to: $ lsnrctl stop You can use below query to check Oracle database uptime history. (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 Because an instance exists in memory and a database (in the narrowest sense of term) is a set of files on disk, an instance can exist without a database and a database. Every running CDB is associated with at least one Oracle database instance. Using dbstart/ dbshut is an improvement above the custom method mentioned in the question: method time called tools The database instance manages the data associated with the CDB and its PDBs and serves their users.
Then you can use the scripts like this: $ whoamiĭbstart brings all up which is needed for Pro*C/OCI programs. My_sid:/home/juser/app/juser/product/11.2.0/dbhome_1:N Or below command for both downtime and startup time.
Oracle startup time install#
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 kommentar(er)
