Wednesday, September 28, 2011

Guest User End Dated in apps

Guest User End Dated

Its been long time I did not blog, I was busy in migration. Last week I came accross "Blank Login Page" (EBS R12) issue in one of the development instance, later I found that the functional team end dated GUEST user thinking that it is not used by anyone.

Guest user has lot of importance in EBS, E-Business Suite uses a guest account to represent a user session that is not yet authenticated, so when the account gets locked then you will see a blank page when you try to login to the instance. I had to fix this issue from backend as I could not login to the instance,

I used this script to check when the guest user was end dated.
>> select USER_NAME, END_DATE from fnd_user where USER_NAME like '%GUEST%' ;

Take backup of FND_USER table and run below statement to remove the end_date.
>> update fnd_user set end_date=null where user_name='GUEST';
>> commit;

I tried to login again, it dint worked, then I validated the guest user password with below statement, this should return "Y" if the guest user password is correct, in my case it returned me "N", so I had to reset the GUEST user password aswell.
>> select fnd_web_sec.validate_login('GUEST','ORACLE') from dual;

Below is the procedure to reset the GUEST user password as per metalink:

1. Reset GUEST password:

SQL> exec fnd_vault.del('FND');SQL> commit;
SQL> select FND_WEB_SEC.CHANGE_GUEST_PASSWORD('ORACLE','') from dual;
SQL> commit;

Note: In Above Sql , FND_WEB_SEC.CHANGE_GUEST_PASSWORD needs two inputs one is the new guest user's password which is "ORACLE" and other is applsys user's password that you need to provide as applicable.

2. Test if Profile Updated or not?

DECLAREstat boolean;
BEGINdbms_output.disable;
dbms_output.enable(100000);
stat := FND_PROFILE.SAVE('GUEST_USER_PWD','GUEST/ORACLE','SITE');
IF stat THEN
dbms_output.put_line( 'Stat = TRUE - profile updated' );
ELSE
dbms_output.put_line( 'Stat = FALSE - profile NOT updated' );
END IF;
end;/

3. Change GUEST user password, FNDCPASS should not be used. It will result in error : "FNDCPASS was not able to decrypt password for user 'GUEST' during applsys"
Use following API:

>>java oracle.apps.fnd.security.AdminAppServer APPS/"APPS Password" UPDATE GUEST_USER_PWD=GUEST/"Guest User Password" DB_HOST="Host_Name" DB_PORT="PortNumber"DB_NAME="SID"

Note: Provide all the parameters as applicable for Guest User password as used in step :1 , and DB related details for DB_HOST, DB_PORT and DB_NAME


4. Check the log of FNDCPASS for any error for GUEST user if there is no error for GUEST user then do the next step


5. Compile JSP
>> cd $FND_TOP/patch/115/bin
>> ojspCompile.pl --compile --flush

6. Set GUEST_USER_PWD password in $FND_SECURE/.dbc to GUEST/ORACLE

7. Correct End_Date of GUEST user & its responsibilities by direct launch of FORMS as explained in Note 552301 1 How To Prevent Users From Accessing Forms Directly In Oracle Applications R12

8. Correct the Roles by Workflow Directory Services User/Role Validation" with Parameters:
Fix Dangling User/Roles=YesAdd Missing User/Role Assignments=Yes

9. Bounce Middle Tier Services

10. Retest the issue. .


Note:- I just shared how I fixed the guest user end_date issue, this may not be the soultion in all the case.

Monday, September 26, 2011

adautocfg.sh managed files (3) web, forms and mwa tier

adautocfg.sh managed files (3) web, forms and mwa tier

1. environment files (4)

$APPL_TOP/APPSORA.env
$APPL_TOP/APPS$CONTEXT_NAME.env
$APPL_TOP/PROD.env
$APPL_TOP/$CONTEXT_NAME.env

2. files used for ad tools, java, and java related environment files (8)

$APPL_TOP/admin/adconfig.txt
$APPL_TOP/admin/adgetlnxver.sh
$APPL_TOP/admin/adjareas.txt
$APPL_TOP/admin/adjborg.txt
$APPL_TOP/admin/adjborg2.txt
$APPL_TOP/admin/adovars.env
$APPL_TOP/admin/PROD_806_BALANCE/adalldefaults.txt
$APPL_TOP/admin/$CONTEXT_NAME/out/adcert.txt

3. other tools for application: WEB ADI, Workflow, XML etc. (15)

$APPL_TOP/bne/11.5.0/conf/webadi.properties
$APPL_TOP/cct/11.5.0/admin/install/$CONTEXT_NAME/cctclean.sh
$APPL_TOP/cct/11.5.0/admin/install/$CONTEXT_NAME/cctclean.sql
$APPL_TOP/fnd/11.5.0/patch/115/import/US/wfautocfg.msg
$APPL_TOP/fnd/11.5.0/resource/appsweb.cfg
$APPL_TOP/fnd/11.5.0/resource/appsweb_$CONTEXT_NAME.cfg
$APPL_TOP/fnd/11.5.0/xml/oamextensions.xml
$APPL_TOP/icx/11.5.0/html/US/ICXINDEX.htm
$APPL_TOP/icx/11.5.0/html/US/ICXINDEX_$CONTEXT_NAME.htm
$APPL_TOP/ieo/11.5.0/admin/install/$CONTEXT_NAME/ieosvicsm.sh
$APPL_TOP/ieo/11.5.0/admin/scripts/$CONTEXT_NAME/ieoenv.sh
$APPL_TOP/ieo/11.5.0/admin/scripts/$CONTEXT_NAME/ieoicsm.sh
$APPL_TOP/ieo/11.5.0/admin/scripts/$CONTEXT_NAME/ieozip.sh
$APPL_TOP/ieo/11.5.0/admin/scripts/$CONTEXT_NAME/ieozipall.sh
$APPL_TOP/ies/11.5.0/admin/install/$CONTEXT_NAME/cooper.sh

