| Title: | SQL/Services Forum |
| Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) |
| Moderator: | SQLSRV::MAVRIS |
| Created: | Thu Oct 13 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2214 |
| Total number of notes: | 8586 |
Is this the right place to ask questions about the OCI dispatcher?
A customer is trying to get the FT version to work. When they start
things up the state of the OCI dispatcher is unknown. and they don't
seem to be able to do anyhting to change the state, except that if they
change the transport from SQL*NET to TCP/IP it starts up, but crashes
when they try to use it. The log file says something like:
SQL*NET TNSNLPAGAS() services failed
SQL*NET SQL*NET TNSLISTENER() services failed
no listener could be created
Peter
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2142.1 | Did they comment out AUTHENTICATION_SERVICES? | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Thu Feb 13 1997 16:21 | 22 |
Hi Peter, This is as good a place as any. We've also kept the rdb70 qar database open for qars on "SQL*Net for Rdb". The only time the dispatcher state will be "unknown" is when the sqlsrv_manage session is not connected to the server. If they are connected and the dispatcher is not running, it'll probably say "inactive". Anyway, in order to use the OCI_DISP with an oracle client, the transport type must be SQLNET not TCPIP. Have them check their listener.ora file. Did they comment out the following line? # SQLNET.AUTHENTICATION_SERVICES = (NONE) If this is not commented out (with the # character), the dispatcher will fail to start. I'm not sure how this was documented in FT1, but it's better documented in FT2. Sue | |||||
| 2142.2 | ukvms3.uk.oracle.com::PJACKSON | Oracle UK Rdb Support | Fri Feb 14 1997 05:11 | 7 | |
They have commented out that line - it is in the release notes.
Alan Ball who did the installation was back in yesterday afternoon and
spoke to the customer. It is still not working. They have sent him some
log files.
Peter
| |||||
| 2142.3 | AVMSV1::EKREISLE | Erich Kreisler | Fri Feb 14 1997 09:26 | 11 | |
Here are my experiences from creating an OCI dispatcher: 1. The dispatcher acts as listener, so make sure that the listener has a different name as the Oracle7 listener. 2. Always use different ports than the O7 listener 3. Place the file created by NETMAN in SYS$COMMON:[SQLSRV71.SQLNET.NETWORK.ADMIN] and remove any bogus keywords as described before. Also make sure that you have the coorect tnsnames.ora also on the client side. Hope this helps, erich | |||||