1 First
, see if the oracle monitor and the oracle service are enabled.
Start oracle monitoring:
In the command line window of cmd, enter lsnrctl start and press Enter to start monitoring.
2 Check what the sid of oracle is called. For example, when creating a database, the instance name is "abc", then manually set the sid of oralce. In the cmd command window, set ORACLE_SID=abc
3
In the command line window of cmd, enter lsnrctl start and press Enter to start monitoring.
2 Check what the sid of oracle is called. For example, when creating a database, the instance name is "abc", then manually set the sid of oralce. In the cmd command window, set ORACLE_SID=abc
3
Then enter sqlplus /nolog, press Enter
and then enter conn / as sysdba; press Enter
4 and then enter startup , press Enter. This step is to start the oracle service. If the startup is told that it has already started, you can enter shutdown immediate first; after the shutdown is over, enter startup.
5After a few seconds, wait for the command to finish running, then you can connect. At this time, you can enter " select count(*) from user_tables; " to test to see if there are query results.
6 The reasons for ORA-01034 and ORA-27101 are various: the main reason is that the current service of oracle is unavailable, shared memory realm does not exist, because oracle has not been started or not started normally, and the shared memory has not been allocated to the current instance . Therefore, by setting the instance name, and then using the operating system authentication method, start the database. In this way, the database will start normally, and two startup exceptions, ORA-01034 and ORA-27101, will not be reported.
and then enter conn / as sysdba; press Enter
4 and then enter startup , press Enter. This step is to start the oracle service. If the startup is told that it has already started, you can enter shutdown immediate first; after the shutdown is over, enter startup.
5After a few seconds, wait for the command to finish running, then you can connect. At this time, you can enter " select count(*) from user_tables; " to test to see if there are query results.
6 The reasons for ORA-01034 and ORA-27101 are various: the main reason is that the current service of oracle is unavailable, shared memory realm does not exist, because oracle has not been started or not started normally, and the shared memory has not been allocated to the current instance . Therefore, by setting the instance name, and then using the operating system authentication method, start the database. In this way, the database will start normally, and two startup exceptions, ORA-01034 and ORA-27101, will not be reported.
Extracted from: https://www.cnblogs.com/alamps/archive/2012/11/29/2794431.html