APPSDBA Data Lake

SQL trace can be enabled in any E-Business module. The following possible ways could be used to enable TRACE for form, self-service page, or concurrent program. Enable trace for Self Service Page Set profile FND: Diagnostics = Yes at USER level.  log in to the Personal Home Page as that user and select the Diagnostics link at the top of the page. Select Set Trace Level and click Go. Select the desired trace level and click Save. Write down the trace id number(s). Perform the activity that you want to trace. Return to the ‘Diagnostics’ page. Select `Set Trace Level’ and click Go. Select ‘Disable Trace’ and click Go. Write down the trace id number(s) if different. Go to diagnostics_dest for your database and collect the raw trace file(s) suffixes by the trace id number(s) you have recorded. Enable trace for forms Set profile FND: Diagnostics = Yes at USER level. log in to the Application Navigate to the form where you want to trace Turn on Tracing by using the menu option: Home > Diag

 The below script can give a fair idea of the current state of the index by using the ANALYZE INDEX VALIDATE STRUCTURE command.  Here's some sample output from the INDEX_STATS Table:             SQL>  select owner,index_name,table_name,blevel from dba_indexes where BLEVEL>3  - Analyze indexes and find out  ratio of (DEL_LF_ROWS/LF_ROWS*100) is > 20   SQL> ANALYZE INDEX IDX_GAM_ACCT VALIDATE STRUCTURE;   Statement processed.       SQL> SELECT name, height,lf_rows,lf_blks,del_lf_rows FROM INDEX_STATS;       NAME          HEIGHT      LF_ROWS    LF_BLKS    DEL_LF_ROW   ------------- ----------- ---------- ---------- ----------   APPSOL_DL_ACCT        2          1          3          6        1 row selected.   There are two rules of thumb to help determine if the index needs to be rebuilt: If the index has height greater than four, rebuild the index. The deleted leaf rows should be less than 20%. SQL> select index_name,status,owner,table_name from dba_indexes where sta