4. MWA related files (7)

$APPL_TOP/mwa/11.5.0/bin/mwactl.sh
$APPL_TOP/mwa/11.5.0/secure/device.cfg
$APPL_TOP/mwa/11.5.0/secure/deviceIP.ini
$APPL_TOP/mwa/11.5.0/secure/mwa.cfg
$APPL_TOP/mwa/11.5.0/secure/$CONTEXT_NAME/device.cfg
$APPL_TOP/mwa/11.5.0/secure/$CONTEXT_NAME/deviceIP.ini
$APPL_TOP/mwa/11.5.0/secure/$CONTEXT_NAME/mwa.cfg

5. cloning support files (62)

$COMMON_TOP/admin/install/$CONTEXT_NAME/abmwebprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/abmwebprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/adadmat.pl
$COMMON_TOP/admin/install/$CONTEXT_NAME/adadmrat.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/adatccnv.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adgendbc.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adgenjky.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/admkenv.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/admkliblist.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/admkpltfrm.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/admkxdir.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adsupmult.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adsvalsn.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adsvapc.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adsvfmc.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adsvfms.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adsvfrm.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adsvtcf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/adunzip.pl
$COMMON_TOP/admin/install/$CONTEXT_NAME/adupdbid.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/afadmprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/afadmprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/afcpclean.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/afcpctx.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/afcpgsm.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/afcpgsm.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/afcpnode.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/afcpnode.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/affrmprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/affrmprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/afgcsreg.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/afgcsreg.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/afwebprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/afwebprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/amswebprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/amswebprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/csfwebprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/csfwebprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/ibywebprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/ibywebprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/icxwebprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/icxwebprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/jtfictx.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/jtfirip.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/jtfsvfm.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/mwamscasvc.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/mwamscasvc.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/oksfrmprf.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/oksfrmprf.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/ssodatan.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/ssodatan.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkFrmUTF8.pl
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkFrmUTF8.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkFrmUTF8.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkGenExtSecConf.pl
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkGenFormServletIni.pl
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkGetWebNodes.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkJdkCfg.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkMultinode.sh
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkOprocmgrConf.pl
$COMMON_TOP/admin/install/$CONTEXT_NAME/txkWfClone.sql
$COMMON_TOP/admin/install/$CONTEXT_NAME/wdbsvr.sh

6. maintenance scripts at web, forms, mwa and discoverer tier (16)

$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adalnctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adapcctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adaprstctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adautocfg.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/addisctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adexecsql.pl
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adfmcctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adfmsctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adfrmctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adpreclone.pl
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adstpall.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adstrtal.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/adtcfctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/gsmstart.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/jtffmctl.sh
$COMMON_TOP/admin/scripts/$CONTEXT_NAME/mwactlwrpr.sh

7. HTML related scripts (7)

$COMMON_TOP/html/bin/appsweb.cfg
$COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg
$COMMON_TOP/html/bin/txkcsa_$CONTEXT_NAME.cfg
$COMMON_TOP/html/txkcsa/txkLoadXMLInDB.sh
$COMMON_TOP/html/txkObjectTag.js
$COMMON_TOP/html/US/ICXINDEX.htm
$COMMON_TOP/html/US/ICXINDEX_$CONTEXT_NAME.htm

8. Portal related files (22)

$COMMON_TOP/portal/$CONTEXT_NAME/apccmsvc.html
$COMMON_TOP/portal/$CONTEXT_NAME/aplogon.html
$COMMON_TOP/portal/$CONTEXT_NAME/appcfg.html
$COMMON_TOP/portal/$CONTEXT_NAME/appdet.html
$COMMON_TOP/portal/$CONTEXT_NAME/appdoc.html
$COMMON_TOP/portal/$CONTEXT_NAME/appfso.html
$COMMON_TOP/portal/$CONTEXT_NAME/appgloss.html
$COMMON_TOP/portal/$CONTEXT_NAME/applist.html
$COMMON_TOP/portal/$CONTEXT_NAME/applog.html
$COMMON_TOP/portal/$CONTEXT_NAME/applogh.html
$COMMON_TOP/portal/$CONTEXT_NAME/appnefso.html
$COMMON_TOP/portal/$CONTEXT_NAME/appnetst.html
$COMMON_TOP/portal/$CONTEXT_NAME/appnevis.html
$COMMON_TOP/portal/$CONTEXT_NAME/apptitle.html
$COMMON_TOP/portal/$CONTEXT_NAME/apscript.html
$COMMON_TOP/portal/$CONTEXT_NAME/index.html
$COMMON_TOP/portal/$CONTEXT_NAME/inst_log.html
$COMMON_TOP/portal/$CONTEXT_NAME/logon.html
$COMMON_TOP/portal/$CONTEXT_NAME/machine.html
$COMMON_TOP/portal/$CONTEXT_NAME/nav.html
$COMMON_TOP/portal/$CONTEXT_NAME/robots.txt
$COMMON_TOP/portal/$CONTEXT_NAME/script.html

9. environment files in 8.0.6 Oracle Home (2)

$ORA_TOP/8.0.6/PROD.env
$ORA_TOP/8.0.6/$CONTEXT_NAME.env

10. adlnk806.sh for relink 8.0.6 Oracle Home

