10 Installation Questions, Reinstallation, and Troubleshooting

This chapter provides information about installation questions, reinstalling your AIP software components, and troubleshooting the installation process.

Installation Questions

Both the database schema and application installers will ask for several different URLs. This section provides information about the URLs and their syntax.

About Installation URLs

Both the database schema and application installers ask for several different URLs, such as the JDBC URL for a database. The following sections describe these path statements.

JDBC URL for a Database

Used by the Java application and by the installer to connect to the database.

Item	Description
Syntax	jdbc:oracle:thin:@<host>:<port>/<sid>
<host>	hostname of the database server
<port>	database listener port
<sid>	system identifier for the database
Example	jdbc:oracle:thin:@myhost:1521/mysid

Reinstalling in Silent Mode

Once you have successfully installed the various AIP software components, you may wish to repeat the installation if needed. When the AIP installers run, they generate and store installation information to the ant.install.properties file. You can reinstall your AIP software using the information stored in this file. When using this information, there is no need to enter any information on the window, since everything required is in the ant.installer.properties file, the reinstallation can be run from the command line and is referred to as reinstalling in silent mode since no prompts or data input is required.

To reinstall your AIP software in silent mode using the information stored in the aip.install.properties file, perform the following procedure.

Edit the ant.install.properties file to correct or modify any settings.
Run the installer again from the installation directory using the following command.
```
./install.sh silent
```

Troubleshooting

This section provides information about potential issues that may be encountered during installation.

Database Installer Hangs on Startup

This section provides symptoms and solutions for when a database installer hangs on startup.

Symptom

When the database schema installer is run, the following is written to the console and the installer hangs indefinitely:

Running pre-install checks

Running tnsping to get listener port

Solution

The installer startup script is waiting for control to return from the tnsping command, but tnsping is hanging. Type Control+C to cancel the Installer, and investigate and solve the problem that is causing the tnsping <sid> command to hang. This can be caused by duplicate database listeners running.

Unreadable Buttons in the Installer

If you are unable to read the text within the installer buttons, it probably means that your JAVA_HOME is pointed to a pre-1.7 JDK. Set JAVA_HOME to a Java Development Kit of version 1.7 or later and run the installer again.

Unresponsive Fields when Running Installer in GUI Mode

This section provides symptoms and solutions for when there are unresponsive fields when running the Installer in GUI mode.

Symptom

In GUI mode, you may click in a field and find it unresponsive, and the following message appears in the console window:

XTEST extension not installed on this X server: Error 0

Solution

To run the AIP Online installer in GUI mode you must have the XTEST extension enabled in your X server. Perform the following procedure to enable XTEST in Exceed.

Note:

As this issue is specific to Exceed, you could also use any X11 server like Cygwin + X11 packages or other tools to avoid the problem.

Open Xconfig to edit your Exceed configuration settings.
Go to the X Server Protocol settings.
Select the Extensions tab.
Make sure the XTEST extension is selected.
Restart the X Server and re-run the AIP Online Installer.

Warning: Could not find X Input Context

This section provides symptoms and solutions for the warning: Could not find X Input Context.

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.

ConcurrentModificationException in Installer GUI

This section provides symptoms and solutions for when there is an ConcurrentModificationException in the 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.