Oracle Security and Administration

Oracle 12 New Sysadmin functionality

on Tuesday, 01 January 2013. Posted in Oracle Security and Administration

Fear not System Administrators: There are exciting new system administration features in the pipeline for managing e-Business Suite environments.

One seemingly never ending task that takes up a considerable amount of time for System Administrators is cloning.  It wasn’t long ago that cloning was done manually (maybe I’m dating myself), using home grown scripts and following documented (or not so documented) procedures.  I’m sure there are still a few of us out there who still follow manual processes, and although Oracle Applications Manager and the adclone utilities and scripts have helped sysadmins reduce the time and effort for cloning, there are still a few areas where things we being done manually behind the scenes.  I’m happy to report the product teams at Oracle have been hard at work, and will be releasing a number of new or improved features for e-Business Suite management in the future.  Here are a few of the improvements I learned about regarding cloning.

Cloning support through OAM will be decommissioned, and in the future cloning will be accomplished through the cloning dashboard in OEM - with the e-Business Suite add on (the “apps pack") installed.  The process will be automated through a provisioning framework, where OEM will walk an administrator through an interview process to determine cloning parameters.  Sys admins will be able to create images, so the possible cloning combinations will be:


  • Source to Target (e.g. PROD to DEV);
  • Source to Image (e.g. PROD to an image to put on the shelf and use for future clones to DEV, UAT, etc.); and
  • Image to Target (e.g. refresh DEV from an earlier image of PROD or another imaged environment).

    One feature I’m sure many have been waiting for is the ability to scramble or purge sensitive data.  I’ve been told this feature will work with 11i10 and Release 12.  This is great news for cloning production environments down to development and test instances where the apps password isn’t always policed as it is in production.  Although the instance might not be production, the data still originated in a production environment, and the ability to scramble or purge sensitive HR, payroll or other personal data (e.g. to meet HIPAA requirements) has been needed for a long time.  It was not made clear as to how extensive the process was, or what data elements for each of the modules would be covered, but it was my understanding that the scrambling will be implemented as an engine where additional input parameters can be input to the process.  Data obfuscation will occur during the cloning of either a Source -> Target or Source -> Image clone, and will not be reversible.

    Also I will be attaching some interesting white papers that some of my friends at Oracle sent me last week.

Sizing your ERP Production Environment

on Tuesday, 01 January 2013. Posted in Blog, Oracle Security and Administration

One question that comes often, how  to size your production, this is not science it is an art, yes guidelines exists but no two client environments are the same.


I like to begin by using the following table to define the online user workload by EBS application family.  This will provide a high level sizing based on blended metrics for multiple application modules within the application family.  Also most vendors have detailed questionaires to help with the sizing exercise. 

Oracle EBS
Application Families
Numbers of Users by EBS Application Family # Sessions per User(default = 1)
* # Named
# Concurrently Active Users
* Total * Light * Std. * Heavy
 Supply Chain Planning 6 6      5  
 Logistics & Transportation    Management            
 Order Management 12 12   6 6  
 Manufacturing 40 40   10 30  
 Sales and Marketing            
 Service 340 340 37 60    
 Human Resources            
 Projects 275 200   100 100  
 Procurement 25       25  
 Maintenance Mgmt            
 Totals 1700          
Under-sizing has a significant increase in TCO, Oversizing in the other hand allocates costs earlier. The company always saves money by right sizing, easier said than done. Metalink has some interesting whitepapers on ERP sizing. Oracle's strategy of launching exadata at OOW10 will help resolve this issue.
Exadata Database Machine relieves the use of responsibility for physical configuration and deployment of database servers and associated storage, offering pretty impressive performance and scalability benefits. It merits careful consideration as your main system or data warehouse or an OLTP database consolidation platform.


Setups that need to be done to get Approvals Management Access (AME) in R12.1

on Tuesday, 01 January 2013. Posted in Blog, Oracle Security and Administration


Here are the setups in point form that need to be done to get Approvals Management Access (AME) in R12.1.3


ü  Access User Management Responsibility.


ü  User Management has to be inherited through Role, as an Indirect Responsibility


ü  For this, assign “Security Administrator” Role to yourself.


ü  This Role grants inheritance of User Management Privileges to the user


ü  Assigning this through SysAdmin will not work


ü  In User Management, grant the Roles for “Approvals Management Administration” to the user.


ü  Also, grant Functional Administrator and Functional Developer roles


ü  These will grant indirect responsibilities to the user


ü  After this, Approvals Management Administrator Responsibility can be accessed.


ü  This will still not open up transaction types for viewing.


ü  For this, create the Grant to the User by following the steps below:


ü  Functional Administrator> Security>Grants>.Create Grant


ü  Do the below to ensure specifics are granted to User for accessing User Management Pages




Once your AME setups are completed the below link is a good starter point in helping with testing. How to test AME set-ups [ID 1071051.1]


ZOO Comment

Copyright 2018 All rights reserved.