$ORA_TOP/8.0.6/bin/adlnk806.sh

11. discoverer related files (26)

$ORA_TOP/8.0.6/discwb4/discwb.sh
$ORA_TOP/8.0.6/discwb4/util/applypreferences.sh
$ORA_TOP/8.0.6/discwb4/util/checkdiscoverer.sh
$ORA_TOP/8.0.6/discwb4/util/registerall.sh
$ORA_TOP/8.0.6/discwb4/util/registercollector.sh
$ORA_TOP/8.0.6/discwb4/util/registerpreference.sh
$ORA_TOP/8.0.6/discwb4/util/registersession.sh
$ORA_TOP/8.0.6/discwb4/util/registersessionwithlog.sh
$ORA_TOP/8.0.6/discwb4/util/runcol.sh
$ORA_TOP/8.0.6/discwb4/util/runpref.sh
$ORA_TOP/8.0.6/discwb4/util/runses.sh
$ORA_TOP/8.0.6/discwb4/util/startall.sh
$ORA_TOP/8.0.6/discwb4/util/startgatekeeper.sh
$ORA_TOP/8.0.6/discwb4/util/startgkconfig.sh
$ORA_TOP/8.0.6/discwb4/util/startlocator.sh
$ORA_TOP/8.0.6/discwb4/util/startoad.sh
$ORA_TOP/8.0.6/discwb4/util/startosagent.sh
$ORA_TOP/8.0.6/discwb4/util/stopall.sh
$ORA_TOP/8.0.6/discwb4/util/stopdisprocess.sh
$ORA_TOP/8.0.6/discwb4/util/stopgatekeeper.sh
$ORA_TOP/8.0.6/discwb4/util/stoplocator.sh
$ORA_TOP/8.0.6/discwb4/util/stopoad.sh
$ORA_TOP/8.0.6/discwb4/util/stoposagent.sh
$ORA_TOP/8.0.6/discwb4/util/unregistercollector.sh
$ORA_TOP/8.0.6/discwb4/util/unregisterpreference.sh
$ORA_TOP/8.0.6/discwb4/util/unregistersession.sh

12. reports and forms related files (4)

$ORA_TOP/8.0.6/reports60/server/CGIcmd.dat
$ORA_TOP/8.0.6/reports60/server/REP60_PROD.ora
$ORA_TOP/8.0.6/tools/web60/html/runform.htm
$ORA_TOP/8.0.6/tools/web60/html/runrep.htm

13. environment files for iAS Oracle Home (2)

$ORA_TOP/iAS/PROD.env
$ORA_TOP/iAS/$CONTEXT_NAME.env

14. configuration files for Apache (38)

$ORA_TOP/iAS/Apache/Apache/bin/apachectl
$ORA_TOP/iAS/Apache/Apache/bin/java.sh
$ORA_TOP/iAS/Apache/Apache/bin/startJserv.sh
$ORA_TOP/iAS/Apache/Apache/bin/stopJserv.sh
$ORA_TOP/iAS/Apache/Apache/cgi-bin/printenv
$ORA_TOP/iAS/Apache/Apache/cgi-bin/test-cgi
$ORA_TOP/iAS/Apache/Apache/conf/apps.conf
$ORA_TOP/iAS/Apache/Apache/conf/custom_apache.conf
$ORA_TOP/iAS/Apache/Apache/conf/httpd.conf
$ORA_TOP/iAS/Apache/Apache/conf/httpd_pls.conf
$ORA_TOP/iAS/Apache/Apache/conf/httpds.conf
$ORA_TOP/iAS/Apache/Apache/conf/imeeting.conf
$ORA_TOP/iAS/Apache/Apache/conf/oprocmgr.conf
$ORA_TOP/iAS/Apache/Apache/conf/oracle_apache.conf
$ORA_TOP/iAS/Apache/Apache/conf/security.conf
$ORA_TOP/iAS/Apache/Apache/conf/trusted.conf
$ORA_TOP/iAS/Apache/Apache/conf/url_fw.conf
$ORA_TOP/iAS/Apache/Apache/htdocs/disco4iv/html/disco4iv.xml
$ORA_TOP/iAS/Apache/Apache/htdocs/discwb4/scripts/htmlvars.js
$ORA_TOP/iAS/Apache/Apache/htdocs/discwb4/scripts/htmlvars_apps.js
$ORA_TOP/iAS/Apache/Jserv/etc/disco4iviewer.properties
$ORA_TOP/iAS/Apache/Jserv/etc/emailcenter.properties
$ORA_TOP/iAS/Apache/Jserv/etc/forms.properties
$ORA_TOP/iAS/Apache/Jserv/etc/formservlet.properties
$ORA_TOP/iAS/Apache/Jserv/etc/jserv.conf
$ORA_TOP/iAS/Apache/Jserv/etc/jserv.properties
$ORA_TOP/iAS/Apache/Jserv/etc/jserv_restrict.properties
$ORA_TOP/iAS/Apache/Jserv/etc/mobile.properties
$ORA_TOP/iAS/Apache/Jserv/etc/ssp_init.txt
$ORA_TOP/iAS/Apache/Jserv/etc/viewer4i.properties
$ORA_TOP/iAS/Apache/Jserv/etc/xmlsvcs.properties
$ORA_TOP/iAS/Apache/Jserv/etc/zone.properties
$ORA_TOP/iAS/Apache/Jserv/etc/zone_restrict.properties
$ORA_TOP/iAS/Apache/mapviewer/conf/mapViewerConfig.xml
$ORA_TOP/iAS/Apache/modplsql/cfg/cache.cfg
$ORA_TOP/iAS/Apache/modplsql/cfg/plsql.conf
$ORA_TOP/iAS/Apache/modplsql/cfg/plsql_pls.conf
$ORA_TOP/iAS/Apache/modplsql/cfg/wdbsvr.app

