Datapatch verbose fails with /usr/bin/ksh: No such file or directory
(Doc ID 2331571.1)
Last updated on JANUARY 16, 2020
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Installing Database Patch Set Update 220.127.116.11.170814 (26609783) with opatch apply succeeds.
However when trying to load modified SQL in the database the ./datapatch -verbose fails with /usr/bin/ksh: No such file or directory
The SQLPATCH invocation logs show below error
/refresh/home> tail -f sqlpatch_invocation.log
Connecting to database...OK
Note: Datapatch will only apply or rollback SQL fixes for PDBs
that are in an open state, no patches will be applied to closed PDBs.
Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
(Doc ID 1585822.1)
catcon: ALL catcon-related output will be written to /refresh/home/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_6082_2017_10_07_20_18_53/sqlpatch_catcon__catcon_6082.lst
catcon: See /refresh/home/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_6082_2017_10_07_20_18_53/sqlpatch_catcon_*.log files for output generated by scripts
catcon: See /refresh/home/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_6082_2017_10_07_20_18_53/sqlpatch_catcon__*.lst files for spool files, if any
/usr/bin/ksh: No such file or directory
Applying Database Patch Set Update 18.104.22.168.170814 (26609783)
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