After System Copy from prd to qua,unable to start the oracle.

[former_member683416]

Dear expeerts,

I have successfully restored the Oracle database 10.2.0.4 from Production to Quality.but when i am trying to start the oracle it giving error message."ORA-00205: error in identifying control file, check alert log for more info"

Please check the logs in alerts_ois.log file.

ORA-00202: control file: 'F:\ORACLE\OIS\ORIGLOGA\CNTRL\CNTRLOIS.DBF'

ORA-27047: unable to read the header block of file

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

Thu Dec 22 14:58:19 2011

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

check the results of

SQL> show parameter control_files;

NAME TYPE

-

---

-

---

VALUE

-

---

control_files string

F:\ORACLE\OIS\ORIGLOGA\CNTRL\C

NTRLOIS.DBF, F:\ORACLE\OIS\ORI

GLOGB\CNTRL\CNTRLOIS.DBF, G:\O

RACLE\OIS\SAPDATA1\CNTRL\CNTRL

OIS.DBF

Please let me know some command to resolved this issue . I am trying it from 2 days.

Regards,

Akash

[nicholas_chang · Accepted solution]

Hi Akash,

Prior to that, have you generated the control script from PRD, adjust and run it on QAS before recovery & open database?

Thanks,

Nicholas Chang

[Former Member · Accepted solution]

Dear All

Can anybody share sap cluster installtion document with screen on window 2003R2 Oracleofs

[former_member683416]

Dear All,

My issue is resolved now,

1. I have again started the fresh restoration job with production offline backup.

2. Checked the all file system and made the control file as old.

3. Resorted database with production control file only and

4. This created a new control file correctly by using source system control file script.

5. Now Oracle database is up & running

One thing I would like to mention here that though my both systems Patch level was different it has not given any problem.

Now my target server is updated as production server patch level

Thanks a Lot for your prompt help guys u2026u2026

Regards,

Akash Bhong-SAP BASIS

[Former Member]

1) Take a controlfile backup on source

2) Restore backup into target

3) Edit the controlfile (As mentioned in system copy guide) with target SID

4) Delete all the old controlfiles from target server

5) Run the new controlfile (Created above in steps 1 and 3), Follow the system copy guide

5) It automatically generates control files under target directories

6) If it is onine backup restore, proceed with recovery by applying next archive logs

If it is offline backup restore, open your database.

It seems your source and target database patch levels are not same, I would maintain the same patch levels to avoid issues.

I strongly suggest you to follow the standard system copy guide.

Regards,

Nick Loy

[former_member683416]

Dear Experts,

I have again tried restoring the Prodcution offline database on Test server.

Today also I am getting the error u201CORA-00205: error in identifying control file, check alert log for more infou201D

And alert log is showing u201C

Sat Dec 31 13:16:50 2011

Starting ORACLE instance (normal)

Sat Dec 31 13:16:50 2011

Specified value of sga_max_size is too small, bumping to 1006632960

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Picked latch-free SCN scheme 3

Autotune of undo retention is turned on.

LICENSE_MAX_USERS = 0

SYS auditing is disabled

ksdpec: called for event 13740 prior to event group initialization

Starting up ORACLE RDBMS Version: 10.2.0.2.0.

System parameters with non-default values:

processes = 80

sessions = 96

event = 10191 trace name context forever, level 1

sga_max_size = 1006632960

shared_pool_size = 486539264

shared_pool_reserved_size= 48302653

filesystemio_options = setall

control_files = F:\ORACLE\OIS\ORIGLOGA\CNTRL\CNTRLOIS.DBF, F:\ORACLE\OIS\ORIGLOGB\CNTRL\CNTRLOIS.DBF, G:\ORACLE\OIS\SAPDATA1\CNTRL\CNTRLOIS.DBF

control_file_record_keep_time= 30

db_block_size = 8192

db_cache_size = 486539264

compatible = 10.2.0

log_archive_dest = J:\oracle\OIS\oraarch\OISarch

log_buffer = 6135808

log_checkpoint_interval = 0

db_files = 254

log_checkpoints_to_alert = TRUE

dml_locks = 4000

replication_dependency_tracking= FALSE

undo_management = AUTO

undo_tablespace = PSAPUNDO

inmemory_undo = FALSE

undo_retention = 43200

recyclebin = off

remote_os_authent = TRUE

remote_login_passwordfile= EXCLUSIVE

job_queue_processes = 1

parallel_execution_message_size= 16384

tablelookup_prefetch_size= 0

background_dump_dest = G:\ORACLE\OIS\SAPTRACE\BACKGROUND

user_dump_dest = G:\ORACLE\OIS\SAPTRACE\USERTRACE

core_dump_dest = G:\ORACLE\OIS\SAPTRACE\BACKGROUND

sort_area_size = 2097152

sort_area_retained_size = 0

db_name = OIS

open_cursors = 800

sortelimination_cost_ratio= 10

btree_bitmap_plans = FALSE

star_transformation_enabled= true

query_rewrite_enabled = false

indexjoin_enabled = FALSE

optimpeek_user_binds = FALSE

pga_aggregate_target = 629145600

optimizermjc_enabled = FALSE

PMON started with pid=2, OS id=1116

PSP0 started with pid=3, OS id=5668

MMAN started with pid=4, OS id=4752

DBW0 started with pid=5, OS id=3284

LGWR started with pid=6, OS id=1848

CKPT started with pid=7, OS id=5576

SMON started with pid=8, OS id=2000

RECO started with pid=9, OS id=1624

CJQ0 started with pid=10, OS id=3484

MMON started with pid=11, OS id=2288

MMNL started with pid=12, OS id=5436

Sat Dec 31 13:16:51 2011

ALTER DATABASE MOUNT

Sat Dec 31 13:16:51 2011

ORA-00202: control file: 'F:\ORACLE\OIS\ORIGLOGA\CNTRL\CNTRLOIS.DBF'

Please give me the commands to proceed further i am just getting frustrated with this error, I know that I am doing somthing wrong but what?& how should I resloved it ?

Thanks in advance.

Akash

[former_member188883]

Hi Akash,

Ensure that you have updated control files at all the 3 locations mentioned in init<SID>.ora

This will help you in resolving the issue.

Regards,

Deepak Kori

[former_member189725]

Please check this link

[http://www.dba-oracle.com/t_ora-00205:_error_in_identifying_controlfile.htm]

Also when you created the control file , did all the files get created with the same size in all the locations mentioned ?

[markus_doehr2]

Was the database restored from a backup?

Are both databases the same version?

Markus

[Former Member]

Hi,

After thr DB is copied from prod to Quality before the DB is opened we need to recreate the control file to point it to new system .

You can check with your DBA or check the system copy doc for control file recreate useing set command.

Once you recreateed the control file try to open the database .

Thanks,

Subhash.G

[volker_borowski2]

Hi,

this might be a longshot, but if your DB was created on Version 7.2 or lower and has been upgraded

all the way to 10.2, you should get a hold of note 650638.

Download the tool described there and run the check against your PRD system (can be done online).

If you still have datafiles with the mentioned 512 byte header,

I think you will need to convert the files on the source first (requires downtime),

otherwise the generated controlfile will not be able to handle this 512 bytes fileheaders.

Volker