ORA-12519 the wrong solution

oerr:ora-12519 tns:no appropriate service handler found

Intermittent failure of client connection, error ORA-12519

Cause:the Listener could no available service handlers that are
Appropriate for the client connection.

Action: Check the Lsnrctl service, instance has been registered, the status display ready, you can connect.

When the listener believes the current number of connections has reached maximum load,
It may set the state's service handler for a instance to "blocked" and begin refusing
Incoming client connections with either of the following errors:ora-12519 or ora-12516

The use of service dynamic registration, by Pmon through the service_update to the current connection, but service_update have time interval,
Therefore, the number of connections displayed by listener may be different from the current actual number of connections.

Search for solutions:

Check to see if the number of processes in the database has reached the size of the parameter processes.

1.select Count (*) from v$process; Gets the current number of processes for the database.
2.select value from V$parameter where name = ' processes '; Gets the upper limit of the number of processes.
3. If the ceiling has been reached, modify the size of the processes in the Initsid.ora.
4. Restart the database to the Nomount state, execute the Create SPFile from Pfile; and startup Open.

The maximum number of concurrent queries to the database since it was started

SELECT * FROM V$license

=====================================================================================

A ORA-12519 error occurred in the JDBC connection at the time of the stress test.

The connection is an error as follows:

<2008-8-23 01:34 A.M. 38 sec cst> <Warning> <JDBC> <BEA-001129> <received exception while creating Connection for Pool "RAC11G1": Listener refused the connection with the following error:

ORA-12519, tns:no appropriate service handler found

The Connection descriptor used by the client is:

172.0.2.58:1521:rac11g1

A half-day Metalink was checked, and the final discovery was due to a bug caused by the setup of the Oracle initialization parameters.

Sql> Show PARAMETER Session

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

Java_max_sessionspace_size integer 0

Java_soft_sessionspace_limit integer 0

License_max_sessions integer 0

license_sessions_warning integer 0

Session_cached_cursors Integer 50

Session_max_open_files Integer 10

Sessions Integer 600

Shared_server_sessions integer

Sql> Show PARAMETER PROCESS

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

Aq_tm_processes integer 0

Db_writer_processes Integer 2

Gcs_server_processes Integer 2

Global_txn_processes Integer 1

job_queue_processes Integer 1000

Log_archive_max_processes Integer 4

Processes integer 150

Depending on the Oracle documentation, the initialization parameters for sessions and transactions should originate from the processes parameter, Sessions = processes * 1.1 + 5 According to the default settings.

However, the current sessions setting has reached 600, and the processes settings have not changed, still 150, resulting in too many user sessions connected to Oracle, Oracle does not have enough background processes to support these sessions.

Detailed problem descriptions can refer to Metalink's documentation: DOC id:note:240710.1.

The solution is very simple, directly set the appropriate processes to produce on it.

=====================================================================================

Methods for modifying the value of a process two (for Linux systems):

First go to oracle_base/admin/your instance name/profile/directory to find a Init.ora file, and then modify the value of the process inside, and then copy the file to the Oracle_home/dbs directory, and rename the file to Initorcl.ora (where the ORCL is your database instance name, my database instance is ORCL so named Initorcl.ora)

Log in as Sysoper with the SYS user Sqlplus

That is, Sqlplus Sys/sa as Sysoper;

After entering the Sqlplus, the database is closed, the Shutdown Abort command can be used, and the shutdown Immediate command can be used, and shutdown Abort command is recommended. Then use the command startup force can be, plainly is to restart the database.