Adding an Alias Hostname with Oracle E-Business Suite Release 12 (Doc ID 603883.1)

Last updated on AUGUST 11, 2024

Applies to:

Oracle Applications DBA - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
Oracle Applications Manager - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
Oracle E-Business Suite Technology Stack - Version 12.0.6 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.

Purpose

This document describes the process of configuring an Oracle Applications Release 12 system to use an alias hostname in case this was not done during the installation using 'rapidwiz -servername <alias-hostname>'.
The most current version of this document is <Note 603883.1> on My Oracle Support.

Attention: This procedure is NOT intended for a complete virtual hosting setup; it is ONLY to setup an alias hostname. For any additional implementation options please check <Note 380483.1> Oracle E-Business Suite Release 12 Additional Configuration and Deployment Options or contact your Oracle Account Manager or Oracle Software Support.

Virtual Aliasing HAS NOT been CERTIFIED by Development in this manner.
Although it is likely to work it HAS NOT been fully tested / vetted.

If one makes use of this configuration, ANY and ALL issues that arise MUST be reproduced in a 'non-aliased' standardized environment before support can be offered.

This configuration SHOULD NOT be used in a PRODUCTION environment as it only being offered as a testing alternative at this time.

In regards to Oracle's current certified Virtualization solutions with E-Business Suite refer to the following:
- 464754.1 Certified Software on Oracle VM
- <Note: 794016.1> - Hardware Vendor Virtualization Technologies on non x86/x86-64 Architectures and EBS

All customers having incorrect defined aliases for apps nodes will hit <Bug 16783195> - AFTER <Patch 16196190>, AUTOCONFIG ON APPS CREATES SQLNET.ORA WITH VALID NODES = Y .
In few words, if the alias is not correctly resolved to the IP, then after applying CPU Patch 16196190, they will get errors like:
TNS-12533: TNS:illegal ADDRESS parameters
TNS-12560: TNS:protocol adapter error
TNS-00503: Illegal ADDRESS parameters

This is because the patch is introducing a new functionality by creating $TNS_ADMIN/sqlnet.ora on apps tier and Profile Option FND_SQLNET_ACCESS is not taken in account for the Applications tier, but it is still true for database tier. The new NetServiceHandler.java 120.19.12010000.8 has introduced a new method generateAppsSqlNet which intentionally hard codes the profile option to ALLOW_RESTRICTED as per internal
Bugs 14757757 - SECURE APPTIER TNS-LISTENER IN TOOLS ORACLE_HOME and BUG 16321978

If the aliases are correctly defined and they are resolved to correct IP address the customers won't have any issue.

So in few words, double check the /etc/hosts file.

The procedure uses Rapid Clone and AutoConfig to convert an existing Release 12 environment to use an alias hostname for the Application tier and configure - which is required - the Concurrent Managers on the physical hostname. Also if EM DBconsole is installed and being used, and was configured for a hostname that is no longer current, it should be reconfigured.

Scope

Note: If an alias hostname has already been configured (at install time running 'rapidwiz -servername <alias-hostname>' to use an alias) it is possible to only perform the actions related to Concurrent Processing and Enterprise Manager DBconsole.