EBS Accessgate Patch for OAM 11gR2

New EBS Accessgate patch :21522495

AccessGate patch 21522495 version 1.3.0.0 as referenced in Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate ( Doc ID 1484024.1 )

OAM and EBS Accessgate Issues

The basic trouble shoot For OAM and EBS Accessgate

Troubleshooting Oracle Access Manager and Oracle E-Business Suite AccessGate (Doc ID 1077460.1)

Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate (Doc ID 1484024.1)

verify user with role UMX|APPS Schema Connect

Set Up Necessary Oracle E-Business Suite Users

Set up a necessary Oracle E-Business Suite user with role UMX|APPS Schema Connect. Refer to Section 2.1.3 Set Up Necessary Oracle E-Business Suite Users in My Oracle Support Knowledge Document 974949.1, titled Oracle E-Business Suite Software Development Kit for Java Readme.

After setting up the user, logon locally to Oracle E-Business Suite as the user with role UMX|Apps Schema Connect.

http://.:/OA_HTML/AppsLocalLogin.jsp

If this user has just been created, you will be prompted on logon to Oracle E-Business Suite to reset the password. Reset the password.

Verify that you can successfully logon locally with the new password as the user with role UMX|Apps Schema Connect.

Solution:

SQL> desc wf_user_roles

 Name                                      Null?    Type

 ----------------------------------------- -------- ----------------------------

 USER_NAME                                 NOT NULL VARCHAR2(320)

 ROLE_NAME                                 NOT NULL VARCHAR2(320)

 USER_ORIG_SYSTEM                                   VARCHAR2(30)

 USER_ORIG_SYSTEM_ID                                NUMBER

 ROLE_ORIG_SYSTEM                                   VARCHAR2(30)

 ROLE_ORIG_SYSTEM_ID                                NUMBER

 START_DATE                                         DATE

 EXPIRATION_DATE                                    DATE

 ASSIGNMENT_TYPE                                    VARCHAR2(1)

 PARENT_ORIG_SYSTEM                                 VARCHAR2(30)

 PARENT_ORIG_SYSTEM_ID                              NUMBER

 PARTITION_ID                                       NUMBER

 ASSIGNMENT_REASON                                  VARCHAR2(4000)

SQL> select USER_NAME,ROLE_NAME from wf_user_roles where USER_NAME='EBSADMIN';

USER_NAME

--------------------------------------------------------------------------------

ROLE_NAME

--------------------------------------------------------------------------------

EBSADMIN

EBSADMIN

EBSADMIN

FND_RESP0:20419

EBSADMIN

FND_RESP1:20420

USER_NAME

--------------------------------------------------------------------------------

ROLE_NAME

--------------------------------------------------------------------------------

EBSADMIN

FND_RESP|FND|APPLICATION_DEVELOPER|STANDARD

EBSADMIN

FND_RESP|FND|APPLICATION_DIAGNOSTICS|STANDARD

EBSADMIN

FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD

USER_NAME

--------------------------------------------------------------------------------

ROLE_NAME

--------------------------------------------------------------------------------

EBSADMIN

UMX|APPS_SCHEMA_CONNECT

EBSADMIN

UMX|ODF_DIAGNOSTICS_SUPER_USER_ROLE


If the 'Apps Schema Connect Role' role is not present in the wf_user_roles for the ASADMIN user, then run the 'Workflow Directory Services User/Role Validation' concurrent program to grant the role.

ORA-20002: 3825: Error '-24033 - ORA-24033: no recipients for message' encountered during execution of Rule function 'WF_RULE.ERROR_RULE'

ORA-20002: 3825: Error '-24033 - ORA-24033: no recipients for message' encountered during execution of Rule function 'WF_RULE.ERROR_RULE' for event 'oracle.apps.fnd.cp.gsc.SvcComponent.stop' with key 'SVC:29-APR-2015'. FUNCTION_NAME=WF_EVENT_OJMSTEXT_QH.enqueue()
Error:
When we try to start/stop the Worflow mailer it shows this error,

