Start with R12 | Oracle Database | Password

How to Start / Stop services in Oracle Applications R12 ( Application / Database Tier) How to Start/Stop services in Oracle

Applications R12. These steps are from Online Oracle Apps DBA (11i /R12) traininghere (This is interactive online course over weekend with hands on exercises on installation, patching, cloning during weekdays) Assumptions Application Tier O.S. User : avisr12 (usually applmgr) Database Tier O.S. User : ovisr12 (usually oracle) R12 install base : /oracle/apps/r12/visr12 Database SID : visr12 Database Version : 11.1.0 Hostname : focusthreadr12 Operating System : Unix/Linux Apps Schema Password : apps (apps is default password) . Start-Up/Shutdown order If you are starting services then first start Database Tier services and then Application Tier Services. If you are shutting down services then first stop Application Tier services andthen Database Tier Services. 1. Startup 1.1 Start Database Tier 1.1.1 Login as database tier user (ovisr12) 1.1.2 Set environment variable by

running $SID_hostname.envfrom $INSTALL_BASE/db/tech_st/11.1.0 —- cd /oracle/apps/r12/visr12/db/tech_st/11.1.0 —- . visr12_focusthreadr12.com (note: dot in front) 1.1.3 Start database —- sqlplus ―/as sysdba‖ —- SQL> startup 1.1.4 Start Database Listener (lsnrctl start $SID) —- lsnrctl start visr12 .

. 1.2 Start Application Tier 1.2.1 Login as application tier user (avisr12)

1.2.2 Set environment variable by running $SID_hostname.envfrom $INSTALL_BASE/apps/apps_st/appl —- cd /oracle/apps/r12/visr12/apps/apps_st/appl —- . visr12_focusthreadr12.com (note: dot in front) 1.2.3 Start Application Tier (adstrtal.sh apps/$apps_password) —- cd $ADMIN_SCRIPTS_HOME —- ./adstrtal.sh apps/apps

. . 2. Shutdown Services 2.1 Shutdown Application Tier 2.1.1 Login as application tier user (avisr12) 2.1.2 Set environment variable by running $SID_hostname.env from $INSTALL_BASE/apps/apps_st/appl —- cd /oracle/apps/r12/visr12/apps/apps_st/appl —- . visr12_focusthreadr12.com (note: dot in front) 2.1.3 Stop Application Tier (adstpall.sh apps/$apps_password)

—- cd $ADMIN_SCRIPTS_HOME —- ./adstpall.sh apps/apps . 2.2 Shutdown Database Tier 2.2.1 Login as database tier user (ovisr12) 2.2.2 Set environment variable by running $SID_hostname.env from $INSTALL_BASE/db/tech_st/11.1.0 —- cd /oracle/apps/r12/visr12/db/tech_st/11.1.0 —- . visr12_focusthreadr12.com (note: dot in front) 2.2.3 Stop database —- sqlplus ―/as sysdba‖ —- SQL> shutdown immediate 2.2.4 Stop Database Listener (lsnrctl start $SID) —- lsnrctl stop visr12 Start-up Shutdown Scripts in Oracle Apps R12 Order of Startup Shutdown ————————————– As in Oracle Apps 11i order for startup is A) Start Database Tier Services –Start Database Listener –Start Database Then B) Start Application/Middle Tier Services – adstrtal.sh Order for shutdown in Oracle Apps R12 is A) Stop Application/Middle Tier Services – adstpall.sh Then

sh .xml) .0/appsutil/scripts/$CO NTEXT_NAME. Scripts are located inDatabase_Install_Dir/db/tech_st/10.For Database Listener Use script addlnctl.2.sh or alternatively you can use lsnrctl startstop listener_name (For Database Listener) sqlplus ―/as sysdba‖ SQL> startup shutdown immediate Middle/Application Tier Scripts in R12 ————————————————Scripts for Application Tier services in R12 are located in ―Install_base/inst/apps/$CONTEXT_NAME/admin/scripts“ where CONTEXT_NAME is of format SID_HOSTNAME i) adstrtal.sh Master script to start all components/services of middle tier or application tier. This script will use Service Control API to start all services which are enabled after checking them in context file (SID_HOSTNAME.xml or CONTEXT_NAME.B) Stop Database Tier Services –Stop Database –Stop Database Listener Database Tier Scripts in R12 ————————————– For Database tier you need to start database and database listener.For Database Use script addbctl.

This listener will file will be in 10. iii) adalnctl.sh Script to start / stop Forms OC4J from 10. In 11i web server oracle home was 1.sh Script to start / stop apps listener (FNDFS and FNDFS).sh Master script to stop all components/services of middle tier or application tier. (In 11i this script directly used to call apachectl executable but now calls opmnctl which in turn calls apachectl.1.1. This script will also useopmnctl to start/stop Forms OC4J like opmnctl stopproc type=oc4j instancename=forms vii) adformsrvctl.2 but in R12 its 10.1.2) iv) adapcctl.ora file will be in $INST_TOP/apps/$CONTEXT_NAME/ora/10.sh Script to start / stop concurrent manager. Similar to one in 11i.0.1.sh Script to start/stop Web Server or Oracle HTTP Server.sh This script is used only if you wish to start forms in socket mode. Forms & Reports Home) listener.2.e.2.e. .1. This script uses opmn (Oracle Process Manager and Notification Server) with syntax similar to opmnctl[startstop]proc ohs likeopmnctl stopproc ohs. from 8.ii) adstpall.3 Oracle_Home.3) v) adcmctl. (This script in turn calls startmgr.2/network/admin directory (Mostly similar to one in 11i with only change in ORACLE_HOME i.0.2 ORACLE_HOME (i.sh ) vi) adformsctl.6 to 10.

If started this will start frmsrv executable from 10.sh This script will start/stop oacore OC4J in 10.3 Oracle_Home like web server or various oc4j instances.1. Log File Location for Startup Shutdown Services in R12 ———————————————————————Log files for startup/shutdown scripts for application/mid tier in R12 are in$INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/l .sh This script will start/stop opmn service in 10.sh This script will be used to start/stop one to one fulfilment server.1.1.3 Oracle_Home. This scripts will also useopmnctl (similar to adapcctl & adformsctl) to start oacore instance of OC4J like opmnctl startproc type=oc4j instancename=oacore ix) adoafmctl.2 Oracle_Home in Apps R12 viii) adoacorectl. This scripts will also useopmnctl (similar to above) to start oacore instance of OC4J like opmnctl startproc type=oc4j instancename=oafm x) adopmnctl.3 Oracle_Home. xi) jtffmctl.sh This script will start/stop oafm OC4J in 10.Default forms connect method in R12 is servlet. opmn will control all services in 10.1. If any services are stopped abnormally opmn will/should start them automatically. xii) mwactl.3 Oracle_Home.1.sh To start / stop mwa telnet server where mwa is mobile application.

