Oracle Cloud Infrastructure
Coming soon ...
Apps R12.2
  • R12.2 Architecture
  • Cloning Error (RC-50208)
  • Apps R12.1
  • Major changes from 11i
  • R12:HTTP Debug Logging
  • Compile Apps Schema invalid objects in R12
  • Apps 11i
  • Apps Components and Architecture
  • Concurrent managers
  • Patching
  • Using AD Patch
  • Using AD Control
  • FNDCPASS utility
  • Single-node Installation
  • Multi-node Installation
  • Find Apps Version
  • Cloning
  • Upgrade 11.5.9 to 11.5.10.2
  • Upgrade from 11.5.10.2 to R12
  • Upgrading 9i to 10g with 11i
  • 11i/R12 General Topics
  • AppsDBA System Management Utilities Guide
  • Identifying Long Idle Sessions
  • Identifying High Active Sessions
  • Change hostname for EBS
  • Oracle 12c Database
  • Oracle12c PSU Apply
  • Oracle12c Datafile moved Online
  • Oracle 11g Database
  • Upgrade 10g to 11g R1
  • Upgrade 11.2.0.2 to 11.2.0.3
  • Database 9i-10g
  • Top 99 Responsibilities of a DBA
  • General Info
  • Database Patching
  • 10g:ASM
  • 10g:Data Pump
  • 10g:Data Guard Installing
  • 10g:Rollback Monitoring
  • 10g:Flashback Table
  • Tablespace Management
  • Materialized Views
  • 10g:Enterprise Manager
  • 10g:Upgrade
  • Error:Ora-01631
  • DBA Scripts
  • Disk I/O,Events,Waits
  • Tablespace Information
  • Session Statistics
  • Hit/Miss Ratios
  • User Information
  • Rollback Segments
  • Full Table Scans
  • Contention/Locking
  • Redo Log Buffer
  • Data Dictionary Info
  • Oracle10g Application Server
  • Oracle10g Application Installation
  • (Re)Securing OAS Control
  • Oracle AS10g null protocol issue
  • Oracle Backup & Recovery
  • RMAN
  • RMAN Setup
  • Backup Recovery
  • Flash Recovery Area
  • Oracle10g Discoverer with Apps
    Coming soon ..............
    Troubleshooting
  • Discoverer Troubleshooting
  • Access EBS in mozile
  • Linux and Unix Platforms
  • How To configure NFS
  • Unix/Linux Command
  • Change hostname in Linux
  • SENDMAIL configuration
  • This Oracle Application DBA Portal is the biggest knowledge gateway for the people in the world of Oracle...
    Friday, April 3, 2009
    AppsDBA System Management Utilities
    Overview
    The following information will detail system management utilities that can be used to
    successfully manage Oracle products in a UNIX environment. As Oracle products have become increasingly complex the simple tasks managing these products has become
    more and more difficult. Each new release brings more details and options that must be handled in order to successfully manage the Oracle environment. Oracle has not made this any easier by consistently failing to deliver tools or scripts to address the problems that are caused by incorrectly set environments and multiple ORACLE_HOME
    installations. Oracle makes no provision for managing the environment requirements of
    most of the Oracle Server utilities like the Net listener, Intelligent Agent, Oracle Names server or Oracle Enterprise Manager.
    Oracle environment management is setup and management of the UNIX operating system environment in which Oracle processes run. This includes the setting of environment variables like ORACLE_HOME and ORACLE_SID, and adding PATH directories like $ORACLE_HOME/bin. It also includes the startup and shutdown of the Oracle database, and the other Oracle processes that run to support an Oracle system like the Net listener and Enterprise Manager. The need for a consistent and defined methodology for handling database, SQL*Net/Network listener, Intelligent Agent/OEM processes, and Oracle Applications processes is important. When combined with multiple ORACLE_HOME software the issues become even more complex. In complicated environments just getting a correct UNIX environment setup can be difficult since Oracle makes it difficult to know which ORACLE_HOME is associated with Oracle service other than the database. Oracle supplies several standard scripts to help with database environment, startup and shutdown, but does not provide any help with its other product offerings. The following is a summary of the issues that are affected by environment management and that this
    Guide will address:
    1. Database startup and shutdown - These tasks must be performed from the correct
    userid (e.g. oracle) and must have the correct environment set (e.g.
    ORACLE_HOME, ORACLE_SID, PATH, LD_LIBRARY_PATH, NLS_LANG). Failure to do so can result in task failure and damage to the database. In addition, anyone with responsibility for these tasks must be aware of the correct procedures to follow.

    2. The following processes all suffer from the problem that there is no process to
    associate the correct ORACLE_HOME and executables with the version of the
    process that is running:SQL*Net/Network listener(s) startup and shutdown. To further complicate the issue, dynamic registration works best if the listener is started before any databases. If running shared servers then the listener should also be running before the database is started in order for the dispatchers to start correctly.
    o Oracle Intelligent Agents
    o Oracle Names server
    o OEM 9i Oracle Management Server
    o 10g OEM dbconsole

    3. Oracle Applications processes - The correct "applmgr" userid and APPL_TOP
    directory structure must be known and set before successful startup and shutdown
    of Oracle Application processes. This is made even more complex when multiple
    nodes are used. All of these issues are magnified when trying to set up automatic startup and shutdown
    during machine reboots.

    Oracle Supplied Environment Setup
    Oracle supplies the utilities coraenv/oraenv and dbhome to help customers with environment setup. These utilities drive off the "oratab" file to obtain the correct
    ORACLE_HOME for the database SID being accessed. Unfortunately these utilities have
    limited functionality. Not all environment variables are set and no support is available for other utilities (e.g. SQL*Net listener(s), Intelligent Agent, etc.).

    Oracle Supplied Database Startup and Shutdown
    Oracle supplies the scripts dbstart and dbshut to automate the startup and shutdown of all databases based on their "oratab" entry. These scripts can be run by hand or when the operating system is started or stopped. Unfortunately there is no mechanism for dealing with the SQL*Net listener, Intelligent Agents or Oracle Applications concurrent manager processes.

    Oracle Environment Control
    Oracle environment control is maintained in two metadata files located in the
    /var/opt/oracle directory1. The oraInst.loc file is used by the Oracle Universal Installer to maintain the inventory directory location and installation group name. The oratab file is used
    1 This will be the /etc directory on some platforms.

    to maintain the database SIDs defined, their corresponding ORACLE_HOME directory and
    a Y or N flag to indicate whether the database should be started on boot. The following willdescribe these files in detail and the extensions made to them.

    oraInst.loc File
    The oraInst.loc file is used by the Oracle Universal Installer to locate the oraInventory directory. The format of the file is as follows:
    #Oracle Installer Location File Location
    #Wed Feb 27 14:43:50 PST 2002
    inventory_loc=/oracle/product/9.2.0/oraInventory
    inst_group=dba

    By default the ‘oraInventory” directory is placed in the $ORACLE_BASE directory.

    Cloning Considerations
    When cloning ORACLE_HOME directories we recommend that the “inventory_loc”
    parameter point to $ORACLE_HOME/oraInventory. This will locate the oraInventory
    directory in the $ORACLE_HOME directory. This facilitates copying the ORACLE_HOME directory structure and still allows it to be patched or upgraded. Thisrequires that the oraInst.loc file be reviewed before starting any Oracle Universal Installer (OUI) session when supporting multiple ORACLE_HOME installations on the same machine. Our standard, when there is more than one ORACLE_HOME being managed is to maintain all of the inventory locations in the file with comments, and then uncomment
    the inventory being maintained at any given point in time. The following shows an example of two ORACLE_HOME directories being maintained in one oraInst.loc file:
    #Oracle Installer Location File Location
    #Wed Feb 27 14:43:50 PST 2002
    inventory_loc=/oracle/product/9.2.0/oraInventory
    #inventory_loc=/oracle/product/9.0.1/oraInventory
    inst_group=dba

    oratab File
    The oratab file maintains information about the databases currently installed. It is created during installation by the root.sh script and updated by the Database Configuration Assistant (DBCA) when creating new databases. The format of an entry is: $ORACLE_SID:$ORACLE_HOME:
    where $ORACLE_SID is the database system identifier, $ORACLE_HOME is the Oracle
    Server software directory for the database, and the third field is used by the “dbstart” utility
    with a “Y” indicating that the database should be started at system boot and a “N” indicating that it shouldn’t. A colon terminates a field and comment lines are ignored by the Oracle utilities.


    oratab Extensions
    The oratab file has been extended through the use of comments that allow it to be used to maintain additional information for other Oracle Server utilities as well. By using additional comments, Oracle provides commented information in this file as well, the integrity of the file is maintained and no Oracle supplied utilities that use this file are affected. The standard Oracle supplied utilities provide no ability to handle the additional server utilities, their locations, and additional options that must be known in order to start them. A good example is the SQL*Net listener. A single SQL*Net listener can support multiple Oracle databases, and each of these databases can have a unique ORACLE_HOME. In addition, there can be multiple listeners defined for a given ORACLE_HOME, or again for multiple ORACLE_HOMEs.
    In order to support these additional Oracle Server utilities the oratab file is modified with additional comment lines to define the Oracle utilities available, their locations and any options. The following lists the current oratab format recommendations, and these do not interfere with Oracle supplied tools and scripts and do not violate Oracle’s syntax for this file:
    :: <== Oracle standard format
    #::
    #APPLMGR:::
    The following lists the different options currently supported:
    - the Oracle database system identifier
    - the Oracle software directory
    - Y signifies that the database should be started during a
    system reboot, N signifies that it shouldn’t (Oracle
    default).
    Custom environment setup utilites set ORACLE_SID if a Y
    and TWO_TASK if an N.
    is:
    NETV1 - SQL*Net Version 1
    SNET - SQL*Net Version 2, Net8, Net8i, Net9, Oracle Networking (10g)
    NAMES - Oracle Names
    AGENT - Oracle Intelligent Agent
    OBACK - Obackup (EBU prior to 2.2)
    EBU - EBU 2.2
    OID - Oracle Internet Directory
    OEM - OEM Management Server
    OWS3 - Oracle Web Application Server 3
    OC4J - Oracle Containers For J2EE (standalone)
    AS9 - Oracle9i Application Server
    AS10 - Oracle 10g Application Server
    GRID - Oracle Grid Control (10g AS based)
    OCA - Oracle Certificate Authority
    is one or more options, separated by a ":".
    Based on the utility keyword, the following options are supported:
    SNET - listener alias (for multiple listener
    support), defaults to LISTENER if not supplied.
    OID - server name, oidlapd|oidrepld, instance
    number, and configset number in that order
    (instance number and configset number are optional,
    OWS3, AS9, AS10, GRID –

    Infrastructure database network alias.
    OEM, AGENT – Database SID for 10g.
    Note: AGENT should not be used with 10g dbconsole.
    APPLMGR is:
    is the applmgr UNIX id
    is the applmgr node name
    is the Oracle Applications system alias (e.g. OAPRD, used to identify multiple systems or if server partitioning is used on a single node), is optional.
    For server partitioned environments two entries are required. One for the database, presumably with a flag of "Y", and one for the Oracle Applications product files with a flag of "N" (an "N" flag causes orasetup to set the TWO_TASK environment variable rather than the ORACLE_SID environment variable).
    STANDBY is:
    This flag is only used on the standby database server. the SID of the Oracle standby database.
    posted by Srinivasan .R @ 2:02 AM  
    1 Comments:
    Post a Comment
    << Home
     
    About Me

    Name: Srinivasan .R
    Home: Chennai, India

    About Me:
    I am working as an Oracle Applications DBA specializing in EBS 11i/R12 with Over 14+ years of experience, mainly in different versions of Oracle Database & Application administration on various platforms like HP-UX, SOLARIS, AIX, Red hat Linux & Windows
    See my complete profile
    High Availability
  • Oracle10g RAC Installation
  • A Quick Reference for Oracle Database 10g RAC on Linux and Unix Platforms
  • Implementing Oracle 10g RAC with ASM on AIX
  • Locked objects for whole RAC
  • Monitor Memory RAC
  • Sessions RAC
  • Install Oracle 11g RAC On Linux
  • Migrating Oracle10g DB to ASM
  • Helpful Links
  • Good Metalink Notes
  • Discoverer:Metalink Notes
  • Logs Scripts:Metalink Notes
  • Support:Metalink Notes
  • Previous Post
  • Top 99 Responsibilities of a DBA
  • A Quick Reference for Oracle Database 10g RAC on L...
  • Implementing Oracle 10g RAC with ASM on AIX
  • DBA
  • Archives
    Download Software
  • Oracle 11g
  • Oracle 10g
  • 10g Express Edition
  • Oracle 9i
  • Oracle Apps
  • Oracle Linux
  • Oracle VM
  • App Server
  • Solaris
  • Fedora
  • Fedora
  • OpenSUSE
  • Ubuntu
  • Advertisement Links
    INTUIT Technology

    MACHS DATA

    Add Ons
    Locations of visitors to this page

    Add to Google Reader or Homepage

    Template by
    Sreene



    Oracle Application DBA Portal