Installation Notes

Refer to Oracle Waveset Installation for detailed product installation instructions.

• On 64–bit AIX systems, the Oracle Waveset installer will halt with the error “attach to native process failed” if run using an IBM JVM supplied with either WebSphere 7.0 Fix Pack 5 (7.0.0.5) or Fix Pack 7 (7.0.0.7). To fix this issue, install Fix Pack 9.

  Note that the os.arch=ppc property must be set when performing an upgrade installation of Oracle Waveset on 64–bit AIX systems. See the following bullet point for details. (ID-22285)

• The Oracle Waveset installer may not run with a 64-bit JDK. (ID-18534)

  Workarounds:

  • Install manually.

  • Use a 32-bit version JDK to run the installer.

  • Set os.arch=ppc by setting JAVA_OPTS (used by the install script) to get through the install. For example,

    export JAVA_OPTS="-Dos.arch=ppc" install

  • Or, if JAVA_OPTS already contains needed options:

    export JAVA_OPTS="$JAVA_OPTS -Dos.arch=ppc" install

• When installing Oracle Waveset do not mix JDKs from different vendors . For example, if you are running Identity Manager using the IBM JDK on WebSphere, use the IBM JDK to install Identity Manager. Do not use JDKs from different vendors because data encrypted under one JDK cannot be read by a JDK from another vendor. (ID-17800)

• When running Oracle Waveset on multiple physical servers, the servers' system clocks must be synchronized. Each Oracle Waveset server regularly issues a timestamped “heartbeat” to the Oracle Waveset repository. If any server observes that another server's heartbeat is too old (by default, five minutes), then it will mark that server as “recovered” and mark all tasks currently executing on that server as terminated. Proper Oracle Waveset operation requires that all server clocks be synchronized to within five minutes of each other, and preferably within one minute. (ID-22418)