November 2015

Unable to login to R12 after SSO integration

Introduction
I am now working on the E-Business Suite Release 12 upgrade project. The login page broke after integrating the R12 development system with Oracle Single Sign-On. We recieved 'HTTP 500 Internal Server Error'. Furthermore, the local login page (/OA_HTML/AppsLocalLogin.jsp) too was not getting rendered.
Problem
This certainly seemed to a java servlet initialization problem in the Oracle OC4J. I noticed the following errors in the $INST_TOP/logs/ora/10.1.3/j2ee/oacore/oacore_default_group_1/application.log
Error initializing servletjava.lang.NoClassDefFoundError: Could not initialize class oracle.apps.fnd.profiles.Profiles html: chain failed javax.servlet.ServletException at com.evermind[Oracle Containers for J2EE 10g
$INST_TOP/logs/ora/10.1.3/opmn/oacore_default_group_1/oacorestd.err logfile.
Exception in static block of jtf.cache.CacheManager. Stack trace is: oracle.apps.jtf.base.resources.FrameworkException: IAS Cache initialization failed.
Solution
The problem has something to do with the Java Cache. I went ahead and disabled the cache mechanism by setting the parameter LONG_RUNNING_JVM to false in the $INST_TOP/ora/10.1.3/j2ee/oacore/config/oc4j.properties and this solved the problem.

Oracle apps prompts for the E-Business username/pwd after entering

AppsDBA , R12.2 , SSO No comments :

Applications SSO Auto Link User' profile and bootstrapping again
Introduction
After integrating Oracle E-Business Suite with SSO, setting the system profile 'Applications SSO Auto Link User' = 'Enabled' lets users login to Oracle using only their SSO username/pwd (Windows NT username/pwd) if the 3rd party LDAP directory is MS Active Directory) WITHOUT the need to enter their Oracle E-Business local username/pwd again in the next page. This profile 'automatically links' the Windows NT username and the existing Oracle username internally (provided there is a user_name in FND_USER that EXACTLY matches the Windows NT username) and directly shows the Oracle E-Business responsibilities navigation pane. It does it by updating FND_USER.USER_GUID to a value that matches with the corresponding OID's ORCLGUID value of the logged in user.

Problem
Due to some circumstances, one may have to bulkdelete all the OID users and reload them from AD to OID using the bootstrap process. Because it is a new bootstrap process, a new ORCLGUID may get generated in the OID that will make it out of sync with the target FND_USER.USER_GUID value. With such a scenario, Oracle will prompt again for the E-Business local username/pwd despite the system profile 'Applications SSO Auto Link User' having an 'Enabled' value. One can verify the mismatch after the reload by running the following command.
ldapsearch -v -h oid_host_name -p 389 -D "cn=orcladmin" -w ***** -b "" -s sub "sn=RAMINENI*" uid orclguid orclactivestartdate orclactiveenddate orclisenabled
ldap_open( oid_host_name, 389 )
filter pattern: sn=RAMINENI*
returning: uid orclguid orclactivestartdate orclactiveenddate orclisenabled filter is: (sn=RAMINENI*) cn=c123456,ou=consultants,ou=users,IdentityRealm
uid=john@mycompany.com
orclguid=844AB8C88EE56B74E040810A0CBC6249
This orclguid shown above may NOT match the FND_USER.USER_GUID for the same user because the former is a newly generated one because of the reload process. In this case, Oracle prompts for the Oracle E-Business username/pwd after entering the Windows NT username/pwd in the login page even though the system profile 'Applications SSO Auto Link User' is set to 'Enabled', often confusing the user.

Solution
The process to 'auto link' SSO username and the FND_USER user_name after a reload of data from the 3rd party LDAP directory to OID is to update FND_USER.USER_GUID value to NULL.
update fnd_user set user_guid = NULL where user_guid is NOT NULL.
A better alternative is to run the $FND_TOP/patch/115/sql/fndssouu.sql USER_NAME
script (Apart from setting the FND_USER.USER_GUID value to NULL, this script also flushes the workflow entity cache for the user)

Cloning Pluggable Databases 12c

12c , AppsDBA , Oracle DBA , R12.2 No comments :

