Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • Oracle Ebs R12.1.1 File Location

    Uploaded by

    niaam
    65 views6 pages
    App

    Original Title

    11iApps

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    App

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    65 views6 pages

    Oracle Ebs R12.1.1 File Location

    Uploaded by

    niaam
    App

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 6

    11i/R12

    ORACLE EBS R12.1.1 FILE LOCATION


    Autoconfig log file:
    Apps:
    $INST_TOP/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log.
    Database:
    $ORACLE_HOME/appsutil/log/$CONTEXT_NAME//adconfig.log
    $ORACLE_HOME/appsutil/log/$CONTEXT_NAME//NetServiceHandler.log
    Startup/Shutdown Log files:
    $INST_TOP/logs/appl/admin/log
    Apache, OC4J and OPMN:
    $LOG_HOME/ora/10.1.3/Apache $LOG_HOME/ora/10.1.3/j2ee
    $LOG_HOME/ora/10.1.3/opmn
    Patch log:
    $APPL_TOP/admin/$SID/log/
    Concurrent log:
    $INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log
    Clone log:
    Preclone log files in source instance 
    Apps:
    $INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM.log) 
    Database:
    $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log) 
    Clone log files in target instance
    Apps :
    $INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_.log 
    Database:
    $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log
    Alert Log File:
    $ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log
    APPL_TOP
    [applmgr@gayatri10 ~]$ cd /oracle/PROD/apps/apps_st/appl
    INST_TOP
    [applmgr@gayatri10 ~]$ cd /oracle/PROD/inst/apps/context_name
    COMMAN_TOP
    [applmgr@gayatri10 ~]$ cd /oracle/PROD/apps/apps_st/comn
    JAVA_TOP  
    [applmgr@gayatri10 ~]$ cd /oracle/PROD/apps/apps_st/comn/java
    Database_top  
    [applmgr@gayatri10 ~]$
    cd /oracle/PROD/db/tech_st/10.2.0/appsutil/scripts/PROD_gayatri10/   
    Context file:-(.xml)
    [applmgr@gayatri10 ~]$
    cd /oracle/PROD/inst/apps/PROD_gayatri10/appl/admin
    Defaults file location:-(.txt) 
    [applmgr@gayatri10 ~]$
    cd  /oracle/PROD/apps/app_st/appl/admin/PROD/adalldefault.txt
    [applmgr@gayatri10 ~]$ cd APPL_TOP/admin/<SID>  
    Autoconfig log file:-
    [applmgr@gayatri10 ~]$
    cd /oracle/PROD/inst/apps/PROD_gayatri10/appl/admin/log

    DIFFERENCE BETWEEN APPLICATION R12 AND 11I


    Applications Release 12 and 11i , I decided to dedicate this post to outline few major
    technical difference.
    Database: 
    Database Version in 11i (11.5.9 & 11.5.10) was 9i Rel 2 where as in Release 12 its 10g
    R2 (10.2.0.2)
    Application Tier:
    Tech Stack in Application Tier consist of iAS(1.0.2.2.2) & Developer 6i (Forms &
    Reports 8.0.6) but in Applications R12 it is build on Fusion Middleware (10g Web Server
    and 10g Forms & Reports)
    Sub component in Application Tier
    A) HTTP Server or Web Server in R12 is Version 10.1.3 which is built on Apache
    version 1.3.34. In apps 11i it is Version 1.0.2.2.2 built on Apache Version 1.3.19
    B) Jserv in apps 11i is replaced by OC4J (mod_jserv is replaced by mod_oc4j)
    C) Forms Version 6i in Apps 11i is replaced by Forms 10.1.2.0.2 in R12
    D) Reports Version 6i in Apps 11i is replaced by Reports 10.1.2.0.2 in R12
    E) JDBC version is changed from version 9 in apps 11i to version 10.2.0 in Apps R12
    F) modplsql or mod_pls is removed from Apps R12 (What will happen to my mod
    plsql applications- coming soon* )
    G) Java processes use JDK/JRE version 1.5.0 in R12 against JDK version 1.3.1 or
    1.4.2 in Apps 11i
    H) For various environment variable changes check below picture
    I) New top INSTANCE_TOP added in Release 12 for configuration and log files.

                          11I/R12 COMMON TOPICS


    11i/R12 Common Topics
    Topic is quite important and I recommend you to go through this thoroughly.
    How to find version of Oracle Components
    APPS Patching
    Change APPS Password
    Context/XML or Autoconfig File
    Autoconfig
    Cloning Internals
    Logs in $APPLCSF
    Diff APPS 11i/R12
    Start/Stop Apps 11i
    Advaned Start/Stop Apps 12
    Patching Basics
    Cloning
    Step by Step Apps Cloning
    Hot backup Cloning

    First Let’s discuss terminology which you will encounter here & in most of Oracle
    Documentation.
    Server – is a process or group of processes and provides a particular
    functionality/service For example, Database Server listen and process database
    requests, similarly Web Server listens for and processes HTTP requests.
    Tier – is a logical grouping of services, may be on single machine or spread across
    more than one physical machine. For Example, Middle Tier in Oracle apps consist
    Form,Web,Report…Services. Forms & Report can be one machine 1 & Web Server can
    be on machine 2, still they will be part of same tier called as Application Tier or Middle
    Tier.
    Node – is referred as Machine, Each tier may consist of one or more node and each
    node can potentially have more than one tier.
    Desktop Tier – Oracle Applications/E-Business Suite is built on three tier Architecture
    with first Desktop Tier ic client machines accessing applications via browser(HTML
    based Self service applications) or Java Applet(Jinitiator) for Form based interface.
    Application/Middle Tier – Second is Application Tier also called as middle tier consists
    of WebServer Forms, Reports, Concurrent processing, Discoverer and Admin Server. I
    suppose its known as Middle tier because it lies between our desktop & third tier called
    database tier.
    Database Tier – Third is Database Tier contain Orale database server which store all
    your application data. I am sure if you are DBA you know it.
    *******************************************************************************

     COMPILE INVALID OBJECTS IN AN R12 APPS


    ENVIRONMENT
    Applying Patches can create invalid objects. To get a quick count of the number of
    existing invalids (if any), use the following select statement :
    SELECT COUNT(*)
    FROM DBA_OBJECTS
    WHERE STATUS = 'INVALID';

    For a more detailed query, use the following script :  

    SELECT OWNER, OBJECT_TYPE, COUNT(*)


    FROM DBA_OBJECTS
    WHERE STATUS = 'INVALID'
    GROUP BY OWNER, OBJECT_TYPE;

    To recompile an individual object, connect to SQL*PLUS as the owner of the object


    (generally apps) and use one of the following depending on the object type :  

    alter package <package_name> compile; (package specification)


    alter package <package_name> compile body; (package body)
    alter view <view_name> compile; (view)

    If the object compiles with warnings, use either of the following to see the errors that
    caused the warnings : 

    show errors
    OR
    select * from user_errors where name = '<OBJECT_NAME>';
    Another way to correct invalid objects is to run the adadmin utility as follows:  

    UNIX OPERATING PLATFORM 

    1. Log in as APPS User : <applmgr username>/<applmgr password>  

    2. Start the adadmin-Utility from the Unix prompt with this command :  

    adadmin

    The utility will then ask you a series of questions. 

    3. Under the Maintain Applications Database Objects Menu, select Compile APPS
    schema(s) 

    This task spawns parallel workers to compile invalid database objects in your APPS
    schema(s). It uses the same parallel phases as AutoInstall.

    Also try running $ORACLE_HOME/rdbms/admin/utlrp  


    .sql ( as sysdba )

    Within Applications, there is a script to compile INVALID objects - called ADCOMPSC.pls

    Arguments for ADCOMPSC.pls : 

    1 - Schema to run in 


    2 - Password for schema
    3 - Check errors for objects starting with #3

    NOTE: The order in which to compile Invalid Objects in schemas is SYS, SYSTEM, APPS and
    then all others. APPS_DDL and APPS_ARRAY_DDL should exist in all schema's. In case of an
    ORA-1555 error while running adcompsc.pls, restart the script. 

    The script can be run as followed : 

    cd $AD_TOP/sql
    sqlplus @adcompsc.pls SCHEMA_NAME SCHEMA_PASSWORD %

    Example : SQL> @adcompsc.pls apps apps %

    After the script completes, check for invalid objects again. If the number has decreased, but
    invalid objects still exist, run adcompsc.pls again. Keep running adcompsc.pls until number of
    invalid objects stops decreasing. 
    If there are any objects still left INVALID, verify them by using the script 'aderrchk.sql' to record
    the remaining INVALID objects. 'Aderrchk.sql' uses the same syntax as 'adcompsc.pls'. This
    script is also supplied with the Applications. Send the aderrchk.sql to a file using the spool <file>
    command in sqlplus. 

    e.g. sqlplus x/y @aderrchk.sql SCHEMA_NAME SCHEMA_PASSWORD %

    For objects which will not compile, try the following : 

    select text
    from user_source
    where name = 'OBJECTNAME'
    and text like '%Header%';

    This script will provide the script that creates the packages/recreates the packages. 
    SQL>@packageheader 
    SQL>@packagebody
    If recreating the package does not make the package valid, analyze the user_errors table to
    determine the cause of the invalid package :

    select text
    from user_errors
    where name = '<PACKAGENAME>';

    *******************************************************************************

    You might also like