How to migrade DMT to LMT in standby database?

Hi,
I plan to migrate my existing tablespace from Dictionary Manage to Local Managed.
I have my Production and a DR Server act as standby DB server.
If i perform the DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL to the tablespace in Production. Will the activity recorded in the archive-log and able sycn with the DR Server automatically?
or i need to perform it manually in DR.
Thanks.

Yes it will propagate to your DR.

Similar Messages

How to apply archivelog with gap on standby database

Hi All,
Oracle Database version : 9.2.0.6
Following is my sequence of commands on standby database.
SQL>alter database mount standby database;
SQL> RECOVER AUTOMATIC STANDBY DATABASE UNTIL CHANGE n;
ORA-00279: change 809120216 generated at 07/24/2006 09:55:03 needed for thread
1
ORA-00289: suggestion : D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC
ORA-00280: change 809120216 for thread 1 is in sequence #19921
ORA-00278: log file 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' no longer
needed for this recovery
ORA-00308: cannot open archived log
'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
I have check the last sequence# on standby database which is 19921. And I have archivelog starting from sequence# 20672 onwards. When I am trying to apply archive log starting from sequence# 20672 , it is searching for 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' file and cancel the recovery. Please note that I don't have those missing archive on Primary server as well. So How can I apply the remaining archive log which I do have from 20672 onwards.
I hope I am not creating any confusion.
Thx in advance.

Hi Aijaz,
Thx for your answer. But my scenario is bit complex. I have checked my standby database status which is not running in recovery mode. I have tried to find archive_gap which is 0 on standby server. I am copying all archived log from primary to standby thru the script every 2 hour and appying them on standby. After applying, the script is removing all applied log files from primary as well as standby. So it is something like I have archivelog from 1,2,3,7,8,9,10. So 4,5 and 6 archivelog are missing which is required when I am trying to recover standby database. Also note that I want to apply 7,8,9,10. I will loose some data from those missing archive but I have cold back any way. I don't have those missing archivelog files(4,5 and 6) anywhere at all. So how can I recover standby database. I am using standby just for the backup purpose.
I hope my question is clear now.
Thx in advance
- Mehul

How will you find out no of standby databases configured for primary database from OS level

How can find the number of standby databases configured for primary database from os level

Check the alert log.
The Alert log will always have Data Guard messages in it.
Example
cd /u01/app/oracle/diag/rdbms/primary/PRIMARY/trace
tail -1700 alert_PRIMARY.log | more
Wed Nov 13 13:35:26 2013
ARC7: Standby redo logfile selected for thread 1 sequence 1164 for destination LOG_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 1165 for destination LOG_ARCHIVE_DEST_2
If you don't see messages like this it's probably not a Data Guard system.
Or search it for :
System parameters with non-default values:
Which on Data Guard system will show things like:
log_archive_dest_1 = "LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY"
log_archive_dest_2 = "SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY"
log_archive_dest_state_1 = "ENABLE"
log_archive_dest_state_2 = "ENABLE"
fal_server = "STANDBY"
Best Regards
mseberg

How to apply the changes in logical standby database

Hi,
I am new to Dataguard. I am now using 10.2.0.3 and followed the steps from Oracle Data Guard Concepts and Administration Guide to setup a logical standby database.
When I insert a record to a table from the primary database side, when i query the same table from the logical standby database, it doesn't show the new records.
Did I miss something? What I want to do is when I insert a record in the primary db, then the corresponding record will be inserted in the standby db.
Or I totally misunderstand what Oracle data guard is? Any help are appreciated.
Denis

