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