Alsum Infotech Pvt.Ltd
          Specialized in Oracle Apps 11i & R12,Fusion Middleware services

         CONTACT US



  Hardware Support

  Database Administration

  Apps DBA & System Admin

  Middle Tier Services


Read more


  BI Publisher 11g Integration with EBS R12

Read more

  Oracle 11i application on Windows .

Read more

  Comparison Between Oracle Apps 11i and R12 Patching .

Read more

  Oracle Apps Patching Scripts .

Read more

  Systems and Application Products In Data Processing (SAP)

Read more

  Key points on oracle opatch utility

Read more

  What is ARU_ID?

Read more

  Oracle 9i Vs 10G Vs 11g - Memory structure

Read more

  Oracle 9i Vs 10g Vs 11g - Process architecture

Read more

  Useful Metalink Notes

Read more

EBS Upgrade from 12.0.6 to 12.1.3

BI Publisher 11g Integration with EBS R12

Software Download

BI publisher is bundled with other BI components

Download software from below URL:

Linux -32 Bit software to be downloaded with RCU (Repository Creation Utility)

Database Section

. Before Installing BI Publisher, the “MDS” & “BIPLATFORM” Schemas need to be loaded to the database.
. If Your Database resides on Linux platform, you can use RCU for Linux. If not, download the 32-bit windows client and run RCU.
. This will create MDS & BIPLATFORM Schemas and uploads the metadata required for BIP.

BI Publisher Installation

. Use BI runinstaller to start the installation
. Select “Enterprise Install” type ,This puts BIP in a managed server of weblogic.
. In the “Configure Components” section, Select only “Business Intelligence Publisher”.
. Once Installed & Configured ,you can access BI Publisher using below URL

        http://hostname: 9704/xmlpserver (For Enterprise Install)
        http://hostname:7001/xmlpserver (For Simple Install)

Integration with R12
Required Steps on BIP

dbc file from $FND_SECURE of Apps needs to be uploaded to BIP.
Before uploading create a local superuser.
Once done, upload the dbc file by selecting administration -> security configutaion -> security model in BI Publisher
Select “Oracle E-business suite” and upload dbc file.

Required Steps on EBS R12

Following responsibilities have to be created in EBS R12 and assigned to users:
Now Users can login to BIP with their EBS Credentials.

Happy BI Publisher Integration with EBS!!!

Oracle 11i application on Windows

[FrontPage Save Results Component]
11i On Windows :
Following are key differences for 11i on windows

. Shared APPL_TOP functionality not available in windows
. No Multiuser installation
· Windows environment files ends with .cmd (e.g.: APPSORA.CMD)

· To set environment
     Run %APPL_TOP%\envshell.cmd
     This will open a new window, run all commands in the new window

· Variables
     %LOCAL%{equal to $TWO_TASK in UNIX}
      %APPL_CONFIG%č Set to Context_name

· Start/stop scripts
     Command line: Adstrtal.cmd start
     Using control panel:
     Go to control panel ŕ servicesŕ select a serviceŕ click start (or) stop

· Installation
     Single user mandates:
     User must have full local admin privilege
     Must be member of local Admin & Domain Group
     Not be member of GUEST group

· Autoconfig
     In Unix will prompt for apps password, in case of windows it will not prompt.     So we need to supply it as

· Setup printers
    Concurrent manager starts by default under internal system Account. This account doesn’t have access to network printing devices. To run reports using Concurrent Manger Click ConcurMGR SID services, In the Login As section select Account, enter admin-privileged account. Repeat above step for TNS listener (Ora806TNSLitsener80) also.
Reboot the system, so that the changes take effect.

· Setup UTF8 character Set
    Complete the following step if you use UTF8 character set
    Rename fmrweb .res fmrweb .res.bak
    Copy fmrweb _utf8.res fmrweb .res
    The above step is not required for US language

Comparison Between Oracle Apps 11i and R12  Patching

There is no Oracle APPS without patching, Most of the time APPS DBA will end up in applying patches for bugs in corresponding releases. We can approximate around 40% of his activity will go in patching. This topic will explain basic differences between 11i and R12 patching.


1. Patch:


