Solution for Oracle SQL Developer Connection error (ORA-12505) (two), developerora-12505

Solution for Oracle SQL Developer Connection error (ORA-12505) (two), developerora-12505

With oracle database new connection encountered ora-12505, after the problem is resolved and ora-12519 error, depressing for half a day, after some tossing problem solution, the following small series will share my two solutions for your reference only.

Solution 1:

Today at work in the new connection encountered a ORA-12505, after the solution encountered a ORA-12519 error.

ORA-12505:

Previously, it was no problem to log on to the database using PL/SQL DEVELOPER and SQLPLUS, that is, when the application connects to Oracle through JDBC, the connection fails, ORA-12505 error listener does not currently know of SID given in connect descriptor .......

After searching, it is found that the service_name and sid_name of Oracle are inconsistent, while PL/SQL DEVELOPER and SQLPLUS use service_name for connection, while the application uses sid_name for connection, therefore, PL/SQL DEVELOPER and SQLPLUS can be connected, but applications cannot be connected.

It is easy to solve the problem. It turns out that the sid_name is wrong. First, find the sid_name of the current INSTANCE: SELECT INSTANCE_NAME from v $ INSTANCE, and then enter the obtained sid_name in the connection string of the application.

ORA-12519:

After a ORA-12505 issue is resolved, the application can connect to Oracle, but reports a ORA-12519. It is found that this is because the processes parameter is too low, because the dedicated server is a connection to establish a server process, the processes of the server is set to 150, and the number of sessions is set to 170, the current login session has almost reached the maximum processes, so it reported a ORA-12519 error. You only need to set up the processes to meet your business needs.

Alter system set processses = 300 scope = spfile;

Restart the database.

Below fill a few PIC for SQLDeveloper to report ORA-12505 Error

In addition, the key to failure to connect eclipse to oracle is to mistake sid_name. Now that we know the updated sid_name, everything goes well.

 

Solution 2:

I had a problem with my Oracle database, and I finally got it done. Today I have created another DBA administrator connection method, and I will share my solution with you, I hope it will be useful to you.

Connection error code: Listener refused the connection with following error: ORA-12505, TNS: listener ......

Are you sure this is the SID error connecting to the database,

Solution:

1. know your SID Name: You can search in the registry, or you can use the sqlplus tool of Oracle and run the command as an administrator to view: select instance_name from v $ instance; it must be an administrator; otherwise, the view does not exist ".

2. Modify the SID Name of your database on the Oracle SQL Developer Connection Tool, as shown in the following figure (Change "xe" to "orcl "):

3. Select "Save command" and "role" and select database administrator.

4. Click "save" and "test" and connect. The connection is successful.
If not! Then you have to modify the listening file, see: http://www.bkjia.com/article/73181.htm