Cloning.adopmnctl.txt. DB & Apps Listener and various components in Apps R12/12i: A. adoacorectl.txt. jtffmctl. adoafmctl. Startup/Shutdown Log files for Application Tier in R12 Instance Top is new TOP added in R12 (to read more click here) –Startup/Shutdown error message text files like adapcctl.txt… $INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log . adformsctl. Startup/Shutdown) Log files are useful in troubleshooting issues in Oracle Applications. Here is the list of Log file location in Oracle Applications for Startup/Shutdown. txt.txt ) Where AD is for Application DBA DB is for database DLN is database listener CTL is control Isn’t this easy to Oracle R12/12i log file (Patch. adcmctl.txt. adcmctl. adapcctl. Patching.txt.log.txt. adstrtal. Clone.og (adalnctl.txt.txt.

1.1.1.3/opmn/ (OC4J~….log) ii) Application Tier – $INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM.2.log Apps Tier – . 10.3 forms/reports/web) $INST_TOP/apps/$CONTEXT_NAME/logs/ora/ (10.2 & 10. oa*.–Startup/Shutdown error message related to tech stack (10.1.log) Clone log files in target instance Database Tier $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_<ti me>. Log files related to cloning in R12 Preclone log files in source instance i) Database Tier – /$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_M MDDHHMM.1.3) $INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.3/Apache/error _log[timestamp] $INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/ne twork/ (listener log) $INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log (CM log files) B.log)$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1. opmn.

.2) Patch $ORACLE_HOME/.1) During clone step on DB Tier it prompts for ―Target System base directory for source homes‖ and during this you have to give like /base_install_dir like .patch_storage iii) Web Server (Apache) patch $IAS_ORACLE_HOME/..patch_storage D.2. Autoconfig related log files in R12 i) Database Tier Autoconfig log : $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/ad config.$INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_<ti me>.log .log —– If your clone on DB Tier fails while running txkConfigDBOcm.patch_storage iv) Database Tier opatch log – $ORACLE_HOME/./r12 and not oracle home like ./r12/db/tech_st_10../. Patching related log files in R12 i) Application Tier adpatch log .pl (Check metalink note – 415020.$APPL_TOP/admin/$SID/log/ ii) Developer (Developer/Forms & Reports 10..1./.log $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/Ne tServiceHandler.0 —– C.

logRDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ohclone.logRDB MS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/make_<MMDDH HMM>.l og RDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDatabase_ <MMDDHHMM>.logRDB MS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adcrdb_<SID>.log RDBMS .logRDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM> /adconfig.logRDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/installdbf.xml E. logRDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTechSta ck_<MMDDHHMM>. R12 Installation Logs Database Tier Installation RDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>.ii) Application Tier Autoconfig log $INST_TOP/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/ad config.log Autoconfig context file location in R12 $INST_TOP/apps/$CONTEXT_NAME/appl/admin/$CONTEXT_NAM E.

log $INST_TOP/admin/log/ApplyAppsTechStack.log $Global Inventory/logs/oraInstall<timestamp>.log $Global Inventory/logs/silentInstall<timestamp>.log $APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppltop_<MMDD HHMM>.log $APPL_TOP/admin/$CONTEXT_NAME/log/<MMDDHHMM>/NetSe rviceHandler.log $APPL_TOP/admin/$CONTEXT_NAME/log/installAppl.$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM> /NetServiceHandler.2/install/make_<MMDDHHMM>. Other log files in R12 1) Database Tier 1.1.3/install/make_<MMDDHHMM>.log $APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppsTechStack.log $INST_TOP/logs/ora/10.1) Relink Log files : .log $APPL_TOP/admin/$CONTEXT_NAME/log/<MMDDHHMM>/adcon fig.log $INST_TOP/admin/log/ohclone.log Application Tier Installation $INST_TOP/logs/<MMDDHHMM>.log F.lo g $INST_TOP/logs/ora/10.log Inventory Registration: $Global Inventory/logs/cloneActions<timestamp>.1.

1.log 1.log 1.3 $INST_TOP/logs/appl/conc/log $INST_TOP/logs/appl/admin/log .1.4) OUI Logs : OUI Inventory Logs : $ORACLE_HOME/admin/oui/$CONTEXT_NAME/oraInventory/logs 2) Application Tier $ORACLE_HOME/j2ee/DevSuite/log $ORACLE_HOME/opmn/logs $ORACLE_HOME/network/logs Tech Stack Patch 10.1.2 $INST_TOP/logs/ora/10.$ORACLE_HOME/appsutil/log/$CONTEXT_NAME /MMDDHHMM/ make_$MMDDHHMM.3 (Web/HTTP Server) $IAS_ORACLE_HOME/j2ee/forms/logs $IAS_ORACLE_HOME/j2ee/oafm/logs $IAS_ORACLE_HOME/j2ee/oacore/logs $IAS_ORACLE_HOME/opmn/logs $IAS_ORACLE_HOME/network/log $INST_TOP/logs/ora/10.3) Network Logs : $ORACLE_HOME/network/admin/$SID.log 1.2) Alert Log Files : $ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.

