Datapatch Fails To Rollback DataPump Merge Patches In Some Cases and Reports ORA-00600 or ORA-7445 [PETIFI]
(Doc ID 2372413.1)
Last updated on MAY 18, 2021
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
- Running datapatch to rollback a merge patch which contains DataPump fixes (for simplicity MLR Patch 27566967 is used as an example), the following error is seen:
ERROR at line 1:
ORA-00600: internal error code, arguments: , , , , , , , , , , , 
ORA-06512: at "SYS.KUPV$FT", line 1201
ORA-06512: at line 2
- Even if datapatch shows rollback process completed with success:
SQL> BEGIN dbms_sqlpatch.patch_finalize; END;
PL/SQL procedure successfully completed.
opatch output reports errors for the rollback operation:
- The error can be different and depends on the platform, e.g:
> on AIX, the error is: ORA-00600 
> on Linux, the error is different: ORA-7445[petinx] or ORA-7445 [PETIFI]
but for all cases, the call stack will contain functions: petifi -> pevm_icd_call_common and the internal error is always reported when running SYS.KUPV$FT.create_gbl_temporary_masters();
The MLR Patch 27566967 is installed and de-installed successfully if for the rollback operation the MLR patch is the only patch from the installation queue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document