Monday, January 11, 2016

Fusion Apps 11.1.8 Startup and Shutdown Steps


FUSION APPS 11.1.8 SHUTDOW

1) FUSION APPS DOMAINS AND INSTANCE SHUTDOWN - 

Your paths may be different please check and proceed.

a) Navigate to directory to stop OHS service:

[oracle@orafus ~]$ cd /u01/fusion118/app/oracle/instance/CommonDomain_webtier/bin/

[oracle@orafus ~]$ ./opmnctl stopall
 
b) Navigate to directory stop BI:

      [oracle@orafus ~]$~]$ cd /u01/fusion118/app/oracle/instance/BIInstance/bin/

      [oracle@orafus ~]$ ./opmnctl stopall

c) Navigate to directory stop GOP:

[oracle@orafus ~]$ ~]$ cd /u01/fusion118/app/oracle/instance/gop_1/bin/

[oracle@orafus ~]$ ./opmnctl stopall

d) Navigate to directory Fusion Application Ad/bin: With one script “./fastartstop.sh” all Fusion Apps Domains including Adminservers, managed servers, are stopped.

     [oracle@orafus ~]$ ~]$ cd /u01/fusion118/app/oracle/fusionapps/applications/lcm/ad/bin/

     [oracle@orafus ~]$ ./fastartstop.sh -Stop -all -username FAAdmin -appbase /u01/fusion118/app/oracle/fusionapps/applications/

e) Kill Nodemanager process by grep the process with below command: Kill process ID found. 

      [oracle@orafus ~]$ ps –ef| grep /u01/ |grep nodemanager

      [oracle@orafus ~] kill -9 “process ID”

f)   Stop Fusion Apps Database

[oracle@orafus ~]$export ORACLE_SID=fusiondb

[oracle@orafus ~]$ export ORACLE_HOME= /u01/fusion118/app/database/product/11.2.0/dbhome_1

g)   Check the database name must be “FUSIONDB”

      [oracle@orafus ~]$ select name from v$database;

h)  Connect as sysdba and shutdown the database now with Immediate command:

[oracle@orafus ~]$ sqlplus / as sysdba

[oracle@orafus ~]$ shutdown immediate

i)  Stop the listener:
 
       [oracle@orafus ~]$ lsnrctl stop LISTENER_FUSIONDB


2) IDM DOMAINS AND INSTANCE SHUTDOWN

Your paths may be different please check and proceed.

We need to shutdown IDM Node and Database (This consist of following Services):

OID Instance, Web Instance, ODSM Instance, Node Manager, Admin Server, and SOA, OIM, OIM, OID Managed Servers

a) Navigate to the scripts directory:

[oracle@orafus ~]$ cd /u03/app/oracle/config/scripts

b) Issue the stopall command.

[oracle@orafus ~]$ ./stopall.sh

c) It will ask for Node Manager and Weblogic Password:     

[oracle@orafus ~]$ Enter NodeManager Password: Oracle832
     
      [oracle@orafus ~]$ Enter Weblogic Admin Password: Oracle832

d)   Check the logs at this path once all the above mentioned services are stopped:

[oracle@orafus ~]$ /u03/app/oracle/config/scripts/logs

e)   Stop IDM Database

[oracle@orafus ~]$ export ORACLE_SID=idmdb

[oracle@orafus ~]$ export ORACLE_HOME=/u03/app/database/product/11.2.0/dbhome_1

f)   Check the database name must be “IDMDB”

      [oracle@orafus ~]$ select name from v$database;

g)  Shutdown the database now with Immediate command:

[oracle@orafus ~]$ sqlplus / as sysdba

[oracle@orafus ~]$ shutdown immediate

h)  Stop the listener:
 

       [oracle@orafus ~]$ lsnrctl stop LISTENER_IDMDB


                                                       FUSION APPS 11.1.8 STARTUP

1) IDM DOMAINS AND INSTANCE STARTUP

Your paths may be different please check and proceed.

We need to startup first IDM Node and Database (This consist of following Services):

