Record of an Oracle startup error fix

First, the initial situation description:

Login Sqlplus, unable to log in. Change PL/SQL developer, Tip:Ora-12514:tns: The listener is currently unable to identify the service requested in the connection descriptor .

Second, my response:

1. First I restart the Monitoring service and Oracle service in the service. (At this point, it feels like the Oracle service is starting, faster than usual, and not too concerned, looking back, this is a signal ...), and then continue with PL/SQL Developer login, prompt.

2, in the Oracle Network Configuration Assistant, the listener is reconfigured, not a new one, no, delete all the reconstruction, the error is still.

3, change sqlplus login-sqlplus/nolog-conn/as sysdba, at this time think is not the last service did not normally shut down, input: Shutdown immediate, a new error occurred:

Ora-00843:parameter not taking memory_max_targetto account ..., then: Startup, a new prompt appears:

Ora-00844:parameter not taking Memory_target to account
Ora-00851:sga_max_size 3221225472 cannot is set to more than Memory_target 1291845632.

The above two errors are visible in the following file: *\app\administrator\product\11.2.0\dbhome_1\database\oradim.log. This time reminds me that I had adjusted the SGA parameters before I last turned off the machine. To some, the problem is basically OK: adjusting the SGA parameter causes the database to have an error during startup and needs to adjust the parameters back.

4, Sql>conn/as sysdba;

Sql>show parameter spfile; this time, the system database is not valid. It seems that the use of this method is not possible to modify.

Recall the 1th case in parentheses, at this time, Oracle should only start a part, when loaded into the spfile, there is an error, so the direct use of the command to modify the method is not able to get through.

Through the network query, get the change idea: Call up SPFile, modify SPFile, Recall SPFile, and then startup.

Specific as follows:

Restart cmd

Sql>sqlplus/nolog

Sql>conn/as SYSDBA

Sql>create pfile= ' d:\pfile.txt ' from SPFile;

Open D:\pfile.txt, at the end of the file, find Sga_max_size, the value of small, specific can be changed to the original size, if not remember, you can change the small part, try again, not to change small. Of course, this place can also be modified with the command line: Exit-notepad d:\pfile.txt-Modify-Save, enter Sqlplus again.

Sql>create spfile from pfile= ' d:\pfile.txt ';

Sql>startup

OK, this is the end of the question.

Iii. Summary

On the internet to find a lot of solutions, no one can succeed. Some are not sure of the problem, some are only the way, there is no reason, the way is not right. So meet the problem, to analyze the possible reasons, layers of search, experiment, always find a solution. In the process, pay attention to the anomalies (as the service startup time in this issue becomes shorter).

　　

Record of an Oracle startup error fix