Bhom Apps DBA || AWS || OCI

Apps password change routine in Release 12.2 E-Business Suite changed a little bit. We have now extra options to change password, as well as some manual steps after changing the password using FNDCPASS. There is a new utility introduced called AFPASSWD. This utility unlike FNDCPASS wont require you to enter apps and system user password, and makes it possible to separate duties between database administrator and application administrator. In most cases both these roles are done by same DBA. But in large organizations, there may be different teams that manage Database and Application. You can read about different options available in AFPASSWD in EBS Maintenance guide. Whether you use FNDCPASS or AFPASSWD to change the APPLSYS/APPS password, you must also perform some additional steps. This is because in R12.2, the old AOL/J connection pooling is replaced with Weblogic Connection Pool ( JDBC Datasource ).  Currently this procedure is not yet automated. It would be good, if th...

To disable  ARCHIVELOG  mode status, complete the following: Procedure Log in as OS user,  oracle  and set the Database Environment After setting the Database Home environment connect to sqlplus.  $ sqlplus /nolog SQL> conn / as sysdba To enable  ARCHIVELOG  mode status, enter the following SQL commands: SQL> Shutdown SQL> Startup mount SQL> Alter database noarchivelog; SQL> alter database open; To check the  ARCHIVELOG  mode status, enter the following SQL command: SQL> archive log list; Database log mode No Archive Mode Automatic archival Disabled Archive destination /oradata2/archive_log_dest Oldest online log sequence 7 Current log sequence 9

While Running Oracle Applications on the web, the following error appears: Node ID  does not exist for the current application server id. Cause: There is a mismatch between server_id in the  fnd_nodes table and appl_server_id in the dbc file and hence we are getting this  "node id does not exist" error. Solution: Stop application. Run adgendbc.sh script to configure apps tier dbc file with the correct id from the database instance. Start the application and retest. Location of script: 11i: $COMMON_TOP/admin/install/$CONTEXT_NAME R12: $INST_TOP/admin/install Below is the Example.  [oraprod@apps oraAP]$ cd $INST_TOP [oraprod@apps POLPROD_apps]$ pwd /oraprod/oraAP/fs2/inst/apps/POLPROD_apps [oraprod@apps POLPROD_apps]$ cd admin/install/ [oraprod@apps install]$ ./adgendbc.sh adgendbc.sh started at Wed Feb 19 10:21:03 EAT 2020 Enter the APPS username: apps Enter the APPS password: SQL*Plus: Release 10.1.0.5.0 - Production on Wed Feb 19 10:21:10 202...