From Oracle to NOMOUNT

To enable Oracle to the nomount state on Windows, enter the following command without starting the oracle service:

1. C: \> sqlplus/nolog
3. SQL * Plus: Release 10.2.0.1.0-Production on Friday October 14 16:28:13 2011
5. Copyright (c) 1982,200 5, Oracle. All rights reserved.
7. SQL> connect/as sysdba
8. ERROR:
9. ORA-12560: TNS: protocol adapter error.
12. SQL> 

Start the listening service (command: lsnrctl start can also start the service, and can display the IP address and Port number of the listener ):

Net start oracleoradb10g_home1tnslistener

The listening service is started successfully. However, the same error still occurs when the connect command is entered again in sqlplus.

 

I found this problem on the Internet and found that many people have encountered it. If you have encountered a similar problem, try the following methods:

1. In Windows, when we start the Database Service, the database automatically enters the Open state. To start now to the nomount status, you must modify the registry and set the key value to HKEY_LOCAL_MACHINE \ SOFTWARE \ ORACLE \ KEY_OraDb10g_home1.The value of ORA_ORCL_AUTOSTART is changed to FALSE. After modification, it will not automatically start to the Open state, so that it will have the opportunity to start to the nomount state.

The following will first start the service and then connect.

1. C: \> net start OracleServiceOrcl
2. The OracleServiceORCL service is starting.
3. The OracleServiceORCL service has been started successfully.
6. C: \> sqlplus/nolog
8. SQL * Plus: Release 10.2.0.1.0-Production on Friday October 14 17:08:14 2011
10. Copyright (c) 1982,200 5, Oracle. All rights reserved.
12. SQL> connect/as sysdba
13. Already connected to the idle routine.
14. SQL> startup nomount
15. The ORACLE routine has been started.
17. Total System Global Area 603979776 bytes
18. Fixed Size 1250380 bytes
19. Variable Size 213912500 bytes
20. Database Buffers 381681664 bytes
21. Redo Buffers 7135232 bytes
22. SQL>

Next, you can modify the database to the mount and open statuses.

1. SQL> alter database mount
3. The database has been changed.
5. SQL> alter database open;
7. The database has been changed.
9. SQL>

2. Directly start the Database Service, connect to the database, shut down, and then start to nomount.

Why? The main reason is as mentioned above. If oracle's startup parameters in the Registry are not modified, once the service is started, the database will be in the open state and it will not be transferred to the nomount state.

The memory process is still running, and oracle accounts for a small amount of memory, because the memory in the global zone of the SGA system has been released.

1. C: \> sqlplus/nolog
3. SQL * Plus: Release 10.2.0.1.0-Production on Friday October 14 17:24:59 2011
5. Copyright (c) 1982,200 5, Oracle. All rights reserved.
7. SQL> connect/as sysdba
8. Already connected to the idle routine.
9. SQL> startup nomount
10. The ORACLE routine has been started.
12. Total System Global Area 603979776 bytes
13. Fixed Size 1250380 bytes
14. Variable Size 218106804 bytes
15. Database Buffers 377487360 bytes
16. Redo Buffers 7135232 bytes
17. SQL>
18. SQL> alter database mount
19. 2;
21. The database has been changed.
23. SQL> alter database open;
25. The database has been changed.
27. SQL>

In addition, when the database is closed and restarted to the open state, the order of closing the database is shown below (The database has been closed, the database has been detached, And the ORACLE routine has been closed.), The order of startup (The ORACLE routine has been started, the database has been loaded, and the database has been opened).

1. SQL> shutdown immediate;
2. The database has been closed.
3. The database has been detached.
4. The ORACLE routine has been disabled.
5. SQL> startup open;
6. The ORACLE routine has been started.
8. Total System Global Area 603979776 bytes
9. Fixed Size 1250380 bytes
10. Variable Size 218106804 bytes
11. Database Buffers 377487360 bytes
12. Redo Buffers 7135232 bytes
13. The database has been loaded.
14. The database has been opened.
15. SQL>

In addition, if the database is directly started to the nomount state, it cannot be started to the mount state (unless shutdown first). You can only modify the database status to the mount state through the alter database mount statement, similarly, the open state is the same, that is, it can only be:

First:

Startup nomount;

Alter database mount;

Alter database open;

Second:

Startup nomount;

Alter database open;

Third:

Startup open;

 

As shown below:

Startup nomount;

Startup mount;This will cause the ora_01081 error.