Rapid clone need redo logs

Hi,
Does Rapid clone need redo log files during cloning on target host on DB tier IN 11.5.10.2?
Thanks

Hi;
Per Note: 230672.1
"Copy the Database Tier File System
Log on to the Source System Database Node as the ORACLE user.
Perform a normal shutdown of the Source System Database
Copy the Database (DBF) files from the Source to the Target System
Copy the Source Database ORACLE_HOME to the Target System
Start up the Source Applications System Database and Application Tier processes"
Step "Copy the Database (DBF) files from the Source to the Target System" I think database files means data files and redo logs both in this scope.Basicly copy all dbtier from your target
Regard
Helios

Similar Messages

Do I always need redo logs?

hi guys,
Is there a way to turn off redo logs being written to to make the database faster? I am not using ARCHIVELOGS as it is a test database, so I dont see of having any redo logs.
thanks

Hi,
No, You can't turn off the redo logs, Let’s conduct a brief summary about the redo process. When Oracle blocks are changed, including undo blocks, oracle records the changes in a form of vector changes which are referred to as redo entries or redo records. The changes are written by the server process to the redo log buffer in the SGA. The redo log buffer is then flushed into the online redo logs in near real time fashion by the log writer LGWR. (See Figure 1)
The redo logs are written by the LGWR when:
•     When a user issue a commit.
•     When the Log Buffer is 1/3 full.
•     When the amount of redo entries is 1MB.
•     Every three seconds
•     When a database checkpoint takes place. The redo entries are written before the checkpoint to ensure recover ability.
Redo log files record changes to the database as a result of transactions and internal Oracle server actions. (A transaction is a logical unit of work, consisting of one or more SQL statements run by a user.) Redo log files protect the database from the loss of integrity because of system failures caused by power outages, disk failures, and so on. Redo log files must be multiplexed to ensure that the information stored in them is not lost in the event of a disk failure. The redo log consists of groups of redo log files. A group consists of a redo log file and its multiplexed copies. Each identical copy is said to be a member of that group, and each group is identified by a number. The Log Writer (LGWR) process writes redo records from the redo log buffer to all members of a redo log group until the file is filled or a log switch operation is requested. Then, it switches and writes to the files in the next group. Redo log groups are used in a circular fashion.
Best practice tip:
Oracle recommends that redo log groups have at least two files per group, with the files distributed on separate disks or controllers so that no single equipment failure destroys an entire log group.
The loss of an entire log group is one of the most serious possible media failures because it can result in loss of data. The loss of a single member within a multiple-member log group is trivial and does not affect database operation, other than causing an alert to be published in the alert log.
Remember that redo logs heavily influence database performance because a commit cannot complete until the transaction information has been written to the logs. You must place your redo log files on your fastest disks served by your fastest controllers. If possible, do not place any other database files on the same disks as your redo log files. Because only one group is written to at a given time, there is no harm in having members from several groups on the same disk.+
Note: This is a extract of my paper: [Logging or Not Logging, This is the Question.|http://oraclenz.com/__oneclick_uploads/2008/08/redo_reduction_v_1_9.pdf]
I hope this will help you.
Regards,
Francisco Munoz Alvarez
www.oraclenz.com

Restore in noarchivelog mode ( redo log files have been dropped )

1, A full backup taken using RMAN is available on disk.
2, The current control files were NOT damaged and do not need to be restored.
3, All data files are damaged .
4, The database is in NOARCHIVELOG mode.
I restore database :
1. RMAN> STARTUP MOUNT
2. RMAN> RESTORE DATABASE;
3. RMAN> recover database;
in this step , I got the information about needing redo log files ; but the redo log
files have been dropped , what should i do ?
else
I want to know there is the command 'recover database using backup control file'
in rman or not ?
Tks

Possibly loss of data (because information in online redo logs is lost):
recover database until cancel;
(cancel immediately)
alter database open resetlogs; (to build a new set of redo logs)
It's not necessary to use a backup controlfile here.

Online redo log group needed??

hey guys!
Am about to recreate the clone file of the clone db, open it using recover it until cancel using backup controlfile and apply all necessary archive logs!
My question is, does ai need to have online redo log group of the production db? since ai have all the archive log, so ai think while recraeting the control file, online redo log group will be created too?
Thanks!

while recraeting the control file, online redo log group will be created tooWhile creating control file, online redo log group doesn't get created. After applying all the archivel logs you have to open the database with RESET LOG option and then oracle will create redo logs for you.
Best of Luck !!
Daljit Singh

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

Need to understand when redo log files content is wrote to datafiles

Hi all
I have a question about the time when redo log files are wrote to the datafiles
supposing that the database is in NOARCHIVELOG mode, and all redo log files are filled, the official oracle database documentation says that: *a filled redo log file is available
after the changes recorded in it have been written to the datafiles* witch mean that we just need to have all the redo log files filled to "*commit*" changes to the database
Thanks for help
Edited by: rachid on Sep 26, 2012 5:05 PM

rachid wrote:
the official oracle database documentation says that: a filled redo log file is available after the changes recorded in it have been written to the datafiles It helps if you include a URL to the page where you found this quote (if you were using the online html manuals).
The wording is poor and should be modified to something like:
<blockquote>
+"a filled online redo log file is available for re-use after all the data blocks that have been changed by change vectors recorded in the log file have been written to the data files"+
</blockquote>
Remember if a data block that is NOT an undo block has been changed by a transaction, then an UNDO block has been changed at the same time, and both change vectors will be in the redo log file. The redo log file cannot, therefore, be re-used until the data block and the associated UNDO block have been written to disc. The change to the data block can thus be rolled back (uncommitted changes can be written to data files) because the UNDO is also available on disc if needed.
If you find the manuals too fragmented to follow you may find that my book, Oracle Core, offers a narrative description that is easier to comprehend.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
Author: <b><em>Oracle Core</em></b>

Oracle standby/redo log file shipping keeps needing logs re-registering

Hi
We have Log File Shipping enabled and the prod system ships redo logs over to the LFS server. It's kept 24 hours behind. It usually ships the logs (and I believe automatically registers them) without issue.
EXCEPT - it keeps complaining about missing redo log files.
The file is usually there; but just needs registering with:
alter database register or replace logfile '/oracle/S1P/saparch/S1Parch1_636443_654987192.dbf';
(we found if we left out the 'or replace' it takes a very long time or even hangs)
It then plods on and applies the next... can go for another 2 or 3... or 20... but then often gets stuck again, and you need to register the next.
Can spend whole days on this...!!
We did try running a script to register the next 1365 redo logs! It failed on 4, so I ran it again... it worked on those 4, but turned up 3 others it had worked with before! HUH?!? So manually did those 3 ... fine... it carried on rolling forward... but got stuck after 10 minutes again when it hit another it reckoned needed registering (we'd already done it twice!!).
Any ideas?
Ross

Hi
We have Log File Shipping enabled and the prod system ships redo logs over to the LFS server. It's kept 24 hours behind. It usually ships the logs (and I believe automatically registers them) without issue.
EXCEPT - it keeps complaining about missing redo log files.
The file is usually there; but just needs registering with:
alter database register or replace logfile '/oracle/S1P/saparch/S1Parch1_636443_654987192.dbf';
(we found if we left out the 'or replace' it takes a very long time or even hangs)
It then plods on and applies the next... can go for another 2 or 3... or 20... but then often gets stuck again, and you need to register the next.
Can spend whole days on this...!!
We did try running a script to register the next 1365 redo logs! It failed on 4, so I ran it again... it worked on those 4, but turned up 3 others it had worked with before! HUH?!? So manually did those 3 ... fine... it carried on rolling forward... but got stuck after 10 minutes again when it hit another it reckoned needed registering (we'd already done it twice!!).
Any ideas?
Ross

When changing redo-logs on Primary, do I need to change my standby also?

Hi, I need to resize my redo logs on a primary db which has a physical standby attached. Do I need to modify this standby or will the change propagate. It seems unlikely to me.
thanx

Only clue that I have found is at
http://download-east.oracle.com/docs/cd/B12037_01/server.101/b10726/configbp.htm
Section "Use Multiplexed Standby Redo Logs and Configure Size Appropriately"
>>
The remote file server (RFS) process for the standby database writes only to an SRL whose size is identical to the size of an online redo log for the production database. If it cannot find an appropriately sized SRL, then RFS creates an archived redo log file directly instead and logs the following message in the alert log:
No standby redo log files of size <#> blocks available.
>>

Do I need to create new group for standby redo log files?

I have 10 group of redo log files with 2 members for each group for my primary database , Do I need to create new group for standby redo log files for the standby database
Group#     Members
==============
1              2
2              2
3             2
4             2
5             2
6             2
7             2
8             2
9             2
10           2
If So, The following statment is correct? or nto
ALTER DATABASE ADD STANDBY LOGFILE GROUP 1 ('D:\Databases\epprod\StandbyRedoLog\REDO01.LOG',D:\Databases\epprod\StandbyRedoLog\REDO01_1.LOG');
please correct me if am doin mistake
becuase when I issue the statment I getting error message sayin the group is already created.

Thanks John
I just find the answer
Yes, it's recomeded to add new group , for instnace If I have 10 group from 1 to 10 then the standby shoudl be from 11 to 20
Thanks I found the answer.

Need to drop a current redo log on a Standby

Oracle 11.2.0.2
I have 3 redo logs on a newly created Standby database.
SQL> SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
GROUP# ARC STATUS
1 YES UNUSED
3 NO CURRENT
2 YES UNUSED
The redo log in Group 3 needs to be dropped and recreated. How can I force a log switch on a Standby in mount mode?
SQL> alter database drop logfile group 3;
alter database drop logfile group 3
ERROR at line 1:
ORA-01623: log 3 is current log for instance ufms216 (thread 1) - cannot drop
ORA-00312: online log 3 thread 1: '/path/redo03.dbf'
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
Please help !!!
Thanks!
Dave

SAME ERROR/SITUATION
SQL> startup mount
ORACLE instance started.
Total System Global Area 1.2527E+10 bytes
Fixed Size 2231240 bytes
Variable Size 3657434168 bytes
Database Buffers 8858370048 bytes
Redo Buffers 8691712 bytes
Database mounted.
SQL> SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
GROUP# ARC STATUS
1 YES UNUSED
3 NO CURRENT
2 YES UNUSED
SQL> alter database drop logfile group 3;
alter database drop logfile group 3
ERROR at line 1:
ORA-01623: log 3 is current log for instance ufms216 (thread 1) - cannot drop
ORA-00312: online log 3 thread 1: '/a0253/d01/oradata/ufms216/redo03.dbf'
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
SQL> alter database recover managed standby database cancel;
alter database recover managed standby database cancel
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active
SQL>
HELP!

When is anything written to standby redo logs on standby database?

I am on Oracle 10.2.0.4 on HP UNIX. I have read Oracle 10.2 concepts guide on technet.oracle.com, have read may article on metalink and internet, yet I am unable to verify when anything is written to standby redo logs on stand by database.
I have a simple database reconfiguration: a primary database and one standby database.
I created primary database and set up log_archive_dest_2 to use LGWR SYNC AFFIRM
I have created standby redo logs on primary.
alter database add standby logfile GROUP
I create standby control file on primary.
I copied all the primary information to create standby database. I have put standby database in managed recovery.
I did archive log switches, I created a table and inserted information in table.
I never saw standby redo logs updated on standby database by looking at timestamp of standby redo log files.
I then setup database in maximum availability mode by running following on primary:
Alter database set standby database to maximize availability
When I do insert into my tables, I do see standby redo log files on primary database being updated, but I have never seen standby redo logs on standby database updated. Why?
I am still at loss when actually standby redo logs are updated on standby database.
When I read Oracle 9i database documentation on data guard, it says that you do not need standby redo logs on primary instead you need them on standby. Only reason, you need them on primary is from primary changes role to standby database, so standby redo logs on standby database should be updated instead of standby redo logs on primary.

What is the PROTECTION_MODE ,PROTECTION_LEVEL values of your database.
As per metalink:--
Create standby redo log files, if necessary:
Standby redo logs are necessary for the higher protection levels such as
Guaranteed, Instant, and Rapid. In these protection modes LGWR from the
Primary host writes transactions directly to the standby redo logs.
This enables no data loss solutions and reduces the amount of data loss
in the event of failure. Standby redo logs are not necessary if you are using
the delayed protection mode.
If you configure standby redo on the standby then you should also configure
standby redo logs on the primary database. Even though the standby redo logs
are not used when the database is running in the primary role, configuring
the standby redo logs on the primary database is recommended in preparation
for an eventual switchover operation.
Standby redo logs must be archived before the data can be applied to the
standby database. The standby archival operation occurs automatically, even if
the standby database is not in ARCHIVELOG mode. However, the archiver process
must be started on the standby database. Note that the use of the archiver
process (ARCn) is a requirement for selection of a standby redo log.
METALINK ID:- Doc ID: Note:219344.1
Edited by: Anand... on Sep 15, 2008 2:15 AM

Cloning Oracle Applications Release 12 with Rapid Clone

Hi,
I was going through metalink doc 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone.
I couldn't understand a few points.
I would appreciate if someone can guide me regarding the following queries.
There is a statement in the doc
1)An important principle in Oracle Applications cloning is that the system is cloned, rather than the topology ....
--What is meant by topology in this description?
2)The Cloning methodology posted on this document requires full Autoconfig complience.
--didn't get this point.
3)Note: In the copying tasks below, UNIX/Linux users should ensure that the symbolic links (soft links) are preserved when copying. On most UNIX platforms, this can be accomplished with the cp -RH command. Consult the UNIX man page for the cp command to check the parameters available on your platform.
--what soft links are being talked about?will the regular cp -R command not preserve the soft links?
4)For patching AutoConfig on the E-Business Suite R12 instance, AutoConfig needs to be enabled on both the applications tier and the database tier. (387859.1)
--HOw do I check if AutoConfig is enabled or not?
5)Why do I need to synchronize appsutil on database tier from application tier?
6)Why do we need to maintaain snapshot information?
What does snapshot actually do?
Thannks,
Rushi

