ORA-20001 Seen When Running Datapatch due to Incorrect Dpload.sql Script
(Doc ID 2468073.1)
Last updated on NOVEMBER 05, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 12.1]
Information in this document applies to any platform.
When applying or rolling back a patch that contains a faulty version of dpload.sql, various unexpected results or errors may occur, especially in a CDB environment.
The ORA-20001 error is one possibility but there might be other manifestations, not all of which can be predicted.
There are cases when a Database Bundle Patch or PSU has a correct dpload.sql in the apply path, but in the rollback files, it has an incorrect dpload.sql script which contains the improper connect statement:
utl_file.put_line(h, 'connect sys/<password> assysdba');
The following error is reported when running datapatch because the improper version of the dpload file is getting called when the patch is applied or rolled back:
Three cases are identified where datapatch fails to run:
1/ dpload.sql in <BUG>/files/rdbms/admin is not same as <BUG>/files/sqlpatch/<bug>/<aru>/rollback_files/rdbms/admin
2/ Under <BUG>/files/sqlpatch/<bug>/<aru>/rollback_files/rdbms/admin - all 60+ child files of dpload.sql are not present. If all 60+ child files are not present under rollback_files directory then datapatch will fail saying missing files.
3/ Cases where dpload.sql is not present in <BUG>/files/rdbms/admin
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