Standby Database Location not listed

We have the primary database created and the primary database, server, and agent and the standby server and agent are listed in grid control targets. but when I go to create a new standby database, the standby server is not listed for selection in the list of servers to select for Standby Database Location.
The agent on the server appears to be running and uploading fine.
Windows 2003 server SP2
Oracle 10.2.0.3 on Primary
Oracle 10.2.0.2 repository
Grid Control 10.1.0.4

We don't have a standby database because the server isn't listed in the list of Standby Database Locations to choose from. We are trying to create the standby database.
We've tried to Discover the standby server but it seems to already be Discovered because it is listed as a target when all targets are displayed (target type of host).
It's almost like the grid control sees the server but for some reason feels it's inelligible to be a standby server.

Similar Messages

ORA-16821: logical standby database dictionary not yet loaded

Dear all,
I have a dataguard architecture with a primary and a standby database (for reporting stuffs). Since I upgraded physical standby to logical standby, I receive this error !
ORA-16821: logical standby database dictionary not yet loaded
If someone has an idea, should be great !!
Thanks
oldschool

Hi,
Ok I applied :
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> alter database start logical standby apply immediate;
Database altered.
SQL>
And now I received this :
ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
What does it mean to check the status report.....
I found this about monitorable status report !!
DGMGRL> show database 'M3RPT' 'StatusReport';
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16821: logical standby database dictionary not yet loaded
DGMGRL>
What can I do ?
Thanks a lot
oldschool
Edited by: oldschool on Jun 4, 2009 2:37 AM

Add new datafile to logical standby database but not in primary

Hi,
Is it ok to add a new datafile to the SYSAUX tablespace on the logical standby database but not on primary? We are running out of disk space on the partition where SYSAUX01.dbf resides so we want to add a new SYSAUX02.dbf in another partition which has space. but this will only be on the logical standby not on primary, there is still lots of space in primary. standby_file_management is MANUAL and this is LOGICAL STANDBY not PHYSICAL.
Is this possible or where there be any issues?
Thanks.

Logical Standby can differ from Primary, it can have extra tablespaces, datafiles, tables, indexes, users ...
HTH
Enrique

Standby database creation notes by metalink

Can any body send me good Standby database creation notes by metalink.

Are you wanting to see notes for physical or logical standby and what Database version and OS?
Use the knowledge browser in Metalink and click the database link in the Support Categories section on the left of the page and select Dataguard under the High Availability Section on the resulting page.

Switchover_status in standby database showing NOT ALLOWED

