Upgrading rman 9i catalog to 10g catalog.

Hi,
I need to know the typical steps to upgrade the rman catalog from 9i to oracle oracle 10g. We have already 9i db's registered with 9i catalog and 10g db's are there which we will register with the upgraded 10g catalog.
Kindly provide links and also summarise here the typical steps involved.
Thanks in advance for all the help !!

Depends. If you want to do an in-place upgrade, then upgrade the database to at least the highest 10g database that will be connecting. For example, if the highest 10g version you have is 10.2.0.1, then go to at least 10.2.0.1. I have been running 10.2.0.3 without any issues.
After upgrading the database, login to the rman catalog using the same ORACLE_HOME as the database, and run:
upgrade catalog;
That's it. No bells, no whistles. The docs are very clear on this and it's not a huge ordeal.
Or, you can export/import to a new database, and run 'upgrade catalog' on it.

Similar Messages

How to upgrade RMAN catalog from 10.2.0.4 to 11?

Hi, we are on Oracle 10.2.0.4, Solaris 5.10. Our RMAN catalog is 10.2.0.4 version and we have several 11g databases that need to connect to the catalog and obviously cannot. So we need to upgrade the catalog to 11. Does anyone have any docs on how to do it. Do I need to upgrade RMAN database to 11 via conventional upgrade and then do UPGRADE CATALOG? Really confusing, any help would be very appreciated.
Thank you!

You need to:
1 - upgrade the recovery catalog database
2 - upgrade the recovery catalog Schema
Please check the details on note *452529.1 Recovery catalog for RMAN backup*.
Normally newer databases (target) can be cataloged on previous version catalog database, but with 11g there is the bug 6756872 (RMAN REGISTER OF 11G TARGET INTO 10G CATALOG FAILS WITH ORA-04028) which force you to upgrade the catalog.
You can also review RMAN Compatibility Matrix (Note 73431.1) which has all valid version combinations.
If your scenario is simple enough, another option could be create a new 11g RMAN catalog and register there your databases, without importing data from the 10.2 catalog.
Regards.

Installed Lightroom 4.4. Crashes every time I try to upgrade my PE11 catalog.

Installed lightroom 4.4. Crashes every time I try to upgrade my PE11 catalog.

Hi sksinner,
You might want to refer : http://helpx.adobe.com/x-productkb/multi/lightroom-3-cant-upgrade-photoshop.html

Upgraded LR1 - LR3 Catalog: blank Grid, non functioning app

I've been dealing with support on this, but they're utterly useless, taking days to get back to me and spinning me over troubleshooting 101 stuff.
Problem:
Upgraded a perfectly working LR1 catalog to LR3. No issues during upgrade.
Upon trying to use the LR3, the first thousand or so of my photos show up in Grid, but everything after that is blank. By that I mean, a grid cell is drawn, but LR3 doesn't display a thumbnail, or any cell extras or metadata.
Clicking on one of these empty cells gives me a thumbnail frame and some metadata (slowwwwly).
Going to Loupe View on a non-empty cell gives me a "Loading..." spinner and an unrendered thumbnail preview (CPU is not ramping up at all)
Going to Loupe View on an empty cell just gives me a blank screen (CPU is not ramping up at all)
Develop module does load the picture, but slowly.
When I quit, the app freezes up completely, with beachball. Must force-quit (after giving it 20 minutes in case it was actually trying to do something)
Initially, when I load LR3, my CPU runs high, 75%, like it's working on something. Then it just cuts out as if it's given up.
Console output when this happens is the following:
6/17/10 7:27:38 PM Adobe Lightroom 3[518] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERRORSERVER<AsyncDataServer( Lightroom 3 Catalog.lrcat )>: A command threw an exception.
6/17/10 7:27:38 PM Adobe Lightroom 3[518] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERROR Error: ?:0: attempt to perform arithmetic on field '?' (a nil value)
6/17/10 7:27:38 PM Adobe Lightroom 3[518] Error initializing alternate universe. bad argument #1 to 'pairs' (table expected, got nil)
System:
MacBook Pro Core2Duo 2.1Ghz 3GB RAM, 500GB Drive.
Initially Mac OS 10.5.8, but I tried upgrading to 10.6.3 and 10.6.4 (no luck).
Library: 21,000 photos
Other things I've tried:
Trashing all LR3 prefs, caches (running YASU), LR preview caches, plists, extensions, reinstalling, restarting -- no luck
Noticed it was copying the LR1 prefs plist, so I archived that. LR3 generated a new pref, but no help
Downloaded LR2 Demo, upgraded LR1 Catalog to LR2 Catalog (which works perfectly, no issues), and then LR2 Cat -> LR3 -- no luck
Checking integrity of Catalog in LR1 and LR2 (no problems) and LR3 when upgrading (no problems)
LR3 runs fine on an empty catalog and if I point it at my photo folder and import everything, it's ok (with none of my 3 years of modifications of course).
Is my only option to write out LR1 data to sidecar files and then setup a new Catalog in LR3?

