Reg:Primary Database

Hello
In my primary database i have a problem
I checked the switchover_status it resulted in "not allowed"
how to make it as "To Standby"

Can you run this query and post the results?
http://www.visi.com/~mseberg/monitor_data_guard_transport.html
"not allowed" generally means you have a gap. The query should provide the first clues.
If you are using Standard Edition then this isn't really Data Guard, its a poor mans copy of the database and you should not expect it to have Data Guard features.
This is also the default for databases not using Data Guard.
Checking switchover status
SWITCHOVER_STATUS
NOT ALLOWED Best Regards
mseberg
Edited by: mseberg on Aug 6, 2012 12:24 PM

Similar Messages

Error: is not a primary database file.

Hello
If I try to set a database online with:
ALTER DATABASE mydb SET online
this error occurs:
Msg 5171, Level 16, State 1, Line 1
E:\Data\mydb_log.ldf is not a primary database file.
Msg 5171, Level 16, State 2, Line 1
E:\Data\mydb.mdf is not a primary database file.
File activation failure. The physical file name "E:\Data\mydb.mdf" may be incorrect.
Msg 945, Level 14, State 2, Line 1
Database 'mydb' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
The path of ldf and mdf file is correct.
And if I delete the database "DROP DATABASE mydb" and attach the files, then it works..
Thanks for your help

Cause
This problem generally occurs if the MDF file of your SQL Server has got damaged. the problem could be due to file header corruption or wrong information in file header.
All such situations lead to the inaccessibility of MDF file and need to repair and restore the database. It is very important to work around this problem, as it may put your business at risk of destruction.
The MDF repair is possible with the help of third party applications known as SQL recovery software. These software are helpful in each and every case of MDF corruption and thus allow you to have perfect MDF recovery.
To perform SQL repair using these software, it is not necessary for the user to have sound technical knowledge as MDF repair software come with interactive user interface. SQL recovery software do systematic scan of corrupted MDF files, repair and restore them in original format.
Stellar Phoenix SQL Database Recovery is the most advanced and the most influential SQL recovery software which allows you to have effective and successful MDF recovery in all cases of corruption. This SQL repair software comes equipped with an interactive, simple and cool looking user interface.
This MDF repair software is powerful enough to carry out systematic scan of entire MDF file and extract all of the data from it. This SQL repair software can restore all of the MDF objects including tables, reports, forms, macros, database constraints, stored procedures, triggers etc.
Cheers, Sridhar -------------- Please Mark it as Answer if it helps u so that it will be useful to other forum guys

Why do we need standby redo log on Primary database.

Hi Gurus,
I was going through the document in OBE,
http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
I have two queries:
1) I noticed the statement -
"Configure the primary database to receive redo data, by adding the standby logfiles to the primary. "
Why do we have to create standby redo log on a primary database?
2) There is another statement --
"It is highly recommended that you have one more standby redo log group than you have online redo log groups as the primary database. The files must be the same size or larger than the primary database’s online redo logs. "
Why do we need one additional standby redo log group than in Primary database.
Could anyone please explain to me in simple words.
Thanks
Cherrish Vaidiyan

Hi,
1. Standby redo logs are used only when the database_role is standby, it is recommended to be added in primary also so that they can be used on role reversal, however during normal working standby redo logs will not be used at all on primary.
2. In case of 3 online redo log groups, it is recommended to use 4 standby redo log group this is in case if log switching is happening frequently on primary and all 3 standby redo logs are still not completely archived on the standby and 4th can be used here as there will be some delay on standby due to network or slowness of arch on standby.
Use of the standby redo log groups depends on the redo generation rate, you can see only 2 standby redo logs are getting used while you have 4 standby redo log groups, when the redo generation rate is less.
So it is recommended to have one more standby redo log group when redo generation rate is high and all of the existing standby redo log group are getting used.
Regards
Anudeep

Is the only way to import large amount of data and database objects into a primary database is to shutdown the standby, turn off archive log mode, do the import, then rebuild the standby?

I have a primary database that need to import large amount of data and database objects. 1.) Do I shutdown the standby? 2.) Turn off archive log mode? 3.) Perform the import? 4.) Rebuild the standby? or is there a better way or best practice?

Instead of rebuilding the (whole) standby, you take an incremental (from SCN) backup from the Primary and restore it on the Standby. That way, if, for example
a. Only two out of 12 tablespaces are affected by the import, the incremental backup would effectively be only the blocks changed in those two tablespaces (and some other changes in system and undo) {provided that there are no other changes in the other ten tablespaces}
b. if the size of the import is only 15% of the database, the incremental backup to restore to the standby is small
Hemant K Chitale

