Listener tracing in 11g

Hi ,
I have three Oracle DB instance running on AIX machine with default listener named "Listener".
I want enable listener tracing for one of DB instance for tracing connection time-out error in Prod env.
Any suggestions how to enable for single instance only.
Thanks .

977220 wrote:
Hi Sb92075 ,
It throws "ORA-03135: connection lost contact” in alert.log file and it is not case with any specific user or specific time ...Normally it works OK but in-between any time it throws connection timeout error So wanted to investigate further .
IMO, ORA-03135 is different from "timeout"
03135, 00000, "connection lost contact"
// *Cause: 1) Server unexpectedly terminated or was forced to terminate.
// 2) Server timed out the connection.
// *Action: 1) Check if the server session was terminated.
// 2) Check if the timeout parameters are set properly in sqlnet.ora.
Listener.log file doesn't have any info about particular time-stamp when connection was not successful.Listener is only involved briefly, when client makes initial request to connect to the DB.
After the DB & client establish direct packet exchange then the listener is no longer involved at all.
>
>
So if not possible for instance than need to enable for all instance .Was concern about amount of log it will generated .
Thanks for your response.can you isolate ORA-03135 to specific client system?

Similar Messages

Unable to connect to sqlplus .. sys as sysdba .. No listener in Oracle 11G

Hi ,
I have installed Oracle 11.2.0 . When connecting to sqlplus with sys as sysdba . Getting error as NO listener .
I started listener . But finally getting the message as
The listener supports no services
The command completed successfully
Kindly help

I am getting the same message
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/11.2.0/dbhome_1/log/diag/tnslsnr/oracledb/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracledb.example.com)(PORT=1521)))
The listener supports no services
The command completed successfully
I don't find the services entry here .

Listener tracing

hi,
if i set trace 16 in lsnrctl
what info is written to the trace file
i know it should be Information about each Oracle Net connection.
but i can't find any!!!!
Thanks

Hi all,
sorry for being late all that long , i had a very bad fever :-)
i went to listener.ora and made
LOGGING_listener=on
TRACE_LEVEL_LISTENER = support
LOG_DIRECTORY_listener=C:\sydhq11_trace
then stop restart the listener , then connect from sqlplus with user called USMAN
i went to the log (attached) , find no usman at all !!!!!
why is that?
thanks..
TNSLSNR for 32-bit Windows: Version 10.1.0.2.0 - Production on 06-JUL-2007 21:02:58
Copyright (c) 1991, 2004, Oracle. All rights reserved.
System parameter file is F:\oracle\product\10.1.0\sydhq11_Home\network\admin\listener.ora
Log messages written to C:\sydhq11_trace\listener.log
Trace information written to F:\oracle\product\10.1.0\sydhq11_Home\network\trace\listener.trc
Trace level is currently 16
Started with pid=3292
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROCipc)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=1521)))
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
06-JUL-2007 21:03:00 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=bassem))(COMMAND=status)(ARGUMENTS=64)(PASSWORD=xxxxxxxx)(SERVICE=LISTENER)(VERSION=168821248)) * status * 0
06-JUL-2007 21:03:20 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=SYDHQ11)(CID=(PROGRAM=F:\oracle\product\10.1.0\sydhq11_Home\BIN\sqlplusw.exe)(HOST=SERVER)(USER=bassem))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=3979)) * establish * SYDHQ11 * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
06-JUL-2007 21:03:24 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=SYDHQ11)(CID=(PROGRAM=F:\oracle\product\10.1.0\sydhq11_Home\BIN\sqlplusw.exe)(HOST=SERVER)(USER=bassem))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=3980)) * establish * SYDHQ11 * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
06-JUL-2007 21:03:25 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=SYDHQ11)(CID=(PROGRAM=F:\oracle\product\10.1.0\sydhq11_Home\BIN\sqlplusw.exe)(HOST=SERVER)(USER=bassem))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=3981)) * establish * SYDHQ11 * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
06-JUL-2007 21:03:41 * ping * 0
06-JUL-2007 21:03:41 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=SYDHQ11)(CID=(PROGRAM=F:\oracle\product\10.1.0\sydhq11_Home\BIN\sqlplusw.exe)(HOST=SERVER)(USER=bassem))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=3985)) * establish * SYDHQ11 * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
06-JUL-2007 21:03:42 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=SYSTEM))(COMMAND=status)(ARGUMENTS=64)(SERVICE=(ADDRESS=(PROTOCOL=TCP)(HOST=server)(PORT=1521)))(VERSION=168821248)) * status * 0
06-JUL-2007 21:03:48 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=SYDHQ11)(CID=(PROGRAM=F:\oracle\product\10.1.0\sydhq11_Home\BIN\sqlplusw.exe)(HOST=SERVER)(USER=bassem))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=3990)) * establish * SYDHQ11 * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
06-JUL-2007 21:03:54 * (CONNECT_DATA=(SID=SYDHQ11)(CID=(PROGRAM=F:\oracle\product\10.1.0\sydhq11_Home\perl\5.6.1\bin\MSWin32-x86\perl.exe)(HOST=SERVER)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=3992)) * establish * SYDHQ11 * 12505
TNS-12505: TNS:listener does not currently know of SID given in connect descriptor
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=server)(PORT=8080))(Presentation=HTTP)(Session=RAW))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=server)(PORT=2100))(Presentation=FTP)(Session=RAW))
06-JUL-2007 21:03:58 * service_register * sydhq11 * 0
06-JUL-2007 21:04:06 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=SYDHQ11)(CID=(PROGRAM=F:\oracle\product\10.1.0\sydhq11_Home\BIN\sqlplusw.exe)(HOST=SERVER)(USER=bassem))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.4)(PORT=3995)) * establish * SYDHQ11 * 0
06-JUL-2007 21:04:16 * service_update * sydhq11 * 0

