Listener TRACE

Hi,
I wanted to track the (malicious) HOSTNAME conneted to the Oracle database server and for that purpose (only) I started listener tracing. I added the following parameters for this purporse in the listener.ora file. As show below:
LISTENER.ORA:
TRACE_DIRECTORY_LISTENER=$ORACLE_HOME/network/trace
TRACE_FILE_LISTENER=hosttrack.trc            # name of the file to be created
TRACE_LEVEL_LISTENER=USER                    # only user level trace required in my case.
TRACE_FILELEN_LISTENER=500                  # size of file in KB
TRACE_FILENO_LISTENER=10                     # Total no. of files used, after that it wil overwriteDatabase: 10g (10.2.0.04), OS=RH Linux Asm Instannce 11 (production DB).
I have used RELOAD the listener after adding above paramters, but I am not able to see the hosttrack.trc file which should be created at the specified location (though it is supposed to be the default location). I didn't see any change. One thing which I did just to see the effect was > lsnrctl trace 4
and after this I found a new line after the lsnrctl status command, i.e.,
Listener Trace File /oracle/diag/tnslsnr/db1/listener/trace/ora_16569_47913942631504.trc
My question is where hosttrac.trc trace file has gone, is it working the way I wanted it or there is something wrong?.
Thanks a lot.
B-R