Hi All,
My oracle database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit on windows platform.
I need to perform switchover activity with dg_broker=TRUE.
When I checked the status of DR database I found that switchover_status is NOT ALLOWED rather than SESSION ACTIVE or TO PRIMARY.I have doubt whether switchover can be done successfully or not with this configuration?
*Parameters from spfile in production database
=======================================
maxprod.__db_cache_size=2046820352
maxprod.__java_pool_size=16777216
maxprod.__large_pool_size=16777216
maxprod.__shared_pool_size=352321536
maxprod.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\maxprod\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\bdump'
*.compatible='10.2.0.1.0'
*.control_files='D:\MaximoData\oradata\maxprod\CONTROL01.CTL','D:\MaximoData\oradata\maxprod\CONTROL02.CTL','D:\MaximoData\oradata\maxprod\CONTROL03.CTL'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\cdump'
*.cursor_sharing='EXACT'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='maxprod'
*.db_recovery_file_dest='D:\MaximoData\flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=maxprodXDB)'
*.fal_client='MAXPROD'
*.fal_server='EAMDR'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(MAXPROD,EAMDR)'
*.log_archive_dest_1='location=D:\MaximoData\Archive_Log valid_for=(all_logfiles,all_roles)'
*.log_archive_dest_2='SERVICE=EAMDR VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=EAMDR'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_archive_start=true
*.log_buffer=100000000
*.nls_language='AMERICAN'
*.open_cursors=8000
*.pga_aggregate_target=848297984
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.session_cached_cursors=20
*.sga_max_size=4294967296
*.sga_target=2550136832
*.sql92_security=TRUE
*.standby_archive_dest='D:\MaximoData\Archive_Log\standby'
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\udump'*
*Parameters from spfile in DR database
============================
maxprod.__db_cache_size=3187671040
eamdr.__db_cache_size=1073741824
maxprod.__java_pool_size=16777216
eamdr.__java_pool_size=16777216
maxprod.__large_pool_size=16777216
eamdr.__large_pool_size=16777216
maxprod.__shared_pool_size=1056964608
eamdr.__shared_pool_size=486539264
maxprod.__streams_pool_size=0
eamdr.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\EAMDR\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\bdump'
*.compatible='10.2.0.1.0'
*.control_files='D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL01.CTL','D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL02.CTL','D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL03.CTL'#Restore Controlfile
*.core_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='maxprod'
*.db_recovery_file_dest_size=10737418240
*.db_recovery_file_dest='D:\MaximoData\flash_recovery_area'
*.DB_UNIQUE_NAME='EAMDR'
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=maxprodXDB)'
*.fal_client='EAMDR'
*.fal_server='MAXPROD'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(MAXPROD,EAMDR)'
*.log_archive_dest_1='LOCATION=D:\MaximoData\Archive_Log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=EAMDR'
*.log_archive_dest_2='service=maxprod valid_for=(online_logfiles,primary_role) db_unique_name=MAXPROD'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.nls_language='AMERICAN'
*.open_cursors=8000
*.pga_aggregate_target=194967296
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=4294967296
*.sga_target=1594967296
*.standby_archive_dest='D:\MaximoData\Archive_Log\standby'
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\udump'*
I didn't find any DG_BROKER_CONFIG_FILE1, DG_BROKER_CONFIG_FILE2 parameters from spfile in both production and DR db?
Is anything missing in spfile?
When I am trying to connect with dgmgrl
DGMGRL>connect sys;
connected
DGMGRL>show configuration;
Error: ORA-16532: Data Guard broker configuration does not exist
what does it mean when dgmgrl is set to true?
I have attached PRODUCTION and DR queries outputs for better understanding.
IN PRIMARY DATABASE
SQL>select database_role from v$database;
DATABASE_ROLE
PRIMARY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
maxprod PRIMARY READ WRITE ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7793
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7834
ARCH CLOSING ARCH 7834
30 rows selected.
SQL> sho parameter log_archive_config
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)
SQL> spool off
IN SECONDARY DATABASE
SQL> select database_role from v$database;
DATABASE_ROLE
PHYSICAL STANDBY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS --------------------
NOT ALLOWED
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
EAMDR PHYSICAL STANDBY MOUNTED ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7809
ARCH CLOSING ARCH 7810
ARCH CLOSING ARCH 7812
ARCH CLOSING ARCH 7813
ARCH CLOSING ARCH 7814
ARCH CLOSING ARCH 7815
ARCH CLOSING ARCH 7816
ARCH CLOSING ARCH 7817
ARCH CLOSING ARCH 7818
ARCH CLOSING ARCH 7819
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7804
ARCH CLOSING ARCH 7805
ARCH CLOSING ARCH 7806
ARCH CLOSING ARCH 7807
ARCH CLOSING ARCH 7808
MRP0 WAIT_FOR_LOG N/A 7836
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE

Meenakshy singh wrote:
Hi All,
My oracle database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit on windows platform.
I need to perform switchover activity.When I checked the status of DR database I found that switchover_status is NOT ALLOWED rather than SESSION ACTIVE or TO PRIMARY.I have doubt whether switchover can be done successfully or not?
I have attached PRODUCTION and DR queries outputs for better understanding.
IN PRIMARY DATABASE
SQL>select database_role from v$database;
DATABASE_ROLE
PRIMARY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
maxprod PRIMARY READ WRITE ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7793
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7834
ARCH CLOSING ARCH 7834
30 rows selected.
SQL> sho parameter log_archive_config
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)
SQL> spool off
IN SECONDARY DATABASE
SQL> select database_role from v$database;
DATABASE_ROLE
PHYSICAL STANDBY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS --------------------
NOT ALLOWED
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
EAMDR PHYSICAL STANDBY MOUNTED ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7809
ARCH CLOSING ARCH 7810
ARCH CLOSING ARCH 7812
ARCH CLOSING ARCH 7813
ARCH CLOSING ARCH 7814
ARCH CLOSING ARCH 7815
ARCH CLOSING ARCH 7816
ARCH CLOSING ARCH 7817
ARCH CLOSING ARCH 7818
ARCH CLOSING ARCH 7819
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7804
ARCH CLOSING ARCH 7805
ARCH CLOSING ARCH 7806
ARCH CLOSING ARCH 7807
ARCH CLOSING ARCH 7808
MRP0 WAIT_FOR_LOG N/A 7836
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
56 rows selected.
SQL> sho parameter log_archive_config
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)
SQL> spool off
1.In this case,is switchover is possible?No
2.If not possible then what will be the next step?If the value in the SWITCHOVER_STATUS column is SESSIONS ACTIVE, identify and terminate active user or SQL sessions that might prevent a switchover from being processed.
If, after performing these steps, the SWITCHOVER_STATUS column still displays SESSIONS ACTIVE, you can successfully perform a switchover by appending the WITH SESSION SHUTDOWN clause to the
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY statement.
3.Is this will impact to our production database when switchover is not successfully perform?
4.In DR RFS is idle,why?Can you paste here log_archive_dest_n paramete which is you are using for transport?
Did you using DELAY attribute in log_archive_dest_n parameter?
Mahir