Overview:
Purpose
This tutorial covers the steps required to clone a pluggable database (PDB) from a container database (CDB) into the same CDB.
Time to Complete
Approximately 15 minutes
Introduction
You can copy a source PDB from a CDB and plug the copy into the same CDB or into another CDB. This capability is suitable for the following situations:
You want to test the application patch of your production PDB. You first clone your production application in a cloned PDB, patch the cloned PDB, and test it.
You want to diagnose performance issues or perform performance regression tests on your application. Because you cannot perform this operation in parallel with the production in the same database, you clone the PDB into another CDB.
Scenario
In this tutorial, you will use SQL*Plus to perform a PDB cloning operation within the same CDB.
Note: If you want to clone a PDB from a CDB into another CDB, you identify the source CDB by creating a database link to it from the CDB in which you want to create the clone.
Prerequisites
Before starting this tutorial, you should:
Ensure that you have enough disk space to hold a complete clone of the PDB.
Install Oracle Database 12c.
Create one CDB with one PDB in it.
The environment used in the development of this tutorial is as follows:
ORACLE_HOME: /u01/app/oracle/product/12.1.0
TNS Listener port: 1521
Container databases:
SID: cdb1
SID: cdb2
Pluggable databases (in cdb1):
pdb1
pdb2
Preparing the Source PDB to Clone:
In this section, you prepare the source PDB to be cloned and the target new PDB to be created.
Setting the Source PDB to READ ONLY Mode
Use SQL*Plus to close the PDB that you want to clone.
. oraenv
[enter cdb1 at the prompt]
sqlplus / as sysdba
alter pluggable database pdb1 close immediate;
Open the PDB that you want to clone in READ ONLY mode.
alter pluggable database pdb1 open read only;
exit
Creating a Directory for the New Clone PDB
Configuring OMF to the Directory of the Clone PDB
Cloning the PDB Within the CDB:
Use SQL*Plus to clone the PDB within the same CDB.
Execute the following statement:
create pluggable database pdb1_clone from pdb1;
Open the new pdb.
alter pluggable database pdb1_clone open;
Connect to the new pdb.
connect system/oracle@localhost:1521/pdb1_clone;
Verify that you are connected to the new PDB:
show con_name

Setting the Source PDB Back to Open Mode:
Connect to the root in the CDB.
connect / as sysdba
alter session set container=cdb$root;
Execute the following statement:
alter pluggable database pdb1 close immediate;
Open the source pdb.
alter pluggable database pdb1 open;

Resetting Your Environment:
Perform the following steps to reset your environment prior to repeating the activities covered in this OBE or starting another OBE.
Close the clone PDB.
alter pluggable database pdb1_clone close immediate;
Delete the clone PDB and its data files.
drop pluggable database pdb1_clone including datafiles;

11gR2 to 12cR1 Upgrade

12c , AppsDBA , Oracle DBA No comments :