Well, on top of having full access to the photo files, LR obviously has proper permissions to affect the files it generates in the AppSupport>Adobe>Lightroom folder, the Caches>Lightroom folder, the Pictures>Lightroom folder and the Preferences> folder, otherwise it wouldn't be able to build a new catalog, new prefs, new caches and so forth when I generate a new empty catalog.
I really doubt this is a permissions voodoo issue or a monitor profile issue.
LR3 works fine with a brand new catalog (and all the same Photo files).
LR1 and LR2 have absolutely no problem with my catalog and photo files.
LR2 upgrades my LR1 Catalog without issue.
LR3 fails with my upgraded catalog (and all the same photo files)
Unless I'm missing something in my logic tree here, it seems to me this is obviously a problem with LR3 upgrading my Catalog.
Other people's catalogs upgrade fine, and that's dandy, but my catalog doesn't upgrade AND it fails with exactly the same error message every time in the Console (See original post), which seem to be related to some internal db issue, dividing by zero, nil values.
Something ain't being handled right by LR3 that previous versions of LR had no problem with.

Oracle RMAN recovery catalog database in a Primary and Standby mode

Hello All,
The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups. There are are 200+ databases running on OEL, RHEL and Windows. So we planned to host the recovery catalog database on Oracle Active DataGuard 11.2.0.1 Enterprise Edition on RedHat EL 5.8 version on two physical servers. The Primary Instance will be in one server in the Primary DC and the Standby Instance will be on another server in another DC. Also all the database datafiles are hosted in ASM Diskgroups on SAN (DATA, FRA, REDO, ARCH diskgroups).
Are there any specific RPM/patch/OS user custom/specific settings or configurations needed..?
Thanks in advance..
Regards,
Abhijit

"The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups"
Hi,
i think you can achieve HA for the catalog DB. (Rac and Asm should work fine)
There's no way (afaik) to use TAF with the rman backup. If you have a failure during a backup it simply fails.
There is no TAF in this situation.
Hope this helps.
Regs,
Drew

Option to Upgrade Photoshop Elements Catalog not available (LR5, PSE 12, Win 8)

Hi there. I have trial versions of both Photoshop Elements 12 and Lightroom 5.2 (trial licenses are both still active (i.e. not expired)). I'm looking to import my PSE12 catalog into Lightroom before I plunk down the money to buy it.
I cannot, however, locate the "File->Upgrade Photoshop Elements Catalog" option in LR5.
I may have originally installed LR 5 before installing PSE 12. So I uninstalled LR5 and reinstalled it. Still no luck - the option isn't there.
Any other ways to force LR5 to look for the PSE 12 catalog? Will LR5 even recognize a PSE12 catalog?
Your help is greatly appreciated - thanks!
Note: Using Win 8.1

dj_paige a écrit:
...But we can also wait and see report from other users.
Unfortunately, there is no doubt that the conversion of PSE12 catalogs has been omitted. It's not the first time : I also had to wait for LR4 to be able to convert PSE11 files. We may hope that Adobe will acknowledge the fact, and possibly solve the problem for future versions of PSE.
Of course, it's not a priority for Adobe: the ability to convert PSE catalogs is mainly a sales argument to make the jump from the PSE Organizer to LR easier. Not so many cases, and anyway you can always write metadata to files in PSE and import later in LR. After the jump to LR, you rarely have more PSE catalogs to convert.
However, maintaining misleading update notes by Adobe is not a good point in favour of LR. I do consider that the ability for LR to convert PSE catalog was and still is a very smart demonstration of the ability to deal with database organizational systems. I also consider that once that conversion process is mastered, the update process for each new Elements version is not such a big deal.