Advantages of new INSTANCE HOME  The additional Instance Home makes the middle tier more easy to manage and organised since the data is kept separate from the config files.  Another advantage of the Instance Home is that the Autoconfig no longer writes anything to the APPL_TOP and ORACLE_HOME directories.The basic structure of the Instance Home is:$APPS_BASE/inst/apps/$CONTEXT_NAME or also defined by environment variable $INST_TOP. Changes to existing environment Variables in R12 . Earlier say the adpatch used to write the log file in APPL_TOP/admin directory but with the new model the APPL_CONFIG_HOME/admin is used. where APPS_BASE (which does not have or need a corresponding environment variable) is the top level of the Applications installation and $CONTEXT_NAME is the highest level at which the Applications context exists (format $SID_$hostname).  To create a new instance that shares an existing middle-tier. The Instance Home also has the ability to share the Applications and Technology stack code across multiple instances. just create a new instance_top with proper config files and NFS Mount the middle tier in the server. everything is now written in the INST_TOP as a result APPL_TOP and ORACLE_HOME can also be made read only file system if required .

. everything is now written in the INST_TOP as a result APPL_TOP and ORACLE_HOME can also be made read only file system if required .Advantages of new INSTANCE HOME  The additional Instance Home makes the middle tier more easy to manage and organised since the data is kept separate from the config files. The Instance Home also has the ability to share the Applications and Technology stack code across multiple instances. Earlier say the adpatch used to write the log file in APPL_TOP/admin directory but with the new model the APPL_CONFIG_HOME/admin is used.  Another advantage of the Instance Home is that the Autoconfig no longer writes anything to the APPL_TOP and ORACLE_HOME directories.

 To create a new instance that shares an existing middle-tier. Port=web_cache_port: Specifies the Oracle Application Server Web Cache listening ports Listen=Oracle_HTTP_Server_port: Specifies the HTTP and HTTPS ports obtained by Oracle HTTP Server.conf ->This is main Apache configuration file. log file locations and other configuration options and files. where APPS_BASE (which does not have or need a corresponding environment variable) is the top level of the Applications installation and $CONTEXT_NAME is the highest level at which the Applications context exists (format $SID_$hostname). just create a new instance_top with proper config files and NFS Mount the middle tier in the server. memory settings.conf -> Oracle HTTP Server includes a Java Virtual Machine (JVM). which is called JServ. From this configuration file it identify port definitions.The basic structure of the Instance Home is:$APPS_BASE/inst/apps/$CONTEXT_NAME or also defined by environment variable $INST_TOP. loggin levels. What are the key configuration files of Oracle EBS and Where are the key configuration files located(for 11i and Rel 12) EXPLANATION OF SOME IMPORTANT CONFIGURATION FILES in 11i:================================================== = httpd.properties are the key configuration files for Jserv . jserv. jserv.conf and jserv.

All our Self Service servlets requests are via mod_jserv like discoverer view.conf ->This file is used to configure pls (Plsql). stops. viewer4i. xml services or OAM login (So you know now where to look if issue happens in these services) If your Form Server is in servlet Mode then Core Applications are also accessed via Web Server (Jserv Component) This file calls few properties files like jserv. apps. oprocmgr. xmlsvcs.conf.properties.conf. This file defines to forward all requests like /pls/ to dedicated apache listener. mod_ossl. oem. zone properties.conf. These files are used for mod_pls configuration. forms.conf -> This configuration file is used to configure Oracle built modules supplied with default Apache like mod_pls.properties.properties. immeting. This file calls other configuration files like plsql.properties. . Plsql. and detects death of processes (starting new processes to replace them). mod_plsql is an Oracle HTTP Server plug-in that communicates with the database.conf ->(in Apache/conf) This Oracle module provides process management and load balancing services to JServ processes This module starts. imeeting. It is often indicated by a /pls/ virtual path. and provides load balancing services to the processes oracle_apache. It maps browser requests into database stored procedure calls over a SQL*Net connection.

Startup Shutdown Scripts Oracle Apps R12 Order of Startup Shutdown ————————————– As in Oracle Apps 11i order for startup is 1) Start Database Tier Services –Start Database Listener –Start Database Then 2) Start Application/Middle Tier Services – adstrtal. If you are changing apps password you use utility FNDCPASS and after changing password you have to manually change apps password in this file.app ->Which in my views is named so after Web Database Server for Applications.sh Order for shutdown in Oracle Apps R12 is 1) Stop Application/Middle Tier Services – adstpall.wdbsvr. This file contains your dad (database Access Descriptor) information like database connection description & apps user name & password.sh Then 2) Stop Database Tier Services –Stop Database –Stop Database Listener Database Tier Scripts in R12 ————————————– .

