APPSINFODB – Information Technology Group

Finding Solutions for DBA's to smile…….!!!!!!! DBA its just not Administration, its core of customer’s data integrity

  • Blog Stats

    • 36,980 hits
  • Visitors

    free counters
  • Vistors Access

  • Calendar

    September 2017
    M T W T F S S
    « Dec    
     123
    45678910
    11121314151617
    18192021222324
    252627282930  
  • Archives

  • Authors

Archive for the ‘E-Business Suite 11i’ Category

Not able to cancel concurrent request & Unable to activate CM after cloning

Posted by appsinfo on August 20, 2012

Below are the two issues that I have faced after cloning from production

Q: How to terminate a concurrent request that cannot be cancelled

1.  Identify the request number to terminate.

2.  Shut down the concurrent managers and issue the following sql command as applsys:

            update fnd_concurrent_requests  set status_code = ‘E’, phase_code = ‘C’  where Request_id = <reqnum>; (reqnum = request number)

Q: A Manager is not activating.         

Check the count in sys.dual, system.dual, & apps.fnd_dual. There should only be one (1) row for each. 
If the count is greater, change to one only. This can be done from sqlplus as  follows:

    As user apps:
                   select * from SYS.DUAL;

    Any extra rows should be deleted.

                   delete rownum from SYS.DUAL; (rownum = the row number to delete)

    Any extra rows for apps.fnd_dual must be removed by performing the following SQL command:

                 delete from fnd_dual where rownum < (select max(rownum) from fnd_dual);

**For more on concurrent managers you can refer to FAQ (Concurrent Manager Unix specific Note ID: 105101.1)**

Advertisements

Posted in Cloning, E-Business Suite 11i, E-Business Suite R12, Troubleshooting | Tagged: | Leave a Comment »

Multi-Node Installation on Windows

Posted by appsinfo on September 1, 2009

Multi-Node Installation on Windows 2003 Server

In a multi-node installation, you install both application tier and database tier servers across two or more nodes. You use the Rapid Install wizard to collect and save the configuration values. To perform the installation, you run Rapid Install by pointing to the configuration (config.txt file). Then, you use the same configuration values to set up all the other nodes in the system.  

