cancel
Showing results for 
Search instead for 
Did you mean: 

System copy homogeneous

Former Member
0 Kudos

Hi ,

I am trying to do a system copy and have a few of questions, please keep in mind I am not a Oracle expert at all, in fact I am a beginner:

1. The guide talks about restoring the data on the target and to do that I have a online backup from the previous night. Question is: what all files are required to start the restoration on the target system? I have one base folder starting with <SID> folder.

Within the <SID> folder I have two folders REDOLOGS and SAPBACKUP.

In the REDOLOGS folder I have a number of <SID>ARCH_xxx_xxx.DBF files and within the REDOLOGS folder I have a sub folder <SID> which has .svd files along with .log and .ora files.

In the SAPBACKUP folder I have two sub folders <SID> which has back<SID>.log, bekxcnxg.fnd, init<SID>.ora and init<SID>.sap.  and another sub folder bekxcnxg which has all the .DATAx files.

Will these be enough?

2. Do I need to create the control file on the source system or is it available in the online backup that I have available as mentioned above?

3. Do I use BRRECOVER or BRRESTORE?

Really appreciate your help/input.

Manish

Accepted Solutions (1)

Accepted Solutions (1)

former_member188883
Active Contributor
0 Kudos

Hi Manish,

Following is the response on your queries

1) You need to have online backup of datafiles ( sapdata1..sapdatan), offline redo log files , back<SID>.log and backup log file bekxcnxg.fnd.

    These files are needed for restoring backup to target systems.

2) Do I need to create the control file on the source system or is it available in the online backup that I have available as mentioned above?

YES. You need to use command alter database backup controlfile to trace; to generate a tracefile on source system. This will be copied to target system and modified ( replace SID, change option to resetlogs , adjust target path for online redo log files etc). Update trace file will be renamed to control.SQL and execute to create target system controlfiles.

3) Do I use BRRECOVER or BRRESTORE?

Use brrestore to perform backup restoration on target system. Then once you create the control file on target system use the command

      recover database using backup controlfile until cancel;

to perform the recovery. Once the recovery is completed , open the database in resetlog mode

  alter database open resetlogs;

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

Thanks Deepak for the quick reply.

Small question the below points please:

This will be copied to target system and modified ( replace SID, change option to resetlogs , adjust target path for online redo log files etc).

I managed to get the copy and since I want to keep the SID the same I will not change that. But, when you say change option to resetlogs, does it mean that I should deleted the below

-- Set #1. NORESETLOGS case

--

-- The following commands will create a new control file and use it

-- to open the database.

-- Data used by Recovery Manager will be lost.

-- Additional logs may be required for media recovery of offline

-- Use this only if the current versions of all online logs are

-- available.

-- After mounting the created controlfile, the following SQL

-- statement will place the database in the appropriate

-- protection mode:

--  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE DATABASE "ACD" NORESETLOGS  ARCHIVELOG

MAXLOGFILES 255
MAXLOGMEMBERS 3
MAXDATAFILES 254
MAXINSTANCES 50
MAXLOGHISTORY 11680

LOGFILE

  GROUP 1 (

'I:\ORACLE\ACD\ORIGLOGA\LOG_G11M1.DBF',
'J:\ORACLE\ACD\MIRRLOGA\LOG_G11M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 2 (

'I:\ORACLE\ACD\ORIGLOGB\LOG_G12M1.DBF',
'J:\ORACLE\ACD\MIRRLOGB\LOG_G12M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 3 (

'I:\ORACLE\ACD\ORIGLOGA\LOG_G13M1.DBF',
'J:\ORACLE\ACD\MIRRLOGA\LOG_G13M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 4 (

'I:\ORACLE\ACD\ORIGLOGB\LOG_G14M1.DBF',
'J:\ORACLE\ACD\MIRRLOGB\LOG_G14M2.DBF'

  ) SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  'E:\ORACLE\ACD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\UNDO_1\UNDO.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_1\SR3.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_2\SR3.DATA2',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_1\SR3702.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_2\SR3702.DATA2',

  'E:\ORACLE\ACD\SAPDATA4\SR3USR_1\SR3USR.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_3\SR3702.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_4\SR3702.DATA4',

  'E:\ORACLE\ACD\SAPDATA2\SR3_3\SR3.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_5\SR3702.DATA5'