xml or CONTEXT_NAME. This .For Database tier you need to start database and database listener. Scripts are located inDatabase_Install_Dir/db/tech_st/10.sh Script to start / stop apps listener (FNDFS and FNDFS).2/network/ad min directory iv) adapcctl. This script will use Service Control API to start all services which are enabled after checking them in context file (SID_HOSTNAME.2 ORACLE_HOME (i.sh Script to start/stop Web Server or Oracle HTTP Server. iii) adalnctl.1.sh.e.xml) ii) adstpall. This listener will file will be in 10. Forms & Reports Home) listener.For Database Listener Use script addlnctl.ora file will be in $INST_TOP/apps/$CONTEXT_NAME/ora/10.For Database Use script addbctl.0/appsutil/scripts/$ CONTEXT_NAME.1.sh Master script to stop all components/services of middle tier or application tier.sh Master script to start all components/services of middle tier or application tier.sh or alternatively you can use lsnrctl startstop listener_name (For Database Listener) sqlplus ―/as sysdba‖ SQL> startup shutdown immediate Middle/Application Tier Scripts in R12 ————————————————Scripts for Application Tier services in R12 are located in ―Install_base/inst/apps/$CONTEXT_NAME/admin/scripts“ where CONTEXT_NAME is of format SID_HOSTNAME i) adstrtal.2.

sh ) vi) adformsctl. This scripts will also use opmnctl(similar to above) to start oacore instance of OC4J like opmnctl startproc type=oc4j instancename=oafm x) adopmnctl.3 Oracle_Home. v) adcmctl.2 Oracle_Home in Apps R12 viii) adoacorectl.sh This script will start/stop oacore OC4J in 10.1.sh This script will start/stop opmn service in 10.sh This script is used only if you wish to start forms in socket mode. This script will also use opmnctl to start/stop Forms OC4J like opmnctl stopproc type=oc4j instancename=forms vii) adformsrvctl.3 Oracle_Home.1.1.sh Script to start / stop concurrent manager (This script in turn calls startmgr. opmn will control all services in 10.1. Default forms connect method in R12 is servlet. If any services are stopped abnormally opmn will/should start them automatically. This scripts will also use opmnctl(similar to adapcctl & adformsctl) to start oacore instance of OC4J like opmnctl startproc type=oc4j instancename=oacore ix) adoafmctl.1.script uses opmn (Oracle Process Manager and Notification Server) with syntax similar to opmnctl [startstop]proc ohs like opmnctl stopproc ohs . xi) jtffmctl.sh Script to start / stop Forms OC4J from 10.sh This script will be used to start/stop one to one fulfilment .3 Oracle_Home.sh This script will start/stop oafm OC4J in 10.1.3 Oracle_Home like web server or various oc4j instances.3 Oracle_Home. If started this will start frmsrv executable from 10.

sh To start / stop mwa telnet server where mwa is mobile application. . adoacore ctl.server. adcmctl.log.adstrtal.txt. adformsctl.txt ) How to compile Oracle Apps 11i Forms ============================ Check whether the forms that you want to generate are not in use at the time you are generating them.txt.env file to set the applications environment.txt. the forms client session terminates. jtffmctl. 2) Change directory to $AU_TOP/forms/US.txt. Log File Location for Startup Shutdown Services in R12 ———————————————————————Log files for startup/shutdown scripts for application/mid tier in R12 are in$INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log (adalnctl. adapcctl. adoafmctl. xii) mwactl. 1) Login to the Forms server node as applmgr and run . If they are in use when you generate the fmx files.txt. adopmnctl.txt.txt.

2) Set the applications environment 3) Ensure that the $FORMS_PATH includes $AU_TOP/resource and $AU_TOP/resource/stub. for example echo $FORMS_PATH /u01/oracle/DEV/apps/apps_st/appl/au/12.fmb userid=apps/<apps_pwd> output_file=/forms/US/<formname>.0/resource/ stub 4) Compile the form a).0/resource: /u01/oracle/DEV/apps/apps_st/appl/au/12.0.geneva.3) Use the “f60gen” command to generate the fmx files for the fmb files.fmx How to compile Oracle Apps R12 Forms ============================= 1) Log into the forms tier.sh module=<path to fmb file> userid=APPS/APPS output_file= . 2) Set the applications environment 3) Ensure that the $FORMS_PATH includes $AU_TOP/resource and $AU_TOP/resource/stub.0/resource: /u01/oracle/DEV/apps/apps_st/appl/au/12. frmcmp_batch. 4) Issue the following command $ f60gen module=<formname>.0.">1) Log into the forms tier.If you are using forms customizations (CUily: verdana.pll) then run the command below to compile the form.0.0/resource/ stub 4) Compile the form a).If you are using forms customizations (CUSTOM.0. for example echo $FORMS_PATH /u01/oracle/DEV/apps/apps_st/appl/au/12.

0.0.fmb userid=APPS/APPS output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/ 12.0/forms/US/XXX. then run the command below to compile the form.<full path to fmx output file> module_type=form compile_all=special For eg:frmcmp_batch.fmb userid=APPS/APPS output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/ 12.sh module=<path to fmb file> userid=APPS/APPS output_file= <full path to fmx output file> module_type=form For example.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12.0/ forms/US/ XXX.0/ forms/US/ XXX.fmx module_type=form How To Trace a Concurrent Request And Generate TKPROF Enable Tracing For The Concurrent Manager Program Select the Enable Trace Checkbox . frmcmp_batch.fmx module_type=form compile_all=special b) If you are NOT using forms customizations.0/forms/US/XXX. frmcmp_batch.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12..0.0.

So even if the trace is set for Binds and Waits on the Submission form once the concurrent program is encountered in the trace it will reset to level 8 so no binds will be present in the trace after that point. Turn On Tracing Responsibility: System Administrator Navigate: Profiles > System Query Profile Option Concurrent: Allow Debugging Set profile to Yes Run Concurrent Program With Tracing Turned On Logon to the Responsibility that runs the Concurrent Program In the Submit Request Screen click on Debug Options (B) Select the Checkbox for SQL Trace .       Note : Checking the Trace Check box on the Concurrent Program gives an Event 10046 Level 8 trace.

