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 $ echo -e 'connect / as sysdba\nstartup\nquit'| sqlplus /nologĪnd a dbshut $ORACLE_HOME$ is basically equivalent to: $ lsnrctl stop Ask Question Asked 9 years, 2 months ago. Oracle database startup fails several times. (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 Last night my production server database (ORACLE 10.2.04) was showing me number of connection exceeded as some times it show me. 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.
#ORACLE DB 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
Start the database (with the pfile parameter), then execute the command create spfile from pfile Your database will now always start from the SPFILE unless explicitly told to do otherwise. I started it with docker run -p 1521:1521 -p 5500:5500 -e ORACLESIDxwiki -e ORACLEPDBxwikipdb -e ORACLEPWDxwiki oracle/database:19.3.0-se2 (note: I also tried by mapping a local directory for the DB files with the same slow result). Oracle databases usually expect to be started from an SPFILE. You can use the dbstart/ dbshut scripts which come with an Oracle install. I would suggest that starting an Oracle database from a PFILE is unusual.
0 kommentar(er)