15. adlinkiAS.sh for relink iAS Oracle Home (1)

$ORA_TOP/iAS/bin/adlnkiAS.sh

16. OEM related file (1)

$ORA_TOP/iAS/oem_webstage/oem.conf

17. SOAP related files (3)

$ORA_TOP/iAS/soap/webapps/soap/WEB-INF/config/soap.properties
$ORA_TOP/iAS/soap/webapps/soap/WEB-INF/config/soapConfig.xml
$ORA_TOP/iAS/soap/webapps/soap/WEB-INF/config/wsConfig.xml

18. listener.ora and tnsnames.ora

$ORA_TOP/8.0.6/network/admin//listener.ora and tnsnames.ora
$ORA_TOP/iAS/network/admin//tnsnames.ora


Above files are created using $AD_TOP/bin/adgentns.pl during adautocfg.sh run with information from the database Net Services Topology Data Model.

19. dbc f iles

$FND_SECURE/prod.dbc

Above file is created using $COMMON_TOP/admin/install/$CONTEXT_NAME/adgendbc.sh during adautocfg.sh run with information from contextfile and database

Friday, September 23, 2011

Too Many Time to Start or Stop Concurrent Managers [ID 726098.1]


Too Many Time to Start or Stop Concurrent Managers [ID 726098.1]

Modified 07-FEB-2011 Type PROBLEM Status MODERATED

In this Document
Symptoms
Cause
Solution


Platforms: 1-914CU;

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Application Object Library - Version: 11.5.10.0 to 11.5.10.2 - Release: 11.5.10 to 11.5.10
Information in this document applies to any platform.
***Checked for relevance on 07-Feb-2011***

Symptoms

Start the concurrent managers employs too much time (over 15 minutes).
After this time, when the concurrent managers are started, all works fine.
Same time to stop the concurrent managers.

This is a single-node e-business suite 11.5.10.2 on 2 cluster nodes.

Cause

In the FNDSMxxxxxx.mgr log file, the following error occurs :

The call to function PingProcess in cartridge CMDCART has failed


In the FNDCPGSC889911.txt log file you found the following :

Jul 31, 2008 5:46:37 PM CEST]:1214927197327:Thread[main,5,main]:0:-1:sid:x.x.x.x:-1: 1:ERROR:[SVC-GSM-WFMLRSVC-889911 :
oracle.apps.fnd.cp.gsc.SvcComponentContainer.startBusinessEventListener()]:BES system
could not establish connection to the control queue after 180 seconds.


Solution

In the start/stop shell script ($OAD_TOP/comn/admin/scripts/_), there was references to the real hostname.

Replace the reference of the real hostname with the logical hostname and concurrent managers starts up in 3 minutes.


Show Related Information Related


Products
  • Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Library
Keywords
CCMGR; CMDCART; STOP CONCURRENT MANAGER; THREADS; FAIL; CARTRIDGE; START CONCURRENT MANAGER

Back to topBack to top

Concurrent Processing - ORA-20100: Error: FND_FILE Failure, Unable to Create File


Concurrent Processing - ORA-20100: Error: FND_FILE Failure, Unable to Create File [ID 749491.1]

Modified 14-APR-2011 Type PROBLEM Status ARCHIVED

In this Document
Symptoms
Cause
Solution


Applies to:

Oracle Application Object Library - Version: 12.0.4 and later [Release: 12 and later ]
Oracle Concurrent Processing - Version: 12.0.0 to 12.0.6 [Release: 12 to 12]
Information in this document applies to any platform.
Checked for relevance on 02-Mar-2011

Symptoms

On Real Application Cluster (RAC) environment, when attempting to run concurrent requests or 'exec FND_FILE.PUT(FND_FILE.LOG, 'TESTING');' from the command line, the following error occurs:

ORA-20100: Error: FND_FILE failure. Unable to create file, o0040178.tmp in the
directory, /usr/tmp.
You will find more information in the request log.
ORA-06512: at "APPS.FND_FILE", line 417
ORA-06512: at "APPS.FND_FILE", line 456
ORA-06512: at line 1


Cause

The issue is caused by the parameter utl_file_dir in the pfile as being taken as a complete string. The utl_file_dir is currently defined in the following manner:
utl_file_dir=/usr/tmp,/oraapp/inst_finp/apps/finp_u914403/appltmp,/oraapp/inst_finp/apps/finp_u914404/appltmp
Modification to the pfile resolved the issue.

Solution

1. On the Database created pfile from spfile.
2. Modified pfile with the entries, utl_file_dir='/usr/tmp','/oraapp/inst_finp/apps/finp_u914403/appltmp','/oraapp/inst_finp/apps/finp_u914404/applt
mp' .
3. Started the DB only on 1 node.
4. Tested the FND_FILE procedure, it completed successfully.
5. Created the spfile from the pfile.
6. Started up all the services (using the spfile).
7. Submitted the concurrent request and it completes successfully




Show Related Information Related


Products
  • Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Library
  • Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Concurrent Processing
Errors
ORA-20100; ORA-6512; 620100 ERROR; 20100 ERROR

Back to topBack to top

Wednesday, September 21, 2011

DBA JOKE : --

DBA JOKE : --

PEOPLE WHO DOES'NT KNOW HOW TO UTILIZE THE TEAM WHEN IT WAS STRONG ....
ARE NOW TALKING ABOUT BUDILING A STRONG TEAM :)