Multiple listener on 9i and 11g

Hi all
I have 9i and 11g installation on same oracle user.
3 of db are using 9i and 1 of db is using 11g binaries
my 9i listener is working fine but when i try to do tnsping for 11g db which is upgraded from 9i is not working.... TNS_ADMIN is set 11g.
echo $TNS_ADMIN
/spqa01/app/oracle/product/11.1.0/network/admin
which tnsping
/spqa01/app/oracle/product/11.1.0/bin/tnsping
when i do tnsping SPD1
Attempting to contact (description=(address=(protocol=tcp)(host= qdchudaa)(port=1527))(connect_data=(sid=SPD1)))
TNS-12541: TNS:no listener
listener of the 9i have below entries
LISTENER_SPQA =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.qdx.com)(PORT = 1526))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = SPQA_EXTPROC))
SID_LIST_LISTENER_SPQA =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /spqa01/app/oracle/product/9.2.0)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = SPQA1.QDX.COM)
(ORACLE_HOME = /spqa01/app/oracle/product/9.2.0)
(SID_NAME = SPQA1)
(SID_DESC =
(GLOBAL_DBNAME = SPQA2.QDX.COM)
(ORACLE_HOME = /spqa01/app/oracle/product/9.2.0)
(SID_NAME = SPQA2)
(SID_DESC =
(GLOBAL_DBNAME = RMANTST.QDX.COM)
(ORACLE_HOME = /spqa01/app/oracle/product/9.2.0)
(SID_NAME = RMANTST)
(SID_DESC =
(GLOBAL_DBNAME = SPD2.QDX.COM)
(ORACLE_HOME = /spqa01/app/oracle/product/9.2.0)
(SID_NAME = SPD2)
----------tnsnames.ora of 9i
SPD1 =
(DESCRIPTION =
(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = xxx)(PORT = 1525)))
(CONNECT_DATA =(SERVICE_NAME = SPD1.qdx.com) (INSTANCE_NAME = SPD1)))
SPQA1.QDX.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx)(PORT = 1526))
(CONNECT_DATA =
(SERVICE_NAME=SPQA1.qdx.com)
SPQA1 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx)(PORT = 1526))
(CONNECT_DATA =
(SERVICE_NAME = SPQA1.qdx.com)
INSTANCE_NAME = SPQA1)
SPQA1 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx)(PORT = 1526))
(CONNECT_DATA =
(SERVICE_NAME=SPQA1.QDX.COM)
SPQA2.QDX.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx)(PORT = 1526))
(CONNECT_DATA =
(SERVICE_NAME=SPQA2.qdx.com)
====================listener.ora of 11g
LISTENER_SP11 =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = extproc1))
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.qdx.com)(PORT = 1527))
SID_LIST_LISTENER_SP11 =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME= /spqa01/app/oracle/product/11.1.0 )
(PROGRAM = extproc)
same tnsnames.ora in 9i in 11g
both compatible is set to 11.1.0 and local_listner is set to (ADDRESS =(PROTOCOL=TCP)(HOST=xxx)(PORT=1527))
How to configure listener which can support 11g instances separatly
please help

