OPatch apply & rollback

1.Stop all services...on both APPS & DB node.......

2.export PATH=$ORACLE_HOME/OPatch

3.Above is mandatory...Before applying patch check PATH should points to opatch directory location.....

4.opatch lsinventory -invPtrLoc /u01/app/oracle/db/tech_st/11.1.0/oraInst.loc |grep 8940108(patch number)

Above command shows whether the patch is applied or not.

5.unzip the patch...

6.shutdown the database...

7.goto patch directory location.....

8.fire the below command to apply the patch....(go to patch directory)

opatch apply -invPtrLoc /u01/app/oracle/db/tech_st/11.1.0/oraInst.loc.

Once the patch is applied successfully on database...

Startup the database....

Start the services

Patch is already … Download the new version of patch rollback patch and apply new version patch:

Oracle_home/inventory/oneoffs/<patch_no>/  opatch rollback  –id <pch_no> -invPtrLoc /u01/app/oracle/db/tech_st/11.1.0/oraInst.loc

---------------------------------------------------------------------------> ManjunathaReddy

To create inventory

./runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/u01/app/oracle/db/tech_st/11.1.0" ORACLE_HOME_NAME="oracleHome" CLUSTER_NODES="{}"

Foms compilation 11i & R12...

11i:

$APPL_tOP/apps/ora/8.0.6/bin/f60gen module=/appltop/apps/au/11.5.0/forms/US/ INVSDOIO.fmb userid=APPS/apps output_file=/appltop/apps/fnd/11.5.0/forms/US/ INVSDOIO.fmx  module_type=form batch=yes compile_all=special

cd $AU_TOP/forms/US
ls -ltr INVSDOIO.fmb
FORMS60_PATH=$AU_TOP/resource:$AU_TOP/forms/US
export FORMS60_PATH
f60gen Module=INVSDOIO.fmb Userid=apps/apps Output_file=INVSDOIO.fmx Debug=Yes Module_type=FORM

--------------

Module type =pll

f60gen module=PNSULOCN.pll module_type=library compile_all=Yes userid=apps/apps@DRTSTB | tee ~/PNSULOCN.log

Module type = form

f60gen module=INVSDOIO.fmb module_type=form compile_all=Yes userid=apps/apps@DRTSTB | tee ~/INVSDOIO.log

----------------------------------------------------------

R12:
frmcmp_batch WMSLABEL.fmb userid=APPS/<apps-password> output_file=/u01/app/oracle/apps/apps_st/appl/wms/12.0.0/forms/US/WMSLABEL.fmx module_type=form compile_all=special

Ho to Create adpatch defaultsfile :

How to apply patches in future ?

adpatch defaultsfile=$APPL_TOP/admin/$TWO_TASK/defaults.txt

Now any future patches you apply non interactive using defaults file like

adpatch defaultsfile=$APPL_TOP/admin/$TWO_TASK/defaults.txt logfile=6241631.log patchtop=/nfs/patches/6241631 driver=u6241631.drv interactive=no

adpatch Non-Interactive mode
               [defaultsfile=<$APPL_TOP/admin/SID/defaultsfile>]
               [logfile=<logfile>][interactive=y|n][workers=<workers>]
               [patchtop=<patchtop>][driver=<driver_file>][restart=y|n]
               [abandon=y|n][wait_on_failed_job=y|n][stdin=y|n]
               [maxworkers=<maxworkers>]

Note:

help=y      - Prints help information about adpatch options.
* preinstall  - To run adpatch in Pre-Install Mode.   Default - No.

* apply       - To run adpatch in Test Mode.          Default - Yes.

* uploadph    - To upload the patch history from the filesystem to the
                database and exit. This feature can be used when the system
                is not in maintenance mode.    Default - No.

* interactive - Invokes adpatch in Non-Interactive mode when
               "interactive=no" is specified.       Default - Yes.

Following are usually specified in Non-Interactive Mode, however not all

  are compulsory. Some are also valid for interactive mode.

    * defaultsfile         - Defaults file name. Default - none. No default file read or written.

    * stdin            - If "stdin=y" then password will be prompted.   Default - No.

    * logfile          - Adpatch log file name. Default - none. Adpatch prompts for this value.

    * workers       - Specifies the number of workers to run. Default - none. Adpatch prompts for this value.

    * maxworkers           - Specifies the maximum number of workers allowed to run.

                             Default - computed dynamically based on database parameters.

    * patchtop             - Top-level directory for the current patch.

                             Default - none. Adpatch prompts for this value.

    * driver               - Name of the patch driver file.

                             Default - none. Adpatch prompts for this value.

    * backup           - Absolute Path for backup. Default - patchtop.

    * restart            To restart an existing session.   Default - none. Adpatch prompts for this value.

    * abandon         To abandon the previous failed session.   Default - No.

    * wait_on_failed_job   - To prevent adpatch from exiting, when all

                             workers have failed in Non-Interactive Mode.  Default - No.

