Forgot your password?    
+ Reply to Thread
Results 1 to 2 of 2

Thread: Oracle Apps Interview Questions for Multiple Organizations

  1. #1

    Smile Oracle Apps Interview Questions for Multiple Organizations

    Hi Guys, these are the few questions which I faced in my recent interviews
    In Striker, Infogane, SOFTENGER, Path, Damcosoft, TCS

    1. What are the rolls and responsibility?*****
    2. what are the daily activities of an APPSDBA And DBA ?*****
    3. Tell about your current projects?****
    4. What kind of calls you recieve from the client?|**
    5. what kind of ticket issues faced/raises on regular interval .
    6. A person cannot able to see login page. Give Step by step solution?
    7. What is your team size?**
    8. Tell the reason for change?*****
    9. What is ADSPLICE UTILITY**
    10. Explain an ORA-01555.
    11. Roll of APPS and DATABASE Listener.
    12. What problems/errors you faced in Frontend.****
    13. If Somebody delete the table then how you resore it?**
    14. What is the size of os block and db block can we change it?
    15. What is rman? Use of RMAN? Do you know RMAN Cloning?
    16. What Issues we face in managing Datafiles and tablespaces?
    17. How to find Tablespace Size?
    18. Have you use R12 in current Project?****
    19. During Patching you shutdown CM , What happen to running Concurrent Manager request.
    20. What error you faced recently and how you troubleshoot it.*****
    21. How frequently you take support from Oracle Support Team & what types of errors.**
    22. What are the prerequisites during installation of oracle and apps 11i.
    23. Backup strategy in your environment., retention policy?**
    24. What is AutoConfig?*
    25. If the request is running from a long time then what would be troubleshooting.
    26. How you will keep concurrent request in hold.
    27. common issues in concurrent manager ?****
    28. Conflict resolution manager function?
    29. Have you applied cu2 patch?
    30. What are the errors you face in daily routine.**
    31. How will you get the assigning of a job:
    32. Why we need downtime?
    33. Mandatory Background processes. With details.
    34. printer set up ?
    35. Oracle EBS Login Page Error**
    36. What steps you follow when user complain about database slowness.
    37. How you will unable trace for a particular session.
    38. How you will generate AWR report and what you check in AWR report.
    39. Custum top in oracle apps.**
    40. How to find the CPU utilation?
    41. How to test apache
    42. How u will monitor u r applications as well as database?
    43. How to increase performance?
    44. Types of patches?***
    45. How to get the current Patchset level of Oracle Applications products in R12 ?
    46. How to Speed up the patch
    47. What is the significance of FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS table?**
    48. Index already applied in patch application what to do?
    49. Restart files in patch.
    50. Rectify working hanging/Patch Hanging Senario?
    51. How to check worker? Which option is the hidden option? adctrl Usage , Diagnosis and Resolution **
    52. We are applying patch. It applied 90%. Then some error come then what to do.
    53. If Patch fail due to some error then what to do? Troubleshooting a Patch Failure - adpatch
    54. What is the difference between ad_bugs and ad_applied_patches?**
    55. Steps for patching in application and database tier.
    56. When You applied patch?
    57. Steps for cloning from multinode environment to single?
    58. common error faced while clonning ?*****
    59. Why we use maintenence mode?
    60. Difference between 11i and R12?**
    61. If users complaining Oracle Applications 11i system is running slow , what all things you will check at broad level ?*
    62. upgradation to R12 ? **
    63. Use of FNDCPASS? If we change it by other method then what happened***



    Note: Star(*) means these questions are asked in in multiple times in different companies. for example 2 star means question asked in two companies


    Hope this is benificial for all
    Best of luck!

  2. #2
    1. What are the rolls and responsibility?*****

    Database Administrator (DBA)

    DBA Responsibilities

    The job of the DBA seems to be everything that everyone else either doesn't want to do, or doesn't have the ability to do. DBAs get the enviable task of figuring out all of the things no one else can figure out. More seriously though, here is a list of typical DBA responsibilities:
    • Installation, configuration and upgrading of Oracle server software and related products
    • Evaluate Oracle features and Oracle related products
    • Establish and maintain sound backup and recovery policies and procedures
    • Take care of the Database design and implementation
    • Implement and maintain database security (create and maintain users and roles, assign privileges)
    • Perform database tuning and performance monitoring
    • Perform application tuning and performance monitoring
    • Setup and maintain documentation and standards
    • Plan growth and changes (capacity planning)
    • Work as part of a team and provide 7x24 support when required
    • Perform general technical trouble shooting and give consultation to development teams
    • Interface with Oracle Corporation for technical support.
    • Patch Management and Version Control

    DBA Skills Required

    • Good understanding of the Oracle database, related utilities and tools
    • A good understanding of the underlying operating system
    • A good knowledge of the physical database design
    • Ability to perform both Oracle and operating system performance tuning and monitoring
    • Knowledge of ALL Oracle backup and recovery scenarios
    • A good knowledge of Oracle security management
    • A good knowledge of how Oracle acquires and manages resources
    • A good knowledge Oracle data integrity
    • Sound knowledge of the implemented application systems
    • Experience in code migration, database change management and data management through the various stages of the development life cycle
    • A sound knowledge of both database and system performance tuning
    • A DBA should have sound communication skills with management, development teams, vendors and systems administrators
    • Provide a strategic database direction for the organisation
    • A DBA should have the ability to handle multiple projects and deadlines
    • A DBA should possess a sound understanding of the business

    Application Database Administrator (ADBA)

    Application DBA's or ADBA's are responsible for looking after the application tasks pertaining to a specific application. This includes the creation of database objects, snapshots, SQL tuning, etc.

    Typical ADBA responsibilities:

    • Implement and maintain the database design
    • Create database objects (tables, indexes, etc.)
    • Write database procedures, functions and triggers
    • Assist developers with database activities
    • Tune database queries
    • Monitor application related jobs and data replication activities


    2. what are the daily activities of an APPSDBA And DBA ?*****

    Daily Activities of Oracle Database Administrator

    Daily Work of DBA:

    1: Health check of the Database.
    2: Viewing the Alert log file to analyze the ORA errors if any.
    3: Tablespace Utilization.
    4: Rebuilding of Indexes, if bulk load of data is inserted.
    5: Viewing the temporary files, through the DBA_TEMP_FILES.
    6: Database Growth Comparision.
    7: User Management.
    8: Backing up the archive log files.
    9: Monitoring Backups.
    10: Monitoring the log files, backups, database space usage and the use of system resources.
    11: Exports/Imports
    12: User Management
    13: Monitoring Tablespace Segments
    14: Monitoring Production Database Performance
    15: Solving the ORA errors.
    16: Take a COLD/RMAN backups at night time.




    Weekly Work of DBA:


    1: Growth of the Database.
    2: Total full backup of the database through hot backup.
    3: Taking logical backups, in case of physical backups failure.
    4: Taking weekly Tablespace backup.




    Monthly Work of DBA:

    1: Index Rebuild.
    2: Tablespace Reorganization.



    Quarterly Work of DBA:

    1: Patching
    2: Database Reorganization



    Below are my complete skill set in Oracle Applications:


    o Cloning of Database, Oracle Applications 11i/R12 (single node and multi node, RAC to RAC and non-RAC)
    o Upgrade of Oracle applications database 9.2.0.6 to 10.2.0.4,10.2.0.5 to 11.2.0.3.
    o Upgrade of Oracle applications from11.5.10.2 to R12.0.6,12.1.2/3.
    o DB and EBS Patch application
    o Monitoring application and databases.
    o Automation of Application DBA daily activities using shell scripts.
    o Support and maintain development and production instances.
    o Extensive Knowledge in Oracle E-Business Suite.
    o Extensive Oracle RDBMS Skills in Windows, Linux, UNIX platforms.
    o Conceptual knowledge of Oracle Applications DMZ, Data Guard.
    o Involved in POC Proof of Concept preparation.
    o R12 Installation and Implementation.
    o PCP Configuration.
    o Shared Application Implementation.
    o Cloning of Oracle Applications 11i/R12 to single node and multi node.
    o RAC to RAC and non-RAC cloning.
    o Had knowledge on 11g Discover setup and Integrating with oracle applications. Deploying the system components like OBIEE,Discoverer,SOA,Agile PLM & Auto Vue setup on fusion middleware.
    o NLS patches, RUP patches and quarterly security CPU patches application
    o Involved in Upgrade of Oracle applications database 9.2.0.6 to 10.2.0.6.
    o Take part in Upgrade of Oracle applications from11i to R12 and R12.1.
    o Monitoring application and databases.
    o Performance tuning.
    o Automation of Application DBA daily activities using shell scripts like refresh ,huge patching etc.
    o Support and maintain development and production instances.
    Specialties

    ***Strong in troubleshooting the issues in relating to individual Form/Report/Page Login issues etc..
    -- Debugging the issues after refresh.
    ***Good understanding towards the Architecture Flow in 11i and R12 with there features.
    ** Good in understanding the issue related to oracle applications and find the RCA.


    3. Tell about your current projects?****

    Self preparation required .


    4. What kind of calls you recieve from the client?|**

    Self preparation required .


    5. what kind of ticket issues faced/raises on regular interval .

    Self preparation required .


    6. A person cannot able to see login page. Give Step by step solution?

    Many front reasons. (Like entry on host file)

    Sever and solutions are:

    Problem:
    1. After cloning environement OA R12
    – Cloning terminated OK
    – Adconfig terminated OK
    - Process Oracle application are launched without error
    – Connection to database is OK
    2. Trying to access the environment: Login Page not displayed (No Error Displayed)

    Solution:
    1. Shut down the Application Tier
    2.Run “ojspCompile.pl” from $FND_TOP/patch/115/bin
    perl ojspCompile.pl –compile –flush -p 2
    3. Run autoconfig on both db and apps tiers
    4. Bring up the services and test login

    Could be other

    7. What is your team size?**

    Self preparation required .


    8. Tell the reason for change?*****
    Self preparation required .


    9. What is ADSPLICE UTILITY**

    http://www.reachdba.com/showthread.p...light=ADSPLICE

    10. Explain an ORA-01555.

    The ORA-01555 is caused by Oracle read consistency mechanism. If you have a long running SQL that starts at 10:30 AM, Oracle ensures that all rows are as they appeared at 10:30 AM, even if the query runs until noon!
    Oracles does this by reading the "before image" of changed rows from the online undo segments. If you have lots of updates, long running SQL and too small UNDO, the ORA-01555 error will appear.
    From the docs we see that the ORA-01555 error relates to insufficient undo storage or a too small value for the undo_retention parameter:
    ORA-01555: snapshot too old: rollback segment number string with name "string" too small

    Cause: Rollback records needed by a reader for consistent read are overwritten by other writers.

    Action: If in Automatic Undo Management mode, increase the setting of UNDO_RETENTION. Otherwise, use larger rollback segments.
    You can get an ORA-01555 error with a too-small undo_retention, even with a large undo tables. However, you can set a super-high value for undo_retention and still get an ORA-01555 error. Also see these important notes on commit frequency and the ORA-01555 error

    11. Roll of APPS and DATABASE Listener.

    Database listener

    From DB stand, there is only one listener. It listens to new connections who is trying to connect to DB server. If the listener goes down, new users would not be able to connect to DB server. But still, already connected users would be able to do their work normally.
    Apps Listener
    Apps listener is the combination of FNDFS and FNDSM. FNDSM is service manager which will monitor application services on that node when GSM:enable profile value is ‘Y’.

    Or
    Apps Listener usually running on All Oracle Applications 11i Nodes with listener alias as APPS_$SID is mainly used for listening requests for services like FNDFS & FNDSM.

    12. What problems/errors you faced in Frontend.****

    Self preparation required .


    13. If Somebody delete the table then how you resore it?**

    Self preparation required . (easy but tricky only experience one can give good answere)

    However,

    Good answer could be for:

    I emptied the recycle bin and I need the table back or I will lose my job. How do I recover a dropped table? Can I restore the table and recover the dropped table without affecting other objects of the database?
    DBAs get fired for dropping production tables, so act quickly! DDL like drop table cannot be rolled-back, and you have lost your recycle bin, but you still have several options for recovering a dropped table:
    • Data pump exports - If you care about the data in this table, you would have exported it nightly.
    • RMAN - You can recover a single dropped table by restoring the entire database into your test environment using RMAN, and then roll forward. You can then extract the table and copy it from test to production using CTAS over a database link and then re-add the indexes and constraints.
    • LogMiner - Oracle LogMiner can used to recover a dropped table. See here, the steps to recover a dropped table using LogMiner.
    • Flashback - It's easy to recover a dropped table with these steps in flashback.
    Here is an example of recovering a dropped table with flashback. To recover the table we first check to see that it resides in the recyclebin, and then we issue the “flashback table to before drop” command to recover the table:
    SQL> drop table mytab;

    Table dropped.

    SQL> select original_name from dba_recyclebin;

    ORIGINAL_NAME
    --------------------------------
    MYTAB

    SQL> flashback table MYTAB to before drop;

    Flashback complete.

    SQL> select * from mytab;

    ID
    ----------
    2
    2


    14. What is the size of os block and db block can we change it?

    A DB block can be one or multiple of os block.

    15. What is rman? Use of RMAN? Do you know RMAN Cloning?

    One (if not the, most important) jobs of the Oracle DBA is to ensure that the databases in their care are protected. Databases, or data in the database, can be lost through a variety of ways including:
    * User error
    * Hardware failure
    * Software failure
    * Disasters
    * Application errors
    To protect your database, you will need to know how to back it up and you will need to know how to recover your database. Backup and recovery is what this last chapter is all about. Backup and recovery can be a very difficult and complex topic, for there are a number of different options for you to choose from when it comes to backing up a database. In this chapter, we aim to set you on the right course, showing you how to perform basic database backup and recovery operations.
    In this chapter we will use the Oracle RMAN tool. It comes with the Oracle RDBMS and it’s free. In this chapter we will cover:
    * Backing up your database with RMAN
    * Restoring your database with RMAN
    So, without further delay, let’s get started on getting your database backed up.
    Backup Your Database with RMAN
    Database backups with RMAN are actually quite easy. Your database can be in one of two modes, ARCHIVELOG or NOARCHIVELOG mode. The mode your database is in determines what kinds of backups you can perform on your database. In this section we will cover the following topics:
    Starting RMAN
    The RMAN client is started from the operating system prompt. To use RMAN, simply set the Oracle environment as you would before you use any other Oracle client (like SQL*Plus). Once the environment is set, then you start RMAN as seen in this example:
    rman target=/
    Once you have started RMAN you will find yourself at the RMAN prompt. We are then ready to begin our database backup.
    Perform an Offline (Cold) Backup of your Database with RMAN
    In this section we will show you how to perform an offline (or cold) backup using RMAN. This will require that the database be down (that’s why it’s called an offline backup). Oracle supports online backups also, and we will be covering these shortly.
    Before we can use RMAN we need to configure a few settings. In this section we will look at configuring the database for our backup, and then we will proceed to do the backup.
    Configure Oracle and RMAN for Backup
    Before we can use RMAN we will need to configure a few settings. In this section we will assume:
    1. That you will be backing up to a file system called /u01/app/oracle/backup. You will need to create this file system if it does not already exist.
    2. That you are using an SPFILE.
    Note that if you created your database as we described earlier in the book, you should already be using an SPFILE.
    The configuration is pretty basic. First, we need to configure a couple of database parameters. These parameters will configure the Flash Recovery Area of the database.
    This is the location that all the disk backups will be made to. To configure the flash recovery area we will use the alter system command to set the value of two database parameters:
    * db_recovery_file_dest – Determines the location of the flash recovery area.
    * db_recovery_file_dest_size – Determines how much space can be used by Oracle in the flash recovery area.
    We will configure the flash recovery area to the value of /u01/app/oracle/backup, and we will assign it a 2 Gigabyte limit. Note! Oracle flash recovery area re-named to fast recovery area
    You may need to assign your flash recovery area more space depending on the following factors:
    * The size of your database
    * The number of backups you want to keep
    * If you are running your database in ARCHIVELOG mode (which we will discuss later in this chapter).
    Here is an example of configuring the flash recovery area for the settlings listed previously. This assumes your database is using a SPFILE which we discussed in earlier chapters:
    Alter system set db_recovery_file_dest=’/u01/app/oracle/backup’;
    Alter system set db_recovery_file_dest_size=2G;
    We will also want to set a couple of RMAN settings before we do our first backup. Start RMAN as detailed earlier in this section with:
    $ rman target /
    Now, we want to configure the following:
    * Automatic backups of the control file and SPFILE.
    * Retention policy to a redundancy of 2
    Next, we can use the RMAN configure command to configure these settings as seen in this example:
    -- Configure the retention policy to redundancy of 2.
    -- This means RMAN will try to keep 2 copies of the database backups.

    RMAN> configure retention policy to redundancy 2;

    -- Configure automated backups of the control file and SPFILE.

    RMAN>configure controlfile autobackup on;
    Now that RMAN and the database are configured, we are ready to proceed to backup the database.


    16. What Issues we face in managing Datafiles and tablespaces?

    Issue could be any where mainly we handle

    • Creating Tablespaces
    • Specifying Nonstandard Block Sizes for Tablespaces
    • Controlling the Writing of Redo Records
    • Altering Tablespace Availability
    • Using Read-Only Tablespaces
    • Renaming Tablespaces
    • Dropping Tablespaces
    • Managing the SYSAUX Tablespace
    • Diagnosing and Repairing Locally Managed Tablespace Problems
    • Migrating the SYSTEM Tablespace to a Locally Managed Tablespace
    • Transporting Tablespaces Between Databases


    17. How to find Tablespace Size?

    Query 

    col "Tablespace" for a22
    col "Used MB" for 99,999,999
    col "Free MB" for 99,999,999
    col "Total MB" for 99,999,999

    select df.tablespace_name "Tablespace",
    totalusedspace "Used MB",
    (df.totalspace - tu.totalusedspace) "Free MB",
    df.totalspace "Total MB",
    round(100 * ( (df.totalspace - tu.totalusedspace)/ df.totalspace))
    "Pct. Free"
    from
    (select tablespace_name,
    round(sum(bytes) / 1048576) TotalSpace
    from dba_data_files
    group by tablespace_name) df,
    (select round(sum(bytes)/(1024*1024)) totalusedspace, tablespace_name
    from dba_segments
    group by tablespace_name) tu
    where df.tablespace_name = tu.tablespace_name ;

    18. Have you use R12 in current Project?****

    Self preparation required


    19. During Patching you shutdown CM , What happen to running Concurrent Manager request.

    During patching you need to close all other services also, its mean you can not work with your EBS if patch mention you need to close apps side
    When performing a normal shutdown of the CM, it waits for the running processes to complete. So, if there are any running processing processes on the system, the concurrent managers may not shutdown.

    It is not recommended to use the kill -9 command. If you want to shutdown the CM while there are running requests, you can change the status of the requests, and shutdown the CM then. When you terminate requests and deactivate an individual manager, requests that are currently running are immediately stopped and marked for resubmission (when the manager is activated).


    20. What error you faced recently and how you troubleshoot it.*****

    Self preparation required


    21. How frequently you take support from Oracle Support Team & what types of errors.**

    (Nice and tricky question Expert Opinion required )


    22. What are the prerequisites during installation of oracle and apps 11i.

    Ensure that /etc/hosts and /etc/oraInst.loc are set right:
    Create OS User:
    Set Kernel Parameters:
    Increase user limits: Add the following to /etc/security/limits.conf

    Add the user Oracle to /etc/profile
    Ensure the following RPMs are installed:

    And many more depands on os


    23. Backup strategy in your environment., retention policy?**

    Self preparation required


    24. What is AutoConfig?*

    AutoConfig is a tool that simplifies and standardizes configuration management tasks in an Oracle E-Business Suite environment. A fresh install of Release 12 includes AutoConfig as a standard (and required) configuration management tool. AutoConfig can also be used with earlier releases of Oracle E-Business Suite.
    Configuring a new installation of Oracle E-Business Suite includes a number of stages:
    • Collection of information required to create the desired configuration
    • Storage of configuration information in the correct locations on the relevant machines
    • Creation of technology stack configuration files with the appropriate details
    • Creation of Applications configuration files with the appropriate details
    • Starting of all required processes in the correct order


    25. If the request is running from a long time then what would be troubleshooting.

    Step 1 : Check Concurrent Request ID of long running concurrent request from front end
    Step 2 : Find SID, SERIAL# and SPID by running SQL (given below)
    Step 3 : Enable event 10046 trace with level 12 using oradebug ( for 15-20 minute)
    Step 4 : Disable trace (once you are happy with trace size)
    Step 5 : Convert raw trace to TKPROF using various sort options like fchela, prsela, execpu
    Step 6 : Check TKPROF out file to find root cause of slow concurrent request
    .

    Step 1 : Check Request ID from Find Concurrent request screen (for example Request ID is 2355)
    Step 2 : Run below command to find SPID, provide concurrent request ID (2355 in my case) when prompted
    SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process , c.SPID
    FROM apps.fnd_concurrent_requests a,
    apps.fnd_concurrent_processes b,
    v$process c,
    v$session d
    WHERE a.controlling_manager = b.concurrent_process_id
    AND c.pid = b.oracle_process_id
    AND b.session_id=d.audsid
    AND a.request_id = &Request_ID
    AND a.phase_code = ‘R’;
    REQUEST_ID SID SERIAL# OSUSER PROCESS SPID
    —————-
    2355 514 28 applmgr 17794 1633.
    .

    Step 3.1 : Check and confirm SPID on Database Node
    oraclevis11i@onlineappsdba>ps-ef | grep 1633
    ovis11i 1633 1 0 13:30:43 ? 0:03 oraclevis11i (LOCAL=NO)
    Step 3.2 : Set OSPID (1633 in my case) for ORADEBUG
    SQL> oradebug setospid 1633

    Oracle pid: 68, Unix process pid: 1633, image: oraclevis11i@onlineappsdba

    Step 3.3 : Enable trace for 10046 event with level 12

    SQL> oradebug event 10046 trace name context forever, level 12

    Step 3.4 : Locate Trace file as
    SQL>oradebug tracefile_name
    /oracle/apps/vis11idb/10.2.0/admin/vis11i_onlineappsdba/udump/vis11i_ora_1633.trc
    Wait for 15-20 minutes
    Step 4 : Disable trace
    SQL> oradebug event 10046 trace name context off

    Step 5: Create tkprof file like
    tkprof ‘/oracle/ apps/ vis11idb/ 10.2.0/ admin/ vis11i_onlineappsdba/ udump/ vis11i_ora_1633.trc’ ’/oracle/ apps/ vis11idb/ 10.2.0/ admin/ vis11i_onlineappsdba/ udump/ tkprof_1633.txt’ explain=apps/[apps_passwd] fchela …
    Step 6 : Check TKPROF file to find root cause of slow concurrent requet
    .
    References
    • 39817.1 Interpreting Raw SQL_TRACE and DBMS_SUPPORT.START_TRACE output
    • 32951.1 Tkprof Interpretation
    • ORADEBUG event tracing from dba-oracle
    • dbaanswers.blogspot.com script for slow concurrent request


    26. How you will keep concurrent request in hold.

    All reports and programs in Oracle Applications run as concurrent processes whether you submit them using the Submit Requests window, or using a product-specific submission window. Throughout this guide we refer to submitted reports and programs as concurrent requests, or simply as requests.
    Each concurrent request runs according to a set of concurrent processing options.
    Default Values of Concurrent Processing Options
    The default values of the concurrent processing options are determined by the values of the following user profile options:
    o Concurrent:Hold Requests--Specifies whether to hold a request temporarily
    o Concurrent:Report Access Level--Specifies who has access to report and log files
    o Concurrent:Report Copies--Specifies the number of copies of a report to print
    o Concurrent:Request Priority--Specifies the priority of a concurrent request
    o Concurrent:Request Start Time--Specifies the start date and time for a concurrent request
    o Concurrent:Save Output--Specifies whether to save report output to a file
    o Concurrent:Sequential Requests--Specifies whether to run your requests sequentially
    o Printer--Specifies the printer to print your report output
    (source oracle doc)/


    27. common issues in concurrent manager ?****

    1. Issues related to startup/shutdown of CM
    2. ICM is Up but some managers are still down



    28. Conflict resolution manager function?

    Concurrent managers read request to start concurrent programs running. The
    Conflict Resolution Manager checks concurrent program definitions for
    incompatibility rules.

    If a program is identified as Run Alone, then the Conflict Resolution Manager
    prevents the concurrent managers from starting other programs in the same
    conflict domain.

    When a program lists other programs as being incompatible with it, the Conflict
    Resolution Manager prevents the program from starting until any incompatible
    programs in the same domain have completed running.


    If the Conflict Resolution Manager fails, the Internal Manager will restart the
    Conflict Resolution Manager, or will process incompatibilities if the profile
    option Concurrent: Use ICM is set to Yes.


    29. Have you applied cu2 patch?

    Answere could be

    No. Release 12.1.1 CUP1 is applicable only if you are upgrading your E-Business Suite Release 11i instance to Release 12.1.1. If your Oracle E-Business Suite instance is already at Release 12 or higher (e.g. Release 12.0.4), you should not apply Release 12.1.1 CUP1.
    The Consolidated Upgrade Patch 1 (CUP1) for Release 12.1.1 combines critical upgrade error corrections and upgrade performance improvements from Release 11i into a consolidated suite-wide patch.


    Who should use it?


    Customers who are upgrading to Release 12.1.1 from Release 11.5.9 (base, CU1, CU2) or Release 11.5.10 (base, CU1, CU2) should apply Release 12.1.1 CUP1.

    How does it differ from the Family Consolidated Upgrade Patch (FCUP) in Release 11i?


    In Release 11i, Family Consolidated Upgrade Patches (FCUP) were the release vehicles used to ship consolidated upgrade-related patches from all products within a product family. In R12, the term Consolidated Upgrade Patch (CUP) has been coined to ship critical upgrade error corrections and upgrade performance improvements across all the product families in Oracle E-Business suite.



    30. What are the errors you face in daily routine.**

    Check Web Server is Up :

    Oracle Applications DBA Field Guide

    Check in browser http://hostname.domainnameort where hostname.domain_name is Machine Name on which Web Server is running.

    Check Jserv is Up :

    Oracle Applications DBA Field Guide

    Check if you can access OAM (Oracle Application Manager) page. http://hostname.domainname:port_numb...m/oam/oamLogin If you can't access login screen for OAM, check logs.

    Check mod_pls is working fine :

    Oracle Applications DBA Field Guide

    http://hostname.domainnameort/pls/$SID so if you installed vision instance with SID as VIS11I your SID here is VIS11II this sometime in documents also called as TWO_TASK. You should see output from procedure FND_WEB.PING . If not check that -
    A) database listener is Up
    B) GUEST User is not end dated & password is correct.
    C) dbc (database connect descriptor) file is corerct at $FND_TOP/secure
    D) apps password is correct in wdbsvr.app at $IAS_ORACLE_HOME/Apache/modplsql/cfg

    Login to Application :

    Oracle Applications DBA Field Guide

    Login to application with Application User to confirm login is working fine , if not check mod_pls for any issues.

    Check Form Server is working :

    Oracle Applications DBA Field Guide

    Click on any Core Responsibility like "System Administrator", If you are facing any problem opening form Applet
    A) Check jinitiator is installed, if not do you have access to install jinitiator
    B) Try clearing cache from jinitiator
    C) Check forms server parameters are configured properly in appsweb_$CONTEXT_NAME.cfg
    D) Check if form server listener is Up : netstat -an | grep form_server_port

    Check Concurrent Manager is Up & Running :

    Oracle Applications DBA Field Guide

    Select "Administer Concurrent Manager" & check if "Actual" & "Target" are same.

    Check Reports can display properly :

    Oracle Applications DBA Field Guide

    Change "Active Users" reports output from "Text file" to "PDF" from Define Concurrent Request Screen. Submit Active Users request & click on Output , check if you can se report in PDF format.

    Check Apps Listener is Up :

    Oracle Applications DBA Field Guide

    Apps listener is different from database listener, Apps Listener is used for various purpose one is to check output & log files in concurrent requests. Check if apps listener is fine by clicking on log file & output file for Active Users request you submitted in Step 7 on previous page. If you encounter any issues while trying to access Log & Output file issue might be with Oracle Apps Listener. Check if adalnctl.sh (where ad is apps dba, aln is apps listener and ctl is control) on application tier started successfully. If yes then check this query (select logfile_name, logfile_node_name, outfile_name, outfile_node_name from fnd_concurrent_requests where request_id=[your request id number].

    Check if Workflow is Up :

    Oracle Applications DBA Field Guide

    Login to OAM (Oracle Application Manager) using url mentioned in step 2 in previous page. After login, On top right of page from "Nevigate to" select "Workflow Manager" from drop down menu and click on GO button. Check "Notification Mailers" is Up .

    Check if Discoverer 4i is Up : There are two type of discoverer 4i
    Discoverer Viewer - Check http://yourhostnameort/discoverer4i/viewer
    Discoverer Plus Check http://yourhostname:port/discwb4/htm...sh/welcome.htm



    31. How will you get the assigning of a job:
    Expert opinion required


    32. Why we need downtime?
    Self preparation required


    33. Mandatory Background processes. With details.

    • Process Monitor Process (PMON)
    The process monitor (PMON) monitors the other background processes and performs process recovery when a server or dispatcher process terminates abnormally. PMON is responsible for cleaning up the database buffer cache and freeing resources that the client process was using. For example, PMON resets the status of the active transaction table, releases locks that are no longer required, and removes the process ID from the list of active processes.
    PMON also registers information about the instance and dispatcher processes with the Oracle Net listener When an instance starts, PMON polls the listener to determine whether it is running. If the listener is running, then PMON passes it relevant parameters. If it is not running, then PMON periodically attempts to contact it.

    • System Monitor Process (SMON)

    The system monitor process (SMON) is in charge of a variety of system-level cleanup duties. The duties assigned to SMON include:
    Performing instance recovery, if necessary, at instance startup. In an Oracle RAC database, the SMON process of one database instance can perform instance recovery for a failed instance.
    Recovering terminated transactions that were skipped during instance recovery because of file-read or tablespace offline errors. SMON recovers the transactions when the tablespace or file is brought back online.
    Cleaning up unused temporary segments. For example, Oracle Database allocates extents when creating an index. If the operation fails, then SMON cleans up the temporary space.
    Coalescing contiguous free extents within dictionary-managed tablespaces.
    SMON checks regularly to see whether it is needed. Other processes can call SMON if they detect a need for it.

    • Database Writer Process (DBWn)

    The database writer process (DBWn) writes the contents of database buffers to data files. DBWn processes write modified buffers in the database buffer cache to disk (see "Database Buffer Cache").
    Although one database writer process (DBW0) is adequate for most systems, you can configure additional processes—DBW1 through DBW9 and DBWa through DBWj—to improve write performance if your system modifies data heavily. These additional DBWn processes are not useful on uniprocessor systems.
    The DBWn process writes dirty buffers to disk under the following conditions:
    When a server process cannot find a clean reusable buffer after scanning a threshold number of buffers, it signals DBWn to write. DBWn writes dirty buffers to disk asynchronously if possible while performing other processing.
    DBWn periodically writes buffers to advance the checkpoint, which is the position in the redo thread from which instance recovery begins . The log position of the checkpoint is determined by the oldest dirty buffer in the buffer cache.
    In many cases the blocks that DBWn writes are scattered throughout the disk. Thus, the writes tend to be slower than the sequential writes performed by LGWR. DBWn performs multiblock writes when possible to improve efficiency. The number of blocks written in a multiblock write varies by operating system.

    Log Writer Process (LGWR)

    The log writer process (LGWR) manages the redo log buffer. LGWR writes one contiguous portion of the buffer to the online redo log. By separating the tasks of modifying database buffers, performing scattered writes of dirty buffers to disk, and performing fast sequential writes of redo to disk, the database improves performance.
    In the following circumstances, LGWR writes all redo entries that have been copied into the buffer since the last time it wrote:
    A user commits a transaction (see "Committing Transactions").
    An online redo log switch occurs.
    Three seconds have passed since LGWR last wrote.
    The redo log buffer is one-third full or contains 1 MB of buffered data.
    DBWn must write modified buffers to disk.
    Before DBWn can write a dirty buffer, redo records associated with changes to the buffer must be written to disk (the write-ahead protocol). If DBWn finds that some redo records have not been written, it signals LGWR to write the records to disk and waits for LGWR to complete before writing the data buffers to disk.
    [B][B] LGWR and Commits

    Oracle Database uses a fast commit mechanism to improve performance for committed transactions. When a user issues a COMMIT statement, the transaction is assigned a system change number (SCN). LGWR puts a commit record in the redo log buffer and writes it to disk immediately, along with the commit SCN and transaction's redo entries.
    The redo log buffer is circular. When LGWR writes redo entries from the redo log buffer to an online redo log file, server processes can copy new entries over the entries in the redo log buffer that have been written to disk. LGWR normally writes fast enough to ensure that space is always available in the buffer for new entries, even when access to the online redo log is heavy.
    The atomic write of the redo entry containing the transaction's commit record is the single event that determines the transaction has committed. Oracle Database returns a success code to the committing transaction although the data buffers have not yet been written to disk. The corresponding changes to data blocks are deferred until it is efficient for DBWn to write them to the data files.
    Note:

    LGWR can write redo log entries to disk before a transaction commits. The redo entries become permanent only if the transaction later commits.
    When activity is high, LGWR can use group commits. For example, a user commits, causing LGWR to write the transaction's redo entries to disk. During this write other users commit. LGWR cannot write to disk to commit these transactions until its previous write completes. Upon completion, LGWR can write the list of redo entries of waiting transactions (not yet committed) in one operation. In this way, the database minimizes disk I/O and maximizes performance. If commits requests continue at a high rate, then every write by LGWR can contain multiple commit records.
    LGWR and Inaccessible Files
    LGWR writes synchronously to the active mirrored group of online redo log files. If a log file is inaccessible, then LGWR continues writing to other files in the group and writes an error to the LGWR trace file and the alert log. If all files in a group are damaged, or if the group is unavailable because it has not been archived, then LGWR cannot continue to function

    Checkpoint Process (CKPT)


    The checkpoint process (CKPT) updates the control file and data file headers with checkpoint information and signals DBWn to write blocks to disk. Checkpoint information includes the checkpoint position, SCN, location in online redo log to begin recovery, and so on. As shown in Figure 15-4, CKPT does not write data blocks to data files or redo blocks to online redo log files.


    Please note: Some people don’t count below process, it but it is good to know and can count as mandatory process of oracle

    • Manageability Monitor Processes (MMON and MMNL)
    Manageability Monitor Processes (MMON and MMNL)
    The manageability monitor process (MMON) performs many tasks related to the Automatic Workload Repository (AWR). For example, MMON writes when a metric violates its threshold value, taking snapshots, and capturing statistics value for recently modified SQL objects.
    The manageability monitor lite process (MMNL) writes statistics from the Active Session History (ASH) buffer in the SGA to disk. MMNL writes to disk when the ASH buffer is full.


    • Recoverer Process (RECO)

    In a distributed database, the recoverer process (RECO) automatically resolves failures in distributed transactions. The RECO process of a node automatically connects to other databases involved in an in-doubt distributed transaction. When RECO reestablishes a connection between the databases, it automatically resolves all in-doubt transactions, removing from each database's pending transaction table any rows that correspond to the resolved transactions.

    34. printer set up ?

    http://docs.oracle.com/cd/E18727_01/...296T174303.htm


    35. Oracle EBS Login Page Error**

    Please review Apache log files for any errors

    Clear the log files first (take a backup), reproduce the issue, and check the log files contents.

    Also, please verify that you have setup your browser as per the steps in the document referenced below.

    Note: 285218.1 - Recommended Browsers for Oracle E-Business Suite 11i
    https://metalink2.oracle.com/metalin...&p_id=285218.1



    36. What steps you follow when user complain about database slowness.

    Follow below steps every time when you heard about performance issue from user.

    1. Find out top consuming process in DB
    2. Find out percentage of CPU consumption of that process
    3. See whether complained user and top consuming session is sharing same kind of data, If not, go for step 4
    4. Enable trace at session level for the complained user. If you have Oracle EBS, you can go to "Help==>Diagnostics==>Trace==>Trace with binds and waits". Turn off trace once after user tried his performance issue area.
    5. If you don't have EBS, try getting trace from DB and collect trace from udump dir and collect tkprof. Identify top SQL in tkprof and tune that.

    4 & 5 steps are only when user complained saying that if he is facing issue in particular functionality. If user is facing over all performance.

    Then use 1,2,3 and also find any huge jobs like payroll or some other programs are running in database. Also see whether anyone is cleaning any temp directory or any other directories.

    Best way to find issue quickly other than going to above steps is getting AWR for time frame and investigating on AWR.



    37. How you will unable trace for a particular session.

    There are a number of ways to trace a session:
    1. Enable trace at the beginning of your session
    2. Enable trace of a running session
    1. Enable tracing at the begin of your session
    To enable tracing for a particular session we will need to set the Oracle event 10046.
    This event contains a level which can be combined using a logical OR relation to mix different trace functions.
    This is what the different levels are used for:
    1 Enable statistics for parse, execute, fetch, commit and rollback operations.
    This is the same as doing a ‘alter session set sql_trace=true’ SQL call.
    2 No information available
    4 Enable tracing of bind variables
    8 Enable tracing for wait events. These should match the events as found in v$event_name
    As said before we can combine the different levels to enable combination’s of tracing.
    A level of 12 means that we will trace bind variables as well as wait events. When setting the level to a value other than zero, level 1 will also be activated. So setting the level to 12 also enables tracing for parse, execute, fetch,… operations.
    – To enable tracing
    alter session set events '10046 trace name context forever, level 12'

    --To stop tracing of the current session
    alter session set events '10046 trace name context off'
    Enable trace of a running session
    In order to enable tracing for a running application, one can use the dbms_system package.
    -- to enable tracing for another sid, serial# pair
    sys.dbms_system.set_ev( sid, serial#, 10046, 12, '');

    -- to disable tracing.
    sys.dbms_system.set_ev( sid, serial#, 10046, 0, '');
    Alternatively, to just enable a level 1 trace:
    -- to enable tracing for another sid, serial# pair
    sys.dbms_system.set_sql_trace_in_session(sid, serial#, true);
    -- to disable tracing.
    sys.dbms_system.set_sql_trace_in_session(sid, serial#, false);
    When your application require frequent tracing for a particular setting, one might think about including an option into the application which – when enabled – just starts tracing the session.
    Alternatively, you can create a schema logon trigger which enables tracing when a user logs on to the schema.


    38. How you will generate AWR report and what you check in AWR report.


    There are few scripts that can be used to generate AWR HTML or text reports.

    @?/rdbms/admin/awrrpt.sql –
    It is an interactive script that can be used to generate HTML or text reports. The script prompts for type of report requested and prompts for number of days of snapshots to choose from so based on that it displays snap ids to choose the start and end snapshot it.

    Specify the Begin and End Snapshot Ids
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Enter value for begin_snap: 795
    Begin Snapshot Id specified: 795
    Enter value for end_snap: 800
    End Snapshot Id specified: 800
    Specify the Report Name
    ~~~~~~~~~~~~~~~~~~~~~~~
    The default report file name is awrrpt_1_795_800.html. To use this name,
    press to continue, otherwise enter an alternative.
    ..
    Another way of generating a report is one can query dba_hist_snapshot to find the snap id for the interval you are looking for.
    SQL> column begin_interval_time format a25
    SQL> column end_interval_time format a25
    SQL> SELECT dbid, snap_id, begin_interval_time, end_interval_time from dba_hist_snapshot order by begin_interval_time;
    DBID SNAP_ID BEGIN_INTERVAL_TIME END_INTERVAL_TIME
    ———- ———- ————————- ————————-
    SQL> SELECT output FROM TABLE (dbms_workload_repository.awr_report_text(19928788 07, 1, 799, 800));
    @?/rdbms/admin/awrrpti.sql – Script can be used for the specified database and instance so the script in addition will prompt for dbid and instance number.

    @?/rdbms/admin/awrddrpt.sql – Script can be used to generate a combine report of 2 different snapshots for comparison of performance in one report so it will prompt for two pairs of snapshot snapshots to compare against.

    @?/rdbms/admin/awrinfo.sql – Script print AWR information like space usage by AWR, subset of AWR snap ids, Automatic Database Diagnostic Monitor (ADDM), Active Session History (ASH) information.

    Use STATSPACK but are not always sure what to check regularly. Remember to separate OLTP and Batch activity when you run STATSPACK, since they usually generate different types of waits. The SQL script "spauto.sql" can be used to run STATSPACK every hour on the hour. See the script in $ORACLE_HOME/rdbms/admin/spauto.sql for more information (note that JOB_QUEUE_PROCESSES must be set > 0). Since every system is different, this is only a general list of things you should regularly check in your STATSPACK output:
    • Top 5 wait events (timed events)
    • Load profile
    • Instance efficiency hit ratios
    • Wait events
    • Latch waits
    • Top SQL
    • Instance activity
    • File I/O and segment statistics
    • Memory allocation
    • Buffer waits


    39. Custum top in oracle apps.**

    Custom Top is nothing but Customer Top, which is created for customer only. we can have multiple custom tops based on client requirement. It is used to store developed & customized components. whenever oracle corp appling patches it will over ride on all the modules except custom top. that's why we will use custom top.
    40. How to find the CPU utilization?

    Old good top command to find out Linux cpu load
    The top program provides a dynamic real-time view of a running system. It can display system summary information as well as a list of tasks currently being managed by the Linux kernel.
    The top command monitors CPU utilization, process statistics, and memory utilization. The top section contains information related to overall system status - uptime, load average, process counts, CPU status, and utilization statistics for both memory and swap space.
    Top command to find out Linux cpu usage
    Type the top command:

    $ top

    Find Linux CPU utilization using mpstat and other tools
    Please note that you need to install special package called sysstat to take advantage of following commands. This package includes system performance tools for Linux (Red Hat Linux / RHEL includes these tools by default).
    # apt-get install sysstat
    Use up2date command if you are using RHEL:
    # up2date sysstat
    Display the utilization of each CPU individually using mpstat
    If you are using SMP (Multiple CPU) system, use mpstat command to display the utilization of each CPU individually. It report processors related statistics. For example, type command:
    # mpstat
    or
    #mpstat -P ALL
    Or
    You can display today’s CPU activity, with sar command:
    # sar
    Comparison of CPU utilization
    The sar command writes to standard output the contents of selected cumulative activity counters in the operating system. The accounting system, based on the values in the count and interval parameters. For example display comparison of CPU utilization; 2 seconds apart; 5 times, use:

    # sar -u 2 5
    Where,
    • -u 12 5 : Report CPU utilization. The following values are displayed:
    o %user: Percentage of CPU utilization that occurred while executing at the user level (application).
    o %nice: Percentage of CPU utilization that occurred while executing at the user level with nice priority.
    o %system: Percentage of CPU utilization that occurred while executing at the system level (kernel).
    o %iowait: Percentage of time that the CPU or CPUs were idle during which the system had an outstanding disk I/O request.
    o %idle: Percentage of time that the CPU or CPUs were idle and the system did not have an outstanding disk I/O request.
    • To get multiple samples and multiple reports set an output file for the sar command. Run the sar command as a background process using.

    # sar -o output.file 12 8 >/dev/null 2>&1 &

    Better use nohup command so that you can logout and check back report later on:

    # nohup sar -o output.file 12 8 >/dev/null 2>&1 &
    • All data is captured in binary form and saved to a file (data.file). The data can then be selectively displayed ith the sar command using the -f option.

    # sar -f data.file
    • Task: Find out who is monopolizing or eating the CPUs
    • Finally, you need to determine which process is monopolizing or eating the CPUs. Following command will displays the top 10 CPU users on the Linux system.

    # ps -eo pcpu,pid,user,args | sort -k 1 -r | head -10
    OR

    # ps -eo pcpu,pid,user,args | sort -r -k1 | less


    iostat command

    You can also use iostat command which report Central Processing Unit (CPU) statistics and input/output statistics for devices and partitions. It can be use to find out your system's average CPU utilization since the last reboot.

    # iostat

    You may want to use following command, which gives you three outputs every 5 seconds (as previous command gives information since the last reboot):$ iostat -xtc 5 3
    GUI tools for your laptops/desktops
    Above tools/commands are quite useful on remote server. For local system with X GUI installed you can try out gnome-system-monitor. It allows you to view and control the processes running on your system. You can access detailed memory maps, send signals, and terminate the processes.
    $ gnome-system-monitor


    41. How to test apache

    To test the status of the Apache Server-


    $apachectl status

    The return from this command is dependent on what the directive "STATUSURL" is set to in the apachectl file as well as on the availability of the lynx command. For example, if the following line is entered in apachectl:
    STATUSURL="http://myserver.acme.com:8002/pls/VIS/FND_WEB.PING"
    then the status command will return:

    $ apachectl status
    FND_WEB.PING
    SYSDATE 08-DEC-2001 06:37:24
    DATABASE VERSION Oracle8i Enterprise Edition - Production
    DATABASE ID:vision
    SCHEMA NAME APPS
    AOL VERSION 11.5
    APPS WEB AGENT http://myserver.acme.com:8002/pls/VIS
    To fully test the configuration of the Oracle HTTP Server, you can bring up the Rapid Installation Index Page , by requesting the following URL:
    http://<server>.<domain>:<port>
    for example, http://myserver.acme.com:8002, and then selecting "Apps Logon Links" from this page. This launches the Oracle Application Login page from which you can login as an Oracle Applications User, such as SYSADMIN.

    42. How u will monitor u r applications as well as database?
    [B][b] Expert Opinion required



    43. How to increase performance?

    • Optimizing Queries with Statistics
    • Optimizing Queries for Response Time
    • Optimizing Queries for Throughput
    • Parallel Queries
    • Tuning Queries with Blocking Operations

    44. Types of patches?***

    There are several different types of patches following are more common patches
    One-Off Patch
    This is simplest Patch to resolve a specific bug
    Minipack Patch
    Collection of One of Patches and enhancements related to a particular module. Alphabetic character denotes the Minipack version for the module.
    Family Pack Patch
    Collection of Minipack patches for a particular family group of application modules
    Maintenance pack patch
    This is collection of family packs that serves as point level release upgrade
    Consolidated patch
    Collection of one-off fixes for a family pack or maintenance pack Oracle Application 11.5.10 Consolidated Update 2 (CU2) is an example of consolidated patch.
    Interoperability patch
    Patch that is required for application to function with a newer version of technology stack
    NLS patch
    Patch that updates language specific information for multi language installation
    Rollup patch
    This is a collection of one off patches that update code levels for particular product
    Legislative patch
    Special patch for HR payroll customers it contains legislative data for multiple countries



    45. How to get the current Patchset level of Oracle Applications products in R12 ?

    1) Login to OAM
    (Responsibility "Oracle Applications Manager", menu "OAM Support Cart")
    and Navigate: Support Cart -> Applications Signature -> Collect -> Check "Product Information" box -> Click on "View" (eyeglasses)
    This will display the following patchset information :

    Application Name
    Current Patch Level
    Product Version
    Status (Installed, Shared Product, Inactive)
    2) The patchset level information can be retrieved directly via sqlplus with the following diagnostic script :
    $AD_TOP/sql/adutconf.sql



    46. How to Speed up the patch

    By Using Some procedures we can decrease the downtime or speeding up patching process
    1. Use a staged applications system
    This major time-saver hinges on a key principle: all of your applications filesystem patches are applied to a clone of your production Apps environment. This can be done while your production system is still running. Your production system is down only for the time needed to apply database patches. For details, see:
    * Using a Staged Applications System to Reduce Patching Downtime [Release 11i] (Note 242480.1)
    * Using a Staged Applications System to Reduce Patching Downtime in Oracle E-Business Suite Release 12 (Note 734025.1)
    2. Use a shared application-tier file system
    If you have a pool of application-tier servers set up for load-balancing, make sure that all of the individual servers share a single application filesystem. Patches applied to this central shared filesystem are instantly available to all application-tier servers. I’ve previously given an overview of this technique in this article.
    3. Distribute worker processes across multiple servers
    When applying a patch that includes a large number of processes, you can reduce the downtime even further by distributing the worker processes across multiple servers on multiple nodes. Using the Distributed AD feature of AutoPatch and AD Controller, you can assign workers to run on the primary node and on other nodes that share the filesystem. See:
    Distributed AD (Metalink Note 236469.1)
    4. Merge multiple patches using AD Merge Patch
    Merging patches saves time because the AutoPatch overhead of starting a new session is eliminated for those patches that are consolidated. Duplicate linking, generating or database actions are run once only. If two patches update the same file, AD Merge Patch will save time by applying only the latest one. Patches can — and should — be merged with their listed prerequisite patches.
    For more details about this AD utility, see the Oracle Applications Maintenance Procedures guide for your Apps release.
    5. Run AD Patch in non-interactive mode
    Applying a set of patches using AD Patch in non-interactive mode eliminates the delay between successive tasks.
    6. Defer system-wide database tasks until the end
    Using adpatch options=nocompiledb,nomaintainmrc defers system-wide database tasks such as “Compile APPS schema” and “Maintain MRC” until after all patches have been applied. As of AD.H, AutoPatch automatically compiles the APPS schema and maintains MRC when applying standard patches.
    7. Avoid resource-related bottlenecks
    Patching can grind to a halt if you bump into the ceiling on your system. Before patching, make sure that you’ve enabled automatic tablespace management, and that you have sufficient hardware and free disk and temp space.
    References
    * Oracle Applications Release 11i Patching Best Practices and Reducing Downtime (Note 225165.1)
    * Using a Staged Applications System to Reduce Patching Downtime [Release 11i] (Note 242480.1)
    * Using a Staged Applications System to Reduce Patching Downtime in Oracle E-Business Suite Release 12 (Note 734025.1)
    * Oracle Applications Patching FAQ (Note 174436.1)

    47. What is the significance of FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS table?**

    When a patch is applied using adpatch it will ask number of workers. These workers are used to run some task ( executing some perl scripts, running some sql scripts....etc).

    If u check in the patch log file before assigning any job to workers the two tables
    1)fnd_install_processes
    2)ad_deferred_jobs

    are created. After the job is finished the tables are dropped automatically.

    1)fnd_install_processes - This table is used to store the information about the job given to the worker. It will insert a row for each worker when it assigned a job.

    2)ad_deferred_jobs - this table is used to store the information about the deferred jobs (jobs failed to run).



    48. Index already applied in patch application what to do?


    Cause

    The error occurs when two Patch Components directories are found in the Software Library. Particularly when you run two patch upload or download jobs, for example, an OPatch patch download job and a regular patch download job, a race condition is created, which in turn creates two directories with the name Patch Components. The Software Library does not display any error while creating these duplicate directories, but when you run the OPatch Update job, the job fails with a NullPointerException.

    Solution

    To resolve this issue, do one of the following:
    If you see two Patch Components directories in the Software Library, then delete the one that has fewer entries, and retry the failed patch upload or download job. To access the Software Library, from the Enterprise menu, select Provisioning and Patching, and click Software Library.
    If you see only one Patch Components directory, but yet see the error that states that the Oracle Software Updates already exists, then retry the failed patch upload or download.

    49. Restart files in patch.

    Restart Files

    Restart files contain information about what processing has already been completed. They are located in $APPL_TOP/admin/<SID>/restart (UNIX) or in %APPL_ TOP%\admin\<SID>\restart (Windows).
    If a utility stops during processing due to an error, or you use AD Controller (in the case of parallel processing) to shut down workers while they are performing processing tasks, you can restart the utility. If you do, it looks for restart files to determine if there was a previous session. If the files exist, the utility prompts you to continue where the processing left off, or to start a new process. If you choose to continue, it reads the restart files to see where the process left off, and continues the process from that point.
    Caution: Do not modify or delete any manager or worker restart files unless specifically directed to do so by Oracle Support Services.
    By default, AD utilities delete their restart files when processing is complete, but leave backup versions with the extensions .bak, .bk2, or .bk3.
    Warning: Restart files record passwords for your Oracle E-Business Suite products. You should restrict access to all restart files (located in $APPL_TOP/admin/<SID>/restart). If you are running a utility with options=nohidepw, the log files may also contain passwords on lines prefixed with HIDEPW.


    50. Rectify working hanging/Patch Hanging Senario?

    http://www.reachdba.com/showthread.p...-Hang-scenario



    51. How to check worker? Which option is the hidden option? adctrl Usage , Diagnosis and Resolution **

    http://www.reachdba.com/showthread.p...and-Resolution


    52. We are applying patch. It applied 90%. Then some error come then what to do

    Start AD Controller
    Follow these steps to start AD Controller:
    1. Start AD Controller with the adctrl command.
    2. (UNIX) ...lcm/ad/bin/adctrl.sh
    3. (Windows) ...lcm\ad\bin\adctrl.cmd
    It prompts you to:
    o Confirm the value of the Oracle Fusion Applications Oracle home
    o Specify an AD Controller log file. This log file is written to the current working directory. The default is adctrl.log.
    • Reviewing Worker Status
    • Determining Why a Worker Failed
    • Restarting a Failed Worker
    • Terminate a Hung Worker Process
    • Shut Down the Manager
    Reactivating the Manager
    Resolving the Error, "Unable to start universal connection pool"
    Resolving a Worker Blocked by a Session
    Resolve an Error During Conflict Checking
    Set the Environment for Troubleshooting Database Issues


    53. If Patch fail due to some error then what to do? Troubleshooting a Patch Failure - adpatch

    http://www.reachdba.com/showthread.p...ailure-adpatch


    54. What is the difference between ad_bugs and ad_applied_patches?**


    AD_BUGS:
    ========
    Holds information about the various Oracle Applications bugs whose fixes have been applied (ie. patched) in the Oracle Applications installation.


    AD_APPLIED_PATCHES:
    ===================
    Holds information about the "distinct" Oracle Applications patches that have been applied.
    If 2 patches happen to have the same name but are different in content (eg. "merged" patches), then they are considered distinct and this table will therefore hold 2 records.

    55. Steps for patching in application and database tier.

    Steps to apply a patch:

    - Stop all application services (keep the database and the database listener up and running)
    - Download the patch from Metalink
    - Copy the patch file to any directory (i.e. /u04/patches)
    - As 'applmgr' do the following:
    - Source the environment file
    - $ cd /u04/patches
    - Type 'unzip <patch_number>.zip'
    - cd <patch_number>
    - Type 'adpatch'
    - When it prompts you to enter the patch driver, type 'u<patch_number>.drv'


    Apply the patch on the database tier first then on the application tier.

    Do not forget to 'Enable Maintenance Mode' from adadmin before applying the patch. Once you apply the patch successfully, 'Disable Maintenance Mode' from adadmin.

    56. When You applied patch?

    Self preparation required



    57. Steps for cloning from multinode environment to single?

    Multi to Single Node Cloning (11 Steps)
    Scenario is that we have database which resides on server [titus].Concurrent Managers and Admin Servers are residing on same machine [titus] while Web Server and Forms Servers are residing on different server which is [dbdem].


    We are going to do cloning of this environment on target system which is [firmus].This scenario will be call Maulti to Single Node cloning.


    Step -1:
    You need to make sure that these patches exist on the Source:
    patch 4038964
    patch 4175764


    Step -2:
    Login to both application nodes and run Maintain Snapshot through adadmin utility.


    Step -3:
    Now you need to make of the node as primary node.In our case we made the [dbdem] as the primary application node.
    On the primary node you need to go to this root
    $ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
    And in there run the script
    $ perl adpreclone.pl appsTier merge
    This script will ask which nodes you want to merge and in our case we are going to merge dbdem apps and titus apps.


    Step -4:
    Now you need to login to the each apps node and go into
    $ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
    And run the script on both apps nodes
    $ perl adpreclone.pl appltop merge
    This script will merge the appltop of both the nodes.


    Step -5:
    Now you need to run the normal cloning scripts on each DB and APPS nodes.
    For database:
    $ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
    $ perl adpreclone.pl dbTier


    Step -6:
    Now shutdown all the services on all nodes including DB and APPS.Lgon to database node and create folders where you are going to copy the db and apps.
    Create users for apps and db and assign those folders to these users and give the folders the read and write permissions.


    Step -7:
    Modify the $vi /etc/oraInst.loc


    Step -8:
    Copy database and only the primary node(in our case dbdem) to target firmus folders.


    Step -9:
    Login to the secondary apps node(titus) and copy the folder
    [COMMON_TOP]/clone/appl
    To the server node folder


    [COMMON_TOP]/clone/appl


    Step -10:
    Login to the firmus the target system and in there go
    $ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
    $ perl adcfgclone.pl dbTier
    After this run the database and the listener and go to
    $ cd [COMMON_TOP]/clone/bin
    And run
    $ perl adcfglone.pl appsTier


    Step -11:
    Remove the temporary directory [COMMON_TOP]/clone/appl to reduce disk space usage.
    [B] please recheck I’m not so sure [B]



    58. common error faced while clonning ?*****


    1. While running adpreclone on EBS , APPS user locked continiously.
    Soultion – Follow metalink Note Id – ID 420001.1

    2. PDF output problem in Instance. No PDF output produced after cloning .
    Solution – Follow metalink Note Id ID 981163.1

    3. Got this in alert.log WARNING: Oracle executable binary mismatch detected.
    Solution – Follow the metal…ink Note ID – 369260.1.

    4. After cloning, forms will not launch.
    Performed the below Steps:
    EXEC FND_CONC_CLONE.SETUP_CLEAN;
    commit;
    Run the cmclean.sql scripts
    Run Autoconfig on all nodes.(DB+CM+WEB Nodes)

    5. After cloning Purge Concurrent Request and/or Manager Data request status alway is running , it is not completing.
    As per Metalink ID 1016766.102 ( OS Files are Purged from Wrong Instance when Running Purge Concurrent Requests),It is because of
    FNDCPPUR is trying to delete files it can’t access because they are belonging to the original environment.
    The following table and columns still contain PATH referencing the original environment :
    FND_CONCURRENT_REQUESTS.LOGFILE_NAME
    FND_CONCURRENT_REQUESTS.OUTFILE_NAME
    Perform the below Steps:
    a) Stop the concurrent managers.
    b) Start a SQL*Plus session as APPLSYS.
    c) Issue the following commands:
    TRUNCATE TABLE fnd_concurrent_requests;
    TRUNCATE TABLE fnd_concurrent_processes;
    UPDATE fnd_concurrent_queues
    SET running_processes = 0,
    max_processes = 0;
    COMMIT;
    d) Exit the SQL*Plus session.
    e) Restart the concurrent managers.

    6. While running adcfgclone.pl getting the Inventory problem , so enter the correct entry in /etc/oraInst.loc location.

    7. After starting the services , the listener will not coming up because of missing listener.ora file in $TNS_ADMIN location.
    Solution:
    Then Stop the APPS Services ./adstpall.sh apps/<appspwd>
    run the Autoconfig . ./adautocfg.sh
    Then start the APPS Services ./adstrtal.sh apps/<appspwd>

    59. Why we use maintenence mode?

    To ensure optimal performance and reduce downtime during patching sessions, AutoPatch requires that you enable Maintenance mode when you apply a patch. Enabling this feature shuts down the Workflow Business Events System and sets up function security so that Oracle Applications functions are unavailable to users. This provides a clear separation between normal runtime operation and system downtime for patching.

    Oracle Applications Patching Procedures

    http://download.oracle.com/docs/cd/B...at/121adpp.pdf

    Please also see (Maintenance Mode - A New Feature in 11.5.10 [ID 291901.1]), it explains the purpose of maintenance mode.

    You can still apply the application patches without enabling maintenance mode but it is not recommended -- How To Apply Patch without Enabling Maintenance Mode Maintenance Mode


    60. Difference between 11i and R12?**

    http://www.reachdba.com/showthread.p...ns-11i-and-R12


    61. If users complaining Oracle Applications 11i system is running slow , what all things you will check at broad level ?*
    First as an Over view of Oracle Applications 11i check following things

    Broad Level Steps to Check

    1. Is Gather stats schedule ? ( atleast weekly ?)
    2. Is Purge Obsolete Workflow request & concurrent request purging scheduled ?
    3. Is there any runaway process on database tier or application tier ? ( runaway process is process taking unexceptionally long time with high CPU or Memory usages)
    4. Any Discoverer process taking long time or High CPU ? ( Usually on Middle tier like dis4ws..) 5. Any Custom report taking long time ?

    In order to understand problem better

    As Next level you should ask questions to yourself or person encountering performance issues like

    1. Is whole application is slow or only component of application is slow (like only Concurrent manager running slow)
    2. If this is paritular component like reports server slow then is a particular report or all reports are slow ?
    3. Is performance issue during all time or at specific time lets say from 11AM to 4PM ?
    4. Was performance issue popped up recently or performance degradation is since long ?
    5. Whats changed recently ?


    Depending on answers you can start looking into application like if issue is specific to whole applications then check
    1. If database initialization parameter is set correctly ?
    2. If application sizing is proper , server configuration is enough to accomodate all users ?

    62. upgradation to R12 ? **

    http://www.reachdba.com/showthread.p...hlight=upgrade



    63. Use of FNDCPASS? If we change it by other method then what happened***
    http://www.reachdba.com/showthread.p...ange-Passwords


    Cheers!!!

