Oracle Apps Technical Part 2

New Feature – AFPASSWD utility in EBS 12.1.2

Oracle has introduced a new utility to change the Oracle E-Business Suite passwords in R12.1.2, AFPASSWD is an enhanced version of FNDCPASS utility.
1) AFPASSWD only prompts for passwords required for the current operation. allowing separation of duties between applications administrators and database administrators.
2) AFPASSWD can be run from the database tier as well as the application tier. In contrast, FNDCPASS can only be run from the application tier.
3) This also improves interoperability with Oracle Database Vault. In contrast, the FNDCPASS utility currently requires specification of the APPS and the SYSTEM usernames and corresponding passwords, preventing separation of duties between applications administrators and database administrators.
3) When changing a password with AFPASSWD, the user is prompted to enter the new password twice to confirm.
SAMPLE OUTPUT: Changing SYSADMIN Password  

$AFPASSWD -f SYSADMIN  

Enter the ORACLE password of Application Object Library ‘APPSUSER’:  

Connected successfully to APPS.  Working…  

Enter new password for user [SYSADMIN]:  

Verify new password for user [SYSADMIN]:  

Password is changed successfully for user SYSADMIN.  

Password is changed successfully for user SYSADMIN.  

AFPASSWD completed successfully.

 

SAMPLE OUTPUT: Changing APPLSYS Password

$AFPASSWD -c apps@PROD -s APPLSYS  

Enter the ORACLE password of Application Object Library ‘APPSUSER’:  

Connected successfully to APPS.  

Enter the password for your ‘SYSTEM’ ORACLE schema:  

Connected successfully to SYSTEM.  Working…  

Enter new password for user:  

Verify new password for user:  

Working…  

AFPASSWD completed successfully.

 

 

Imporatant – Concurrent Manager Issues

1) Running FND_CONC_CLONE.SETUP_CLEAN
Note : In the case of a clone instance, it is strongly recommended to clean the non – existing nodes
FND_NODE table contains the node entries of both SOURCE environment and TARGET environment after clone.
If u want to get rid of the source node entries
a. Stop all middle tier services including the concurrent managers.
b. Stop the database.
c. Start the database.
d. Connect SQLPLUS as APPS user and run the following :
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
e. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables.
2) Executing afdcm037.sql – Create The Service Manager “FNDSM”
NOTE: This script will create libraries for FNDSM and create managers for preexisting nodes.
If Service Manager is not running , To create the Service Manager “FNDSM” Please perform below steps.
a. Log in as applmgr
b. cd to $FND_TOP/patch/115/sql
c. Run the script: afdcm037.sql
Check again that FNDSM entries now exist: select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like ‘FNDSM%’;
3) Relink the binaries FNDLIBR, FNDSM, FNDFS and FNDCRM
It is better to relonk the binaries once, If Concurrent Managers do not start for the cloned Instance.
Go to cd $FND_TOP/bin
$ adrelink.sh force=y “fnd FNDLIBR”
$ adrelink.sh force=y “fnd FNDSM”
$ adrelink.sh force=y “fnd FNDFS”
$ adrelink.sh force=y “fnd FNDCRM”
4) Run CMCLEAN.sql, To Clean Concurrent Manager Tables.
Cleaning out the Concurrent Manager tables is a useful method of making sure that there are no invalid statuses that can prevent the managers from starting.
a.  Log in as APPS user
b.  Run the script: cmclean.sql
c.  COMMIT;

Find version of Oracle E-Business suite

We can find the Application version in two ways:
1) From the Form Application:
Help > About Oracle Applications

2)  Connect to database as user apps and execute below command.
SQL> SELECT RELEASE_NAME FROM FND_PRODUCT_GROUPS;
RELEASE_NAME
————————————————–
12.0.6

Find Concurrent manager logs on Oracle Apps

Concurrent Mangers log files are located in the $APPLCSF/$APPLLOG location.
cd $APPLCSF/$APPLLOG
For ICM Log                                       –> ls -lrt *$TWO_TASK*
For Standard manager Log                  –> ls -lrt w*.mgr
For Conflict Resolution manager Log –> ls -lrt c*.mgr
We can also get the ICM manager logfile location with below query
SELECT ‘ICM_LOG_NAME=’ || fcp.logfile_name
FROM fnd_concurrent_processes fcp, fnd_concurrent_queues fcq
WHERE fcp.concurrent_queue_id = fcq.concurrent_queue_id
AND fcp.queue_application_id = fcq.application_id
AND fcq.manager_type = ’0′
AND fcp.process_status_code = ‘A’;
Sample Output:
SQL> SELECT ‘ICM_LOG_NAME=’ || fcp.logfile_name
2  FROM fnd_concurrent_processes fcp, fnd_concurrent_queues fcq
3  WHERE fcp.concurrent_queue_id = fcq.concurrent_queue_id
4  AND fcp.queue_application_id = fcq.application_id
5  AND fcq.manager_type = ’0′
6  AND fcp.process_status_code = ‘A’;
‘ICM_LOG_NAME=’||FCP.LOGFILE_NAME
——————————————————————————–
ICM_LOG_NAME=/u01/PROD/inst/apps/PROD_oracle-master/logs/appl/conc/log/PROD_0712.mgr