|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit) B15511-05 |
|
|
Previous |
Next |
This chapter describes the issues with Oracle Application Server InterConnect (OracleAS InterConnect). This chapter contains the following topics:
This section describes the installation issues and the workarounds for OracleAS InterConnect. It contains the following topics:
Problem
Usually, on Linux, the path of make is not /bin/make but /usr/bin/make. However, Oracle Universal Installer (OUI) looks for make in the /bin directory. This causes an error during installation.
Workaround
Before installing OracleAS InterConnect on Linux, ensure that /bin/make exists. If it doesn't exist, then make a soft link from /usr/bin/make. Run the ln -s /bin/make /usr/bin/make command as root.
Problem
When installing the Database or Oracle Applications adapter on the same database with an existing oai schema, then the Specify Spoke Database Connection Information page is displayed with the Continue button. This button appears instead of the Ignore button.
Workaround
If the oai schema already exists in the hub database, then click the Ignore button to continue. When you choose this option, the existing schema will be used by the Database or Oracle Applications adapter install.
Problem
When installing a newer version of OracleAS InterConnect on the same computer, creation of the new oaiusers.dbf file fails. This is because the oaiusers.dbf file exists even after deinstalling the older OracleAS InterConnect version. The deinstall_schema.sql script is configured to deinstall only the hub schema. Thus, oaiusers.dbf still remains after the deinstallation.
Solution
The deinstall_schema.sql script is modified to deinstall both the hub schema and the associated tablespaces. Dropping the tablespaces will delete the oaiusers.dbf file. Hence, you should run the deinstall_schema.sql script on the database manually to delete the oaiusers.dbf file, before you start the deinstallation. This script is located in the following directory:
<MidTierHome>\integration\interconnect\repository\sql
However, if you miss this step and delete the older InterConnect version, then the workaround is to manually delete the oaiusers.dbf file, which is located in the WINNT/System32 directory.
Problem
In OracleAS InterConnect 10g Release 2 (10.1.2), you can define non-ASCII event names in iStudio. While doing business process modeling leveraging Oracle Workflow, the non-ASCII event name becomes a part of the internal event name in Oracle Workflow. The internal event name in Oracle Workflow allows only ASCII characters. This conflicts result in errors when OracleAS InterConnect and the Oracle Workflow are integrated in a non-ASCII environment.
Workaround
Use ASCII characters to name event in OracleAS InterConnect.
This section describes documentation errata. It contains the following topics:
Table 5-1 "Operating System Requirements" in Chapter 1, "Overview," in the OracleAS InterConnect Installation Guide includes the mention of HP Tru64 and IBM AIX.
Ignore these two platforms. The support to these platforms have been withdrawn for OracleAS Integration InterConnect 10g Release 2 (10.1.2).
Table 5-1 "Operating System Requirements" in Chapter 1, "Overview," in the OracleAS InterConnect Installation Guide does not include Windows 2003 (32-bit), Linux AMD64, and Linux EM64T platforms.
OracleAS Integration InterConnect Release 2 (10.1.2) supports Windows 2003 (32-bit), Linux AMD64, and Linux EM64T platforms.
Section "JRE Requirements" in Chapter 1, "Overview," in the OracleAS InterConnect Installation Guide mentions the bundles of JRE with OracleAS InterConnect on Sun SPARC Solaris, Linux, and Windows.
Currently, JRE is bundled with OracleAS InterConnect on HP-UX also.
Table 1-3 "Hardware Requirements for Adapters" in Chapter 1, "Overview," in the OracleAS Integration InterConnect Installation Guide contains incorrect Disk space and Memory requirements.
The Disk Space required for installing adapters on Windows and Unix is 400MB and Memory required is 512 MB.
Table 1-1 "Hardware Requirements" in Chapter 1, "Introduction," in the following guides contain incorrect Disk space and Memory requirements:
OracleAS Integration InterConnect Adapter for AQ Installation and User's Guide
OracleAS Integration InterConnect Adapter for DB Installation and User's Guide
OracleAS Integration InterConnect Adapter for MQSeries Installation and User's Guide
OracleAS Integration InterConnect Adapter for FTP Installation and User's Guide
OracleAS Integration InterConnect Adapter for HTTP Installation and User's Guide
OracleAS Integration InterConnect Adapter for SMTP Installation and User's Guide
OracleAS Integration InterConnect Adapter for Oracle Applications Installation and User's Guide
The Disk Space required for installing adapters on Windows and Unix is 400MB and Memory required is 512 MB.