CHARACTER SET UTF8

;

-- Commands to re-create incarnation table

-- Below log names MUST be changed to existing filenames on

-- disk. Any one log file from each branch can be used to

-- re-create incarnation records.

-- ALTER DATABASE REGISTER LOGFILE 'S:\ORACLE\ACD\ORAARCH\ACDARCH1_1_775524145.DBF';

-- Recovery is required if any of the datafiles are restored backups,

-- or if the last shutdown was not normal or immediate.

RECOVER DATABASE

-- All logs need archiving and a log switch is needed.

ALTER SYSTEM ARCHIVE LOG ALL;

-- Database can now be opened normally.

ALTER DATABASE OPEN;

-- Commands to add tempfiles to temporary tablespaces.

-- Online tempfiles have complete space information.

-- Other tempfiles may require adjustment.

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'E:\ORACLE\ACD\SAPDATA1\TEMP_1\TEMP.DATA1'

SIZE 4096M REUSE AUTOEXTEND ON NEXT 20971520  MAXSIZE 10000M;

-- End of tempfile additions.

--

and leave this portion as it is in the newly created control.sql, since I want to keep the files location to be the same:

-- Set #2. RESETLOGS case

--

-- The following commands will create a new control file and use it

-- to open the database.

-- Data used by Recovery Manager will be lost.

-- The contents of online logs will be lost and all backups will

-- be invalidated. Use this only if online logs are damaged.

-- After mounting the created controlfile, the following SQL

-- statement will place the database in the appropriate

-- protection mode:

--  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE DATABASE "ACD" RESETLOGS  ARCHIVELOG

MAXLOGFILES 255
MAXLOGMEMBERS 3
MAXDATAFILES 254
MAXINSTANCES 50
MAXLOGHISTORY 11680

LOGFILE

  GROUP 1 (

'I:\ORACLE\ACD\ORIGLOGA\LOG_G11M1.DBF',
'J:\ORACLE\ACD\MIRRLOGA\LOG_G11M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 2 (

'I:\ORACLE\ACD\ORIGLOGB\LOG_G12M1.DBF',
'J:\ORACLE\ACD\MIRRLOGB\LOG_G12M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 3 (

'I:\ORACLE\ACD\ORIGLOGA\LOG_G13M1.DBF',
'J:\ORACLE\ACD\MIRRLOGA\LOG_G13M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 4 (

'I:\ORACLE\ACD\ORIGLOGB\LOG_G14M1.DBF',
'J:\ORACLE\ACD\MIRRLOGB\LOG_G14M2.DBF'

  ) SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  'E:\ORACLE\ACD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\UNDO_1\UNDO.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_1\SR3.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_2\SR3.DATA2',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_1\SR3702.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_2\SR3702.DATA2',

  'E:\ORACLE\ACD\SAPDATA4\SR3USR_1\SR3USR.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_3\SR3702.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_4\SR3702.DATA4',

  'E:\ORACLE\ACD\SAPDATA2\SR3_3\SR3.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_5\SR3702.DATA5'

CHARACTER SET UTF8

;

-- Commands to re-create incarnation table

-- Below log names MUST be changed to existing filenames on

-- disk. Any one log file from each branch can be used to

-- re-create incarnation records.

-- ALTER DATABASE REGISTER LOGFILE 'S:\ORACLE\ACD\ORAARCH\ACDARCH1_1_775524145.DBF';

-- Recovery is required if any of the datafiles are restored backups,

-- or if the last shutdown was not normal or immediate.

RECOVER DATABASE USING BACKUP CONTROLFILE

-- Database can now be opened zeroing the online logs.

ALTER DATABASE OPEN RESETLOGS;

-- Commands to add tempfiles to temporary tablespaces.

-- Online tempfiles have complete space information.

-- Other tempfiles may require adjustment.

ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'E:\ORACLE\ACD\SAPDATA1\TEMP_1\TEMP.DATA1'

SIZE 4096M REUSE AUTOEXTEND ON NEXT 20971520  MAXSIZE 10000M;

-- End of tempfile additions.

--

Thanks again for your help. I believe I am pretty close to getting this sorted now and I understand the intricacies a lot better now.

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

Keep only the below mentioned lines in the file. Rest others you can remove

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE DATABASE "ACD" RESETLOGS  ARCHIVELOG


MAXLOGFILES 255