Error in primary database alert log

Dear all i am getting the following error in my primary database alert log
oracle 10.2.0.3
Os/ rhel 4
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:20:37 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Tue Jul 7 23:25:38 2009
Errors in file /u01/app/oracle/admin/PROSVR1/bdump/prosvr1_arc0_26151.trc:
ORA-00088: command cannot be executed by shared server
Tue Jul 7 23:25:38 2009
PING[ARC0]: Heartbeat failed to connect to standby 'DRSVR1'. Error is 88.
Please let me know what needs to be done.
THanks in advance,
Aj

00088, 00000, "command cannot be executed by shared server "
// *Cause: Debug command issued on shared server.
// *Action: Reissue the command using a dedicated server.

Delete standby redo log from primary database

Hi all,
I'm trying to drop standby logfiles on primary database (other database that I'm configuring the DG).
The members of the standby log groups don't exists on file system.
Somebody have deleted these files. Its old configuration where the files were in file system. Now they are in ASM.
When I try to drop the standby logfiles I got the following error:
SQL> alter database clear logfile group 7;
alter database clear logfile group 7
ERROR at line 1:
ORA-19528: redo logs being cleared may need access to files
SQL> select * from v$logfile order by 1;
    GROUP# STATUS TYPE    MEMBER                                                                           IS_
         1         ONLINE +REDO1/proj/onlinelog/group_1.256.340558657                                     NO
         1         ONLINE +REDO2/proj/onlinelog/group_1.256.340558659                                     NO
         2         ONLINE +REDO1/proj/onlinelog/group_2.257.340558879                                     NO
         2         ONLINE +REDO2/proj/onlinelog/group_2.259.340558879                                     NO
         3         ONLINE +REDO1/proj/onlinelog/group_3.258.340558707                                     NO
         3         ONLINE +REDO2/proj/onlinelog/group_3.257.340558709                                     NO
         4         ONLINE +REDO2/proj/onlinelog/group_4.258.340558713                                     NO
         4         ONLINE +REDO1/proj/onlinelog/group_4.259.340558711                                     NO
         5         ONLINE +REDO2/proj/onlinelog/group_5.260.340558965                                     NO
         5         ONLINE +REDO1/proj/onlinelog/group_5.260.340558963                                     NO
         6         ONLINE +REDO1/proj/onlinelog/group_6.261.340558967                                     NO
         6         ONLINE +REDO2/proj/onlinelog/group_6.261.340558967                                     NO
         7         STANDBY /oracle/proj/onlinelog2/redo_702.log                                            NO
         7         STANDBY /oracle/proj/onlinelog1/redo_701.log                                            NO
         8         STANDBY /oracle/proj/onlinelog2/redo_802.log                                            NO
         8         STANDBY /oracle/proj/onlinelog1/redo_801.log                                            NO
         9         STANDBY /oracle/proj/onlinelog2/redo_902.log                                            NO
         9         STANDBY /oracle/proj/onlinelog1/redo_901.log                                            NO
        10         STANDBY /oracle/proj/onlinelog1/redo_1001.log                                           NO
        10         STANDBY /oracle/proj/onlinelog2/redo_1002.log                                           NO
20 rows selected.
SQL> select * from v$standby_log order by 1;
    GROUP# DBID            THREAD# SEQUENCE#      BYTES       USED ARC STATUS     FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
         7 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
         8 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
         9 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
        10 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0What can I do to drop these reference?
Any other solution instead of edit the controlfile and stop/start tghe database?
thank you!!!!

Hello;
Well Oracle thinks the files are there, but I remember a bug on metalink where the controlfile still had them, but they were not on the file system. Can you confirm they exist?
Meanwhile I check my notes for the Oracle doc nunber.
Bug 6128242: TRYING TO DROP STANDBY LOG FAILS WITH ORA-19528
So if you are Oracle 10 this might be the issue.
workaround is to re-create the controlfile without the incorrect logfile. ( Yuk!! )
ORA-01156 When Adding Or Dropping Redo Logs [ID 452152.1]
Best Regards
mseberg
Edited by: mseberg on Oct 31, 2011 5:09 PM

Use of standby redo log files in primary database

Hi All,
What is the exact use of setting up standby redo log files in the primary database on a data guard setup?
any good documents?

A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.
refer the link,and Perform the following steps to configure the standby redo log.:-
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
If the real-time apply feature is enabled, log apply services can apply redo data as it is received, without waiting for the current standby redo log file to be archived. This results in faster switchover and failover times because the standby redo log files have been applied already to the standby database by the time the failover or switchover begins.
refer the link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1023371

Creating standby database and replication of primary database in 9i