How to configure listener which can support 11g instances separatly hi in this case you need to put 9i & 11g network files in different locations for example
ORACLE 9i:-
export TNS_ADMIN=/u01/app/oracle/product/9.2.0/db_1/network/admin
ORACLE 11g:-
export TNS_ADMIN=/u02/app/oracle/product/11.1.0/network/admin
then export which listener you wan...
TWO_TASK(tns connection string) & TNS_ADMIN(path of network files $ORACLE_HOME/network/admin) before if you want to use specific listener either 11g or 9i.
HI Sb,
can you correct if im wron. Thanks

11g listener

Hi
Oracle 10.2.0.3
Oracle 11.2.0.1
AIX 5.3
I have six databases on one server. I have upgraded one database to 11g and rest of the databases are on 10g.
what i have to do so 10g databases talk to 11g listener?
and what should i do with 10g listener?
should i keep 10g listener or 11g listener?
Thanks,
Vishal

>
I have six databases on one server. I have upgraded one database to 11g and rest of the databases are on 10g.
what i have to do so 10g databases talk to 11g listener?
and what should i do with 10g listener?
should i keep 10g listener or 11g listener?
>
Pl indicate how many ORACLE_HOMEs you have - do you have one per instance (dedicated OH) or one per release (shared OH) ? I suspect you have a shared OH. How many listeners do you have - one for 10g and one for 11g ?
My personal preference is to have the 11g listener service the 11g instances and the 10g listener service the 10g instances, although the 11g listener is perfectly capable of servicing all of the instances.
HTH
Srini

CLIENT SIDE TRACING IN SQL*NET V2

제품 : SQL*NET
작성날짜 : 1997-10-10
Client Tracing
~~~~~~~~~~~~~~
1) Set the environment variable TNS_ADMIN to the directory where the
tnsnames.ora and listener.ora files exist.
The default location is $ORACLE_HOME/network/admin. Set $TNS_ADMIN
to this if it is not set. This ENSURES you know which files you are
using.
2) Start the listener: lsnrctl
> set password <password>
> start
Note any errors. If you do not have a password set then ignore the
set password command.
3) If the listener started, start the database.
4) Create a file in $HOME called .sqlnet.ora and add the lines:
trace_level_client= 16
trace_file_client=client
trace_directory_client= /tmp (or similar)
trace_unique_client=true
5) Try to connect from SQL*Plus thus:
sqlplus username/password@alias
or
sqlplus username/password
substituting a suitable alias.
6) If you get an error we may need to see the client trace file
/tmp/client_<PID>.trc where <PID> is the process ID of the
client process (*1).
This will be quite large so it is best to FAX or EMAIL it.
*1 Note: On earlier versions of SQL*Net the filename may NOT have
the process ID appended to it.
Listener Tracing:
~~~~~~~~~~~~~~~~~
1) Edit your $TNS_ADMIN/listener.ora file and add the lines:
TRACE_LEVEL_LISTENER = 16
TRACE_DIRECTORY_LISTENER = /tmp
TRACE_FILE_LISTENER = "listener"
2) Stop and restart the listener:
lsnrctl stop
lsnrctl start
Output should go to /tmp/listener.trc