adpatch help=y

options = Generic options passed to adpatch.

checkfile,compiledb,compilejsp,copyportion,databaseportion,generateportion,integrity,parallel,prereq,validate,hotpatch & maintenancemode 

Mobile Application Services in Oracle Apps R12

Login as applmgr user :
Go to $ADMIN_SCRIPTS_HOME

Stop Mobile Application Services :

./mwactl.sh -login apps/apps_password stop_force
./mwactlwrpr.sh stop apps/apps_password

Start Mobile Application Services :

./mwactl.sh -login apps/apps_password start
./mwactlwrpr.sh start apps/apps_password

Check Mobile Services are up and Runing:

ps -ef | grep mwa

Find port Number of Mobile Services :

grep mwa $CONTEXT_FILE

Connect to Mobile Services :
telnet hostname.domainname portnumber(mobile application service port_number)
++++++++++++++++++++++++++++++++++++

Hot to configure Mobile applications on EBS – 11i

++++++++++++++++++++++++++++++++++++

1. Stop the current servers.

a. $ cd $MWA_TOP/bin

b. $ nohup mwactl.sh -login SYSADMIN/sysadmin1 stop 10260

    $ netstat -na  | grep 10260

c. $ ./mwactl.sh stop_dispatcher

2. Verify that MWA servers are stopped.

a. $ ps -ef | grep mwa

b. No processes should be found.

3. Locate the mwa.cfg file in the $MWA_TOP/secure directory.

4. Edit the mwa.cfg file and configure following parameters

a. Set mwa.DbcFolder=full directory of folder containing the .dbc file ending with “/”:

mwa.DbcFolder=/d01/oracle/SVRSUPTappl/fnd/11.5.0/secure/SVRSUPT_svrsuptsql1

b. Set mwa.DbcFile=dbc file name with extension:

mwa.DbcFile=SVRSUPT

c. Set mwa.logdir=full directory of log file without the trailing “/”:

mwa.logdir=/d01/oracle/SVRSUPTcomn/admin/log/SVRSUPT_svrsuptsql1

d. Set mwa.LogLevel=error or trace:

mwa.LogLevel=error

e. Set mwa.TelnetPortNumber=port number

mwa.TelnetPortNumber=10240

f. Set mwa.DropConnectionTimeout= no. of minutes:

mwa.DropConnectionTimeout=5

g. Set mwa.StaleSessionTimeout= no. of minutes:

mwa.StaleSessionTimeout=60

h. Specify the port number and machine for running the dispatcher:

mwa.Dispatcher=svrsuptsql1.d-rco.com:10328

i. Specify the server manager telnet server information

mwa.TelnetServer=svrsuptsql1.d-rco.com:10260;10262

5. Start the MWA telnet servers

a. $ cd $MWA_TOP/bin

b. $ nohup ./mwactl.sh start 10260 &

6. Start the dispatcher

a. $ nohup ./mwactl.sh start_dispatcher &

++++++++++++++++++++++++++++++++

how to check it is working or not:
Start  à  Run à cmd à telnet hostame:portnumber  ß press enter  , it will show 4 options select , appropriate option & give username & password.

++++++++++++++++++++++++++++++++

ID 1393369.1 , 782162.1 & 269991.1

Target node/queue unavailable or Concurrent Manager Issue’s after cloning or DB-Refresh

Target node/queue unavailable or Concurrent Manager Issue’s after cloning or DB-Refresh

Concurrent Processing - After Cloning All the Concurrent Managers Do Not Start for the Clone [ID 555081.1]

Conflict Resolution Manager Shows Target Node/Queue Unavailable [ID 732709.1]

Concurrent Managers Do Not Start After Cloning Nodes Not Updated In Conc_queues [ID 466532.1]

EXEC FND_CONC_CLONE.TARGET_CLEAN;

Run autoconfig on dbtier then appsTier.

Run cmclean.sql script  Non destructive script this can also be tried-->>

Start all application services and check whether managers are up.

Apply this solution in last when the above one doesnt work.

select node_name,target_node,control_code from fnd_concurrent_queues;

update apps.fnd_concurrent_queues set node_name = 'Node NAME' where node_name='Existing Node Name'; 

select NODE_NAME,NODE_MODE,STATUS from fnd_nodes;

desc fnd_concurrent_queues

select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;

UPDATE fnd_concurrent_queues set control_code = null;

UPDATE fnd_concurrent_queues set target_node = 'Node Name';

UPDATE fnd_concurrent_queues set node_name = 'Node Name';

update FND_CONCURRENT_QUEUES set control_code = null where concurrent_queue_name = 'OAMGCS_NODENAME'; -- supply the node name..(Ur Existing Node Name)

Commit;

select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;