This is what I get when doing "grep rror" from 9239089 logfile.
will be ignored without error.
will be ignored without error.
will be ignored without error.
0 files had fatal errors.
0 files had fatal errors.
Performing second half of mirrored copies...
No mirrored copies were executed in this patch.
oracle/apps/ad/splice/adError [120.0.12010000.1] {oracle/apps/ad/splice/adError.class }
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.2/forms/java/frmall.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.2/jlib/ewt3.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.2/jlib/ewt3-nls.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/lib/xmlparserv2.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/j2ee/oafm/applications/mapviewer/web/WEB-INF/lib/mvclient.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/j2ee/home/lib/mail.jar: No metadata entry META-INF/JRIMETA.DAT found
Cause: Error while trying to read metadata from file /appldev/apps/tech_st/10.1.3/j2ee/home/lib/activation.jar: No metadata entry META-INF/JRIMETA.DAT found
oracle/apps/media/ieu_status_error
oracle/xml/parser/v2/XMLErrorMsg
oracle/xml/parser/v2/mesg/XMLErrorMesg
oracle/xml/parser/v2/mesg/XMLErrorMesg_ar_AE
oracle/xml/parser/v2/mesg/XMLErrorMesg_ca_ES
oracle/xml/parser/v2/mesg/XMLErrorMesg_cs_CZ
oracle/xml/parser/v2/mesg/XMLErrorMesg_da_DK
oracle/xml/parser/v2/mesg/XMLErrorMesg_de_DE
oracle/xml/parser/v2/mesg/XMLErrorMesg_el_GR
oracle/xml/parser/v2/mesg/XMLErrorMesg_en_US
oracle/xml/parser/v2/mesg/XMLErrorMesg_es_AR
oracle/xml/parser/v2/mesg/XMLErrorMesg_es_ES
oracle/xml/parser/v2/mesg/XMLErrorMesg_fi_FI
oracle/xml/parser/v2/mesg/XMLErrorMesg_fr_FR
oracle/xml/parser/v2/mesg/XMLErrorMesg_hu_HU
oracle/xml/parser/v2/mesg/XMLErrorMesg_it_IT
oracle/xml/parser/v2/mesg/XMLErrorMesg_iw_IL
oracle/xml/parser/v2/mesg/XMLErrorMesg_ja_JP
oracle/xml/parser/v2/mesg/XMLErrorMesg_ko_KR
oracle/xml/parser/v2/mesg/XMLErrorMesg_nl_NL
oracle/xml/parser/v2/mesg/XMLErrorMesg_no_NO
oracle/xml/parser/v2/mesg/XMLErrorMesg_pl_PL
oracle/xml/parser/v2/mesg/XMLErrorMesg_pt_BR
oracle/xml/parser/v2/mesg/XMLErrorMesg_pt_PT
oracle/xml/parser/v2/mesg/XMLErrorMesg_ro_RO
oracle/xml/parser/v2/mesg/XMLErrorMesg_ru_RU
oracle/xml/parser/v2/mesg/XMLErrorMesg_sk_SK
oracle/xml/parser/v2/mesg/XMLErrorMesg_sv_SE
oracle/xml/parser/v2/mesg/XMLErrorMesg_tr_TR
oracle/xml/parser/v2/mesg/XMLErrorMesg_zh_CN
oracle/xml/parser/v2/mesg/XMLErrorMesg_zh_TW
Errors and warnings are listed in the log file
Also I am getting same kind of errors for patches 8919489,9171651,9833058 and 12404574.
Although there were neither failures nor any ORA- error in any of the log files.
Please guide what needs to be done regarding the shown errors for the patches.
after executing adpreclone on db tier I got the following message in logfile.
error while preclone on db tier:Attempt to remove existing adcrdb.zip failed
What could have been wrong?
Is the message normal and can it be safely ignored?
As a pre-install task of patch 9239089,I executed adgrantsall.sql
which gave me a prompt Enter a value for 1:
I entered apps (apps schemaname/username)
Is it ok?
Thanks,
Rushi