By default in 11g traces will go to the ADR which is a new feature.
To disable that feature add the following line to your sqlnet.ora
diag_adr_enabled =OFF
[oops] saw that this is over a month old this post - sorry about that!
hope that helps
John
Edited by: Johnsung on Sep 27, 2012 3:59 PM

Listener Does not Respond

I am having an issue with a listener . All of a sudeen , listener stopped responding .
When I was doing lsnrctl stat , I was getting "TNS-01189" . When I reloaded the listener , I am getting the same error .
I am on 11g r2 on windows 2008 r2 64 bit .
Thanks in Advance.
C:\Users\Administrator>lsnrctl reload
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 18-OCT-2010 20:29
:20
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=198.6.432.35)(PORT=1521)
TNS-01189: The listener could not authenticate the user
C:\Users\Administrator>lsnrctl reload
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 18-OCT-2010 20:30
:35
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
The command completed successfully
C:\Users\Administrator>

01189, 00000, "The listener could not authenticate the user"
// *Cause: The user attempted to issue a privileged administrative command, but
// could not be successfully authenticated by the listener using the local OS
// authentication mechanism. This may occur due to one of the following
// reasons:
// 1. The user is running a version of LSNRCTL that is lower than the version
//    of the listener.
// 2. The user is attempting to administer the listener from a remote node.
// 3. The listener could not obtain the system resources needed to perform the
//    authentication.
// 4. The local network connection between the listener and LSNRCTL was
//    terminated unexpectedly during authentication message exchange, such as
//    if LSNRCTL program was suddenly aborted.
// 5. The communication between the listener and LSNRCTL is being intercepted
//    by a malicious user.
// 6. The software that the user is running is not following the authentication
//    protocol, indicating a malicious user.
// *Action: Make sure that administrative commands are issued using the LSNRCTL
// tool that is of a version equal or greater than the version of the listener,
// and that the tool and the listener are running on the same node. You can
// issue the VERSION command to find out the version of the listener.
// If a malicious user is suspected, use the information provided in
// the listener log file to determine the source and nature of the requests.
// Enable listener tracing for more information. If the error persists,
// contact Oracle Support Services.are you 100% CERTAIN that ORACLE_HOME is correct?
are there more than one ORACLE_HOME on this system?
Handle:      user11142794
Status Level:      Newbie
Registered:      May 7, 2009
Total Posts:      68
Total Questions:      33 (23 unresolved)
so many questions & so few answers.
Edited by: sb92075 on Oct 18, 2010 6:05 PM

TRACING IN SQL*NET V2

