Modern Oracle DBA

1. ADOP Validate – Quick Health Check Purpose : To check if the current patching cycle is healthy. Command:  adop -validate What it does: Runs a quick system check Alerts you if there are any configuration or edition issues Often the first step Oracle Support asks you to run Location:  $AD_TOP/bin Use case:  Before starting or during a patching cycle, run this to ensure everything is OK.   2. ADOPSCANLOG – Scan ADOP Log Files Easily Purpose:  To check patching logs quickly from current or past sessions. Why it is important: Saves time by scanning all logs in one go Helps you find errors, warnings, or specific messages You can search older ADOP sessions too Command examples: adopscanlog                --> Scans latest session logs adopscanlog session_id=0   --> Scans ALL past sessions adopscanlog loglevel=error...

When managing Oracle E-Business Suite R12.2, system administrators often need to decrypt the WebLogic boot.properties password for troubleshooting or configuration validation. Below is a step-by-step guide to perform this securely using WLST (WebLogic Scripting Tool). Step 1: Locate the boot.properties File Copy cd $EBS_DOMAIN_HOME/servers/AdminServer/security/ cat boot.properties Sample Output: Copy username={AES}32WjQKxRgxZu23m3gohzso8sSV4IlB3xCfW+fVMLbf0 password={AES}traTrS34UEZ4bfIuDeJBFpLIjJXL+laajBDGyikOzsM= This file stores encrypted credentials used for WebLogic Server auto-start. Step 2: Set Required Environment Make sure your $EBS_DOMAIN_HOME and $FMW_HOME are correctly set. In this example: Copy echo $EBS_DOMAIN_HOME /apps/applmgr/r12/fs1/FMW_Home/user_projects/domains/EBS_domain Step 3: Launch WLST Navigate to the WLST location: Copy cd $FMW_HOME/oracle_common/common/bin/ ./wlst.s...

 If you need to gather details about the installed modules, product installation statuses, and configurations, you can leverage the following SQL utility. The Query  sqlplus apps/<apps_pw>@AD_TOP/sql/adutconf.sql Why use this  This script particularly using for during: Upgrades : Ensure all modules are dependencies are installed correctly. System Diagostics : Verity the product version and statues when trubleshooting   

In this guide, we will walk you through the steps to add and manage a new managed server in Oracle E-Business Suite (EBS). This process involves creating the managed server, updating configuration files, and starting the server. 1. Creating a Managed Server To create a new managed server, execute the following command. This will create the managed server and add a new entry to the context file, enabling you to start and stop the server using the adstrtal and adstpall scripts: Copy $ perl /patch/115/bin/adProvisionEBS.pl \ ebs-create-managedserver -contextfile=$CONTEXT_FILE \ -managedsrvname=MANAGED_SERVER_NAME -servicetype=forms \ -managedsrvport=MANAGED_SERVER_PORT -logfile=LOGFILE For example, to create a forms_server4 with port 7405: Copy $ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl \ ebs-create-managedserver -contextfile=$CONTEXT_FILE \ -managedsrvname= forms_server4 -servicetype= forms \ -managedsrvport= 7405 -logfile=$APPLRGF/TXK/addMS_formsserver4...

The Problem with ALTER USER When you change a EBS applicatation user's password directly at the database level using the ALTER USER command: The new password is updated only in the database. The password remains unchanged in the EBS application's FND tables . Why This Matters The FND tables store encrypted versions of user passwords, and they must be synchronized with the database. If the passwords between the FND tables and the database are out of sync: The EBS application won't recognize the new password. Login failures occur. Application functionality is disrupted. The Correct Approach To avoid these issues, passwords should always be changed through: The  EBS application  itself, or The  FNDCPASS utility . Using these methods ensures that: The database password is updated. The corresponding encrypted password in the FND tables is also updated. Related Posts: FNDCPASS Utlity in R12.2 How to Grant Privileges in Oracle EBS R12.2 Using AD_ZD.GRANT_PRIVS

Oracle Data Guard for data protection and high availability. Knowing how to start and stop the Oracle Data Guard server is essential for database administrators. This document will explain the process step-by-step. Steps to Stop the DR Database Stop the Listener Copy lsnrctl stop <listener_name> Replace <listener_name> with the name of your database listener. This command stops the listener service that facilitates client connections to the database.   Cancel Managed Recovery Connect to the database using SQL*Plus and cancel the managed recovery process: Copy SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; Database altered. This halts the recovery process for the standby database. Shutdown the Database Execute the following command to shut down the DR database: Copy SQL> SHUT IMMEDIATE; ORA-01109:database not open Database dismounted. ORACLE instance shut down. SQL> This...