I installed a software called SQL-station from Platium technology, and
I thought the installation program changed my Oracle listener setting.
The listener runs at 100% all the time ever after I installed the sql-
station. I tried to turn off every "trace" option that I could find in
the Oracle settings( all the *.ora files), but no luck. One thing I
noticed is that listener keeps on writing to a file called
\orant\network\admin\trace\listener.trc.
Anyone has ideas or suggestion on how to turn the listener trace off ?
The following is the part of the trace log for the listener.
TNSLSNR for 32-bit Windows: Version 2.3.3.0.0 - Production on 10-JUN-99
13:55:16
Copyright (c) Oracle Corporation 1994. All rights reserved.
- TRACE CONFIGURATION INFORMATION FOLLOWS ---
New trace stream is "C:\ORANT\network\trace\listener.trc"
New trace level is 6
- TRACE CONFIGURATION INFORMATION ENDS ---
- PARAMETER SOURCE INFORMATION FOLLOWS ---
Attempted load of system pfile source C:
\ORANT\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 <-
STARTUP_WAIT_TIME_LISTENER = 0
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = ORCL)))
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = ADMIN
PASSWORDS_LISTENER = (oracle)
LISTENER = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= IPC) (KEY=
oracle.world)) (ADD
RESS= (PROTOCOL= IPC) (KEY= ORCL)) (ADDRESS= (COMMUNITY= TCP.world)
(Host = ml07
3953) (PROTOCOL= TCP) (Port= 1521)) (ADDRESS= (COMMUNITY= TCP.world)
(Host = ml0
73953) (PROTOCOL= TCP) (Port= 1526)))
--- PARAMETER SOURCE INFORMATION ENDS ---
- LOG CONFIGURATION INFORMATION FOLLOWS ---
Log stream will be "C:\ORANT\network\log\listener.log"
Log stream validation requested
Log stream is valid
- LOG CONFIGURATION INFORMATION ENDS ---
Resolved "CONNECT_TIMEOUT_LISTENER" to: 10
Resolved "STARTUP_WAIT_TIME_LISTENER" to: 0
(DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=(PROTOCOL=IPC)
(KEY=oracle.world)))
opening transport...
listening on pipe 132
transport is open
global context check-in (to slot 0) complete
completing partial addr: (DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=
(PROTOCOL=IPC
)(KEY=oracle.world)))Listening on: (ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.
\pipe\ora
cle.worldipc))
(ADDRESS=(PROTOCOL=ipc)(PARTIAL=yes)(QUEUESIZE=1))
opening transport...
listening on pipe 164
transport is open
global context check-in (to slot 1) complete
(DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=(PROTOCOL=IPC)(KEY=ORCL)))
opening transport...
listening on pipe 168
transport is open
global context check-in (to slot 2) complete
completing partial addr: (DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=
(PROTOCOL=IPC
)(KEY=ORCL)))Listening on: (ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.
\pipe\ORCLipc))
(DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=(COMMUNITY=TCP.world)
(Host=ml073953)(P
ROTOCOL=TCP)(Port=1521)))
port resolved to 1521
looking up IP addr for host: ml073953
opening transport...
No PROTOCOL.ORA file is found
Validnode Table IN use; err 0x0
getting sockname
transport is open
global context check-in (to slot 3) complete
completing partial addr: (DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=
(COMMUNITY=TC
P.world)(Host=ml073953)(PROTOCOL=TCP)(Port=1521)))Listening on:
(ADDRESS=(PROTOC
OL=tcp)(DEV=196)(HOST=146.125.8.205)(PORT=1521))
(DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=(COMMUNITY=TCP.world)
(Host=ml073953)(P
ROTOCOL=TCP)(Port=1526)))
port resolved to 1526
looking up IP addr for host: ml073953
opening transport...
Validnode Table IN use; err 0x0
getting sockname
transport is open
global context check-in (to slot 4) complete
completing partial addr: (DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=
(COMMUNITY=TC
P.world)(Host=ml073953)(PROTOCOL=TCP)(Port=1526)))Listening on:
(ADDRESS=(PROTOC
OL=tcp)(DEV=224)(HOST=146.125.8.205)(PORT=1526))
Testing for 2 cxds on protocol Windows NT TCP/IP NT Protocol Adapter
Testing for 2 cxds on protocol Windows NT Named Pipes IPC NT Protocol
Adaptor
Testing for 2 cxds on protocol Windows NT Named Pipes IPC NT Protocol
Adaptor
Testing for 2 cxds on protocol Windows NT TCP/IP NT Protocol Adapter
Testing for 2 cxds on protocol Windows NT Named Pipes IPC NT Protocol
Adaptor
Testing for 2 cxds on protocol Windows NT TCP/IP NT Protocol Adapter
Testing for 2 cxds on protocol Windows NT Named Pipes IPC NT Protocol
Adaptor
..........
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Received on Thu Jun 10 1999 - 16:52:27 CDT