제품 : SQL*NET
작성날짜 : 1997-10-10
Introduction
~~~~~~~~~~~~
For most problems you need to identify the relevant parts of a
connection to trace. To do this consider which scenario you are
having problems with and where tracing needs to be enabled.
Note that tracing produces a lot of output , especially at higher
trace levels.
There are 3 main areas of SQL*Net that can produce trace output:
1 = the SQL*Net 'client'
2 = the 'listener' process
3 = the SQL*Net 'server'.
a) Establishing a connection:
Client ----> Listener ----> Server
1 2 3
b) An established connection:
Client --------> Server
1 3
c) Opening a database link:
Client ----> Server ----> Listener -----> Server2
1 3 1 2 3
Note here that the Oracle server process is also a SQL*Net
client when it makes an outgoing call to a listener to
open a database link. Database links are OPENED when first
used. They should then remain open until closed.
d) An established database link:
Client ----> Server -----> Server2
1 3 1 3
In each case here there are several potential sampling points. You
should be able to identify quickly which of these scenarios matches
your setup. As these scenarios are likely to involve connections
between different machines you should remember that tracing for any
process is controlled by the configuration details that the process
reads WHEN IT IS STARTED. This is especially important when looking
at MTS connections as the SQL*Net server is the 'dispatcher' process.
Some dispatchers are started when the database instance is started
and others may start at a later time (on demand). Each dispatcher will
read their SQL*Net configuration WHEN THEY START.
7.2 Client Tracing
~~~~~~~~~~~~~~
For client TOOLS edit or create the file $HOME/.sqlnet.ora and add
the lines:
trace_level_client=16
trace_file_client=cli
trace_directory_client=/tmp # Or a known directory
trace_unique_client=true # Add '_pid' to trace filename
This will turn on FULL tracing for your user account only producing
output in a file called /tmp/cli_<PID>.trc .
(For some SQL*Net versions the file will be just /tmp/cli.trc)
For client 'ORACLE' process (as in the case of database links) put this
same information into $TNS_ADMIN/sqlnet.ora file.
On versions up to and including Oracle 7.0.16 client trace may not
add a process ID to the name of the trace file. This means two
processes may end up writing to the same trace file unless you
take care to control which processes write trace output to each file.
7.3 Listener Tracing
~~~~~~~~~~~~~~~~
Listener tracing can ONLY be configured in the listener.ora file.
Add the lines below to the listener.ora file:
trace_level_listener=16
trace_file_listener=listener
trace_directory_listener=/tmp # Or a known directory
This will define FULL listener tracing to the file /tmp/listener.trc.
You can enable this tracing by either:
lsnrctl reload
OR
lsnrctl stop;
lsnrctl start;
TCP/IP
~~~~~~
It is often useful to confirm that a listener is listening on a
specified address. Most Unix machines include a command called
'netstat' (Often in /etc or in /usr/etc). The command netstat -a
should list all TCP/IP end points on which a listener is listening.
Eg:
For a listener listening on HOST=... PORT=1580 there should be a
netstat entry of the form:
RecvQ SendQ Local Address Foreign Address TCP state
0 0 *.1580 *.* LISTEN
Note: Some versions of netstat will only list established connections
and not listen end points. See the man page on your machine.
7.4 Server Tracing
~~~~~~~~~~~~~~
Server side trace is not required as often as the other two traces
mainly because most problems are related to establishing a connection.
Once a connection has been established the client and server processes
are communicating. It is sometimes useful to see exactly what SQL
commands have been received by the server, and what data it has sent
back out.
The file $TNS_ADMIN/sqlnet.ora controls the server side tracing. Add
the lines below to this file:
trace_level_server=16
trace_file_server=server
trace_directory_server=/tmp # Or a known directory
Output should be sent to the file /tmp/server_<PID>.trc
Note: Server side tracing acts on the SQL*Net server side.
For dedicated connections this is the Oracle process on the
server machine.
For MTS connections this is the DISPATCHER and NOT the shared
server. Data is passed between the dispatcher and the shared
servers via the SGA and this does NOT involve SQL*Net.
It is also important to note that as a dispatcher handles
several client processes the dispatcher trace output can be a
mix of trace from many client processes making it VERY difficult
to follow. The general advice for such problems is:
a) See if the problem reproduces WITHOUT using MTS - if
so the trace is much cleaner
b) If a problem ONLY reproduces under MTS ensure the machine
is in a controlled environment so you can be sure that only
YOUR process is using the dispatcher.
7.5 Trace Summary
~~~~~~~~~~~~~
1) Identify where you need to trace.
2) Identify which files on which machines control tracing at these
points. Tracing is controlled in the following files:
Client Server Listener
~~~~~~ ~~~~~~ ~~~~~~~~
Files: $HOME/.sqlnet.ora sqlnet.ora listener.ora
sqlnet.ora
3) Add in the relevant trace parameters (See Below)
4) Restart any processes that need to read the new trace values.
Reload the listener as required.
5) Reproduce your problem
6) Save all your trace output immediately
7) Disable the tracing
7.6 Main Trace Parameters
~~~~~~~~~~~~~~~~~~~~~
trace_level_listener = off
trace_file_listener = Filename *1
trace_directory_listener = Directory *2
*1 Unquoted (") filenames will be translated into lower case.
*2 You CANNOT use environment variables in the Filename or Directory
name.
7.7 Diagnosing Trace output
~~~~~~~~~~~~~~~~~~~~~~~
Trace output can be very difficult to follow. Before looking at a
trace file make sure:
a) You are familiar with the sequence of events in setting up
a connection. SQL*Net connections follow a sequence of
events - you will need to determin where in the sequence
the problem occurs.
b) Do not be misled by error reports in the trace files. You
must follow the context of the errors - an error may be
quite valid at that point in a sequence. Eg: For client
connections a list of addresses to call is built - if the
first address yeilds no response the next address is tried.
This next address may yeild a response and the 'true' error
occurs at this point in the sequence.
c) Do not be misled by unusual 'Bequeath' connections in the
trace. If an error is received over SQL*Net the client
may use a "Bequeath" operation to spawn an oracle process
which it then uses to get the TEXT of the error. A very short
exchange of packets occurs and the bequethed process exits.
The 'TRUE' problem is likely to be before this bequeath
operation.
Useful trace 'tags':
The following are useful items to follow in trace files - these
are not guaranteed to be valid across all SQL*Net releases and
are for guidance only. Entries are assumed to be taken at trace
level 16 to allow data packets to be seen. This will produce a
LOT of trace output.
-<ERROR>-
Error information follows. Remember the error may be acceptable
osntns: Calling address
Shows address list constructed for a call OUT to a listener
nricall: Making call with following address information: ...
Shows the ACTUAL address being called from the above list
nsopen: entry
We are about to try and open a connection.
nsopen: transport is open
nsopen: error exit
A connection to the called address has been made / failed.
nsclose: ...
An established connection is being closed - check nearby
for errors.
nscall: redirected
The client has been redirected to a differenct address.
The next step should be to call the new address. The address
should appear in an earlier data packet.
nspsend / nsprecv
Outgoung / Incoming data

