Modern Oracle DBA

Normally we are getting email/tickets to DEV/PROD instance application,forms are opening slow. those are very frequent issue we expected from devlopment and functional team. Before troubleshooting first we need to understand the issue so collect the below basic information from Users. 1) Is it slow for all users OR specific users OR slow for specific site/locations? 2) Any specific operation being performed which is making application slow? 3) What part of application is slow: HTTP pages, Forms, All etc? 4) If forms, then are these seeded or custom? 5) If seeded forms ask any customization causing issue 6) Can screenshot or navigation be provide so that DBA can replicate? 7) Is it constantly slow or slow at specific time of the day? Scenario-1: If all forms are opening slowly in particular machine? 1. Need to Clear internet browser history and cache. Go to IE->Internet options->Delete browsing history.

fnd_conc_clone.setup_clean : fnd_conc_clone is the package name setup_clean is procedure name After clone we must need to run the fnd_conc_clone.setup_clean script It will be clear the below tables in target node information in to source node table fnd_concurrent_queue_size fnd_concurrent_queues_tl fnd_concurrent_queue_size fnd_concurrent_queues fnd_nodes Syntax: $sqlplus apps/<apps_password> SQL> exec fnd_conc_clone.setup_clean; PL/SQL procedure successfully completed. SQL> commit; Commit complete. Once the script was executed must run the autoconfig in DB and Middle-Tier   Cmclean.sql We use the cmclean.sql scrip clean the running and pending requests Down the concurrent manager and check if any concurrent program running/not(ps- ef |grep FNDLIBR, ps- ef |grep FNDOPP) Cmclean.sql script is not recommended by oracle. R12 will user cpadmin.sh and  concurrent manager recovery wizard. It will be clea

We need to check v$parameter table and find the coumn name in ISSUE_MODIFIABLE Static parameter The ISSUE_MODIFIABLE column value FALSE means parameters are static parameter Static parameter values change the value in spfile only so we need to restart the database otherwise it  will be reflect on next database bounce. Must we need to use scop=spfile EX: SQL>Alter system set sga_max_size=50m scope=spfile; Dynamic parameter: The ISSUE_MODIFIABLE column value Immediate means parameter are dynamic   parameter We can change the dynamic parameter in anytime no need to bounce for this changes This changes are applied in database memory and spfile We can use scope=memory and scope=both parameters EX: SQL> Alter system set log_archive_dest=’/u01/arch’ scope=both; Meaning of scope= memory|spfile|both Scope: Changes should be made in memory spfile and both areas Scope= Memory : Change the