[oracle@testvm admin]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Wed Jul 3 15:47:41 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
SQL> @utlu121i.sql
DOC>############################################################################
DOC>
DOC>
DOC> Note that the new preupgrd.sql script replaces the utlu121i.sql script
DOC> and earlier versions of the Pre-Upgrade Information Tool.
DOC>
DOC> The Pre-Upgrade Information Tool, which now consists of preupgrd.sql
DOC> and utluppkg.sql.
DOC>
DOC> 1. Make sure preupgrd.sql and utluppkg.sql (located in the admin
DOC> directory of the new installation of Oracle Database 12.1) are
DOC> accessible while connected to your source database, which is the
DOC> database to be upgraded
DOC>
DOC> 2. Connect to your source database using an account with DBA privileges
DOC> and execute the preupgrd.sql script.
DOC>
DOC> For more information on the Pre-Upgrade Information Tool, see the
DOC> Oracle Database Upgrade Guide.
DOC>
DOC>
DOC>############################################################################
SQL> @preupgrd.sql
Loading Pre-Upgrade Package...
Executing Pre-Upgrade Checks...
Pre-Upgrade Checks Complete.
************************************************************
Results of the checks are located at:
/oracle/product/cfgtoollogs/test/preupgrade/preupgrade.log
Pre-Upgrade Fixup Script (run in source database environment):
/oracle/product/cfgtoollogs/test/preupgrade/preupgrade_fixups.sql
Post-Upgrade Fixup Script (run shortly after upgrade):
/oracle/product/cfgtoollogs/test/preupgrade/postupgrade_fixups.sql
************************************************************
Fixup scripts must be reviewed prior to being executed.
************************************************************
************************************************************
====>> USER ACTION REQUIRED <<====
************************************************************
The following are *** ERROR LEVEL CONDITIONS *** that must be addressed
prior to attempting your upgrade.
Failure to do so will result in a failed upgrade.
You MUST resolve the above errors prior to upgrade
************************************************************
SQL> @/oracle/product/cfgtoollogs/test/preupgrade/preupgrade_fixups.sql
Pre-Upgrade Fixup Script Generated on 2013-07-03 15:48:22 Version: 12.1.0.1 Build: 006
Beginning Pre-Upgrade Fixups...
**********************************************************************
Check Tag: DEFAULT_PROCESS_COUNT
Check Summary: Verify min process count is not too low
Fix Summary: Review and increase if needed, your PROCESSES value.
**********************************************************************
Fixup Returned Information:
WARNING: --> Process Count may be too low
Database has a maximum process count of 150 which is lower than the
default value of 300 for this release.
You should update your processes value prior to the upgrade
to a value of at least 300.
For example:
ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
or update your init.ora file.
*****************************************************************
*****************************************************************
Check Tag: EM_PRESENT
Check Summary: Check if Enterprise Manager is present
Fix Summary: Execute emremove.sql prior to upgrade.
*****************************************************************
Fixup Returned Information:
WARNING: --> Enterprise Manager Database Control repository found in the database
In Oracle Database 12c, Database Control is removed during
the upgrade. To save time during the Upgrade, this action
can be done prior to upgrading using the following steps after
copying rdbms/admin/emremove.sql from the new Oracle home
- Stop EM Database Control:
$> emctl stop dbconsole
- Connect to the Database using the SYS account AS SYSDBA:
SET ECHO ON;
SET SERVEROUTPUT ON;
@emremove.sql
Without the set echo and serveroutput commands you will not
be able to follow the progress of the script.
*****************************************************************
*****************************************************************
Check Tag: DBMS_LDAP_DEPENDENCIES_EXIST
Check Summary: Check for dependency on DBMS_LDAP package
Fix Summary: Network Objects must be reviewed manually.
*****************************************************************
Fixup Returned Information:
WARNING: --> Existing DBMS_LDAP dependent objects
Database contains schemas with objects dependent on DBMS_LDAP package.
Refer to the Upgrade Guide for instructions to configure Network ACLs.
USER APEX_030200 has dependent objects.
*****************************************************************
*****************************************************************
Check Tag: AMD_EXISTS
Check Summary: Check to see if AMD is present in the database
Fix Summary: Manually execute ORACLE_HOME/oraolap/admin/catnoamd.sql script to remove OLAP.
*****************************************************************
Fixup Returned Information:
INFORMATION: --> OLAP Catalog(AMD) exists in database
Starting with Oracle Database 12c, OLAP is desupported.
If you are not using the OLAP Catalog component and want
to remove it, then execute the
ORACLE_HOME/oraolap/admin/catnoamd.sql script before or
after the upgrade.
*****************************************************************
*****************************************************************
[Pre-Upgrade Recommendations]
*****************************************************************
*****************************************
********* Dictionary Statistics *********
*****************************************
Please gather dictionary statistics 24 hours prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
^^^ MANUAL ACTION SUGGESTED ^^^
**************************************************
************* Fixup Summary ************
4 fixup routines generated INFORMATIONAL messages that should be reviewed.
**************** Pre-Upgrade Fixup Script Complete *********************
SQL> EXECUTE dbms_stats.gather_dictionary_stats;
SQL> exit
[oracle@testvm ~]$ . /oracle/product/db/12.1.0/dbhome/bin/oraenv
ORACLE_SID = [test] ?
The Oracle base remains unchanged with value /oracle/product
[oracle@testvm ~]$ cd /oracle/product/db/12.1.0/dbhome/bin/
[oracle@testvm bin]$ ./dbua

[oracle@testvm ~]$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.1.0 Production on Thu Jul 4 11:38:44 2013
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> select banner from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
PL/SQL Release 12.1.0.1.0 - Production
CORE 12.1.0.1.0 Production
TNS for Linux: Version 12.1.0.1.0 - Production
NLSRTL Version 12.1.0.1.0 - Production
SQL> EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS
PL/SQL procedure successfully completed.
SQL> select count(*) from dba_objects where status like 'INVALID';
COUNT(*)
----------
0
SQL> exit

Starting/Stopping a Pluggable Database

12c , AppsDBA , Oracle DBA , R12.2 No comments :

From Root Container:
To change the open mode of a pluggable database from the root container, do as follows:
$ sqlplus / as sysdba
SQL> alter pluggable database salespdb open;
You can also start a pluggable database in a particular state, such as read-only:
SQL> startup pluggable database salespdb open read only;
To close a pluggable database, you can specify the name of the pluggable database:
SQL> alter pluggable database salespdb close immediate;
You can also open or close all pluggable databases while connected to the root container as SYS:
SQL> alter pluggable database all open;
SQL> alter pluggable database all close immediate;
From Pluggable:
To open/start a pluggable database, connect to the pluggable database as SYS:
$ sqlplus sys/foo@salespdb as sysdba
SQL> startup;
To shut down the database, issue the following command:
SQL> shutdown immediate;
Pluggable database architecture:

Oracle 12cR1 Optimal Flexible Architecture:

Oracle 12c Database Architecture:

RedHat Linux OS upgradation on Oracle 11gR2 RAC environment