This forum is for Oracle Migration Workbench issues, i.e. migration using the workbench from a non Oracle database to an Oracle database.
Here are some pointers that may be useful, but you may need to get more information elsewhere, for example Oracle Customer Support.
a Oracle 7.1 client (including your example) will connect to an Oracle 8.1.5 server.
Is the server correctly configured (can a client connect from another machine)?
Tracing can be turned on in the client, server and/or listener to get further information.
Turloch

TNS:listener could not hand off client connection

while trying to select from dblink I got ORA-12518: TNS:listener could not hand off client connection
What should I do?
here is the listener.ora
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_2)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = disater)(PORT = 1521))
)

What is the operating system and database version for remote and local machines.
Are you using dedicated or threaded server on the remoted DB. More information is needed.
output from error message search:-
12518, 00000, "TNS:listener could not hand off client connection"
// *Cause: The process of handing off a client connection to another process
// failed.
// *Action: Turn on listener tracing and re-execute the operation. Verify
// that the listener and database instance are properly configured for
// direct handoff. If problem persists, call Oracle Support.
// *Comment: The problem can be worked around by configuring dispatcher(s)
// to specifically handle the desired presentation(s), and connecting
// directly to the dispatcher, bypassing the listener.

Listener service stopping periodically

Hi all,
My Oracle 10gR2 listener service has been stopping periodically around 9.00am every monday for the past 4 weeks now. I checked every log files (alert log, listener log, OS SuSE Ent Linux log) and nothing was reported. Once I restart the listener service, every thing will be back to normal.
Has anyone exprience this before or anyone has an idea on what is happening?
Regards,

Hey
maybe it will give you a hint when you enable the listener tracing:
http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/troublestng.htm#i423150
and check this metalink Note: 340091.1
have you clusterware (check with crs_stat -v -t) or RAC installed?
Regards