Standby database is not completing recovery.

All,
I applied a PSU to 10.2.0.4 (8576156) patch this afternoon on both the primary and standby oracle_home(s). Upon starting up the standby database, I no longer see the “media recovery waiting” message in the alert log when an archive log is sent from the primary.
Not sure if I have an issue with the patch or DG is configured or started.
Perhaps another set of eyes can lead me to an issue I am not seeing.
The standby database was started as follows:
alter database RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
Example alert log message before:
Sun Sep 13 02:20:39 2009
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Sun Sep 13 02:20:47 2009
Media Recovery Waiting for thread 1 sequence 52 (in transit) <<== NOTE
Sun Sep 13 02:20:47 2009
Recovery of Online Redo Log: Thread 1 Group 4 Seq 52 Reading mem 0
Mem# 0: /oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log
Mem# 1: /oradat2/cwsiqa2/cwsiqa2_sb_redo04_b.log
Example alert log message after:
Primary database is in MAXIMUM PERFORMANCE mode
Tue Sep 15 15:56:27 2009
RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Tue Sep 15 15:56:27 2009
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
Tue Sep 15 15:57:05 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 29772
RFS[5]: Identified database type as 'physical standby'
Tue Sep 15 16:12:56 2009
The same messages are listed in v$datagurd_status
1* select message from v$dataguard_status
SQL> /
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARC9: Becoming the 'no FAL' ARCH
ARC9: Becoming the 'no SRL' ARCH
ARC0: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 28316
RFS[1]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 28318
RFS[2]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 29693
RFS[3]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 29691
RFS[4]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 29772
RFS[5]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
I also have a “gap” that is not getting resolved.
SQL> select * from v$archive_gap
2 /
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 53 53
SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT
2* FROM V$ARCHIVED_LOG R, V$LOG L WHERE R.DEST_ID=2 AND L.ARCHIVED='YES'
SQL> /
LAST_SEQ_RECD LAST_SEQ_SENT
54 58
Any insight would be appreciated.

Problem has been resolved.

Standby database is not Sync with primary DB

Hi,
One week back I configured standby database and It was running fine.
But 2 days back(Saturday) somebody had down my standby database. Today when I mounted my database; I saw this is not sync with primary database.
Database Name :- pcs
Primary db_unique_name :- pcs
standby db_unique_name :- pcstd
Present scanerio is...
Status of Standby Database is...
SQL> startup mount;
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 1073741824 bytes
Fixed Size 2063792 bytes
Variable Size 301990480 bytes
Database Buffers 763363328 bytes
Redo Buffers 6324224 bytes
Database mounted.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
SQL> recover managed standby database disconnect from session;
Media recovery complete.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
N/A 130 0 WAIT_FOR_LOG
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /backup/bkpcs/
Oldest online log sequence 121
Next log sequence to archive 0
Current log sequence 126
Status of Primary database is..
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /data/pcs10g/archive/
Oldest online log sequence 129
Next log sequence to archive 131
Current log sequence 131
SQL>
Somebody can help me to resolve the following issues
(1). Why archive log list not showing exact log sequence number on Standby Database.
(2). How can I configure automatic archive logs apply from Live to Standby again.
Regards,

