APPSDBA Data Lake

  At times, it may be necessary to regenerate a specific form for any number of reasons. This note provides a detailed example of how to generate a specific form through the AD utility adadmin. The basic steps are as follows: 1. Select the "Generate Applications Files menu" option. 2. Then select the "Generate forms files" option. 3. Choose the number of workers, the default is recommended and is based off the number of CPUs in your server. 4. Enter "yes" at this prompt to regenerate PL/SQL library files (.pll extension) 5. Enter "yes" at this prompt to regenerate Forms Menu files (.mmb -> .mmx extension) 6. Enter "yes" at this prompt to regenerate Forms Executable files (.fmb -> .fmx extension) 7. Enter the list of products, by short name as they are listed in "$APPL_TOP/". Use commas to separate the product names. 8. If you would like to generate specific files for each product, you may answer "Yes" here and

  The  “getent”  is a short form of “get entries from the LDAP database”. “getent”  is a Linux command that allows users to fetch details from LDAP  databases. The  “getent”  uses the same service name as the system, and it will display all user details and network information. passwd : can be used to check the user’s username, user’s ID, home folder, and full name. groups : shows all the groups of your Linux system. services:  gives information on all Linux services that are configured on your system. networks:  shows the networks of your system. protocols:  tells us about our network protocols. This post is focusing on how to fetch data from different databases. Syntax: Here’s the syntax of the “getent” command: $  getent   [ database ]   [ databse_name ] Below are the use of  “getent” Command: getent passwd: Use  “passwd”  as a database to get the information of the currently logged user. It displays the username, user’s id, and folder name. Run the command: $  getent   passwd   { u

 Check all the servers that are part of the applications are accessible. -> login to the servers that confirms servers are up and accessible. -> verify the load on the servers to see if any hung processes. -> verify disk spaces. -> verify if disks are accessible. ->Verify database health check. -> check any blocking locks in the database. -> check any tablespace running out of space. -> check Gather schema statistics running periodically and verify if any scheduled job failed.      set linesize 200      col table_name for a30      select table_name, last_analyzed from dba_tables order by last_analyzed desc; -> check the alert log for errors. -> check temporary space, and undo retention. -> verify if any recent changes to database configuration parameters. -> verify if any recent changes to the database Oracle home like patching/upgrade .. -> If any changes to Oracle home consider applying CPU/PS patches to Oracle home to make sure the latest bugs

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