N/APosted on - 07/18/2011
I downloaded Oracle Developer suite 10g and installed in my PC. Then I opened a form and created one module of emp table. After that I started OC4J instance in Edit/Preference/runtime set application server url http://shahzaib-1:8889/forms90/f90servlet
(Reset to Default) then after that I ran the form through web and download Jinit (JInitiator 18.104.22.168). It then gave me an error
ora-12560 TNS Protocol Adapter Failure
I pressed OK and connected again but again same error. Please help me. I am using oracle 10g database and developer suit 10g only in server no client setup yet.
Thanks in advance.
ORA-12560 TNS Protocol Adapter Failure
Is there a listener running? Have you run the netca program to configure and start the listener? The Oracle docs note that you should troubleshoot the ORA-12560 by tracing the connection:
ORA-12560: TNS: protocol adapter error
Cause: A generic protocol adapter error occurred.
Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and re-execute the operation. Turn off tracing when the operation is complete.
MOSC Note: 117976.1 offers tips for diagnosing the TNS-12560 error noting that the TNS-12560 is in the TNS transport layer and the TNS-12560 may only be a symptom of a lower-level network error as listed in MOSC Note 39662.1.
You can use MOSC Note 39774.1 to get a SQL*Net trace or follow these instructions for getting a SQL*Net trace.
The "TNS-12560: TNS:protocol adapter error" sometimes a transient error on a SQL*Net (Oracle*Net) client, happening sporadically. To turn-on tracing for the ORA-12560, use these settings. Also check/var/log/messages (Linux) for errors:
TRACE_LEVEL_<<listner_name>> = admin
TRACE_DIRECTORY_<<listner_name>> = <<some directory>>
TRACE_TIMESTAMP_<<listner_name>> = true
Possible fixes for the TNS-12560 include:
1. Get the latest patches for the SQL*Net client software.
2. Check your $ORACLE_HOME and $PATH variables
3. Check file permissions on the PC client
4. Ensure that TNS_ADMIN is set properly
5. Check for network firewall issued
6. In Windows, Verify that the database service is started. Verify that the ORACLE_SID parameter is correctly set in the registry.