6 Known Issues with Oracle E-Business Suite Certified Configuration

6.1 Environment Type Limitations and Considerations

To avoid conflicts, you cannot have two environments of the same environment type on one system.

6.2 Discoverer Startup Fails on Solaris

When running the addischtl.sh start script, you see the following message:

Registering Discoverer Preference Repository oadutil.reg:Failed to bind to OAD

Workaround

Set the TMPDIR environment variable to the Oracle home directory of the release 8.0.6 visibroker directory. The following is an example of commands required to make this change:

% TMPDIR=/mount_point/product/8.0.6/vbroker
% export TMPDIR

6.3 ocheck Error on AIX

When running the ocheck utility, the script returns the following error:

./ocheck[504]:  psrinfo: not found
./ocheck [504]: sysdef: not found

Total swap space expected: >=2146435072 MB failed

Workaround

You can ignore this error.

6.4 ocheck Fails When Using NFS on Linux

If you use NFS and do not have VERITAS installed on the system, then the ocheck utility fails with the following errors:

$ cd /admin/ebso/ocheck/
./ocheck -product ebiz -preinstall -prettyprint

Package "VRTSvxvm-3.2"  (not installed) == VRTSvxvm-3.2 fail

Workaround

Modify the /admin/ebso/ocheck/ocheck.conf file to remove the VERITAS package from the prerequisite packages. Change the line to the following:

OCC_PACKAGES2_LINUX="XFree86-Xvfb-4.1.0-46"

6.5 Unable to Use the Applications When Logged in as BOL-SETUP

If you experience problems, log into Oracle Applications as the BOL-SETUP user, then perform the following workaround.

Workaround

The following procedure is a workaround for this issue:

1. Log in to the appropriate On Demand URL. The following is an example of the URL:

   http://auohsspaw01.oracleoutsourcing.com:10515/dev60cgi/f60cgi
   
   

2. Log in as sysadmin/sysadmin.

3. Select the Application Developer responsibility.

4. Click Menu from the Applications menu.

5. Change Menu Type to standard in the XBO_APPLICATIONS4.0 menu, and save it. This will recompile the menus in the database.

6. Stop and restart the HTTP server.

7. Log in as the BOL-SETUP user to access the application.

6.6 Unable to Open BOL-Forms

You get the following alert while accessing BOL-Forms through the BOL-SETUP user using the Application Administration responsibility:

Function not available for this responsibility. Change responsibility or contact your system administrator

Workaround

Apply the workaround in Bug number 4034038:

1. Change directory to the location of the formservlet.ini file:

   $ cd <iAS-10222 OH>/Apache/Jserv/etc
   
   

2. Back up the formservlet.ini file:

   $ cp -p formservlet.ini formservlet.ini.pre_4034038
   
   

3. Add the following line to the end of the formservlet.ini file:

   XBOL_TOP=/<Your Apps-11.5.10 Mount-Point>/applmgr/CUSTOM/xbol/11.5.0
   
   

4. Bounce the Apache-Server, using the following:

   $ cd $COMMON_TOP/admin/scripts/<Your Apps-11.5.10 Context-Name>
   $ adapcctl.sh stop
   $ adapcctl.sh start
   

6.7 Data Segment Size on AIX

You must have at least 1 GB of data segment size available for relinking MSC, MSO, and MSR product executables. To check the current size, run the following command:

$  dump  -X64 -o  /usr/ccs/bin/bind64

If the last line returns 0x00000000 for maxDATA, the current maximum size is 256 MB (the default for AIX 32-bit applications).

Workaround

To set the data segment size to 1 GB, set the LDR_CNTRL variable to:

LDR_CNTRL_MAXDATA=0x40000000

6.8 Unable to Launch gatekeeper.properties Window on AIX Using startgkconfig.sh

If you are unable to launch the gatekeeper.properties window using the startgkconfig.sh script, use the following workaround.

Workaround

The following is the workaround:

1. Edit the $ORACLE_HOME/discwb4/discwb.sh script. Change VBROKER_JAVAVM=<8i ORACLE_HOME>/jre1162o/bin/jre to:

   VBROKER_JAVAVM=<8i ORCLE_HOME>/jre1183/bin/jre
   
   

2. Edit the $ORACLE_HOME/jre1183/bin/jre file. Change the line export CLASSPATH=$JAVA_HOME/lib/rt.jar:$JAVA_HOME/lib/i18n.jar:$JAVA_HOME/lib/math.jar to:

   export CLASSPATH=$JAVA_HOME/lib/rt.jar:$JAVA_HOME/lib/i18n.jar:$JAVA_HOME/lib/math.jar:$CLASSPATH
   
   

3. Run the startgkconfig.sh script.

6.9 Discoverer OAD Does Not Start on Solaris

On Solaris, Discoverer OAD does not start when the VBROKER_ADM and TMPDIR environment variables point to directories of different devices. The oad.log file would contain the OAD: Fatal Error [Cross-device link] error message while registering with OAD.

To workaround, set the TMPDIR environment variable to a directory on the same device as the one pointed by VBROKER_ADM before starting OAD. More details can be found in bug number 4077027.

6.10 Directory /igold Must Exist Before Installation on Solaris

On Solaris, before starting the installation of Oracle E-Business Suite Certified Configuration, create a soft link /igold pointing to your installation mount point. For example, /igold -> /tabci. (This workaround is not needed if an igold instance is already present on the same system.)