Modern Oracle DBA

Every issues we have tuning opportunities but before start to troubleshoot the issue we need to analysis the Issue. First need to collect basic level of information to user Second task is where to get the information to server Third task is find out the issue Most of the common performance problem causes due to Lack of Sufficient server hardware Ex: CPU,Memory,Storage,Network Poorly configured initialization parameters Poor application coding Collect the basic level of information to user Program Level: It’s happening in Prod/Non- Prod? Oracle seeded program/Custom program? How much time it used earlier? Any recent code changes done/not? How much data is getting processed? Application Level: I s this happening for all user or particular user? Is this happening all forms or particular forms? Application level performance issue Document click hear Where to get the information to server Hardware issues: Need to ch...

Concurrent Processing using the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests. Post-processing actions are actions taken on concurrent request output. Example of a post-processing action is that used in Concurrent Processing support of XML Publisher. If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output. Tuning for Output post processor 1.Increase the number of Output Post Processor as follows:  Logon to Applications with "System Administrator" responsibility  Navigate to Concurrent -> Manager -> Define  Query for "Output Post Processor"  Click on "Work Shifts" and Increase the number of processes. (If you have 2 processes then make them 4 if require...

Concurrent manager log file location: Concurrent manager log files are located under $APPLCSF and $APPSLOG home [oracle@VIS ~]$cd $APPLCSF [oracle@VIS conc]$pwd /apps/applmgr/fs_ne/inst/VIS/logs/appl/conc [oracle@VIS conc]$cd log/ [oracle@VIS log]$pwd /apps/applmgr/fs_ne/inst/VIS/logs/appl/conc/log [oracle@VIS log]$ Internal concurrent manager log file: [oracle@VIS log]$ls -lrt *$TWO_TASK* Standard manager log file: [oracle@VIS log]$ls -lrt w*.mgr Conflict resolution manager log file: [oracle@VIS log]$ ls -lrt c*.mgr Output post processer log file: [oracle@VIS log]$ps -ef |grep OPP Concurrent program related some basic SQL queries How to find concurrent program status? SQL> select REQUEST_ID,phase_code,status_code,ORACLE_SESSION_ID from apps.fnd_concurrent_requests where request_id=’1234567’; How to find concurrent request output and log file location? SQL> select LOGFILE_NAME, OUTFILE_NAME from fnd_concurrent_requests where request_id...

Adadmin (Ad administration): It’s performance the maintenance tasks for Oracle E-business suite. AD Administration Main Menu 1. Generate Applications Files menu 2. Maintain Applications Files menu 3. Compile/Reload Applications Database Entities menu 4. Maintain Applications Database Entities menu 5. Change Maintenance Mode 6. Exit AD Administration 1. Generate Applications Files menu 1. Generate message files 2. Generate form files 3. Generate report files 4. Generate graphics files 5. Generate product JAR files 6. Return to Main Menu 2-Maintain Applications Files 1. Relink Applications programs 2. Create Applications environment file 3. Copy files to destinations 4. Convert character set 5. Maintain snapshot information 6. Check for missing files 7. Return to Main Menu 3-Compile/Reload Applications Database Entitie 1. Compile APPS schema 2. Compile menu information 3. Compile flexfields 4. Reload J...

 Adop Phase=fs_clone What is the fs_clone Phase? The fs_clone phase in Oracle EBS refers to the process of cloning the patch edition file system from the run edition.  It is used for file system cloning, and the usual cloning (adcfgclone.pl) script cannot be used to synchronize the run and patch file systems. Normally, fs_clone deletes the patch file system and restores the run system. When to Use  fs_clone Consider using the  fs_clone  phase in the following scenarios: After Aborting an Online Patching Cycle If a previous online patching cycle is aborted, the file system must be synchronized. If Technology Stack Patch is Applied in the Run Edition If any manual changes are made in the run file system, such as applying a technology stack patch, the file system must be synchronized. After Applying a RUP Patch Using  fs_clone  will synchronization between run and patch file and its help complete the prepare phase quickly. How to Execute fs_clone? adop Ph...

What is the ADOP Finalize Phase? After applying the patches in the patch edition, it will create lots of invalid objects. The finalize phase will compile the invalid objects, and it will prepare the environment for the cutover phase. The finalize phase is the optional phase in the patching cycle. After applying the patch, if we missed it, run Finalize and directorally run the cutover. The cutover phase will check if the if the finalize phase is completed or not. If not completed, the finalize phase cutover phase will start. Key Actions during the Finalize Phase Mode Selection : ADOP offers two modes for finalization - "quick" and "full": Quick Mode : This mode prioritizes speed by skipping non-essential tasks, making it ideal for scenarios where minimal downtime is critical. Full Mode : In contrast, full mode executes additional actions such as gathering statistics to the DML statment and enhance system performance after the patch is applied. This mode is beneficial...

adop phase=prepare Understanding ADOP Prepare Parameters Before diving into the prepare phase, let's go over the key parameters: skipsyncerror : This parameter specifies whether to ignore errors that may occur during incremental file system synchronization. Options :  yes  or  no  (default:  no ) Usage : Set to  yes  if you encountered errors in a previous patching cycle but decided to continue with the cutover. This will ignore apply errors during the next synchronization. sync_mode : This parameter determines the method used to synchronize the patch file system with the run file system. Options :  delta  or  patch  (default:  patch ) Usage : delta : Uses the file system synchronization command specified in  $AD_TOP/patch/115/etc/delta_sync_drv.txt . patch : Reapplies patches applied on the run file system. Example Command adop phase=prepare skipsyncerror= yes sync_mode=delta Step-by-Step Execution 1. Validating Passwo...