MAXLOGMEMBERS 3

MAXDATAFILES 254

MAXINSTANCES 50

MAXLOGHISTORY 11680

LOGFILE

  GROUP 1 (


'I:\ORACLE\ACD\ORIGLOGA\LOG_G11M1.DBF',

'J:\ORACLE\ACD\MIRRLOGA\LOG_G11M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 2 (


'I:\ORACLE\ACD\ORIGLOGB\LOG_G12M1.DBF',

'J:\ORACLE\ACD\MIRRLOGB\LOG_G12M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 3 (


'I:\ORACLE\ACD\ORIGLOGA\LOG_G13M1.DBF',

'J:\ORACLE\ACD\MIRRLOGA\LOG_G13M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 4 (


'I:\ORACLE\ACD\ORIGLOGB\LOG_G14M1.DBF',

'J:\ORACLE\ACD\MIRRLOGB\LOG_G14M2.DBF'

  ) SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  'E:\ORACLE\ACD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\UNDO_1\UNDO.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_1\SR3.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_2\SR3.DATA2',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_1\SR3702.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_2\SR3702.DATA2',

  'E:\ORACLE\ACD\SAPDATA4\SR3USR_1\SR3USR.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_3\SR3702.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_4\SR3702.DATA4',

  'E:\ORACLE\ACD\SAPDATA2\SR3_3\SR3.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_5\SR3702.DATA5'

CHARACTER SET UTF8

;

Regards,

Deepak Kori

former_member188883
Active Contributor
0 Kudos

Hi Manish,

Is your query resolved.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

Unfortunately no. When I tried to run BRTOOLs in Disaster recovery mode first and then a full Database recovery it started complaining about CTL1<SID>.ora not available in <ORACLE_HOME>\database folder. And then I was busy with other work so couldn't look into it yesterday.

Another small question on this is that do I need to copy all the files from all the folders from the backup into all the folder on the target system for this to work?

Thanks again for your help!

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

Another small question on this is that do I need to copy all the files from all the folders from the backup into all the folder on the target system for this to work?

Could you provide point by point details of what actions have been performed by you.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi again,

Basically I have a full online backup available to me. And now I want to do a homogeneous system copy. My original backups were on the Z: drive with folder Z:\Backup\ACD\SAPBACKUP.

On the target system I have started the install of SAP using SAPINST and the installation has stopped asking me to complete the DB related activity.

I have made the backup available to the target system on Z:\Backup\ACD\SAPBACKUP.

I have created a CTL1ACD.ORA from the source system using alter database backup controlfile to trace; and edited it to just contain the lines you have mentioned and placed it in the <ORACLE_HOME>\database folder as the BRRECOVER was asking for this.

Then I started BRTOOLS. There I selected 7. Disaster Recovery then I went on pressing c at the next option screens until it restored spaceACD.log, structACD.log. The it read the backACD.log and found the one entry I had left in there of the last successful backup. I selected this backup to be restored. Then it restored the *.fnd files. And then it tried to restore profiles and log files from BRARCHIVE backup and successfully completed that and exited the program Disaster Recovery menu.

Then I went to Complete Database Recovery option. Pressed c once to continue. Then it came to the stage of Check the status of database files. Pressed c here to continue. And then got the below:

BR0280I BRRECOVER time stamp: 2013-04-11 11.32.00

BR0308I Shutdown of database instance ACD successful

BR0280I BRRECOVER time stamp: 2013-04-11 11.32.00

BR0330I Starting and mounting database instance ACD ...

BR0278E Command output of 'F:\oracle\ACD\11202\BIN\sqlplus /nolog < E:\oracle\ACD\sapbackup\.vekymum

c.spi':

SQL*Plus: Release 11.2.0.2.0 Production on Thu Apr 11 11:32:00 2013

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

SQL> SQL> Connected to an idle instance.

SQL>

SQL> ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 1006358528 bytes

Fixed Size                  2259304 bytes

Variable Size             511706776 bytes

Database Buffers          486539264 bytes

Redo Buffers                5853184 bytes

ORA-00205: error in identifying control file, check alert log for more info

SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

BR0280I BRRECOVER time stamp: 2013-04-11 11.32.02

BR0279E Return code from 'F:\oracle\ACD\11202\BIN\sqlplus /nolog < E:\oracle\ACD\sapbackup\.vekymumc