Writing in redo log members

Hi i have a couple of questions
1) what is the max value i can set for MAXLOGFILES in controlfile? that is maximum how many redo log groups i can have in a database(when not considering space occupied by log members)
2) I had a 2 log groups with 2 members in each. how LGWR writes into log members of each group. whether it will done in serial(sequential order) or parallel? If it is sequential, when LGWR writes into 2nd member of one group if i perform a log switch, will it wait till it completes writing into that member and switches to another group?
thanks in advance

>>> I had a 2 log groups with 2 members in each. how LGWR writes into log members of each group. whether it will done in serial(sequential order) or parallel? If it is sequential, when LGWR writes into 2nd member of one group if i perform a log switch, will it wait till it completes writing into that member and switches to another group?
Mr.Howard Rodger wrote:-
There is only ever one Log Writer process. Unlike Database Writer, for example, which can have several 'clone' processes sharing the work burden, redo log records must be written to disk sequentially -and that means only one process can be in charge of working out what to write to disk. If that wasn't true, you might come to grief when a series of transactions have dependencies. If you first create a new product record and then raise a new sale record to indicate that the new product has just been sold, for example, you need the product transaction to be recorded before the sale transaction -otherwise, during a recovery, you might end up trying to sell a product that doesn't exist yet. To prevent that logical nonsense from happening, therefore, a single Log Writer process writes everything in the correct sequence.
I hope it helps
Regards
Nisanth V Santhan

