November 20, 2008

11i/R12: Not a valid responsibility for the current user

After attaching a responsibility to a user often used to receive,

"XXXX is not a valid responsibility for the current user. Please contact your System Administrator."

And the attached responsibility will not appear in the Home Page until you bounce the apache. It appears from 11i.FND.H to 12.0.4

We ran into many SR's while working with different customers at different patch levels.

According Note: 374309.1 Newly added responsibility is not displayed until Apache is bounced, after applying ATG RUP3 or ATG RUP4,

It is because of delayed processing of changes through the Apache Java Cache mechanism.

Normally when you are adding a responsbility to a user or end date a responsibility it fires considerable number of business events like,

  • oracle.apps.fnd.wf.ds.userRole.created
  • oracle.apps.fnd.user.role.insert
  • oracle.apps.fnd.wf.ds.userRole.updated, etc.,

If the Workflow Deferred Agent Listener and Workflow Java Deferred Agent Listener are not running, then these business events will not get processed.

Then we will face the above said error. Hence, It is necessary to ensure the below Workflow Service Components are up and running (OAM -> Workflow Manager -> Service Components) as one of the verification checks,

  • Workflow Deferred Agent Listener
  • Workflow Java Deferred Agent Listener

October 12, 2008

Sysadmin Zoom functionality using Oracle Forms Personalization

Oracle introduced Forms Personalizations Feature, which was first introduced with FND Patch Set Level H (FND.H). Since then, lots of customizations got moved from CUSTOM.pll.

One of simply achievable functionality is Zoom functionality. Often my developers / APPS sysadmins wants to Navigate in the following flow.

1. Define Users Window -> Responsibilities Details Window -> Request Group Details Window -> Concurrent Program Details Window -> Executable Details Window
[OR]
2. Define Users Window -> Responsibilities Details Window -> Menu Details Window -> Sub Menu Details Windows -> Function Details Window

Download the below ldt file and Upload the personalizations into your test instance using below command.
Datafile (.ldt)

FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct sysadmincus.ldt

Now Login into Applications -> Define Users Window -> Query for a User -> Place the cursor on a responsibility -> Tools Menu -> Responsibility Details

It will take you to the Responsibilities Details Window.

When you are in the Responsibilities Window, you can find below menu items

  • Tools -> Menu Details
  • Tools -> Requeset Group Details
When you are in Request Group Details window, you can find below menu items
  • Tools -> Program Details
  • Tools -> Requeset Set Details
When you are in Concurrent Program Details window, you can find below menu items
  • Tools -> Executable Details
When you are in Concurrent Program Details window, you can find below menu items
  • Tools -> Executable Details
When you are in Menu Details window, you can find below menu items
  • Tools -> Submenu Details
  • Tools -> Function Details

September 18, 2008

After R12 Installation, $ORACLE_HOME/.patch_storage consumes more space.

After R12 installation we find the RDBMS patching backup area ($ORACLE_HOME/.patch_storage) takes more than 5 GB space.
This will increase you backup time and requires more backup space.

Note 550522.1 stats,
From OPatch Version 10.2 Opatch does not backup only the affected modules, it also takes a backup of the complete affected libraries to $ORACLE_HOME/.patch_storage//backup// for faster rollback.
This causes the .patch_storage directory to grow accordingly to the size of the libraries and modules being patched.

Hence after every R12 installation, we can clean up this area. Steps are,

•Login as Database OS User
•Set the Path
$ PATH=$ORACLE_HOME/OPatch:$PATH
$ export PATH
$ which opatch
$ opatch lsinventory -invPtrLoc $ORACLE_HOME/oraInst.loc

•Check the size of .patch_storage
$ du -sh $ORACLE_HOME/.patch_storage

•Run opatch cleaning
$ opatch util cleanup -help
$ opatch util cleanup -invPtrLoc $ORACLE_HOME/oraInst.loc

•After cleaning check the .patch_storage size
$ du -sh $ORACLE_HOME/.patch_storage

Note:550522.1 How To Avoid Disk Full Issues Because OPatch Backups Take Big Amount Of Disk Space.