Hi
Can anyone help to answer me is my logical standby db have a archive gap?
SQL> SELECT APPLIED_SCN, APPLIED_TIME, READ_SCN, READ_TIME, NEWEST_SCN, NEWEST_T
IME FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN APPLIED_TIME READ_SCN READ_TIME NEWEST_SCN
NEWEST_TIME
851821 29-JUL -08 17:58:29 851822 29-JUL -08 17:58:29 1551238
08-AUG -08 08:43:29
SQL> select pid, type, status, high_scn from v$logstdby;
no rows selected
SQL> alter database start logical standby apply;
Database altered.
SQL> select pid, type, status, high_scn from v$logstdby;
PID
TYPE
STATUS HIGH_SCN
2472
COORDINATOR
ORA-16116: no work available
3380
READER
ORA-16127: stalled waiting for additiona 852063
l transactions to be applied
2480
BUILDER
ORA-16116: no work available
2492
ANALYZER
ORA-16111: log mining and apply setting
up
2496
APPLIER
ORA-16116: no work available
2500
APPLIER
ORA-16116: no work available
3700
APPLIER
ORA-16116: no work available
940
APPLIER
ORA-16116: no work available
2504
APPLIER
ORA-16116: no work available
9 rows selected.
Thanks a lot.
Message was edited by:
Denis Chan

How to apply Oracle patch when physical standby database in place

Dear All,
I want to apply Oracle patchset 8 on 10.2.0.5 when physical standby database in place. What are the steps for Primary site and for standby site.
Thanks in advance
Kamran Laeeq

Hi Kamran,
You will not upgrade or patch the standby database by importing offline redologs. On the contrary, there is a procedure to do this. Please note that you will not transitiate the role from standby to primary or startup the database. You will just startup the database by executing "startup mount" and "startup upgrade", during the upgrade. It means that you will not change database role standby to primary and you will be able to continue to the log shipment after the respective upgrade.
But, it is very important that you should stop the log shipment and apply all the offline redologs, before the upgrade. Technically, you can import offline redologs after the upgrade, by changing "compatibility" parameter in oracle, but regarding to my experiences it may cause some problems after you transitiate the role from standby to primary.
In short;
In order to stop log shipment, at the primary site;
alter system set log_archive_dest_state_2=defer;
In order to import all the offline redologs without a delay, at the standby site;
alter database recover managed standby database cancel;
alter database recover managed standby database nodelay disconnect from session;
I hope that I clarified the issue,
Best regards,
Orkun Gedik

How to change COMPATIBLE with a physical standby database?

Hello.
The obvious answer is do it on both the primary and the standby at the same time... since the reference manual says : "When using a standby database, this parameter must have the same value on both the primary and standby databases.".
However, I was wondering, I have a 10.2.0.3 DB with compatible=9.2.0.5. What will happen if I leave the parameter to 9.2.0.5 on the standby and just make the change to 10.2.0.3 on the primary? Would I be able to continue to apply the logs on the physical standby? Would I be able to open it ? (I understand that the transport won't probably work anymore and that I won't be able to switchover)
I guess those 2 questions are stupid but I haven't found any clear statement yet.
Please stay tolerant. Thank you.
Gregory
PS: I know what are the alternatives.

So the answer is obviously: We cannot do that. That completely makes sense btw. I tried with 10.2.0.1 to 10.2.0.4 and I got:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/22/2008 18:35:55
RMAN-11003: failure during parse/execution of SQL statement: alter
database recover logfile '/u01/app/oracle/oradata/WHITE/redo02.log'
ORA-00331: log version 10.2.0.4.0 incompatible with ORACLE version 10.2.0.1.0
ORA-00334: archived log: '/u01/app/oracle/oradata/WHITE/redo02.log'
I should have think about it before I asked. That would have meant we could revert the database from 10g to 9i any time... And the bootstrap changes are not stored in the redo log...
Gregory

How to delete archive logs on the standby database....in 9i

Hello,
We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
thanks,
C.

We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.From 10g there is option to purge on deletion policy when archives were applied. Check this note.
*Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]*
Still it is on 9i, So you need to schedule RMAN job or Shell script file to delete archives.
Before deleting archives
1) you need to check is all the archives are applied or not
2) then you can remove all the archives completed before 'sysdate-2';
RMAN> delete archvielog all completed before 'sysdate-2';
As per your requirement.