AppsDBA , Linux , Oracle DBA , RAC No comments :

Two months before I was performed Linux OS upgradation on live production and test environment for one of my big client. Both environments are 2 node RAC configured.
Below mentioned steps for OS upgradation,
OS Upgrade Pre-requisites Steps:-
Kindly cross check with Oracle and RedHat for license certification matrix
Take fullbackup of OS and Database.
OS Upgrade Steps:-
(1) Shutdown DB, DBconsole (if any), Cluster, ASMlib (if any in Linux)
As RDBMS owner id “oracle”:
$ srvctl stop database -d -o immediate #– run once in any node
$ emctl stop dbconsole #– run on all nodes
As UNIX/Linux “root”:
# /bin/crsctl stop crs #– run on all nodes
# /bin/crsctl disable crs #– run on all nodes
# /etc/init.d/oracleasm stop #– run on all nodes
# /etc/init.d/oracleasm disable #– run on all nodes
(2) Backup filesystem for GRID ORACLE_HOME & RDBMS ORACLE_HOME
(3) Upgrade RedHat OS
configure RHN (Give Rhn_register command thru root user).
You have to give Redhat login user/password and your proxy address & port.
RHN will collect your system information then will send that to redhat network.
Once RHN configured then give command like #yum update --no plugin (or yum update)
It will download latest packages from redhat repository and install automatically, final stage the OS will ask you for reboot the machine.
After reboot you can get the latest kernal (using this command check the kernal and redhat os version #uname-a, cat /etc/redhat-release)
(4) Upgrade ASMlib (Download ASM packages based on latest kernal version)
# rpm -Uvh oracleasm-support-xxx
# rpm -Uvh oracleasm-2.6.xxx
# rpm -Uvh oracleasmlib-xxx
# /etc/init.d/oracleasm enable
# /etc/init.d/oracleasm lisdisks
(5) Relink RDBMS ORACLE_HOME Binary
Note: complete full steps in one node, then proceed to next
As RDBMS owner id “oracle”:
$ /bin/relink all
(6) Relink GRID ORACLE_HOME Binary
Note: complete full steps in one node, then proceed to next
As UNIX/Linux “root”:
# cd /crs/install
# ./rootcrs.pl -unlock
As RDBMS owner id “oracle”:
$ cd /bin
$ ./relink all
As UNIX/Linux “root”:
# cd /rdbms/install
# ./rootadd_rdbms.sh
# cd /crs/install
# ./rootcrs.pl –patch
(7) Enable CRS auto-startup and start CRS on all nodes
Note: complete full steps in one node, then proceed to next
As UNIX/Linux “root”:
# /bin/crsctl start crs
# /bin/crsctl enable crs
(8) Double check if DB, instances and all resrouces are ONLINE.
As RDBMS owner id “oracle”:
$ crsctl stat res -t
Reference :: How to Check Whether Oracle Binary/Instance is RAC Enabled and Relink Oracle Binary in RAC [ID 284785.1]

Database Recovery Methods

RMAN No comments :

FRM 92101 There was a failure in the forms server during start up

AppsDBA , R12.2 No comments :

FRM 92101 There was a failure in the forms server during start up. This could happen due to invalid configuration.
Logfile location:
$LOG_HOME/ora/10.1.3/opmn/forms_default_group_1/formsstd.out
Example Log file:
12/07/06 02:55:04 FormsServlet init():
configFileName: /R12/oracle/APPS_R12/apps/test_testr12/ora/10.1.2/forms/server/appsweb.cfg
testMode: false
12/07/06 02:55:05 Oracle Containers for J2EE 10g (10.1.3.4.0) initialized
12/07/06 03:17:36 ListenerServlet init()
12/07/06 03:17:41 Forms session <1> aborted: runtime process failed during startup with errors /R12/oracle/APPS_R12/apps/tech_st/10.1.2/bin/frmweb: error while loading shared libraries: libXm.so.2: cannot open shared object file: No such file or directory
12/07/06 03:19:36 Forms session <2> aborted: runtime process failed during startup with errors /R12/oracle/APPS_R12/apps/tech_st/10.1.2/bin/frmweb: error while loading shared libraries: libXm.so.2: cannot open shared object file: No such file or directory
Cause:
The cause is not unusual with Linux, or Oracle, or Oracle Apps. It’s that Oracle Forms is looking for a library file. But the file doesn’t exist in the expected place. Nor does a link. Not again.
In this case, libXm.so.2 can’t be found.
Solution:
Check this directory and below mentioned files "/usr/X11R6/lib".
/usr/lib/libMrm.so.3.0.2
/usr/lib/libMrm.so.4.0.1
/usr/lib/libUil.so.3.0.2
/usr/lib/libUil.so.4.0.1
/usr/lib/libXm.so.3.0.2
/usr/lib/libXm.so.4.0.1
If its not there then create it below mentioned manner,
1. As root:
mkdir -p /usr/X11R6/lib
2. Make Links To The Original Files:
cd /usr/X11R6/lib
ln -s /usr/lib/libMrm.so.3.0.2 .
ln -s /usr/lib/libMrm.so.4.0.1 .
ln -s /usr/lib/libUil.so.3.0.2 .
ln -s /usr/lib/libUil.so.4.0.1 .
ln -s /usr/lib/libXm.so.3.0.2 .
ln -s /usr/lib/libXm.so.4.0.1 .
Make Links With An Abbreviated Name:
ln -s /usr/lib/libXm.so.3.0.2 libXm.so.3
ln -s /usr/lib/libXm.so.4.0.1 libXm.so.4
ln -s /usr/lib/libXm.so.4.0.1 libXm.so
ln -s /usr/lib/libUil.so.4.0.1 libUil.so.4
ln -s /usr/lib/libUil.so.3.0.2 libUil.so.3
ln -s /usr/lib/libUil.so.4.0.1 libUil.so
ln -s /usr/lib/libMrm.so.4.0.1 libMrm.so.4
ln -s /usr/lib/libMrm.so.3.0.2 libMrm.so.3
ln -s /usr/lib/libMrm.so.4.0.1 libMrm.so
ln -s /usr/lib/libMrm.so.3.0.2 libMrm.so.2
ln -s /usr/lib/libUil.so.3.0.2 libUil.so.2
ln -s /usr/lib/libXm.so.3.0.2 libXm.so.2
3. Check the issue again forms will open without FRM 92101 error.

Fast formula invalid objects compile procedure

AppsDBA , R12.2 No comments :

You have two options for this,
Run the Bulk compile concurrent request from your respective legislation and verify via the log file if it completes with no errors.
Back end runs: Using FFXBCP command
i.e. $FF_TOP/bin/FFXBCP <appsuser>/<appspassword> 0 Y %% %%
Please see this metalink document id for your reference:
Doc ID 167689.1 How to Compile Fast Formulas From the Server (via FFXBCP)
Doc id 155737.1 How To Compile Oracle Fast Formulas
Doc ID 185723.1 How to Diagnose Formula Compilation Errors due to APP-FF-33980: Internal Error Attempting to Generate Package

Steps for finding password of a User in Oracle Apps R12

AppsDBA , R12.2 No comments :

Here is a wonderful oracle seeded Procedure fnd_web_sec.get_guest_username_pwd which will help us to find out user password.
Please use with this care and don't misuse this.
Kindly Follow the below mentioned steps:
Login to Apps user
Step 1:
--Package Specification
CREATE OR REPLACE PACKAGE get_pwd
AS
FUNCTION decrypt (KEY IN VARCHAR2, VALUE IN VARCHAR2)
RETURN VARCHAR2;
END get_pwd;
/
Step 2:
--Package Body
CREATE OR REPLACE PACKAGE BODY get_pwd
AS
FUNCTION decrypt (KEY IN VARCHAR2, VALUE IN VARCHAR2)
RETURN VARCHAR2
AS
LANGUAGE JAVA
NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String';
END get_pwd;
/
Step 3:
Query to get password for apps user.
SELECT
(SELECT get_pwd.decrypt (UPPER ((SELECT UPPER (fnd_profile.VALUE ('GUEST_USER_PWD')) FROM DUAL)), usertable.encrypted_foundation_password) FROM DUAL) AS apps_password
FROM fnd_user usertable
WHERE usertable.user_name LIKE UPPER ((SELECT SUBSTR (fnd_profile.VALUE ('GUEST_USER_PWD') ,1 , INSTR (fnd_profile.VALUE ('GUEST_USER_PWD'), '/') - 1 ) FROM DUAL))
Step 4:
--Query for finding any application user
SELECT usr.user_name,
get_pwd.decrypt
((SELECT (SELECT get_pwd.decrypt
(fnd_web_sec.get_guest_username_pwd,
usertable.encrypted_foundation_password
)
FROM DUAL) AS apps_password
FROM fnd_user usertable
WHERE usertable.user_name =
(SELECT SUBSTR
(fnd_web_sec.get_guest_username_pwd,
1,
INSTR
(fnd_web_sec.get_guest_username_pwd,
'/'
)
- 1
)
FROM DUAL)),
usr.encrypted_user_password
) PASSWORD
FROM fnd_user usr
WHERE usr.user_name = '&USER_NAME';

Changes to OID Users Are Not Being Provisioned to E-Business Suite (EBS) FND_USER Table

AppsDBA No comments :

To resolve the issue add the users to be provisioned to EBS to the EBS Service Subscription List.
A. Using OIDDAS Provisioning Console
1. Access OIDDAS and login as ORCLADMIN user.
2. Navigate to Directory --> Services --> EBS instance name.
3. Click on Edit Subscription.
4. Click Edit on cn=ACCOUNTS folder.
5. Search for the user by name.
6. Add the user to the Subscription List.
B. Using PROVSUBTOOL
The commandline tool PROVSUBTOOL can be used to add multiple users to the subscription list in batch update.
Ref::Metalink id 1129023.1

Disabling SSL for EBS R12

AppsDBA , R12.2 No comments :

The SSL can be enabled in R12 environment by following the oracle support document: 376700.1 Recently I cloned R12 instance in test server that time I disable SSL settings because in my production environment SSL enabled.
To disable the ssl:
Changed the value for context variables s_url_protocol, s_local_url_protocol,s_webentryurlprotocol in context file from https to http.
Changed the value for s_active_webport to the value for context variable s_webport.
Changed the value of s_help_web_agent, s_login_page, s_external_url context variables to point to http url and the port in the url refers to s_webport.
Executed autoconfig after the changes and bounced MT services. The appslocal login url worked just fine, no problem but the appslogin url had a problem, it automatically switched from http://hostname:port/OA_HTML/AppsLogin to https://hostname:port/OA_HTML/AppsLogin and errored out with some ssl error.
The issue is because of ssl_terminator.conf included in the httpd.conf file. To resolve the issue, set the value for context variable s_enable_sslterminator to #. After executing autoconfig, the include ssl_terminator.conf is commented out in the httpd.conf.
After the bounce of MT services, the ssl was disabled and the Appslogin url with http protocol, worked just fine

Function not available to this responsibility When Trying to Access Custom Form

AppsDBA , R12.2 No comments :

We cloned R12 instance in test server after that the Apps technical team faced
'Function not available to this responsibility' error when they trying to access custom form.
The reason for this issue is that, missing entry for CUSTOM_TOP under default.env file.
Then we followed below steps to solve this issue:
1. Login to Linux server with APPLTEST user.
2. Go to $INST_TOP/ora/10.1.2/forms/server directory.
3. Ensure that your CUSTOM_TOP's are registered in the default.env file.
We should create an entry for env variable CUSTOM_TOP
like below in default.env file present under location.
$INST_TOP/ora/10.1.2/forms/server directory.
For Example:
APPL_TOP=/home/applmgr/PROD/apps/apps_st/appl
CUSTOM_TOP=/home/applmgr/PROD/apps/apps_st/custom
4. Restart the middle tier services.
5. Retest the issue.

R12 – Shortcut to access the forms URL and sysadmin Responsibility page

AppsDBA No comments :

It will be skip the login page and direct to the sysadmin responsibility page.
To access the Sysadmin responsibility page
http://<domain><PORT>/OA_HTML/fndvald.jspusername=SYSADMIN&password=SYSADMIN
To Launch the forms directly
http://<host>.<domain>:<port>/forms/frmservlet.
Modify the context variable parameter (s_appserverid_authentication) from SECURE to OFF and run autoconfig, then forms will startup without that authorization error.

Workflow Notification mailer issue

AppsDBA , R12.2 , WF No comments :

I saw the particular user mail status in that all status was shows expired.
So I submitted "Move Messages from Exception to Normal Queue of Workflow Agent" concurrent request. It will ask parameters then we need to give WF component name in my case I was given WF_NOTIFICATION_OUT.
How To Move Notifications From Exception Queue To Normal Queue? ID 472204.1
FNDWF_MOVE_MSGS_EXCEP2NORMAL "The agent is not found" [ID 760983.1]
Error APP-FND-1030 Is Displayed When Trying To Submit "Move messages from Exception to Normal Queue of Workflow Agent" FNDWF_MOVE_MSGS_EXCEP2NORMAL [ID 1451820.1]
For Enabling De-Queue we need run below procedure,
exec dbms_aqadm.start_queue(queue_name=>'APPLSYS.AQ$_WF_NOTIFICATION_OUT_E',
dequeue=>TRUE,enqueue=>FALSE)

Workflow Structure in R12

How To Ensure Load Balancing Of Concurrent Manager Processes In PCP-RAC Configuration

AppsDBA , R12.2 No comments :

How to troubleshoot issues where load balancing of Concurrent manager processes does not work in a RAC with PCP configuration.
In a RAC with PCP configuration, it is noticed that the 2 instances are not sharing the load and most of the time only one node is having concurrent manager processes running. How to ensure that the concurrent manager processes are load balanced across the PCP nodes ?
Solution
There are 2 types of resources in use for PCP/RAC:
1.O/S processes for manager and requests
2.Shadow processes for database connection for managers and requests.
O/S processes for managers (e.g. FNDLIBR, etc.) and request processes (ar60run, sqlplus, etc.)
will run on primary node defined for manager.
Shadow processes for database connection use load balanced alias (s_cp_twotask) and the load is
distributed between database nodes by sqlnet. This is controlled by sqlnet and CP code is not
involved. This should mimic what happens to sqlplus connections using load balanced alias for
RAC.
The following sql can be used to check how manager connections are spread:
Select inst_id, count (*) from gv$session where process in (select os_process_id from fnd_concurrent_processes where process_status_code = 'A') group by inst_id;
Now to load balance the shadow concurrent manager processes please set the below:
1.Set the profile option "Concurrent: PCP Instance Check" to "OFF"
2. Set the context variable s_cp_twotask to '<SERVICE_NAME>_806_BALANCE' (This entry can be found in the tnsnames.ora file). You have to set this in both RAC nodes.
3. Run autoconfig and after that you can check for the load balancing aspects
Ref :: Using Server side load balancing with MRP will break MRP, see Note.279156.1

Internal Login Flow in Oracle Apps

AppsDBA , R12.2 No comments :

1.DB connection is established using APPLSYSPUB user.
This user “APPLSYSPUB” is having access to fnd_user view and a small set of other public tables needed to establish the initial connection.
2.Once DB connection is established FND_USER table is used to get ENCRYPTED_FOUNDATION_PASSWORD.
3.Using GUEST/ORACLE password combination and ENCRYPTED_FOUNDATION_PASSWORD string obtained from 2 above,
we get Apps schema password.
4.Internally it tries to connect to Apps schema with the password retrieved in step 3 above.
If the connection fails, then
a)The GUEST username password is incorrect
b)The FNDNAM (APPS) environment variable is set incorrectly.
c)Some other problem prevented a connection
5 Using Apps password obtained in Step 3 and ENCRYPTED_USER_PASSWORD string from FND_USER table, password for Application user (e.g. SYSADMIN) is obtained.
6. The Application user password obtained in Step 5 is compared to the application user password entered by user in login screen. If both passwords match then user is allowed to get into self-service.
7. A list of responsibilities assigned to that user is shown.
The user picks one of the responsibilities listed.
8. Each responsibility has a data group and application defined for it.Together, the data group and application define the Oracle account the responsibility uses.

