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

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

Use of non-migratable database link not allowed in OSB

Hi All,
I have a procedure in which tables are invoked using Database links.
Now I have created a business service which uses this procedure. However I am getting below error
The invocation resulted in an error: Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/E2xInterface_V1/WSDL/GetEWOStatus [ GetEWOStatus_ptt::GetEWOStatus(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'GetEWOStatus' failed due to: Stored procedure invocation error.
Error while trying to prepare and execute the SP_GETEWOSTATUS API.
An error occurred while preparing and executing the SP_GETEWOSTATUS API. Cause: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-24777: use of non-migratable database link not allowed
can we use dblink in procedure while accessing through business service. Please let me know.
Thanks
Chandana

hello gurus . i have same problem on my stored procedure what is a non xa datasource. how can i create on my weblogic server

Field exit showing---not allowed to change cross client customizing

hi all ,
when im trying to activate field exit . Its showing---not allowed to change cross client customizing.
how to correct that.
thanks in advance.
sg

hi SG,
first and foremost thing while using field exit is, ask your basis person to include the parameter abap/fieldexit = Y in your instance profile.
Otherwise u can't use the field exits.
Regards....
Arun.
Reward points if useful.

Use of non-migratable database link not allowed ERROR

Hello,
We have a notification process (on disabled user) in OIM that needs to connect to a schema in another instance to check some information before the notification is sent out.
We have OIM in an instance A and the other schema lives in the instance B. We created a database link from A to B, some synonyms, and grant the right permissions for OIM to select the tables in the schema on instance B.
We can login to OIM using SQL Developer and execute the query without any problems.
However, when the query is executed in the Disable User process task, we got the error:
java.sql.SQLException: ORA-24777: use of non-migratable database link not allowed
We tried to create a view in OIM that is similar to the one that lives in the schema in instance B. However, the same error exists.
How can we work around this error?
Thanks

with all the info you have put here all I can say is : (with some help from google ;-) )
ORA-24777: use of non-migratable database link not allowed
Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multi threaded server process.
Action: Perform the work in the local database or open a connection to the remote database from the client. If multi threaded server option is installed, connect to the Oracle instance through the dispatcher.

Use of non-migratable database link not allowed - weblogic

Can somebody help me with this error?
The application use an entity bean for a view that use a dblink for accesing a table from another oracle database.
Thank you.
javax.ejb.EJBException: EJB Exception: ; nested exception is:
     Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-24777: use of non-migratable database link not allowed
Error Code: 24777
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.unwrapRemoteException(RemoteBusinessIntfProxy.java:120)
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:102)
     at $Proxy190.queryVCommentMonitoring(Unknown Source)
     at ro.uct.capone.viewcontroller.Utils.getStatus(Utils.java:36)
     at ro.uct.capone.viewcontroller.forms.WatchListForm.validate(WatchListForm.java:114)
     at org.apache.struts.action.RequestProcessor.processValidate(RequestProcessor.java:942)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:255)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-24777: use of non-migratable database link not allowed

I've gotten past this by creating the dblink as SHARED.
The SQL is
CREATE SHARED DATABASE LINK "yourlink"
CONNECT TO "dbuser" IDENTIFIED BY "dbuserpassword"
AUTHENTICATED BY "dbuser" IDENTIFIED BY "dbuserpassword"
USING 'databasename';
note the quote character use.
You can also use SQL Developer to adjust this.
This does depend on shared database connections between your db's.

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.

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 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.

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.

How to automatically "show" not "allow" on timeline?

I want it to be in that little header section (lives, studied- that little box) with the spotify logo that says I listened to yadda yadda. Automatically! It only shows up like that if you change it to "show on timeline" not "allow," correct? So how can I make this automatic? It appears I have to individually change the setting for each different song and that is just ridiculous! I'm sure there's another way!!!
And with the shown on timeline option, it won't post in the newsfees correct? I don't want to bombard everyone's newsfees with what I'm listening to, just want it to be available on the page.

For Music:
Settings > Music > turn off Show All Music
For Videos:
Settings > Videos > turn off Show All Videos

Standby database showing open resetlogs/we dont want to resetlogs

Dear All,
I created standby database from cold backup in oracle 8.0.5/sunsolaries
After appling archivelog from primary database i am tring to open in read/readwrite mode
but its asking to resetlogs.
I want to avoide resetlogs and open the database how i can?
Regads,
sami

Hi Sami,
It may be due to redo logs are not applied in standby so apply them as well and then try to open a database. Did you create controlfile from primary as standby? I mean did you use below command?
alter database create standby controlfile as '<location'; so without that it'll think that it's primary database. Change init.ora files accordingly. Are you creating a duplicate database or standby database?
Thanks,
Keyur

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;
}

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.

Switchover_status in standby database showing NOT ALLOWED

Similar Messages

Maybe you are looking for