RE: Oracle 11.2 as RMAN Catalog - My experience
- From: "Storey, Robert \(DCSO\)" <RStorey@xxxxxxxxxxxxxxxxxx>
- To: <cicciuxdba@xxxxxxxxx>, <ssibert@xxxxxxxxx>
- Date: Thu, 22 Apr 2010 10:51:08 -0500
I'm seeing some say that they are using 11.2 as a catalog and it works
fine, but I'm now seeing that Oracle support recommends in this one case
to downgrade to 11.1.0.7.
I guess I'm confused. Is there an issue with 11.2 as a Catalog database?
Or is it just on the flavor of install/os/hardware that is causing an
issue?
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Guillermo Alan Bort
Sent: Thursday, April 22, 2010 10:36 AM
To: ssibert@xxxxxxxxx
Cc: Oracle-L Freelists
Subject: Re: Oracle 11.2 as RMAN Catalog - My experience
Jared, Oracle Support recommended downgrading to 11.1.0.7 in fact, so I
think that is what we will do.
Avadhani, I didn't mean don't go live, just test it thoroughly before
you do ;-)
Scott, on what platforms are your databases running? We've had the most
problems with the DBs running on Linux.
I have a TAR (SR?) with MOS and there is a bug open... there are
workarounds but they are not viable for production environments... so
downgrade seems to be the best option at this point.
Alan.-
On Wed, Apr 21, 2010 at 4:28 PM, Scott Sibert <ssibert@xxxxxxxxx> wrote:
We're using 11.2 for our catalog (we're backing up 11.2 databases) and
since we went live in the middle of November we haven't had any
problems. We don't have many databases though and are only backing up
10.2, 11.1 and 11.2 databases with rman, all with the same catalog
server.
On Wed, Apr 21, 2010 at 2:18 PM, Avadhani mys <avadhanimys@xxxxxxxxx>
wrote:
Thanks Alan,
This is really good notification, in fact we have 11g R2 version
database which is ready to go live as a catalog database. We will think
of alternative or wait for some time till the fixes to those bugs are
released.
Thanks
Avadhani
On Wed, Apr 21, 2010 at 7:40 PM, Guillermo Alan Bort
<cicciuxdba@xxxxxxxxx> wrote:
Listers
A few days ago someone decided that one of our catalogs should be
moved to 11g, they chose to use 11.2.0.1. This is a small catalog, there
are about 50 databases in it, most of them on AIX and only a few on
Linux, with versions going from 9.2.0.6 to 10.2.0.4, interestingly,
there were no 11g databases.
The migration went flawlessly, schema export, import, statistics,
catalog resync, first backup, catalog was updated correctly... so I
thought it was a happy upgrade (I had never seen one before)... until
they started to come... endless traces of ORA-7445 and ORA-600, database
crashes each time the dump dest filled up. My coworker tried opening an
SR but the interface did not work for him, another day went by, several
(though not all) backups were failing due to problems with the catalog.
They'd connect all right but then during the implicit resync they'd
crash. I finally managed to open a Service Request, after answering a
lot of questions and doing my own investigation in the knowledge base...
there are bugs in 11g and there appears to be no solution.
The main bug is being worked on at present time so there is not even
a workaround.
It looks like we might be reverting the migration, though this has
not been decided yet.
This is only a warning, so other people don't hit the same wall.
Now, I've worked with Oracle for several years now, new software is
always buggy as hell (reminds me of 9.2.0.1, or OracleAS 10g 9.0.4) and
after a dew patchsets it becomes quiet stable (9.2.0.4, 9.2.0.6,
9.2.0.8, 10.1.0.4, 10.2.0.3, etc)
I'd recommend anyone planning to migrate their catalog to 11g to
hold off for a few months until the grosest bugs are solved.
cheers
Alan.-
Other related posts:
