Solutions to ora-12520 and ora-12516 errors at work

The first reason for this error is that the session and process connections are full. view the number of sessions and processes at www.2cto.com: select count (1) from v $ session; select count (1) from v $ process; display the maximum value of session and process: show paramater session; show parameter process; you must have the dba permission to set the session and process. alter system set processes = 200 scope = spfile; session is a derived value, which is determined by process and automatically generated. formula: sessions = 1.1 * processes + 5. the steps to solve the problem are as follows: 1. log on to the Linux server and enter the command df-h under the root user to view the disk space. normal. 2. log on to the Linux server and run the crs_stat-t command under the oracle user (su-oracle) to check the status of the database instance. all are ONLINE, normal. 3. I tried to connect to the database using the sqlplus method on the server. 4. trying to stop the database with shutdown immediate and shutdown abort, nor was it successful, the error is: ora-24324, ora-24323, ora-00020.5.reboot server, can successfully log on to the database after getting up, enter the command show parameter session and show parameter process. The result is that the maximum number of connections between the session and process is 300 and 335, which is normal. 6. run the select count (1) from v $ session and select count (1) v $ process command to run more than 200 results. When the database is just started, the number of sessions and processes has reached more than 200, which indicates that the database is still abnormal. 7. at this time, I restarted the application on WebSphere and found that I could log on normally. The menu on the left still could not be displayed normally. I checked the background log, the background shows that more than 50 processes are suspended. I think this is why the database session and process remain high. 8. log on to all servers in the cluster in WebSphere, stop the node in the corresponding node, stop the Manager on the master node, and reboot the machines where all nodes are located. 9. after the machine starts normally, go to the master node startManager and startNode, and then to the other control nodes startNode.10. start all servers on WebSphere, and then start WebServer on the Web server (this is the control cluster ).