Sie sind auf Seite 1von 5

Document Display

15/12/2016 20:45

RUP Installer fails with ODI-10190: The user FUSION_APPS_PROV_PATCH_APPID has its
account expired (Doc ID 1666023.1)
In this Document
Symptoms
Cause
Solution
References

APPLIES TO:
Oracle Fusion Applications Common Components - Version 11.1.4.0.0 and later
Information in this document applies to any platform.
Checked for Currency on 07-Nov-2016

SYMPTOMS
While upgrading FA 11.1.4 to 11.1.5, the Rup Installer is throwing below error and halting the upgrade process.

[2014-03-13T05:54:37.101-04:00] [apps] [ERROR] [] [oracle.apps.ad] [tid: 13] [ecid:


0000KIurJ4bDCgP_qdH7iY1J8O12000004,0] CFGLOG00169 : Validation step "Oracle Data Integrator (ODI)" failed.[[
oracle.patchset.common.exception.PatchsetException: COMMONEX-00016 : Errors encountered when
running validation step "oracle.as.install.fapatchconfig.plugin.impl.OdiValidation".
Action : See the log for details.
at
oracle.as.install.fapatchconfig.plugin.impl.OdiValidation.executeBeforeConfig(OdiValidation.java:5
at
oracle.as.install.fapatchconfig.OfflinePreConfiguration.runPlugin(OfflinePreConfiguration.java:39)
at
oracle.as.install.fapatchconfig.PluginConfiguration.runPlugins(PluginConfiguration.java:119)
at
oracle.as.install.fapatchconfig.PluginConfiguration.handlePlugins(PluginConfiguration.java:98)
at
oracle.as.install.fapatchconfig.PluginConfiguration.doExecute(PluginConfiguration.java:76)
at
oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:371)
at
oracle.as.install.fapatchconfig.ConfigAssistantBase.execute(ConfigAssistantBase.java:196)
at
oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
at
oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerforme
at
oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:16)
at
oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:64)
at
oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(Standard
at
oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(Configuration
at
oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86
at java.lang.Thread.run(Thread.java:662)
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=s0d1b0v1q_14#SYMPTOM

Page 1 of 5

Document Display

15/12/2016 20:45

Caused by: oracle.apps.ad.common.exception.ADException: Failed to check for ODI Setup.


at oracle.apps.ad.fapmgr.sdk.FAPManagerSDK.validateODISetup(FAPManagerSDK.java:1520)
at
oracle.as.install.fapatchconfig.plugin.impl.OdiValidation.executeBeforeConfig(OdiValidation.java:4
at
oracle.as.install.fapatchconfig.OfflinePreConfiguration.runPlugin(OfflinePreConfiguration.java:40)
... 13 more
Caused by: oracle.odi.core.security.AccountExpiredException: ODI-10190: The user
FUSION_APPS_PROV_PATCH_APPID has its account expired.
at
oracle.odi.core.security.SecurityManager.doODIInternalAuthentication(SecurityManager.java:374)
at oracle.odi.core.security.SecurityManager.createAuthentication(SecurityManager.java:271)
at oracle.apps.ad.fapcore.sdk.ODIConfigureUtil.create(ODIConfigureUtil.java:159)
at oracle.apps.ad.fapcore.sdk.ODIConfigureUtil.initODI(ODIConfigureUtil.java:104)
at oracle.apps.ad.fapcore.sdk.ODIConfigureUtil.getInstance(ODIConfigureUtil.java:55)
at oracle.apps.ad.fapcore.ODIPatchingCommand.checkForODISetup(ODIPatchingCommand.java:216)
at oracle.apps.ad.fapmgr.sdk.FAPManagerSDK.validateODISetup(FAPManagerSDK.java:1516)
... 15 more
]]

CAUSE
Under FUSION_ODI schema, the table SNP_USER which holds the user details of FUSION_APPS_PROV_PATCH_APPID
had the expiry date set to 01-Jan-1970 which is a past date and the Password column was blank.

SQL> show user


USER is "FUSION_ODI"
SQL> select WUSER_NAME,PASS,USER_EXPIRACY_DATE,AUT_SUPERVISOR from SNP_USER where
WUSER_NAME='FUSION_APPS_PROV_PATCH_APPID';
WUSER_NAME
FUSION_APPS_PROV_PATCH_APPID

PASS

USER_EXPIRACY_DATE
1-Jan-70

AUT_SUPERVISOR
1

This was not allowing the user to login to ODI studio.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=s0d1b0v1q_14#SYMPTOM

Page 2 of 5

Document Display

15/12/2016 20:45

The RupInstaller during execution checks for authentication based on the expiry date set on the table SNP_USER.
Please note, an error like "ODI-10199: Incorrect ODI username or password" may be what is shown in the patching
logs. This would be the case when the USER_EXPIRACY_DATE on table SNP_USER is set to a future date but the PASS
column is still null.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=s0d1b0v1q_14#SYMPTOM

Page 3 of 5

Document Display

15/12/2016 20:45

SOLUTION
The password can be reset in 2 ways:

1. Reset password through ODI Studio:


a. Run below ldapsearch command to get the actual password of user FUSION_APPS_PROV_PATCH_APPID.
/u01/app/oracle/product/fmw/idm/bin/ldapsearch -h idmhost -p 6501 -D "cn=orcladmin" -w -b
"cn=FusionDomain,cn=JPSContext,cn=FAPolicies" -s sub "orclCSFName=FUSION_APPS_PROV_PATCH_APPID"
b. Log into ODI Studio using the default ODI Supervisor user (SUPERVISOR) or a different ODI user that has ODI
Supervisor privilege.
Open user FUSION_APPS_PROV_PATCH_APPID and reset it's password to the value that we got from the ldapsearch
command and reset the expiracy date.
c. Check the table SNP_USER to see the USER_EXPIRACY_DATE is set to the reset value and the column 'PASS' is
populated with an encrypted value (which was NULL before).
d. Now login to ODI studio with FUSION_APPS_PROV_PATCH_APPID and the login should be successful
e. Rerun the RUP Installer

2. Reset passsword manually from backend:


https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=s0d1b0v1q_14#SYMPTOM

Page 4 of 5

Document Display

15/12/2016 20:45

If the ODI studio is not installed and configured, then take the below steps to reset the password of
FUSION_APPS_PROV_PATCH_APPID maanually through backend tables.
a. Run below ldapsearch command to get the actual password of user FUSION_APPS_PROV_PATCH_APPID.
/u01/app/oracle/product/fmw/idm/bin/ldapsearch -h idmhost -p 6501 -D "cn=orcladmin" -w -b
"cn=FusionDomain,cn=JPSContext,cn=FAPolicies" -s sub "orclCSFName=FUSION_APPS_PROV_PATCH_APPID"
b. On fusion server, run below command to encrypt the password
cd /u01/APPLTOP/fusionapps/odi/oracledi/agent/bin
encode <password we got from step a>
c. Executed the bellow SQLs to update the password and expiry date in backend table:
Update FUSION_ODI.SNP_USER set USER_EXPIRACY_DATE='09-APR-2034' where
WUSER_NAME='FUSION_APPS_PROV_PATCH_APPID';
Update FUSION_ODI.SNP_USER set PASSSWORD='<encrypted password from Step b>' where
WUSER_NAME='FUSION_APPS_PROV_PATCH_APPID';
commit;
d. Rerun the RUP Installer
Note: Always try to use the first method in resetting the passsword whereever possible.

REFERENCES
NOTE:1525052.1 - 11.1.5 Upgrade RUP Phase 2 Fails On Offline Preverification For ODI
NOTE:1511501.1 - Oracle Fusion Applications Technical Known Issues - Release 5
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=s0d1b0v1q_14#SYMPTOM

Page 5 of 5

Das könnte Ihnen auch gefallen