Hi,
Please find details below :-
SQL> show parameter log_archive_dest_2 ;( For primary )
NAME TYPE VALUE
------------------------------------ -----------
------------------------------
log_archive_dest_2 string service="rac", LGWR ASYNC
NOAF
FIRM delay=0 optional
compress
ion=disable max_failure=0
max_
connections=1 reopen=300
db_un
ique_name="rac"
net_timeout=30
,
valid_for=(all_logfiles,prim
ary_role)
DGMGRL> show database verbose 'standby'
Database - standby
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
standby
Error: ORA-16737: the redo transport service for standby database
"rac" has an error
Properties:
DGConnectIdentifier = 'standby'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '30'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = '+DATA/rac/, +DATA/standby/'
LogFileNameConvert = '+DATA/rac/, +DATA/standby/'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'standby'
StaticConnectIdentifier =
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=standby_DGMGRL.racattack)(INSTANCE_NAME=standby)(SERVER=DEDICATED)))'
StandbyArchiveLocation = '+FRA'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = '%t_%s_%r.dbf'
TopWaitEvents = '(monitor)'
Database Status:
ERROR
Fatal NI connect error 12514, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=racattack-cluster-scan)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=rac)(CID=(PROGRAM=oracle)(HOST=racattackstandby.racattack)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 -
Production
Time: 20-FEB-2017 07:37:30
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
***********************************************************************
(Alert log at primary (Db unique_name - standby)
Fatal NI connect error 12514, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=racattack-cluster-scan)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=rac)(CID=(PROGRAM=oracle)(HOST=racattackstandby.racattack)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 -
Production
Time: 20-FEB-2017 07:37:30
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Error 12514 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'rac'. Error is 12514.
------------------------------------------------------------------------------------------(Broker
log at primary)--------------------------------------------------------
02/20/2017 07:35:30
Redo transport problem detected: redo transport for database rac has the
following error:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
Data Guard Broker Status Summary:
Type Name Severity
Status
Configuration haconfig Warning
ORA-16607
Primary Database standby Error
ORA-16778
Physical Standby Database rac Success
ORA-00000
02/20/2017 07:35:58
Redo transport problem detected: redo transport for database rac has the
following error:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
Data Guard Broker Status Summary:
Type Name Severity
Status
Configuration haconfig Warning
ORA-16607
Primary Database standby Error
ORA-16778
Physical Standby Database rac Success
ORA-00000
02/20/2017 07:36:25
Redo transport problem detected: redo transport for database rac has the
following error:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
02/20/2017 07:36:45
Redo transport problem detected: redo transport for database rac has the
following error:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
Data Guard Broker Status Summary:
Type Name Severity
Status
Configuration haconfig Warning
ORA-16607
Primary Database standby Error
ORA-16778
Physical Standby Database rac Success
ORA-00000
02/20/2017 07:37:46
Redo transport problem detected: redo transport for database rac has the
following error:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
Data Guard Broker Status Summary:
Type Name Severity
Status
Configuration haconfig Warning
ORA-16607
Primary Database standby Error
ORA-16778
Physical Standby Database rac Success
ORA-00000
02/20/2017 07:38:45
Redo transport problem detected: redo transport for database rac has the
following error:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
Data Guard Broker Status Summary:
Type Name Severity
Status
Configuration haconfig Warning
ORA-16607
Primary Database standby Error
ORA-16778
Physical Standby Database rac Success
ORA-00000
02/20/2017 07:39:45
Redo transport problem detected: redo transport for database rac has the
following error:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
Data Guard Broker Status Summary:
Type Name Severity
Status
Configuration haconfig Warning
ORA-16607
Primary Database standby Error
ORA-16778
Physical Standby Database rac Success
ORA-00000
Fatal NI connect error 12514, connecting to:
------------------------------------------------------------------------------------------
Can anyone kindly assist ?
Appreciate your assistance & cooperation .
Best Regards,
Sandip
On Mon, Feb 20, 2017 at 6:25 AM, Andrew Kerber <andrew.kerber@xxxxxxxxx>
wrote:
In the trace directory there will be the alert log and one other log file,
call drc<something>.log. This is the dataguard broker log file, and should
list the specific errors. Also, in dataguard broker you should be able to
run the command show database verbose 'standby'; That should give the
specific error message. Once you get the specific error messages, you
should be able to fix it or ask the list again.