NaturalOracle DataGaurd tutorial Series Coming Soon!! Natural
For Any queries, please mail us at support@funoracleapps.com

ORA-20001: Unabled to call fnd_ldap_wrapper.update_user due to the following reason

2 comments
There are scenarios where we face the below error while changing the password for a front end user in R12 or 11i where SSO is enabled.

Error:

Unabled to call fnd_ldap_wrapper.update_user due to the following reason:
ORA-20001: Unabled to call fnd_ldap_wrapper.update_user due to the following reason:
An unexpected error occured. Please contact System Administrator.. (USER_NAME=HSINGH)

Cause:

This may occur due to wrong SSO registration or there may be chances of duplicate entries in the FND_USER table.

Solution:

Step 1.
Delete the USER_GUID in FND_USER for each user table by running the following
SQL> set server output on
SQL> @$FND_TOP/patch/115/sql/fndssouu.sql ;
 
example
SQL> set server output on
SQL> @$FND_TOP/patch/115/sql/fndssouu.sql  USER_NAME;

2. Get the user 'USER_NAME' to log-into EBS through the SSO homepage -> this will populate FND_USER table with the same GUID from OID.
Profile level option are must to be set before the login into SSO.

Note: Make Sure System Profile "Applications SSO Auto Link User" is set to "Y" at "Site" level

If the issue persists then we might be required to  de-register and register the SSO.

2 comments :

Post a Comment

Enabling Automatic Compilation of JSP's in R12

No comments
The manual jsp compilation can be done with ojspcompile.sh. But we can also enable the automatic compilation of jsp's.
   
Steps for Enabling Automatic Compilation of JSP's

Step 1:
Go to $INST_TOP/appl/admin and edit the parameter s_jsp_main_mode and change its value from
'justrun' to 'recompile' in the context file.

cd $INST_TOP/appl/admin/

grep -i s_jsp_main_mode <SID>_<Hostname>.xml

Step 2:
Update
  <jsp_debug_parameters oa_var="s_jsp_main_mode">justrun</jsp_debug_parameters>
to
  <jsp_debug_parameters oa_var="s_jsp_main_mode">recompile</jsp_debug_parameters>

Step 3:
Stop the application services and Run autoconfig .
$INST_TOP/admin/scripts/adautocfg.sh

Step 4:
Verify that the
$INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml
has below entry.

<init-param>
<param-name>main_mode</param-name>
<param-value>recompile</param-value>
</init-param>



No comments :

Post a Comment

HTTP 404 -he requested URL /OA_HTML/AppsLocalLogin.jsp was not found on this server.

No comments
Issue
All the services were up and running but still we were facing the below error while opening the front end application link.

Error:
Not Found
The requested URL /OA_HTML/AppsLocalLogin.jsp was not found on this server.

Solution:

First Fix:-

Regenerate all jar(using adadmin) and compile all jsp files.

Second Fix:-

Go to location
//app//DEV/inst/apps/DEV_rac0001e/logs/ora/10.1.3/opmn/oacore_default_group_3/

In the oacorestd.out file I observed the below issue

12/07/05 23:08:22 Oracle Containers for J2EE 10g (10.1.3.5.0)  initialized
12/07/06 00:43:40 Shutting down...
error: error reading //app//DEV/apps_st/appl/custom_top/12.0.0/java/IDA417.jar; invalid CEN header (bad signature)
1 error
12/07/06 01:09:02 Oracle Containers for J2EE 10g (10.1.3.5.0)  initialized
12/07/06 01:13:08 Shutting down...
error: error reading //app//DEV/apps_st/appl/custom_top/12.0.0/java/IDA417.jar; invalid CEN header (bad signature)
1 error
12/07/06 01:49:43 Oracle Containers for J2EE 10g (10.1.3.5.0)  initialized

There was some issue with the jar and it cannot be loaded. I just move the IDA417.jar to IDA417.jar_bkp file from its location as it was just a custom file.
 
Restart the services.

Now Re-test the issue.


For more info please refer metalink ID[1177264.1]

No comments :

Post a Comment

Starting R12 Apache errors with status 204 after Cloning

1 comment
If we face in issue starting the Apache as below after cloning.
$INST_TOP/admin/scripts/adapcctl.sh start

adapcctl.sh: exiting with status 204

Cause:

The issue persists even after the below script is run in the Target instance, to remove references to the SSO configuration of the Source instance:

txkrun.pl -script=SetSSOReg -removereferences=yes
 
This is  due to residual references to SSO configuration in the <SID_hostname>.xml context file.

The "s_mod_osso_conf_comment" variable enables or disables mod_osso for R12. This variable is updated by the SSO registration utility for R12.

Solution:

First Fix:-
If the instance is SSO enabled the deregister SSO and register back SSO properly.Check the log file of SSO for any issues.

Start the Apache service to re-test the issue.
Second Fix:-
This variable should have a value "#" if the instance is not SSO enabled.

1. Backup the $CONTEXT_FILE.

2. Edit the parameter  "s_mod_osso_conf_comment" in the $CONTEXT_FILE using 

    editContext utility,  or manually using a text editor

3. Set the value for the above parameter to "#"
    <mod_osso_conf_comment oa_var="s_mod_osso_conf_comment"/># 

    </mod_osso_conf_comment>

4. Save the changes and run Autoconfig
    If you are facing issue while running autoconfig.The use $AD_TOP/bin/adconfig utility and 

    provide full path of the context file whihc has been updated.

5. Start the Apache service to re-test the issue


1 comment :

Post a Comment

adopmnctl.sh: exiting with status 206

No comments
If we face issue while starting opmn managed services like

opmnctl startall

adopmnctl.sh: exiting with status 206

Solution:

 Step 1. cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/
 Step 2. rm -rf *
 Step 3. Repeat the above step for oafm. 
              The path will be cd $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/

No comments :

Post a Comment