ORA-00824: cannot set sga_target due to existing solution

ORA-00824: cannot set sga_target due to existing solution

When I got home from work today, I received a call from a colleague, saying that after I used the Oracle9i client to connect to Oracle10g, some parameters were modified, so that Oracle10 could not be started normally, and I had to restart the server several times.

After the remote connection, the system prompts the following when Oracle users start up under sqlplus:

ORA-00824: cannot set sga_target due to existing internal settings, see alert log for more information

It seems that the sga_target parameter is set incorrectly. I checked the sga_target parameter information on the Internet (Specific can be seen in my another reprinted article: ORACLE10--SGA_MAX_SIZE and SGA_TARGET), understand that it is oracle10 new memory parameters, it is used to dynamically adjust the components of the SGA memory. Its content is also stored in spfile.

Previously, in another article, ORACLE9i -- Optimized SGA to a maximum of 1.7G, the instance cannot be started. The relationship between pfile and spfile solves the problem that the instance cannot be started because of SGA_MAX_SIZE adjustment, using this relationship can also solve the sga_target problem today.

In addition, after practice, I found that the method used last time was too cumbersome. Today, I found a simple method through practice.

But the idea is the same: Find a way to change the sga_target value to the normal threshold value, and then start the database instance.

Follow these steps:

1. We can start the database instance with the pfile configuration parameters.

2. create spfile from pfile)

3. Shut down database instances

4. Start the database instance normally

The specific operations are as follows:

[Oracle @ RedHat pfile] $ sqlplus/nolog

SQL * Plus: Release 10.2.0.1.0-Production on Tue Oct 20 00:20:19 2009

Copyright (c) 1982,200 5, Oracle. All rights reserved.

SQL> conn/as sysdba
Connected to an idle instance.
SQL> startup pfile = '/home/oracle/admin/zgz/pfile/init. ora.82220096537'

-- "Start an oracle instance using the pfile file"
ORACLE instance started.

Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
Database opened.
SQL> create spfile from pfile = '/home/oracle/admin/zgz/pfile/init. ora.82220096537'; -- "Rebuilding spfile through pfile"

File created.

SQL> shutdown immediate -- "disabling database instances"
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup -- "using the spfile file to start an oracle instance"
ORACLE instance started.

Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
Database opened.
SQL>

Look! Compared with the previous method, it is not very simple. It can be completed completely in the command line.

Learning is like this. To solve the same problem, you must constantly master the simpler method and make progress!

But when I shut down the database with shutdown immediate, the system suddenly reported the following error: ORA-03113: end-of-file on communication channel

I have never encountered this before. I searched the internet and found many reasons for this error, most of which are caused by poor network connections. As a result, I closed the current SSH window and re-established an SSH connection, solve the problem.