ORA-12541: TNS no listener while remote archiving
REFERENCE: How to Resolve
Error in Remote Archiving [ID 799353.1]
Problem on Primary
ORA-12541: TNS:no listener
LNS: Failed to archive log 5 thread 2 sequence 1101 (12541)
Sun May 22 13:05:55 2011
Error 12541 received logging on to the standby
Check whether the listener is up and running.
LNS: Failed to archive log 5 thread 2 sequence 1101 (12541)
Sun May 22 13:05:55 2011
Error 12541 received logging on to the standby
Check whether the listener is up and running.
Note
:- This error can be happen when you add new standby server for the primary
Solution:
1. Check the status of remote
archive destination on primary database
SELECT DESTINATION, STATUS, ERROR FROM
V$ARCHIVE_DEST WHERE DEST_ID=2;
DESTINATION STATUS
ERROR
——————– ——— —————————————-
ERPDR ERROR ORA-12541: TNS:no listener
——————– ——— —————————————-
ERPDR ERROR ORA-12541: TNS:no listener
2. Defer and enable the remote
archive destination (that can be check
any destination like 3 4 5 )
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER;
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;
3. Perform 2 log switches on
the Primary/Source database:
ALTER SYSTEM SWITCH LOGFILE;
ALTER SYSTEM SWITCH LOGFILE;
ALTER SYSTEM SWITCH LOGFILE;
4. Check the status of remote
archive destination again:
SELECT DESTINATION, STATUS, ERROR FROM
V$ARCHIVE_DEST WHERE DEST_ID=2;
DESTINATION STATUS
ERROR
——————– ——— —————————————-
ERPDR ERROR ORA-12541: TNS:no listener
——————– ——— —————————————-
ERPDR ERROR ORA-12541: TNS:no listener
5 . Check Whether Redo Logs
Are Getting Received On the Standby Using:
From Standby
From Standby
SELECT THREAD#,MAX(SEQUENCE#) FROM
V$ARCHIVED_LOG GROUP BY THREAD#;
THREAD# MAX(SEQUENCE#)
---------- --------------
1 1087
2 1101
---------- --------------
1 1087
2 1101
Perform 2 log switches on primary
database:
ALTER SYSTEM SWITCH LOGFILE;
ALTER SYSTEM SWITCH LOGFILE;
Check whether SEQUENCE# changes
SELECT THREAD#,MAX(SEQUENCE#) FROM
V$ARCHIVED_LOG GROUP BY THREAD#;
THREAD# MAX(SEQUENCE#)
---------- --------------
1 1087
2 1103
---------- --------------
1 1087
2 1103
Remote archiving is working fine if
the sequence# is moving.
Proceed to step 6 if sequence# is not moving:
Proceed to step 6 if sequence# is not moving:
6 . Check the value of log_archive_max_processes on primary: (this
parameter will be avoid any issue in GAP sequence)
Current status
SHOW PARAMETER LOG_ARCHIVE_MAX_PROCESSES
NAME TYPE VALUE
------------------------------- ----------- -------------
log_archive_max_processes INTEGER 2
Note :- Increase the value of log_archive_max_processes to 10 (From 10.2 you can increase value up to 30).
ALTER SYSTEM SET LOG_ARCHIVE_MAX_PROCESSES=10;
Repeat step 5 and check whether
redo is getting received on the standby.
If
error not resolve please following steps will be help
5. Spawn new ARC processes for
primary database: This is required because ARC processes get stuck with
old error messages
a.Check the OS PID of the ARC
processes on the primary database using:
For Unix Linux
Log in to as root
$ ps -ef|grep -i arc| grep
$ORACLE_SID
And kill
all the output PID and retest or restart the Instance
For UNIX LINUX
$kill -9 <pid1> <pid2>
… <pid n>
No comments:
Post a Comment