Problem has been resolved.

Standby database is not applying redo logs due to missing archive log

We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
Milivoj

On a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
}

Location not Listed in a Job Opening

Hi,
Am a beginner of Peoplesoft.
We recently set up the Mexico BU and respective locations etc. Now, when I create a new JO for Mexico region, I do not get the list of Locations. Locations where configured with the SHARE set id.
I guess am missing some relationship between the BU and the Location thro the SET ID.
Please help.
Thanks,
Chris.

Did you ran the SJT processes?
When Should the Security Processes be Run? [ID 656750.1]
If you are new to PeopleSoft have a look at the followind doc on Row Level Security.
Row Level Security Red and White Papers for HRMS 8.9 and Above. [ID 748073.1]
And maybe the most obvious solution, if the effdt of the JO prior to the effdt of the Location?
Is the location on effdt Active?

Component on database but not listed in app

I recently started a 'Create Report' wizard under one of my applications, The application is named APP_REPORT_PROTOTYPE.
I named the report RPT_USING_SESSION_STORAGE. I did not complete the 'Create Report' wizard session. As I recall, I cancelled out of the wizard before completion.
Now, when I would like to create that component under that application, I get this error message:
Error: Invalid component name: - Name already exists in the schema: APP_REPORT_PROTOTYPE. Please choose another name (WWV-13003)
The component RPT_USING_SESSION_STORAGE does not appear in the list of components under the application.
How can I delete that component name, so I can use it again?
null

Barb,
You might have clicked on the "Navigator" or "Home" icon instead of "Cancel". To delete your component "RPT_USING_SESSION_STORAGE"
follow these steps:
1) Goto your applications "APP_REPORT_PROTOTYPE".
2) Type "RPT_USING_SESSION_STORAGE" in the field next to "Find" and click "Go" button.
It will show the "RPT_USING_SESSION_STORAGE".
Now you can delete it.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Barb Spiecker ([email protected]):
I recently started a 'Create Report' wizard under one of my applications, The application is named APP_REPORT_PROTOTYPE.
I named the report RPT_USING_SESSION_STORAGE. I did not complete the 'Create Report' wizard session. As I recall, I cancelled out of the wizard before completion.
Now, when I would like to create that component under that application, I get this error message:
Error: Invalid component name: - Name already exists in the schema: APP_REPORT_PROTOTYPE. Please choose another name (WWV-13003)
The component RPT_USING_SESSION_STORAGE does not appear in the list of components under the application.
How can I delete that component name, so I can use it again?<HR></BLOCKQUOTE>
null

Databases are not listed in the DBUA

Hi There,
The DB software upgrade completed and the DBUA popped up automatically. However, the two databases that exist are not showing up in the DBUA screen. Any suggestions, how to get the databases to show?
Thanks,
J

Thank you. However, the /etc/oratab has the following:
+ASM:/licensed/oracle/product/11.2.0/grid_11_2_0_3:N
db1:/licensed/oracle/product/11.2.0/dbhome_1:N # line added by Agent
db2:/licensed/oracle/product/11.2.0/dbhome_1:N # line added by Agent
However, the weird thing is I added another line to the oratab and it picks up the new entry:
db3:/licensed/oracle/product/11.2.0/dbhome_1:N
As well, I've changed the name of an exisiting database on line 2 and it picked that up:
+ASM:/licensed/oracle/product/11.2.0/grid_11_2_0_3:N
db1:/licensed/oracle/product/11.2.0/dbhome_1:N # line added by Agent
dbmodified:/licensed/oracle/product/11.2.0/dbhome_1:N # line added by Agent
Any ideas?
Thanks,
J

EM does not show standby database in database list

Hi All,
I am little bit surprised, that i am not able to get the status of standby database or you can say that standby database is not discovered in EM whereas primary database is discovered in the EM grid control
Grid control is Oracle 10g 10.2.0.5.0
Db version :- 11.1.0
I am getting the status of both the database from DGMGRL CLI

Ok i done the troubleshooting from my own.
What i did is uninstall agent on the second machine whose db is not discovered and reinstall the agent back.
Now the problem is sorted out.
But now the problem again arises. I am able to get the status of standby database on OEM grid control. But when i try to perform change of data protection mode, i am getting error that Database standby is not discovered. This problem arise from em grid control only.
Please advice over the same.

