Archive

Archive for the ‘TNS’ Category

Listener can’t write log file

August 18, 2014 Leave a comment

Symptoms

Listener can’t write log file. The log file has no log

[oracle@wplodb03 log]$ ls -al
total 28841972
drwxr-x—   2 oracle oinstall        4096 Jul 18 14:06 .
drwxr-x—  12 oracle oinstall        4096 May  7  2007 ..
-rw-r–r–   1 oracle oinstall           0 Aug 18 14:39 listener_wplodb03.log

Fixed

Set log_status of Listeners on/off as below

LSNRCTL> show log_status
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
LISTENER parameter “log_status” set to ON
The command completed successfully
LSNRCTL> set log_status off
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
LISTENER parameter “log_status” set to OFF
The command completed successfully
LSNRCTL> show log_status
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
LISTENER parameter “log_status” set to OFF
The command completed successfully
LSNRCTL> set log_status on
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
LISTENER parameter “log_status” set to ON
The command completed successfully
LSNRCTL> show log_status
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
LISTENER parameter “log_status” set to ON
The command completed successfully
LSNRCTL> exit
[oracle@wplodb03 log]$ ls -lrt
-rw-r–r–  1 oracle oinstall     4972026 Aug 17 23:10 sqlnet.log
-rw-r–r–  1 oracle oinstall        1759 Aug 18 14:44 listener_wplodb03.log

After on/off, the log file grows

Advertisements
Categories: TNS

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

June 20, 2012 Leave a comment

Today, I clone a 11gR2.0.3 database at the same database server. Once I start rman, I get the ORA errors message below

[oracle@ycsdb01 dbs]$ rman target / nocatalog auxiliary sys/12345@spbpro

Recovery Manager: Release 11.2.0.3.0 – Production on Wed Jun 20 17:13:06 2012

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: CSPRO (DBID=3560463483)
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12528: TNS:listener: all appropriate instances are blocking new connections
[oracle@ycsdb01 dbs]$ cd $ORACLE_HOME/network/admin

Solution

Then, I add the option “(UR=A)”  in tnsnames.ora as below. The problem is fixed.

SPBPRO =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = scan.springboard.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = spbpro)(UR=A)
)
)

 

 

Categories: ORA-XXX, RMAN, TNS

WARNING: Subscription for node down event still pending

February 15, 2011 Leave a comment

Symptoms

In  listener log file, the warning message happened

WARNING: Subscription for node down event still pending
14-JAN-2011 11:13:30 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=gsqsvmdb)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=1
85599744)) * status * 0
2011-01-14 11:14:09.862000 +08:00
WARNING: Subscription for node down event still pending
14-JAN-2011 11:14:09 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=gsqsvmdb)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=1
85599744)) * status * 0
2011-01-14 11:17:02.792000 +08:00
WARNING: Subscription for node down event still pending
14-JAN-2011 11:17:02 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=gsqsvmdb)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=1
85599744)) * status * 0
2011-01-14 11:21:37.933000 +08:00
WARNING: Subscription for node down event still pending
14-JAN-2011 11:21:37 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=gsqsvmdb)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=1
85599744)) * status * 0
2011-01-14 11:21:52.666000 +08:00
WARNING: Subscription for node down event still pending
14-JAN-2011 11:21:52 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=gsqsvmdb)(USER=

Cause
These messages are related to the Oracle10g TNS Listener’s default subscription to the Oracle Notification Service (ONS). In a non-RAC environment it is recommended to disable this subscription.

Solution
Set the following parameter in the listener.ora:

SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name>=OFF

Where <listener_name> should be replaced with the actual listener name configured in the
LISTENER.ORA file.

This will prevent the messages from being written to the log file, but also prevent the 10g TNS
Listener from hanging periodically.

Categories: TNS