RAC Setup Instructions

• Pre-reqs. to make sure the cluster is setup OK. • Stage all the software on one node, typically Node1 • Prepare the Shared Disk • Install the Oracle Clusterware (using the push mechanism to install on the other nodes in the cluster) • Patch the Oracle Clusterware layer to 10.2.0.3 • Install Oracle ASM Software only Home • Patch the Oracle ASM Software Home to 10.2.0.3 • Create Node Specific Network Listeners • Create ASM Instances and initial ASM disk group • Install Oracle RAC Database Software only Home • Patch the Oracle RAC Database Software Home to 10.2.0.3 • Create RAC database

The /etc/sysconfig/network-scripts/ifcfg-ethN files

The /etc/sysconfig/network-scripts/ifcfg-ethN files File configurations for each network device you may have or want to add on your system are located in the /etc/sysconfig/network-scripts/ directory with Red Hat Linux 6.1 or 6.2 and are named ifcfg-eth0 for the first interface and ifcfg-eth1 for the second, etc. Following is a example /etc/sysconfig/network-scripts/ifcfg-eth0 file: DEVICE=eth0 IPADDR=208.164.186.1 NETMASK=255.255.255.0 NETWORK=208.164.186.0 BROADCAST=208.164.186.255 ONBOOT=yes BOOTPROTO=none USERCTL=no If you want to modify your network address manually, or add a new network on a new interface, edit this file -ifcfg-ethN, or create a new one and make the appropriate changes. DEVICE=devicename, where devicename is the name of the physical network device. IPADDR=ipaddr, where ipaddr is the IP address. NETMASK=netmask, where netmask is the netmask IP value. NETWORK=network, where network is the network IP address. BROADCAST=broadcast, where broadcast is the broadcast IP address. ONBOOT=answer, where answer is yes or no. Do the interface need to be active or inactive at boot time. BOOTPROTO=proto, where proto is one of the following : none - No boot-time protocol should be used. bootp - The bootp now pump protocol should be used. dhcp - The dhcp protocol should be used. USERCTL=answer, where answer is one of the following: yes - Non-root users are allowed to control this device. no - Only the super-user root is allowed to control this device.

RCU:6107 DB Init Param Error

While Installing Repository Creation Utility (RCU) Installation the following error occurs: RCU:6107 DB Init Param Error This can be removed simply by the following: 1. Login on your database with system user. 2. Write > show parameters processes (which will show the current value of processes). 3. If its value is less than 500 then write the following command: ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE; 4. Write > show parameters open_cursors (which will show the current value of open_cursors). 5. If its value is less than 500 then write the following command: ALTER SYSTEM SET OPEN_CURSORS=500 SCOPE=SPFILE; 6. Restart your DB or system. SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 599785472 bytes Fixed Size 1288820 bytes Variable Size 167773580 bytes Database Buffers 427819008 bytes Redo Buffers 2904064 bytes Database mounted. Database opened. SQL> show parameters processes; NAME TYPE VALUE ———————————— ———– —————————— aq_tm_processes integer 0 db_writer_processes integer 1 gcs_server_processes integer 0 job_queue_processes integer 4 log_archive_max_processes integer 2 processes integer 500 7. Start the installation now…. There will be no error….. Courtsey :http://mhabib.wordpress.com/2010/07/20/rcu6107-db-init-param-error/

Oracle Database 11g 11.2.0.1.0

www.tecmint.com/oracle-database-11g-release-2-installation-in-linux/ kamranagayev.com/2011/03/21/step-by-step-installing-oracle11g-on-linux/

DSA DSE X.500 in OID 11g

