Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy Connect 2.0 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
||
|
|
||
Symptoms |
If Prinergy is started too quickly after the Oracle TnsListener service is started, then Prinergy will fail to start properly. DIAG logs report messages like: "TNS:listener could not resolve SERVICE_NAME given". This problem also prevents SQL scripts from logging in using TNS for logins, such as: sqlplus prinergy/araxi@araxidbserver If you wait approximately 60 seconds after TNS Listener has started, then everything will work properly. |
|
|
|
||
Cause |
Oracle TNS Listener service seems to require at least 60 seconds to initialize AFTER the service says that it's running. | |
|
|
||
Solution |
1) The workaround is to wait 60 seconds after the TNS Listener service has started before trying to start Prinergy. 2) For SQL scripts, if you do not append "@araxidbserver" to the command, then it will also work, without waiting the extra 60 seconds (because TNS listener is not involved). Another workaround is to use "@beq-local" instead of "@araxidbserver", which also won't use the TNS listener. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
11 Sep 2000 |
|