>> 1 ... version issue?
Probably ... I'm no rman expert but just a guess based on the RV(CAT|MAN) version 11.02.00.02 ... message
>> 2 ... anything to do?
Perhaps try a catalog upgrade, that ought to get the version in the catalog db up to snuff, the `upgrade catalog` command in rman (needs a 2x run to confirm) after connecting might straighten it out. Others may have much better info. Google can offer better (or, It Depends, maybe not so better) advice.
But the overall question, if you have EE in use why bother with an XE install for the rman catalog instance? 188.8.131.52 release was moved to extended support quite some time ago, and creating a database instance is not a big deal. With a host, some storage, and a few commands it doesn't take long to create an instance. Or there is the DBCA if the GUI tools are preferred, but they're not my preference .
RMAN is quite a powerful (and quite complex) utility, with some settings the defaults are fine, others, not so much. Knowing the rman configuration is rather critical, and when a restore is needed is not an ideal time to go hunting down the "how to".
Thanks for the reply.
I've run upgrade catalog x2 on the recovery catalog and I get the following response from Express edition:
recovery catalog upgraded to version 11.02.00.02
DBMS_RCVMAN package upgraded to version 11.02.00.02
DBMS_RCVCAT package upgraded to version 11.02.00.02
I don't think the catalog is going to upgrade past that.
To answer the other question - the decision to try to use XE to backup EE is due to our group (the backup group) being separate from the database group, and we wanted to keep our own database and catalog for backups separate from the other departments. It is not only a question of organization, but also of Disaster Recovery and other considerations - we would like to be independent from the other groups so in case of catastrophe we don't need to wait on anyone to get our systems back online.
So, we have successfully upgraded our catalog to 184.108.40.206 and did a backup.
The solution, which may have been easier than easy, was to use the client's RMAN (220.127.116.11) to connect to our catalog (18.104.22.168). Then run the upgrade catalog command.
RMAN> connect username/password@CATALOG
RMAN > upgrade catalog
Obviously, CATALOG is the name of your recovery catalog, and probably should have a tnsnames.ora entry and such.
We got it working.
clcarter, thanks for the breadcrumbs - I never would have thought to use the client rman to update the main server catalog.