No question at this time
DBA Top 10
1 M. Cadot 7200
2 B. Vroman 3100
3 J. PĂ©ran 2100
4 A. Kavsek 1400
5 P. Tsongayinwe 1300
6 P. Wisse 600
7 D. Walgude 400
7 J. Schnackenberg 400
9 J. Alcroft 200
10 A. Hudspith 100
10 D. Johnson 100
10 B. B 100
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48684
Total active users1329
Act. users last 24h2
Act. users last hour0
Registered user hits last week44
Registered user hits last month235
Go up

opatch error 255 in Azure (Azure is here important)
Next thread: Out-of-place patching for RAC - official documentation
Prev thread: ERROR: ORA-01017: invalid username/password; logon denied

Message Score Author Date
Hi all, updating $ORACLE_HOME/OPatch with latest ...... Kay Gruenenberg Jul 20, 2022, 07:31

Follow up by mail Click here

Subject: opatch error 255 in Azure (Azure is here important)
Author: Kay Gruenenberg, Germany
Date: Jul 20, 2022, 07:31, 28 days ago
Os info: Windows x64
Oracle info: 19c
Error info: 255
Message: Hi all,
updating $ORACLE_HOME/OPatch with latest opatch patch ( run into error 255.
Host is located in Azure cloud. Patch file has been unzipped with Windows file explorer in $ORACLE_HOME. Executing $ORACLE_HOME/OPatch/opatch lsinventory run into error 255.
Long story short - do not use Windows file explorer for unzipping, use another tool like Winzip or 7z. In our case Windows file explorer do not show or extract dangerous files like batch files, Perl or Pythons scripts. After unipping with 7z.exe all files were unzipped and $ORACLE_HOME/OPatch/opatch lsinventory worked well.
We recognized this behaviour from Windows file explorer by uploading Autonomous Health Framework (AHF) from Oracle into Azure and opening this Zip-file. It was only one file shown (README.txt), all other batch-files, folders wit Perl and Pythons scripts were not shown or extracted from File explorer. After installing 7z we could open AHF-zip-file and extracting all files. We also extracted latest OPatch and it ran as expected without any errors.
In the moment we are in investigation why Windows file explorer deals in that way.
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here