OID Instance, Web Instance, ODSM Instance, Node Manager, Admin Server, and SOA, OIM, OIM, OID Managed Servers

Start IDM Database

a)   [oracle@orafus ~]$ export ORACLE_SID=idmdb

[oracle@orafus ~]$ export ORACLE_HOME=/u01/app/database/product/11.2.0/dbhome_1

b)  Startup the database now with startup command:

[oracle@orafus ~]$ sqlplus / as sysdba

[oracle@orafus ~]$ startup

c)   Check the database name must be “IDMDB” after startup:

      [oracle@orafus ~]$ select name from v$database;

d)  Start the listener:
 
       [oracle@orafus ~]$ lsnrctl start LISTENER_IDMDB

e) Navigate to the scripts directory:

[oracle@orafus ~]$ cd /u03/app/oracle/config/scripts

f) Issue the startall command.

[oracle@orafus ~]$ ./startall.sh

g) It will ask for Node Manager and Weblogic Password:     

[oracle@orafus ~]$ Enter NodeManager Password: Oracle832  

      [oracle@orafus ~]$ Enter Weblogic Admin Password: Oracle832

h)   Check the logs at this path once all the above mentioned services are stopped:

[oracle@orafus ~]$ /u03/app/oracle/config/scripts/logs


2) FUSION APPS DOMAINS AND INSTANCE STARTUP

Your paths may be different please check and proceed.

a)   Start Fusion Apps Database
                                                   
[oracle@orafus ~]$ export ORACLE_SID=fusiondb

[oracle@orafus ~]$ export ORACLE_HOME= /u03/fusion118/app/database/product/11.2.0/dbhome_1

b)  Connect as sysdba and start database now with startup command:

[oracle@orafus ~]$ sqlplus / as sysdba

[oracle@orafus ~]$ startup

c)   Check the database name must be “FUSIONDB”

      [oracle@orafus ~]$ select name from v$database;

d)  Start the listener:
 
       [oracle@orafus ~]$ lsnrctl start LISTENER_FUSIONDB

e) Navigate to directory to start OHS service:

[oracle@orafus ~]$ cd /u01/fusion118/app/oracle/instance/CommonDomain_webtier/bin/

[oracle@orafus ~]$ ./opmnctl startall
 
f) Navigate to directory start BI:

      [oracle@orafus ~]$ cd /u01/fusion118/app/oracle/instance/BIInstance/bin/

      [oracle@orafus ~]$ ./opmnctl startall

g) Navigate to directory start GOP:

[oracle@orafus ~]$ cd /u01/fusion118/app/oracle/instance/gop_1/bin/

[oracle@orafus ~]$ ./opmnctl startall

h) Navigate and Start Nodemanager process:

      [oracle@orafus ~]$ cd /u01/fusion118/app/oracle/instance/nodemanager/igatefusionapps.igatecorp.com

[oracle@orafus ~]$ ./startNodeManagerWrapper.sh & disown

i) Navigate to directory Fusion Application Ad/bin: With one script “./fastartstop.sh” all Fusion Apps domains including Adminservers, managed servers, are started.

     [oracle@orafus ~]$ cd /u01/fusion118/app/oracle/fusionapps/applications/lcm/ad/bin/

     [oracle@orafus ~]$ ./fastartstop.sh -Start -all -username FAAdmin -appbase /u01/fusion118/app/oracle/fusionapps/applications/

**************************************Done****************************

Note - For physical or virtual installation of fusion applications at your end for learning and training purpose only please contact us at
info@orainstall.com



In Fusion 11.1.8 HCM Application error in the Admin Server logs for HCM Domain.

Error in Fusion HCM Domain Admin Server logs:

####<Nov 30, 2015 10:11:08 AM IST> <Error> <oracle.adf.share.jndi.MDSBackingStore> <igatefusionapps.igatecorp.com> <TalentManagementServer_1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <d5bf8a97eae9c8ed:-610dacbb:15156ab6da9:-8000-0000000000000002> <1448858468927> <JBO-1400> <Exception while getting mutable object
oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/oracle/apps/financials/generalLedger/accounts/codeCombinations/publicFlex/ccDscr/applicationModule/common/bc4j.xcfg"
MDS-00201: PDocument not found in MetadataStore : [store-type=DBMetadataStore app-name=HcmTalentApp(V2.0) repository-name=mds-ApplicationMDSDB partition-name=FAGlobal]
  at oracle.mds.core.MetadataObject.getBaseMO(MetadataObject.java:1446)
  at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:3852)
  at oracle.mds.core.MDSSession.getMutableMO(MDSSession.java:2080)
  at oracle.mds.core.MDSSession.getMutableMO(MDSSession.java:1991)
  at oracle.adf.share.jndi.MDSBackingStore.getMetadataObject(MDSBackingStore.java:465)
  at oracle.adf.share.jndi.MDSBackingStore.getMutableMetadataObject(MDSBackingStore.java:450)
  at oracle.adf.share.jndi.MDSBackingStore.obtainMetadataObject(MDSBackingStore.java:640)
  at oracle.adf.share.jndi.MDSBackingStore.getMOBean(MDSBackingStore.java:719)
  at oracle.bc4j.mbean.RuntimeMXBeanImpl.init(RuntimeMXBeanImpl.java:144)
  at oracle.bc4j.mbean.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:135)
  at oracle.bc4j.mbean.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:126)
  at oracle.bc4j.mbean.BC4JConfigLifeCycleCallBack.contextInitialized(BC4JConfigLifeCycleCallBack.java:160)
  at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
  at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
  at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
  at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3164)
  at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)
  at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:489)
  at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
  at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
  at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
  at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
  at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
  at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
  at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
  at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
  at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
  at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
  at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:187)
  at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:379)
  at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
  at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
  at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
  at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
  at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:246)
  at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
  at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
  at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
  at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)


Solution:

Bouncing the managed server "TalentManagementServer" in HCM Domain solves this error.

*****************************Thanks***************************

Fusion Application 11.1.8 Tasklist and Workflow error on homepage

Error Message:

Error showing tasklist. Possible reasons could be : 1. SOA server connection information is not available. 2. If it is run in federated mode, the default server may be down..

Solution:

Please make sure all the admin and managed servers for the installed fusion applications are up and running.

If everything is working fine then please check the SOA managed server logs for each domain installed.

********************************Any queries please write***************************

Note - For physical or virtual installation of fusion applications at your end for learning and training purpose only please contact us at
info@orainstall.com

Fusion Apps Installation 11.1.8


Oracle Fusion Applications Installation High Level Steps for 11.1.8

We have used following configuration for our installation on physical server with 188 GB RAM and 1 TB hard disk.

Server 1 - Node 1
Hostname: idmserver
OS: Oracle Linux x86-64
Disk size: 300 GB
Memory: Minimum 8+ GB (Recommended 16+ GB)
Server 1 - Node 2
Hostname: faserver
OS: Oracle Linux x86-64
Disk size: 500 GB
Memory:
  1. For single product (except Financials, CRM or SCM) : Minimum 64+ GB (Recommended 96+ GB)
  2. For Financials or CRM or SCM: Minimum 88+ GB (Recommended 128 GB)
  3. For all products selected: Minimum 144+ GB

Fusion Application Installations can be largely divided into following steps.
Preparing for Oracle Fusion Applications installation
1. Downloading Oracle Fusion Applications media from www.oracle.edelivery.com
2. Creating Oracle Fusion Applications provisioning repository / Staging directories
3. Installing OS (here Oracle Linux x86-64) on physical machine or Virtual machine. 
Steps - Installing Oracle Fusion Applications 
Below are the steps that need to installed in order while selecting the options installing Fusion Apps. 
Please refer oracle website for detailed steps or any blog.
A. Setting up Identity and Access Management Node
B. Setting up Fusion Applications Node

Note - For physical or virtual installation of fusion applications at your end for learning and training purpose only please contact us at
info@orainstall.com