ORA-12520 error resolution instance

ORA-12520 error resolution instance

Problem description:

An error was reported when I suddenly found a connection to the database today. When I use pl/SQL dev to connect to data, sometimes I can connect to the database. Sometimes I can report the following connection times:

ORA-12520: TNS: The Listener cannot find the available handle for the desired server type

Log on to the database through the server and report the following connection error:

[Oracle @ dbserver22 ~] $ Sqlplus "/as sysdba"

SQL * Plus: Release 11.2.0.3.0Production on Friday November 14 10:23:23 2014

Copyright (c) 1982,201 1, Oracle. All rights reserved.

ERROR:

ORA-00020: max imum number ofprocesses (150) exceeded

Enter the User Name:

ERROR:

ORA-01017: invalid username/password; login denied

......

SP2-0157: Unable to connect to ORACLE after 3 attempts, exit SQL * Plus

[Oracle @ dbserver22 ~] $

After communicating with developers, the reason was that there was a new business going online last night and the business volume increased, leading to a rise in the number of connections.

Solution:

Increase process connections

-- Stop listening

[Oracle @ dbserver22 ~] $ Lsnrctl stop

-- Kill the connection process

[Oracle @ dbserver22 ~] $ Ps-ef | grep LOCAL = NO | cut-c 10-15 | xargs kill-9

-- Increase the number of connections

SQL> alter system set processes = 650 scope = spfile;

The system has been changed.

-- Restart the database

SQL> shutdown immediate

The database has been closed.

The database has been detached.

The ORACLE routine has been disabled.

SQL> startup

The ORACLE routine has been started.

Total System Global Area1.7103E + 10 bytes

Fixed Size 2245480 bytes

Variable Size 6744444056 bytes

Database Buffers 1.0335E + 10 bytes

Redo Buffers 21708800 bytes

The database has been loaded.

The database has been opened.

SQL> exit

-- Start the listener

[Oracle @ dbserver22 ~] $ Lsnrctl start

Summary:

The possible cause of the problem is simple, but accurate identification and identification require experience and skills. Communication with developers is very important. In the end, as long as you find out the cause, it may be very easy to solve it!

Migration from 32-bit to 64-bit for a single Oracle instance

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian