Wednesday, March 31, 2010

Oracle Apps Installation Prerequisites

Oracle Apps Installation Prerequisites


Oracle Apps Version: 11.5.10.2
Platform: Solaris
                   This is the version of the product and platform for our installation of Oracle Apps. This document is also applicable for the upgrade to 11.5.10.2 from the lower versions. All the information given in this note is obviously for the platform Solaris SPARC.

Operating System Details:
                          Version of the Solaris SPARC which we should follow is Maintenance pack of 6(5.6) or the Installation and Maintenance pack of 8(5.8), 9(5.9) and 10(5.10).



Other Required Applications:
1. Oracle Server: 9.2.0
2. Sun swap: match RAM
3. Sun tmp: 10 GB
4. Sun JDK, JRE: JDK 1.3.1_02 & 1.1.8_12 (32bit) 1.1.8_15 (64bit)
5. Sun Patches/ Packages: 32bit/64bit SUNWarc, SUNWbtool, SUNWhea, SUNWlibm,
SUNWlibms,
SUNWmfrun,
SUNWsprot,
SUNWtoo
SUNWi1of and SUNWxwfnt (for Java)
SUNWsprox (for 64bit Oracle) (Not applicable to Solaris 10)
SUNWuiu8,SUNWulcf (if Bug 4025250 occurs)
SUNWxcu4

6. Sun Kernel Settings: SEMMNI 100 ***
SEMMSL 256 ***
SHMMAX 4294967295
SHMMNI 100***
NOEXEC_USER_STACK 1
*** default value in Solaris 10 is already larger

7. Maintenance Tools:

 ar
 gcc
 g++
 ld
 ksh
 make
 X Display Server

Tuesday, March 30, 2010

Enhancements to VPD

Main enhancements to VPD in Oracle Database 10g include: column-level privacy, customization, and shared policies. These enhancements are explained in the following three paragraphs.

Column-Level Privacy
VPD provides row-level security (RLS). Oracle Database 10g enforces row-level access control only when a command accesses or references security-relevant columns. You can specify more than one relevant column in a policy. If you do not specify any relevant columns, the database applies VPD rewrites to all commands that access or reference the object. This behavior is consistent with previous releases.

You use row-level access control when you want to limit the rows returned. For example, queries on nonsensitive data (such as LAST_NAME or DEPARTMENT_ID) should not be limited because there is no harm in returning a list of all departments but queries that reference sensitive or private columns (such as national identification) should be limited by VPD.

The enforcement of relevant-column VPD occurs whenever a command references the column:

Explicitly: When the column name is included in the query
Implicitly: In a SELECT * command because all columns are returned
The ability to specify relevant columns in VPD policies lends itself to privacy. Often privacy-relevant information, or personally identifiable information (PII), is stored in columns. For example: national identifier, credit card number, address, and account number are all PII. Only queries that access the relevant columns should have VPD’s granular access control applied to them. A VPD policy need not restrict queries that do not reference relevant columns.

The column-level VPD increases performance by limiting the number of queries that the database rewrites. Rewrites occur only when the statement references relevant columns.

Customization
You use customization to base the VPD on the individual requirements of a customer’s deployment. You can customize VPD to always enforce the same predicate with a static policy or you can have VPD predicates that change dynamically with a nonstatic policy.

Shared Policies
In Oracle Database 10g, you apply a single VPD policy to multiple objects. This feature reduces the administration costs.

Overview of the Virtual Private Database

Defining a Virtual Private Database (VPD)
VPD enables the database to perform query modification based on a security policy you have defined in a package, and associated with a table or view. VPD provides fine-grained access control that is data driven, context dependent, and row based. VPD is a key enabling technology in building three-tier systems that expose mission-critical resources to customers and partners.

When a user directly or indirectly accesses a table or view associated with a VPD security policy, the server dynamically modifies the user’s SQL statement. The modification is based on a WHERE condition (also known as a predicate) returned by a function that implements the security policy. The database modifies the statement dynamically, transparently to the user, using any condition that can be expressed in, or returned by a function.

Oracle Database 10g enhances the VPD to further increase effectiveness, security, flexibility, and performance. You can use VPD to assist with privacy initiatives.

Enhancements in Oracle Database 10g are applicable to private information. For example, VPD now includes the notion of security-relevant columns. Within a VPD policy, you can reference “relevant columns” so that the database appends the VPD predicate to queries that reference these relevant columns.

In Oracle Database 10g, to provide flexibility for all types of implementations, policies can be:

Static: These policies strictly enforce the same predicate at all times.
Non-static: These policies can change dynamically.

Wednesday, March 24, 2010

How To Find the FND_PATCHSET_LEVEL While Applying India Localization Patch


How To Find the FND_PATCHSET_LEVEL While Applying India Localization Patch

Solution
For finding the FND patchset level use the below query

select patch_level from fnd_product_installations where patch_level like '%FND%' ;
The above query for example will return values like 11i.FND.C or 11i.FND.D

Based on this pass the parameter value as FND_PATCHSET_LEVEL = 'C' if the query returns 11i.FND.C,"D if it returns 11i.FND.D"

How To Find the FND_PATCHSET_LEVEL While Applying India Localization Patch


How To Find the FND_PATCHSET_LEVEL While Applying India Localization Patch

Solution
For finding the FND patchset level use the below query

select patch_level from fnd_product_installations where patch_level like '%FND%' ;
The above query for example will return values like 11i.FND.C or 11i.FND.D

Based on this pass the parameter value as FND_PATCHSET_LEVEL = 'C' if the query returns 11i.FND.C,"D if it returns 11i.FND.D"
Oracle E-Business Suite > Financial Management > Localizations > Oracle Financials for India

Command to do active duplicate for Oracle Database

1. First login to target server 2. Validate tns connectivity between Source DB and Target DB 3. Prepare and validate space availability 4. S...