Mir Sayeed Hassan – Oracle Blog

Oracle DBA – Tips & Techniques | Learn with real-time examples

  • Translate

  • It’s Me






  • My Certificates

  • Links

    My Acclaim Certification : Credly Profile
    My Oracle ACE Pro Profile

  • Achievements

    Awarded Top 100 Oracle Blogs from Worldwide - #RANK 39
  • VISITORS COUNT

  • Verified International Academic Qualification from World Education Service (WES)

    Verified International Academic Qualification from World Education Service (WES)

  • Jobs

RMAN-04015: error setting target database character set to US7ASCII & ORA-06553

Posted by Mir Sayeed Hassan on February 13th, 2019

RMAN-04015: error setting target database character set to US7ASCII & ORA-06553

Database Status

sys@TESTDB>select instance_name,status,version from v$instance;

INSTANCE_NAME    STATUS       VERSION
---------------- ------------ -----------------
testdb           OPEN         11.2.0.4.0

Error log:

[oracle@testdb ~]$ rman target /
Recovery Manager: Release 11.2.0.4.0 - Production on Wed Feb 13 15:37:30 2019
Copyright (c) 1982, 2011, Oracle and/or its affiliates  All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-06553: PLS-213: package STANDARD not accessible
RMAN-04015: error setting target database character set to US7ASCII

The above error occurs after the creation of the database, where the mandatory packages are not executed/skip or RMAN packages has been corrupted.

Try to find by using some below query

sys@TESTDB> select object_name,object_type,owner,status from dba_objects where object_name like '%DBMS_BACKUP%';
no rows selected
sys@TESTDB> select count(*) from dba_objects where object_name like '%DBMS_BACKUP_RESTORE%';

  COUNT(*)
----------
         0

The above query returns “0”, therefore we need to run the given scripts as – CATALOG.SQL & CATPROC.SQL

Login to the database by using sys credential

[oracle@testdb ~]$ !sq

sqlplus /as sysdba
sys@TESTDB> @$ORACLE_HOME/rdbms/admin/catalog.sql;
sys@TESTDB> @$ORACLE_HOME/rdbms/admin/catproc.sql;
sys@TESTDB> @$ORACLE_HOME/rdbms/admin/utlrp.sql;

Note: By running the catproc,.sql package it will invalidate all PL/SQL & other related objects therefore we need to re-compile by running this script utlrp.sql.

[oracle@testdb ~]$ rman target /
Recovery Manager: Release 11.2.0.4.0 - Production on Wed Feb 13 16:02:05 2019
Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
connected to target database: TESTDB (DBID=2783463591)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TESTDB are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_testdb.f'; # default

===========Hence tested & verified in our test env===========