Patch is a piece of code/software update for fixing a bug, adding new feature or functionality. It can be simply stated as correction or modification to Application.


2. Patch Format classification:




Ø      Standalone/One-off patch

                         Resolves specific bug

Ø      Minipack      

                   Collection of one-off patches for specific module.

Ø      Family pack 

                         Collection of minipack for particular family group.

Ø      Consolidated update (CU)

Includes recommended patches for all products, Updates apps to latest recommended patch level.


Ø      Maintenance pack

Collection of all minipacks for all products. Maintenance pack upgrades system to new point release, such as 11.5.10




In R12 patches are grouped in to code lines and associated with Code levels. Codeline includes all patches to maintain that point release.


Lets say 12.0 is the point release, it introduces codeline A. Similarly 12.1 introduces codeline B and so on.


Code level includes all bug fixes and codelevels for particular codeline. Code levels are cumulative. All code levels created after the initial point release are aggregated into cumulative release update packs (RUPs)


Base code level for 12.0 is A. Cumulated New bug fixes for products are released as A.1.

A.2 includes A.1 & A.2; similarly A.3 includes A.1 to A.3 and so on.


Ø      Individual bug fix 

              Similar to one off in 11i

Ø      Product Family Release Update pack (RUP)

Similar to family pack in 11i.Aggregation of all one-off in particular codeline specific to a family

Ø      Release Update Pack (RUP)

Cumulative of all Product Family RUPs.Changes version from 12.0 to 12.0.1,12.0.2 and so on.

Ø      Consolidated Upgrade 

Similar to CU on 11i.Its available for upgrading R12 system from one point release to another.


3. Patch naming convention:




ü      One-off patch

                  Patchnum e.g.: 8234812

ü      Minipack

                 11. <PROD>.A e.g.: 11.AD.I

ü      Family Pack :

                 11i. <PROD family>. letter e.g.: 11i.HR_PF.A

ü      Maintenance pack:

                 11.5.x e.g. 11.5.9




The patch naming convention has changed to  R12.PROD.CL. #

Where PROD à Product (E.g. GL, OAM, AP, AR…)

                  CL àCode line (E.g. A, B, C…) R12.PROD.CL -> code level

                   #  à  Fix sets (E.g. 1,2.)


E.g.: R12.OAM.A.1


This is code level A with first set of fixes.



4. Downloaded patch Example:


11i                                                    R12        


5.Patch driver files:


An 11i patch comes with c, d, g & unified driver format. R12 patches have unified drivers.


6.Applying patch:


Use adpatch (Both 11i & R12)


Help à adpatch -help


7.Merging patches


Use admrgpch (Both 11i & R12)


Help à admrgpch -help


8.Log Files


Both 11i & R12


Patching log files adpatch.log  and adwrkxxx.log files are Located at $APPL_TOP/admin/$TWO_TASK/log


Restart files are Located at $APPL_TOP/admin/$TWO_TASK/restart


Timing report files are located at $APPL_TOP/admin/$TWO_TASK/out


9.MRC schema:




MRC schema is available, while executing d driver invoker rights is necessary. 




MRC schema is not available, so while executing d driver invoker rights is not necessary.


10.Oracle Patch application assistant (PAA):



 Not available



PAA helps users to track and perform manual steps during patching Executed by invoking




When patches are merged using admrgpch, PAA merges readme files and this avoids redundant tasks. Also it simplifies patch application by combining all manual steps 


11. Customized files:




We have $APPL_TOP/admin/applcust.txt file containing records of all customized files. 


Registered Flagged Files Tool in OAM records customization. Autopatch reviews AD_FILES table to check for customization.


