Tuesday, August 18, 2009

RMAN backup failed with ORA-01031: insufficient privileges

Early morning I got email from unix team with given below error message.

Error Message

opyright (c) 1982, 2007, Oracle. All rights reserved.

 

RMAN> connect target system/********

 

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

ORA-01031: insufficient privileges

 

RMAN> quit

 

Issue Identification

I noticed 10.2.0.3 RDBSM $ORACLE_HOME/bin/oracle file permission was as given below.

$ ls -l $ORACLE_HOME/bin/oracle

-rwxrwxr-x 1 orastg oinstall 134741371 May 22 17:03 oracle

 

Resolution

  1. I changed oracle executable permission as given below.

    $ chmod 6751 $ORACLE_HOME/bin/oracle

    $ ls -l $ORACLE_HOME/bin/oracle

    -rwsr-s--x 1 orastg oinstall 134741371 May 22 17:03 $ORACLE_HOME/bin/oracle

  2. I tried to connect system user as sysdba and it failed so I had to grant sysdba, sysoper to system user as given below.

    $sqlplus system/*****@JAI as sysdba

     

    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Aug 18 09:47:49 2009

     

    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

     

    ERROR:

    ORA-01031: insufficient privileges

     

    SQL> connect / as sysdba

    Connected.

    SQL> grant sysdba, sysoper to system;

    $sqlplus system/******@JAI as sysdba

    SQL*Plus: Release 10.1.0.5.0 - Production on Tue Aug 18 09:51:34 2009

    Copyright (c) 1982, 2005, Oracle. All rights reserved.

     

    Connected to:

    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

    With the Partitioning, OLAP, Data Mining Scoring Engine and Real Application Testing options

     

    SQL>

Oracle Applications 11i Clone SSO Registration

We had cloned Oracle Apps development instance JAID from production instance JAIP. After clone completion we had to deregister SSO integration with Production SSO (10giAs) server and register with development SSO (10giAS server).

Login to oracle applications middle tier and perform given below activities.

  1. Deregister SSO (Reference to Production SSO server)

    $txkrun.pl -script=SetSSOReg -deregistersso=Yes -appspass=<apps password> -orassopass=<orassop password of SSO production server> -ssosdkpass=<ssosdk password of apps, default ssosdk>

    Checking preferences in the database.

    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_12_08_2009.log

    Program : /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Tue Aug 18 14:12:12 2009

     

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_12_08_2009.log

     

    Beginning input parameter validation for SSO de-registration.

    Input parameters validation for SSO de-registration completed.

     

    BEGIN SSO DE-REGISTRATION:

     

    Partner application not found to be removed.

    End of /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered

     

  2. Deregister OID (Reference to Production SSO server)

    $txkrun.pl -script=SetSSOReg -deregisteroid=Yes -appspass=<apps password> orcladminpass=<orcladmin password of production SSO>

    Checking preferences in the database.

    Enter the Oracle Internet Directory Administrator (orcladmin) Bind password ? ss0p1dminusr

    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_13_38_2009.log

    Program : /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Tue Aug 18 14:13:57 2009

     

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_13_38_2009.log

     

    Beginning input parameter validation for OID de-registration.

    Following is the number of user subscriptions found to be deleted : 5904

     

    ******************************** WARNING **********************************

     

    For better performance it is advisable to use bulk delete utility as

    described in Oracle Internet Directory Administrator's Guide, before

    continuing with the de-registration.

    This script will delete the subscriptions one at a time. Depending upon number of

    subscriptions, this action might take a long time but you can watch the progress

    in the log file in another terminal window.

     

    ******************************** WARNING **********************************

     

    Do you want to continue <Y/N> ? Y

    Input parameters validation for OID de-registration completed.

     

    BEGIN OID DE-REGISTRATION:

     

    No dangling provisioning profiles found.

    Beginning to delete provisioning profile for this application.

    Provisioning profile for this application has been deleted successfully.

    Following is the number of user subscriptions found to be deleted : 5904

     

    USER SUBSCRIPTION DELETE LOG FILE : /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/usrDelSubs_Tue_Aug_18_14_13_38_2009.out

     

    All user subscriptions have been deleted successfully.

    Beginning to de-register this application from Oracle Internet Directory.

    This application has been de-registered successfully from Oracle Internet Directory.

    End of /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered

     

  3. Register SSO (New Reference to Development SSO server)

    $txkrun.pl -script=SetSSOReg -registersso=Yes -appspass=network1 -infradbhost=ios10901e.idc.ikon.org -infradbport=1510 -infradbsid=SSOD -orassopass=N16FKR0g -systempass=network1 -ssosdkpass=ssosdk

    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_28_52_2009.log

    Program : /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Tue Aug 18 14:28:53 2009

     

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_28_52_2009.log

     

    ######################## WARNING ########################################

    This application works with SSOSDK version 9.0.2 or higher. If lower version

    (3.0.9) of SSOSDK was installed in your system and you have a registered

    partner application, this process will remove the 3.0.9 version of the SSOSDK

    schema and install the 9.0.2 version.

    ######################## WARNING ########################################

    Beginning input parameter validation for SSO registration.

    Beginning loading SSO SDK into database if necessary.

    Loading of SSO SDK into database is not required.

    Input parameter validation for SSO registration completed.

     

    BEGIN SSO REGISTRATION:

     

    Beginning to register partner application.

    Partner application has been registered successfully.

    Single Sign-On partner application registered successfully.

     

  4. Register to OID (New Reference to Development SSO server)

    $ txkrun.pl -script=SetSSOReg \

    > -provtmp=$FND_TOP/admin/template/ProvOIDToApps.tmp \

    > -registeroid=Yes \

    > -appspass=<appspassword> \

    > -infradbhost=ios10901e.idc.ikon.org \

    > -orcladminpass=<orcladmin password> \

    > -instpass=<instance registeration password> \

    > -ldapport=3030 \

    > -appname="JAID" \

    > -svcname="JAID"

    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_30_13_2009.log

    Program : /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Tue Aug 18 14:30:13 2009

     

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_30_13_2009.log

     

    Beginning input parameter validation for OID registration.

     

    Registration failed with given below error.

    Oid Registration Fails With "Can not register a service which is already registered"

     

    I had to deregister and reregister again.

     

    Reference :

    Subject: Oid Registration Fails With "Can not register a service which is already registered"

    Doc ID: 565246.1

     

    $ txkrun.pl -script=SetSSOReg -deregister=Yes

    Enter Oracle E-Business apps database user password ? ******            ß apps password

    Checking preferences in the database.

    Enter Oracle iAS Infrastructure database ORASSO schema password ? ******    ß Development orasso schema password

    Enter E-Business Suite SSOSDK schema password ? SSOSDK

    Enter the application name used for registration of this application instance in OID ( 24 chars or less ) ? JAID        ß Instance_Name

    Enter the descriptive service name used for registration of this application instance in OID ( 80 chars or less ) ? JAID    ß Service Name

    Enter the LDAP Port on Oracle Internet Directory server ? 3030                                ß Port

    Enter the Oracle Internet Directory Administrator (orcladmin) Bind password ? *******                    ß orcladmin password

    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_59_14_2009.log

    Program : /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Tue Aug 18 15:00:35 2009

     

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_14_59_14_2009.log

     

    Beginning input parameter validation for SSO de-registration.

    Input parameters validation for SSO de-registration completed.

    Beginning input parameter validation for OID de-registration.

    Following is the number of user subscriptions found to be deleted : 1352

     

    ******************************** WARNING **********************************

     

    For better performance it is advisable to use bulk delete utility as

    described in Oracle Internet Directory Administrator's Guide, before

    continuing with the de-registration.

    This script will delete the subscriptions one at a time. Depending upon number of

    subscriptions, this action might take a long time but you can watch the progress

    in the log file in another terminal window.

     

    ******************************** WARNING **********************************

     

    Do you want to continue <Y/N> ? Y

    Input parameters validation for OID de-registration completed.

     

    BEGIN SSO DE-REGISTRATION:

     

    Partner application found and will be removed.

    Partner application has been removed successfully.

     

    BEGIN OID DE-REGISTRATION:

     

    No dangling provisioning profiles found.

    Beginning to delete provisioning profile for this application.

    Provisioning profile for this application has been deleted successfully.

    Following is the number of user subscriptions found to be deleted : 1352

     

    USER SUBSCRIPTION DELETE LOG FILE : /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/usrDelSubs_Tue_Aug_18_14_59_14_2009.out

    All user subscriptions have been deleted successfully.

    Beginning to de-register this application from Oracle Internet Directory.

    This application has been de-registered successfully from Oracle Internet Directory.

    End of /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered

     

    Registered Again SSO

     

    $ txkrun.pl -script=SetSSOReg -registersso=Yes -appspass=***** -infradbhost=ios10901e.idc.ikon.org -infradbport=1510 -infradbsid=SSOD -orassopass=****** -systempass=***** -ssosdkpass=*****

     

    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_15_02_47_2009.log

    Program : /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Tue Aug 18 15:02:47 2009

     

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_15_02_47_2009.log

     

    ######################## WARNING ########################################

    This application works with SSOSDK version 9.0.2 or higher. If lower version

    (3.0.9) of SSOSDK was installed in your system and you have a registered

    partner application, this process will remove the 3.0.9 version of the SSOSDK

    schema and install the 9.0.2 version.

    ######################## WARNING ########################################

    Beginning input parameter validation for SSO registration.

    Beginning loading SSO SDK into database if necessary.

    Loading of SSO SDK into database is not required.

    Input parameter validation for SSO registration completed.

     

    BEGIN SSO REGISTRATION:

     

    Beginning to register partner application.

    Partner application has been registered successfully.

    Single Sign-On partner application registered successfully.

     

    End of /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered

     

    Registered Again OID

    $ txkrun.pl -script=SetSSOReg \

    > -provtmp=$FND_TOP/admin/template/ProvOIDToApps.tmp \        ß Provision template from OID to Apps Only

    > -registeroid=Yes \

    > -appspass=network1 \                            ß Apps password

    > -infradbhost=ios10901e.idc.ikon.org \                    ß OID infrastructure host

    > -orcladminpass=ssodpoc123 \                        ß orcladmin password

    > -instpass=welcome123 \                            ß Registration Password

    > -ldapport=3030 \                                ß OID Port

    > -appname="JAID" \                            ß Application Name

    > -svcname="JAID"                            ß Service Name

    *** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_15_03_25_2009.log

    Program : /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl started @ Tue Aug 18 15:03:25 2009

     

    *** Log File = /opt11/app/jaidcomn/rgf/JAID_osijaid/sso/txkSetSSOReg_Tue_Aug_18_15_03_25_2009.log

     

    Beginning input parameter validation for OID registration.

    Input parameters validation for OID registration completed.

     

    BEGIN OID REGISTRATION:

     

    Beginning to register Application and Service containers if necessary.

    Application and Service containers were found and thus not created.

    Beginning to register application in Oracle Internet Directory.

    Registration of application in Oracle Internet Directory completed successfully.

    Beginning to register instance password in Oracle Internet Directory.

    Registration of instance password in Oracle Internet Directory completed successfully.

    Beginning to test application registration in Oracle Internet Directory.

    Testing of application registration in Oracle Internet Directory completed successfully.

    Beginning to register provisioning profile in Oracle Internet Directory.

    Registration of provisioning profile in Oracle Internet Directory completed successfully.

    Application is now registered successfully with provisioning in Oracle Internet Directory.

    End of /opt01/app/jaidappl/fnd/11.5.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered

     

  5. Perform validationLogin to 11i environment and navigate to screens listed below to perform validation.

    http://<>URL>/OA_HTML/jtflogin.jsp è diagnostic è "Application Object Library" è "SSO Setup Test".

     

    Status for following component should be "SUCCEED"

     

    SSO SDK Version and Files     

    ATG SSO File Versions 

    SSO Settings 

     

  6. Make sure given below system profile should be set as given below.

    Profile                        Value

    Application SSO LDAP Synchronization         enabled

    Applications SSO Auto Link User            enabled

    Applications SSO Enable OID Identity Add Event        enabled

    Applications SSO Login Types                SSO (SYSADMIN and GUEST should be LOCAL)

    Applications SSO Type                Sswa w/sso

    Applications SSO Linking Source of Truth        Oracle internet directory

     

  7. I tried to login to application using SSO login using given below link and it prompted for user id and password. This was expected behavior. As I mentioned support apps instance was cloned from production so APPS. USER_GUID value was from Production integrations. In order to make Development apps instance (JAID) integrated with SSO development server. I heed to nullify USER_GUID value so at runtime it can update value.

    http://URL/oa_servlets/AppsLogin

     

    $sqlplus apps/<password>

    SQL>create table apps.fnd_user_bkp as select * from apps.fnd_user;

    SQL>update apps.fnd_user set user_guid=null where user_name not in

    (

    'APPSMGR',

    'AUTOINSTALL',

    'CR_SCHEDULER',

    'GUEST',

    'IBE_GUEST',

    'PORTAL30',

    'PORTAL30_SSO',

    'SYSADMIN',

    'OP_CUST_CARE_ADMIN',

    'OP_SYSADMIN',

    'SYSADMIN',

    'WIZARD',

    'ANONYMOUS',

    'AUTOINSTALL',

    'CONCURRENT MANAGER',

    )

     

  8. After above update I again tried to login to applications using given below URL and I could login to oracle applications.

    http://URL/oa_servlets/AppsLogin

Saturday, August 1, 2009

Oracle Applications MWA Configuration

Due to busy scheduled I could not post any update yesterday. Last year we implemented oracle MWA (Mobile) in our company. Oracle mobile application is being used in warehouse to keep track of goods. Following are steps I performed as oracle applications DBA.

Apply MWA patches

  1. Stop Oracle Applications Services (Apache, Forms, Concurrent Manager, Report Server).

[orajai1@jai0301e] /home/orajai1

Source Oracle apps environment

$ . $APPL_TOP/$CONTEXT_NAME.env

$cd $COMMON_TOP/admin/scripts/$CONTEXT_NAME

$ adstpall.sh stop apps/<password> (Only on concurrent manager node)

  1. Take name and number of invalid objects belongs to apps, mwa, inv schema.

    SQL> SELECT COUNT(1) FROM DBA_OBJECTS WHERE status='INVALID' AND OWNER='APPS'

Export Invalid objects name in excel sheet, to compare invalid objects after apply these patches in case of any issue.

SELECT object_name, object_type, owner, status FROM dba_objects WHERE status = 'INVALID' AND owner = 'APPS' ORDER BY 1, 2, 3

  1. Take backup of following directories on all applications tier (web/form as well concurrent manager).

$cp $FND_TOP/secure $FND_TOP/secure.<mmddyyyy>

$cp $TNS_ADMIN/$CONTEXT_NAME $TNS_ADMIN/$CONTEXT_NAME.<mmddyyyy>

$cp $IAS_ORACLE_HOME/network/admin/$CONTEXT_NAME $IAS_ORACLE_HOME/network/admin/$CONTEXT_NAME.<mmddyyyy>

  1. Apply following MWA Patches using /staging/scripts/ikn_autopatch.sh script.

Noteà Sometime file version would be updated after running autoconfig. Autoconfig you need to run at end of installation of all patches. You need to make sure about file version using adident after running autoconfig.

# 4260471 Mobile Applications Telnet Screen is rendere

Duration : 30 Min

Check file version after patch installation

$ adident Header $MWA_TOP/bin/MWADIS

/opt01/app/jai1appl/mwa/11.5.0/bin/MWADIS:

$Header mwadis.oc 115.158.1159.5 2005/03/28 18:49:15 sthamman noship $

$Header mwacfg.lc 115.24.1159.2 2004/12/31 10:38:20 sthamman noship

$ adident Header $MWA_TOP/admin/template/mwactl.sh

/opt01/app/jai1appl/mwa/11.5.0/admin/template/mwactl.sh:

$Header mwactl.sh 115.53.1159.3 2004/11/17 10:03:19 sthamman ship

# 4577556 Mandatory Mobile Patch for 1159 Customer

Duration: 30

Check file version after patch installation

$cd $COMMON_TOP/java/oracle/apps/mwa/presentation/telnet

$ adident Header Options.class

Options.class:

$Header Options.java 115.17.1159.9 2005/09/30 04:12:05 ajohnson ship $

$ adident Header ProtocolHandler.class

ProtocolHandler.class:

$Header ProtocolHandler.java 115.133.1159.8 2005/05/18 13:32:12 ajohnson ship

# 4630366 Mandatory Mobile Patch for 1159 Customer

Duration 30 Min

$cd $COMMON_TOP/java/oracle/apps/mwa/presentation/telnet

$ adident Header Options.class

Options.class:

$Header Options.java 115.17.1159.9 2005/09/30 04:12:05 ajohnson ship

# 3869946 MOBILE PAGES FAILED TO OPEN

Duration 60 min

Check file version

$ adident Header $WMS_TOP/patch/115/import/US/wmsmenu.ldt

/opt01/app/jai1appl/wms/11.5.0/patch/115/import/US/wmsmenu.ldt:

$Header wmsmenu.ldt 115.29.11590.5 2004/09/16 19:13:01 htnguyen ship $

$ adident Header $FND_TOP/patch/115/sql/AFFMFUNB.pls

/opt01/app/jai1appl/fnd/11.5.0/patch/115/sql/AFFMFUNB.pls:

$Header AFFMFUNB.pls 115.36 2005/04/11 13:50:03 skghosh ship $

# 4345239 STOCK LOCATOR ISSUE IN THE SUB TRANSFER SCREEN

Duration 60 min

Check file version

$ adident Header $INV_TOP/patch/115/sql/INVITPSB.pls

/opt01/app/jai1appl/inv/11.5.0/patch/115/sql/INVITPSB.pls:

$Header INVITPSB.pls 115.108.11590.8 2005/05/27 16:07:52 mchemban ship $

$ adident Header $INV_TOP/patch/115/sql/INVLKFFB.pls

/opt01/app/jai1appl/inv/11.5.0/patch/115/sql/INVLKFFB.pls:

$Header INVLKFFB.pls 115.1.11590.3 2005/05/27 15:57:27 mchemban ship $

$ adident Header $INV_TOP/patch/115/sql/INVLKFFS.pls

/opt01/app/jai1appl/inv/11.5.0/patch/115/sql/INVLKFFS.pls:

$Header INVLKFFS.pls 115.1.11590.2 2005/05/27 15:46:14 mchemban ship $

$ adident Header $INV_TOP/patch/115/import/US/i4345239.ldt

/opt01/app/jai1appl/inv/11.5.0/patch/115/import/US/i4345239.ldt:

$Header i4345239.ldt 115.0 2005/05/27 15:33:22 mchemban noship $

  1. Compile all invalid objects and check if there is any new invalid objects.
  2. Check invalid object of INV and MWA schema and compile them manually if it is taking long
  3. We need to check MWA related configuration in auto context file on each middle tier , concurrent manager tier before running autoconfig.
  4. Make following changes in applications context file on each middle and concurrent manager tier and run autoconfig.

    <oa_mwa_server>

    <hostname oa_var="s_mwahost">jai0301e</hostname>

    <domain oa_var="s_mwadomain">orbit.com</domain>

    <mwaLogLevel oa_var="s_mwaLogLevel">error</mwaLogLevel>

    <mwaLogRotate oa_var="s_mwaLogRotate">Yes</mwaLogRotate>

    <mwaLogFileSize oa_var="s_mwaLogFileSize">10000000</mwaLogFileSize>

    <mwaDropConnectionTimeoutoa_var="s_mwaDropConnectionTimeout">5</mwaDropConnectionTimeout>

    <mwaStaleSessionTimeoutoa_var="s_mwaStaleSessionTimeout">60</mwaStaleSessionTimeout>

    <mwaDispatcherThreadCountoa_var="s_mwaDispatcherThreadCount">15</mwaDispatcherThreadCount>

    <mwaDispatcherClientsPerWorkeroa_var="s_mwaDispatcherClientsPerWorker">10</mwaDispatcherClientsPerWorker>

    <mwaJVMb oa_var="s_mwaJVMb">FALSE</mwaJVMb>

    <mwaPortNo oa_var="s_mwaPortNo" oa_type="PORT">10210</mwaPortNo>

    <mwaTelnetPortNo oa_var="s_mwaTelnetPortNo" oa_type="PORT">10200</mwaTelnetPortNo>

    <mwaDispatcherPort oa_var="s_mwaDispatcherPort"oa_type="PORT">10310</mwaDispatcherPort>

    <mwaActivateLOVByEnter oa_var="s_mwaActivateLOVByEnter">FALSE</mwaActivateLOVByEnter>

    <mwaSubmenuChangeOrgResp oa_var="s_mwaSubmenuChangeOrgResp">FALSE</mwaSubmenuChangeOrgResp>

    </oa_mwa_server>

    Check value for following tag in the application context file $APPL_TOP/admin/<SID>_<HOSTNAME>.xml. Value for these port would be decided for production. We'll use last two digit of mwaPortNo same as last two digit of Apache Port.

    e.g.

    if Production port is 8010 then mwaPortNo would be 10210 and Dispatcher port 10310

    <mwaPortNo oa_var="s_mwaPortNo" oa_type="PORT">10210</mwaPortNo>

    mwa.Dispatcher=%s_hostname%.%s_domainname%:%s_mwaDispatcherPort%

    mwa.TelnetServer=%s_hostname%.%s_domainname%:%s_mwaPortNo%

    Make sure Dispatcher and Telnet Server hostname is as per production requirement.

  5. Run autoconfig on all web/concurrent manager tier.

$cd $SCRIPTS

$ pwd

/opt01/app/oracle/jai1comn/admin/scripts/JAI1_jai0301e

$adautocfg.sh

Enter apps password : *****

Check autoconfig log on each tier (middle tier, concurrent manager tier).

  1. Run /staging/scripts/ikn_post_autoconf.sh on each node.

Run ikn_post_autoconf.sh on both jai00108e and jai00208e.

$cd /staging/scripts

./ikn_post_autoconf.sh ERMR_jai0108e ERMR ERMR1PPSSYS eierm

  1. Copy back the listener.ora and tnsnames.ora files from backup in 806 home and IAS home.
  2. Check the DBC files in $FND_TOP/secure and add given entry if not there.

    BATCH_VALIDATE_USER=GUEST

    BATCH_VALIDATE_PWD=ORACLE

    Make sure DBC file exists.

    -rwxr-xr-x 1 orajai1 dba 806 Feb 08 11:00 jai001_jai1.dbc

  3. Start applications services including concurrent manager.
  4. Email to Functional team to run given below "Concurrent Manager", which is part of post installation step of patch # 4345239 "Generate Stock Locator Flexfield definition for Mobile transactions"
  5. Compile invalid objects if there was any due to above concurrent program.
  6. Validate applications services

Configure MWA

We are going to use only MWA server for time being. Ensure mwa related

setting are part of configuration file. Please perform as given below.

  1. Make given changes in $MWA_TOP/secure/mwa.cfg file.

mwa.logdir= /log01/JAI1/mwa

Rest of given below mwa related settings are part of autocontext file. Please cross check values for given variables in the $MWA_TOP/secure/mwa.cfg file

File : $MWA_TOP/secure/mwa.cfg

Variable Values:

mwa.DbcFolder= /opt01/app/jai1appl/fnd/11.5.0/secure/

mwa.DbcFile= jai0301e_jai11

mwa.logdir= /log01/JAI1/mwa

mwa.TelnetPortNumber=10210

mwa.DropConnectionTimeout=5

mwa.StaleSessionTimeout=60

mwa.SystemLog=system.log

mwa.LogLevel=trace

Check Dispatcher setting

Dispatcher related setting variable's values are already part of autocontext file. Please check values for following dispatcher related variables in the $MWA_TOP/secure/mwa.cfg file.

[orajai1@jai0301e] /opt01/app/jai1appl/mwa/11.5.0/secure

$ grep -i Dispatcher mwa.cfg grep -v "#"

mwa.Dispatcher=jai0301e.orbit.com:10310

mwa.DispatcherWorkerThreadCount=15

mwa.DispatcherClientsPerWorker=10

Change Default_key Files

Please modify $MWA_TOP/default_key.ini file in JAI1 instance with following updates

The changes required to be done are in $MWA_TOP/default_key.ini

$ cp $MWA_TOP/default_key.ini $MWA_TOP/default_key.ini.mmddyyyy

1) Change DEFAULT_WIDTH = 27

2) Change DEFAULT_HEIGHT = 18

3) Change PROMPT_RATIO = 1:2

Performance Related Changes.

Execute following SQL using APPS schema

SQL> CREATE INDEX po.idx_rcv_tran_interface_prf1 ON po.rcv_transactions_interface

(shipment_header_id,transaction_status_code)

TABLESPACE pox COMPUTE STATISTICS ;

SQL> CREATE INDEX inv.idx_mtl_onhand_quan_det_prf1

ON inv.mtl_onhand_quantities_detail(lpn_id,organization_id)

TABLESPACE invx COMPUTE STATISTICS;

SQL> analyze table inv.MTL_SECONDARY_INVENTORIES delete statistics

SQL> CREATE INDEX wsh.idx_wsh_delivery_details_prf1 ON wsh.wsh_delivery_details

(source_header_number,released_status)

TABLESPACE wshx COMPUTE STATISTICS;

SQL> create index PO.idx_rcv_ship_headers_PRF1 ON PO.rcv_shipment_headers(EXPECTED_RECEIPT_DATE)

TABLESPACE POX COMPUTE STATISTICS;

Schedule Gather Schema Statistic for MWA

Login to Oracle Applications and select "SYSTEM ADMINISTRATOR" and Submit gather statistics

MWA Services Alert/Start/Stop Scripts

/home/orajai1/start_mwa

/home/orajai1/stop_mwa

/home/orajai1/stat_mwa

Start MWA Server

Ensure script mwa_services has been deployed in $HOME to start services.

Start mwa services using script

$. ./start_mwa

Validate MWA Configuration

After copying scripts run /home/orajai1/start_mwa script to start MWA services. Allocate following responsibility to any user and perform given steps to validate configurations.

"Materials & Mfg"

Start à Run à telnet jai0301e.orbit.com 10210

Noteà Only "Oracle Mobile Applications" repsonsbility would be visible in WMA telnet session.

Appendix

Start MWA services

$ cat start_mwa.sh

. $APPL_TOP/$CONTEXT_NAME.env

export WMATELPORT=10250 # WMA Tel Net Server Port

export WMATELPORT2=10260 # WMA Tel Net Server Port

ulimit -n 1024

echo "Starting the MWA Telnet Server ..."

cd $MWA_TOP/bin

nohup mwactl.sh -java_config "-mx128m -ms64m -Dmwa.cfg=$MWA_TOP/secure/$CONTEXT_NAME/mwa.cfg" start $WMATELPORT &

sleep 30

nohup mwactl.sh -java_config "-mx128m -ms64m -Dmwa.cfg=$MWA_TOP/secure/$CONTEXT_NAME/mwa.cfg" start $WMATELPORT2 &

sleep 30

if [ `ps -ef grep mwa grep -v grep wc -l` -eq 2 ]

then

echo "MWA Telnet Server is up now "

else

echo "WMA Telnet Server Did not start"

fi

cd

Stop MWA services

# You need instance sysadmin password to stop MWA server

. $APPL_TOP/$CONTEXT_NAME.env

export WMATELPORT=10250

export WMATELPORT2=10260

echo "Stoping the MWA Telnet Server ..."

cd $MWA_TOP/bin

mwactl.sh -java_config "-Dmwa.cfg=$MWA_TOP/secure/$CONTEXT_NAME/mwa.cfg" -mwatop $MWA_TOP -login SYSADMIN/<password> stop_force $WMATELPORT &

mwactl.sh -java_config "-Dmwa.cfg=$MWA_TOP/secure/$CONTEXT_NAME/mwa.cfg" -mwatop $MWA_TOP -login SYSADMIN/gone2acpt stop_force $WMATELPORT2 &

for i in `ps -ef grep mwa grep -v grep grep -v _mwa awk '{ print $2 }'`

do

kill -9 $i

done

echo "MWA Server and dispatcher is down ...."

cd

MWA Services availability Check

$ cat stat_mwa

# Description:This script will check mwa services and send notify DBAs if it was down.

# Author: Janmejai Singh

#

# History

##############################################

#! /bin/ksh

maillist="jsingh@orbit.com"

set -x

if [ -f /tmp/run_it.txt ]

then

exit

fi

if [ `ps -ef grep -i mwa grep -v grep grep -v stat_mwa wc -l` -ne 2 ]

then

echo "MWA Server is down on `hostname` ." mailx -s "Please start MWA Services using $HOME/start_mwa.sh script ..." $maillist

#echo "Please start MWA Services using `hostname` : $HOME/start_mwa script ..." mailx -s "MWA Server is down on `hostname` ." $maillist

fi