Life Cycle of concurrent Request

AppsDBA , CM , R12.2 No comments :

How to apply patch while you are in the middle of patching

AppsDBA No comments :

Sometimes when you are in the middle of applying a patch you may get adworkers errors or you can find out that a patch is missing. So you need to apply a second patch (which solves the problem) in the middle of a running patch.
1. Use adctrl (option 3) to tell all the existing workers to QUIT
2. Use adctrl (option 5) to tell managers that all workers have QUIT. (Adpatch session ends!)
3. Backup tables applsys.ad_deferred_jobs and applsys.fnd_install_processes.
Login as APPLSYS user and execute:
ALTER "TABLE" applsys.ad_deferred_jobs "RENAME" TO ad_deferred_jobs_old;
ALTER "TABLE" applsys.fnd_install_processes "RENAME" TO fnd_install_processes_old;
ALTER "INDEX" applsys.ad_deferred_jobs_u1 "RENAME" TO ad_deferred_jobs_u1_old;
ALTER "INDEX" applsys.fnd_install_processes_u1 "RENAME" TO fnd_install_processes_u1_old;
4. Go to $APPL_TOP/admin/SID/ for example $APPL_TOP/admin/TEST/ and rename the existing directory "restart"
$mv restart restart.old
5. Use adpatch to apply the second/other patch.
6. Login as APPLSYS and revert back to the original tables, ad_deferred_jobs and fnd_install_processes
ALTER "TABLE" applsys.ad_deferred_jobs_old "RENAME" TO ad_deferred_jobs;
ALTER "TABLE" applsys.fnd_install_processes_old "RENAME" TO fnd_install_processes;
ALTER "INDEX" applsys.ad_deferred_jobs_u1_old "RENAME" TO ad_deferred_jobs_u1;
ALTER "INDEX" applsys.fnd_install_processes_u1_old "RENAME" TO fnd_install_processes_u1;
7. Replace the original restart directory:
cd $APPL_TOP/admin/SID/ for example $APPL_TOP/admin/TEST/
mv restart restart_new
mv restart.old restart
8. Run adpatch to continue the first patch (with continue session?Yes)
9. Use adctrl (option 2, will change status to “Fixed/Restart”) to restart the failed workers for first patch

