Restoring Standby Controlfile results in ORA-00600

I received ORA-00600 error while restoring Controlfile on a RAC-standby database (Physical). We purposely disabled redo log shipping on the Primary database and as a result the Standby Database was lagging way behind the production. Instead of applying all the Archive logs I took the shortest path of taking SCN based RMAN backup on the Primary and apply it to the Standby.

While doing so, I took a backup of Controlfile from primary database and shipped it to the standby site. I was able to successfully restore the controlfile as shown below:

RMAN> restore controlfile from '/tmp/control01.ctl';

Starting restore at 08-JUN-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1083 instance=qtprod1 devtype=DISK

channel ORA_DISK_1: copied control file copy
output filename=+DATADG/control01.ctl
output filename=+FRADG/control02.ctl
output filename=+DATADG/control03.ctl
Finished restore at 08-JUN-10

RMAN> exit

However, while mounting the database with this new controlfile, I was greeted with ORA-00600. Below is the error:

SQL> alter database mount standby database;
alter database mount standby database
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kccsga_update_ckpt_5], [1453], [0],
[62], [0], [], [], []

Searching for the above error in "Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool" did not provide any information. :(

Looking back at the steps that lead me to ORA-00600 error, I found the solution to the problem. The controlfile should have been restored as a standby CF. After correcting the mistake database happily mounted.

RMAN> restore standby controlfile from '/tmp/control01.ctl';

Starting restore at 08-JUN-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1082 instance=biodb1 devtype=DISK

channel ORA_DISK_1: copied control file copy
output filename=+DATADG/control01.ctl
output filename=+FRADG/control02.ctl
output filename=+DATADG/control03.ctl
Finished restore at 08-JUN-10

RMAN> exit

SQL> alter database mount standby database;

Database altered.

After applying the RMAN backup, standby database got in sync with the primary.

Moving From the Standard Edition to the Enterprise Edition

One of our customers wanted to implement Oracle Advanced Security (OAS) Option on their Oracle Database 11g. This database was a Standard Edition and OAS option is available only for Enterprise Edition. So, we have to upgrade the Standard Edition database to Enterprise Edition.

Following are the steps required to upgrade a Standard Edition database to Enterprise Edition:

1) Shutdown.

2) Remove Oracle Standard Edition software.

3) Install Oracle Enterprise Edition software.

4) Startup database

5) Run catalog.sql and catproc.sql

Note:

1) Backup your database before you begin.

2) Make sure that the release number of your Standard Edition and Enterprise Edition softwares is same.

Oracle documentation does not mention of running catalog and catproc scripts. However, Oracle Support Note does mention it. It seems to be a documentation bug.

References:

1) Oracle® Database Upgrade Guide 11g Release 2 (11.2)

2) Converting An Enterprise Edition Database To Standard Edition [ID 139642.1]

AIOUG Webcast: The Basics of Cost Based Optimization - Part II by Jonathan Lewis

Jonathan Lewis will be presenting part-2 of "The Basics of Cost Based Optimization" on 09-June-2010 at 14:00 GMT.

About the Presentation:

This presentation is a short introduction to the two key questions that drive the optimizer which are: How much data do I have to visit How widely scattered is that data We will look at a simple model to demonstrate the way that the optimzer "thinks" when choosing an execution path, and then explain why the optimizer sometimes chooses very silly execution paths.

For more information:

http://www.aioug.org/aioug_webcast.php

Make sure you capitalize on this opportunity!!!