PSFT Listener in OIM

Hi
I followed the steps in connector guide to deploy the PSFT listener in OIM server. I didn't see an option on how to deploy the listener in Weblogic. By default it is deployed in OIM Server.
We have a requirement to deploy PeopleSoft Listener in Weblogic server but not on OIM Sever. let me know how can I do this.
Thnx

The documentation is here for deploying the listener for the 11g version: http://docs.oracle.com/cd/E22999_01/doc.111/e25370/deploy.htm#autoId12
Basically it's the same as going to the weblogic admin console, selecting deployments, and choosing the ear file that is in the connector directory. The listener, when it connects to oim, it is required to be able to find an xml file that is in the file structure, so you will want to make sure this file exists wherever the listener is deployed.
-Kevin

Impossible to start a listener: Failed to start service, error 3 TNS-12560

Hi all,
I had a database in my machine in 10g.
I have installed oracle 11.1.0.7 on the same machine.
So now i have 2 oracle_home.
With 10g I have a default listener which is running on port 1521.
I wanted to run an other listener under the 11g oracle home.
listener.ora:
# listener.ora Network Configuration File: C:\ora111\network\admin\listener.ora
# Generated by Oracle configuration tools.
LISTENER2 =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = T0009696.corp.gltrade.com)(PORT = 1522))
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
C:\ora111\BIN>lsnrctl start listener2
LSNRCTL for 32-bit Windows: Version 11.1.0.7.0 - Production on 16-MARS -2010 15:21:19
Copyright (c) 1991, 2008, Oracle. All rights reserved.
Lancement de tnslsnr: Veuillez patienter...
Failed to start service, error 3.
TNS-12560: TNS : erreur d'adaptateur de protocole
TNS-00530: Erreur d'adaptateur de protocoleEven if I stop the 10g listener I can't start the 11g listener. I also tried to start a default listener with 11g (name=listener and port=1521) but I get the same error.
Please, can someone explain me the reason of such error ?

C:\ora111\BIN>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
ANT_HOME=U:\eclipse\plugins\org.apache.ant_1.7.0.v200706080842
CLIENTNAME=Console
CommonProgramFiles=C:\Program Files\Fichiers communs
COMPUTERNAME=T0009696
ComSpec=C:\WINDOWS\system32\cmd.exe
ECLIPSE_HOME=C:\Program Files\Eclipse
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
JAVA_HOME=U:\JDK
JMS_ADAPTER=ActiveMQJMS
JMS_SERVERURL=tcp://SRV-JMS:61616
LOGONSERVER=\\SRV-46-CORP1
MSDevDir=C:\msdev\Common\MSDev98
NUMBER_OF_PROCESSORS=2
ORACLE_HOME=C:\ora111
oracle_sid=ubix11
OS=Windows_NT
Path=C:\ora111\bin;C:\ora111\bin;C:\ora102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Prog
ram Files\Fichiers communs\Adaptec Shared\System;c:\uti\exew32;c:\Perforce;c:\uti;C:\WINDOWS\system32\WindowsP
owerShell\v1.0;C:\Sun\SDK\bin;C:\Program Files\EclipsePATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
;.PSC1
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1
PERL5LIB=C:\ora102\perl\lib\5.8.3\MSWin32-x86;C:\ora102\perl\lib\5.8.3;C:\ora102\perl\5.8.3\lib\MSWin32-x86-mu
lti-thread;C:\ora102\perl\site\5.8.3;C:\ora102\perl\site\5.8.3\lib;C:\ora102\sysman\admin\scripts
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 75 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=4b02
ProgramFiles=C:\Program Files
PROMPT=$P$G
PYDEVHOME=C:\Program Files\Eclipse\plugins\org.python.pydev.debug_1.3.13\pysrc
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
tns_admin=C:\ora111\network\admin
UBIXDEV_DRIVE=U
USERDNSDOMAIN=CORP.GLTRADE.COM
USERDOMAIN=CORP
USERNAME=EMB
UTI=c:\uti
Vs6CommonDir=c:\msdev
windir=C:\WINDOWS