The SQL prompts the user for the request id prompt accept request prompt 'Please enter the concurre nt request id for the appropriate concurrent pro gram:' promptcolumn traceid format a8 column tracename format a80 column user_concurrent_program_name format a40 column execname format a15 column enable_trace format a12 set lines 80 set pages 22 set head offSELECT 'Request id: '||request_id . 'Trace id: '||oracle_Process_id.If the Debug option is greyed out & not updateable set the profile Concurrent: Allow Debugging to Yes 2. . Find Trace File Name Run the following SQL to find out the Raw trace name and location for the concurrent program.

application_id = execname.addr = ses.'Trace Flag: '||req.program_application_id = prog.'Normal').executable_id.user_concurrent_program_nam e.paddr(+) and dest.subroutine_name .spid(+) and proc.request_id = &request and req.sid||'. v$session ses. To check the timeline of the request : .serial#.oracle_process_id=proc.'R'.application_i d and prog.concurrent_ program_id and req.value)||'_ora_'|| oracle_process_id||'. fnd_executables execname where req. v$process proc.value||'/'||lower(dbnm. fnd_concurre nt_programs_vl prog. 'Module : '||ses. Name: '||prog. v$parameter dbnm. 'Trace Name: '||dest.'Running') ||'-'||decode(status_code. v$parameter dest.enable_trace.execution_file_name|| ex ecname.application_id and prog.trc'.applicatio n_id --and prog.concurrent_program_id = prog.name='user_dump_dest' and dbnm. 'Prog.executable_application_id = execname. 'Status : '||decode(phase_code. 'File Name: '||execname.'|| ses. 'SID Serial: '||ses.executable_id=execname.module from fnd_concurrent_requests req.'R'.name='db_name' and req.

'DD-MON-YYYY HH24:MI:SS' ) actual_completion_date.trc: Name of trace file output_file: tkprof out file explain: This option provides the explain plan for the sql statements sort: This provides the sort criteria in which all sql statements will be sorted. 'DDMON-YYYY HH24:MI:SS' ) current_date.trc output_file explain=apps/apps sort=(exeela. You may produce a complete report reference of the request ID using the Note:187504. TO_CHAR( actual_completion_date. TO_CHAR( sysdate.1 bde_request. 'DDMON-YYYY HH24:MI:SS' ) request_date. 'DD-MON-YYYY HH24:MI:SS' ) actual_start_date. sysdate ) actual_start_date ) * 24.fchela) sys=noWhere:raw_trace_file. This will bring the bad sql at . TO_CHAR( request_date. TO_CHAR( actual_start_date. TO_CHAR( requested_start_date.5) 3.SELECT request_id.'DDMON-YYYY HH24:MI:SS' ) requested_start_date. TKPROF Trace File Once you have obtained the Raw trace file you need to format the file using TKPROF. $tkprof raw_trace_file. 2 ) duration FROM fnd_concurrent_requests WHERE request_id = TO_NUMBER('&p_request_id'). ROUND( ( NVL( actual_completion_date.sql Process and Session info for one Concurrent Request(11.

86 8000 How to check snapshot information SQL> select aat.LAST_UPDATE_DATE.456. sys=no: Disables sql statements issued by user SYS How to check whether the port is opened or not from client machine Status Check of port 8000 from Windows Operating System Go to Start menu tab.CREATION_DATE.AD_SNAPSHOTS asn.APPL_TOP_ID = aat.'||host||‘.SNAPSHOT_TYPE = ‗C‘.RAN_SNAPSHOT_FLAG FROM APPS.APPL_TOP_ID AND asn. How to check for DB links Execute this command as sysdba SQL> select owner||‘.789. . Then run ‗cmd. asn.'||db_link||‘.'||created from dba_db_links.‘ which will take you to the command prompt. In the command prompt. APPS. After that you can check the status of DB links to know which DB links are working/not working SQL>Select sysdate from dual@< DB_LINK> .AD_APPL_TOPS aat WHERE asn.asn.NAME.'||username||‘.asn. you must type the following command and hit Enter: telnet 123.the top of the outputfile.

Run (@adutconf. find SID from v$session.—————1234 365 366 1234 366 365 In second step find the serial number for the Blocking Session to kill using SID SQL> select SERIAL# from v$session where SID=365.lst How to find Oracle Database Blocking Session Details In first step. but there is simple way to find it out. SERIAL# ———130 .Go to $AD_TOP/sql 2.Output will be in same directory in the name of adutconf.How to find Release version of Oracle Apps? Login to sqlplus as apps/apps SQL> select release_name from fnd_product_groups. 1. SQL> select process. PROCESS SID BLOCKING_SESSION ———— ———. blocking_session from v$session where blocking_session is not null.sql) 4.0.Connect to sqlplus as apps/apps 3.0 How to find a product version in Oracle Applications?? There are so many ways to find out the product version. RELEASE_NAME ————————————————– 12.sid.

System altered Oracle Apps Yellow Bar Issue It can occur while copying the content from Apps to Any other application like Apps forms to notepad or excel. Choose any responsibility.130′.wku. 2.exe with the following errors. by Info-ZIP (ZipBugs@lists.In third step. Uninstall the the Jinitiator from the system (Control Panel) 3. Appsbase.edu). Delete cache : Delete all the files from Temporary Internet Files and temp table. It instals the latest version available on server and now you can see ―Yellow Bar‖ is disabled and you can perform Copy and Paste If you have problem while installing jinitiator.40 of 28 November 1998. kill the blocking session using SID and serial number SQL> alter system kill session ’365. ================================================== ========== UnZipSFX 5. Open the Oracle application Login to apps. . Troubleshooting: 1.htm window will be opened(which initiates Applet in it).

How to check the version of jinitiator on your sever? .bat extracting: setup. Then downlod the jinitiator.x.txt extracting: oajsetup.cerextracting: adjbuild/jinit11816..x Oracle Jinitiator Setup Utility Copyright (c) Oracle Corp. exeextracting: autosetup.extracting: adjbuild/appltop.1. 2000 Usage: oajsetup [] [] The system cannot find the file specified. exeextracting: adjbuild/oajsetup. ================================================== ========== It may happen because some times the version at server may be corrupted or so.bat oajsetup: Jinitiator version number not valid. should be 1. The batch file cannot be found.exe and version should be same as the one you have on server.

there you right click and view source there you can see the version of jinitiator. If you still have problem.obj ‖ from any of your network users who are using the same Oracle application and paste in your ―Oracle‖ folder where jinitiator is installed the typical path is like c:\program files\oracle\identitydb. .obj How to recover the Oracle Applications context file The Oracle Applications context file can be recovered by running the adclonectx.com/technology/software/products/developer/ht docs/jinit. select the option of retrieving the Applications tier context file that has been lost and retrieve it to the default location specified by the script. copy the ‖ identitydb.pl script. delete all the temporaty files from PC Install jinitiator in your PC and check the Oracle apps again.htm Clear Cache. perl /clone/bin/adclonectx. you can see a appsbase.htm which starts applet.pl retrieve On being prompted for the context file to be retrieved. It should work now. Download the jinitiator from the above below path http://www.When you login to apps and choose responsibility. there is another tip.oracle.

Commit complete.pls AFSCJAVS. set it to any existing directory with write permission. Once the context file has been generated in the specified location.orig Add following lines to the AFSCJAVS. Login to Middle Tier as ap user $cd $FND_TOP/patch/115/sql $cp AFSCJAVS.pl retrieve On being prompted for the context file to be retrieved. While confirming the location for the context file.pls file CREATE OR REPLACE PACKAGE apps.The above command can be used only when INST_TOP the is still intact. The below method is not suggested for Production or Critical systems. $sqlplus system/ @AFSCJAVS. Please note you need have system password to perform the below actions. select the option of retrieving the Applications tier context file that has been lost. In case the has also been lost accidentally. value in varchar2) return varchar2. . How to find Oracle Apps password in 11i and R12?? The below methog helps us to find out when we lost the Apps password.fnd_web_sec AS function decrypt(key in varchar2.pls Package created.pls. move it to the location specified for the context file in the context variable ‗s_contextfile‘. the Applications tier context file may be retrieved as follows: Execute the following command on the Database tier: perl /appsutil/clone/bin/adclonectx.

owner from dba_objects where object_name='FND_WEB_SEC'.object_type.FND_WEB_SEC. As system excute the following. If there are any invalids compile them. select object_name.fnd_profile_options where profile_option_name='GUEST_USER_PWD').FND_WEB_SEC compile body. set line 200. Package body altered. Obtain Guest user ID and password.status.fnd_profile_option_values where profile_option_id = (select profile_option_id from apps. SQL>col OBJECT_NAME for a30.status. Synonym created. PROFILE_OPTION_VALUEGUEST/ORACLE SQL> show user USER is "SYSTEM" SQL> create synonym FND_WEB_SEC_TEST for apps.object_type. select object_name. SQL> show user USER is "SYSTEM" SQL> select profile_option_value from apps.As system excute the following to find out if anything marked as invalid. set line 200. SQL> show user USER is "SYSTEM" SQL>col OBJECT_NAME for a30. SQL> show user USER is "SYSTEM" .owner from dba_objects where object_name='FND_WEB_SEC'. OBJECT_NAME OBJECT_TYPE STATUS OWNER FND_WEB_SEC PACKAGE VALID APPSFND_WEB_SEC PACKAGE BODY INVALID APPS SQL> alter PACKAGE apps.

Now Obtain Apps password using the below sql SQL> SELECT(SELECTfnd_web_sec_test.WOW we got the Apps password now SQL> drop synonym FND_WEB_SEC_TEST.encrypted_foundation_password)FROM dual)AS APPS_PASSWORDFROMapps. Commit complete.decrypt('GUEST/ORA CLE'. -bash-3. .FND_WEB_SEC.Both tables use the same encryption algorithm to protect the passwords... 2 3 4 5 6 7 8 9 APPS_PASSWORDAPPS -.The FND_USER table stores application user account passwords and the FND_ORACLE_USERID table stores internal Oracle Applications database account passwords. Synonym created. Column Value Encryption Key ENCRYPTED_FOUNDATION_PASSWORD APPS username/password ENCRYPTED_USER_PASSWORD user APPS password The 2 columns as. Please find the below explanation for the above steps: A) We know in Oracle Applications passwords are stored in FND_USER and FND_ORACLE_USERID tables. There are two password columns in this table: ENCRYPTED_FOUNDATION_PASSWORD and ENCRYPTED_USER_PASSWORD.fnd_userWHEREuser_name like 'GUEST'.pls Package created. The FND_USER table contains all the application accounts.SQL> create synonym FND_WEB_SEC_TEST for apps. Synonym dropped.2$ sqlplus apps/ @AFSCJAVS.

pls above. All rights reserved. object_name. FNDCPASS SYNTAX AND TROUBLE SHOOTING In Oracle Applications. COLUMN object_name FORMAT A30 SELECT owner. product schema passwords. object_type. So to make the function available outside the package.22 (c) Copyright 2000-2006 Oracle Corporation.The DECRYPT function in the FND_WEB_SEC package is a local function and cannot be called from outside the package. status FROM dba_objects WHERE status = ‗INVALID‘ ORDER BY owner. we have an FND functionality for changing the passwords for application users. object_name. object_type.0.a)If we know the username/password we can get the Apps Password (ENCRYPTED_FOUNDATION_PASSWORD)b)If we know the Apps password we can get any users password (ENCRYPTED_USER_PASSWORD) B) To decrypt and verify user passwords Oracle Apps uses FND_WEB_SEC package in Apps. and ―APPS and APPLSYS. How to find rapidwiz version Go to: cd startCD\Disk1\rapidwiz type: rapidwiz Version Output will be: Oracle Applications Rapid Install Wizard Version 12.0. we have altered the AFSCJAVS. Press any key to continue Invalid Objects Query SQL> select count(*) from dba_objects where status=‘INVALID‘. .‖ The location of FNDCPASS utility is $FND_TOP/bin directory.

it will give you these details. The first usage FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME is for changing the password for apps and applsys. Following activities will take place (1) applsys validation. Oracle recomends using FNDCPASS only to change apps and applsys password.FNDCPASS Usage: FNDCPASS logon 0 Y system/password mode username new_password where logon is username/password[@connect] system/password is password of the system account of that database mode is SYSTEM/USER/ORACLE username is the username where you want to change its password new_password is the new password in unencrypted format example FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1 FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME If you just type FNDCPASS and press enter. Also note that using this command will change the password for both apps and applsys. Please do not try any other method for changing apps and applsys password. You can change the password of these users using this command. Note that this is the only way to change the password for apps and applsys. These are the database schema users (most important for application to work). Password for both these users should be in synch. (make sure APPLSYS name is correct) (2) re-encrypt all password in FND_USER (3) re-encrypt all password in FND_ORACLE_USERID .

(2) alter user to change GL‘s password. If GL does not exists. The third usage FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME is for changing the application level passwords like sysadmin etc used for logging into application. Message for invalid oracle user is written in the log file. step (2) below does not happen. The new password is re-encrypted with the current applsys password. . The new password is re-encrypted with the current applsys password. If VISION does not exist. (5) Update apps password in FND_ORACLE_USERID table. message for invalid application user is written in the log file.(4) update applsys‘s password in FND_ORACLE_USERID table. No products affected by the patch When you run FNDCPASS command it will check the integrity of all schema password in the application. If any of the password is corrupt then this will through and error and will not change the password. Also changes are made in DBA_USERS table. Following activities will take place (1) update GL‘s password in FND_ORACLE_USERID table. GL etc. The second usage FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1 is for changing password for any other product schema like MSC. Following activities will take place (1) update VISION‘s password in FND_USER table.

Always use FNDCPASS.The tables that it uses is FND_USER and FND_ORACLE_USERID. When we run FNDCPASS it will update all the above 3 tables. . System password can be set directly using ALTER command in database. Issue with APPLSYS and APPS password Issue 1: As you know that apps and applsys password should be in synch and should be changed using FNDCPASS. So always be cautions about this command. All the application passwords and schema passwords are stored in these two tables. Best usage of FNDCPASS Before using FNDCPASS: 1) Always keep the back of tables FND_USER and FND_ORACLE_USERID. In case if FNDCPASS fails then it might corrupt the passwords of your application and worst can happen that the application wont come up. Ofcourse DBA_USERS will have the schema users and password stored as well. applsys or any schema password directly from database using the alter command. You can take back of these tables using CREATE TABLE — AS SELECT * FROM —. You must have backup of these tables before running FNDCPASS. 4) Never update apps. Like verify that apps and system passwords you are providing is correct. 2) If possible also keep an export dump of these two tables. 3) verify each arguement you are providing to FNDCPASS.