Lightroom won't upgrade second PSE catalog

I have successfully upgraded my main Photoshop Elements 11 catalog into Lightroom 5.6.
I have a second PSE catalog I'd also like to upgrade, but not import into the main Lightroom catalog (keeping it as a standalone catalog). According to the user manual, there should be a dropdown available from File > Upgrade Photoshop Elements Catalog that will allow me to select this second PSE catalog. However, the dropdown only expands the Catalog info without giving me access to any other catalog. Is there a workaround (or am I doing this wrong)?
For what it's worth, the PSE catalogs are on a separate drive from Lightroom, are in different folder from each other, and the location is not the default location the PSE 11 would have put them. Nevertheless, Lightroom found the first PSE catalog without difficulty.

Per the user's guide, from the Library Module I: File > Upgrade Photoshop Elements Catalog
This brings up a dialog box that shows the most recently upgraded PSE catalog. Then, to quote the user's guide, "To choose a different PSE catalog, click the Elements drop-down menu."
There is no "Elements drop-down menu" within the dialog box to click on. The closest thing is an expand triangle opposite "Catalog info," but when clicked, that only displays more detail about the source PSE catalog I have already upgraded. There doesn't seem to be any way to browse to or select a second PSE catalog — which is what I'm trying to do.

How to merge or upgrade the PSE8 catalog into the LR3 master catalog?

I did some searching but wasn't able to find a good match for the issue I'm trying to resolve.
I have recently installed LR3 after using LR3-beta, and had also been using PSE8 as my main photo library. After installing LR3 I used the "Upgrade Photoshop Elements Catalog...." to create a LR3 catalog of all photos that were in PSE8 catalog. In doing so LR8 created a separate catalog (Lightroom Catalog-2.lrcat) for these photos. However, I would like all photos in one catalog in LR8 (preferably in the LR8 master catalog: Lightroom Catalog.lrcat). Is there a way to either merge those 2 catalogs, or is there a better way to add the PSE8 photos into the LR3 master catalog? Thanks.

Thanks for the reply.
Tried that - while in LR using the master catalog, I selected the other catalog (Lightroom 3 Catalog-2.lrcat) and received the following pop-up box:

Upgrade Photoshop Elements Catalog option is missing

The File Menu/Upgrade Photoshop Elements Catalog is missing on my version of LR5. I've followed the suggested procedure to update the preferences files for both Elements 12 and Lightroom 5, but LR5 still does not recognize that I have an existing Elements 12 catalog. I assume if it did the option would now be available?
This was the instruction I tried:
http://helpx.adobe.com/x-productkb/multi/lightroom-3-cant-upgrade-photoshop.html

dj_paige a écrit:
...But we can also wait and see report from other users.
Unfortunately, there is no doubt that the conversion of PSE12 catalogs has been omitted. It's not the first time : I also had to wait for LR4 to be able to convert PSE11 files. We may hope that Adobe will acknowledge the fact, and possibly solve the problem for future versions of PSE.
Of course, it's not a priority for Adobe: the ability to convert PSE catalogs is mainly a sales argument to make the jump from the PSE Organizer to LR easier. Not so many cases, and anyway you can always write metadata to files in PSE and import later in LR. After the jump to LR, you rarely have more PSE catalogs to convert.
However, maintaining misleading update notes by Adobe is not a good point in favour of LR. I do consider that the ability for LR to convert PSE catalog was and still is a very smart demonstration of the ability to deal with database organizational systems. I also consider that once that conversion process is mastered, the update process for each new Elements version is not such a big deal.

'Upgrade Photoshop Elements catalog' menu item missing

Hi,
I have been using PSE for many years and recently upgraded to PSE8 (and PRE8). In addition, I started playing with the LR3 Beta and realized that I wanted to migrate LR from PSE. I just bought LR3 and now want to import my PSE8 catalog into LR3. The Lightroom Help tells me that I should go to File - Upgrade Photoshop Elements Catalog (while in Library module), but this menu item is not showing up in my Lightroom... Is my LR3 not detecting my PSE8 catalog installation? How can I fix this?
Any help or pointers would be greatly appreciated!