.spi': 0

BR0302E SQLPLUS call for database instance ACD failed

BR0332E Start and mount of database instance ACD failed

BR0280I BRRECOVER time stamp: 2013-04-11 11.32.02

BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last acti

on

BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:

Here are the last few lines of the alert log:

ORACLE_BASE from environment = F:\oracle

Thu Apr 11 11:32:02 2013

ALTER DATABASE   MOUNT

ORA-00210: cannot open the specified control file

ORA-00202: control file: 'F:\ORACLE\ACD\11202\DATABASE\CTL1ACD.ORA'

ORA-27048: skgfifi: file header information is invalid

OSD-04001: invalid logical block size (OS 1145258332)

ORA-205 signalled during: ALTER DATABASE   MOUNT...

Here is what the CTL1ACD.ORA looks like:

Trace file E:\ORACLE\ACD\SAPTRACE\diag\rdbms\acd\acd\trace\acd_ora_1116.trc

Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

Windows NT Version V6.1 

CPU                 : 6 - type 8664, 6 Physical Cores

Process Affinity    : 0x0x0000000000000000

Memory (Avail/Total): Ph:7297M/16383M, Ph+PgF:57298M/81916M

VM name             : VMWare Version (6)

Instance name: acd

Redo thread mounted by this instance: 1

Oracle process number: 51

Windows thread id: 1116, image: ORACLE.EXE (SHAD)

*** 2013-04-09 11:36:43.856

*** SESSION ID:(97.1387) 2013-04-09 11:36:43.856

*** CLIENT ID:() 2013-04-09 11:36:43.856

*** SERVICE NAME:(SYS$USERS) 2013-04-09 11:36:43.856

*** MODULE NAME:(sqlplus.exe) 2013-04-09 11:36:43.856

*** ACTION NAME:() 2013-04-09 11:36:43.856

-- The following are current System-scope REDO Log Archival related

-- parameters and can be included in the database initialization file.

--

-- LOG_ARCHIVE_DEST=''

-- LOG_ARCHIVE_DUPLEX_DEST=''

--

-- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf

--

-- DB_UNIQUE_NAME="ACD"

--

-- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'

-- LOG_ARCHIVE_MAX_PROCESSES=4

-- STANDBY_FILE_MANAGEMENT=MANUAL

-- STANDBY_ARCHIVE_DEST=%ORACLE_HOME%\RDBMS

-- FAL_CLIENT=''

-- FAL_SERVER=''

--

-- LOG_ARCHIVE_DEST_1='LOCATION=S:\oracle\ACD\oraarch\ACDarch'

-- LOG_ARCHIVE_DEST_1='OPTIONAL REOPEN=300 NODELAY'

-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM NOEXPEDITE NOVERIFY SYNC'

-- LOG_ARCHIVE_DEST_1='REGISTER NOALTERNATE NODEPENDENCY'

-- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'

-- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'

-- LOG_ARCHIVE_DEST_STATE_1=ENABLE

--

-- Below are two sets of SQL statements, each of which creates a new

-- control file and uses it to open the database. The first set opens

-- the database with the NORESETLOGS option and should be used only if

-- the current versions of all online logs are available. The second

-- set opens the database with the RESETLOGS option and should be used

-- if online logs are unavailable.

-- The appropriate set of statements can be copied from the trace into

-- a script file, edited as necessary, and executed when there is a

-- need to re-create the control file.

--

-- Commands to re-create incarnation table

-- Below log names MUST be changed to existing filenames on

-- disk. Any one log file from each branch can be used to

-- re-create incarnation records.

-- ALTER DATABASE REGISTER LOGFILE 'S:\ORACLE\ACD\ORAARCH\ACDARCH1_1_775524145.DBF';

-- Recovery is required if any of the datafiles are restored backups,

-- or if the last shutdown was not normal or immediate.

-- RECOVER DATABASE

-- All logs need archiving and a log switch is needed.

-- ALTER SYSTEM ARCHIVE LOG ALL;

-- Database can now be opened normally.

-- ALTER DATABASE OPEN;

-- Commands to add tempfiles to temporary tablespaces.

-- Online tempfiles have complete space information.

-- Other tempfiles may require adjustment.

-- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE 'E:\ORACLE\ACD\SAPDATA1\TEMP_1\TEMP.DATA1'