you get following error . or there may have been a database connect error. Resolution to such problem is to rollback the 2 tables FND_USER and FND_ORACLE_USERID. apps and applsys passwords will be in synch and password will be older one. You may have entered an invalid applications password. Use the ALTER USER command to change the APPLSYS password 2. You will get an error ―Cannot complete applications logon. Infact the services even wont start. Try to run the adstrall. Once you rollback the tables. You can then run FNDCPASS and change the password.‖ 4. Then try FNDCPASS to fix password and you will get the error the APP-FND-01496 error. Issue 2: Some times when you run FNDCPASS. You can even reproduce this issue (ofcourse after taking the backup of FND_USER and FND_ORACLE_USERID table) using the following steps 1. 3.sh script to start Apps services. If this situation happens then you cannot access the application.There can be situation where a novice user changes applsys password from the backend database. In that case when you try to start the services it will show following error APP-FND-01496: Cannot access application ORACLE password Cause: Application Object Library was unable access your ORACLE password.

APP-FND-01502: Cannot encrypt application ORACLE password Cause: Application Object Library was unable encrypt your ORACLE password. Action: Contact your support representative. This will resolve this issue. Those rows must be deleted from the table. Still following methodology is proposed which might help you to restore the password back and make your application work fine. (ORACLEUSER=APPS_SERV) The error comes because the table fnd_oracle_userid contain rows for schemas that does not exist. This method is for resetting apps and applsys passwords. Use the following query to get the details of the schema that doest not exists select * from fnd_oracle_userid where oracle_username not in (select username from all_users). Below are the SQL statements that will help you reset the APPS and . Under such situation. For this to work you should have some other application (may be debug or UAT) which is having the same passwords or default passwords for schemas. Issue 3: There can be situation where users has update APPLSYS password using ALTER command in database directly and also you dont have backup of those tables. If you have such application the following the below steps in the application which is affected by password mismatch. it is very difficult to recover the application and make it working. The rows returned by this query can be deleted from FND_ORACLE_USERID table.