How standby database works

Hi!!
I have created standby database (testcat) for primary database (test) using Duplicate Command of RMAN on same server (windows XP) on Oracle 11.2 . I know how to create standby database But i don't know how and when standby database works. I checked init.ora file of standby database it contains all parameters prefixed with *. as follow
*.db_create_file_dest='F:\app\Administrator\oradata'
*.db_domain=''
*.db_recovery_file_dest='F:\app\Administrator\flash_recovery_area'
*.db_recovery_file_dest_size=10737418240
*.db_unique_name='testcat'
*.DB_NAME='test'
*.control_files="D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘'
While init.ora file of primary database contains entries like
db_create_file_dest=F:\app\Administrator\oradata
db_recovery_file_dest=F:\app\Administrator\flash_recovery_area
db_recovery_file_dest_size=4039114752
control_files="F:\APP\ADMINISTRATOR\ORADATA\TEST\CONTROLFILE\O1_MF_8TXW6QN0_.CTL"
So I want to know is
          1. IS there any difference between parameter that start with .* and start without .*
          2. Can i set db_create_file_dest parameter in init.ora of standby database to another location.
           3. How redo log will be applied to standby database when I run ALTER DATABASE RECOVER ..... command
          4. where archived log files of standby database will stored?

1. Fetch Archive Log (FAL) Client :- It requests for archived redo log files from the primary site.
That means FAL Client is required (should exist) on standby database server. Am i right here?
FAL Client is Standby database, FAL Client requre archived log from FAL Server (primary, Cascading standby database ) for Gap Resolution.
2. Fetch Archive Log (FAL) Server:- It requests for archive redo logs from FAL Client (Standby database).That means FAL Server is required (should exist) on primary database server.
If yes then, why it is required because FAL Server request for archived redo logs from standby database while on other side standby database can not have redo logs as it runs in READ ONLY Access mode (So no DML and DDL) ?.
Also primary database will be always one step ahead in terms of archive logs than standby database and hence there is no need to request for archived logs from stanby. Am i right here?
Yes you are right. Primary is newer require archived log from standby. You asked and answered.
Regards
Mahir M. Quluzade

ORA-279 signalled during recovery of standby database

Hi All,
I am preparing standby database after taking hot backup and copying those datafiles to standby,
taken controlfile standby controlfile backup from primary
mounted the standby database using standby controlfile using
startup nomount pfile='/u01/stand.ora'
alter database mount standby database;
Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
recover standby database;
But I am getting the below warning on the recovery screen...
ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
ORA-00280: change 51667629050 for thread 1 is in sequence #55118
ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
ORA-00280: change 51667703096 for thread 1 is in sequence #55119
ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
ORA-00280: change 51667767649 for thread 1 is in sequence #55120
ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
ORA-00280: change 51667831821 for thread 1 is in sequence #55121
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
needed for this recovery
and I am getting the below warning on the alert log..........
Sun Jul 5 18:37:36 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:37:36 2009
Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
Sun Jul 5 18:40:31 2009
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Sun Jul 5 18:40:31 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:40:31 2009
Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
Please suggest what to do now.............
Thanks in Advance,
Sukanta Paul.

Hi Sukanta,
I didn't really understand what the problem is...
Let me explain, hope it will be clear.
You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
The messages you see say the following:
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Configure standby database

hi all;
how many system r required to configure standby database
i m configure standby database in a single(same) system where my primary database already running.if this possible or not
i have configured my standby
but when i start "c:\sqlplus sys@orclstdy as sysdba"
then he create error ora-12154: TNS:could not resolve the connect identifier specified
and when i start with "c:\set oracl_sid=orclstdy"
sql>conn as sys/pass as sysdba
connected to an idle instance
sql> startup
ora-02778: Name given for the log directory is invalid
how can solve this problem . please reply