Navigate to the partition where stage area is created. (Presuming that partition to be G 🙂

 E:\> cd Stage11i\startCD\Disk1\rapidwiz

E:\Stage11i\startCD\Disk1\rapidwiz> rapidwiz.cmd 

Database Tier Node 1: 

  • Step 1: Choose an installation operation.
  • Step 2: Choose configuration/Installation Type. ( Multi node).
  • Step 3: Use Load Balancing (in our case do not enable load balancing).
  • Step 4: Assign servers to nodes and indicate operating system. (do not select shared application tier file system).
  • Step 5: Define Database type (Fresh Database) and specify the database name (PROD).
  • Step 6: Setup database installation directory.
  • Step 7: Select product license type.
  • Step 8: Select country specific functionality.
  • Step 9: Select additional languages (in our case we select Arabic).
  • Step 10: Select internationalization (NLS) settings.
  • Step 11: Enter node-specific information for “Install” nodes.
  • Step 12: Review global settings. (i.e. specify port pool from the list of port pools available).
  • Step 13: Save configuration file (i.e. config.txt).
  • Step 14: Review pre-installation checks.
  • Step 15: Begin the installation on first node (i.e. on Database tier).


Application Tier Node 2:

 Setting Up the Other Node (Application Tier)

 You have finished the configuration and setup of the first node where you installed the database — the first step in a multi-node installation.  Now, run Rapid Install on Application tier node  in your system using the same configuration file you used for the database node. You can set up additional nodes in any order. 

  • Copy the configuration file (config.txt) you saved at Database tier node to each of the Application tier nodes. 
  • On the application tier  nodes, start Rapid Install, and choose the Install Oracle Applications E-Business 11i option. Click Next to continue. 
  • Because you set up the parameters for all nodes when you first created the configuration file, Rapid Install goes directly to the pre-install test and begins the validation process.  
  • Review or resolve any issues flagged with ‘!’ or ‘x’ on the Pre-install Checks screen. If necessary, click Back to return to the appropriate screen(s) and make necessary changes. Save the config.txt file and then click Next to re-run the pre-install test. If there are no issues listed on the summary screen, click Next to continue. 
  • Click Next when each alert screen is displayed. Rapid Install begins the installation on this application tier node.
  • Once application installation is completed check the post-installation steps and login into the application to confirm successfull installation.

Posted in E-Business Suite 11i | Leave a Comment »

Splicing IZU TOP for Support Diagnostics

Posted by appsinfo on August 25, 2009

Splicing IZU TOP

For diagnostic patch you need to apply certain other patches and Splice IZU_TOP. Below are the steps that you need to follow while splicing the TOP.

1. Verify that the product is in the database or not

select APPLICATION_ID
       from fnd_application
       where APPLICATION_SHORT_NAME = ‘IZU’

2. 1. Copy the following text files from 3636980 to the admin directory under
   APPL_TOP.

        izuprod.txt
        izuterr.txt
        newprods.txt

Review newprods.txt and verify that the tablespaces listed exist
and are the ones planned for use by this product.
If changes are required, edit the file as appropriate and save it

3. Create tablespace

user_data
user_idx
apps_ts_tool—–create this table becoz this will throw an error
using adsplice

4. Run env and then adsplice

5. check
SQL> select APPLICATION_ID
  2         from fnd_application
  3         where APPLICATION_SHORT_NAME = ‘IZU’;

APPLICATION_ID
————–
           278

From within SQL*Plus, logged in as APPS, run the following:
        select STATUS
        from fnd_product_installations
        where APPLICATION_ID = 278;

   This statement should return one row:
   S
   –
   I
6. Set the IZU top in the evniornment file, echo and check the patch
7. Apply 3636980
8. Check the log files

9. Remove standalone RDA if installed into $IZU_TOP/bin/rda
   If you have previously installed RDA into the $IZU_TOP/bin/rda directory
   by manually extracting it from a zip or tar file, you should remove the rda
   directory and its contents from under $IZU_TOP/bin before applying the patch
   unified driver.

   Failure to do so could result in an adpatch error similar to this:

   Error: Applying rda.cmd to the wrong release:
    Patch  : /PATCH/7530017/izu/bin/rda/rda.cmd, v115.6
   On-Site: /u01/appltop/izu/11.5.0/bin/rda/rda.cmd, v1.4

10. Apply the following unified driver file with AutoPatch:
     u7530017.drv

11. Perform menu and/or responsibility setup as per Note 358831.1

Posted in Application 11i.x/12.x Patches, E-Business Suite 11i | Leave a Comment »

General Health Check for eBusiness Suite 11i

Posted by appsinfo on March 29, 2009

As part of patch application, configuration changes, releasing instances to functional users and during trouble shooting as Oracle Apps DBA / Sysadmin you need to perform proper health check of the components of your applications, Here is the list of components you should check as part from your custom services.  

  • Check Database instance availability
  • Login to Application
  • Check Web Server
  • Check Jserv
  • Check mod_pls
  • Check Form Server
  • Check Concurrent Manager
  • Check Reports display
  • Check Apps Listener
  • Check if Workflow
  • Check if Discoverer 4i
  • Custom applications

 

Posted in E-Business Suite 11i | Leave a Comment »

System Requirement for EBS 11.5.10.2 on Windows 2003

Posted by appsinfo on March 1, 2009

Requirement Gathering

 Before you begin the installtion at client place you need to collect the requirements of servers, networks, architecture, liciencing and there backup strategy. Once you are done with all these you can begin installation. Usually at some client locations you can experience that architecture, their network setup can be changed.

 Verify system requirements

 1.       Check memory, swap and temp space

2.       Verify OS version and patch levels

3.       Verify package requirements  

 Pre-installation Setup

 1.       Verify/add Oracle and database mount points

2.       Create Oracle groups

3.       Create Oracle user account

4.       Set Oracle user environment

5.       Assign Oracle User to Administrator group(Local) and as Domain User

 Pre-Installation (E-Business Suite 11.5.10.2)

 1.       Install Microsoft Visual C++ 6.0

2.       Apply Visual C++ Service pack 5 or Higher

3.       Install MKS Tool kit 8.0

4.       Install and Configure GNUMAKE 3.77 

Install E-Business Suite 11.5.10.2

 1.       Run rapidwiz as Oracle user

2.       Remember to select NLS as Arabic

3.       Follow necessary mount point locations for Database Tier and Application Tier. 

Post Installation

1.       Maintain Multi-Lingual tables.

2.       Apply NLS Driver (Arabic)

3.       Run Forms, Report and Messages files for Arabic Language.

 Backups

 1.       Perform complete Backups after fresh install, MO, Patches etc.

2.       Plan backup strategy (Cold and Hot backup/RMAN). 

Network Configuration

 1. Verify sqlnet.ora, tnsnames.ora and listener.ora configuration files exist (or their links) in %ORACLE_HOME%/network/admin

2.  Verify parameters and log file locations

3. Configure IPC local database connections (optional)

4.  Move sqlnet.ora and tnsnames.ora files to %ORACLE_BASE%/admin/snet/admin directory and create links in each  %ORACLE_HOME%/network/admin directory

 Utility Setup

 1.       Create %ORACLE_BASE%/local directory and create “log” and “script” subdirectories

2.       Set up dbcontrol and orasetup utilities

3.       Set up dbora utility and follow script directions to install in /etc/init.d

4.       Optionally add:  Backup utility (e.g. bkctrl)

  • logdelete utility
  • chkdberr utility
  • SYSMON utility
  • SPACEMON utility

5. Create crontab/schedule entries for any installed utilities

Posted in Requirement Gathering | Leave a Comment »