Modern Oracle DBA

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...

  To check if your standby database is in sync with the primary database, follow these steps: 1.      Compare Sequence Numbers : Look at the latest sequence number generated on the primary database and the latest sequence number applied on the standby database. 2.      Check for Gaps : Ensure there are no missing sequence numbers on the standby database. The sequence numbers on both databases should match, and there should be no gaps in the sequence on the standby database. If they do match and there are no gaps, the databases are in sync. Verifying the Status of Primary and Standby Databases in Oracle On the Primary Server First, log in to the primary server and run the following SQL query to check the status: Copy Select name,open_mode,database_role from v$database; On the Standby Server Log in to the standby server and execute the same SQL query: Copy Select name,open_mode,database_role from v$datab...

1. Disk and File System Checks Objective: Monitor disk usage and verify file system configurations. Commands and Steps:   View Disk Space Usage: Command:  df -h Verify the available and used space in a human-readable format.   Check File System Configurations: Command:  cat /etc/fstab Ensure all required file systems are configured to mount at boot.   Verify Permissions of fstab File: Command:  ls -ld /etc/fstab Check permissions to ensure security and avoid unauthorized changes. 2. Network Configuration and Connectivity Objective: Validate DNS configurations and network routes. Commands and Steps:   Verify DNS Resolver Permissions: Command:  ls -ld /etc/resolv.conf   Display DNS Server Configuration: Command:  cat /etc/resolv.conf   Check Kernel Routing Table: Command:  ip route Confirm active routes for ...

When working with Oracle E-Business Suite (EBS) R12.2, granting privileges to applicatation objects requires special care to avoid invalidating objects in the current edition.  Grants cannot be performed in the run edition when the application is being used. A direct GRANT (DDL) command can potentially cause object invalidation when the application is actively being used. To handle this in a more controlled manner, Oracle introduced the AD_ZD.GRANT_PRIVS utility. Why Use AD_ZD.GRANT_PRIVS? In Oracle EBS R12.2, all grants should be performed using the AD_ZD.GRANT_PRIVS procedure rather than the traditional GRANT statement.  The reason is simple: the GRANT statement directly modifies objects in the database, and this can invalidate them in the current edition. Invalidations during runtime can cause service interruptions, which is unacceptable in a live system. Syntax for Granting and Revoking Privileges The AD_ZD package provides two p...