Go to TOP

  • Oracle Apps Patching Scripts

  • Oracle APPS Patching Scripts


     Follow metalink note 139684.1 to download and use script.

    2.Query to check individual patch/Bug

    select bug_number,last_update_date from ad_bugs where bug_number=’&bnum’;


    3.Query to check Product patch levels

    set linesize 1000

    column APPS format a10


    select decode(nvl(a.APPLICATION_short_name,'Not Found'),


            'Not Found','id '||to_char(fpi.application_id),

            a.APPLICATION_short_name) apps,


                   'N','Inactive',fpi.status) status,


            nvl(fpi.patch_level,'-- Not Available --') Patchset,

            to_char(fpi.last_update_date,'dd-Mon-RRRR') "Update Date"

    from fnd_oracle_userid o, fnd_application a, fnd_product_installations fpi

    where fpi.application_id = a.application_id(+)

      and fpi.oracle_id = o.oracle_id(+)

    order by 1,2



    4. Query to Check ATG (Techstack) Patch level




    SET head off Lines 120 pages 100
    col p_num format A65
    col bug_number format A10
    col patch_name format A10
    select bug_number, decode(bug_number,
    '3438354', '11i.ATG_PF.H'
    ,'4017300' ,'11i.ATG_PF.H.RUP1'
    ,'4125550' ,'11i.ATG_PF.H.RUP2'
    ,'4334965' ,'11i.ATG_PF.H RUP3'
    ,'4676589' ,'11i.ATG_PF.H RUP4'
    ,'5382500' ,'11i.ATG_PF.H RUP5 HELP'
    ,'5473858' ,'11i.ATG_PF.H.5'
    ,'5674941' ,'11i.ATG_PF.H RUP5 SSO Integrat'
    ,'5903765' ,'11i.ATG_PF.H RUP6'
    ,'6117031' ,'11i.ATG_PF.H RUP6 SSO 10g Integration'
    ,'6330890' ,'11i.ATG_PF.H RUP6 HELP'
    ) p_num, last_update_date
    FROM ad_bugs
    WHERE bug_number
    IN ( '3438354', '4017300', '4125550', '4334965', '4676589', '5382500', '5473858', '5674941', '5903765', '6117031', '6330890' );





    SET head off Lines 120 pages 100
    col p_num format A65
    col bug_number format A10
    col patch_name format A10

    select bug_number, decode(bug_number,
    '5917344', 'R12.ATG_PF.A.DELTA.2',

    '6077669', 'R12.ATG_PF.A.DELTA.3',

    '6272680', 'R12.ATG_PF.A.DELTA.4 '
    ) p_num, last_update_date
    FROM ad_bugs
    WHERE bug_number
    IN ('5917344', '6077669', '6272680');


    5..Query to check AD Patch level




    SET head off Lines 120 pages 100
    col p_num format A65
    col bug_number format A10
    col patch_name format A10

     select bug_number, decode(bug_number,
    '1351004' '11i.AD.A'
    ,'1460640' ,'11i.AD.B'
    ,'1475426' ,'11i.AD.C'
    ,'1627493' ,'11i.AD.D'
    ,'1945611' ,'11i.AD.E'
    ,'2141471' ,'11i.AD.F'
    ,'2344175' ,'11i.AD.G'
    ,'2673262' ,'11i.AD.H'
    ,'4038964' ,'11i.AD.I.1'
    ,'4229931' ,'11i.AD.I.2'
    ,'4337683' ,'11i.AD.I.2'
    ,'4502904' ,'11i.AD.I.3'
    ,'4605654' ,'11i.AD.I.4 Delta.4'
    ,'4712847' ,'11i.AD.I.3'
    ,'4712852' ,'11i.AD.I.4'
    ,'5161676' ,'11i.AD.I.5'
    ,'5161680' ,'11i.AD.I.5'

    ,'6502079' ,'11i.AD.I.Delta.6'

    ,'6502082' ,'11i.AD.I.6'

    ) p_num, last_update_date
    FROM ad_bugs
    WHERE bug_number IN ( '1351004' '1460640' '1475426' '1627493' '1945611' '2141471' '2344175' '2673262' '4038964' '4229931' '4337683' '4502904' '4605654' '4712847' '4712852' '5161676' '5161680','6502079','6502082'  );





    SET head off Lines 120 pages 100
    col p_num format A65
    col bug_number format A10
    col patch_name format A10

     select bug_number, decode(bug_number,
    '4502962' 'R12.AD.A'
    ,'5905728' ,'R12.AD.A.1'
    ,'6014659' ,'R12.AD.A.2'

    ,'6272715' ,'R12.AD.A.3'

    ,'6510214' ,'R12.AD.A.4'
    ) p_num, last_update_date
    FROM ad_bugs
    WHERE bug_number IN ( '4502962' '5905728' '6014659','6272715','6510214'  );


    6 Query to check .Autoconfig patch Level


    SET head off Lines 120 pages 100
    col p_num format A65
    col bug_number format A10
    col patch_name format A10
     select bug_number, decode(bug_number,
    '2488995' ,'11i.ADX.A'
    ,'2682177' ,'11i.ADX.B'
    ,'2682863' ,'11i.TXK-C'
    ,'2757379' ,'11i.TXK-D'
    ,'2902755' ,'11i.TXK-E'
    ,'3002409' ,'11i.ADX.C'
    ,'3104607' ,'11i.TXK-F'
    ,'3219567' ,'11i.TXK-B'
    ,'3239694' ,'11i.TXK-G'
    ,'3271975' ,'11i.ADX.E'
    ,'3416234' ,'11i.TXK-H'
    ,'3453499' ,'11i.ADX.F'
    ,'3594604' ,'11i.TXK-I'
    ,'3817226' ,'11i.ADX.E.1'
    ,'3950067' ,'11i.TXK-J'
    ,'4104924' ,'11i.TXK-K'
    ,'4367673' ,'11i.TXK-J.1'
    ,'4717668' ,'11i.TXK-M'
    ,'5035661' ,'11i.One_off'
    ,'5107107' ,'11i.TXK-N ROLLUP PATCH (AUG 2'
    ,'5414396 ' ,'11i RAPIDCLONE CONSOLIDATED FIXES JAN/2008 '
    ,'5456078' ,'11i.One_off_a'
    ,'5473858' ,'11i.ATG_PF.H RUP5'
    ,'5478710' ,'11i.TXK-O'
    ,'5759055' ,'11i.TXK-P'
    ,'5903765' ,'11i.ATG_PF.H RUP6'
    ,'5985992' ,'11i.TXK-Q'
    ) p_num, last_update_date
    FROM ad_bugs
    WHERE bug_number IN ( '2488995' ,'2682177' ,'2682863' ,'2757379' ,'2902755',
    '3002409' ,'3104607' ,'3219567' ,'3239694' ,'3271975' ,'3416234' ,
    '3453499' ,'3594604' ,'3817226' ,'3950067' ,'4104924' ,
    '4367673' ,'4717668' ,'5035661' ,'5107107' ,'5414396 ' ,
    '5456078' ,'5473858' ,'5478710' ,'5759055' ,'5903765' ,'5985992' );



    SET head off Lines 120 pages 100
    col p_num format A65
    col bug_number format A10
    col patch_name format A10
    spool LACF_ptch_level.txt
    select ' LACF ' FROM dual;
    select bug_number, decode(bug_number,
    '4494373' ,'R12.TXK.A'
    ,'5872965' ,'R12.OAM.A'
    ,'5909746' ,'R12.TXK.A.1'
    ,'5917601' ,'R12.TXK.A.2'
    ,'6077487' ,'R12.TXK.A.DELTA.3'
    '6329757' ,'R12.TXK.A.DELTA.4'
    ,'6145693 ' ,'R12 RAPIDCLONE CONSOLIDATED FIXES JAN/2008')
    p_num, last_update_date
    FROM ad_bugs
    WHERE bug_number IN ( '4494373' ,'5872965' ,'5909746' ,'5917601' ,'6077487' ,'6145693 ','6329757'  );


    Go to TOP

    Systems and Application Products In Data Processing (SAP) 

    [FrontPage Save Results Component]

    Systems and Application Products (SAP) 

    A market Leader in ERP & competitor to Oracle Applications. .


    SAP version History


    The following Lists the SAP Releases in order

    SAP R/1

    SAP R/2  (Mainframe Based/Terminal Screens )

    SAP R/3 (Client/server based Application)

         R/3 Release 1.0 & 1.1

         R/3 Release 2.0,2.1

         R/3  Release 3.0,3.1

         R/3 Release 4.0

         R/3  Release 4.5

         R/3 Release 4.6

         R/3 Enterprise Release 4.7

    SAP ERP (My SAP)

        ECC 5.0

        ECC 6.0            { ECC – ERP Central Component}



    SAP (From R/3) is purely a 3-tier architecture with presentation, Application and Database tiers. It is able to run on different platforms (Operating Systems, Hardware & Database) with the help of BASIS. Application Programs are written in SAP’s own interpretative ABAP ( Advanced Business Application Programming) Language.


    SAP supported Databases


    The Following are the list of databases supported by SAP.It is noted that Sybase(One of the Market Leader in database) is not in the list.The Cheapest out of all this is MaxDB owned by SAP.

    • Oracle
    • MS SQL Server
    • IBM DB2 for Linux, UNIX, and Windows
    • SAP liveCache Technology
    • MaxDB (SAPS own Database, Formerly MysqlDB)
    • IBM DB2 Universal Database for z/OS
    • IBM DB2 Universal Database for iSeries
    • IBM Informix


     Adabas D (Adaptable Data Base System) Database  was supported by SAP in its initial versions.


    Go to TOP




    Patches are a small collection of files that are copied over an existing installation




    Is oracle supplied utility used for applying interim patches to oracles software.Its a java based utility which makes use of OUI.


    To download/Install opatch:


    Follow metalink id :274526.1 - How to download and install opatch (generic platform)


    To Find opatch version:


    Command :


    $ opatch version




    Invoking OPatch


    OPatch Version:


    OPatch succeeded.



    Available opatch vesrions:


    For version 10.2 before   -->

    For version 10.2 onwards  -->   10.2.x.x.x


    Structure of interim patches :


    The interim patches have the following contents:


    Patch Metadata: This contains information on the patch ID, the bugs fixed, the files affected, and the actions to be performed.


    Payload: This contains the files that will be modified by OPatch.


    Custom Scripts: Pre-processing and post-processing scripts that needs to be run before and after patching.


    Before applying patch:


    It is recommended to back up the following before any patch operation



    2. Central inventory


    Opatch help:


    opatch -help


     Usage: opatch [ -help ] [ -r[eport] ] [ command ]


                command := apply








    OPatch Command options:


    apply             Installs an interim patch

    lsinventory    Lists what is currently installed on the system

    query             Queries a given patch for specific details

    rollback         Removes an interim patch

    version          Prints the current version of the patch tool.

    prereq           Runs the prerequisite checks

    util                  Runs opatch internal utilities



    To apply a patch :


    opatch apply


    To Rollback a patch:


    opatch rollback -id <ID>


    where <ID> is the patch number


    To List inventory:


    opatch lsinventory


    Opatch log files:


    OPatch maintains logs for all apply, rollback, and lsInventory operations. The log files are located in

    <ORACLE_HOME>/cfgtoollogs/opatch   for 10.2 onwards & in

    <ORACLE_HOME>/.patch_storage       before 10.2.  

    Each log file will be tagged with the timestamp of the operation. Log files are named as opatch_<date mm-dd-yyyy>_<time hh-mm-ss>.log.


    Backup :


    The opatch will take backup of old files and copy the same in to






    To restore the oracle home ,execute the located at




    Types of RAC patching:


    1.All node patching


    In this case all rac nodes are brought down, patches are applied to all the nodes. The downtime will be maximum.


    2. Rolling patching


    Patches are applied to nodes one by one. The downtime is zero, but only few patches can be applied in this mode.


    3.Minimum downtime patching


    The nodes are divided in to sets and patches are applied to sets individually by bringing down the set alone.


    command :  opatch apply -minimize_downtime


    Opatch in 11G


    Hot patching


    We already aware of oracle 11i hot patching, Now RDBMS patching has also become Hot in 11g.


    This is new in 11g and It doesn’t requires instance to be down for patching.


    Currently It is available for Linux x86/x86-64 , Sun SPARC platforms.


    To determine whether patch can be applied hot or not?


    Opatch query –is_online_patch <Patch_location>


    Note : Not all bug fixes/Diagnostic patches are available as a hot patch


    Rollup Patch:


    RAC rolling patching is applied by starting opatch in one instance. It automatically copies all files to other RAC nodes and applies the patch on them.


    To determine whether patch is rollup or not?


    Opatch query –is_rolling_patch


    Go to TOP

    This is unique Platform ID  used for patching oracle .

    To see the ARU_ID:

    Before Installation in the software DVD/CD,


    The ARU_ID is in /Disk1/stage/shiphomeproperties.xml file


    After Installation,





    XML Content:








    ARU ID’s for different platforms


    Platform                        ARU ID

    HPUX 64 bit                  59

    IBM 5L                           212

    Linux 32 bit                    46

    Solaris 32 bit                 453

    Solaris 64 bit                 23

    Windows XP                 912 


    Go to TOP

    The following section describes changes/feature in memory structure of their respective releases.


    Oracle 9i


    1.Dynamic SGA


    The size of the buffer cache, the shared pool, the large pool, and the process-private memory can be changed without shutting down the instance.


    With dynamic SGA, the unit of allocation is called a granule. Components, such as the buffer cache, the shared pool, the java pool, and the large pool, allocate and free SGA space in units of granules.


    2.       2.Multiple block size


    Oracle supports multiple block size in a database. Size of standard buffer is determined by



    Non-standard block size buffers are specified by the following parameters:







    3.Multiple Buffer pools


    It supports multiple buffer pools namely KEEP, RECYCLE and DEFAULT.

    v     The KEEP buffer pool retains the schema object’s data blocks in memory.

    v      The RECYCLE buffer pool eliminates data blocks from memory as soon as they

    are no longer needed.

    v      The DEFAULT buffer pool contains data blocks from schema objects that are not

    assigned to any buffer pool, as well as schema objects that are explicitly

    assigned to the DEFAULT pool.

    4. PGA memory management automatic for dedicated Mode


    WE can automatically and globally manage the size of SQL work areas. We need to specify the total size dedicated to PGA memory for the Oracle instance by setting the initialization parameter PGA_AGGREGATE_TARGET.


    Oracle 10g:


    1.  Automatic Shared Memory Mangement

    The size of SGA can be set by using SGA_TARGET.Oracle manages all other components internally. SGA_TARGET is not dynamic.


    Still few components were not automatically managed, They are




    1. Streams pool

    The streams pool is used exclusively by Oracle Streams. The Streams pool stores buffered queue messages, and it provides memory for Oracle Streams capture

    processes and apply processes.

    Size is determined by strems_pool_size init parameter.


    1. PGA memory Management (PGA_AGGREGATE_TARGET) for both Dedicated and shared server.


    Oracle 11g:


    1. Result Cache


    It stores query results for improving performance of queries. It is composed of


    SQL query result cache  à Results of queries and query fragments are cached in to it

    PL/SQL Function result cache à Results of PL/SQL functions are cached in to it.


    1. AMM(Automatic memory management)

    The memory used by collection of all PGA’s( Referred to as instance PGA) can be maintained automatically. So the ASMM (Automatic Shared Memory Management in 10g has now been moved to AMM.


    BOTH SGA & PGA instance can be maintained automatically.


    Go to TOP

    Oracle 9i Vs 10g Vs 11g -  Process architecture

    Process Architecture:


    The following document describes changes/feature in Process Architecture  of their respective releases.


    Oracle 9i


    1.Background Processes


    Job queue processes are managed dynamically.


    Oracle 10g:


    1.Background Processes


    Total Number of background processes = 157


    Few Newbie’s on 10g


    1.1.AWR  (Automatic Workload Repository)


    MMON  à It makes snapshots of the database 'health' (statistics) and stores this information in the automatic workload repository.

    MMNL à MMON Lite process, performs frequent and light-weight manageability-related


    1.2. ASMM (Automatic shared Memory Management)


    MMAN à Memory Manager dynamically adjusts size of following SGA Components:


    Database buffer cache

    Large pool

    Java pool

    Shared pool


    1.3. ASM (Automatic Storage Management)


    RBAL à coordinates rebalance activity for disk groups in an Automatic Storage

    Management instance.

    ORBn à performs the actual rebalance data extent movements in an Automatic Storage

    Management instance.

    OSMB àIt  is responsible for communicating with the ASM instance.



    Oracle 11g:


    1.  Alert log is now  in both text & XML format. Use ADRCI utility to view a text version of the alert log (with XML tags stripped)


    2.  ADR(Automatic Diagnostic repository)


    A file based repository outside database which stores diagnosing information and same can be used for analyzing errors based on incident number. Location of this is set by DIAGNOSTIC_DEST initialization parameter

    3.Location of alert log and trace files :

    Files are under ADR_HOME.. Contents  are as below:

    Subdirectory Name



    The XML-formatted alert log


    Background and server process trace files and SQL trace files and text alert.log file


    Core files


    For Additional Details Follow metalink note 438148.1


        4. Background Processes


    Total Number of background processes = 212


    Few Newbie’s on 11g


    DBRM à database resource manager process is responsible for setting resource

    plans and other resource manager related tasks.


    DIA0 à  diagnosability process 0  is responsible for hang detection and deadlock resolution.


    DIAG  à diagnosability  process performs diagnostic dumps and executes global

    oradebug commands.


    VKTM à virtual keeper of time is responsible for providing a wall-clock time

    and reference-time counter .


    FBDA à flashback data archiver process  archives the historical rows of tracked

    tables into flashback data archives


    Go to TOP




    Oracle 9i,10g:




    It’s a binary file. Initialization parameters stored in a server parameter file are persistent. Changes mad to init.ora will persist across instance shutdown and startup.


    Recovery terminology


    Instance recovery

    Rolling forward and rolling back the committed and uncommitted data respectively.


    Oracle 11g


    Oracle Hardware Assisted Resilient Data (HARD)


    Program designed to prevent data corruptions before they happen. Using this the database performs validation steps when we change a basic parameter to prevent illegal values from being written to SPFILE.


    New Recovery terminology


    Cache Recovery


    Rolling forward – applying changes recorded in redo log to datafiles


    Transaction Recovery


    Rolling back – applying undo to rollback uncommitted changes.


    Tablespaces and data files


    Oracle 9i


    Oracle Managed Files


    Operating system files are managed by oracle using OMF/We need to specify operations in terms of objects rather than file name.


    Undo tablespaces


    Replaces rollback segment in earlier version. It stores undo information. Automatic undo management mode is supported under compatibility levels 9i or higher.


    Default Temporary tablepsace


    If system tablepsace is local then temporary we must define default temporary tablespace.


    Transport tablespace


    It is used to move subset of an oracle database from one database to another on the same platform.

    It has an added advantage of not to rebuild index after importing table data.


    Physical limitation


    Minimum Redolog file size  is 50 Kb

    Maximum  Number of partitions allowed per index or table is 64k-1.


    Oracle 10g



    Bigfile tablespace


    It allows oracle database to contain tablespaces made up of single larger files .So the traditional type is named as small file tablespace which is default. Oracle database can now scale up to 8 terra bytes in size.


    Bigfile tablespaces are supported only for locally managed tablespaces with automatic segment space management.



    Sysaux Tablespace


    A new tablespace created during db creation or upgrade and is an auxiliary tablespace to system.This can’t be dropped or renamed. Also transportable tablespaces for SYSAUX is not supported.


    Undo tablespace


    We can create bigfile undo tablespace.

    undo advisor can be used to provide advice on undo retention.

    10G Automatically tunes undo retention period parameter. Automatic tuning is not supported for LOB’s,


    Temporary tablespace:


    We can create group of temporary tablespaces. A tablespace group can be specified as default temporary tablespace. We can create bigfile temporary tablespace.


    Transport tablespace


    Tablespace transport is supported even across different platforms. Tablespaces that are read only prior to oracle 10g must be made read write at least once before they can use cross platform transportable feature.


    Physical limitation


    Minimum Redolog file size  is 50 Kb

    Maximum  Number of partitions allowed per index or table is 1024k-1.


    Oracle 11g:


    Undo tablespace


    Automatic undo management mode is made as default.


    Physical limitation


    Minimum Redolog file size  is 4 Mb

    Maximum  Number of partitions allowed per index or table is 1024k-1. 


    Go to TOP

    The following Lists  Useful Metalink Notes for Installing and Maintaining 11i.

    The format will be document Title –Note number.


    11i ALL

    Oracle E-Business Suite Release 11i Technology Stack Documentation Roadmap --207159.1



    Oracle Applications Installation Update Notes, Release 11i ( --316806.1

    Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0) --216550.1

    Oracle Applications Release 11i with Oracle Database 10g Release 1 (10.1.0) --282038.1

    Oracle Applications NLS Release Notes, Release 11i ( --316804.1

    Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 1 --356839.1

    Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i --217368.1

    Installing Oracle9i Application Server with Oracle Applications 11i --146468.1

    Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i --233436.1



    Visual C++ Requirement for Release 11i on Windows --201392.1

    Using Cygwin to Maintain Release 11i on Windows --302859.1



    Oracle E-Business Suite Upgrade Guide - Execute --461710.1

    Interoperability Notes Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0) --216550.1

    Interoperability Notes Oracle Applications Release 11i with Oracle Database 10g Release 1 (10.1.0) --282038.1

    Interoperability Notes Oracle Applications Release 11i with Oracle Database 10g ( --362202.1

    Interoperability Notes Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0) --362203.1

    Interoperability Notes - Oracle E-Business Suite Release 11i with Oracle Database 11g Release 1 (11.1.0) --452783.1

    Upgrading Developer 6i with Oracle Applications 11i --125767.1

    Upgrading Oracle JInitiator with Oracle Applications 11i  --124606.1



    Migrating to Linux with Oracle Applications Release 11i  --238276.1

    Windows OS Upgrade for 11i E-Business Suite --231876.1

    32-bit/64-bit Certification/Conversion Issues on Oracle Applications 11i --197031.1



    Cloning Oracle Applications Release 11i with Rapid Clone --230672.1

    Additional steps after cloning an environment using the 11i cloning whitepaper --182812.1

    Frequently Asked Questions About Cloning Oracle Applications 11i  --216664.1



    Using AutoConfig to Manage System Configurations with Oracle Applications 11i  --165195.1

    Frequently Asked Questions About Using AutoConfig With Oracle Applications Release 11i  --218089.1



    Oracle Applications Patching FAQ for Release 11i -- 457566.1

    Patching Best Practices and Reducing Downtime  --225165.1

    How to Correctly Obtain and Apply D2K Forms Patches --150911.1

    Sharing the Application Tier File System in Oracle E-Business Suite11i --233428.1



    Best Practices for Securing Oracle E-Business Suite  --189367.1

    integrating Oracle E-Business Suite Release 11i with Oracle Database Vault --428503.1


    Performance tuning

    Troubleshooting Oracle Applications Performance Issues --169935.1

    Configuring various JVM tuning parameters for Oracle E-Business suite 11i and R12 --567551.1

    Performance issues relating to Oracle Applications 11i client connections --123878.1


    Maintenance & Troubleshoot

    Applications 11i Health Check After Maintenance -- 283976.1

    Oracle Application Server 10g with Oracle E-Business Suite Release 11i Troubleshooting Guide  --295606.1

    Oracle9i Application Server (9iAS) with Oracle E-Business Suite Release 11i Troubleshooting  --216208.1

    Tips & Tricks To Make Apache Work With Jserv --330250.1

    11i: Troubleshooting Issues with the Applications Signon Form --108045.1

    Checking the Forms Server Client Connection Process In Oracle Applications 11i --310976.1

    How to Troubleshoot Forms Hanging Using Export Functionality --423261.1



    Using Discoverer 4i with Oracle Applications 11i --139516.1

    Using Discoverer 10g (9.0.4) with Oracle Applications 11i --257798.1,



    FAQ (Oracle Applications Manager) --117264.1

    Troubleshooting (Oracle Applications Manager) --117270.1



    Configuring an X Display Server for Applications on Unix Platforms --181244.1

    Recommended Browsers for Oracle Applications 11i -- 285218.1

    Database Initialization Parameters and Configuration for Oracle Applications 11i --216205.1

    How to investigate printing issues and work towards its resolution ? --297522.1


    This is not a complete list, It will be updated with more in future.


    Go to TOP


    Copyright ©2010 Alsum Infotech Company Inc. All rights reserved.