KYA WOH STRONG TEAM BUILD KARR PAAYENGEY ?

AGAR AAPKA JAWAB HAAN HAI THO "STRONG TEAM SPACE HAAN" TYPE KARKE ISS THREAD MEIN COMMENT KIJIYE.

AGAR AAPKA JAWAB NAA HAI THO "STRONG TEAM SPACE NAA" TYPE KARKE ISS THREAD MEIN COMMENT KIJIYE.

JAAGO DELIVERY LEADS JAAGO ......

KARLO INSTANCE MUTTI MEIN PATCHING KARO CHUTTI MEIN :)

Monday, September 19, 2011

Error: "EPMCFG-10399: EPM System Configurator has detected use of a non-UTF-8 Oracle database; UTF-8 encoding needs to be used."


Error: "EPMCFG-10399: EPM System Configurator has detected use of a non-UTF-8 Oracle database; UTF-8 encoding needs to be used." [ID 1318128.1]

Modified 05-MAY-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution


Applies to:

Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.

Goal

When running the Oracle Hyperion Enterprise Performance Management (EPM) System Configurator 11.1.2.1 to configure the Database (using an Oracle repository) the installing user sees the following error:
"EPMCFG-10399: EPM System Configurator has detected use of a non-UTF-8 Oracle database; UTF-8 encoding needs to be used."


Solution

Per the Oracle Database Creation Considerations:

For the best compatibility with non-ASCII character sets, the database must be created using Unicode Transformation Format UTF-8 encoding (character set). Use of UTF-8 is required if you need any characters beyond ASCII. Oracle supports the following character sets with UTF-8 encoding:

- AL32UTF8 (preferred/standard UTF-8 encoding)
- UTF8 (backward compatible/non-standard encoding for Oracle [only includes the base plane of Unicode])
- UTFE (UTF-8 encoding for EBCDIC platforms)

Note: The UTF-8 character set must be applied to the client and to the Oracle database.

Check with the DBA if the repository you are about to use for the Oracle EPM system meets this requirement or query via SQLPlus or a similar tool using the following SQL:

SELECT * FROM NLS_DATABASE_PARAMETERS

Recent versions of Microsoft SQL Server automatically communicate with Oracle Hyperion EPM 11 in UTF-8. IBM DB2 must also be configured for UTF-8.

Thursday, September 15, 2011

Master Note of Linux OS Requirements for Database Server [ID 851598.1]


Master Note of Linux OS Requirements for Database Server [ID 851598.1]

Modified 01-JUL-2011 Type REFERENCE Status PUBLISHED

In this Document
Purpose
Scope
Master Note of Linux OS Requirements for Database Server
Red Hat Enterprise Linux (RHEL)
SuSE Linux Enterprise Server (SLES)
Oracle Enterprise Linux (OEL)
Using My Oracle Support Effectively
Generic Links
Community Discussions
References


Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.2.0.1 - Release: 9.2 to 11.2
Oracle Server - Standard Edition - Version: 9.2.0.1 to 11.2.0.1 [Release: 9.2 to 11.2]
Linux x86
IBM: Linux on System z
Generic Linux
IBM: Linux on POWER Systems
Linux x86-64
Linux Itanium

Purpose

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support articles with respect to Linux OS Requirements for Oracle Database Software Installation.

The vast majority of software installation and relinking problems on Linux are caused by missing OS requirements.

If you are encountering a software installation or relinking problem, it is vital that you ensure your OS meets all of the minimum requirements documented in the appropriate article below before creating a new SR.

Scope

Only Linux articles are referenced in this article. For an "all-in-one" article that covers OS requirements for most major OS platforms, please refer to...

Document 169706.1 Oracle Database ... Installation and Configuration Requirements Quick Reference

Where a My Oracle Support article for a given version/platform is "Not available", you should refer to the Installation Guide and the article referenced above.

Master Note of Linux OS Requirements for Database Server

Red Hat Enterprise Linux (RHEL)


Document 376183.1 Defining a "default RPMs" installation of the RHEL OS

Quick Links for RHEL

RHEL5: x86 x86_64 Itanium zLinux Power
RHEL4: x86 x86_64 Itanium zLinux Power
RHEL3: x86 x86_64 Itanium zLinux Power



RHEL5 x86:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 419646.1 Requirements For Installing Oracle 10gR2 On RHEL 5 (x86)
11.1.0 - Document 438765.1 Requirements for Installing Oracle 11gR1 32bit RDBMS on RHEL 5
11.2.0 - Document 880936.1 Requirements for Installing Oracle 11gR2 RDBMS on RHEL (and OEL) 5 on 32-bit x86


RHEL5 x86-64:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 421308.1 Requirements For Installing Oracle10gR2 On RHEL 5 (x86_64)
11.1.0 - Document 438766.1 Requirements for Installing Oracle 11gR1 RDBMS on RHEL 5 on AMD64/EM64T
11.2.0 - Document 880989.1 Requirements for Installing Oracle 11gR2 RDBMS on RHEL (and OEL) 5 on AMD64/EM64T>


RHEL5 Itanium:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 748378.1 Requirements for Installing Oracle 10gR2 RDBMS on RHEL 5 on Linux Itanium (ia64)


RHEL5 zLinux:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 741646.1 Requirements for Installing Oracle 10gR2 RDBMS on RHEL 5 on zLinux (s390x)


RHEL5 Power:


10.2.0 - Document 341507.1 Oracle Database Server on Linux on IBM POWER


RHEL4 x86:


