ORACLE Database Exception Handling

ORACLE DatabaseAs a widely used database, it is well received by many users. However, it is inevitable that someExceptionThe following section describes the exceptions in ORACLE Database Operations.ProcessingMethod.

When the project JDBC connects to the ORACLE database, the following exception is reported:

ORA-12519, TNS: no appropriate service handler found

The Connection descriptor used by the client was:

The initial calculation is the reason that the number of JDBC connections is insufficient.

Therefore, you can increase the number of connections.

It may be that the current number of connections in the database has exceeded the maximum number it can process.

Selectcount (*) fromv $ process -- current number of connections

Selectvaluefromv $ parameterwherename = 'processs' -- maximum number of connections allowed by the database

Modify the maximum number of connections:

Altersystemsetprocesses = 300 scope = spfile;

Restart the database:

Shutdownimmediate;

Startup;

After the database is detached and loaded.

Log on to the database as SYSDBA.

View which users are using data

SELECTosuser, a. username, cpu_time/executions/1000000 |'s ', SQL _fulltext, machine

Fromv $ session a, v $ sqlarea B

I have introduced so many exceptions in ORACLE databases. I believe you have learned some about the Exception Handling Methods in ORACLE databases after learning above, I hope the content mentioned above will be helpful to you.