Kevin Kempf's Blog

September 8, 2009

11.2 Install

Filed under: 11g, advanced compression, Oracle, RMAN — kkempf @ 12:10 pm

I bit the bullet and installed 11.2 on my Enterprise Manager/RMAN repository database last week.  It’s a small vm, used mostly by only me, so I figured why not?

First impressions were a little mixed.  I really thought the installer looked great.  It’s come a long way, from when I first started using it (8i).  I wish I’d taken some screen shots, but basically it had a consistent look on all pages, and a nice “progress bar” as you were answering the questions before installing.  In addition, when it was checking pre-requisites, it had the ability to do a “fix it” for kernel parameters which was kind of convenient.  I did have to use yum to install a few packages (don’t know if I had to, but the point is the installer asked for them):

  • elfutils-libelf-devel
  • unixODBC
  • unixODBC-devel

I always do a manual upgrade.  Just too old school to trust the DBUA, so when I ran the pre-requisite script against my 11.1 environment, here’s what it had to say:

SQL> @utlu112i
Oracle Database 11.2 Pre-Upgrade Information Tool    09-03-2009 10:31:53
**********************************************************************
Database:
**********************************************************************
--> name:          OEMREP
--> version:       11.1.0.7.0
--> compatible:    11.1.0
--> blocksize:     8192
--> platform:      Linux x86 64-bit
--> timezone file: V10
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 576 MB
.... AUTOEXTEND additional space required: 86 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 129 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 576 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> MGMT_TABLESPACE tablespace is adequate for the upgrade.
.... minimum required size: 2932 MB
**********************************************************************
Flashback: OFF
**********************************************************************
**********************************************************************
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No update parameter changes are required.
**********************************************************************
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No renamed parameters found. No changes are required.
**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No obsolete parameters found. No changes are required
**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> Oracle Catalog Views         [upgrade]  VALID
--> Oracle Packages and Types    [upgrade]  VALID
--> Oracle Workspace Manager     [upgrade]  VALID
**********************************************************************
Miscellaneous Warnings
**********************************************************************
WARNING: --> Database is using a timezone file older than version 11.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 11.1.0.7.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains schemas with stale optimizer statistics.
.... Refer to the Upgrade Guide for instructions to update
.... schema statistics prior to upgrading the database.
.... Component Schemas with stale statistics:
....   SYS
WARNING: --> log_archive_format must be updated.
.... As of 10.1, log_archive_format requires a %r format qualifier
.... be present in its format string.  Your current setting is:
.... log_archive_format='OEMREP%T%R__%s.arc'.
.... Archive Logging is currently ON, and failure to add the %r to the
.... format string will prevent the upgraded database from starting up.
WARNING:--> recycle bin in use.
.... Your recycle bin is turned on and it contains
.... 203 object(s).  It is REQUIRED
.... that the recycle bin is empty prior to upgrading
.... your database.
.... The command:  PURGE DBA_RECYCLEBIN
.... must be executed immediately prior to executing your upgrade.

In short: empty your recycle bin, and %r is now a required part of the archivelog format.  No problem, made the minor changes and proceeded with the manual upgrade.  It didn’t complain again, until I was done and wanted to connect to RMAN and upgrade the catalog.

First problem: ZLIB is apparently no longer a valid compression algorithm.  Opened an SR to figure out what happened to it, as it was the only piece of advanced compression that worked.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on oem_disk_backup channel at 09/03/2009 11:51:40
ORA-19962: compression algorithm ZLIB is not valid with release 11.2.0.0.0

Next problem: upgrading the recovery catalog failed.  I can only describe my repository as vanilla, but when I tried upgrade catalog I received this error:

[oracle@zso-orabkp-01 env]$ rman catalog  rcat_user/pw@oemrep

Recovery Manager: Release 11.2.0.1.0 - Production on Thu  Sep 3 12:06:43 2009

Copyright (c) 1982, 2009, Oracle and/or its affiliates.   All rights reserved.

connected to recovery catalog database
PL/SQL package  RCAT_USER.DBMS_RCVCAT version 11.02.00.00 in RCVCAT database is not
current
recovery catalog is partially upgraded to 11.02.00.00

RMAN> upgrade  catalog;

recovery catalog owner is RCAT_USER
enter UPGRADE CATALOG command  again to confirm catalog upgrade

RMAN> upgrade catalog;

error creating  remove_null_db_unique_name_rows_from_node
RMAN-00571:  ===========================================================
RMAN-00569:  =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571:  ===========================================================
RMAN-06004: ORACLE  error from recovery catalog database: ORA-02292: integrity constraint
(RCAT_USER.TSATT_F2) violated - child record found

I opened an SR on this issue, looks like a bug.  In the end my solution was to drop catalog and reuild it from scratch, then re-register all the databases.  Once that was done, everything was fine and I’ve been running on 11.2 ever since.   I’m still going over what else may be of benefit in this release, but at least I can say I’m running 11.2 in a production instance!

Advertisements

Blog at WordPress.com.