Oracle cannot start problem analysis and solution after SGA is modified

1. If the console is not installed on the database machine or the network service name is not configured using the console.
You can log on to the idle process on the server by running the command sqlplus sys/sys as sysdba. See step 4.

2. If the network service name is configured,
In Path D: \ oracle \ product \ 10.2.0 \ db_1 \ Network \ admin \ listener. O
Find listener under RA. ora.
changed to copy Code the code is as follows: # listener. ora network configuration file: D: \ oracle \ product \ 10.2.0 \ db_1 \ Network \ admin \ listener. ora
# generated by Oracle configuration tools.
sid_list_listener =
(sid_list =
(sid_desc =
(sid_name = plsextproc)
(ORACLE_HOME = D: \ oracle \ product \ 10.2.0 \ db_1)
(program = EXTPROC)
(sid_desc =
(global_dbname = xxx (Network Service name ))
(ORACLE_HOME = D: \ oracle \ product \ 10.2.0 \ db_1)
(sid_name = xxx (Network Service name)
)
listener =
(description_list =
(description =
(address = (Protocol = IPC) (Key = extproc1 ))
(address = (Protocol = TCP) (host = 127.0.0.1) (Port = 1568)
)

3. log on to Oracle using DOS
Sqlplus sys/sys @ xxx (Network Service name). As sysdba
Able to log on
Prompt that the idle routine has been connected
4. Find pfile. Under/.../admin/XXX (Service name)/pfile, init. ora. xxxxxxx (number string)

5. execute commands
SQL> startup pfile = 'pfile Path'
Start a database instance using the specified pfile

6. execute commands
SQL> Create spfile from pfile = 'pfile path'; (you must have a semicolon !)
If the file is successfully created, a message is displayed, indicating that the file has been created.
You can log on to the database and check the routine, configuration, and memory.
For 32-bit Windows systems, there is a SGA 1.7g limit
Some OS systems also have some memory parameter restrictions.