9.2.0 - Document 303859.1 Requirements for Installing Oracle 9iR2 on RHEL 4
10.1.0 - Document 392940.1 Requirements for Installing Oracle 10.1.0.x RDBMS on RHEL 4 x86 platform
10.2.0 - Document 343431.1 Requirements for Installing Oracle 10gR2 RDBMS on RHEL 4 x86 platform
11.1.0 - Document 430653.1 Requirements for Installing Oracle 11gR1 32-bit on RHEL 4
11.2.0 - Document 880211.1 Requirements for Installing Oracle 11gR2 RDBMS on RHEL (and OEL) 4 x86


RHEL4 x86-64:


9.2.0 - Document 353529.1 Requirements for Installing Oracle 9iR2 64-bit on RHEL 4 x86-64 (AMD64/EM64T)
10.1.0 - Document 390900.1 Requirements for Installing Oracle 10g (10.1.0.x) RDBMS on RHEL 4 on AMD64/EM64T (Linux x86-64)
10.2.0 - Document 339510.1 Requirements for Installing Oracle 10gR2 RDBMS on RHEL 4 on AMD64/EM64T
11.1.0 - Document 437123.1 Requirements for Installing Oracle 11gR1 RDBMS on RHEL 4 on AMD64/EM64T
11.2.0 - Document 880942.1 Requirements for Installing Oracle 11gR2 RDBMS on RHEL (and OEL) 4 on AMD64/EM64T


RHEL4 Itanium:


9.2.0 - Not available
10.1.0 - Not available
10.2.0 - Not available


RHEL4 zLinux:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 420382.1 Requirements for Installing Oracle 10gR2 RDBMS on RHEL 4 on zLinux (s390x)


RHEL4 Power:


10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 341507.1 Oracle Database Server on Linux on IBM POWER


RHEL3 x86:


9.2.0 - Document 252217.1 Requirements for Installing Oracle 9iR2 32-bit on RHEL 3
10.1.0 - Document 394360.1 Requirements for Installing Oracle 10g 32-bit on RHEL 3
10.2.0 - Not available
11.1.0 - Not certified, not supported, not planned.
11.2.0 - Not certified, not supported, not planned.


RHEL3 x86-64:


9.2.0 - Document 308588.1 Requirements for Installing Oracle 9iR2 x86_64 on RHEL 3
10.1.0 - Document 351679.1 Requirements for RPM Arch. for 10g x86_64 on RHEL 3
10.2.0 - Document 353735.1 Requirements for RPM Arch. for 10gR2 x86_64 on RHEL 3
11.1.0 - Not certified, not supported, not planned.
11.2.0 - Not certified, not supported, not planned.


RHEL3 Itanium:


9.2.0 - Not available
10.1.0 - Not available
10.2.0 - Not available
11.1.0 - Not certified, not supported, not planned.
11.2.0 - Not certified, not supported, not planned.


RHEL3 zLinux:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Not certified, not supported, not planned.
11.1.0 - Not certified, not supported, not planned.
11.2.0 - Not certified, not supported, not planned.


RHEL3 Power:


10.2.0 - Not certified, not supported, not planned.
11.1.0 - Not certified, not supported, not planned.
11.2.0 - Not certified, not supported, not planned.


SuSE Linux Enterprise Server (SLES)


Document 386391.1 Defining a "default RPMs" installation of the SLES OS

Quick Links for SLES

SLES11: x86 x86_64
SLES10: x86 x86_64 zLinux Power
SLES 9: x86 x86_64 zLinux Power



SLES11 x86:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
11.1.0 - Document 849583.1 Requirements for Installing Oracle 11gR1 32-bit (x86) on SLES 11
11.2.0 - Document 881025.1 Requirements for Installing Oracle 11gR2 32-bit (x86) on SLES 11


SLES11 x86_64:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 956194.1 Requirements for Installing Oracle 10gR2 64-bit (AMD64/EM64T) on SLES 11
11.1.0 - Document 1081555.1 Requirements for Installing Oracle 11gR1 64-bit (AMD64/EM64T) on SLES 11
11.2.0 - Document 881044.1 Requirements for Installing Oracle 11gR2 64-bit (AMD64/EM64T) on SLES 11


SLES10 x86:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 387137.1 Requirements for Installing Oracle 10gR2 32-bit (x86) on SLES 10
11.1.0 - Document 452818.1 Requirements for Installing Oracle 11gR1 32-bit on SLES 10
11.2.0 - Document 763386.1 Requirements for Installing Oracle 11gR2 32-bit on SLES 10 (x86)


SLES10 x86-64:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Document 373681.1 Requirements for Installing Oracle 10gR2 64-bit (AMD64/EM64T) on SLES 10
11.1.0 - Document 457143.1 Requirements for Installing Oracle 11gR1 64-bit (AMD64/EM64T) on SLES 10
11.2.0 - Document 884435.1 Requirements for Installing Oracle 11gR2 64-bit (AMD64/EM64T) on SLES 10


SLES10 s390x (zLinux):


9.2.0 - Not available
10.1.0 - Not available
10.2.0 - Document 1082253.1 Requirements for Installing Oracle 10gR2 RDBMS on SUSE SLES 10 on zLinux (s390x)
11.1.0 - Not certified, not supported, not planned.


SLES10 Power:


10.2.0 - Document 341507.1 Oracle Database Server on Linux on IBM POWER


SLES9 x86:


9.2.0 - Document 427976.1 Requirements for Installing Oracle 9iR2 32-bit on SLES 9
10.1.0 - Not available
10.2.0 - Document 400429.1 Requirements for Installing Oracle 10gR2 32-bit on SLES 9
11.1.0 - Not certified, not supported, not planned.