ORA-20002: 3825: Error '-24033 - ORA-24033: no recipients for message' encountered during execution of Rule function 'WF_RULE.ERROR_RULE' for event 'oracle.apps.fnd.cp.gsc.SvcComponent.stop' with key 'SVC:29-APR-2015'. FUNCTION_NAME=WF_EVENT_OJMSTEXT_QH.enqueue()

Solution:

To resolve the issue try restarting the components

1. Workflow Mailer Service

2. Workflow Document Web Services 

3. Workflow Agent Listener Service

Navigation to restart the components

Login as SYSADMIN --> System Administrator --> Oracle Application Manager --> Workflow 

Click on "Notification Mailer" --> Click "Workflow Mailer Services" Under Container Column --> Select "Workflow Mailer Services" --> Select "Start" --> "Go" button --> Ok

Similary do the same for "Workflow Document Web Services" and "Workflow Agent Listener Service"

Now the workflow mailer will be Started/Stopped

Verify registration using OAM Console "out of space in CodeCache for adapters"

 Verify registration using OAM Console

Logon to the OAM Console

http://.:/oamconsole

Verify that the following artifacts are visible now in the OAM Console, under Launch Pad:.

• Application Security (tab) > Click on the 'Agents' icon > Search for {Identifier for your WebGate}
• Application Security (tab) > Click on 'Host Identifiers' (in the 'Access Manager' region) > Search for {Identifier for your WebGate}
• Application Security (tab) > Click on 'Application Domains' (in the 'Access Manager' region) > Search for {Identifier for your WebGate}

If any one see "out of space in CodeCache for adapters" error below is the solution.

Solution:

On your oam_domain location:


/apps/oemora/Oracle/Middleware/user_projects/domains/oam_domain/bin/setDomainEnv.sh


set USER_MEM_ARGS=-XX:ReservedCodeCacheSize=128M -Xms2048M -Xmx2048M -XX:PermSize=256M -XX:MaxPermSize=512M -XX:+UseParallelGC -XX:+UseParallelOldGC -verbose:gc -XX:+PrintGCDetails -XX:-PrintGCDateStamps -Xloggc:/temp/gc/wls_pre_sizing_jms.log

OAM Webgate 11g EditHttpConf tool

While I was working on  OAM (Oracle Access Manager) 11g, trying to get the Webgate agent to install over OHS (Oracle HTTP Server) I came across this odd error:

[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/Oracle_OAMWebGate1/webgate/ohs/tools/setup/InstallTools]$ ./EditHttpConf \

> -w /apps/oemora/Oracle/Middleware/Oracle_WT1/instances/instance8/config/OHS/ohs1 \

> -oh /apps/oemora/Oracle/Middleware/Oracle_OAMWebGate1

./EditHttpConf: error while loading shared libraries: libclntsh.so.11.1: cannot open shared object file: No such file or directory

Obviously, the webgate installer doesn't set up the environment for you.  In this case, there's a missing shared library named "libclntsh.so.11.1".  In my environment, there were several instances of that library.  I got random obscure errors, ranging from "unable to run "Ob*", to wrong ELFCLASS.  In the end, I had help from fellow colleagues, but long story short, I needed to reference the shared library in the OHS_HOME directory- in my case it is/u01/middleware/ohs_home/lib, so I needed to run this command:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$WL_HOME/Oracle_WT1/lib

In doing so, I finally got it to run correctly:

[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/Oracle_OAMWebGate1/webgate/ohs/tools/setup/InstallTools]$ ./EditHttpConf \

> -w /apps/oemora/Oracle/Middleware/Oracle_WT1/instances/instance8/config/OHS/ohs1 \

> -oh /apps/oemora/Oracle/Middleware/Oracle_OAMWebGate1

The web server configuration file was successfully updated

/apps/oemora/Oracle/Middleware/Oracle_WT1/instances/instance8/config/OHS/ohs1/httpd.conf has been backed up as /apps/oemora/Oracle/Middleware/Oracle_WT1/instances/instance8/config/OHS/ohs1/httpd.conf.ORIG

[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/Oracle_OAMWebGate1/webgate/ohs/tools/setup/InstallTools]$