Cannot View Concurrent Manager Log And Out Files in R12 (APP-FND-01634 )

AppsDBA , CM , R12.2 No comments :

'APP-FND-1634-The log file &FILENAME does not exist or this program is restricted from reading it'
If the concurrent request has completed then please contact your system administrator.
APP-FND-1636 NO REPORT AVAILABLE FOR THIS CONCURRENT PROCESS
Cause:
Profile Option 'RRA:enabled' setting is not correct.
Solution:
To implement the solution, please execute the following steps:
1. Shut down managers and verify no FNDLIBR processes are running.
2. Go into the responsibility: System Administrator
3. Navigate to profile/system
4. Search for profile 'RRA:enabled' and set the value to Yes.
5. Save
6. Restart the managers
7. Retest the issue.

Sleep Seconds in Concurrent manager

AppsDBA , CM , R12.2 No comments :

Setting concurrent manager sleep seconds
S = N * (1 – U) * T
S--Setting.
N--Number of manager processes
U--Average Utilization of level of concurrent managers.
T--Average time of how long the request is allowed to be pending.

EBS Release 12.2 Technology Components

AppsDBA , R12.2 No comments :

Oracle Technology	Version included in or required by Release 12.2.2	Most Recent Certified Version for Release 12.2
Oracle Database 11g	11.2	11.2
XDK for the Database Tier	11.2	11.2
Oracle Application Server (for Application Tier Forms and Reports)	10.1.2.3	10.1.2.3
Oracle Application Server/ Oracle Fusion Middleware (for Application Tier Java Code and Oracle Application Framework)	11.1.1.6	11.1.1.6
Oracle Java Required Files (JRF)	11.1.1.6	11.1.1.6
XDK for the Application Tier	11.1.1.6	11.1.1.6
Oracle HTTP Server	11.1.1.6	11.1.1.6
Oracle WebLogic Server	Oracle WebLogic Server 10.3.6 in Oracle Fusion Middleware 11g Release 1 (11.1.1.6)	Oracle WebLogic Server 10.3.6 in Oracle Fusion Middleware 11g Release 1 (11.1.1.6)
JSP Compiler	WebLogic JSP Compiler 11.1.1.6 (weblogic.appc)	WebLogic JSP Compiler 11.1.1.6 (weblogic.appc)
JSP Engine	WebLogic JSP Engine 11.1.1.6 (weblogic.appc)	WebLogic JSP Engine 11.1.1.6 (weblogic.appc)


