After installation, you can verify the actual checksums of installed files against a bill of materials that ships with the product. After configuring your system, create a checksum so that you can compare the system periodically to the checksum. Use the result to analyze changes to your configured system.
After configuring the product, save a new baseline checksum to establish a new checksum standard for your system.
You can use the installver_wbi command to create and compare an inventory of configured files to the currently installed files.
The installver_wbi command can compute a new baseline checksum for the inventory of all files in the installation root directory. Running the command stores the new checksum by default in the sys.inv file within the current working directory. You can specify a different file path and file name. Create the file outside of the installation root directory or exclude the file from comparisons.
Later, compare the checksums in the sys.inv file (or the file that you specified when creating the inventory) to the checksums of the currently installed files to see what files have changed.
The baseline checksum report identifies missing files, additional files, and changed files.
Change directories to the bin directory to start the installver_wbi tool from the command line.
To compute a new baseline checksum for an inventory of configured files, perform the following steps.
When you issue an installver_wbi command from the install_root/bin directory, the status of the command is displayed on the terminal console. To create a log, use the -log parameter.