Application Server Installation Issues

After installing Domain Administration Server, Node Agent is listed as installed and compatible (6379283)

If you install the Application Server Domain Administration Server, the Application Server Node Agent is listed as installed and compatible in subsequent installation sessions. This issue arises because the Domain Administration Server and Node Agent use the same set of packages and differ only in configuration.

Solution None. The software to support node agents is installed. To create a node agent, use the asadmin create-node-agent command. See create-node-agent(1) for more information.

Installer does not recognize host name user enters in configuration page (4931514)

The installer prompts you for the “server name” for the Application Server. However, the installer uses the actual host name of the machine regardless of what you input in the text field.

Solution If the server name is different from the server’s host name, become superuser and type the following in the domain directory of interest (the “server root” directory):

# find . -type f -exec grep -l $HOSTNAME {} \\ ;

Then, change the file contents appropriately.

Cannot start domain on Linux (6396102)

On Linux, attempts to start a domain generate an exception that refers to libstdc++. This occurs because Application Server requires certain compatibility libraries on Linux that are not installed by default.

Solution Install the following compatibility libraries:

• compat-gcc-7.3-2.96.build.i386.rpm

• compat-gcc-c++-7.3-2.96.build.i386.rpm

• compat-libstdc++-7.3-2.96.build.i386.rpm

These libraries are not installed by default, but are available in the Red Hat Linux distribution. Note that the value of build may differ on different versions of Red Hat Linux.

On Windows, HADB Instance Is Not Starting in Application Server (6480152)

If a Windows machine is not connected to the network, the HADB instance does not start.

Solution Connect Windows machine to the network.