Technology Components Delivered in APPL_TOP	Version included in or required by Release 12.2.2	Most Recent Certified Version for Release 12.2
Oracle JDeveloper runtime libraries	10.1.3	10.1.3
Oracle BI Beans	3.1.1.11	3.1.1.11
Oracle Thin JDBC Drivers (for Application Tier Java Code)	11.2	11.2



Externally Installed Oracle Technology	Version included in or required by Release 12.2.2	Most Recent Certified Version for Release 12.2
Oracle Single Sign-On	N/A	N/A
Oracle Internet Directory	11g Release 1 PS4 (11.1.1.5.0)	11g Release 1 (11.1.1.7.0)
Oracle Access Manager	11.1.1.5	11.1.2.1
Oracle Business Intelligence Enterprise Edition	11.1.1.6	11.1.1.6
Oracle Discoverer	11.1.1.6	11.1.1.7
Oracle WebCenter	11.1.1.6	11.1.1.7
Oracle Portal	11.1.1.6	11.1.1.7
Oracle BPEL Process Manager	11.1.1.6	11.1.1.7
Oracle Secure Enterprise Search	11.1.2.2	11.1.2.2
Oracle Collaboration Suite	10.1.2	10.1.2
Oracle Universal Content Management	10g Release 3	10g Release 3
Oracle Enterprise Manager	11.1.0.1	11.1.0.1



Java Technology	Version included in or required by Release 12.2.2	Most Recent Certified Version for Release 12.2
Java SE Development Kit – JDK (for Application Tier Java Code and Oracle Application Framework)	6	6
Java SE Development Kit – JDK (for Concurrent Processing Tier)	6	6
Native Java Plug-in (for Client side Java code running in the Browsers)	6	7

Oracle Database Mobile Server Installation

MSCA/MWA No comments :

Architecture:

Step 1: Pre-requisites,
1. Oracle Database.
2. Application Server,
Oracle Weblogic (I've used Oracle Weblogic 12c).
(or)
Oracle Glassfish.
(or)
Oracle Application Server.
Step 2: Installing Database Mobile Server,
Unzip the DMS_11.2.0.0.0_LINUX.zip

Go to Disk1-- you can find two folders one for linux 32 bit and another one linux 64 bit, In my case I'm using linux64 bit--> Go to Linux64 folder and run the runInstaller file.