WARNING: This procedure will cause all user passwords to become invalid. update FND_ORACLE_USERID set ENCRYPTED_ORACLE_PASSWORD = ‗ZGA34EA20B5C4C9726CC95AA9D49EA4DBA8EDB705CB767 .APPLSYS passwords to APPS. ALTER USER applsyspub IDENTIFIED BY pub. Open a SQL*Plus session as APPLSYS and backup the tables: create table FND_ORACLE_USERID_BAK as (select * from FND_ORACLE_USERID). do take a backup. You can restore the same when ever you want). ALL users passwords will need to be reset through the sysadmin responsibility. create table FND_USER_BAK as (select * from FND_USER). and the APPLSYSPUB Oracle user ID: ALTER USER apps IDENTIFIED BY apps. the APPLSYSPUB password to PUB. Step 1) Reset the Oracle User IDs Open a SQL*Plus as SYSTEM and reset the passwords for the APPS. APPLSYS. and the SYSADMIN password to SYSADMIN. Step 2) Backup the FND_ORACLE_USERID and FND_USER tables (even though these tables are right now corrupted. Step 3) Reset the APPS and APPLSYS application encrypted passwords Open a SQL*Plus session as APPLSYS and update the FND_ORACLE_USERID table. ALTER USER applsys IDENTIFIED BY apps.