DSE DIRECTORY-SPECIFIC ENTRY DSA DIRECTORY SYSTEM AGENT See directory-specific entry (DSE) DSA-specific entries. Different DSAs may hold the same DIT name, but have different contents. That is, the contents can be specific to the DSA holding it. A DSE is an entry with contents specific to the DSA holding it. directory system agent (DSA) The X.500 term for a directory server. X.500 Overview The X.500 directory service is a global directory service. Its components cooperate to manage information about objects such as countries, organizations, people, machines, and so on in a worldwide scope. It provides the capability to look up information by name (a white-pages service) and to browse and search for information (a yellow-pages service). The information is held in a directory information base (DIB). Entries in the DIB are arranged in a tree structure called the directory information tree (DIT). Each entry is a named object and consists of a set of attributes. Each attribute has a defined attribute type and one or more values. The directory schema defines the mandatory and optional attributes for each class of object (called the object class). Each named object may have one or more object classes associated with it. The X.500 namespace is hierarchical. An entry is unambiguously identified by a distinguished name (DN). A distinguished name is the concatenation of selected attributes from each entry, called the relative distinguished name (RDN), in the tree along a path leading from the root down to the named entry. Users of the X.500 directory may (subject to access control) interrogate and modify the entries and attributes in the DIB. Protocols The X.500 standard defines a protocol (among others) for a client application to access the X.500 directory. Called the Directory Access Protocol (DAP), it is layered on top of the Open Systems Interconnection (OSI) protocol stack. Brief History of LDAP Once upon a time, in the dim and distant past (the late 70's - early 80's) the ITU (International Telecommunication Union) started work on the X.400 series of email standards. This email standard required a directory of names (and other information) that could be accessed across networks in a hierarchical fashion not dissimilar to DNS for those familiar with its architecture. This need for a global network based directory led the ITU to develop the X.500 series of standards and specifically X.519, which defined DAP (Directory Access Protocol), the protocol for accessing a networked directory service. The X.400 and X.500 series of standards came bundled with the whole OSI stack and were big, fat and consumed serious resources. Standard ITU stuff in fact. Fast forward to the early 90's and the IETF saw the need for access to global directory services (originally for many of the same email based reasons as the ITU) but without picking up all the gruesome protocol (OSI) overheads and started work on a Lightweight Directory Access Protocol (LDAP). LDAP was designed to provide almost as much functionality as the original X.519 standard but using the TCP/IP protocol - while still allowing inter-working with X.500 based directories. Indeed, X.500 (DAP) inter-working and mapping is still part of the IETF LDAP series of RFCs. A number of the more serious angst issues in the LDAP specs, most notably the directory root naming convention, can be traced back to X.500 inter-working and the need for global directories. LDAP - broadly - differs from DAP in the following respects: 1. TCP/IP is used in LDAP - DAP uses OSI as the transport/network layers 2. Some reduction in functionality - obscure, duplicate and rarely used features (an ITU speciality) in X.519 were quietly and mercifully dropped. 3. Replacement of some of the ASN.1 (X.519) with a text representation in LDAP (LDAP URLs and search filters). For this point alone the IETF incurs our undying gratitude. Regrettably much ASN.1 notation still remains.

EBS (E-Buisness Suite) R12 Integration with Oracle Access Manager 11g R2