MV Logs not getting purged in a Logical Standby Database

We are trying to replicate a few tables in a logical standby database to another database. Both the source ( The Logical Standby) and the target database are in Oracle 11g R1.
The materialized views are refreshed using FAST REFRESH.
The Materialized View Logs created on the source ( the Logical Standby Database) are not getting purged when the MV in the target database is refreshed.
We checked the entries in the following Tables: SYS.SNAP$, SYS.SLOG$, SYS.MLOG$
When a materialized view is created on the target database, a record is not inserted into the SYS.SLOG$ table and it seems like that's why the MV Logs are not getting purged.
Why are we using a Logical Standby Database instead of the Primary ? Because, the load on the Primary Database is too much and the machine doesn't have enough resources to support MV based replication. The CPU usage is 95% all the time. The appplication owner won't allow us to go against the Primary database.
Do we have to do anything different in terms of Configuration/Privileges etc. because we are using a Logical Standby Database as a source ?
Thanks in Advance.

We have a 11g RAC database in solaris OS where there is huge gap in archive log apply.
Thread Last Sequence Received Last Sequence Applied Difference
1 132581 129916 2665
2 108253 106229 2024
3 107452 104975 2477
The MRP0 process seems not to be working also.Almost 7000+ archives lag in standby if compared with primary database.
i suggest you to go with Incremental rollforward backups to make it SYNC, use this below link for step by step procedure.
http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/
Here questions.
1) Whether those archives are transported & just not applied?
2) Is in production do you have archives or backup of archives?
3) What you have found errors in alert log file?
post
SQL> select severity,message,error_code,timestamp from v$dataguard_status where dest_id=2;
4) What errors in primary database alert log file?
Also post
select     ds.dest_id id
,     ad.status
,     ds.database_mode db_mode
,     ad.archiver type
,     ds.recovery_mode
,     ds.protection_mode
,     ds.standby_logfile_count "SRLs"
,     ds.standby_logfile_active active
,     ds.archived_seq#
from     v$archive_dest_status     ds
,     v$archive_dest          ad
where     ds.dest_id = ad.dest_id
and     ad.status != 'INACTIVE'
order by
     ds.dest_id
/Also check errors from standby database.

Redo log files are not applying to standby database

Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar Lapani

Thank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks

Ora 00364,ora 00305 ora 00312 errors in standby database

