While applying Oracle PSU patches on 12cR1 database and checking the view dba_registry_sqlpatch the STATUS was “WITH ERRORS”.
In order to fix this you need to check the log file for patch (you can find the location for the log file from dba_registry_sqlpatch OR using DBMS_QOPATCH package) , in my case the error was referring to database vault type:
create or replace type dvsys.ku$_dv_realm_member_t as object
ERROR at line 1:
ORA-22308: operation not allowed on evolved type
to fix this:
SQL> drop type dvsys.ku$_dv_realm_member_t validate;
In this blog article, I will illustrate the ability to change RMAN configuration through SQL using DBMS_BACKUP_RESTORE package. This package is not well known and is not documented.
Traditionally we use RMAN interface utility as shown:
rman target /
RMAN> show all;
Let us now explore changing RMAN configuration through the package:
SQL> VARIABLE rman_config NUMBER;
SQL> EXECUTE :rman_config := SYS.DBMS_BACKUP_RESTORE.SETCONFIG(‘BACKUP OPTIMIZATION’,’ON’);
Checking through the RMAN interface utility, we can see that the configuration change is reflected successfully:
What are the benefits?
This will help you with the provisioning and automation of your new databases to have identical RMAN configuration. Also, this will enable you to propagate RMAN configuration changes to all of your landscape.
for some reason my sessions was kicked out and the patch process didn’t complete. Then, when i tried to re-apply the patch the following error was thrown:
UtilSession failed: Lock file left by a different patch, OPatch will not try re-using the lock file.
OPatch failed with error code 73
remove the patch lock file using the below UNIX command:
then try to re-apply the patch again.