Hi,
We have a 9i database on Windows Server.Now recently we are planning to replicate the primary database to standby database once after creating the standby database.Can anyone guide me with the procedure or documentation with this . We were asked to do this without the data guard set-up. Please do help me regarding this ASAP.
Regards,

specifiying ASAP isnt a way to get people to help on a volunteer forum.
If you dont have dataguard You need to search for "manual standby apply".
lots and lots and lots of google hits for you but this is the official cookbook
http://docs.oracle.com/cd/B10500_01/server.920/a96653/manual_recovery.htm

RAW primary database and ASM standby database

Hi,
I would like to know if it is possible to have a ASM standby database for a primary database which is on RAW files.Is there any changes in procedure for a switchover to DR site.

Sekar_BLUE4EVER wrote:
Hi,
I would like to know if it is possible to have a ASM standby database for a primary database which is on RAW files.Is there any changes in procedure for a switchover to DR site.Yes, you can. and there is no change in procedure for switchover.
for creation of standby DB, consider these parameters: db_create_file_dest,db_recovery_file_dest,control_files
see an example here: http://pythianpang.wordpress.com/2010/02/18/data-guard-non-asm-primary-to-asm-physical-standby/
HTH
Tobi
Edited by: teits on Nov 20, 2012 12:13 PM

SECURITY PATCH ON STANDBY DATABASE AND PRIMARY DATABASE

I have a question on applying CPU on standby and primary database
I have a standby database on machine2 and primary on machine1
I applied a CPU patch on the Oracle Home of Standby database and
did not run the catcpu.sql as standbydatabase is in mount state.
Now i am going to apply the CPU patch on primary database.
What i need to confirm is that after i apply the patch on primary database oracle home
and run the cat cpu.sql on that do i have to do anything on the standby database
for instance rebuilding it or something or the change would be shipped to the standby
server automatically.
The purpose is to have the primary and standby database on the same patch level
in case of a failover
Please let me know asap

Any one has any idea on this. Any ideas would be appreciated

The observer only reinstate the old primary database after startup it twice

I use Oracle 11g r2 configure a data guard and fast_start fail over (using data guard broker) environment on linux.
The data guard works fine, and the fail over too.
The problem is that after fail over, the observer can't reinstate the old primary database to new standby database after start up it to mount, and what strange is that if shutdown (immediate) it again, and start up it to mount again, the reinstating can be completed automatically and successfully.
I use 'shutdown abort' to simulate the database crash.
Any one have some advice? Thanks in advance!
Edited by: user1665703 on 2011-7-27 下午4:33

There are some strange log in drcorcl.log,
2011-07-27 16:30:57.702 RSM0: HEALTH CHECK ERROR: ORA-16808: primary database is not open
2011-07-27 16:30:57.844 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.844 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property LogXptMode found
ORA-16777 error
2011-07-27 16:30:57.845 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.845 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.845 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property DelayMins found O
RA-16777 error
2011-07-27 16:30:57.845 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.846 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.846 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property Binding found ORA
-16777 error
2011-07-27 16:30:57.846 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.847 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.847 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property MaxFailure found
ORA-16777 error
2011-07-27 16:30:57.847 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.848 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.848 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property MaxConnections fo
und ORA-16777 error
2011-07-27 16:30:57.848 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.849 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.849 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property ReopenSecs found
ORA-16777 error
2011-07-27 16:30:57.849 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.849 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.850 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property NetTimeout found
ORA-16777 error
2011-07-27 16:30:57.850 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.850 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.850 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property RedoCompression f
ound ORA-16777 error
2011-07-27 16:30:57.851 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb

Change DBID for primary database

