Re: Connection problem ORA 12535 TNS Timeout

From: Bernd Maierhofer $dato$ <bernd.maierhofer_at_dato.at>
Date: Thu, 26 Feb 2004 11:46:21 GMT
Message-ID: <h0l%b.84079$174.57043@news.chello.at>

Howard,
thanks for the detailed answer. We have had no trouble using 8.1.5 on Win2k, only since we tried to setup the server in the VMWare box. But I will pay attention to your advice using v9. Btw VMWare is v3.0.0

The listenr.ora on the server loks like this: # C:\ORACLE\ORA81\NETWORK\ADMIN\LISTENER.ORA Configuration File:C:\Oracle\Ora81\NETWORK\ADMIN\listener.ora # Generated by Oracle Net8 Assistant

LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle)(PORT = 1521)) (PROTOCOL_STACK =

      (PRESENTATION = TTC)
      (SESSION = NS)

)
)

CONNECT_TIMEOUT_LISTENER = 60 SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =

      (GLOBAL_DBNAME = bf)
      (ORACLE_HOME = C:\Oracle\Ora81)
      (SID_NAME = bf)

)
)

LOGGING_LISTENER = OFF Thank you,

Bernd

"Howard J. Rogers" <hjr_at_dizwell.com> schrieb im Newsbeitrag news:14a1f766.0402251551.a2df89a_at_posting.google.com...
> "Bernd Maierhofer $dato$" <bernd.maierhofer_at_dato.at> wrote in message
news:<mc5%b.76818$174.71933_at_news.chello.at>...

> > Hi and thanks for reading. My configuration is as follows:
> >
> > Oracle 8.i 8.1.5 Client and Server
> > Server installed in a Win2K Professional VMWare Box, a database is up

and

> > running, connecting locally (loopback) works ok
> > Client is installed on a Win2k machine
>
>
> The version of VMware might have helped, too. But my initial
> observation is that 8.1.5 was never certified for Windows 2000 (from
> memory, 8.1.6 was the first version that was). So you can expect
> fireworks.
>
> > TNSPing can reach the database, times are about 9000 msec, sometimes

3000

> > msec
>
> TNSPing tells you you can reach the *listener*, not the database.
> Which means your client tnsnames must be resolving aliases correctly,
> but your listener hasn't a clue how to forward the request on to an
> instance.
>
> And whilst the log is interesting, I can't comment further about why
> the Listener is having trouble dealing with the connection request
> unless you post the listener.ora.
>
> I will say, however, that tahiti.oracle.com describes error 12160 as
> follows:
>
> TNS-12160 TNS:internal error: Bad error number
>
> Cause: Corrupt error reporting subsystem. This message is not normally
> visible to the user.
>
> Action: For further details, turn on tracing and re-execute the
> operation. If the error persists, contact Oracle Customer Support.
>
> And the fact that something is reported as "corrupted" means this is
> the sort of fireworks you get by running an antiquated and buggy
> Oracle version on a non-certified Operating System inside a
> non-certified virtual machine configuration.
>
> I'd try 9i Release 2 if I were you, since I know that works perfectly
> well inside Vmware.
>
> Regards
> HJR
>
>
> >
> > Connecting from the client fails, the sql.log on the server says:
> > Fatal NI connect error 12160, connecting to:
> >  (LOCAL=NO)
> >
> >   VERSION INFORMATION:
> >  TNS for 32-bit Windows: Version 8.1.5.0.0 - Production
> >  Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version

8.1.5.0.0 -

> > Production
> >  Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version
> > 8.1.5.0.0 - Production
> >   Time: 25-FEB-04 18:35:04
> >   Tracing not turned on.
> >   Tns error struct:
> >     nr err code: 0
> >     ns main err code: -1
> >     TNS-4294967Message -1 not found;  product=NETWORK; facility=TNS
> >
> >     ns secondary err code: 0
> >     nt main err code: 0
> >     nt secondary err code: 0
> >     nt OS err code: 0
> >
> > The listener says:
> > Listen auf:
> >

(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle)(PORT=1521))(PROTOCOL_STACK

> > =(PRESENTATION=TTC)(SESSION=NS)))
> > TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
> > 25-FEB-04 18:03:51 * service_register * BF * 0
> > 25-FEB-04 18:03:51 * service_register * BF * 0
> > 25-FEB-04 18:05:11 *
> >

(CONNECT_DATA=(SERVICE_NAME=bf)(INSTANCE_NAME=bf)(CID=(PROGRAM=C:\Oracle\Ora > > 81\BIN\SQLPLUS.EXE)(HOST=ORTLER)(USER=b.maierhofer))) * > > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3340)) * establish * bf * 0

> > 25-FEB-04 18:09:01 * ping * 0
> > 25-FEB-04 18:11:05 *
> >

(CONNECT_DATA=(SERVICE_NAME=bf)(INSTANCE_NAME=bf)(CID=(PROGRAM=C:\Oracle\Ora > > 81\BIN\SQLPLUSW.EXE)(HOST=ORTLER)(USER=b.maierhofer))) * > > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3350)) * establish * bf * 0
> > 25-FEB-04 18:13:54 * bf *
> > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3350)) * service_update * BF

> > * 0
> > 25-FEB-04 18:13:54 * bf *
> > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3350)) * service_update *

> > * 0
> > 25-FEB-04 18:15:36 *
> >

(CONNECT_DATA=(SERVICE_NAME=bf)(INSTANCE_NAME=bf)(CID=(PROGRAM=C:\Oracle\Ora > > 81\BIN\SQLPLUSW.EXE)(HOST=ORTLER)(USER=b.maierhofer))) * > > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3356)) * establish * bf * 0
> > 25-FEB-04 18:23:51 * bf *
> > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3356)) * service_update * BF

> > * 0
> > 25-FEB-04 18:23:51 * bf *
> > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3356)) * service_update *

> > * 0
> > 25-FEB-04 18:24:04 *
> >

(CONNECT_DATA=(SERVICE_NAME=bf)(INSTANCE_NAME=bf)(GLOBAL_NAME=bf)(CID=(PROGR > >
AM=C:\Programme\Oracle\jre\1.1.7\bin\jrew.exe)(HOST=ORACLE)(USER=Administrat > > or))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.19)(PORT=1221)) * establish *

> > bf * 0
> > 25-FEB-04 18:24:34 *
> >

(CONNECT_DATA=(SERVICE_NAME=bf)(INSTANCE_NAME=bf)(CID=(PROGRAM=C:\Oracle\Ora > > 81\BIN\SQLPLUSW.EXE)(HOST=ORTLER)(USER=b.maierhofer))) * > > (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.31)(PORT=3369)) * establish * bf * 0
> >
> > I already tried to increase the connection_timeout, but this does not help.

> >
> > Thanks for any idea.
> > Bernd

Received on Thu Feb 26 2004 - 05:46:21 CST