Skip Headers
Oracle® Retail Integration Bus Installation Guide
Release 13.1
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

B RIB Installer Common Errors

This section provides some common errors encountered during installation to aid in troubleshooting.

Unreadable Buttons in the Installer

If you are unable to read the text within the installer buttons, it could mean that your JAVA_HOME is pointed to an older version of the JDK than is supported by the installer. Set JAVA_HOME to a Java 1.5 JDK and run the installer again.

"Could not create system preferences directory" Warning

Symptom:

The following text appears in the installer Errors tab:

May 22, 2006 11:16:39 AM java.util.prefs.FileSystemPreferences$3 run
WARNING: Could not create system preferences directory. System preferences are
unusable.
May 22, 2006 11:17:09 AM java.util.prefs.FileSystemPreferences
checkLockFile0ErrorCode
WARNING: Could not lock System prefs. Unix error code -264946424.

Solution:

This is related to Java bug 4838770. The /etc/.java/.systemPrefs directory may not have been created on your system. See http://bugs.sun.com for details.

This is an issue with your installation of Java and does not affect the Oracle Retail product installation.

ConcurrentModificationException in Installer GUI

Symptom:

In GUI mode, the Errors tab shows the following error:

java.util.ConcurrentModificationException
........at
 java.util.AbstractList$Itr.checkForComodification(AbstractList.java:448)
........at java.util.AbstractList$Itr.next(AbstractList.java:419)
........etc.

Solution:

You can ignore this error. It is related to third-party Java Swing code for rendering of the installer GUI and does not affect the retail product installation.

"Couldn't find X Input Context" Warnings

Symptom:

The following text appears in the console window during execution of the installer in GUI mode:

Couldn't find X Input Context

Solution:

This message is harmless and can be ignored.

Error While Unpacking the EAR file

Symptom:

The following text appears in the console window during execution of the installer:

07/12/19 10:53:17 Notification ==>Error while unpacking <app>.ear
java.util.zip.ZipException: error in opening zip file

Solution:

This is a known bug (BugID 6330834) related to Solaris and NFS in Oracle Application Server 10.1.3.3. Follow the workaround documented for this bug: in the opmn.xml file in $ORACLE_HOME/opmn/conf add the following parameter to the java-options for the instance you are installing.

Solution:

-Doc4j.autoUnpackLockCount=-1

After making this change you should reload OPMN, restart the affected OC4J instance(s), and retry the retail application installation.

"Problem occurred during parsing input xml files" Message

Symptom:

The following text appears in the console window during execution of the installer:

ERROR oracle.retail.rib.compiler.Main - Problem occurred during parsing input xml files. Please check the log file(../../../rib-home/application-assembly-home/log) for more details.
.....
Caused by: ValidationException:
.....

Solution:

The rib-deployment-env-info.xml file is validated during the Assembly Phase using stricter criteria than is enforced by the installer input screens. If the validation fails, the installer will print an error message to help you determine the cause of the validation failure. It is recommended that you fix the rib-deployment-env-info.xml file manually, and then re-run the installer with the "Use existing rib-deployment-env-info.xml" option.