Size of Oracle Binary Becomes Small or the Size of Oracle Binary Differs on Different Nodes After Enabling IBM Guardium
(Doc ID 2547112.1)
Last updated on JANUARY 01, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
Difference in oracle binary size and checksum observe for <ORACLE_HOME>/bin/oracle in a Real Application Cluster environment
The output of md5sum and the size of the oracle binary are different on one of the nodes after enabling IBM Guardium
Server MD5SUM Value Binary Size
<nodename1> 5d1868a44aad1d20f710dfdbeee70e1a 169471
<nodename2> 3dacefa06ae3b9d51cd2e84aef4f46ee 333109399
<nodename3> 7ee8e58cbf4e3fae5e4ccb7222fef7b0 169471
<nodename4> c15e15a046db49125fe1fb860bba6a10 169471
The size of the oracle binary becomes very small, example: 169471 bytes in few of the nodes
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