hii friends i got a problem in my standby database yesterday i performed database restoration activity, restoration is done and database is in MRM modemout stage, archive gap sequence is completed and is in synchronize with primary but suddenly after some time i got in alertlog media recovery waiting for thread one and from there its is showing nothing in alert log after stoping mrm and restarting database i got few errors please check them and suggest me some solution
alert log file
RFS[87]: Assigned to RFS process 7912
RFS[87]: Identified database type as 'physical standby'
Tue Jan 4 17:12:14 2011
RFS[87]: Archived Log: '/backup/standby_archivelogs/1_87532_622555682.dbf'
Tue Jan 4 17:12:17 2011
Media Recovery Log /backup/standby_archivelogs/1_87532_622555682.dbf
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:55:35 2011
alter database recover managed standby database cancel
Tue Jan 4 17:55:38 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:55:38 2011
Errors in file /oracle/app/oracle/admin/****/bdump/*******mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:55:39 2011
Waiting for MRP0 pid 3017 to terminate
Tue Jan 4 17:55:39 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:55:39 2011
MRP0: Background Media Recovery process shutdown (****)
Tue Jan 4 17:55:40 2011
Managed Standby Recovery Canceled (****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:55:56 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:55:56 2011
Attempt to start background Managed Standby Recovery process (****)
MRP0 started with pid=16, OS id=9300
Tue Jan 4 17:55:56 2011
MRP0: Background Managed Standby Recovery process started (****)
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp09300.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:56:02 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:57:56 2011
alter database recover managed standby database cancel
Tue Jan 4 17:57:56 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:57:56 2011
Errors in file /oracle/app/oracle/admin/APMBDRDB/bdump/apmbdrdb_mrp0_9300.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:57:57 2011
Waiting for MRP0 pid 9300 to terminate
Tue Jan 4 17:57:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:57:57 2011
MRP0: Background Media Recovery process shutdown (*****)
Tue Jan 4 17:57:58 2011
Managed Standby Recovery Canceled (*****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:58:10 2011
Shutting down instance: further logons disabled
Tue Jan 4 17:58:10 2011
Stopping background process CJQ0
Tue Jan 4 17:58:10 2011
Stopping background process MMNL
Tue Jan 4 17:58:11 2011
Stopping background process MMON
Tue Jan 4 17:58:12 2011
Shutting down instance (immediate)
License high water mark = 3
Tue Jan 4 17:58:12 2011
Stopping Job queue slave processes
Tue Jan 4 17:58:12 2011
Job queue slave processes stopped
Tue Jan 4 17:58:12 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Tue Jan 4 17:58:12 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Tue Jan 4 17:58:17 2011
ARCH shutting down
ARC1: Archival stopped
Tue Jan 4 17:58:22 2011
ARCH shutting down
ARC0: Archival stopped
Tue Jan 4 17:58:24 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Jan 4 17:58:33 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =242
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 2000
sga_max_size = 3221225472
__shared_pool_size = 1006632960
shared_pool_size = 637534208
__large_pool_size = 503316480
large_pool_size = 503316480
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 3221225472
control_files = /dev/vg01/rCTRLR1, /dev/vg01/rCTRLR2, /dev/vg01/rCTRLR3
db_block_size = 8192
__db_cache_size = 1677721600
db_cache_size = 637534208
compatible = 10.2.0.1.0
log_archive_config = DG_CONFIG=(APMBPROD,APMBDRDB)
log_archive_dest_1 = LOCATION=/archive/archivelogs/ valid_for=(ONLINE_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=APMBDRDB
log_archive_dest_2 =
log_archive_dest_4 = service=APMBPROD LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=APMBPROD
log_archive_max_processes= 2
standby_archive_dest = /backup/standby_archivelogs
fal_client = APMBDRDB
fal_server = APMBPROD
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
job_queue_processes = 10
background_dump_dest = /oracle/app/oracle/admin/APMBDRDB/bdump
user_dump_dest = /oracle/app/oracle/admin/APMBDRDB/udump
core_dump_dest = /oracle/app/oracle/admin/APMBDRDB/cdump
audit_file_dest = /oracle/app/oracle/admin/APMBDRDB/adump
db_name = APMBPROD
db_unique_name = APMBDRDB
open_cursors = 300
pga_aggregate_target = 1703936000
PMON started with pid=2, OS id=9371
PSP0 started with pid=3, OS id=9373
MMAN started with pid=4, OS id=9375
DBW0 started with pid=5, OS id=9377
LGWR started with pid=6, OS id=9380
CKPT started with pid=7, OS id=9382
SMON started with pid=8, OS id=9384
RECO started with pid=9, OS id=9386
CJQ0 started with pid=10, OS id=9388
MMON started with pid=11, OS id=9390
MMNL started with pid=12, OS id=9392
Tue Jan 4 17:58:35 2011
ALTER DATABASE MOUNT
Tue Jan 4 17:58:39 2011
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=9395
Tue Jan 4 17:58:39 2011
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Tue Jan 4 17:58:39 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
ARC1 started with pid=15, OS id=9397
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Tue Jan 4 17:58:39 2011
Successful mount of redo thread 1, with mount id 3471861451
Tue Jan 4 17:58:39 2011
Physical Standby Database mounted.
Completed: ALTER DATABASE MOUNT
Tue Jan 4 17:58:51 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:58:51 2011
Attempt to start background Managed Standby Recovery process ()
MRP0 started with pid=16, OS id=9400
Tue Jan 4 17:58:51 2011
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:58:57 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 19:37:24 2011
alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:24 2011
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
Completed: alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:27 2011
Media Recovery Log /backup/standby_archivelogs/1_87533_622555682.dbf
Tue Jan 4 19:37:43 2011
Media Recovery Waiting for thread 1 sequence 87534
from here it is showing no errors or nothing in my alert log file from yesterday evening

No version number, no definition of what you mean by "standby database" and not a clue as to what you mean by "restore" or why you did it.
No help is possible at this time.
PS: We do not guess at what someone means by "MRM modemout stage" ... you need to define your terms.

Standby Database Location not listed

Similar Messages

Maybe you are looking for