Verify the table update: select ENCRYPTED_ORACLE_PASSWORD from FND_ORACLE_USERID where ORACLE_USERNAME IN (‗APPS‘. So if your application is having apps password the encrypted string will look like this. Step 4) Reset the APPLSYSPUB application encrypted password Open a SQL*Plus session as APPLSYS and update the FND_ORACLE_USERID table. If your applsyspub password is pub then the encrypted string in FND_ORACLE_USERID will look like this. . ‗APPLSYS‘). We are updating this encrypted string here directly. ‗APPLSYS‘). update FND_ORACLE_USERID set ENCRYPTED_ORACLE_PASSWORD = ‗ZG31EC3DD2BD7FB8AD2628CE87DDDF148C1D2F248BE88B E987FDF82830228A88EF44BC78BC7A9FAD4BFB8F09DAD49 DF7280E‘ where ORACLE_USERNAME = (‗APPLSYSPUB‘). This encrypted string we are updating is the default encrypted string for apps.3E645EED570D5447161491D78D444554655B87486EF537ED9 843C8′ where ORACLE_USERNAME in (‗APPS‘. Verify the table update: select ENCRYPTED_ORACLE_PASSWORD from FND_ORACLE_USERID where ORACLE_USERNAME = ‗APPLSYSPUB‘. commit. commit. The above encrypted string is the encrypted string for password pub.

to_char(last_connect.spid = b.process and d. apps.pid=c. select count(distinct user_id) ―users‖ from icx_sessions where last_connect > sysdate – 1/24 and user_id != ‗-1′. try your luck by running FNDCPASS and it should work fine. 4: Use this SQL statement to get number of users connected to Oracle Apps in the last 15 minutes. 3: Use this SQL statement to get number of users connected to Oracle Apps in the past 1 day.fnd_user d where b.user_name) from apps.user_id and (d.paddr = c.user_id = a.pid and a. user_id. disabled_flag from icx_sessions where last_connect > sysdate – 1/96. v$process c. ‗DD-MONRR HH:MI:SS‘) ―Last Connection time‖. limit_connects. select limit_time. .addr and a. select count(distinct user_id) ―users‖ from icx_sessions where last_connect > sysdate – 1 and user_id != ‗-1′. How to know how many users connected to Oracle Applications 1: Use this SQL statement to count number of concurrent_users connected to Oracle apps: select count(distinct d.Once these updates are done.fnd_logins a.user_name = ‗USER_NAME‘ OR 1=1) 2: Use this SQL statement to count number of users connected to Oracle Apps in the past 1 hour. v$session b.

However.---------------------------APPLIED_PATCH_ID NOT NULL NUMBER RAPID_INSTALLED_FLAG VARCHAR2(1) PATCH_NAME NOT NULL VARCHAR2(120) PATCH_TYPE NOT NULL VARCHAR2(30) MAINT_PACK_LEVEL VARCHAR2(30) SOURCE_CODE NOT NULL VARCHAR2(3) CREATION_DATE NOT NULL DATE CREATED_BY NOT NULL NUMBER LAST_UPDATE_DATE NOT NULL DATE LAST_UPDATED_BY NOT NULL NUMBER IMPORTED_FLAG VARCHAR2(1) IMPORTED_FROM_DB VARCHAR2(30) IMPORTED_ID NUMBER MERGE_DATE DATE DATA_MODEL_DONE_FLAG VARCHAR2(1) . with busy work schedules. keeping track of applied patches can be a challenge.How to find applied patches for R12 EBS Oracle Applications One key task for Oracle Application EBS Database Administrators is to perform patching on regular basis for maintenance pack upgrades and bug fixes. Oracle R12 Applications uses the following tables under the APPS schema to track the status for bug fixes and patches with adpatch: ad_applied_patches ad_bugs SQL> desc ad_applied_patches Name Null? Type ----------------------------------------.-------.

--------------45449 03-DEC-09 45450 03-DEC-09 45451 03-DEC-09 Hope this quick tip helps fellow Oracle Apps DBAs. .--------------41444 03-NOV-09 41445 03-NOV-09 42444 09-NOV-09 42445 09-NOV-09 43444 18-NOV-09 44444 24-NOV-09 45444 30-NOV-09 45445 30-NOV-09 45446 30-NOV-09 45447 30-NOV-09 45448 03-DEC-09 APPLIED_PATCH_ID LAST_UPDATE_DAT ---------------.A useful query to track status of applied patches for the EBusiness Suite with Oracle EBS is the following: SQL> select applied_patch_id. APPLIED_PATCH_ID LAST_UPDATE_DAT ---------------. last_update_date from ad_applied_patches order by last_update_date.

Sign up to vote on this title
UsefulNot useful