Redo Log Error

Thread 1 cannot allocate new log, sequence 108
All online logs needed archiving
Current log# 1 seq# 107 mem# 0:

I guess by now you have probably figured out the problem.
1- Failure to have log_archive_start set to true when running the database in archivelog mode
2- Rapid switching of logs caused by too small and online redo log file size and delay in archiving
HTH -- Mark D Powell --

Unable to copy redo-logs for cloning

Hello
We are using R12 with 10.2.0.2 db
we take db tier backups every night and apps backup twice a month(15 days interval)
We normally run autocfg.sh and adprecolne.pl on dbTier.After this we stop all services, shutdown the database and copy all the datafiles,controlfiles and logfiles)
This backup is helpful in restoration in case any failure on PROD server and for cloning purpose on an another node for testing purpose
Now my question is, are we doing the clone procedure properly or is there a better way for cloning for suppose RMAN..or maybe any other
Secondly, Last night all the datafiles got copied after a clean shutdown except for logfiles.
Will i be able to restore the data later if i dont have the log files? can i build new logfiles?
Will this data be succesful for cloning without the redo logs
Please Note: This is a cold backup we take i.e Consistent backup
Thanks

I would go against the oft-repeated and common "Expert" and "Documentation" advice here.
If you are doing a COLD Backup and are are planning to use the Backup to restore to another server, there is no harm in taking the online redo logs as well.
Where the risk with online redo log backups arises is when the SysAdmin/DBA , when doing a FullRestore also restores the online redo logs back to the target database overwriting any present online redo logs.
For this to occcur :
a. The SysAdmin/DBA happens to restore all the files in the backup set without selectively excluding the online redo logs
b. The databases's online redo logs are present and good on disk
c. The DBA isn't very confident of being able to rollforward through his redo logs
It is for those reasons that it is easier to advice everyone not to backup online redo logs.
However, as I've noted above, if you are doing a Cold Backup and restoring to another server (with no database present at the target site), there is no harm in taking the online redo logs. Such a backup and restore makes your scripting very easy and doesn't even need a DBA.
Hemant K Chitale
http://hemantoracledba.blogpsot.com
Here are some of my comments on the issue of backups of online redo logs :
http://hemantoracledba.blogspot.com/2008/03/backup-online-redo-logs.html

Rapid clone need redo logs

Similar Messages

Maybe you are looking for