--      SIZE 4096M REUSE AUTOEXTEND ON NEXT 20971520  MAXSIZE 10000M;

-- End of tempfile additions.

--

--     Set #2. RESETLOGS case

--

-- The following commands will create a new control file and use it

-- to open the database.

-- Data used by Recovery Manager will be lost.

-- The contents of online logs will be lost and all backups will

-- be invalidated. Use this only if online logs are damaged.

-- After mounting the created controlfile, the following SQL

-- statement will place the database in the appropriate

-- protection mode:

--  ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE DATABASE "ACD" RESETLOGS  ARCHIVELOG

    MAXLOGFILES 255

    MAXLOGMEMBERS 3

    MAXDATAFILES 254

    MAXINSTANCES 50

    MAXLOGHISTORY 11680

LOGFILE

  GROUP 1 (

    'I:\ORACLE\ACD\ORIGLOGA\LOG_G11M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGA\LOG_G11M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 2 (

    'I:\ORACLE\ACD\ORIGLOGB\LOG_G12M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGB\LOG_G12M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 3 (

    'I:\ORACLE\ACD\ORIGLOGA\LOG_G13M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGA\LOG_G13M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 4 (

    'I:\ORACLE\ACD\ORIGLOGB\LOG_G14M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGB\LOG_G14M2.DBF'

  ) SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  'E:\ORACLE\ACD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\UNDO_1\UNDO.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_1\SR3.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_2\SR3.DATA2',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_1\SR3702.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_2\SR3702.DATA2',

  'E:\ORACLE\ACD\SAPDATA4\SR3USR_1\SR3USR.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_3\SR3702.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_4\SR3702.DATA4',

  'E:\ORACLE\ACD\SAPDATA2\SR3_3\SR3.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_5\SR3702.DATA5'

CHARACTER SET UTF8

;

Sorry for being so long winded but this tells you exactly what I have done. Hopefully you can tell me what I am doing wrong so that I can get this sorted.

And above all, thank you so much for the help!

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

ORA-00210: cannot open the specified control file

ORA-00202: control file: 'F:\ORACLE\ACD\11202\DATABASE\CTL1ACD.ORA'

ORA-27048: skgfifi: file header information is invalid

OSD-04001: invalid logical block size (OS 1145258332)

Do you have CTL1ACD.ORA in the path mentioned above ?

Also check for space in F:\drive .

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

Yes, I do have it there. And I have pasted the contents of that in my previous reply. And yes there is about 90 GB free on the F: drive.

One small question is where is it finding this name of CTL1ACD.ORA? Is it in any .ora or .sap file?

Look forward to hearing back. Thanks.

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

As per the error logs

ORA-00205: error in identifying control file, check alert log for more info

Could you ensure updated controlfiles exists in the location defined in initSID.ora file of your system.

You may check alert_SID.log file to find details of missing controlfile.

PS: You may share location of control files defined in initSID.ora as well as error details from alert_SID.log

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

I think I need to step back a little here. Coming to the control file creation on the source system and then running it on the target system.

Question:

When I create the control file using the command

alter database backup controlfile to trace;

I get the trace file that I edit and leave this portion below:

STARTUP NOMOUNT

CREATE CONTROLFILE SET DATABASE "ACD" RESETLOGS  ARCHIVELOG

    MAXLOGFILES 255

    MAXLOGMEMBERS 3

    MAXDATAFILES 254

    MAXINSTANCES 50

    MAXLOGHISTORY 11680

LOGFILE

  GROUP 1 (

    'I:\ORACLE\ACD\ORIGLOGA\LOG_G11M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGA\LOG_G11M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 2 (

    'I:\ORACLE\ACD\ORIGLOGB\LOG_G12M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGB\LOG_G12M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 3 (

    'I:\ORACLE\ACD\ORIGLOGA\LOG_G13M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGA\LOG_G13M2.DBF'

  ) SIZE 50M BLOCKSIZE 512,

  GROUP 4 (

    'I:\ORACLE\ACD\ORIGLOGB\LOG_G14M1.DBF',

    'J:\ORACLE\ACD\MIRRLOGB\LOG_G14M2.DBF'

  ) SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  'E:\ORACLE\ACD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',

  'E:\ORACLE\ACD\SAPDATA1\UNDO_1\UNDO.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_1\SR3.DATA1',

  'E:\ORACLE\ACD\SAPDATA2\SR3_2\SR3.DATA2',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_1\SR3702.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_2\SR3702.DATA2',

  'E:\ORACLE\ACD\SAPDATA4\SR3USR_1\SR3USR.DATA1',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_3\SR3702.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_4\SR3702.DATA4',

  'E:\ORACLE\ACD\SAPDATA2\SR3_3\SR3.DATA3',

  'E:\ORACLE\ACD\SAPDATA3\SR3702_5\SR3702.DATA5'