Undo table space using more and 100% Full

Undo table space is not release the data and using more space.

When the UNDO tablespace is created with NO AUTOEXTEND, following the allocation algorithm, here is the explanation for this correct behavior:

For a fixed size UNDO tablespace (NO AUTOEXTEND), starting with 10.2, we provide max retention given the fixed undo space, which is set to a value based on the UNDO tablespace size.
This means that even if the undo_retention is set to a number of seconds (900 default), the fixed UNDO tablespace supports a bigger undo_retention time interval (e.g: 36 hours), based on the tablespace size, thing that makes the undo extents to be UNEXPIRED. But this doesn't indicate that there are no available undo extents when a transaction will be run in the database, as the UNEXPIRED undo segments will be reused.

concerning an UNDO tablespace created with AUTOEXTEND OFF in 10gR2, so there is not need to add more space to it or be concerned by the fact that it appears to be 100% full.

Whether the undo is automatically managed by the database by checking the following instance parameter:
UNDO_MANAGEMENT=AUTO

1. Whether the undo tablespace is fixed in size:
   
    SELECT autoextensible
        FROM dba_data_files
        WHERE tablespace_name=''
   
   This returns "NO" for all the undo tablespace datafiles.
2. The undo tablespace is already sized such that it always has more than enough space to store all the undo generated within the undo_retention time, and the in-use undo space never exceeds the undo tablespace warning alert threshold (see below for the query to show the thresholds).
3. The tablespace threshold alerts recommend that the DBA add more space to the undo tablespace:
   
    SELECT creation_time, metric_value, message_type, reason, suggested_action
        FROM dba_outstanding_alerts
        WHERE object_name='';
   
   This returns a suggested action of: "Add space to the tablespace".
   
   Or,
   
   This recommendation has been reported in the past but the condition has now cleared:
   
   SQL> SELECT creation_time, metric_value, message_type, reason, suggested_action, resolution
        FROM dba_alert_history
        WHERE object_name='';
4. The undo tablespace in-use space exceeded the warning alert threshold at some point in time. To see the warning alert percentage threshold, issue:
   
    SELECT object_type, object_name, warning_value, critical_value
   FROM dba_thresholds
   WHERE object_type='TABLESPACE';
   
   To see the (current) undo tablespace percent of space in use:
   
    SELECT
            ((SELECT (NVL(SUM(bytes),0))
              FROM dba_undo_extents
              WHERE tablespace_name=''
              AND status IN ('ACTIVE','UNEXPIRED')) * 100)/       
            (SELECT SUM(bytes)
             FROM dba_data_files
             WHERE tablespace_name='')
            "PCT_INUSE"
        FROM dual
5. SOLUTION:
6. 1. Set the AUTOEXTEND and MAXSIZE attributes of each datafile of the undo tablespace in such a way that they are autoextensible and the MAXSIZE is equal to the current size (so the undo tablespace now has the AUTOEXTEND attribute but does not autoextend):
      
       ALTER DATABASE DATAFILE '' AUTOEXTEND ON MAXSIZE
      
      With this setting, V$UNDOSTAT.TUNED_UNDORETENTION is not calculated based on a percentage of the undo tablespace size. Instead it is set to the maximum of (MAXQUERYLEN secs + 300) and UNDO_RETENTION.
   2. Set the following instance parameter:
      
      _smu_debug_mode=33554432
      
      With this setting, V$UNDOSTAT.TUNED_UNDORETENTION is not calculated based on a percentage of the fixed size undo tablespace. Instead it is set to the maximum of (MAXQUERYLEN secs + 300) and UNDO_RETENTION.
   3. Set the following instance parameter:
      
      _undo_autotune = false
      
      With this setting, V$UNDOSTAT (and therefore V$UNDOSTAT.TUNED_UNDORETENTION) is not maintained and the undo retention used is based on the UNDO_RETENTION instance parameter.
      
      
      NOTE: This means you loose all advantages in having automatic undo management and is not an ideal long term fix.

   Automatic Tuning of Undo_retention Causes Space Problems (Doc ID 420525.1).