Hello All,
We are have Quality and Production database. The quality database has a active DR setup and the standby database is in sync with the primary.
Now we have a issue, Production and Quality have a same DBID (quality was refreshed with production's database with SAP tools) due to which we are unable to register it to RMAN catalog.
The question I have is, lets say I change the DBID using the NID tool, using NID tool will perform "alter database open resetlogs" and it means old backups will be void and new redo logs will generate.
Will this affect/invalidate the standby database because of the open reset logs statement? Do I need to rebuild the standby database after changing the DBID of primary database?
Thanks all in advance.
Regards,
Bala

you cannot have different DBID for production and standby databases, physical standby is a exact replica, so DBID will also be same.
Yes, if you change the DBID of primary , you will have to rebuild the standby database which will have same DBID again
About Standby Database Registration
.http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmcatdb.htm#BRADV89654

Unable to delete primary database archivelogs using RMAN

Hi,
rman unable to delete the archivelogs of primary database even it is in sync ( with standby database).
giving an error :-
archive log filename=+FLASH/simsval/archivelog/2012_05_24/thread_2_seq_1693.11359.784134169 thread=2 sequence=1693
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=+FLASH/simsval/archivelog/2012_05_24/thread_2_seq_1694.5554.784135415 thread=2 sequence=1694
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=+FLASH/simsval/archivelog/2012_05_24/thread_2_seq_1695.11643.784164901 thread=2 sequence=1695
RMAN-08137: WARNING: archive log not deleted as it is still needed
archive log filename=+FLASH/simsval/archivelog/2012_05_24/thread_2_seq_1696.12654.784164913 thread=2 sequence=1696
archive gap showing at primary.
SQL> select to_char (sysdate,'DD-MON-YYYY HH24:MI') as "Now", a.thread#, max(a.sequence#) as "Latest" ,max(b.sequence#) as "Last", max(a.sequence#)-max(b.sequence#) as "To Apply",to_char ( max (b.next_time), 'YYYY-MON-DD HH24:MI') as "LastDate",round ((sysdate - max (b.next_time) ) * 24 * 60, 0) as "Mins Behind" FROM V$ARCHIVED_LOG a , V$ARCHIVED_LOG b where a.applied = 'NO'and b.applied = 'YES' and a.thread# = b.thread# group by a.thread#, a.applied, b.thread#, b.applied order by a.thread#;
Now THREAD# Latest Last To Apply LastDate Mins Behind
01-JUN-2012 00:57 1 2321 2195 126 2012-APR-25 22:34 51983
01-JUN-2012 00:57 2 1729 1576 153 2012-APR-26 15:11 50985
no archive gap showing at standby .
SQL> select to_char (sysdate,'DD-MON-YYYY HH24:MI') as "Now", a.thread#, max(a.sequence#) as "Latest" ,max(b.sequence#) as "Last", max(a.sequence#)-max(b.sequence#) as "To Apply",to_char ( max (b.next_time), 'YYYY-MON-DD HH24:MI') as "LastDate",round ((sysdate - max (b.next_time) ) * 24 * 60, 0) as "Mins Behind" FROM V$ARCHIVED_LOG a , V$ARCHIVED_LOG b where a.applied = 'NO'and b.applied = 'YES' and a.thread# = b.thread# group by a.thread#, a.applied, b.thread#, b.applied order by a.thread#;
Now THREAD# Latest Last To Apply LastDate Mins Behind
01-JUN-2012 04:59 1 2321 2321 0 2012-MAY-31 22:32 386
01-JUN-2012 04:59 2 1729 1729 0 2012-MAY-31 22:32 386
any one please help me to resolve this.
thanks ,
Badam.
Edited by: 937988 on May 31, 2012 9:56 PM

Can you past here log_archive_ parameter on primary database?
Did you create data guard configuration with dgmgrl ?
Mahir M. Quluzade
www.mahir-quluzade.com

Primary Database and Standby Database sync

How to know that standby database is in sync with primary database?

Query the V$LOG_HISTORY view on the standby database, which records the latest log sequence number that has been applied. For example, issue the following query:
SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
2> FROM V$LOG_HISTORY
3> GROUP BY THREAD#;
THREAD# LAST_APPLIED_LOG
1 967In this example, the archived redo log with log sequence number 967 is the most recently applied log.
You can also use the APPLIED column in the V$ARCHIVED_LOG fixed view on the standby database to find out which log is applied on the standby database. The column displays YES for the log that has been applied. For example:
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
THREAD# SEQUENCE# APP
1 2 YES
1 3 YES
1 4 YES
1 5 YES
1 6 YES
1 7 YES
1 8 YES
1 9 YES
1 10 YES
1 11 NO

Create Primary Database from DR database backup

Hi Experts
I got the requirement as follows:
Build Production database using DR backup.
When I am creating the Production database(Primary Database),I tried with the Duplicate command to create the primary database using DR backup.It is failing at the control file creation.
Script used:
I am executing this script on Primary server:
Rman target sys/***@DR auxiliary /
run
allocate channel c1 device type disk sbt_tape;
allocate channel c2 device type disk sbt_tape;
NB_ora_client...,nb_ora_policy.....,
dupilicate target database to PR;
relaease channel c1;
exit
So can any body tell me is there any way to create the Primary Database from DR backup.
Also please refer me to some documents in cloning the Primary database from production database.
Thanks
Veera

Please note that "So can any body tell me is there any way to create the Primary Database from DR backup" this is with Duplicate command.
I know how to do with Restore command.If some body refers to the Documentation using Restore database is also highly appreciated.
Thanks in advance
Veera

Reg:Primary Database

Similar Messages

Maybe you are looking for