Modified 21-JAN-2011 Type WHITE PAPER Status PUBLISHED
View Change log
Oracle EBusiness Suite R12.1.x Rapid Install
md5 Checksums
October 2010
Section 1: Overview
Section 2: Download md5 checksum results from Oracle
Section 3: Compare md5 checksums
Section 4: Disk overview, to be used when corrupted files are found
Section 1: Overview
After staging the Rapid Install software with the adautostg.pl script or downloading the Rapid Install software from Oracle Electronic Delivery, the md5 checksums for the staged directory structure can be used to validate the software integrity. Do this by running the md5sum program against the stage area using the oracle created checksum file. This is not an official development document - this procedure was performed/tested using the downloadable Rapidwiz media.
Section 2: Download md5 checksum results from Oracle
Download the md5 checksum results from Oracle as posted below into a local file, for example
The attached files contain the md5 checksum results for every R12.1.1 release. Download the file corresponding to the used release and platform. The md5 checksum has been created without the startCD as it is often being updated, the checksum for the startCD's can be tested separately.
Release 12.1.1 Checksums currently available:
R12.1.1 - Windows
R12.1.1 - IBM AIX
R12.1.2 - Linux on IBM System z
R12.1.1 - Linux 32-bit
R12.1.1 - Linux 64-bit
R12.1.1 - Solaris Sparc 64-Bit
R12.1.1 - HP_UX
R12.1.1 - HP_UX Itanium
Release 12.1.x StartCD Checksums:
R12.1.1 startCD - Version 12.1.1.9
R12.1.1 startCD - Version 12.1.1.10
R12.1.1 startCD - Version 12.1.1.11
R12.1.2 startCD (Linux on IBM System z only) - Version 12.1.1.12.ZLINUX
Section 3: Compare md5 checksums
Compare the Stage with the md5sums downloaded from Oracle (md5sum_.txt). There should not be any FAILED entry in the output. If a FAILED entrie was found, then the stage area was not created successfully. The stage have to be re-created for every component indicating differences (FAILED).
Note: The following example assumes the stage exists in /u01 for Unix and Linux, or F:\ for Windows customers.
Execute the following example commands to check stage using the the md5 checksums
On Unix/Linux:
Install the md5sum utility for your platform if md5sum is not present on your system. If md5sum is not available from your OS Vendor for your OS version (for example HP 11.0), download and install the coreutils package from gnu.org .
$ cd /u01/StageR12
$ md5sum --check md5sum_Linux32.txt > md5sum_result.txt
On Windows:
MKS Toolkit or cygwin needs to be installed to be able to use mdm5sum.
F:\> cd StageR12
F:\StageR12> md5sum --check md5sum_Windows.txt > md5sum_result.txt
Note: The md5 checksum will validate the entire stage area and may take 10 minutes or more depending on hardware resources and system load.
Section 4: Disk overview, to be used when corrupted files are found
When a corrupted file is found the following can be used to identify which part needs to be re-downloaded from edelivery.
Release 12.1.1 Disk overview:
R12.1.1 - Windows
R12.1.1 - IBM AIX
R12.1.2 - Linux on IBM System z
R12.1.1 - Linux 32-bit
R12.1.1 - Linux 64-bit
R12.1.1 - Solaris Sparc 64-Bit
R12.1.1 - HP_UX
R12.1.1 - HP_UX Itanium
No comments:
Post a Comment