Re: Can't register database with RMAN

I may be way off here (it's sometimes difficult to tell with RMAN!), but registering the database really means registering it with the catalog -and I don't see you connecting to a catalog anywhere.

So what you ought to have is:

RMAN> connect target system/manager_at_PRD1 catalog rman/rman_at_CATL

(Obviously use appropriate usernames and passwords and tnsnames aliases).

Then try the register database command.

I notice however that the RMAN replies state that the registration is actually successful, and it's only the release of the server processes (ie, channels) that's causing grief... if that's true, we're entering the twilight zone (ie, it's time to check all sorts of network configuration and hardware configuration issues). The only thing I've ever learnt with RMAN is not to pay too much attention to the message dialogs it displays, since they frequently bear little or no relation to what is actually going on.

You did grant recovery_catalog_owner to the RMAN User didn't you? And unlimited quota on the catalog tablespace? And connect and resource?

Regards
HJR "bonminh Lam" <no_spam_at_bmlam.de> wrote in message news:3AAB7979.B3A1DEE6_at_bmlam.de...
> Hi,
>
> I am running server 8.1.5 on Redhat 6.1. After having created a
> dedicated tablespace and the catalog owner on the catalog database, I
> could connect to the catalog database as the catalog owner and created a
> catalog. However, following errors occur when I tried to register the
> database:
>
>
> RMAN> connect target
>
> RMAN-06005: connected to target database: PRD1 (DBID=724408206)
>
> RMAN> register database;
>
> RMAN-03022: compiling command: register
> RMAN-03023: executing command: register
> RMAN-08006: database registered in recovery catalog
> RMAN-03023: executing command: full resync
> RMAN-03026: error recovery releasing channel resources
> RMAN-00571: ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> RMAN-00571: ===========================================================
> RMAN-07005: error during channel cleanup
> RMAN-07004: unhandled exception during command execution on channel
> default
> RMAN-10032: unhandled exception during execution of job step 1:
> RMAN-10031: ORA-65535 occurred during call to
> DBMS_BACKUP_RESTORE.DEVICESTATUS
> RMAN-03008: error while performing automatic resync of recovery catalog
> RMAN-07004: unhandled exception during command execution on channel
> default
> RMAN-10032: unhandled exception during execution of job step 1:
> ORA-01403: no data found
> RMAN-10031: ORA-65535 occurred during call to
> DBMS_BACKUP_RESTORE.GETPARM
>
> RMAN>
>
>
> Did I miss something? Any enlightenment will be highly appreciated.
>
> P.S: The catalog was created with the RMAN command "CREATE CATALOG
> TABLESPACE ..." and I did explicitly create a public synonym for
> DBMS_BACKUP_RESTORE and grant EXECUTE on it to the catalog owner.
>
> Bon-Minh Lam
> --
> To reply to me directly, please mail to: bmlam at online dot de
Received on Mon Mar 12 2001 - 02:25:09 CST