Ora-12505 in windows


















To resolve this problem, use the listener. This parameter will tell the listener to use the SID in the connect descriptor as a service name and allow you to connect the client to this particular database. As with any error, make sure to double check your spelling and syntax. For example, the problem may be a matter of a missing character in your jdbc string.

The error may be caused by one of the following reasons: The connect descriptor received by the listened specifies a SID for an instance that has not been dynamically registered with the listener. The connect descriptor received by the listened specifies a SID for an instance that has not been statically configured for the listener. Managed Services. I have faced the same issue and solved by restart the OracleServiceXE service.

Goto Services. Check by doing tnsping and instance name in host machine. It will give u the tns decription and all most of the time host name is different which is not matching.

This help me in my concrete situation. I afraid, that could exists many other reasons with different solutions. Had a similar issue. The issue started occurring suddenly - we are having load balanced database connection URL, but in jdbc connections I was pointing to a single db directly. In my case not was working out, finally i restarted my oracle and TNS listener and everything worked.

Was struggling for 2 days. Just make sure they are not blocked. My oracle stopped working and I was getting this error. I restarted my machine and also tried above solutions.

Ultimately, I opened component services and restarted the oracle services and it all started working. Hope this helps someone. I encounter this problem because I did kill task to "Oracle" task in the Task Manager. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 8 years, 5 months ago. Active 5 months ago. Viewed k times. AJPerez 3, 9 9 gold badges 60 60 silver badges 87 87 bronze badges. Learner Learner 1, 2 2 gold badges 11 11 silver badges 5 5 bronze badges. Starting the OracleServiceXE manually from services worked for me. Add a comment. Active Oldest Votes.

I fixed this issue by correcting my jdbc string. For example, the correct jdbc string should be Wade H Wade H 2, 1 1 gold badge 11 11 silver badges 5 5 bronze badges.

There are two reasons for this: the database has not been started up, the database has not registered with the listener, e. When the database starts, it registers itself with a listener if it is already running. If the listener isn't running, the database doesn't register itself, and if the listener starts, it doesn't go looking for databases that might register with it.

Luke Woodward Luke Woodward Raj: I don't see what your edit brings to the answer, so I've deleted it. If you want to contribute a significant amount to a question, please post your own answer rather than editing someone else's. This should be able to prevent ORA, and after this, I know you may see some other errors like ORA or ORA if you connect to the database from a plain old client version, e.

Oracle 9i client. If you prefer to solve this issue on the server side, the potential solution is to make the listener treat the SID as a service name and establish connections for users. Luckily, Oracle provides a parameter for listener to do this. For cluster databases, we should go for listener. Please note that, such backward compatibility has some restrictions. Which means, you cannot connect it through SCAN listener.



0コメント

  • 1000 / 1000