Binoy Kumar

Database Replay workload capture of external clients is performed at the database server level. Therefore, Database Replay can be used to assess the impact of any system changes below the database tier level such as below:      Database upgrades, patches, parameter, schema changes, etc. Configuration changes such as conversion from a single instance to RAC etc. Storage, network, interconnect changes Operating system, hardware migrations, patches, upgrades, parameter changes         DB replay does this by capturing a workload on the production system with negligible performance overhead( My observation is 2-5% more CPU usage ) and replaying it on a test system with the exact timing, concurrency, and transaction characteristics of the original workload. This makes possible complete assessment of the impact of the change including undesired results; new contentions points or performance regressions. Extensive analysis and reporting ( AWR , ADDM report and DB replay report) is provided to

-Multi-Org Access Control feature allows you to enter, process data and generate reports from a single responsibility. -This is achieved by providing the Operating Unit field on the forms/pages and while running the concurrent processes. -To Set this feature you need to define the security profile containing operating units and set it at MO: Security Profile. -You can default the Operating Unit on forms/pages by setting the MO: Default Operating Unit profile. 1) Business Grou p (Which dealt with HRMS Module) It is the Higest level in the ORG structure. 2) Legal Entity ( Dealt with Tax entities, Govt reporting authorities) 3) Set of Books ( Dealt with 4 C's that is Chart of Account, Currencies and Calender, Accounting Convention) 4) Operating Unit (Dealt with 5 sub ledger modules by name AP/AR/GL/PO/OM 5) Inventory Organization (Dealt with INV/BOM/WIP/MS_MRP) You can assign any no. of Organization under a Operating Unit.

MO_GLOBAL Package MOAC functionality is provided through the MO_GLOBAL package (AFMOGBLB.pls).  Following are some of the more important functions and procedures in the package. Init () This is generally called by forms and reports to setup the list of orgs that can be accessed.  It calls the set_org_access procedure, which in turn calls populate_orgs.  This inserts the orgs a user is allowed to access in a global temporary table -- MO_GLOB_ORG_ACCESS_TMP.  The table is populated based on the MO: Security Profile and MO: Operating Unit profile option values. Org_security() This returns a sql predicate (where clause) that controls which records can be accessed.  Example: EXISTS (SELECT 1                     FROM mo_glob_org_access_tmp oa                     WHERE oa.organization_id = org_id) This is used in dbms_rls.add_policy to add the vpd security to synonyms. Check_access() Checks to see if an org can be accessed by a user.  If  access mode is M (Multiple), see if the

Here is a list of security enhancement features: Column-Level VPD - Virtual Private Database (VPD) is now finer grained. You are now able to enforce VPD rewrite when a query references a particular column. VPD Static and Dynamic Policies - Virtual Private Database (VPD) now lets you distinguish between static policies, which are suitable for hosting environments that always need to enforce an unchanging policy, and dynamic policies, which are suitable for time-dependent enforcement, such as time of day, where rows returned must vary at a particular time. Fine-Grained Auditing (FGA) on DML - Fine-Grained Auditing (FGA) extends the support to include UPDATE, INSERT, and DELETE statements. Virtual Private Database Virtual Private Database (VPD) was first introduced in Oracle8i. It set a new standard in database security, being built into the database server, instead of each application accessing the data. Security is no longer bypassed when a user accesses the