Home » Server Options » Data Guard » not able to get data of primary in standby database (dataguard) (11g R1, windows 7(64bit))
not able to get data of primary in standby database (dataguard) [message #574866] Wed, 16 January 2013 05:11 Go to next message
mohib3088
Messages: 1
Registered: January 2013
Junior Member

Hi all,
i have configured physical standby in my local system, to check logshipping i created a table at primary db, wen i tried to check in standby, it says table does not exist..
below are primary & standby alert entries..

Primary alert log

Fatal NI connect error 12514, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.0.98)(PORT=1522))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=STAND)(SERVER=dedicat ed)(CID=(PROGRAM=d:\oracle11g\app\administrator\product\11.1.0\db_1\bin\ORACLE.EXE)(HOST=A960M)(USER=SYSTEM))(SERVER=dedicated)))

VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Time: 16-JAN-2013 16:20:12
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
Errors in file d:\oracle11g\app\administrator\diag\rdbms\prod\prod\trace\prod_arcm_8836.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
PING[ARCm]: Heartbeat failed to connect to standby 'STAND'. Error is 12514.
Wed Jan 16 16:25:13 2013


Standby alert log

ARCg: Thread not mounted
Wed Jan 16 15:17:26 2013
ARC9: Thread not mounted
Wed Jan 16 15:17:26 2013
ARCm: Thread not mounted
Wed Jan 16 15:32:24 2013
db_recovery_file_dest_size of 4096 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed Jan 16 16:17:48 2013
alter database recover managed standby database disconnect from session
Wed Jan 16 16:17:48 2013
MRP0 started with pid=18, OS id=5884
Fast Parallel Media Recovery enabled
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 5 processes
Waiting for all non-current ORLs to be archived...
Clearing online redo logfile 1 D:\ORACLE11G\APP\ADMINISTRATOR\ORADATA\STAND\REDO01.LOG
Completed: alter database recover managed standby database disconnect from session
Clearing online log 1 of thread 1 sequence number 145
Clearing online redo logfile 1 complete
Clearing online redo logfile 2 D:\ORACLE11G\APP\ADMINISTRATOR\ORADATA\STAND\REDO02.LOG
Clearing online log 2 of thread 1 sequence number 146
Clearing online redo logfile 2 complete
Clearing online redo logfile 3 D:\ORACLE11G\APP\ADMINISTRATOR\ORADATA\STAND\REDO03.LOG
Clearing online log 3 of thread 1 sequence number 144
Wed Jan 16 16:17:59 2013
Clearing online redo logfile 3 complete
Media Recovery Waiting for thread 1 sequence 146
Wed Jan 16 16:19:41 2013
alter database open read only
ORA-1154 signalled during: alter database open read only...
Re: not able to get data of primary in standby database (dataguard) [message #574882 is a reply to message #574866] Wed, 16 January 2013 08:44 Go to previous message
Michel Cadot
Messages: 68624
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
 *Cause:  The listener received a request to establish a connection to a
 database or other service. The connect descriptor received by the listener
 specified a service name for a service (usually a database service)
 that either has not yet dynamically registered with the listener or has
 not been statically configured for the listener.  This may be a temporary
 condition such as after the listener has started, but before the database
 instance has registered with the listener.
 *Action:
  - Wait a moment and try to connect a second time.
  - Check which services are currently known by the listener by executing:
    lsnrctl services <listener name>
  - Check that the SERVICE_NAME parameter in the connect descriptor of the
    net service name used specifies a service known by the listener.
  - If an easy connect naming connect identifier was used, check that
    the service name specified is a service known by the listener.
  - Check for an event in the listener.log file.

ORA-01154: database busy. Open, close, mount, and dismount not allowed now
 *Cause: Some operation is in progress that expects the opened/mounted state
           of this instance to remain the same.
 *Action: Wait for the operation to complete then retry. If attempting to
           do a shutdown, SHUTDOWN ABORT will work.  If this is a shutdown
         of a standby database that is operating in NO DATA LOSS mode, you
         must shutdown the primary database first.

Regards
Michel
Previous Topic: Issue in finding logs applied on Standby database
Next Topic: refresh primary using standby database
Goto Forum:
  


Current Time: Thu Mar 28 05:39:51 CDT 2024