This chapter describes issues associated with Oracle Fusion Applications Provisioning and Oracle Fusion Applications Patching It includes the following topics:
This section describes general issue and workarounds. It includes the following topics:
Section 45.1.1, "Provisioning: Error in Functional Setup Post-Configure Log File"
Section 45.1.2, "Patching: Using Smart Update to Apply Patches to Oracle WebLogic Server"
Section 45.1.3, "Provisioning: Shut Down Oracle Services Before Database Installation"
Section 45.1.5, "Patching: Ignore Warning Message During jazn Patching"
Section 45.1.6, "Patching: Workaround for Patching B2B Metadata in Offline Mode"
Section 45.1.7, "Provisioning: Ignore Preverify Failure Warnings"
Section 45.1.8, "Provisioning: Use Node Manager To Start Servers in a Provisioned Environment"
Section 45.1.9, "Provisioning: Verify Node Manager Status Before Running the Postconfigure Phase"
Section 45.1.10, "Provisioning: Preverify Phase Fails with Identity Store SSL Validation Error"
Section 45.1.11, "Provisioning: Install Phase Hangs While Registering OAM"
Section 45.1.12, "Provisioning: Add Variable When Provisioning a Transaction Database"
The following error appears in the functional setup post-configure log file (runProvisioning-fs-postconfigure.log):
**************FLEXFIELD DEPLOYMENT REPORT**************
<ERROR>
Application TopologyManagerServices is not registered with Deployments and ASK tables.
--Aborting Flexfield Deployment
***********************END*****************************
This error means provisioning was unable to import flex data for the Topology Manager Service application. The error is harmless since this application does not have flex field data.
In order to have Smart Update apply patches to the Oracle WebLogic Server after you have completed the provisioning of a new Oracle Fusion Applications environment, you must ensure that the patches are stored in a writable location. If they are not, Smart Update cannot apply the patches.
Before you install Oracle Database using the Provisioning Wizard, you must shut down all Oracle and Oracle-related services. Failure to do so will result in database installation failures.
On starting the Provisioning Wizard and proceeding to the Identity and Policy Management Configuration page, you cannot enter any value in the password field.
This issue occurs on Oracle Linux 5 and Red Hat Enterprise Linux 5 only when Smart Common Input Method (SCIM) is used along with VNC to perform tasks on a remote system. The issue is not seen when Fusion Applications Provisioning GUI is accessed directly on the computer or accessed using .ssh.
There are two ways to work around this issue:
Add the following entry in the ~/.scim/config file:
/FrontEnd/X11/Dynamic = true
Remove the SCIM packages completely from the computer
jazn PatchingIncluded as per bug: 12913937
While patching applications policies (system-jazn-data.xml files), you can safely ignore the following warning message:
WARNING: Cannot instantiate permission class
Included as per bug: 12913914
Before you perform Step 3, "Import the patched export file" under "Patching Oracle B2B Metadata," ensure that you do the following setup:
The Host Trading Partner name must be "MyCompany" in the B2B repository. To confirm this:
Log in to the B2B console at: http://HOST:PORT/b2bsonsole.
Change the Host Trading Partner name to "MyCompany," log out, and then import the patched export file.
After the import, log in to the B2B console again and change the Host Trading Partner back to its original name.
Included as per bug 12915561
During provisioning, the preverify phase (target) may display a message that some of the Solaris operating system patches are missing. On Solaris x86-64, the following perverify failures may be reported:
WARNING: Check:Patches failed. Checking for 127111-02; Not found. Failed <<<< Checking for 137111-04; Not found. Failed <<<<
These errors do not halt the perverify phase or the provisioning process and can be safely ignored.
Included as per bug 12927965
In order to correctly start a server in an Oracle Fusion Applications provisioned environment, you must always use Node Manager instead of the generic Oracle WebLogic Server scripts. This ensures that the fusionapps start parameters will always be used by the server process(es).
Once the Administration Server is up, you can start the Managed Server by going to the Admin console (since the console uses Node Manager "under the covers" to start Managed Servers).
Included as per bug: 11686896
When you run the postconfigure phase, there is no process in place to alert you if the Node Managers are not running. To check the status of Node Managers, run the following command before running the postconfigure phase:
ps -aef|grep Node netstat -a|grep 5556
If the Node Managers are started, you will receive a message about the status of the Node Managers on that port. For example:
<Mar 23, 2011 3:09:26 PM> <INFO> <Secure socket listener started on port 5556>
If the Node Managers are not started, follow the instructions in Section 45.1.8, "Provisioning: Use Node Manager To Start Servers in a Provisioned Environment" for startup directions.
Included as per bug: 12933328
If the Identity Store Enabled SSL check box is selected on the Identity Management Configuration screen during the creation of a provisioning plan, you will see the following validation error during the preverify phase:
Error 1: IDSTORE_IS_SSL_ENABLED : Validation error. IDSTore SSL flag is currently false. Error 2: OAM11G_OIM_OHS_URL :Invalid OIM RUL Protocol.
This failure can be ignored. To suppress prerequisite failures and allow provisioning to continue, specify the -ignoreSysPrereqs true when you run the Provisioning Wizard (provisioningWizard.sh) or when you run a provisioning phase (runProvisioning.sh). The syntax is:
(UNIX)
cd framework_location/provisioning/bin ./provisioningWizard.sh -ignoreSysPrereqs true
path_to_script/runProvisioning.sh -ignoreSysPrereqs true -plan provisioning_plan_location -target preverify
(Windows)
cd framework_location\provisioning\bin\provisioningWizard.bat -ignoreSysPrereqs true
path_to_script\runProvisioning.bat -ignoreSysPrereqs true -plan provisioning_plan_location -target preverify
Note that the -ignoreSysPrereqs true argument must be specified for all phases that follow the preverify phase: install, preconfigure, configure, configure-secondary, postconfigure, startup, and validate.
Included as per bug: 12937115
If you use PuTTY to create the user session when running the install phase of provisioning, the OAM policy domain registration may fail. To avoid this issue, create the user session using VNC instead.
Included as per bug: 12919697
You can improve performance when installing a transaction database with the Provisioning Wizard by adding the following variable to the command line syntax used to start the wizard:
export SKIP_ROOTPRE=TRUE
This section describes configuration issues and their workarounds. It includes the following sections:
Section 45.2.2, "Provisioning: Verify Length of PATH Before Oracle Database Installation"
Section 45.2.6, "Provisioning: Restart SOA Server for HCM, IC, PRC, PRJ, and SCM Domains"
Section 45.2.7, "Provisioning: Virtual Memory Tuning (Windows)"
Section 45.2.8, "Provisioning: Postconfigure Fails on CommonDomain Host"
shmmax Before Oracle Database InstallationBefore you install Oracle Database using the Provisioning Wizard, make sure the value of the kernel parameter shmmax is greater than the value of SGA Memory.
The value of SGA Memory (sga_target) is 9 GB in the default DBCA template. If you are running DBCA using the production DBCA template packaged with Oracle Fusion Applications Provisioning, the value of the SGQ Memory is 18 GB.
Ensure that shmmax > (shmall * shmmni) > SGQ Memory, where shmmax, shmall, shmmni are kernel parameters.
For example, to retrieve the values of these kernel parameters, do the following:
user@host> /sbin/sysctl -a | grep shm kernel.shmmni = 4096 kernel.shmall = 3145728 kernel.shmmax = 12884901888
To set the value of a kernel parameter:
user@host> /sbin/sysctl -w sys.kernel.shmmax=value
Before installing Oracle Database, verify that the length of the PATH environment variable is less than 900 characters. Use this command to check the character count:
env | grep ^PATH= | wc -m
When installing a transaction database, the database installer requires a unique identifier (uid) of six digits or less. The Provisioning Wizard prerequisite check for the Install an Applications Transaction Database option gives an error if the uid has 7 or more digits.
Switch to a user whose uid is six digits or less to fix the error.
These two installers are no longer staged in the provisioning repository:
Oracle JDeveloper 11g (installers/JDEV)
Oracle JDeveloper 11g Extensions (installers/JDEV_Extensions)
These two installers can be found, independent of the provisioning repository, as part of the Oracle Fusion Applications Product Media pack.
Included as per bug 12909821
The installers for Oracle Forms Recognition (OFR) and Oracle Document Capture (ODC) have been added to the Oracle Fusion Applications Product Media Pack. These two installers are downloaded into the same directory as the other applications-related installers described in Section 2.3, "Creating the Provisioning Repository," in Oracle Fusion Applications Installation Guide.
For complete instructions about using these two products once they are downloaded, see the "Financials" chapter of Oracle Fusion Applications Post-Installation Guide.
Included per bug 12917769
If the SOA Server is up and running for Oracle Human Capital Management (HCM), Oracle Incentive Compensation (IC), Oracle Procurement (PRC), Oracle Projects (PRJ), and Oracle Supply Chain Management (SCM) domains at the end of the provisioning startup phase, use the Admin console to restart those servers. This allows certain configurations that were done during provisioning to take effect.
Change the Virtual Memory setting to the "Custom Size." The recommended Initial Size is one and one-half times the Physical RAM and Maximum Size is three times the physical RAM.
Do not provision a topology where all the following conditions are true:
Local domain is enabled, and...
UCM_server1 does not reside on the same host as AdminServer, and...
The CRM Marketing or Sales offering is selected
Provisioning this configuration will result in failure of the postconfigure phase on the CommonDomain host.
This section describes documentation errata. It includes the following topics. There are no documentation errata items to report at this time.