iamonlinewiki.blogspot.com/2012/10/ebs-e-buisness-suite-r12-integration.html#!/2012/10/ebs-e-buisness-suite-r12-integration.html Note: This post is not a new invention but simplies the steps that are given in the integration document provided by Oracle. I have sucessfully integrated using below steps. Pre-Requisites:· Oracle EBS 12.0.6 or 12.1.1 or later installed and configured o 10220779 Patch needs to be apply for 12.0.6 o 8919489 Patch needs to be apply for 12.1.1. Note: For other verison no patch required · OID 11g R1 installed and configured · OAM 11g R1 or OAM 11g R2 installed and configured · OHS & Webgate (11g) installed and configured The High Level Steps & components involved in this Intigration 1. EBS R12: •Depends on the verison of the EBS it requires a patch before the integration. Refer to above pre-requisites section for the required patches. • FND patch (as listed below) needs to be applied •Site Profiles needs to be modified as explained in below sections •Register the EBS instance & Home with OID 2. EBS AccessGate: •The integration uses EBS AccessGate. So EBS AccessGate is required to be installed in either its own domain or existing domain (not IAM doamin) as a managed server. AccessGate will be deployed in this managed or admin server 3. OID 11g R1: •EBS R12 SSO using OAM 11g has a mandatory requirement of OID. The EBS instance & Home will be registered with OID. Also OID is the identity store for user authentication. •Configure OID to return operational attributes for lookup requests 4. OAM 11g R2/R1: •Requires Resources, Policies (AuthN & AuthZ) to be created in a Policy Domain. 5. OHS & Webgate: •Update the OHS proxy configuration so the requests proxy to protected resources from OHS Detailed Steps for the Integration: 1.Make sure the listed components above are installed before the integration 2.Configure OID to return the operational attribtues for lookup requests •Make LDIF file with below contents dn: cn=dsaconfig, cn=configsets,cn=oracle internet directory changetype: modify add: orclallattrstodn orclallattrstodn: cn=orcladmin where orclallattrstodn is the Bind DN which is used to connect to OID •Run ldapmodify command to add the above entry. Also the entry can be modified using ODSM console 3. Install weblogic instance or domain for EBS AccessGate 4. Download the EBS AccessGate (Patch 12796012) from oracle website • Create a folder for EBS AccessGate •Unzip the downloaded patch •Create another directory "plan" in patch directory location •copy the fndext.jar file from the downloaded location to EBS AccessGate Weblogic domain to the 'lib' location. ($MW_HOME/user_projects/domains//lib/ •Restart the EBS AccessGate domain & managed servers 5. Create a directory "public" in OHS Server at OHS_HOME/instances//config/OHS/ohs1/htdocs/ 6. Copy the samplecleanup.html file from the above EBS AccessGate Patch location to OHS Server at OHS_HOME/instances//config/OHS/ohs1/htdocs/public location 7. Rename the file as "oacleanup.html". Make sure there is no another file with this name. This is Centralized log-out script which cleansup the cookies and log-out the user. 8. Get DBC file from EBS server. It is required for creating the datasource connection from EBS AccessGate to EBS Database server. •Login to EBS DB Server. •Run the environment variables script (Ex: . VIS_.env) •java oracle.apps.fnd.security.AdminDesktop / CREATE NODE_NAME= IP_ADDRESS= DBC= •Copy the generated DBC file back to EBS AccessGate patch directory 9. Deploy the AccessGate Application and create the datasource connection to EBS DB server •cd $MW_HOME/wlserver_10.3/server/bin/ •. setWLSEnv.sh •Set DOMAIN_HOME variable (ex: export DOMAIN_HOME=$MW_HOME/user_projects/domains/) •Go to EBS AccessGate Patch directory and look for the script "txkEBSAuth.xml" •run the command as shown below •ant -f txkEBSAuth.xml •Prmots for Weblogic userid, pw, EBS application scheama, deployment plan file location, DBC file location etc... •The above command will deploy the AccessGate application into EBS AccessGate server and create datasource connections Note: The above command works for only single instance Database. If using Oracle RAC the datasource connections needs to be created manually. • Restart EBS AccessGate admin and managed servers 10. Assuming webgate is already installed and registered with OAM 11g server, create the required application domain, resources, policies etc... in OAM console •Create an application Domain like "EBS App Domain" in OAM Console •Create EBS Id (data store) store under system configuration tab. This is OID user data store •Create an EBS Authentication Module (LDAP) and assign above data store as "identity store" •Create EBS Authentication Scheme with below parameters •Authentication Level: 1 •Challenge Method: FORM •Challenge Redirect URL: http://:14100/oam/server •Authentication Module: EBS Authentication Module •Challenge URL: http://:///OAMLogin.jsp •Context Type: external •Create Protected Resource & Public Resource containers under Authentciation Policies •Create Protected Resource & Public Resource containers under Authorization Policies •Create the below resources for the above application domain •Protected Resources Policies •/ebsauth_app (This is the EBS application context) •/ebsauth_appsp1/…/* •Public Resource Policies •/ebsauth_appsp1/OAMLogin.jsp •ebsauth_appsp1/ssologout.do •/ebsauth_appsp1/ssologout_callback •/ebsauth_appsp1/style •Un-Protected (Excluded) Resource Policies •/exclude/index.html•/public/oacleanup.html •Open the Protected Resource Policies under EBS Application Domain Authentication Policies •Assign "EBS Authentication Scheme" as authentication •Enter "http://:///OAMLogin.jsp in failure URL •In response tab enter below details •USER_NAME Header $user.userid •USER_ORCLGUID Header $user.attr.orclguid •Open Protected Resource Policies under EBS Application Domain Authorization Policies •Enter "http://:///OAMLogin.jsp in failure URL •Check the "Use Implied Constraints" checkbox •In response tab enter below details •USER_NAME Header $user.userid •USER_ORCLGUID Header $user.attr.orclguid 11. Configure redirection configuration in OHS server •Login to OHS server •Go to /instances/instance_name/config/OHS/ohs1/ •Update the mod_wl_ohs.conf file with below contents • SetHandler weblogic-handler WebLogicHost WebLogicPort •Restart the OHS server 12. Apply the FND patch on EBS Server •12408040 for 12.0.6 version •12408233 for 12.1.1 version •12387976 for 12.1.2 & 12.1.3 13. Restart EBS Application 14. Configure EBS Site Policies as listed below •Application Authenticate Agent = http://:/// •AutoLink SSO User = True •OID Syncronization = True •Application SSO Type = SSWA w/SSO 15. Restart EBS Application 16. Configure the centralzied log-out page •open "oacleanup.html" file in OHS server •update the below lines • •In function doLoad() section add below lines logoutHandler.addCallback('/ebsauth_fin02/ssologout_callback'); logoutHandler.addCallback('http://webgatehost2.example.com:7780/ebsauth_test/ssologout_callback'); logoutHandler.addCookie('ObSSOCookie','domain=.); •Restart the OHS Server 17. Test the integration by access the EBS Application URL (ex: http://ebs server:8000/OA_HTML/AppsLogin?>. It prompts for EBS AccessGate Login Page. Enter user credentials and verify if you are able to access EBS Application