dj_paige a écrit:
...But we can also wait and see report from other users.
Unfortunately, there is no doubt that the conversion of PSE12 catalogs has been omitted. It's not the first time : I also had to wait for LR4 to be able to convert PSE11 files. We may hope that Adobe will acknowledge the fact, and possibly solve the problem for future versions of PSE.
Of course, it's not a priority for Adobe: the ability to convert PSE catalogs is mainly a sales argument to make the jump from the PSE Organizer to LR easier. Not so many cases, and anyway you can always write metadata to files in PSE and import later in LR. After the jump to LR, you rarely have more PSE catalogs to convert.
However, maintaining misleading update notes by Adobe is not a good point in favour of LR. I do consider that the ability for LR to convert PSE catalog was and still is a very smart demonstration of the ability to deal with database organizational systems. I also consider that once that conversion process is mastered, the update process for each new Elements version is not such a big deal.

Lightroom 4 has previously upgraded the selected catalog

I have upgraded to LR 4 and in the process, I upgraded my primary catalog.
However, ever time I open the catalog I get a dialog with the message "lightroom 4 has previously upgraded the selected catalog"
Would you like to use the upgraded catalog instead?"
What is going on?

Ah, of course.
Thanks for making what should have been obvious clear to me.
We all get a little remedial sometimes.
Thanks for the jolt!
James Haney
[email protected]
c: 312-339-5565
<http://www.linkedin.com/in/jameshaney>
2012/4/4 Dorin Nicolaescu-Musteață <[email protected]>
Re: lightroom 4 has previously upgraded the selected catalog
created by Dorin Nicolaescu-Musteață<http://forums.adobe.com/people/dorin_nicolaescu>in
Photoshop Lightroom - View the full discussion<http://forums.adobe.com/message/4312763#4312763

Different between normal rman and rman with catalog

Hi all ,
my question is what is the advantage of using rman with catalog server , and how i can making rman backup to protect my database till last transaction
thanks

my question is what is the advantage of using rman with catalog server , and how i can making rman backup to protect my database till last transaction Catalog database/server can register number of target database backup information.
Lets suppose you have 10 databases in your environment, If you want to check each database backup details you have to check in each and every database, where in case of catalog, you just need to connect catalog and you can see all the information from RC_ views.
Its a centralized repository database.
Of course the backup information will hold both the catalog database & target database, When your Retention is high the backup information will stores in controlfile, then there is chance to huge growth in controlfile size which is not good. Also you lost whole Target database then with the help of catalog you can easily find out which is latest backup and easy to restore with that information.
Hope this clears.

How to upgrade RMAN package RMAN.DBMS_RCVCAT ? Thank

$ rman target / catalog rman/rman@infra
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Nov 29 15:45:10 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TRAN7 (DBID=3923896548)
connected to recovery catalog database
PL/SQL package RMAN.DBMS_RCVCAT version 10.01.00 in RCVCAT database is too old
RMAN> register database;
PL/SQL package RMAN.DBMS_RCVCAT version 10.01.00 in RCVCAT database is too old
PL/SQL package RMAN.DBMS_RCVCAT version 10.01.00 in RCVCAT database is too old
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 11/29/2006 15:46:18
RMAN-06429: RCVCAT database is not compatible with this version of RMAN

Your rman recovery catalog appears to be a lower version the RMAN client. Check out the RMAN compatibility matrix located below:
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/compat002.htm

Upgrading bi publisher server error (10g to 11g)

Hi All,
We have installed OBIEE 11g (11.1.1.6).
After installing we have upgraded bi publisher repository from 10g to 11g. Stopped managed server while upgrading. Upgradation was successful. But the managed server is starting in Admin mode. So unable to login to analytics or bi publisher. Weblogic server is working fine.
In the managed server, under deployments bipublisher (11.1.1) is showin failed.
Any help..
Thanks.

Hi All,
Problem Solved.
Thanks.

Using DS 4.2 repo manager to upgrade a repository in oracle 10g?

Hello Experts,
The DS 4.2 PAM states that oracle 10g is no more supported as a local repository. I have a couple of DS 3.x local repositories on oracle 10g. Will the DS 4.2 repository manager allow to upgrade these 3.1 oracle 10g local repositories? i dont have a DS 4.2 environment so can't test it at my end , anyone out there whose been successful?

I didn't mean that, because i have not actually done it. According to their installation document you can configure with oracle 10g as well.
Check this - http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_install_win_en.pdf

Upgrading rman 9i catalog to 10g catalog.

Similar Messages

Maybe you are looking for