+ Reply to Thread

Similar Threads

  1. Oracle DBA Interview Questions
    By Hemant in forum Oracle Database Interview Questions
    Replies: 1
    Last Post: 06-06-2012, 04:01 PM
  2. More RAC and 11g Database Interview Questions
    By Hemant in forum RAC Interview Questions
    Replies: 0
    Last Post: 04-20-2012, 10:49 AM
  3. RAC Interview Questions
    By Hemant in forum RAC Interview Questions
    Replies: 1
    Last Post: 04-17-2012, 06:33 PM
  4. Oracle Interview Questions (Contains DBA and Developer Questions)
    By Pradeep in forum Oracle Database Interview Questions
    Replies: 0
    Last Post: 02-29-2012, 05:13 AM
  5. Here are some possible Oracle DBA Interview Questions:
    By Akhil Kumar in forum Oracle Database Interview Questions
    Replies: 0
    Last Post: 02-12-2012, 04:47 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

DBA Lounge (P) Ltd. deals in Oracle Technologies on Consulting, Resourcing, Corporate Training


Online and corporate training available on Oracle Database 11g, Oracle 11g Real Application Cluster (RAC), Oracle Applications 11i/R12, Oracle Fusion Middleware 11g, Oracle Identity Management-OIM, Oracle Internet Directory 11g-OID, Oracle Business Intelligence Enterprise Edition-OBIEE, Oracle Golden Gate, Oracle Access Management-OAM, Oracle Internet Directory-ODS, Oracle Identity Analytics Architecture-OIA Statistics