- ANKUSH THAVALI
- 01 Dec, 2023
- 0 Comments
- 1 Min Read
RMAN-07539: Insufficient Privileges To Create Or Upgrade The Catalog Schema.
While creating a catalog for the database, received this error.
RMAN> connect target sys/oracle@1234@PRIM connected to target database: PRIM (DBID=605974767) RMAN> connect catalog RMAN_st/rman@catlogdb connected to recovery catalog database RMAN> create catalog RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-07539: insufficient privileges to create or upgrade the catalog schema
Solution :
Connect to catalog db and run the script dbmsrmansys.sql and dbmsrmanvpc.sql$ sqlplus sys/oracle@catalogdb as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Thu May 12 14:35:52 2023 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select name from v$database; NAME --------- CATALOGDB SQL> @?/rdbms/admin/dbmsrmansys.sql alter session set "_ORACLE_SCRIPT" = true * ERROR at line 1: ORA-02248: invalid option for ALTER SESSION PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. alter session set "_ORACLE_SCRIPT" = false * ERROR at line 1: ORA-02248: invalid option for ALTER SESSION SQL> SQL> SQL> @?/rdbms/admin/dbmsrmanvpc.sql Checking the operating user... Passed Usage: dbmsrmanvpc.sql [...] dbmsrmanvpc.sql -all This script performs an upgrade of RMAN base catalog and corresponding VPC users schemas to a new VPD model. RMAN base catalog schema names have to be supplied as command line parameters. Up to 10 schema names can be supplied per script execution. When -all is specified the script attempts to detect the RMAN base catalog schemas automatically
Now try to create the catalog, it should work.
RMAN> connect target sys/oracle@1234@PRIM connected to target database: PRIM (DBID=605974767) RMAN> connect catalog catalog RMAN_st/rman@catlogdb connected to recovery catalog database RMAN> create catalog recovery catalog created RMAN> register database; database registered in recovery catalog starting full resync of recovery catalog full resync complete