Oracle9i Application Server Release Notes Addendum
Release 2 (9.0.2.0.1) for Microsoft Windows Part No. A90336-10 |
|
This chapter discusses the following topics:
This section describes general issues and their workarounds for Oracle9iAS InterConnect.
When reinstalling the HTTP adapter after deinstalling the HTTP adapter component, the oaiservlet
application must be undeployed. If this step is not completed, the reinstallation of the HTTP adapter fails.
To workaround this issue, undeploy oaiservlet
using the following commands:
%dcmctl undeployApplication -a oaiservlet -co OC4J_OAI
where dcmctl
is in the ORACLE_HOME
/dcm/bin
directory.
When using iStudio to deploy metadata to Oracle Workflow and the service name is longer then 30 characters, the following error message may display:
"BES Error: Could not connect to Messenger service: OMB or Oracle AQ is down"
Complete the following steps as the workaround for this issue:
Shut down iStudio and the repository.
Run SQL*Plus and connect to the hub database using the following:
@ - sqlplus oaihub902/<hubuser_password>@tnsname
Replace <service_name_truncated_to_30_characters>
with your service name truncated to 30 characters.
Run the following SQL*Plus command:
- update lookup set value = '<service_name_truncated_to_30_characters>' where key = 'SYSTEM';
For example:
update lookup set value = 'IASDB.SKCHATTE_PC.US.ORACLE.CO' where key = 'SYSTEM';
The Oracle9iAS InterConnect installer copies the oaiservice.ini
file incorrectly. Complete the following steps for the Oracle9iAS InterConnect Oracle Management Server (OMS) plug-ins to function correctly.
Shutdown OMS.
See Also: Oracle Management Server User Guide |
Access the ORACLE_HOME
\oai\9.0.2\console\
directory and open the oaiservice.ini
file.
Replace all instances of '\' with '\\' in this file.
Re-start OMS.
When installing Oracle9iAS InterConnect, the OMSExternalRegistry.registry
file is incorrectly copied. This causes the Oracle Management Server (OMS) plug-ins for Oracle9iAS InterConnect to function incorrectly.
To workaround this issue, complete the following steps:
Shutdown OMS.
See Also: Oracle Management Server User Guide |
Access the ORACLE_HOME
\sysman\config\
directory and open the OMSExternalRegistry.registry
file.
Replace all instances of '\' with '\\' in this file.
This will affect the following lines:
/com/oracle/sysman/em/oms/services/external/oaiservice/args=<make changes here>
and:
/com/oracle/sysman/em/oms/services/external/oaiservice/service_classpath=<make changes here>
Re-start OMS.
This section describes configuration issues and their workarounds for Oracle9iAS InterConnect.
This issue applies only for the CICS adapter when using Universal Client for ECI. The configuration uses the SNA protocol to communicate to the ECI server, therefore, the path to SNA binaries should be added to the service_path
in the adapter.ini
file.
The path to Universal Client should have been added to the service_path
by the Oracle9iAS InterConnect installer. But, because the installer gives precedence to Universal Client if both UC and SNA clients are found on the same machine, this manual step is necessary.
This section describes known errors in the documentation.
To browse PeopleSoft in iStudio, the path to PeopleSoft client binaries must be added to the PATH
variable in iStudio.bat
file.
To update the PATH variable, edit the iStudio.bat
file and add the location of PeopleSoft client binaries to the PATH
variable. For example, if your PeopleSoft client is installed under the C:t750
directory, add C:t750\bin\CLIENT\WINX86
to the PATH
variable.
The user starting the adapter in an NT service must use the credentials of the user that installed the adapter. At runtime, use the credentials of the NT user that installed the adapter and not the system user. If the agents are running as NT services, make sure that in the Startup for that service, the Log on As This Account is checked and contains the credentials of the NT user account used to install the adapter.