Bhom Apps DBA || AWS || OCI

Issue :- [oracle@testserv1~]$ crontab -l You (oracle) are not allowed to access to (crontab) because of pam configuration. [oracle@testserv1~]$ When you will check the log file /var/log/cron you will be able to see the error in logfile. May 22 12:28:57 testserv1 crontab[48079]: (oracle) PAM ERROR (Authentication token is no longer valid; new one required) May 22 12:29:37 testserv1 crontab[48205]: (oracle) PAM ERROR (Authentication token is no longer valid; new one required) Solution :- There could be two reason for this error: 1. Expired password for the user. 2. User not allowed to cron in /etc/security/access.conf file. Check for expired user password.  1. First of all, check the password expiry for the user using chage command. [root@testserv1 ~]# chage -l oracle Last password change                                    : Feb 19, 2021 Password expires        ...

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

While dropping a user in oracle database , you may face below error. ORA-01940 Problem:- SQL> drop user bhom cascade; drop user bhom cascade * ERROR at line 1: ORA-01940: cannot drop a user that is currently connected SQL> Solution:- Run the below by entering the schema name which you want to drop. As it will kill all the connected session for particular schema.  BEGIN   FOR r IN (select sid,serial# from v$session where username = 'BHOM')   LOOP     EXECUTE IMMEDIATE 'alter system kill session ''' || r.sid        || ',' || r.serial# || '''';   END LOOP; END; / Once the above query gets completed you can try to drop the schema again. SQL> BEGIN   FOR r IN (select sid,serial# from v$session where username = 'BHOM')   LOOP     EXECUTE IMMEDIATE 'alter system kill session ''' || r.sid       || ',' || r.serial# || ''''; ...

Error Occurred :– Trying to connect using SID as ServiceName.DomainName getConnectionUsingServiceName() –> JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oratest.tipl.com)(PORT=1532))(CONNECT_DATA=(SERVICE_NAME=TIR12.ticfg.com))) Exception occurred: java.sql.SQLException: The Network Adapter could not establish the connection Connection could not be obtained; returning null RC-00118: Error occurred during creation of database StackTrace: java.lang.Exception: Control file creation failed at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:661) at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:328) at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:304) at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:154) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.re...