APPSDBA Data Lake

The Background Engine is a PLSQL Procedure that checks and executes any deferred or timed-out activities in the workflow system.  If new activities are deferred or timed out after the current Background Engine is started, the procedure will check one more time for any new activities to execute before terminating. When all matching activities have been completed, the procedure comes to end. It  can be run as a Concurrent program or as a package or SQLPLUS command. Run Workflow Background Process from Unix SQL script placed in $APPL_TOP which can be used to run How to run Workflow Background Process from Unix $FND_TOP/Admin/Sql/wfbkg.sql       cat workflow_background.sh       sqlplus apps/<apps pass> << EOF       @$FND_TOP/Admin/Sql/wfbkg.sql      exit      EOF Run Workflow Background Process from SQL*Plus BEGIN wf_engine.background (itemtype=>NULL , process_deferred=>TRUE , minthreshold=>NULL , maxthreshold=>NULL , process_timeout=>FALSE , process_stuck=>FA

Below command will fix the issue:   sudo xfs_repair -v -L /dev/dm-0 Node failed to boot after a power outage and got the error "Failed to mount /sysroot" and entered into emergency mode. Mount and unmount failed so in this condition just run with  -L  option and that will help node to boot up again.

 The following points need to answer before jumping into troubleshooting: Are there any recent code changes done in the concurrent program?           Check long_running_sid and verify the recent code change of last_ddl_timestamp after a             discussion with the developer. Was this running long in the last few run as well, or was this time only?            ==> Check the program history. How much time does it take to complete?           Once again program history can give us some idea. Are these jobs fetching higher data compared to the last run           ===> Confirm on data change . Query Plan change will indicate this issue. Does this job runs at any specific time or it can be run anytime           ===> The nature of the job can help to understand the job's nature. Does this job fetch data using DB Link          ====> Check whether the DB link is involved or not. The below-given approach would help to conclude the gray areas. Check the load of the server using t

Linux instance can be connected through Putty by using the below method. SSH private key files generated by  Oracle Cloud Infrastructure  are not compatible with PuTTY. If you are using a private key file generated during the instance creation process you need to convert the file to a  .ppk  file before you can use it with PuTTY to connect to the instance. Convert a generated .key private key file: Open PuTTYgen. Click  Load , and select the private key generated when you created the instance. The extension for the key file is  .key . Click  Save private key . Specify a name for the key. The extension for the new private key is  .ppk . Click  Save . Connect to the Linux instance using a .ppk private key file: If the instance uses a key pair that you created using PuTTY Key Generator, use the following procedure. Open PuTTY. In the  Category  pane, select  Session  and enter the following: Host Name (or IP address): <username> @ <public-ip-address> Port:  22 Connection type:

 Step 1: Create Authentication SSH-Keygen Keys on – (Source) ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home/sid/.ssh/id_rsa): [Press enter key] Created directory '/home/sid/.ssh'. Enter passphrase (empty for no passphrase): [Press enter key] Enter same passphrase again: [Press enter key] Your identification has been saved in /home/sid/.ssh/id_rsa. Your public key has been saved in /home/sid/.ssh/id_rsa.pub. The key fingerprint is: 5f:ad:40:00:8a:d1:9b:99:b3:b0:f8:08:99:c3:ed:d3 sid@appsolworld.com The key's randomart image is: +--[ RSA 2048]----+ | ..oooE.++| | o. o.o | | .. . | | o . . o| | S . . + | | . . . o| | . o o ..| | + + | key will be generated in /user/.ssh/rsa_id/ folder use without a passcode. Step 2: Upload SSH Key to – (Target) ssh-copy-id sid@192.168.1.121 ssh-copy-id user@i.p/hostname Step 3: Test SSH Passwordless Login from Sourc

  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