(16215390) Configuring an external preview server with a switching database may cause database errors when the server starts. The database errors relate to the SiteRepository_production repository.
Workaround: Add an /atg/multisite/SiteRepository_production.properties file to the configuration path for the external preview server. Set the dataSource property in that file as shown below.
dataSource=/atg/dynamo/service/jdbc/SwitchingDataSource
(15960297) Unresolvable server hostname invoked by RMI client.
On some network configurations, the RMI server can have a misinterpreted hostname/IP address. This behavior can cause the RMI client to invoke a remote method using a reference that contains an un-resolvable server hostname (127.0.0.1).
Note that the hostname specified in the initial connection, which is used to locate the registry, has no effect on the hostname embedded in the remote reference to the RMI server.
Workaround: Set the system property java.rmi.server.hostname when starting the server. The value of the property should be the externally reachable hostname (or IP address) of the server.
(13312733) The installation program reports an incorrect error if it runs out of space in the temporary directory.
If the Oracle Commerce Platform installation program runs out of disk space in the temporary directory that it is using, it may report an error message that includes the incorrect statement: “the size of the extracted files to be installed are corrupted.”
Workaround: Remove files from the temporary directory to make more space available for the installation program. For example, if you are installing on a Linux or UNIX server, make sure there is enough space in the /tmp directory. If you cannot free enough space in that directory, set the IATEMPDIR environment variable to the path of a directory in which more space is available. The installation program will use that directory for its temporary files.
(13303341) Stopping the console installation program before completion causes errors during subsequent installation attempts.
If you escape, or stop the console installation program for the Oracle Commerce Platform before it is complete, it does not remove all of its temporary installation files. These files may cause errors when you attempt to install again. For example, you might encounter this problem if you escape the console installation program using the Ctrl-c key combination on Linux and UNIX servers. The error message includes this incorrect statement: “the size of the extracted files to be installed are corrupted.”
Workaround: Delete files named install.dir.* from the temporary directory before running the installation program again. For example, rm -r /tmp/install.dir.* on Linux or UNIX servers. To avoid the problem, use the quit command to exit the console installation program. If you need to correct configurations while the program is running, use the back command.
(13285865) In some situations, a backup ServerLockManager server may not become the primary server if the primary server becomes unavailable. This is typically related to a condition in which more than two servers are running the /atg/dynamo/service/ServerLockManager component.
Workaround: Make sure that only two servers run the /atg/dynamo/service/ServerLockManager component.
