Once Oracle modifies the maximum number of connections, the instance cannot be logged in after Oracle is restarted


This is a local stress test. By default, the maximum number of database connections of Oracle 10g is 150. But it takes 300 to test the program.

So I refer to the online information, execute the following two lines of commands, modify the maximum number of connections, restart the Oracle server, and an error occurs, indicating that Oracle cannot log in.


Step 1: modify the maximum number of connections

#Select value from V $parameter where name ='processes'
#Modify the maximum number of connections
alter system set processes = 1000 scope = spfile


After restarting the computer, the original management page of Oracle normal login prompts the error recovery page as follows



Step 2: recheck and fix the problem

Through the Oracle configuration file of the installation directory on the Oracle server, modify the relevant parameters


The main modified parameters are as follows


The parameter processes = maximum number of connections, which is related to the performance of your hardware.

The parameter sessions = processes * 1.1 + 5 is set together with the above parameter processes, which is related to the concurrent processing ability of the database.

Parameter PGA_ aggregate_ Target = quantity * 4m, here we calculate 1600m according to the parameter sessions * 4m.

# Part 1
# processes=150
sessions=335# pga_aggregate_target=25165824pga_aggregate_target=1600M



Step 3: restart the database

After setting the three parameters of Part 1, save the ora configuration file and start it with the sqlplus command line, as follows

#Click the CMD window and enter
CMD >> sqlplus /nolog

#Connect with sydba identity
SQL > connect /as sysdba

#Start Oracle instance
SQL > startup 

#Check for error messages
SQL > ORA-00371: not enough shared pool memory, should be atleast 132663296 bytes



According to the above prompt, we can see that the pool memory parameter needs to be set as follows

# Part 2
# large_pool_size=8388608
# shared_pool_size=83886080



Step 4: finally, start data successfully

After modifying the part 1 and Part 2 parameters in the ora file above, you must restart the database with the sqlplus command line for the first time. The operation is as follows

#Click the CMD window and enter
CMD >> sqlplus /nolog

#Connect with sydba identity
SQL > connect /as sysdba

#Below init.ora The file comes from the configuration file directory where you actually installed the Oracle instance
SQL > startup pfile='D:\oracle\product.1.0\admin\ORA10DBS01\pfile\init.ora.08201701227'

#Check database information
SQL > show parameter process




Step 5, fix the problem, log in successfully, and the interface is as follows





Recommended Today

Multi version management of golang in Windows

Multi version management of golang in Windows currentgolangThere are still some incompatibilities among different versions. Recently, we encountered some problemsgo-microThe framework can only run in go 1.13 ~ 1.14, but I installed it under windows1.15So you need to install other versions of golang, so many versionsgolangHow to useWindowsIt’s coexistence on the Internet. If you find […]