Database Backup and Recovery (MOSC)

MOSC Banner

Oracle 12.1.0.2 redo logs of cloned database fail checksum error due to size mismatch

edited Jun 19, 2015 10:36AM in Database Backup and Recovery (MOSC) 4 commentsAnswered

Hi,

We have a customer environment wherein we clone the production database and mount the copy to an alternate host. We rename the database and the ASM diskgroups. To bring up the database we recreate the control file as:

CREATE CONTROLFILE REUSE SET DATABASE clarqa RESETLOGS ARCHIVELOG

                MAXLOGFILES 80

                MAXLOGMEMBERS 5

                MAXDATAFILES 6500

                MAXINSTANCES 1

                MAXLOGHISTORY 9348

                LOGFILE

                GROUP 1 '+QAREDO/CLARITY/ONLINELOG/group_1.256.874757879' SIZE 50M BLOCKSIZE 4096,

GROUP 2 '+QAREDO/CLARITY/ONLINELOG/group_2.260.874758149' SIZE 50M BLOCKSIZE 4096,

GROUP 3 '+QAREDO/CLARITY/ONLINELOG/group_3.257.874757897' SIZE 50M BLOCKSIZE 4096,

GROUP 4 '+QAREDO/CLARITY/ONLINELOG/group_4.263.874758211' SIZE 50M BLOCKSIZE 4096,

GROUP 5 '+QAREDO/CLARITY/ONLINELOG/group_5.258.874757935' SIZE 50M BLOCKSIZE 4096,

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center