- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SID parameter in the connect descriptor specifies an instance known by the listener.
- Check for an event in the listener.log file.
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.
- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.
- Check for an event in the listener.log file.
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the INSTANCE_NAME parameter in the connect descriptor specifies an instance name known by the listener.
- Check for an event in the listener.log file.
1. The other process was terminated.
2. The machine on which the other process is running went down.
3. Some other communications error occurred.
1. The other process was terminated.
2. The machine on which the other process is running went down.
3. Some other communications error occurred.
1. Change the entry in sqlnet.ora that determines which services are to be used.
2. Relink the client with at least one of the authentication service adapters that the server supports.
3. Relink the server with at least one of the authentication service adapters that the client supports.
4. Disable authentication on both the client and server.
- The user might not have permission to make up his own pincode.
- The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters.
- The pincode contains any non alphanumeric characters.