Mandatory software required for Oracle EBS 12.2.0 installation

Environment Operating System - Oracle Linux x86-64 Installation Path - R12.2.0 > 12.2.2 > 12.2.4 Software Requirement for R12.2.0 installation Following sotware must be downloaded from edelivery.oracle.com for a successful installation of Oracle E Business Suite 12.2.0 installation: Oracle E-Business Suite Release 12.2.0 Rapid Install StartHere (Part 1 of 3) V35215-01 Part 1 of 3 1.3G Oracle E-Business Suite Release 12.2.0 Rapid Install StartHere (Part 2 of 3) V35215-01 Part 2 of 3 81M Oracle E-Business Suite Release 12.2.0 Rapid Install StartHere (Part 3 of 3) V35215-01 Part 3 of 3 97M Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Oracle Database 11.2.0.3.0 - Disk 1 (Part 1 of 2) V35230-01 Part 1 of 2 1.3G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Oracle Database 11.2.0.3.0 - Disk 1 (Part 2 of 2) V35230-01 Part 2 of 2 1.1G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Oracle Database 11.2.0.3.0 - Disk 2 (Part 1 of 5) V35231-01 Part 1 of 5 933M Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Oracle Database 11.2.0.3.0 - Disk 2 (Part 2 of 5) V35231-01 Part 2 of 5 628M Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Oracle Database 11.2.0.3.0 - Disk 2 (Part 3 of 5) V35231-01 Part 3 of 5 587M Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Oracle Database 11.2.0.3.0 - Disk 2 (Part 4 of 5) V35231-01 Part 4 of 5 457M Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Oracle Database 11.2.0.3.0 - Disk 2 (Part 5 of 5) V35231-01 Part 5 of 5 108M Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install AS10.1.2 V35802-01 711M Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install APPL_TOP - Disk 1 (Part 1 of 3) V35803-01 Part 1 of 3 1.2G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install APPL_TOP - Disk 1 (Part 2 of 3) V35803-01 Part 2 of 3 1.0G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install APPL_TOP - Disk 1 (Part 3 of 3) V35803-01 Part 3 of 3 1.4G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install APPL_TOP - Disk 2 (Part 1 of 2) V35804-01 Part 1 of 2 1.2G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install APPL_TOP - Disk 2 (Part 2 of 2) V35804-01 Part 2 of 2 1.6G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases PROD - Disk 1 (Part 1 of 2) V35805-01 Part 1 of 2 1.4G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases PROD - Disk 1 (Part 2 of 2) V35805-01 Part 2 of 2 1.3G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases PROD - Disk 2 (Part 1 of 3) V35806-01 Part 1 of 3 1.4G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases PROD - Disk 2 (Part 2 of 3) V35806-01 Part 2 of 3 1.1G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases PROD - Disk 2 (Part 3 of 3) V35806-01 Part 3 of 3 1.0G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases VISION - Disk 1 V35807-01 3.2G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases VISION - Disk 2 V35808-01 2.9G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases VISION - Disk 3 V35809-01 2.9G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases VISION - Disk 4 V35810-01 2.8G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases VISION - Disk 5 V35811-01 2.6G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Databases VISION - Disk 6 V35812-01 2.3G Oracle E-Business Suite Release 12.2.0 for Linux x86-64 Rapid Install Technology one-off Patches V35813-01 730M Oracle Fusion Middleware Web Tier Utilities 11g Patch Set 5 (11.1.1.6.0) for Linux x86-64 V29764-01 1.6G Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence V29856-01 1.0G