Hi user569791
you can configure standby to multiple destinations(up to 9 different destinations) and it is also possible to configure in same system also.
you need to create standby controlfile for Physical standby database.
check whether the standby instance run as a separate service and whether you
have an relevant entry in tnsnames.ora file. note that the db_name is same for both
sites but only the instance name differs.
Ensure that you have a
1.valid cold backup of datafiles,
2.valid standby controlfile
3.standby init parameters with db_file_name_convert and log_file_name_convert
parameters are valid
4. a special init parameter called lock_name_space need to be given when you configure standby on same site.
check all these condition and Try again.
Regards
SM

RAC Standby Database rebuild

Hi
Current 10.2.0.4 Setup is with Dataguard Broker (Unix/No OEM Setup):
Rac Primary 2node cluster
Rac Standby 2node cluster
The rac Standby Database are going to be opened read/write.
Then will require a rebuild of standby ie delete db files and duplicate db using rman
1) My questions is how do I rebuild of a rac standby database with an existing enabled dg broker?
2) Are there any documentation on the steps to follow.
3) Should the dg broker config be dropped or just disabled and if so at which stage?
Config on Rac primary should be kept to a minimum as its being used so no outage expected here.
Regards
Me

Have you given any thought to using flashback (depending on how long your standby will be open for read/write)? You could (before you open read/write) copy your dr*.dat files (broker config files), stop the broker and create a guarenteed restore point. After you have finished and ready to convert back to standby you would flashback your database to the restore point, convert back to a physical standby, restart the broker and shutdown. Restore the dr*.dat files to their location and then startup the standby. From there it should fetch the logs from the time the broker was down and catch back up.
If you would rather rebuild, again you would need to take the broker out of the equation and use RMAN to create a clone for standby and then once in place you would reconfigure the broker (may be able to just restore the dr*.dat files from before the open operation but unsure.

How to delete the foreign archivelogs in a Logical Standby database

How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?

OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923

How to delete archivelog with RMAN in the Primary and Standby database?

Hello,
I am working on Oracle 10gR2.
My question is :
How could I implement a automatized and secure way of:
1) Delete archivelogs on my PRIMARY server only when these logs are successfully TRANSFERED to all my standby databases?
2) Delete archivelogs on my STANDBY server only when these logs are sucessfully APPLIED to the database?
Thanks a lot for your help!

on 10G
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#CHDBEICE
Coskan Gundogar
http://coskan.wordpress.com

How to configure standby database in a single machine

I am in Windows XP professional and oracle 9i . I want to configure a standby database for a database called proddb in the same machine. For doing this, I created a standby controlfile. But this work for the same name standby database?. How this happen ? two database with same name possible? How to create the second database (Standby) Please help?
Shiju

The Oracle Solaris Cluster concepts guide has some information on which zone model to choose:
http://docs.oracle.com/cd/E18728_01/html/821-2682/gcbkf.html#scrolltoc
When managing a Solaris zone with the HA Zones agent, the cluster basically regards the non-global zone as a blackbox.
As such you can either start the Oracle database as part of the runlevel/SMF startup of the non-global zone, or you can use the sczsh or sczsmf component and use your own scripts to start, probe and stop the Oracle database.
Usage of the standard HA Oracle data service is not supported in combination with the HA Zones agent.
If you require a more fine grained control of services running in non-global zones, why not setup a zone cluster and then having HA Oracle failover the Oracle database between non-global zones?
Regards
Thorsten

How to create 11.2.0.2 physical standby database from 2 node RAC (11.2.0.2)

Hi,
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5
RMAN duplicate is causing problem with network and we decided to go for manual creation of the same.
Thanks in Advance..

Hi;
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5I had similar issue, what i did
1. Used source oracle_home on standby server
2. Created new asm instance and use same naming
3. I took RMAN full backup on source and move it to target
4. I edit initora file remove RAC setting and restore db(also edited listener file)
Regard
Helios

How to migrade DMT to LMT in standby database?

Similar Messages

Maybe you are looking for