Order of Startup ShutdownAs in Oracle Apps 11i order for startup isA) Start Database Tier ServicesStart Database ListenerStart DatabaseThenB) Start Application/Middle Tier Services adstrtal.shOrder for shutdown in Oracle Apps R12 isA) Stop Application/Middle Tier Services adstpall.shThenB) Stop Database Tier ServicesStop DatabaseStop Database ListenerDatabase Tier Scripts in R12For Database tier you need to start database and database listener. Scripts are located in Database_Install_Dir/db/tech_st/10.2.0/appsutil/scripts/$CONTEXT_NAME- For DatabaseUse script addbctl.sh- For Database Listener Use script addlnctl.shor alternatively you can uselsnrctl startstop listener_name (For Database Listener)sqlplus /as sysdbaSQL> startup shutdown immediateMiddle/Application Tier Scripts in R12-Scripts for Application Tier services in R12 are located in Install_base/inst/apps/$CONTEXT_NAME/admin/scriptswhere CONTEXT_NAME is of format SID_HOSTNAMEi) 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.xml)ii) adstpall.shMaster script to stop all components/services of middle tier or application tier.iii) adalnctl.sh Script to start / stop apps listener (FNDFS and FNDFS). This listener will file will be in 10.1.2 ORACLE_HOME (i.e. Forms & Reports Home)listener.ora file will be in $INST_TOP/apps/$CONTEXT_NAME/ora/10.1.2/network/admin directory(Mostly similar to one in 11i with only change in ORACLE_HOME i.e. from 8.0.6 to 10.1.2 )iv) adapcctl.shScript to start/stop Web Server or Oracle HTTP Server. This script uses opmn (Oracle Process Manager and Notification Server) with syntax similar to opmnctl [startstop]proc ohslike opmnctl stopproc ohs .(In 11i this script directly used to call apachectl executable but now calls opmnctl which in turn calls apachectl. In 11i web server oracle home was 1.0.2.2.2 but in R12 its 10.1.3)v) adcmctl.sh Script to start / stop concurrent manager, Similar to one in 11i. (This script in turn calls startmgr.sh )vi) adformsctl.shScript to start / stop Forms OC4J from 10.1.3 Oracle_Home. This script will also use opmnctl to start/stop Forms OC4J likeopmnctl stopproc type=oc4j instancename=formsvii) adformsrvctl.shThis script is used only if you wish to start forms in socket mode. Default forms connect method in R12 is servlet.If started this will start frmsrv executable from 10.1.2 Oracle_Home in Apps R12viii) adoacorectl.shThis script will start/stop oacore OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl (similar to adapcctl & adformsctl) to start oacore instance of OC4J likeopmnctl startproc type=oc4j instancename=oacoreix) adoafmctl.shThis script will start/stop oafm OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl (similar to above) to start oacore instance of OC4J likeopmnctl startproc type=oc4j instancename=oafmx) adopmnctl.shThis script will start/stop opmn service in 10.1.3 Oracle_Home. opmn will control all services in 10.1.3 Oracle_Home like web server or various oc4j instances. If any services are stopped abnormally opmn will/should start them automatically.xi) jtffmctl.shThis script will be used to start/stop one to one fulfilment server.xii) mwactl.shTo start / stop mwa telnet server where mwa is mobile application.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.txt, adapcctl.txt, adcmctl.txt, adformsctl.txt, adoacorectl.txt, adoafmctl.txt, adopmnctl.txt, adstrtal.log, jtffmctl.txt )

/addlnctl.sh start VIS (works from oracle and root user)./addbctl.sh start (works from oracle but not from root user)./adstrtal.sh apps/apps (works but does not work from oracle user but works from root)

