Oracle SQL Developer Connection Error (ORA-12505) solution (two kinds) _oracle

When you create a new connection with an Oracle database, you encounter ora-12505, this problem is resolved and ora-12519 error, depressed for a half-day, after a toss problem solved, the following small series of my two solutions to share to you, for reference only.

Solution One:

Today when you work in a new connection to encounter ORA-12505, resolved and encountered ORA-12519 error.

ORA-12505:

There is no problem with using Pl/sql Developer and sqlplus to log on to the database before the application can connect to Oracle through JDBC, ORA-12505 error listener does not currently of SID given in Connect descriptor .....

After looking, we found that Oracle's service_name and Sid_name were inconsistent, while pl/sql developer and Sqlplus were connected by service_name, and the application was connected according to Sid_name, so pl/ Problems where SQL developer and sqlplus can connect and applications cannot connect.

Solve the problem is very simple, originally is oneself will sid_name to make a mistake; first find the Sid_name:select instance_name from v$instance of the current instance, and then populate the resulting sid_name into the application's connection string.

ORA-12519:

After the ORA-12505 problem is resolved, the application can connect to Oracle, but it is reported ORA-12519. After finding this is due to the processes setting of the parameter is too low, because the dedicated server is a connection to establish a server process, the server processes set to the 150,session number set to 170, and the current login session has almost reached the maximum processes, so reported ORA-12519 error. Simply set the processes to meet the needs of the business can be resolved.

Alter system set PROCESSES=300 Scope=spfile;

Then restart the database.

Below a few pieces of pic for even Sqldeveloper newspaper ORA-12505 wrong

Add another: The key to Eclipse's failure to connect to Oracle is to get sid_name wrong. Now I know the updated sid_name, everything goes well.

Solution Two:

I had a problem with Oracle database before, and I finally got the trouble, and today I created a connection with a DBA administrator problem, I now share the solution to you, I hope to be useful to you.

Connection times wrong code: Listener refused the connection with following Error:ora-12505,tns:listener ...

Determine that this is a SID error for the connection database.

Workaround:

1. Know your SID name: You can find it in the registry, or you can view it by using the Oracle Sqlplus tool and connecting to the administrator by clicking the command: Select instance_name from v$instance; must be administrator, otherwise "view does not exist ”。

2. Modify your database SID name on the Oracle SQL Developer Connection Tool, and I'll do the following (modify "XE" to "ORCL"):

3. Check "Save Command", "role" Select Database administrator.

4. Click "Save" and "test" and connect, and the rest is the successful connection.
If not again! Then you have to modify the listening file, see: http://www.jb51.net/article/73181.htm