CHARACTER SET UTF8

;

I rename this file to CONTROL.SQL.

Then I copy this file to the target at the following location:

F:\oracle\ACD\11202\database

After I have copied this to the target, I tried to execute it in SQLPLUS and got this:

CREATE CONTROLFILE SET DATABASE "ACD" RESETLOGS  ARCHIVELOG

*

ERROR at line 1:

ORA-01503: CREATE CONTROLFILE failed

ORA-01565: error in identifying file

'E:\ORACLE\ACD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'

ORA-27041: unable to open file

OSD-04002: unable to open file

O/S-Error: (OS 2) The system cannot find the file specified.

Bear in mind I have not copied the files from the backup to their respective locations as I am expecting BRRESTORE to do that for me. Am I right in doing/assuming this?

The second thing I tried is to run the recovery even though the above has not worked by copying the existing control files(.dbf files) from the backup and I got this:

BR0280I BRRECOVER time stamp: 2013-04-12 18.36.16

BR0331I Start and mount of database instance ACD successful

BR0752E Control files are not 'CURRENT' - complete recovery not possible

Given this situation if you can guide me as to the correct process that I need to follow, I will be greatful to you.

Look forward to hearing back from you.

Thanks.

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

Sequence should be as follows

1) You create a trace file from source database and create control.SQL and keep at the location you decided

2) Perform brbrestore to restore database

3) Once the database is restored, you now need to create a new control file using control.SQL

4) Perform recovery of the database using the updated controlfile.

5) Open database using resetlogs option.

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

Thanks again. Please see the actions below:

1) You create a trace file from source database and create control.SQL and keep at the location you decided

DONE.

2) Perform brbrestore to restore database

DONE.

3) Once the database is restored, you now need to create a new control file using control.SQL

Comes up with this issue:

CREATE CONTROLFILE SET DATABASE "ACD" RESETLOGS  ARCHIVELOG

*

ERROR at line 1:

ORA-01503: CREATE CONTROLFILE failed

ORA-00200: control file could not be created

ORA-00202: control file: 'I:\ORACLE\ACD\ORIGLOGA\CNTRL\CNTRLACD.DBF'

ORA-27038: created file already exists

OSD-04010: <create> option specified, file already exists

4) Perform recovery of the database using the updated controlfile.

Comes with this issue:

BR0280I BRRECOVER time stamp: 2013-04-13 09.53.19

BR0308I Shutdown of database instance ACD successful

BR0280I BRRECOVER time stamp: 2013-04-13 09.53.19

BR0330I Starting and mounting database instance ACD ...

BR0280I BRRECOVER time stamp: 2013-04-13 09.53.29

BR0331I Start and mount of database instance ACD successful

BR0752E Control files are not 'CURRENT' - complete recovery not possible

BR0280I BRRECOVER time stamp: 2013-04-13 09.53.29

BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat t

5) Open database using resetlogs option.

Haven't reached to this stage yet.

Hope you can help me resolving the control file issue.

Thanks.

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

3) Once the database is restored, you now need to create a new control file using control.SQL

Comes up with this issue:

CREATE CONTROLFILE SET DATABASE "ACD" RESETLOGS  ARCHIVELOG

*

ERROR at line 1:

ORA-01503: CREATE CONTROLFILE failed

ORA-00200: control file could not be created

ORA-00202: control file: 'I:\ORACLE\ACD\ORIGLOGA\CNTRL\CNTRLACD.DBF'

ORA-27038: created file already exists

OSD-04010: <create> option specified, file already exists

Please rename the existing controlfiles on all the locations defined in initSID.ora .

Then start from step 3 again

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

I have made very good progress thanks to your support. I think I am at my last hurdle now. I did rename the control files and then issued the creation of control files and was able to complete the recovery in BRTOOLS. Now when I go back the SAP install screen and click on continue after the step of finishing off the DB related steps I get an issue which says this:

An error occurred while processing option Enhancement Package 5 for SAP ERP 6.0 > Software Life-Cycle Options > System Copy > Oracle > Target System Installation > Central System > Based on AS ABAP > Central System( Last error reported by the step: SQL statement or script failed. DIAGNOSIS: Error message: ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance ORACLE instance started. Total System Global Area 2639106048 bytes Fixed Size 2256016 bytes Variable Size 1325400944 bytes Database Buffers 1291845632 bytes Redo Buffers 19603456 bytes Control file created. ORA-01109: database not open Database dismounted. ORACLE instance shut down. ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance ORACLE instance started. Total System Global Area 2639106048 bytes Fixed Size 2256016 bytes Variable Size 1325400944 bytes Database Buffers 1291845632 bytes Redo Buffers 19603456 bytes Database mounted. Database altered. ALTER DATABASE OPEN * ERROR at line 1: ORA-01589: must use RESETLOGS or NORESETLOGS option for database open ORA-01109: database not open Database dismounted. ORACLE instance shut down. Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options . SOLUTION: For more information, see ora_sql_results.log and the Oracle documentation.). You can now:

  • Choose Retry to repeat the current step.
  • Choose Log Files to get more information about the error.
  • Stop the option and continue with it later.

Contents of the ora_sql_results:

CONNECT / AS SYSDBA

SHUTDOWN ABORT

@CONTROL.SQL

SHUTDOWN IMMEDIATE

STARTUP MOUNT

ALTER DATABASE ARCHIVELOG;

ALTER DATABASE OPEN;

SHUTDOWN IMMEDIATE

EXIT

exit;

Executed with error.

I tried to run all these commands in a SQLPLUS session and could see that after the re-creation of the control files the system does not like the statement ALTER DATABASE OPEN.

Is there a way to fix this situation? When I run ALTER DATABASE OPEN RESETLOGS then it opens up with issues.

Thanks again. Hopefully this is the last question on this issue.

Thanks.

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

Do the following

1) Ensure that you are able to connect to database using SQLplus

2) The open the file CONTROL.SQL from the installation directory

3) Remove all the lines from this file and just mention EXIT; Save the file

4) Go to SAPinst screen then press retry . It should work

Note: As the database is up you may skip the steps where it is trying to mount and start the database.

Alternate solution

1) Stop the sapinst installation process

2) Edit the keydb.xml file present in the installation directory

3) Search for keyword "ERROR" ( in CAPS)

4) replace it by keyword "OK"

5) save the file

6) Retry sapinst with option

     ./sapinst SAPINST_ERRORSTEP_SKIP=true

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

You are a star! The exit worked, hurray!!

Now the sapinst is asking if it should remove OPS$<DOMAINNAME>\SAPSERVICEACD and OPS$<DOMAINNAME>\ACDADM schemas?

What is this for and should I let it remove these schemas?

Thanks again.

Regards,

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

Yes. You need to remove these schemas and later SAPINST will create new schemas for your system.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak,

I have carried on with the installation by allowing the system to remove the two tablespaces and now...

Seems my DDIC password is not correct. And in trying to see if a few of the others are correct, I have managed to get it locked!

I have used the backend command to unlock it but the SAPINST doesn't seem to register that fact and after having restarted the install a few times with the old options, it is still not successful.

Is there way to make sure that SAPINST flag for this value is reset?

Thanks.

Manish

former_member188883
Active Contributor
0 Kudos

Hi Manish,

1) Set the profile parameter login/no_sapstar_user = 0 in instance profile

2) Login to database using Sqlplus

3) Run the command delete from <SAPSCHEMA>.USR02 where BNAME='SAP*' and MANDT=000;

4) Take R3 restart

5) Login to client 000 with user SAP* ( password is pass).

6) reset the password for DDIC. Ensure DDIC is unlocked

7) Recheck login with DDIC with new password in client 000.

😎 Retry the step from SAPINST.

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

Hi Deepak!!

Thank you so much for all your help!!!

I have it working now. I was able to sign in to the instance and did not need to run the above command. By signing in I was able to reset the password to the one I had entered when I started the install and viola... The installation completed. This was a real experience.

Thanks again!

Regards,

Manish

Answers (0)