RMAN Backup fail with error Rman-00600

Problem-

Managing and checking backups it’s a common DBA task. Today a backup from one database that I manage, failed with the error----- RMAN backup failed with ORA-00600[8201] error-------. You should always check if the backups are finishing without errors, and you should always make some restore tests of your backups. As you probably know, when you hit an ORA-00600, usually this mean trouble. So let’s look at the error :

RMAN backup failed with ORA-00600[8201] error

RMAN-00571: ====================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ========

RMAN-00571: ====================================================

RMAN-03002: failure of backup command at 22/10/2010 23:30:25

RMAN-00600: internal error, arguments [8201] [] [] [] []

This server has a 11g r2 Oracle Database and the backup uses an RMAN database catalog. The reason for this error is a well know bug (6035495). There is a mismatch between the information stored in the Controlfile and RMAN Catalog.

Solution-

One solution is to explicit resync catalog with the target database .

RMAN> resync catalog;

By resync the catalog I’ve solved my problem, but sometimes this does not solve it. If after the resync the problem still exists then probably you’ll need to recreate the controlfile of the target database .

A note about RMAN

How Oracle Works  - A note about RMAN

Let me first say YOU DON'T HAVE TO USE RMAN TO TAKE HOT BACKUPS!

I'm amazed at how many people still take cold backups because they don't understand RMAN and think it is the only proper way to take backups.

In my opinion, RMAN wasn't even a very good tool when it first came out. It has now matured and is something that should be CONSIDERED by everyone.

Don't forget the most important question...'WHY?"

Well, RMAN is better than OS backups, right? Well, yes or no. If you are not using hot backups at all, then RMAN is useless anyway, right? So first start taking hot backups, then learn how to migrate to RMAN.


INCREMENTAL vs. FULL backups in RMAN

Oracle has made it easy for people to not understand these backups in RMAN.

If you're not using 10g and "true incrementals", just use full. Older versions of RMAN were not much faster because it had to do just as much reading as a full backup (read the whole datafile, backup anything that's changed). They were ONLY designed to save disk/tape speed and/or bandwidth to disk/tape. They certainly didn't speed up recovery.

In 10g, they've FINALLY introduced a "change tracking file" and many other enhancements like incrementally Updated Backups.

So, RMAN started out as a ham fisted tool that caused problems for a lot of people (but did help many who dedicated themselves to it), but has now become much more of an asset to the DBA.

I use RMAN and I am glad I do. But I also use 10g. I still have problems recommending it to people on older versions.

Read through the product docs and you can see what it offers (you'll notice RMAN doesn't have to put your tablespaces in backup mode). It also seems to be a lot easier to use nowadays, but maybe I've just gotten used to it.

Like anything in Oracle, there are lot's of powerful tools and features for you to exploit if you know WHY to. Don't be one of those poor saps that tries to use every feature or tool just hoping that it's the proper way of doing it.

Analyze YOUR needs and use the pieces you'll need. You'll be more successful and get a lot more sleep.

Oracle database odbc driver not available in windows 64 bit

Problem:
I am not able to find Oracle ODBC driver in datasource administrator in Windows 2003 64 bit.
Cause:
64 bit and 32 bit compatibility issue , data source administrator and application.
Solution:
I have Windows 2003 64 bit, Oracle 10.2 32 bit Client and 64 bit application.
After researching on the internet
I found that there are two versions of odbc datasource administrator:
The default one, is 64 bit which is primarily used  in Start menu for opening it.
In order to open the 32 bit version I used:( %windir%\SysWOW64\odbcad32.exe.)
With the help of 32 bit version datasource administrator, I could see my 32 bit odbc driver listed.
I extracted this rule: If your application is 32 bit, then your data source must be 32 bit supporting client as well.
You need to be aware of 3 pieces:
1- your application (which uses DSN definition),
2- Oracle client
3-data source administrator
All pieces must have same version, in my case it is 64 bit and therefore I installed 64 bit client.
At last i would say that the compatibility plays a very important role in ODBC drivers and data source.