Hi,
[oracle@db1 ~]$ production
[oracle@db1 ~]$ lsnrctl status
LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 16-FEB-2012 14:49:48
Listener Parameter File   /oracle/product/11.2.0/grid/network/admin/listener.ora
Listener Log File         /oracle/diag/tnslsnr/db1/listener/alert/log.xml
Listener Trace File       /oracle/diag/tnslsnr/db1/listener/trace/ora_16569_47913942631504.trc
[oracle@db1 ~]$ asm
[oracle@db1 ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 16-FEB-2012 14:50:45
Listener Parameter File   /oracle/product/11.2.0/grid/network/admin/listener.ora
Listener Log File         /oracle/diag/tnslsnr/db1/listener/alert/log.xml
Listener Trace File       /oracle/diag/tnslsnr/db1/listener/trace/ora_16569_47913942631504.trcI have added parameters in this file /oracle/product/11.2.0/grid/network/admin/listener.ora to ENABLE LISTENER TRACING.
Regards,

Similar Messages

  • Tnslsnr.exe crashes 9i (9.0.1.1) on Windows 2000  anyone speak listener trace?

    I'm running 9i (9.0.1.1) on Windows 2000 Professional tnslsnr.exe crashes as soon as it is accessed.
    Here is an example of what happens when I use tnsping with listener trace on.
    Can anyone speak listener trace and tell me what is wrong?
    C:\>tnsping odb1 5
    TNS Ping Utility for 32-bit Windows: Version 9.0.1.1.1 - Production on 05-MAY-20
    02 06:40:10
    Copyright (c) 1997 Oracle Corporation. All rights reserved.
    Used parameter files:
    C:\oracle\ora90\network\admin\sqlnet.ora
    C:\oracle\ora90\network\admin\tnsnames.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = MYLAPTO
    P) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = ODB1)))
    OK (4450 msec)
    TNS-12547: TNS:lost contact
    C:\>
    Then I get a Program error dialog box
    ! TNSLSNR.exe has generated errors and will be closed by Windows. You will need to restart the program.
    An error log is bein created.
    here is my listener.ora
    # LISTENER.ORA Network Configuration File: C:\oracle\ora90\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = MYLAPTOP)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_DESC =
    (GLOBAL_DBNAME = ODB1)
    (ORACLE_HOME = C:\oracle\ora90)
    (SID_NAME = ODB1)
    here is my tnsnames.ora
    ODB1=(DESCRIPTION =
    (ADDRESS =
    (PROTOCOL = TCP)
    (HOST = MYLAPTOP)
    (PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = ODB1)
    here is the listener.trc run at level 4
         TNSLSNR for 32-bit Windows: Version 9.0.1.1.1 - Production on 02-MAY-2002 21:37:32
         Copyright (c) 1991, 2001, Oracle Corporation. All rights reserved.
         --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
         New trace stream is C:\oracle\ora90\network\trace\listener.trc
         New trace level is 4
         --- TRACE CONFIGURATION INFORMATION ENDS ---
         --- PARAMETER SOURCE INFORMATION FOLLOWS ---
         Attempted load of system pfile source C:\oracle\ora90\network\admin\listener.ora
         Parameter source loaded successfully
         Attempted load of command line source
         Parameter source was not loaded
         -> PARAMETER TABLE LOAD RESULTS FOLLOW <-
         Successful parameter table load
         -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <-
         LISTENER = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = MYLAPTOP)(PORT = 1521)))
         SID_LIST_LISTENER = (SID_DESC = (GLOBAL_DBNAME = ODB1) (ORACLE_HOME = C:\oracle\ora90) (SID_NAME = ODB1))
         TRACE_LEVEL_LISTENER = USER
         --- PARAMETER SOURCE INFORMATION ENDS ---
         --- LOG CONFIGURATION INFORMATION FOLLOWS ---
         Log stream will be "C:\oracle\ora90\network\log\listener.log"
         Log stream validation requested
         Log stream is valid
         --- LOG CONFIGURATION INFORMATION ENDS ---
         nsglldprm: Resolved "STARTUP_WAIT_TIME_LISTENER" to: 0
         nsglma: Listener's pid=712
         nttgetport: port resolved to 1521
         nttbnd2addr: looking up IP addr for host: MYLAPTOP
         nttcnp: Validnode Table IN use; err 0x0
         nsopen: opening transport...
         nttcnp: Validnode Table IN use; err 0x0
         nttcnp: getting sockname
         nsopen: transport is open
         nsopen: global context check-in (to slot 0) complete
         nsgllsn: completing partial addr: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MYLAPTOP)(PORT=1521)))
         nsgllsn: Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MYLAPTOP)(PORT=1521)))
         nsopen: opening transport...
         nsopen: transport is open
         nsopen: global context check-in (to slot 1) complete
         nsopen: opening transport...
         nttcnp: Validnode Table IN use; err 0x0
         nttcnp: getting sockname
         nttcnr: waiting to accept a connection.
         nttcnr: getting sockname
         nttvlser: valid node check on incoming node 127.0.0.1
         nttvlser: Accepted Entry: 127.0.0.1
         nttcon: set TCP_NODELAY on 336
         nsopen: transport is open
         nsnainit: inf->nsinfflg[0]: 0xd inf->nsinfflg[1]: 0xd
         nsopen: global context check-in (to slot 2) complete
         nsanswer: deferring connect attempt; at stage 5
         ntt2err: soc 336 error - operation=5, ntresnt[0]=524, ntresnt[1]=997, ntresnt[2]=0
         nscon: doing connect handshake...
         nscon: got NSPTCN packet
         nsevdansw: exit
         nscon: sending NSPTAC packet
         nscon: doing connect handshake...
         nscon: nsctxinf[0]=0x4d, [1]=0x9
         nsconbrok: asking transport to enable NTOBROKEN
         ntt2err: soc 336 error - operation=5, ntresnt[0]=524, ntresnt[1]=997, ntresnt[2]=0
         nsevdansw: exit
         nsdo: 516 bytes from NS buffer
         ntt2err: soc 336 error - operation=5, ntresnt[0]=524, ntresnt[1]=997, ntresnt[2]=0
         nsglgrDoRegister: Creating new instance: "odb1".
         nsglgrDoRegister: Creating new handler: "DEDICATED".
         nsdo: 188 bytes to NS buffer
         nsdo: 248 bytes from NS buffer
         ntt2err: soc 336 error - operation=5, ntresnt[0]=524, ntresnt[1]=997, ntresnt[2]=0
         nsdo: 116 bytes to NS buffer
         nsopen: opening transport...
         nttcnp: Validnode Table IN use; err 0x0
         nttcnp: getting sockname
         nttcnr: waiting to accept a connection.
         nttcnr: getting sockname
         nttvlser: valid node check on incoming node 127.0.0.1
         nttvlser: Accepted Entry: 127.0.0.1
         nttcon: set TCP_NODELAY on 316
         nsopen: transport is open
         nsnainit: inf->nsinfflg[0]: 0xd inf->nsinfflg[1]: 0xd
         nsopen: global context check-in (to slot 3) complete
         nsanswer: deferring connect attempt; at stage 5
         ntt2err: soc 316 error - operation=5, ntresnt[0]=524, ntresnt[1]=997, ntresnt[2]=0
         nscon: doing connect handshake...
         nscon: got NSPTCN packet
         nsevdansw: exit
         nscon: sending NSPTRF packet
         ntt2err: soc 316 error - operation=5, ntresnt[0]=524, ntresnt[1]=997, ntresnt[2]=0
         nstimarmed: no timer allocated
         nsclose: closing transport
         nsclose: global context check-out (from slot 3) complete
         nsglecmd: Deallocating cxd 0x13dffa0.

    Hi,
    I don't know too much about this to be honest but I have some suggestions so I'll throw my two cents worth in. A few things come to mind, first I'd check the client, the issue looks like its there, second check the local security setup and third if your using Active Directory there are special directory issues.
    Hope this helps

  • Listener trace file: Winsock 54 errors

    I am seeing many of the following error ("soc nnn error - operation=5, ntresnt[0]=517, ntresnt[1]=54...") in my Listener trace file.
    This is on an Oracle 9.2.0.4 server (Windows 2003 Server R2).
    If my intepretation of the Listener trace is correct, this corresponds to Winsock Error 10054 (Connection reset by peer).
    SQL*net trace files at the client side (a separate host) do not indicate a corresponding error - all the trace files appear "clean".
    So what is the peer in this context? My initial thought was that the Oracle server had established a session for the client, but then the client
    had appeared to disappear from the network. But I would have expected to see something in the client trace files at the same time.
    This is an example from the Listener trace file.
    nscon: sending NSPTRD packet
    nspsend: entry
    nspsend: plen=65, type=5
    nttmwr: entry
    nttmwr: socket 332 had bytes written=65
    nttmwr: exit
    nspsend: 65 bytes to transport
    nspsend: packet dump
    nspsend: 00 41 00 00 05 00 00 00 |.A......|
    nspsend: 00 37 28 41 44 44 52 45 |.7(ADDRE|
    nspsend: 53 53 3D 28 50 52 4F 54 |SS=(PROT|
    nspsend: 4F 43 4F 4C 3D 74 63 70 |OCOL=tcp|
    nspsend: 29 28 48 4F 53 54 3D 31 |)(HOST=1|
    nspsend: 39 32 2E 31 36 38 2E 32 |92.168.2|
    nspsend: 2E 32 35 34 29 28 50 4F |.254)(PO|
    nspsend: 52 54 3D 34 34 35 37 29 |RT=4457)|
    nspsend: 29 |) |
    nspsend: normal exit
    nscon: exit (0)
    nsdo: nsctxrnk=0
    nsdo: normal exit
    nsrah: entry
    nsrah: reading (asynchronously) from transport...
    nsrah: ...into overflow area...
    nttmrd: entry
    ntt2err: entry
    ntt2err: soc 332 error - operation=5, ntresnt[0]=517, ntresnt[1]=54, ntresnt[2]=0
    ntt2err: exit
    ntt2err: entry
    ntt2err: Read unexpected EOF ERROR on 332
    ntt2err: exit
    nttmrd: socket 332 had bytes read=0
    nttmrd: exit
    nserror: entry
    nserror: nsres: id=4, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
    nsrah: exit (-1)
    nsclose: entry
    nstimarmed: entry
    nstimarmed: no timer allocated
    nstimarmed: normal exit
    Any thoughts/recommendations on this would be gratefully received, thanks.
    Andy.

    nspsend: 4F 43 4F 4C 3D 74 63 70 |OCOL=tcp|
    nspsend: 29 28 48 4F 53 54 3D 31 |)(HOST=1|
    nspsend: 39 32 2E 31 36 38 2E 32 |92.168.2|
    nspsend: 2E 32 35 34 29 28 50 4F |.254)(PO|
    nspsend: 52 54 3D 34 34 35 37 29 |RT=4457)|
    So what is the peer in this context?192.168.2.245 port=4457
    go to http://download.oracle.com/docs/cd/B10501_01/network.920/a96580/troubles.htm
    then Find: EOF ERROR

  • NET8의 LOGGING과 TRACE 관련 PARAMETER에 대한 Q & A

    제품 : SQL*NET
    작성날짜 : 2002-05-07
    NET8의 LOGGING과 TRACE 관련 PARAMETER에 대한 Q & A
    =================================================
    PURPOSE
    Net8을 이용하면서 발생하는 문제를 추적 하기위해 oracle의 configuration
    file에 들어갈 수 있는 parameter와 logging과 tracing을 하는 방법에 대해
    질의/응답을 통해 알아 보도록 한다.
    Explanation
    1) NET8에서 trace를 사용하는 이유와 어떤 component들에 trace를 할 수 있나?
    Trace의 특징은 네트워크을 수행하게 될때 network event들을 기술한다
    즉 trace와 관련된 일련의 문장들이 자세하게 생성된다.
    "Tracing"의 운영으로 log파일에 제공되어 있는 것 보다 NET8의 component들의
    내부적인 정보를 보다 많이 얻을 수 있다.
    이러한 정보는 에러의 결과로 인하여 발생하는 동일한 event들로 파일들에
    결과가 생성되어 이를 이용하여 문제의 원인을 판단할 수 있다.
    주의 : trace의 기능을 이용하는 경우 충분한 disk space와 system performance의
    현격한 저하를 가져올 수 있다 즉 trace의 기능은 반드시 필요할
    경우에만 사용할 것을 권한다.
    << trace의 기능을 이용하여 trace를 할 수 있는 component들 >>
    * Network listener
    * Net8 components on the client and server
    * Connection Manager
    * Oracle Names Server
    * Oracle Names Control Utility
    * TNSPING utility
    2) 어떤 parameter들을 설정하면 trace 기능을 이용할 수 있는가 ?
    tracing을 하기 위해서는 특정 trace parameter들을 설정함으로써 가능하며
    아래에 주어진 방법들과 또는 utility들중 하나를 선택하여 설정함으로써
    사용할 수 있다.
    * Component Configuration Files
    * Component Control Utilities
    * Oracle Trace
    component의 configuration 파일을 이용하여 traceing parameter를 설정하려면
    1.component의 configuration 파일에 다음의 traceing parameter를 설정한다.
    - SQLNET.ORA for client or server, LISTENER.ORA for listener:
    TRACE_LEVEL_<CLIENT/LISTENER/SERVER>=(0/4/10/16)
    TRACE_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    LOG_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    2.만일 component들이 수행중인 동안 configuration 파일의 수정이 있었다면
    병경된 parameter들을 사용하기 위해 component들을 다시 시작하여야 한다.
    component control utility들을 이용하여 trace parameter들을 설정하려면
    1. listener의 경우, Listener Control Utility(lsnrctl)에서 TRACE 명령어를
    이용하여 listener가 수행중인 동안에도 trace level을 설정할 수 있다.
    EX)
         RC80:/mnt3/rctest80> lsnrctl
         LSNRCTL for SVR4: Version 8.0.4.0.0 - Production on 01-SEP-98 15:16:52
         (c) Copyright 1997 Oracle Corporation. All rights reserved.
         Welcome to LSNRCTL, type "help" for information.
         LSNRCTL> trace admin
         Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
         Opened trace file: /mnt4/coe/app/oracle/product/8.0.4/network/trace/
    lsnr_coe.trc
         The command completed successfully
         LSNRCTL> trace off
         Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
         The command completed successfully
         LSNRCTL> exit
         RC80:/mnt3/rctest80>
    2. Oracle Names의 경우, Names Control Utility(namesctl)에서 TRACE_LEVEL
    명령어를 이용하여 Oracle Names가 수행중인 동안에도 trace level을
    설정할 수 있다.
    주의 : Connection Manager의 경우, trace level은 configuration 파일인 CMAN.ORA
    에서만 설정할 수 있다.
    Oracle Enterprose manager(이하 OEM)에 있는 Oracle Trace는 trace parameter들을
    설정하고 GUI를 통해 trace data의 형태를 볼수 있도록 하는 tracing tool이다.
    3) trace된 data를 해석할 수 있는 다른 utility들이 있다면 ?
    Trace Assistant를 사용하면 사용자의 *.trc 파일 (SQL*Net v2의 형식에 의해
    생성된) 또는 *.txt (Orace Trace 과 TRCFMT에 의해 생성된 출력물)을 통해
    trac된 정보를 해석할 수 있다.
    이 유틸리티 네트워크의 문제들로 인해 발생하는 문제점들을 진단하고
    해결하는 데 보다 많은 정보를 제공하여 사용자의 이해를 돕는다.
    * the source and destination of trace files
    * the flow of packets between network nodes
    * which component of Net8 is failing
    * pertinent error codes
    다음에 주어진 명령어를 수행하므로써 Trace Assistant 실행할 수 있다.
    trcasst [options] <filename>
    Trace Assistant Text Formatting Options
    -o Displays connectivity and Two Task Common (TTC) information.
    After the -o the following options may be used:
    c (for summary connectivity information)
    d (for detailed connectivity information)
    u (for summary TTC information)
    t (for detailed TTC information)
    q (displays SQL commands enhancing summary TTC information)
    -p Oracle Internal Use Only
    -s Displays statistical information
    -e Enables display of error information After the -e, zero
    or one error decoding level may follow:
    0 or nothing : translates the NS error numbers dumped from the
    nserror function plus lists all other errors
    1 : displays only the NS error translation from the nserror function
    2 : displays error numbers without translation
    만일 option들이 제공되지 않는다면 기본적으로 -odt -e -s가 지정되어 자세한
    connectivity, Two-Task Common, 에러 level 0 그리고 통계정보들이 tracing 된다.
    4) SQL*Net v2 tracing과 어떻게 다른가 ?
    Net8 tracing에서는 이전 버전인 SQL*NET V2에서 제공 되는 모든 option을
    포함하고 있고 Oracle Trace의 기능이 추가되었다.
    이것은 Oracle Trace Repository를 OEM 콘솔을 통하여 사용자의 trace 정보를
    관리할 수 있도록 허용한다.
    5) *.cdf와 *.dat은 어떤 파일 인가 ?
    *.cdf 와 *.dat 파일들은 Oracle Trace에 의해 생성되는 파일들로서 이 파일들을
    읽기 위해서는 반드시 trcfmt utility를 이용해야만 한다.
    trcfmt는 binary (*.dat와 *.cdf의 확장자) 파일내에 있는 data를
    일반 text(.txt의 확장자)로 정보를 추출한다. 이 tool을 사용하기 위해서는
    다음의 명령어를 이용하면 된다.
    trcfmt collection.cdf
    주의 : .cdf와 .dat파일이 존재하는 디렉토리가 아닌 곳에서 이 tool을 이용
         한다면 path가 포함되야 한다. 만일 하나의 .cdf 와 .dat 파일들내에
         여러 프로세스들의 tracing정보가 수집된다면 그것들은 process_id.txt의
    이름과 함께 파일이 추출될 것이다.
    6) trac관련 configuration은 어떤 것이 있으며 설정할 수 있는 parameter는
    무엇이 있는가 ?
    ==========================================================================
    || SQLNET.ORA Parameters ||
    ==========================================================================
    DAEMON.TRACE_DIRECTORY
    Purpose: Controls the destination directory of the Oracle
    Enterprise Manager daemon trace file
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_DIRECTORY=/oracle/traces
    DAEMON.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level for
    the Oracle Enterprise Manager daemon.
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_LEVEL=10
    DAEMON.TRACE_MASK
    Purpose: Specifies that only the Oracle Enterprise Manager daemon
    trace entries are logged into the trace file.
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_MASK=(106)
    LOG_DIRECTORY_CLIENT
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_CLIENT=/oracle/network/trace
    LOG_DIRECTORY_SERVER
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Valid in File: SQLNET.ORA
    Example: LOG_DIRECTORY_SERVER=/oracle/network/trace
    LOG_FILE_CLIENT
    Purpose: Controls the log output filename for an Oracle client.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_CLIENT=client
    LOG_FILE_SERVER
    Purpose: Controls the log output filename for an Oracle server.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_SERVER=svr
    NAMESCTL.TRACE_LEVEL
    Purpose: Indicates the level at which the NAMESCTL program should
    be traced.
    Default Value: OFF
    Values: OFF, USER, or ADMIN
    Example: NAMESCTL.TRACE_LEVEL=ADMIN
    NAMESCTL.TRACE_FILE
    Purpose: Indicates the file in which the NAMESCTL trace output is
    placed.
    Default Value: namesctl_PID.cdf and namesctl_PID.dat
    Example: NAMESCTL.TRACE_FILE=NMSCTL
    NAMESCTL.TRACE_DIRECTORY
    Purpose: Indicates the directory where trace output from the NAMESCTL
    utility is placed.
    Default
    Value: $ORACLE_HOME/network/trace
    Example: NAMESCTL.TRACE_DIRECTORY=/ORACLE/TRACE
    NAMESCTL.TRACE_UNIQUE
    Indicates whether a process identifier is appended to the
    Purpose: name of each trace file generated, so that several can
    coexist.
    Default
    Value: OFF
    Values: OFF or ON
    Example: NAMESCTL.TRACE_UNIQUE = ON
    TNSPING.TRACE_DIRECTORY
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TNSPING.TRACE_DIRECTORY=/oracle/traces
    TNSPING.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TNSPING.TRACE_LEVEL=10
    TRACE_DIRECTORY_CLIENT
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_CLIENT=/oracle/traces
    TRACE_DIRECTORY_SERVER
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_SERVER=/oracle/traces
    TRACE_FILE_CLIENT
    Purpose: Controls the name of the client trace file
    Default Value: SQLNET.CDF and SQLNET.DAT
    Example: TRACE_FILE_CLIENT=cli
    TRACE_FILE_SERVER
    Purpose: Controls the name of the server trace file
    Default Value: SVR_PID.CDF and SVR_PID.DAT
    Example: TRACE_FILE_SERVER=svr
    TRACE_LEVEL_CLIENT
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_CLIENT=10
    TRACE_LEVEL_SERVER
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_SERVER=10
    TRACE_UNIQUE_CLIENT
    Used to make each client trace file have a unique name to
    Purpose: prevent each trace file from being overwritten with the next
    occurrence of the client. The PID is attached to the end of
    the filename.
    Default
    Value: OFF
    Example: TRACE_UNIQUE_CLIENT=ON
    USE_CMAN
    If the session is in an Enhanced Discovery Network with a
    Purpose: Names Server, this parameter forces all sessions to go
    through a Connection Manager to get to the server.
    Default
    Value: FALSE
    Values: TRUE or FALSE
    Example: USE_CMAN=TRUE
    ==========================================================================
    || LISTENER.ORA Parameters ||
    ==========================================================================
    LOG_DIRECTORY_listener_name
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_LISTENER=/oracle/traces
    LOG_FILE_listener_name
    Purpose: Specifies the filename where the log information is
    written
    Default Value: listener_name.log
    Example: LOG_FILE_LISTENER=lsnr
    TRACE_DIRECTORY_listener_name
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_LISTENER=/oracle/traces
    TRACE_FILE_listener_name
    Purpose: Controls the name of the listener trace file
    Default Value: LISTENER_NAME.CDF and LISTENER_NAME.DAT
    Example: TRACE_FILE_LISTENER=lsnr
    TRACE_LEVEL_listener_name
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 - WorldWide Customer Support trace information
    Example: TRACE_LEVEL_LISTENER=10
    ==========================================================================
    || NAMES.ORA Parameters ||
    ==========================================================================
    NAMES.TRACE_DIRECTORY
    Purpose: Indicates the name of the directory to which trace files
    from a Names Server trace session are written.
    Default
    Value: platform specific
    Example: names.trace_directory = complete_directory_name
    NAMES.TRACE_FILE
    Purpose: Indicates the name of the output file from a Names Server
    trace session. The filename extension is always.trc
    Default
    Value: names
    Example: names.trace_file = filename
    NAMES.TRACE_LEVEL
    Purpose: Indicates the level at which the Names Server is to be
    traced.
    Default Value: OFF
    Example: names.trace_level = OFF
    NAMES.TRACE_UNIQUE
    indicates whether each trace file has a unique name, allowing
    Purpose: multiple trace files to coexist. If the value is set to ON, a
    process identifier is appended to the name of each trace file
    generated.
    Default
    Value: OFF
    Example: names.trace_unique = ON
    names.trace_file = names_05.trc
    ==========================================================================
    CMAN.ORA Parameters
    ==========================================================================
    TRACING
    Default
    Value: NO
    Example: TRACING = NO
    References
    7) listener.log 파일에 loggin정보를 남기지 않게 하는 방법이 있나요 ?
    고객이 개발하여 사용중인 application에서 NET8을 이용하여 접속하거나 접속을
    종료하는 경우 listener.log에 이와 관련된 정보가 남으며, 수 많흔 사용자가
    접속을 하게되므로서 급속하게 listener.log 파일이 커져 file system이 꽉
    차거나 데이터베이스가 hang이 되는 결과를 초래하는 경우가 있다.
    고객들은 listener.log에 write할수 있는 메세지의 양에 제한을 두기를 원하는
    경우가 있으나 이러한 기능은 제공되지 않는다. 하지만 listener의 logging은
    on 또는 off를 할 수는 있다.
    Net8에서는 listener.ora에 "LOGGING_(the listener name)=off"를 설정하게 되면
    listener의 logging을 멈출 수 있다.
    ** SQL*NET 2.3.x 에서도 이 parameter가 유효한가요 ? **
    물론 사용이 가능합니다. NET8에서 사용하는 것과 동일하게 parameter를
    listener.ora에 설정함으로서 가능합니다.
    EX)
    LOGGING_LISTENER=OFF
    이 parameter는 listener의 전체 logging을 disable하는 parameter로 일부만
    여과하여 logging할 수 있는 기능은 아니다.
    이 parameter는 NET8에 알려진 parameter로 SQL*NET 2.3.x manuals에 나와
    있지는 않지만 정상적으로 사용할 수 있다.
    Reference Ducumment
    ---------------------

  • NET8의 LOGGING AND TRACE관련 PARAMETER에 대한 Q & A

    제품 : SQL*NET
    작성날짜 : 1999-07-30
    NET8의 LOGGING AND TRACE관련 PARAMETER에 대한 Q & A
    ==================================================
    PURPOSE
    NET8의 LOGGING AND TRACE관련 PARAMETER에 대해 알아 보도록한다
    Explanation
    1. NET8에서 trace를 왜 사용하고 어떤 component들에 trace를 할 수 있나요 ?
    Trace의 특징은 네트워크을 수행하게 될때 network event들을 기술한다
    즉 trace와 관련된 일련의 문장들이 자세하게 생성된다.
    "Tracing"의 운영으로 log파일에 제공되어 있는 것 보다 NET8의 component들의
    내부적인 정보를 보다 많이 얻을 수 있다.
    이러한 정보는 에러의 결과로 인하여 발생하는 동일한 event들로 파일들에
    결과가 생성되어 이를 이용하여 문제의 원인을 판단할 수 있다.
    주의 : trace의 기능을 이용하는 경우 충분한 disk space와 system
    performance의 현격한 저하를 가져올 수 있다.
    즉 trace의 기능은 반드시 필요할 경우에만 사용할 것을 권한다.
    Example
    Reference Ducumment
    << trace의 기능을 이용하여 trace를 할수 있는 component들 >>
    * Network listener
    * Net8 components on the client and server
    * Connection Manager
    * Oracle Names Server
    * Oracle Names Control Utility
    * TNSPING utility
    2. 어떤 parameter들을 설정하면 trace 기능을 이용할 수 있는가 ?
    tracing을 하기 위해서는 특정 trace parameter들을 설정함으로써 가능하며
    아래에 주어진 방법들과 또는 utility들중 하나를 선택하여 설정함으로써
    사용할 수 있다.
    * Component Configuration Files
    * Component Control Utilities
    * Oracle Trace
    component의 configuration 파일을 이용하여 traceing parameter를 설정하려면
    1) component의 configuration 파일에 다음의 traceing parameter를 설정한다.
    - SQLNET.ORA for client or server, LISTENER.ORA for listener:
    TRACE_LEVEL_<CLIENT/LISTENER/SERVER>=(0/4/10/16)
    TRACE_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    LOG_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    2) 만일 component들이 수행중인 동안 configuration 파일의 수정이 있었다면
    변경된 parameter들을 사용하기 위해 component들을 다시 시작하여야 한다.
    component control utility들을 이용하여 trace parameter들을 설정하려면
    1) listener의 경우, Listener Control Utility(lsnrctl)에서 TRACE 명령어를
    이용하여 listener가 수행중인 동안에도 trace level을 설정할 수 있다.
    EX)
    RC80:/mnt3/rctest80> lsnrctl
    LSNRCTL for SVR4: Version 8.0.4.0.0 - Production on 01-SEP-98 15:16:52
    (c) Copyright 1997 Oracle Corporation. All rights reserved.
    Welcome to LSNRCTL, type "help" for information.
    LSNRCTL> trace admin
    Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
    Opened trace file: /mnt4/coe/app/oracle/product/8.0.4/network/trace/
    lsnr_coe.trc
    The command completed successfully
    LSNRCTL> trace off
    Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
    The command completed successfully
    LSNRCTL> exit
    RC80:/mnt3/rctest80>
    2) Oracle Names의 경우, Names Control Utility(namesctl)에서 TRACE_LEVEL
    명령어를 이용하여 Oracle Names가 수행중인 동안에도 trace level을
    설정할 수 있다.
    주의 : Connection Manager의 경우, trace level은 configuration 파일인
    CMAN.ORA 에서만 설정할 수 있다.
    Oracle Enterprose manager(이하 OEM)에 있는 Oracle Trace는 trace parameter
    들을 설정하고 GUI를 통해 trace data의 형태를 볼수 있도록 하는 tracing tool
    이다.
    3. Trace된 data를 해석할 수 있는 다른 utility들이 있다면 ?
    Trace Assistant를 사용하면 사용자의 *.trc 파일 (SQL*Net v2의 형식에 의해
    생성된) 또는 *.txt (Orace Trace 과 TRCFMT에 의해 생성된 출력물)을 통해
    trac된 정보를 해석할 수 있다.
    이 유틸리티 네트워크의 문제들로 인해 발생하는 문제점들을 진단하고
    해결하는 데 보다 많은 정보를 제공하여 사용자의 이해를 돕는다.
    * the source and destination of trace files
    * the flow of packets between network nodes
    * which component of Net8 is failing
    * pertinent error codes
    다음에 주어진 명령어를 수행하므로써 Trace Assistant 실행할 수 있다.
    trcasst [options] <filename>
    Trace Assistant Text Formatting Options
    -o Displays connectivity and Two Task Common (TTC) information.
    After the -o the following options may be used:
    c (for summary connectivity information)
    d (for detailed connectivity information)
    u (for summary TTC information)
    t (for detailed TTC information)
    q (displays SQL commands enhancing summary TTC
    information)
    -p Oracle Internal Use Only
    -s Displays statistical information
    -e Enables display of error information After the -e, zero
    or one error decoding level may follow:
    0 or nothing (translates the NS error numbers dumped
    from the nserror function plus lists all
    other errors)
    1 (displays only the NS error translation from
    the nserror function)
    2 (displays error numbers without translation)
    만일 option들이 제공되지 않는다면 기본적으로 -odt -e -s가 지정되어 자세한
    connectivity, Two-Task Common, 에러 level 0 그리고 통계정보들이 tracing
    된다.
    4. SQL*Net v2 tracing과 어떻게 다른가 ?
    Net8 tracing에서는 이전 버전인 SQL*NET V2에서 제공 되는 모든 option을
    포함하고 있고 Oracle Trace의 기능이 추가되었다.
    이것은 Oracle Trace Repository를 OEM 콘솔을 통하여 사용자의 trace 정보를
    관리할 수 있도록 허용한다.
    5. *.cdf와 *.dat은 어떤 파일 인가 ?
    *.cdf 와 *.dat 파일들은 Oracle Trace에 의해 생성되는 파일들로서 이 파일들을
    읽기 위해서는 반드시 trcfmt utility를 이용해야만 한다.
    trcfmt는 binary (*.dat와 *.cdf의 확장자) 파일내에 있는 data를 일반text
    (.txt의 확장자)로 정보를 추출한다. 이 tool을 사용하기 위해서는 다음의
    명령어를 이용하면 된다.
    $ trcfmt collection.cdf
    주의 : .cdf와 .dat파일이 존재하는 디렉토리가 아닌 곳에서 이 tool을 이용
    한다면 path가 포함되야 한다. 만일 하나의 .cdf 와 .dat 파일들내에
    여러 프로세스들의 traceing정보가 수집된다면 그것들은 process_id.txt
    의 이름과 함께 파일이 추출될 것이다.
    6. trac관련 configuration은 어떤 것이 있으며 설정할 수 있는 parameter는
    무엇이 있는가 ?
    ==========================================================================
    || SQLNET.ORA Parameters ||
    ==========================================================================
    DAEMON.TRACE_DIRECTORY
    Purpose: Controls the destination directory of the Oracle
    Enterprise Manager daemon trace file
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_DIRECTORY=/oracle/traces
    DAEMON.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level for
    the Oracle Enterprise Manager daemon.
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_LEVEL=10
    DAEMON.TRACE_MASK
    Purpose: Specifies that only the Oracle Enterprise Manager daemon
    trace entries are logged into the trace file.
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_MASK=(106)
    LOG_DIRECTORY_CLIENT
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_CLIENT=/oracle/network/trace
    LOG_DIRECTORY_SERVER
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Valid in File: SQLNET.ORA
    Example: LOG_DIRECTORY_SERVER=/oracle/network/trace
    LOG_FILE_CLIENT
    Purpose: Controls the log output filename for an Oracle client.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_CLIENT=client
    LOG_FILE_SERVER
    Purpose: Controls the log output filename for an Oracle server.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_SERVER=svr
    NAMESCTL.TRACE_LEVEL
    Purpose: Indicates the level at which the NAMESCTL program should
    be traced.
    Default Value: OFF
    Values: OFF, USER, or ADMIN
    Example: NAMESCTL.TRACE_LEVEL=ADMIN
    NAMESCTL.TRACE_FILE
    Purpose: Indicates the file in which the NAMESCTL trace output is
    placed.
    Default Value: namesctl_PID.cdf and namesctl_PID.dat
    Example: NAMESCTL.TRACE_FILE=NMSCTL
    NAMESCTL.TRACE_DIRECTORY
    Purpose: Indicates the directory where trace output from the NAMESCTL
    utility is placed.
    Default
    Value: $ORACLE_HOME/network/trace
    Example: NAMESCTL.TRACE_DIRECTORY=/ORACLE/TRACE
    NAMESCTL.TRACE_UNIQUE
    Indicates whether a process identifier is appended to the
    Purpose: name of each trace file generated, so that several can
    coexist.
    Default
    Value: OFF
    Values: OFF or ON
    Example: NAMESCTL.TRACE_UNIQUE = ON
    TNSPING.TRACE_DIRECTORY
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TNSPING.TRACE_DIRECTORY=/oracle/traces
    TNSPING.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TNSPING.TRACE_LEVEL=10
    TRACE_DIRECTORY_CLIENT
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_CLIENT=/oracle/traces
    TRACE_DIRECTORY_SERVER
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_SERVER=/oracle/traces
    TRACE_FILE_CLIENT
    Purpose: Controls the name of the client trace file
    Default Value: SQLNET.CDF and SQLNET.DAT
    Example: TRACE_FILE_CLIENT=cli
    TRACE_FILE_SERVER
    Purpose: Controls the name of the server trace file
    Default Value: SVR_PID.CDF and SVR_PID.DAT
    Example: TRACE_FILE_SERVER=svr
    TRACE_LEVEL_CLIENT
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_CLIENT=10
    TRACE_LEVEL_SERVER
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_SERVER=10
    TRACE_UNIQUE_CLIENT
    Used to make each client trace file have a unique name to
    Purpose: prevent each trace file from being overwritten with the next
    occurrence of the client. The PID is attached to the end of
    the filename.
    Default
    Value: OFF
    Example: TRACE_UNIQUE_CLIENT=ON
    USE_CMAN
    If the session is in an Enhanced Discovery Network with a
    Purpose: Names Server, this parameter forces all sessions to go
    through a Connection Manager to get to the server.
    Default
    Value: FALSE
    Values: TRUE or FALSE
    Example: USE_CMAN=TRUE
    ==========================================================================
    || LISTENER.ORA Parameters ||
    ==========================================================================
    LOG_DIRECTORY_listener_name
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_LISTENER=/oracle/traces
    LOG_FILE_listener_name
    Purpose: Specifies the filename where the log information is
    written
    Default Value: listener_name.log
    Example: LOG_FILE_LISTENER=lsnr
    TRACE_DIRECTORY_listener_name
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_LISTENER=/oracle/traces
    TRACE_FILE_listener_name
    Purpose: Controls the name of the listener trace file
    Default Value: LISTENER_NAME.CDF and LISTENER_NAME.DAT
    Example: TRACE_FILE_LISTENER=lsnr
    TRACE_LEVEL_listener_name
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 - WorldWide Customer Support trace information
    Example: TRACE_LEVEL_LISTENER=10
    ==========================================================================
    || NAMES.ORA Parameters ||
    ==========================================================================
    NAMES.TRACE_DIRECTORY
    Purpose: Indicates the name of the directory to which trace files
    from a Names Server trace session are written.
    Default
    Value: platform specific
    Example: names.trace_directory = complete_directory_name
    NAMES.TRACE_FILE
    Purpose: Indicates the name of the output file from a Names Server
    trace session. The filename extension is always.trc
    Default
    Value: names
    Example: names.trace_file = filename
    NAMES.TRACE_LEVEL
    Purpose: Indicates the level at which the Names Server is to be
    traced.
    Default Value: OFF
    Example: names.trace_level = OFF
    NAMES.TRACE_UNIQUE
    indicates whether each trace file has a unique name, allowing
    Purpose: multiple trace files to coexist. If the value is set to ON, a
    process identifier is appended to the name of each trace file
    generated.
    Default
    Value: OFF
    Example: names.trace_unique = ON
    names.trace_file = names_05.trc
    ==========================================================================
    CMAN.ORA Parameters
    ==========================================================================
    TRACING
    Default
    Value: NO
    Example: TRACING = NO
    References
    7. listener.log 파일에 loggin정보를 남기지 않게 하는 방법이 있나요 ?
    고객이 개발하여 사용중인 application에서 NET8을 이용하여 접속하거나 접속을
    종료하는 경우 listener.log에 이와 관련된 정보가 남으며, 수 많은 사용자가
    접속을 하게 되므로서 급속하게 listener.log 파일이 커져 $ORACLE_HOME이 있는
    file system이 꽉 차서 데이터베이스가 hang이 되는 결과를 초래하는 경우가 있다.
    고객들은 listener.log에 write할수 있는 메세지의 양에 제한을 두기를 원하는
    경우가 있으나 이러한 기능은 제공되지 않는다. 하지만 listener의 logging은
    ON 또는 OFF는 설정을 통해서 가능하다.
    Net8에서는 listener.ora에 "LOGGING_(the listener name)=off"를 설정하게
    되면 listener의 logging을 멈출 수 있다.
    물론 설정후 listener stop후 재기동을 하셔야 변경된 paramerter에 의해
    이 기능이 enable됩니다.
    참고 : SQL*NET 2.3.x 에서도 이 parameter가 유효한가요 ?
    물론 사용이 가능합니다. NET8에서 사용하는 것과 동일하게 parameter를
    listener.ora에 설정함으로서 가능합니다.
    EX)
    LOGGING_LISTENER=OFF
    이 parameter는 listener의 전체 logging을 disable하는 parameter로 일부만
    여과하여 logging할 수 있는 기능은 아니다.
    이 parameter는 NET8에 알려진 parameter로 SQL*NET 2.3.x manuals에 나와
    있지는 않지만 정상적으로 사용할 수 있다.

  • EM 10g - Listener does not show up on DB home, but is running. Why??

    Oracle Version          10.2.0.1.0
    Microsoft Windows Server 2003 R2 Server 5.2 Service Pack 2 (32-bit)
    LSNRCTL> start LISTENER
    Starting tnslsnr: please wait...
    TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
    System parameter file is D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Log messages written to D:\oracle\product\10.2.0\db_1\network\log\listener.log
    Trace information written to D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
    Start Date 22-OCT-2007 11:42:18
    Uptime 0 days 0 hr. 0 min. 5 sec
    Trace Level user
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Listener Log File D:\oracle\product\10.2.0\db_1\network\log\listener.log
    Listener Trace File D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
    Services Summary...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    ========================================================
    LSNRCTL> status LISTENER
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
    Start Date 22-OCT-2007 11:42:18
    Uptime 0 days 0 hr. 14 min. 8 sec
    Trace Level user
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Listener Log File D:\oracle\product\10.2.0\db_1\network\log\listener.log
    Listener Trace File D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
    Services Summary...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "orcl.us-as1.nti2.org" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "orclXDB.us-as1.nti2.org" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "orcl_XPT.us-as1.nti2.org" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    The command completed successfully
    ======================================================
    C:\Documents and Settings\pierrel>netstat -a
    Active Connections
    Proto Local Address Foreign Address State
    TCP us-as1:smtp us-as1.nti2.org:0 LISTENING
    TCP us-as1:http us-as1.nti2.org:0 LISTENING
    TCP us-as1:nntp us-as1.nti2.org:0 LISTENING
    TCP us-as1:epmap us-as1.nti2.org:0 LISTENING
    TCP us-as1:microsoft-ds us-as1.nti2.org:0 LISTENING
    TCP us-as1:nntps us-as1.nti2.org:0 LISTENING
    TCP us-as1:kpop us-as1.nti2.org:0 LISTENING
    TCP us-as1:1110 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1111 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1117 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1119 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1158 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1521 us-as1.nti2.org:0 LISTENING
    ==================================================
    init.ora
    # $Header: init.ora 25-jul-01.18:03:38 rajayar Exp $
    # Copyright (c) 1991, 2001, Oracle Corporation. All rights reserved. */
    # Example INIT.ORA file
    # This file is provided by Oracle Corporation to help you customize
    # your RDBMS installation for your site. Important system parameters
    # are discussed, and example settings given.
    # Some parameter settings are generic to any size installation.
    # For parameters that require different values in different size
    # installations, three scenarios have been provided: SMALL, MEDIUM
    # and LARGE. Any parameter that needs to be tuned according to
    # installation size will have three settings, each one commented
    # according to installation size.
    # Use the following table to approximate the SGA size needed for the
    # three scenarious provided in this file:
    # -------Installation/Database Size------
    # SMALL MEDIUM LARGE
    # Block 2K 4500K 6800K 17000K
    # Size 4K 5500K 8800K 21000K
    # To set up a database that multiple instances will be using, use the
    # same file for all instance. Place all instance-specific parameters
    # at the end of the file using the <sid>.<parameter_name> = <value> syntax.
    # This way, when you change a public
    # parameter, it will automatically change on all instances. This is
    # necessary, since all instances must run with the same value for many
    # parameters. For example, if you choose to use private rollback segments,
    # these must be specified differently for each instance, but since all gc_*
    # parameters must be the same on all instances, they should be in one file.
    # INSTRUCTIONS: Edit this file and the other INIT files it calls for
    # your site, either by using the values provided here or by providing
    # your own.
    # replace "clustdb" with your database name
    db_name = clustdb
    compatible=9.0.0
    db_files = 1024 # INITIAL
    #INITIAL
    #db_files=80
    #SMALL
    #DB_files=400
    #MEDIUM
    #db_files=1000
    #LARGE
    control_files = ("\\.\clustdb_control1", "\\.\clustdb_control2")
    db_file_multiblock_read_count = 8 # INITIAL
    # db_file_multiblock_read_count = 8
    #SMALL
    #db_file_multiblock_read_count = 16
    #MEDIUM
    #db_file_multiblock_read_count = 32
    #LARGE
    #Datawarehouse
    db_block_size=8192
    # Transaction processing
    # db_block_size=4096
    open_cursors=300
    #Transaction processing
    #sort_area_size=524288
    #Datawarehouse
    sort_area_size=1048576
    large_pool_size=1048576 #Transaction processing, Datawarehouse
    db_cache_size=50331648 #Datawarehouse, Transaction processing
    java_pool_size=67108864 #Datawarehouse, Transaction processing
    # db_block_buffers = 200 # INITIAL
    # db_block_buffers=100 #SMALL
    # db_block_buffers =550 # MEDIUM
    # db_block_buffers=3200 #LARGE
    #shared_pool_size = 52428800 # INITIAL
    shared_pool_size = 67108864 # datewarehouse, transaction processing
    log_checkpoint_interval = 10000
    processes = 59 # INITIAL
    # processes = 50
    #SMALL
    #processes = 100
    #MEDIUM
    #processes = 200
    #LARGE
    parallel_max_servers = 5
    #SMALL
    # parallel_max_servers = 4 x (number of CPUs)
    #MEDIUM
    # parallel_max_servers = 4 x (number of CPUs)
    # LARGE
    log_buffer = 8192 # INITIAL
    #log_buffer = 8192
    #SMALL
    #log_buffer = 32768
    #MEDIUM
    #log_buffer = 163840
    #LARGE
    # audit_trail = true # if you want auditing
    # timed_statistics = true # if you want timed statistics
    max_dump_file_size = 10240 # limit trace file size to 10 K each
    # Uncommenting the line below will cause automatic archiving if archiving has
    # been enabled using ALTER DATABASE ARCHIVELOG.
    # log_archive_start = true
    # log_archive_dest = %ORACLE_HOME%/admin/clustdb/arch
    # log_archive_format = "%%ORACLE_SID%%T%TS%S.ARC"
    # If using private rollback segments, place lines of the following
    # form at the end of this file:
    # <sid>.rollback_segments = (name1, name2)
    # If using public rollback segments, define how many
    # rollback segments each instance will pick up, using the formula
    # # of rollback segments = transactions / transactions_per_rollback_segment
    # In this example each instance will grab 40/10 = 4:
    # transactions = 40
    # transactions_per_rollback_segment = 10
    # Global Naming -- enforce that a dblink has same name as the db it connects to
    global_names = TRUE
    # Edit and uncomment the following line to provide the suffix that will be
    # appended to the db_name parameter (separated with a dot) and stored as the
    # global database name when a database is created. If your site uses
    # Internet Domain names for e-mail, then the part of your e-mail address after
    # the '@' is a good candidate for this parameter value.
    # db_domain = us.acme.com # global database name is db_name.db_domain
    # Uncomment the following line if you wish to enable the Oracle Trace product
    # to trace server activity. This enables scheduling of server collections
    # from the Oracle Enterprise Manager Console.
    # Also, if the oracle_trace_collection_name parameter is non-null,
    # every session will write to the named collection, as well as enabling you
    # to schedule future collections from the console.
    # oracle_trace_enable = TRUE
    # define directories to store trace and alert files
    background_dump_dest=%ORACLE_HOME%/admin/clustdb/bdump
    user_dump_dest=%ORACLE_HOME%/admin/clustdb/
    db_block_size = 4096
    remote_login_passwordfile = exclusive
    # text_enable = TRUE
    # The following parameters are needed for the Advanced Replication Option
    job_queue_processes = 2
    # job_queue_processes = 4 #datawarehouse
    # job_queue_interval = 10
    # job_queue_keep_connections = false
    distributed_transactions = 5
    open_links = 4
    # The following parameters are instance-specific parameters that are
    # specified for two instances named clustdb1 and clustdb2
    undo_management=AUTO # For automatic undo management
    # = MANUAL For manual/RBS undo management
    cluster_database= true
    cluster_database_instances=2
    remote_listener=LISTENERS_CLUSTDB
    # First instance specific parameters
    clustdb1.thread=1
    clustdb1.instance_name=clustdb1
    clustdb1.instance_number=1
    clustdb1.local_listener=listener_clustdb1
    clustdb1.remote_login_passwordfile = exclusive
    # Comment out clustdb1.undo_tablespace and uncomment clustdb1.rollback_segments
    # when undo_management=MANUAL
    clustdb1.undo_tablespace = UNDOTBS1
    # clustdb1.rollback_segments = (rbs1_1,rbs1_2)
    # Second instance specific parameters
    clustdb2.thread=2
    clustdb2.instance_name = clustdb2
    clustdb2.instance_number = 2
    clustdb2.local_listener = listener_clustdb2
    clustdb2.remote_login_passwordfile = exclusive
    # Comment out clustdb2.undo_tablespace and uncomment clustdb2.rollback_segments
    # when undo_management=MANUAL
    clustdb2.undo_tablespace = UNDOTBS2
    # clustdb2.rollback_segments = (rbs2_1,rbs2_2)
    ===========================================
    listener.ora
    # listener.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    (PROGRAM = extproc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = us-as1.nti2.org)(PORT = 1521))
    TRACE_LEVEL_LISTENER = USER
    ===============================================
    sqlnet.ora
    # sqlnet.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    # Generated by Oracle configuration tools.
    # This file is actually generated by netca. But if customers choose to
    # install "Software Only", this file wont exist and without the native
    # authentication, they will not be able to connect to the database on NT.
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    =================================================
    tnsnames.ora
    # tnsnames.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    ORCL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = us-as1.nti2.org)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = orcl.us-as1.nti2.org)
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    ============================================================

    Enterprise manager still requires a static service definition in listener.ora and does not rely on dynamic registration.
    From documentation:
    The SID_LIST is required for backward compatibility with Oracle8 or Oracle7 databases, as well as external procedures and heterogeneous services, and some management tools, including Oracle Enterprise Manager.
    Werner

  • ORA-12514: TNS:listener does not currently know of service requested in con

    Hi All,
    I am trying to create a physical standby using RMAN duplicate command.Yesterday I created it succesfully ,today I dropped the standby database I tried to create new one when I got hit by this error"
    <code>
    [email protected](standby) $ rman target sys/root123#@db1 auxiliary sys/root123#@standby
    Recovery Manager: Release 11.2.0.1.0 - Production on Sun Mar 3 11:38:08 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    [email protected](standby) $
    </code>
    below is my tnsname and listener files from primary
    [email protected](db1) $ pwd
    /u01/app/oracle/dbhome_1/network/admin
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $ ls -ltr
    total 28
    -rw-r--r-- 1 oracle oinstall 187 May 7 2007 shrept.lst
    drwxr-xr-x 2 oracle oinstall 4096 Sep 12 22:12 samples
    -rw-r--r-- 1 oracle oinstall 40 Jan 20 03:38 sqlnet.ora_1
    -rw-r----- 1 oracle oinstall 1004 Mar 3 00:33 tnsnames.ora
    -rw-r--r-- 1 oracle oinstall 1004 Mar 3 11:27 tnsnames13030311AM2745.bak
    -rw-r--r-- 1 oracle oinstall 514 Mar 3 11:27 listener13030311AM2745.bak
    -rw-r--r-- 1 oracle oinstall 508 Mar 3 11:28 listener.ora
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $ cat tnsnames.ora
    # tnsnames.ora Network Configuration File: /u01/app/oracle/dbhome_1/network/admin/tnsnames.ora
    # Generated by Oracle configuration tools.
    DB1 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary.swapnilkambli.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = db1.primary.swapnilkambli.com)
    RCAT =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary.swapnilkambli.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = rcat.primary.swapnilkambli.com)
    DB2 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary.swapnilkambli.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = db2.primary.swapnilkambli.com)
    STANDBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = standby.swapnilkambli.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = standby.standby.swapnilkambli.com)
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $ cat listener.ora
    # listener.ora Network Configuration File: /u01/app/oracle/dbhome_1/network/admin/listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = rcat.primary.swapnilkambli.com)
    (ORACLE_HOME = /u01/app/oracle/dbhome_1)
    (SID_NAME = rcat)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary.swapnilkambli.com)(PORT = 1521))
    ADR_BASE_LISTENER = /u01/app/oracle
    [email protected](db1) $
    [email protected](db1) $ lsnrctl services
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 03-MAR-2013 11:42:52
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=primary.swapnilkambli.com)(PORT=1521)))
    Services Summary...
    Service "db1.primary.swapnilkambli.com" has 1 instance(s).
    Instance "db1", status READY, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:6 refused:0 state:ready
    LOCAL SERVER
    Service "db1XDB.primary.swapnilkambli.com" has 1 instance(s).
    Instance "db1", status READY, has 1 handler(s) for this service...
    Handler(s):
    "D000" established:0 refused:0 current:0 max:1022 state:ready
    DISPATCHER <machine: primary.swapnilkambli.com, pid: 2617>
    (ADDRESS=(PROTOCOL=tcp)(HOST=primary.swapnilkambli.com)(PORT=23611))
    Service "rcat.primary.swapnilkambli.com" has 1 instance(s).
    Instance "rcat", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:0 refused:0
    LOCAL SERVER
    The command completed successfully
    [email protected](db1) $ tnsping db1
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 03-MAR-2013 11:43:36
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = primary.swapnilkambli.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = db1.primary.swapnilkambli.com)))
    OK (0 msec)
    [email protected](db1) $
    [email protected](db1) $
    [email protected](db1) $ tnsping standby
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 03-MAR-2013 11:43:44
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = standby.swapnilkambli.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = standby.standby.swapnilkambli.com)))
    OK (0 msec)
    and below are my entries from standby server
    [email protected](standby) $ pwd
    /u01/app/oracle/dbhome_1/network/admin
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $ ls -ltr
    total 24
    -rw-r--r-- 1 oracle oinstall 187 May 7 2007 shrept.lst
    drwxr-xr-x 2 oracle oinstall 4096 Sep 12 22:12 samples
    -rw-r----- 1 oracle oinstall 576 Mar 3 11:21 tnsnames.ora
    -rw-r--r-- 1 oracle oinstall 576 Mar 3 11:25 tnsnames13030311AM2540.bak
    -rw-r--r-- 1 oracle oinstall 514 Mar 3 11:25 listener13030311AM2540.bak
    -rw-r--r-- 1 oracle oinstall 514 Mar 3 11:26 listener.ora
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $ cat tnsnames.ora
    # tnsnames.ora Network Configuration File: /u01/app/oracle/dbhome_1/network/admin/tnsnames.ora
    # Generated by Oracle configuration tools.
    DB1 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary.swapnilkambli.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = db1.primary.swapnilkambli.com)
    STANDBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = standby.swapnilkambli.com)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = standby.standby.swapnilkambli.com)
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $ cat listener.ora
    # listener.ora Network Configuration File: /u01/app/oracle/dbhome_1/network/admin/listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = standby.standby.swapnilkambli.com)
    (ORACLE_HOME = /u01/app/oracle/dbhome_1)
    (SID_NAME = standby)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = standby.swapnilkambli.com)(PORT = 1521))
    ADR_BASE_LISTENER = /u01/app/oracle
    [email protected](standby) $
    [email protected](standby) $ lsnrctl services
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 03-MAR-2013 11:43:14
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=standby.swapnilkambli.com)(PORT=1521)))
    Services Summary...
    Service "standby" has 1 instance(s).
    Instance "standby", status BLOCKED, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:0 refused:0 state:ready
    LOCAL SERVER
    Service "standby.standby.swapnilkambli.com" has 1 instance(s).
    Instance "standby", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:3 refused:0
    LOCAL SERVER
    The command completed successfully
    [email protected](standby) $ tnsping db1
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 03-MAR-2013 11:49:12
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = primary.swapnilkambli.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = db1.primary.swapnilkambli.com)))
    OK (0 msec)
    [email protected](standby) $
    [email protected](standby) $
    [email protected](standby) $ tnsping standby
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 03-MAR-2013 11:49:18
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = standby.swapnilkambli.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = standby.standby.swapnilkambli.com)))
    OK (0 msec)
    tnsping works from both side I am able to connect from primary as below:
    [email protected](db1) $ rman target sys/root123#@db1 auxiliary sys/root123#@standby
    Recovery Manager: Release 11.2.0.1.0 - Production on Sun Mar 3 11:44:23 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: DB1 (DBID=1402881212)
    connected to auxiliary database: DB1 (not mounted)
    RMAN>
    DB version 11.2.0.1.0
    OS version Linux 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
    primary server--- primary.swapnilkambli.com
    primary database--- db1
    standby server--- standby.swapnilkambli.com
    standby database--- standby
    After I dropped the physical standby first time I did make some changes in tns of standby server which I dont recollect.
    Help on this error ORA-12514 is available on internet but I did not find anything helpful to my situation
    Edited by: user12860499 on Mar 2, 2013 10:45 PM

    GOT IT!!!!
    I check listener trace and found below:
    Log messages written to /u01/app/oracle/diag/tnslsnr/standby/listener/alert/log.xml
    03-MAR-2013 12:21:59 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=standby.swapnilkambli.com)(USER=oracle))(COMMAND=reload)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186646784)) * reload * 0
    03-MAR-2013 12:22:00 * service_register * standby * 0
    Sun Mar 03 12:22:16 2013
    03-MAR-2013 12:22:16 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=db1.primary.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=standby.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=39512)) * establish * db1.primary.swapnilkambli.com * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    03-MAR-2013 12:22:20 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=standby.standby.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=standby.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.102)(PORT=54862)) * establish * standby.standby.swapnilkambli.com * 0
    03-MAR-2013 12:22:20 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=standby.standby.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=standby.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.102)(PORT=54863)) * establish * standby.standby.swapnilkambli.com * 0
    03-MAR-2013 12:22:20 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=standby.standby.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=standby.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.102)(PORT=54864)) * establish * standby.standby.swapnilkambli.com * 0
    Sun Mar 03 12:22:27 2013
    03-MAR-2013 12:22:27 * service_update * standby * 0
    Sun Mar 03 12:22:40 2013
    03-MAR-2013 12:22:40 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=standby.standby.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=primary.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.101)(PORT=60821)) * establish * standby.standby.swapnilkambli.com * 0
    03-MAR-2013 12:22:40 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=standby.standby.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=primary.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.101)(PORT=60822)) * establish * standby.standby.swapnilkambli.com * 0
    03-MAR-2013 12:22:40 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=standby.standby.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=primary.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.101)(PORT=60823)) * establish * standby.standby.swapnilkambli.com * 0
    03-MAR-2013 12:22:42 * service_update * standby * 0
    03-MAR-2013 12:22:45 * service_update * standby * 0
    Sun Mar 03 12:22:51 2013
    03-MAR-2013 12:22:51 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=db1.primary.swapnilkambli.com)(CID=(PROGRAM=rman)(HOST=standby.swapnilkambli.com)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=39536)) * establish * db1.primary.swapnilkambli.com * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    there was a entry in /etc/hosts which was directing primary.swapnilkambli.com to 127.0.01
    This was because I created this OS from a Virtual box template wherein that entry was made.
    I changed the /etc/hosts to refelct the true address and it worked!!

  • ORA-12504 tns listener was not given the SERVICE_NAME in CONNECT-DATA

    Hi
    i installed a fresh oracle linux and installes 11.2.0 database server. the server works fine but i have a proplem to connect to the database from a windows 2008 r2
    client. For the client connection i installed the oracle instantclient on the windows system. Now i want to configure the system dsn to connect to the oracle
    server like this
    data source description: vSphere 64
    description: ----
    TNS Service Name: VCDB
    user id: system
    then i go to TEST connection
    Service Name: VCDB
    user name: system
    Password: mypassword
    so i copied the tnsnames.ora from the server to the client
    then i get
    ora-12504 tns listener was not given the SERVICE_NAME in CONNECT-DATA
    here´s my tnsnames.ora from the client
    VCDB =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 172.31.98.173)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = vcdb.vmware)
    i tested serveral config´s but nothing works. I can ping the server and also i cn telnet the server on port 1521. The listener on the server works fine
    lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 20-SEP-2010 20:48:52
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=vc-db1.mydomain)(PORT=1521)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 20-SEP-2010 20:47:45
    Uptime 0 days 0 hr. 1 min. 7 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/vc-db1/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=vc-db1mydomain)(PORT=1521)))
    Services Summary...
    Service "vcdb.vmware" has 1 instance(s).
    Instance "vcdb", status READY, has 1 handler(s) for this service...
    Service "vcdbXDB.vmware" has 1 instance(s).
    Instance "vcdb", status READY, has 1 handler(s) for this service...
    The command completed successfully
    but it´s not possible to create a connection to the server. My enviroment variables are this
    ORACLE_BASE=/u01/app/oracle
    ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
    ORACLE_HOSTNAME=vc-db1.mydomain
    ORACLE_SID=vcdb
    ORACLE_TERM=xterm
    so i think on the server site everything is correct. How could i establish a connection from the windows client
    to the linux database server. Or is ODBC the wrong method for this?
    Kind regards
    ACID25

    Hi,
    Check the listener log and see if the connection information is logged (in this case with error)
    If logged, then we are reaching the correct listener.
    Then check tnsping VCDB works fine along with sqlplus connection through listener using VCDB as connect string.
    If above both works, then issue can be isolated to ODBC configuration or setup issue.
    In case even if the tnsping / sqlplus is failing to connect with VCDB, then worth taking a client sqlent trace at level 16 and listener trace at level 16 to analyse the issue further.
    Thanks,
    Sathya

  • "ORA-12514 TNS: listener does not currently know of service equested in con

    Hi All,
    I have Oracle 11g Express edition installed on windows(this is a remore machine)
    I searched google and tried many options ....don't know where am i going wrong
    below are my tnsnames,listener and sqlnet files
    LISTENER.ora
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (SID_NAME = PLSExtProc)
          (ORACLE_HOME = c:\oraclexe\app\oracle\product\11.2.0\server)
          (PROGRAM = XE)
        (SID_DESC =
          (SID_NAME = CLRExtProc)
          (ORACLE_HOME = c:\oraclexe\app\oracle\product\11.2.0\server)
          (PROGRAM = XE)
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
            (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.61.5)(PORT = 1521))
            (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
    TRACE_FILE_listener=list_h.trc
    TRACE_LEVEL_listener=admin
    DEFAULT_SERVICE_LISTENER = (XE)tnsnames.ora
    XE=
      (DESCRIPTION=
        (ADDRESS=
          (PROTOCOL=TCP)
          (HOST=192.168.61.5)
          (PORT=1521)
        (CONNECT_DATA=
          (SERVER=dedicated)
          (SERVICE_NAME=XE)
    # This file is actually generated by netca. But if customers choose to
    # install "Software Only", this file wont exist and without the native
    # authentication, they will not be able to connect to the database on NT.
    #SQLNET.AUTHENTICATION_SERVICES =
    #NAMES.DIRECTORY_PATH=C:\oraclexe\app\oracle\product\11.2.0\server\network\ADMIN
    sqlnet.authentication_services=(NTS)

    Thanks for your reply....
    below is my listener.log
    Wed Dec 07 14:12:21 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_5396_5244.trc
    Trace level is currently 6
    Started with pid=5396
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    Wed Dec 07 14:15:42 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_2352_5320.trc
    Trace level is currently 6
    Started with pid=2352
    Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191.168.61.5)(PORT=1521)))
    TNS-12545: Connect failed because target host or object does not exist
    TNS-12560: TNS:protocol adapter error
      TNS-00515: Connect failed because target host or object does not exist
       32-bit Windows Error: 49: Unknown error
    Wed Dec 07 14:15:56 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_384_5368.trc
    Trace level is currently 6
    Started with pid=384
    Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191.168.61.5)(PORT=1521)))
    TNS-12545: Connect failed because target host or object does not exist
    TNS-12560: TNS:protocol adapter error
      TNS-00515: Connect failed because target host or object does not exist
       32-bit Windows Error: 49: Unknown error
    Wed Dec 07 14:16:48 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_5316_5512.trc
    Trace level is currently 6
    Started with pid=5316
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    Wed Dec 07 14:18:55 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_5992_2320.trc
    Trace level is currently 6
    Started with pid=5992
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    Wed Dec 07 14:28:22 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_2904_5604.trc
    Trace level is currently 6
    Started with pid=2904
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=1521)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    Wed Dec 07 14:40:01 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\ADMIN\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_4756_4852.trc
    Trace level is currently 6
    Started with pid=4756
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=1521)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    Wed Dec 07 14:40:30 2011
    07-DEC-2011 14:40:30 * ping * 0
    Wed Dec 07 14:40:59 2011
    07-DEC-2011 14:40:59 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59621)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 14:41:15 2011
    WARNING: Subscription for node down event still pending
    07-DEC-2011 14:41:15 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=thangavelur))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
    Wed Dec 07 14:42:22 2011
    07-DEC-2011 14:42:22 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\oraclexe\app\oracle\product\11.2.0\server\bin\sqlplus.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59649)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 14:44:55 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\ADMIN\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_4312_5456.trc
    Trace level is currently 6
    Started with pid=4312
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=1521)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    Wed Dec 07 14:45:34 2011
    WARNING: Subscription for node down event still pending
    07-DEC-2011 14:45:34 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=thangavelur))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
    Wed Dec 07 14:46:06 2011
    07-DEC-2011 14:46:06 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=thangavelur))(COMMAND=services)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * services * 0
    Wed Dec 07 14:47:20 2011
    07-DEC-2011 14:47:20 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59758)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 14:49:29 2011
    07-DEC-2011 14:49:29 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59791)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 14:49:52 2011
    07-DEC-2011 14:49:52 * (CONNECT_DATA=(SERVICE_NAME=XE)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59795)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 14:50:08 2011
    07-DEC-2011 14:50:08 * (CONNECT_DATA=(SERVICE_NAME=XE)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59800)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 14:50:27 2011
    07-DEC-2011 14:50:27 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59807)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 14:51:03 2011
    07-DEC-2011 14:51:03 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59816)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 15:01:27 2011
    07-DEC-2011 15:01:27 * (CONNECT_DATA=(SERVER=dedicated)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=59996)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 15:02:42 2011
    07-DEC-2011 15:02:42 * (CONNECT_DATA=(SERVER=dedicated)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=60016)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 15:05:31 2011
    07-DEC-2011 15:05:31 * ping * 0
    Wed Dec 07 15:05:55 2011
    WARNING: Subscription for node down event still pending
    07-DEC-2011 15:05:55 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=thangavelur))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
    Wed Dec 07 15:06:28 2011
    07-DEC-2011 15:06:28 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=thangavelur))(COMMAND=services)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * services * 0
    Wed Dec 07 15:08:19 2011
    07-DEC-2011 15:08:19 * ping * 0
    Wed Dec 07 15:23:50 2011
    System parameter file is C:\oraclexe\app\oracle\product\11.2.0\server\network\ADMIN\listener.ora
    Log messages written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\alert\log.xml
    Trace information written to c:\oraclexe\app\oracle\diag\tnslsnr\WP2345\listener\trace\ora_1508_5128.trc
    Trace level is currently 6
    Started with pid=1508
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=1521)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROCipc)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    Wed Dec 07 15:24:36 2011
    WARNING: Subscription for node down event still pending
    07-DEC-2011 15:24:36 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=thangavelur))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
    Wed Dec 07 15:24:59 2011
    07-DEC-2011 15:24:59 * ping * 0
    Wed Dec 07 15:25:40 2011
    07-DEC-2011 15:25:40 * (CONNECT_DATA=(SERVER=dedicated)(SERVICE_NAME=XE)(SERVER=dedicated)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=60525)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    Wed Dec 07 15:26:10 2011
    07-DEC-2011 15:26:10 * (CONNECT_DATA=(SERVICE_NAME=XE)(CID=(PROGRAM=C:\Program?Files??x86?\Quest?Software\Toad?for?Oracle\Toad.exe)(HOST=WP2345)(USER=thangavelur))(SERVER=dedicated)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.61.5)(PORT=60534)) * establish * XE * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor

  • TNS-12560: TNS:protocol adapter error listener not starting up.

    Hi all
    we came to an issue where we have to move our server from one data centre to another after unplugging the machine and re-plugging the server
    1) Operating system (OEL 5.1) started.
    2) Database 11gR2 started.
    3) Listener Failed to Start.
    [oracle@yam01 tmp]$ lsnrctl start lsn_yscc12
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 02-OCT-2012 07:57:58
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Starting /u01/app/oracle/product/11.2.0/bin/tnslsnr: please wait...
    TNS-12537: TNS:connection closed
    TNS-12560: TNS:protocol adapter error
    TNS-00507: Connection closed
    Linux Error: 29: Illegal seek
    [oracle@yam01 tmp]$
    When checked in sqlnet.log we found.
    [oracle@yam01 log]$ cat sqlnet.log
    Directory does not exist for read/write [u01/app/oracle/product/11.2.0/log] [u01/app/oracle/product/11.2.0/log/diag/clients]
    [oracle@yam01 log]$
    /u01/app/oracle/product/11.2.0/log
    /u01/app/oracle/product/11.2.0/log/diag/clients --> here under diag folder client folder was missing.
    drwxrwxr-x 3 oracle oinstall 4096 Sep 30 12:59 /u01/app/oracle/product/11.2.0/log/diag/
    *[oracle@yam01 log]$ cd /u01/app/oracle/product/11.2.0/log/diag/clients*
    -bash: cd: /u01/app/oracle/product/11.2.0/log/diag/clients: No such file or directory
    *[oracle@yam01 log]*
    [oracle@yam01 diag]$ mkdir clients
    [oracle@yam01 diag]$ ls -ltr
    total 12
    drwxr-x--- 3 oracle oinstall 4096 Sep 30 12:59 rdbms
    -rw-r----- 1 oracle oinstall 15 Oct 2 07:43 adrci_dir.mif
    drwxr-xr-x 2 oracle oinstall 4096 Oct 2 08:27 clients
    [oracle@yam01 diag]$
    and added *"SUBSCRIBE_FOR_NODE_DOWN_EVENT_lsn_yscc12=OFF"*
    and then when started all the listener it started successfully.+_
    [oracle@yam01 ~]$ lsnrctl status lsn_yscc12
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 02-OCT-2012 08:40:19
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=100.100.50.199)(PORT=1603)))
    STATUS of the LISTENER
    Alias lsn_yscc12
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 02-OCT-2012 08:28:09
    Uptime 0 days 0 hr. 12 min. 9 sec
    Trace Level admin
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/yam01/lsn_yscc12/alert/log.xml
    Listener Trace File /u01/app/oracle/diag/tnslsnr/yam01/lsn_yscc12/trace/ora_10095_3086223040.trc
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=100.100.50.199)(PORT=1603)))
    Services Summary...
    Service "YSCC12.YAMAMACEMENT.COM" has 1 instance(s).
    Instance "yscc12", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    [oracle@yam01 ~]$
    Thanks all for Reading this post
    hope if you came across this issues this may work for you.
    Best Regards
    Kaleem.

    Welcome to OTN
    Thank you For you sharing :)

  • Prolem starting listener in Oracle 9i on Windows

    After a fresh installation of Oracle 9.2 on Windows 2003 server, there is no service created for listener. When I tried to start it from command prompt, I get following
    D:\oracle\ora92\bin>lsnrctl start
    LSNRCTL for 32-bit Windows: Version 9.2.0.1.0 - Production on 17-JUL-2006 16:14:43
    Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
    Starting tnslsnr: please wait...
    TNS-12560: TNS:protocol adapter error
    TNS-00530: Protocol adapter error
    There is no listener.log file created at all. Further I started the trace for the listener but it is not even creating the listener trace file.
    Please help

    Thanks. I installed software and created database as well. The database service is running but there is no listener service created. But I am getting the error even if I try to start the listener with lsnrctl start. Follwoing is listener.ora.
    # LISTENER.ORA Network Configuration File: D:\oracle\ora92\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = cqs702)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\ora92)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = TCGPUNDB)
    (ORACLE_HOME = D:\oracle\ora92)
    (SID_NAME = TCGPUNDB)
    TRACE_LEVEL_LISTENER = SUPPORT

  • Oracle listener problem in 9204 rac

    Hi ,
    I have an oracle database running in rac .
    Platform - solaris 8
    RDBMS version - 9204
    I am two nodes on which the individual instances runs
    The dbname is PSFTP AND the node 1 is PSFTP1 AND node 2 is PSFTP2
    I am unable to connect to the first node
    /u00/app/oracle/product/92/network/log $ sqlplus <uid>/<passwd>@psftp
    SQL*Plus: Release 9.2.0.4.0 - Production on Thu Aug 19 15:41:51 2004
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    ERROR:
    ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect
    descriptor
    Enter user-name:
    /u00/app/oracle/product/92/network/log $ sqlplus uid>/<passwd>@psftp1
    SQL*Plus: Release 9.2.0.4.0 - Production on Thu Aug 19 15:42:10 2004
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    ERROR:
    ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect
    descriptor
    Init.ora parameter
    local_listener=LISTENER_PSFTP1
    service_names=PSFTP
    Tnsnames.ora
    LISTENER_PSFTP1=(address=(protocol=tcp)(host=10.176.247.230)(port=2521))
    PSFTP =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.176.247.230)(PORT = 2521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.176.247.244)(PORT = 2521))
    (LOAD_BALANCE = yes)
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = PSFTP)
    (failover_mode =
    (type = select)
    (method = basic)
    (retries = 20)
    (delay = 15)
    PSFTP1 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.176.247.230)(PORT = 2521))
    (CONNECT_DATA =
    (SERVICE_NAME = PSFTP)
    (INSTANCE_NAME = PSFTP1)
    Listener.ora
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.176.247.230)(PORT = 2521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (ORACLE_HOME = /u00/app/oracle/product/92)
    (SID_NAME = PSFTP1)
    Listener.log
    TNSLSNR for Solaris: Version 9.2.0.4.0 - Production on 17-AUG-2004 21:58:31
    Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
    System parameter file is /u00/app/oracle/product/92/network/admin/listener.ora
    Log messages written to /u00/app/oracle/product/92/network/log/listener.log
    Trace information written to /u00/app/oracle/product/92/network/log/listener.trc
    Trace level is currently 16
    Started with pid=29809
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.176.247.230)(PORT=2521)))
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    17-AUG-2004 21:58:31 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=psfpdb01)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VE
    RSION=153093120)) * status * 0
    17-AUG-2004 21:58:39 * service_register * PSFTP1 * 0
    17-AUG-2004 21:58:39 * service_died * PSFTP1 * 12537
    17-AUG-2004 21:59:39 * service_register * PSFTP1 * 0
    17-AUG-2004 21:59:39 * service_died * PSFTP1 * 12537
    17-AUG-2004 22:00:39 * service_register * PSFTP1 * 0
    17-AUG-2004 22:00:39 * service_died * PSFTP1 * 12537
    17-AUG-2004 22:01:40 * service_register * PSFTP1 * 0
    17-AUG-2004 22:01:40 * service_died * PSFTP1 * 12537
    17-AUG-2004 22:02:40 * service_register * PSFTP1 * 0
    17-AUG-2004 22:02:40 * service_died * PSFTP1 * 12537
    17-AUG-2004 22:03:40 * service_register * PSFTP1 * 0
    17-AUG-2004 22:03:40 * service_died * PSFTP1 * 12537
    17-AUG-2004 22:04:40 * service_register * PSFTP1 *
    LSNRCTL> status
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.176.247.230)(PORT=2521)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Solaris: Version 9.2.0.4.0 - Production
    Start Date 17-AUG-2004 21:58:31
    Uptime 1 days 17 hr. 42 min. 55 sec
    Trace Level support
    Security OFF
    SNMP OFF
    Listener Parameter File /u00/app/oracle/product/92/network/admin/listener.ora
    Listener Log File /u00/app/oracle/product/92/network/log/listener.log
    Listener Trace File /u00/app/oracle/product/92/network/log/listener.trc
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.176.247.230)(PORT=2521)))
    Services Summary...
    Service "PSFTP1" has 1 instance(s).
    Instance "PSFTP1", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    LSNRCTL>
    Thanks
    Prabhakar

    do sqlplus @LISTENER_PSFTP1
    your tns entry is misleading.

  • ORA-12514: TNS:listener does not currently know of service request

    Helllo ! I have just performed a new oracle 11g installation on a Windows pc. However I get error ORA-12514 when attempting to connect to the database using sql plus or even when doing a connection test with oracle net manager.
    Below are the contents of my files:
    Listner.ora
    # listener.ora Network Configuration File: C:\app\dfernandes\product\11.2.0\dbhome_1\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = CLRExtProc)
    (ORACLE_HOME = C:\app\dfernandes\product\11.2.0\dbhome_1)
    (PROGRAM = extproc)
    (ENVS = "EXTPROC_DLLS=ONLY:C:\app\dfernandes\product\11.2.0\dbhome_1\bin\oraclr11.dll")
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    ADR_BASE_LISTENER = C:\app\dfernandes
    tnsnames.ora
    # tnsnames.ora Network Configuration File: C:\app\dfernandes\product\11.2.0\dbhome_1\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    ORACLR_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    (CONNECT_DATA =
    (SID = CLRExtProc)
    (PRESENTATION = RO)
    ORCL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = orcl)
    when I run the command lsnrctl services I just get the below.....
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
    Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:0 refused:0
    LOCAL SERVER
    The command completed successfully
    ......which probably tells me (I'm assuming) that my database is not registered with the listener.
    Can someone please help ? I'm not very familiar with oracle connection issues. Thanks !

    Hi! Below is the contents of file c:\app\dfernandes\diag\tnslsnr\sedona\listener\alert\log.xml
    <msg time='2011-12-08T16:02:51.581+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    </txt>
    </msg>
    <msg time='2011-12-08T16:02:52.783+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Listener completed notification to CRS on start
    </txt>
    </msg>
    <msg time='2011-12-08T16:02:52.783+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    </txt>
    </msg>
    <msg time='2011-12-08T16:03:48.335+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>08-DEC-2011 16:03:48 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=dfernandes))(COMMAND=services)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186646784)) * services * 0
    </txt>
    </msg>
    <msg time='2011-12-08T16:03:51.096+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>08-DEC-2011 16:03:51 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=dfernandes))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186646784)) * status * 0
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.888+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>System parameter file is C:\app\dfernandes\product\11.2.0\dbhome_1\network\admin\listener.ora
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.904+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Log messages written to c:\app\dfernandes\diag\tnslsnr\sedona\listener\alert\log.xml
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.904+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Trace information written to c:\app\dfernandes\diag\tnslsnr\sedona\listener\trace\ora_4512_4516.trc
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.920+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Trace level is currently 0
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.920+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.935+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Started with pid=4512
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.935+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:13.951+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:15.199+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>Listener completed notification to CRS on start
    </txt>
    </msg>
    <msg time='2011-12-08T16:05:15.199+11:00' org_id='oracle' comp_id='tnslsnr'
    type='UNKNOWN' level='16' host_id='SEDONA'
    host_addr='fe80::e487:38ca:d34a:79c4%10'>
    <txt>
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    </txt>
    </msg>

  • How to use trace file information?

    Hello.
    I got trace files in $O_H/network/trace/ listener.trc and in
    $O_H/rdbms/log/ora_orcl_22846.trc and others in the same dir. SO
    how can I get any understandable form? ( All this numbers and
    letters say nothing to me :((. Maybe I should read some manual?)
    Thank You.
    null

    ANdrey (guest) wrote:
    : Hello.
    : I got trace files in $O_H/network/trace/ listener.trc and in
    : $O_H/rdbms/log/ora_orcl_22846.trc and others in the same dir.
    SO
    : how can I get any understandable form? ( All this numbers and
    : letters say nothing to me :((. Maybe I should read some
    manual?)
    : Thank You.
    Listener trace should be humanly readable by itself and
    oracle trace files should be processed by using tkprof.
    null

  • TNS-1190 despite listener password

    Hi,
    we are migrating from em 11g to em 12c. Now we are getting listener error TNS-1190 "trc_directory (TNS-1190),. Please check log for details. ". As per note 1399060.1 I set listener password and changed "Monitoring Configuration" in oms but the same error still occurs.
    When I execute "show trc_directory" from shell everything works fine:
    oracle@orarac11g:~ $ lsnrctl
    LSNRCTL for Solaris: Version 11.2.0.3.0 - Production on 03-DEC-2012 09:48:37
    Copyright (c) 1991, 2011, Oracle.  All rights reserved.
    Welcome to LSNRCTL, type "help" for information.
    LSNRCTL> show trc_directory
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    TNS-01190: The user is not authorized to execute the requested listener command
    LSNRCTL> set password
    Password:
    The command completed successfully
    LSNRCTL> show trc_directory
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    LISTENER parameter "trc_directory" set to /oraclebin/app/gridbase11.2/diag/tnslsnr/orarac11g/listener/trace
    The command completed successfullyDoes anybody have the same error?
    Thanks in advance

    Hi
    I suggest first check you listener log. If you still see messages "trc_directory * 1190", you have not fixed the problem with your listener password.
    If you setup the listener password properly on the server, you need then to place it in the listener config on OEM side.
    Go to Listener Menu ->Target Setup -> Monitoring Configuration and place the password in "Listener Password" field. Then save the config.
    and see again. if it does not help try to reboot the agent.
    Kirill Loifman, dadbm.com
    Edited by: Kirill Loifman on Jan 14, 2013 1:40 AM
    Edited by: Kirill Loifman on Apr 12, 2013 7:51 AM

Maybe you are looking for

  • Blue screen crash when hooking up iPhone

    I have had my iPhone for a few months now and have only been able to hook up my phone to my husband's (far inferior) laptop. Whenever I hook my phone up to my Sony Vaio desktop I get a blue screen crash and the whole system starts rebooting. Does any

  • Question regarding ASO application in Essbase 11 version

    Hi All, Thanks for the replies to my previous posts. I have a question regarding the ASO applications for telecom company built in Essbase 11 version. Please provide your feedback on the design. The ASO application has the following number of Dimensi

  • How do I get dates to appear on photos?

    Can anyone tell me how to get dates to appear on photos so that when you print them it shows the date in the bottom corner?

  • My Toshiba Satellite L845 shuts down

    Hi. I bought a few hours ago this laptop, and every 30 minutes it shuts down. I've checked if it could be overwarming, but it's not. Now it shuts down when it wants, tomorrow I'll change it for a new one, but, is ther any problem than I can fix? Than

  • Fsck error after installation

    Hi Everyone! I installed Arch on my system with three hdds, sda, sdb, and sdc. Arch is installed on sdb with two linux partitions, sdb1 and sdb2. On sda and sdc I use Windows and they are ntfs formatted. I don't want to use those two disks in Arch, s