SLES9 x86-64:


9.2.0 - Document 361169.1 Requirements for Installing Oracle 9iR2 64-bit on SuSE SLES 9 x86_64 (AMD64/EM64T)
10.1.0 - Not available
10.2.0 - Document 365607.1 Requirements for Installing Oracle 10gR2 RDBMS on SLES 9 on AMD/EM64T
11.1.0 - Not certified, not supported, not planned.


SLES9 s390x (zLinux):


9.2.0 - Document 270577.1 Installing Oracle 9i on IBM z/Series - SLES8/9
10.1.0 - Not available
10.2.0 - Document 431443.1 Requirements for Installing Oracle 10gR2 RDBMS on SLES 9 on zLinux (s390x)
11.1.0 - Not certified, not supported, not planned.


SLES9 Power:


10.2.0 - Document 341507.1 Oracle Database Server on Linux on IBM POWER


Oracle Enterprise Linux (OEL)


Document 401167.1 Defining a "default RPMs" installation of the Oracle EL OS

Quick Links for OEL

OEL5: x86 x86_64
OEL4: x86 x86_64



OEL5 x86:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Identical to RHEL5 x86. See "RHEL5 x86:" section above.
11.1.0 - Identical to RHEL5 x86. See "RHEL5 x86:" section above.
11.2.0 - Identical to RHEL5 x86. See "RHEL5 x86:" section above.


OEL5 x86-64:


9.2.0 - Not certified, not supported, not planned.
10.1.0 - Not certified, not supported, not planned.
10.2.0 - Identical to RHEL5 x86-64. See "RHEL5 x86-64:" section above.
11.1.0 - Identical to RHEL5 x86-64. See "RHEL5 x86-64:" section above.
11.2.0 - Identical to RHEL5 x86_64. See "RHEL5 x86_64:" section above.


OEL4 x86:


9.2.0 - Identical to RHEL4 x86. See "RHEL4 x86:" section above.
10.1.0 - Identical to RHEL4 x86. See "RHEL4 x86:" section above.
10.2.0 - Identical to RHEL4 x86. See "RHEL4 x86:" section above.
11.1.0 - Identical to RHEL4 x86. See "RHEL4 x86:" section above.
11.2.0 - Identical to RHEL4 x86. See "RHEL4 x86:" section above.


OEL4 x86-64:


9.2.0 - Identical to RHEL4 x86-64. See "RHEL4 x86-64:" section above.
10.1.0 - Document 436800.1 Requirements for Installing Oracle 10g RDBMS on OEL 4 on AMD64/EM64T
10.2.0 - Document 418890.1 Requirements for Installing Oracle 10gR2 RDBMS on OEL 4 update 4 on AMD64/EM64T
- Document 435900.1 Requirements for Installing Oracle 10gR2 RDBMS on OEL 4 update 5 on AMD64/EM64T
11.1.0 - Identical to RHEL4 x86-64. See "RHEL4 x86-64:" section above.
11.2.0 - Identical to RHEL4 x86_64. See "RHEL4 x86_64:" section above.



Using My Oracle Support Effectively

Document 374370.1 New Customers Start Here
Document 747242.5 My Oracle Support Configuration Management FAQ
Document 868955.1 My Oracle Support Health Checks Catalog
Document 166650.1 Working Effectively With Global Customer Support
Document 199389.1 Escalating Service Requests with Oracle Support Services


Generic Links

Document 854428.1 Patch Set Updates for Oracle Products
Document 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution
Document 881382.1 Critical Patch Update October 2009 Patch Availability Document for Oracle Products
Document 967472.1 Critical Patch Update January 2010 Patch Availability Document for Oracle Products
Document 1060989.1 Critical Patch Update April 2010 Patch Availability Document for Oracle Products
Document 756671.1 Oracle Recommended Patches -- Oracle Database
Document 268895.1 Oracle Database Server Patchset Information, Versions: 8.1. 7 to 11.2.0
Document 161549.1 Oracle Database Server and Networking Patches for Microsoft Platforms

Community Discussions

Still have questions? Use the communities window below to discuss this subject with your peers.

NOTE: The communities window below is the live community, not a screenshot!

For Database Install Linux/Unix Community, click here to open in main browser window.
For Database Install Windows Community, click here to open in main browser window.

References

NOTE:169706.1 - Oracle Database on Unix AIX,HP-UX,Linux,Mac OS X,Solaris,Tru64 Unix Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2)
NOTE:841292.1 - Linux Threads: Why some Oracle RDBMS Releases do not work on some Linux Releases?

Show Related Information Related


Products
  • Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Standard Edition
  • Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Keywords
INSTALLATION; LINUX; ORACLE DATABASE; PREREQS; RHEL; RPM; SUSE; ZLINUX

Back to topBack to top

How to Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD)

How to Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) [ID 437260.1]

Modified 08-MAY-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
Using the FNDCPASS Utility:
Verify the new password.
Examples:
Using the AFPASSWD Utility as of R12.1.2:
Diagnostics & Utilities Community:
Troubleshooting FNDCPASS
References


Applies to:

Oracle Application Object Library - Version: 11.5.10.2 and later [Release: 11.5.10 and later ]
Information in this document applies to any platform.
Checked for relevance 23-APR-2011

Goal

  • The goal of this document is to help understand the process of changing passwords in Oracle Applications. As the Applications directory structure has changed a little, the files that need to be updated have also changed, although the FNDCPASS commands to change/reset the passwords remained pretty much the same.

  • For R12.1.2, an enhanced version of FNDCPASS is available using AFPASSWD noted at the bottom of this document.