Startup / Shutdown Apps In our next topic in learning Oracle Apps DBA , this post covers startup & shutdown of Oracle Application DBAAs you are aware by now there is Database Tier ( Database & DB Listener ) and Application Tier ( WebServer, Forms, Reports, Concurrent Manager, Discoverer, Apps Listener, OnetoOne Fullfillment Server )Order of StartUp of Services Should be First DB Listener, Database & then Application Tier ServicesOrder of ShutDown of Services Should beFirst Application Tier Services then Database & DB ListenerDatabase Startup/Shutdown ScriptsDepending on your AD Version these will be in ORACLE_HOME / appsutil/scripts /SID_hostnameaddbctl.sh database startup shutdown scriptaddlnctl.sh database listener Script Where AD is for Application DBADB is for databaseDLN is database listenerCTL is controlIsnt this easy to remeber ( Thanks to Oracle for naming convention)Application Tier Startup/Shutdown ScriptsDepending on your AD Version these will be inOAD_TOP/admin/scripts/ SID_hostnameadalnctl.sh Apps Listener Control Scriptadapcctl.sh Apache/Web Server Control Scriptadcmctl.sh Concurrent Manager Control Scriptaddisctl.sh Discoverer Control Scriptadfrmctl.sh Forms server Control Scriptadrepctl.sh Report Server Control Scriptadstpall.sh Stop All Middle/Application Tieradstrtall.sh Start All Middle/Application TierWhere AD & CTL you already know now isnt itadl stand for Apps Listenerapc stand for Apachecm Concurrent Managerdis Discovererfrm formsrep reportDo you know whats Use of Apps Listener ? Check else I will post it in future post .Check what Advertisers has to say on your right side of pageQuestion: I just got Oracle Applications eBusiness Suite Release 12, and patch 3842506 recommend running the OATM tablespace migration utility. I tried running it but I am getting errors and I dont understand the purpose of running OATM. What does the OATM do, and why are OATM tablespaces important?Answer: The OATM procedure was designed to migrate Oracle Applications 11i and 12i systems to UNIX-based filesystems to raw devices as a preparatory step to RAC, which requires RAW devices. Beware, that a migration to RAC is very tricky and it should never be attempted by somebody without a history of success. Its an Oracle best practice to engage experts to perform your RAC migration and guarantee your migration to RAC is successful.Oracle Applications has become a massive product that performs virtually every possible area of managing a business. When ERP products get huge, standardization becomes important, and the new Oracle Applications Tablespace Model (OATM) has a tablespace migration utility in R12 as well as instructions as noted in MOSC patch number 3942506. OATM does tablespace consolidation with an eye towards maintaining a uniform logical storage layer for the application: Move data files to from UNIX File System files (UFS) to raw devices to allow RAC to read the files. Standardizes tablespaces to allow for uniform file striping via ASM. Consolidates tablespaces from 382 tablespaces down to only 9 standard tablespaces. Creates only one locally managed tablespace for all transaction tables and another LMT for transaction indexes.OATM has these system management tablespaces: undo tablespace - Undo data temp tablespace - Temporary data. Global Temporary tables system tablespace - system tablespace. Holds data dictionaryOATM also creates these new application tablespaces: apps_ts_tx_data tablespace OATM tablespace for transaction tables apps_ts_tx_idx tablespace - OATM tablespace for transaction Indexes apps_ts_seed tablespace - OATM tablespace for FND objects (reference and setup data) plus indexes. apps_ts_interface tablespace - OATM tablespace for Interface and temporary objects (temp data and indexes). apps_ts_summary tablespace OATM tablespace for summary management objects, a.k.a. materialized views. apps_ts_nologging tablespace This OATM tablespace is reserved for materialized views that are dro[pped and re-created in nologging mode. apps_ts_queues tablespace - This is the OATM tablespace for advanced queuing objects apps_ts_media tablespace - Multimedia objects apps_ts_archive tablespace - Archive purge related objectsIn sum, OATM is a new unified way of managing the complexity of over 380 tablespaces by moving them into only 9 applications tablespaces, all utilizing identical features.