11g Database Upgrade

Hello,
I was going over the upgrade documention.
When upgrading to 11g from 10.2 database.
The 11g database software is installed in a new oracle_home than run the upgrade DBUA from that new 11g home
and upgrade the 10.2 database oracle_home ?
Is this the correct procedure for upgrading to 11g ?
Thanks

Upgrade process consists of two broad steps -
1. Install the new version of the software in a separate/new ORACLE_HOME
2. Upgrade any databases in the older ORACLE_HOME
>
1) Do I install the 11g software only or the started DB and then do the upgrade.
I woud have 3 running DB if i did this.
>
All of the steps are documented in the Upgrade Guide at http://download.oracle.com/docs/cd/B28359_01/server.111/b28300/toc.htm
Any reason you have chosen 11gR1 instead of 11gR2, which is the newest version ?
>
2) The OUI throws errors that my paths LD_library and oracle _home is already used.
How do I set this prior to installing the 11g software ?
>
You haven't posted enough details of what you did, but I suspect you are trying to install the 11gR1 software in the 10g ORACLE_HOME, which cannot be done. You will need to install in a new/separate ORACLE_HOME - see http://download.oracle.com/docs/cd/B28359_01/install.111/b32002/toc.htm
>
3) I am alos using a listener from my other 10g oracle_home and not the one I am upgrading.
Do I need to use the 11g listener and stop my 10g listener and copy my files into the 11g listener ?
>
The recommended approach is to use the latest (11gr1 in your case) listener for all oracle databases. As you stated, you will need to stop your 10g listener, configure the 11g listener for your databases and bring up the 11g listener.
HTH
Srini

Listener.log archiving

What is the suggested technique for archiving the listener.log contents in 11g?
I've been rolling out old listener.log files since oracle 7 with the following logic:
set log_file new_file_name
mv old_file_name to archive_file_name
set log_file listener.log
In 11g I get a tns-1251 with the set log_file lsnrctl cmd,
01251, 00000, "Cannot set trace/log directory under ADR"
// *Cause: ADR trace and log directories cannot be set by the user.
// *Action: None.

As the error message indicates 11g introduced a new diagnosability system,the Automatic Diagnostic Repository (ADR).
Concerning the listener,now you have additionally to listener.log a corresponding xml-file. See these 2 metalink notes, how to deal with ADR:
Using and Disabling the Automatic Diagnostic Repository (ADR) with Oracle Net for 11g Doc ID: Note:454927.1
11g Diagnosability: Frequently Asked Questions Doc ID: Note:453125.1
Werner

Enabling sqlnet tracing on client

Hi,
on 8.1.7 on a win 2003 server which is an oracle client , I want to enable sqlplus tracking by adding the followin in sqlnet.ora file :
TRACE_LEVEL_CLIENT = 16
TRACE_FILE_CLIENT = cli
TRACE_DIRECTORY_CLIENT = e:\tempShould I stop/start something in order that tarcking be effectively done ?
And also when I want to stop that after deleting these lines from sqlnet.ora file ,Should I stop/start something in order that tarcking be effectively stopped ?
Thanks and regards.

SQL*Net tracing is controlled by setting SQL*Net control file parameters in your SQLNET.ORA and LISTENER.ORA control files. For example, starting and stopping SQL*Net client tracing is done by setting the SQLNET.ORA parameter, TRACE_LEVEL_CLIENT, to one of the following values: OFF, USER, or ADMIN. The default value for this parameter is OFF. Setting the value to USER will start user-level tracing for SQL*Net client processes, which generates English sentences describing significant client networking events. Similarly, starting and stopping SQL*Net listener tracing is done by setting the LISTENER.ORA parameter, TRACE_LEVEL_LISTENER, to one of the following values: OFF, USER, or ADMIN.

Listener tracing in 11g

Similar Messages

Maybe you are looking for