Solution

Since changing passwords frequently helps ensure database security, Oracle Applications provides a command line utility, FNDCPASS, to change/reset Oracle Applications schema passwords. This utility changes the password registered in Oracle Applications tables, changes the schema password in the database and can also change user passwords.

Note: One cannot change a schema name, such as APPLSYS or GL, after a product is installed, with FNDCPASS.
Ensure that the entire Oracle Applications system has been shut down before changing any schema passwords.
All users should log out and the Applications system should be down before running this utility.
If Oracle Applications user passwords are being changed then the relevant users should not be logged in.
Before changing any passwords, you should make a backup of the tables FND_USER and FND_ORACLE_USERID.


Note: SOURCE the environment FIRST. Ex:

1. Log into the Operating system level by way of the applmgr user.
2. Run the environment script APPSORA.env:
a. cd $APPL_TOP
b. Run APPSORA.env.
c. The above should also run _.env, but can verify by running it.
d. cd admin.
e. Run adovars.env.

Using the FNDCPASS Utility:

FNDCPASS / 0 Y \

/

Please set the depending on your needs:

Note:
The SYSTEM token is used when changing the APPLSYS password.
The ORACLE token is used when changing a SINGLE Applications schema password.
The ALLORACLE token is used when changing ALL Applications schema passwords.
The USER token is used when changing an Applications USER password.

Note: Passwords for APPLSYS and the APPS schemas -- including the MRC schema -- must be the same. If you change the password for one, FNDCPASS automatically changes the others. When changing APPS (or APPLSYS) and APPLSYSPUB passwords, do not restart the system until the entire password change process has been completed.

Verify the new password.

If you changed the password for APPS (and APPLSYS), restart all concurrent managers, then log on to Oracle Applications to test the new password.


Examples:

A). To change the APPS and APPLSYS schema password:

Use the following command to change passwords for schema that are used by shared components of Oracle Applications.

FNDCPASS  0 Y  SYSTEM  

FNDCPASS uses the following arguments when changing the APPLSYS password. When specifying the SYSTEM token, FNDCPASS expects the next arguments to be the APPLSYS username and the new password.

  • logon The Oracle username/password.
  • system/password The username and password for the SYSTEM DBA account.
  • username The APPLSYS username. For example, 'applsys'.
  • new_password The new password.

This command does the following:

  1. Validates APPLSYS.
  2. Re-registers password in Oracle Applications.
  3. Changes the APPLSYS and all APPS passwords (for multi-APPS schema installations) to the same password.
    Because everything with a Privilege Level [set to any of ('E', 'U', 'D')] in the FND_ORACLE_USERID table must always have the same password, FNDCPASS updates these passwords as well as APPLSYS's password.
    For example, the APPS password will be updated when the APPLSYS password is changed.
  4. ALTER USER is executed to change the ORACLE password for the above ORACLE users.

For instance, the following command changes the APPLSYS password to 'WELCOME'.

FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME


B). To change an Oracle Applications schema password (other than APPS/APPLSYS):

Use this command to change the password of a schema provided by an individual product in Oracle Applications.

FNDCPASS  0 Y  ORACLE  

Use the above command with the following arguments. When specifying the ORACLE token, FNDCPASS expects the next arguments to be an ORACLE username and the new password.

  • logon The Oracle username/password.
  • system/password The username and password for the SYSTEM DBA account.
  • username The Oracle username. For example, 'GL'.
  • new_password The new password.

For example, the following command changes the GL user password to 'GL1'.

FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1


C). To change all ORACLE schema passwords:

Use this command to change the passwords of all schemas provided by Oracle Applications products.

FNDCPASS  0 Y  ALLORACLE 

Use the above command with the following arguments. When specifying the ALLORACLE token, FNDCPASS expects the next argument to be the new password.

  • logon The Oracle username/password.
  • system/password The username and password for the SYSTEM DBA account.
  • new_password The new password.

For example, the following command changes all ORACLE schema passwords to "WELCOME":

FNDCPASS apps/apps 0 Y system/manager ALLORACLE WELCOME 


For additional information on the use of ALLORACLE, please reference NOTE 189367.1 - Best Practices for Securing the E-Business Suite


D). To change an Oracle Applications user's password:

Use this command to change an individual Oracle Applications user's password.

FNDCPASS  0 Y  USER   

Use the above command with the following arguments. When specifying the USER token, FNDCPASS expects the next arguments to be an Oracle Applications username and the new password.

  • logon The Oracle username/password.
  • system/password The username and password for the System DBA account.
  • username The Oracle Applications username. For example, 'VISION'.
  • new_password The new password.

For example, if you were changing the password for the user VISION to 'WELCOME', you would use the following command:

FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME 



Using the AFPASSWD Utility as of R12.1.2:


For Applications release 12.1.2, please reference page 11-8 of the 'Oracle E-Business Suite System Administrator's Guide - Configuration' for use of the AFPASSWD utility. Document 457166.1 must be used for migration from FNDCPASS.

NOTE:
AFPASSWD only prompts for passwords required for the current operation,
allowing separation of duties between applications administrators and database administrators.
This also improves interoperability with Oracle Database Vault.
In contrast, the FNDCPASS utility currently requires specification of the APPS and the
SYSTEM usernames and corresponding passwords, preventing separation of duties
between applications administrators and database administrators.

When changing a password with AFPASSWD, the user is prompted to enter the new password twice to confirm.

AFPASSWD can be run from the database tier as well as the application tier.
In contrast, FNDCPASS can only be run from the application tier.