AppsFusion

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:30:00 -0700

Step by Step upgrade of OBIEE 11.1.1.5 to 11.1.1.7 and 12c including upgrade to ODI 11gR1 with BI Apps 11.1.1.9.2.

Upcoming Article - Work in Progress.

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:26:00 -0700

Step by Step Upgrade of SOA/OSB/BAM/OHS 11.1.1.5 to 11.1.1.7 and 12c.

Upcoming Article - Work in Progress.

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:25:00 -0700

Step by Step Upgrade from EBS 11.5.10CU to EBS R12.2.x and from EBS R12.1.3 to EBS R12.2.

Upcoming Article - Work in Progress.

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:24:00 -0700

Step by Step Upgrade from BI Publisher 10g to 11g and its integration with MS-AD/OVD using Fusion Security.

Upcoming Article - Work in Progress.

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:17:00 -0700

Step by Step Installation/Upgrade of Web Center Portal and integration with EBS /OAM/OID/OVD/OHS(WebGate)/Access Gate/BI Publisher 11g.

Coming Soon. Work in Progress.

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:17:00 -0700

Step by Step Installation/Upgrade of Web Center Portal and integration with EBS /OAM/OID/OVD/OHS(WebGate)/Access Gate/BI Publisher 11g.

Coming Soon. Work in Progress.

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:15:00 -0700

Step by Step SSL and TLS Implementation on EBS R12.1.3 and R12.2.

Coming soon..

noreply@blogger.com (Ramnik Gupta) — Wed, 21 Sep 2016 19:12:00 -0700

Step by Step information on Goverance, Risk and Compliance - GRC 8.6.4.5000 and GRCI (Intelligence) 8.6.4.5000 and its upgrade to 8.6.4.6000/7000/8000 - Non SOA implementation (Part 2) - Coming soon.

Recently implemented latest GRC Version with PCG/PEA/AACG/GRCI integration with EBS R12.1.3.

Step by Step information on Goverance, Risk and Compliance - GRC 8.6.4.5000 and GRCI (Intelligence) 8.6.4.5000 and its upgrade to 8.6.4.6000/7000/8000 - Non SOA implementation (Part 1)

noreply@blogger.com (Ramnik Gupta) — Sat, 3 Aug 2013 18:55:00 -0700

The most important aspect for any Oracle professional to understand client needs and their environments also the challenges you may face during implementation of any Oracle products. You need to understand the dynamics of client teams , important client folks who can influence the project like Project Manager, Client DBA's, O/S and Network Administrator. Also it is very important to understnad the Change Management Process which help you to implement any product within the cost , on time and schedule.

Consider the following important points which you should always remember before you start any implementation. I may add some more points later too.

1) Project Contacts and Project Manager who is running the show.
2) Understand duration of the implementation
3) Request Project Manager for any unforseen issues may cause during product implementation and always ask for buffer time as you may face issue at their O/S Level, Network , Software Download/Upload issues, Staging issues and it could be anything which you can not expect. So the best is do a dry run and prepare you own project plan and include all requirement and analysis. When Project Manager ask you to start the project you should have all your requirement go in to your change request. This will help you avoid delays due to various reason which depends on project to project.
4) Understand Security and Compliance issues with in the project like which ports to be open and which firewall to be open and from where to where. Also do you need keep any data retention for compliance reason.
5) Check Oracle Certification and always go through Documentatoin on Installation, Upgrade ,Release Notes and mandatory MOS notes. If you get the time please re-read again and again during implementation. Before actual implementation start always download the latest updated documentation this will help you avoid any issues during your implementation. The same is applicable for Oracle MOS notes too.
6) You may use MS-Project or MS-Excel or MS-Word or a your note books. It doesn't matter what you are comfortable with but it is very important you keep you anaylysis ready for your implementation include client folks comments and their DBA/Sys administrator comments are very important to understand in-house issues.
7) Always make sure what version of software requesting to you and request them to download and upload to stage area or you have given access then do this step as atmost priority , the same is applicable to all required patches and/or any other client tools you requried during your implementation or post-implemenation.

Hope the above points are useful in your day-to-day professional life.

Today's Step by Step Oracle Product Series article is on Installation of Goverance Risk and Complaince (GRC /GRCI 8.6.4.500) and its upgrade.

I am going to cover the steps in this article and will build the Virtual environment at home and later place the screen shots for Oracle user community for their learning.

URL for GRC Suite 8.6.4.5000 Documentation: http://docs.oracle.com/cd/E39187_01/index.htm

URL for Oracle GRC Suite Software Download : edelivery.oracle.com , Select Linux 64-bit.

URL for Oracle Certification Matrix : GRC Suite Certification Matrix (Doc ID 741001.1)
Straight from Oracle Documentation :

Oracle Governance, Risk and Compliance (GRC) serves as a platform for two components — Enterprise Governance, Risk and Compliance Manager (EGRCM) and Enterprise Governance, Risk and Compliance Controls (EGRCC).

EGRCM forms a documentary record of a company’s strategy for addressing risk and complying with regulatory requirements. It enables users to define risks to the company’s business, controls to mitigate those risks, and other objects, such as business processes to which risks and controls apply.

EGRCC comprises two elements, Application Access Controls Governor (AACG) and Enterprise Transaction Controls Governor (ETCG). These enable users to create models and controls and to run them within business applications to uncover and resolve segregation of duties violations and transaction risk.

These components run as modules in the GRC platform. EGRCC runs as a Continuous Controls Monitoring (CCM) module. EGRCM provides a Financial Governance module by default, and users may create other EGRCM modules to address other areas of the company’s business.

A third component, Oracle Fusion GRC Intelligence (GRCI), provides dashboards and reports that present summary and detailed views of data generated in GRC. GRCI may be embedded in GRC, or run as a standalone application.

GRC 8.6.4.5000 High Level Installation Steps. I will includes screenshots when I get the chance.

(1)
Create a stage area /OracleSoftwareStage to stage the software. I would like to recommend here to stage all GRC Suite Software. I would like to recommend at least 100 GB to stage and unzip the files also to be used for staged backup during implementation.

Check the JDK 1.7.0_13+ is also installed.

Required Software to be staged for GRC 8.6.4.5000 Implementation are as under:
(1) Oracle Database 11.2.0.3 & Examples software
(2) Weblogic 10.3.6
(3) ADR 11.1.1.6
(4) JDK 1.7.0_13+
(5) GRC 8.6.4.5 (included rpd and Webcat files for GRCI - V36363-01.zip file).

(2)

For O/S Pre Requisites, please refer documents listed as under:

Verify Oracle RPM's, Kernel parameters (/etc/security/limits.conf),VNC,required ports to be open, including Oracle userid (oracle:dba user) and application grc user id (grcapp:dba user) for Database and GRC Installation. Sudo to root user is required for DB and GRC Application Tier installation.

a) Defining a "default RPMs" installation of the RHEL OS [ID 376183.1]
b) Master Note of Linux OS Requirements for Database Server [ID 851598.1]
c) Requirements for Installing Oracle 11gR2 RDBMS on RHEL6 or OL6 64-bit (x86-64) [ID 1441282.1]) (Must use)
d) http://docs.oracle.com/cd/E11882_01/install.112/e24321/pre_install.htm#BABCFJFG
e) Governance Risk and Compliance (GRC) Product Information [ID 1084596.1]

(3)

Verify File systems are in place and validated before the installation. Also needs to validate if the space is adequately allocated. Validate the appropriate permission for oracle user and group as dba on File system.

/u01 - For Database Binaries and Middleware Binaries.
/u02 - For Data Files , ETL & Report directories.
/opt/oracle - For Oracle Inventory location and permission should be 775 must be set for oracle and grcapp users can write to this location. Make sure both users are created on step 1 must be part of same group "dba".
archive log mount point - For Oracle Database in archive mode.

(4)

Install Oracle Database 11.2.0.3 as well as Install Oracle Examples.

(5)

Create GRC (grc_superuser and GRCI schema DA (da_superuser - will be used for GRCI implementation later).

Creation of Schema's for GRC and GRCI

In the Oracle database, create a GRC schema for use by GRC. If you intend also to install GRCI, create a second schema, known as the Data Analytics (DA) schema.
The following is a sample script that serves for the creation of either schema. You are assumed to have created tablespaces; each schema requires its own. The values you choose for tablespace name, user (schema) name, and password would be dis-tinct for each schema, and are represented here by TablespaceName, UserName, and UserPassword, respectively. Each password must contain at least six characters.

create user grc_superuser identified by mypass default tablespace GRC_TS_DATA quota unlimited on GRC_TS_DATA quota 0k on system;
grant connect, resource to grc_superuser;
grant create any view to grc_superuser;
grant create any table to grc_superuser;
grant drop any table to grc_superuser;
grant create synonym to grc_superuser;

Run the following commands as the system user:

ALTER SYSTEM SET open_cursors=5000 scope=spfile;
ALTER SYSTEM SET processes=3000 scope=spfile;
ALTER SYSTEM SET deferred_segment_creation=FALSE scope=spfile;

After running these commands, bounce the database.

GRC may display information in any of twelve languages. To use the multilingual capability, set up the database that hosts the GRC schema for UTF-8 encoding. To do so, execute this command, for which the return value should be AL32UTF8:

SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET' ;

Once installation is complete, users will be able to use a set of Schema Import/Export fields (available in the Properties tab of a Manage Application Configurations page) to download the GRC schema, or to upload a copy of it.

To set up this feature, create a DATA_PUMP_DIR directory, which provides temporary storage for schema-file copies.

In the following commands, use a SQL editor such as SQL*Plus; replace with the name of the admin user for the GRC application server; replace with the path to a directory that will serve as your DATA_PUMP_DIR directory.

a. Create a directory object, and grant READ and WRITE access to it.
CREATE DIRECTORY DATA_PUMP_DIR AS /u02/GRC_DATA_DUMP_DIR;
GRANT READ, WRITE ON DIRECTORY DATA_PUMP_DIR TO grc_superuser;

b. Ensure that grc_superuser has EXP_FULL_DATABASE and IMP_FULL_DATABASE roles. For a list of roles within your security domain, enter the following:

SELECT * FROM SESSION_ROLES;

c. If the grc_superuser does not have these roles, execute the following commands:

GRANT EXP_FULL_DATABASE, IMP_FULL_DATABASE TO grc_superuser;
GRANT CREATE SESSION TO grc_superuser;
GRANT CREATE TABLE TO grc_superuser;
GRANT UNLIMITED TABLESPACE TO grc_superuser;

d. Grant an additional permission, required for the import operation:

GRANT EXECUTE ON UTL_FILE TO grc_superuser;

Note:
Before a schema file can be imported, an empty schema must be created for it, and a tablespace must be created for the schema. The script shown above may be used to create the schema. The following is an example of a script that creates a tablespace if the original GRC schema and its copy will reside in the same database. UserName is the name of the copied schema, and UserNameTS is the name of the tablespace.
CREATE USER "grc_superuser_cp" IDENTIFIED BY "mypasscp" DEFAULT TABLESPACE GRC_TS_DATA QUOTA UNLIMITED ON GRC_TS_DATA;

Note: Please execute all the steps above for creation of grc_superuser_cp ,da_superuser and da_superuser_cp (Copy Schema). Also create seperate Index tablespace for indexes to be stored and you can use the name as "GRC_TS_INDEX". Also create two additonal tablespace for DA (GRCI Schema's to store data and index) for example DA_TS_DATA and DA_TS_INDEX.

(6)

Make sure /u02/GRC8645_ETL and /u02/GRC8645_Report directories.

(7)

Complete the Install of Weblogic 10.3.6 and ADR 11.1.1.6. (Without SOA)

(8)

Weblogic Domain Creation Steps.

== Detailed Steps (8) ==

For any installation, one template is selected automatically: “Base WebLogic Server Domain — 10.3.6.0.” Also select “Oracle Enterprise Manager — 11.1.1.0.” When you do, a third template, “Oracle JRF — 11.1.1.0,” is selected with it.
Only if you are installing GRC with SOA, select three more templates: “Oracle SOA Suite — 11.1.1.0,” “Oracle WSM Policy Manager — 11.1.1.0,” and “Oracle JRF Webservices Asynchronous Services — 11.1.1.0.”
2. Create a name for your WebLogic domain. Use any name you wish. (Throughout this document, the value represents the name you configure here.) In two other fields — Domain Location and Application Location — accept default values.
3. At a Configure Administrator Username Password prompt, create a WebLogic Server username and password.
4. At a Configure Server Start Mode and JDK prompt, select “Production Mode.” In the JDK Selection area, ensure that the correct JDK is selected. (This is the JDK instance you confirmed to be in the path to install and run WebLogic under “Initial WebLogic Installation” on page 2-3.) If necessary, use the “Other JDK” option to browse.
5. For GRC with SOA only, respond to a Configure JDBC Component Schema prompt. Enter details you’ve already established as you used RCU to create repositories (see step 2b of “Initial WebLogic Installation” on page 2-4). When you complete this step, you should see the value “Test Successful” at a Test Component Schema prompt.
6. For any installation, select “Administration Server” at a Select Optional Con-figuration prompt. Also select “Managed Servers, Clusters and Machines” if you are installing GRC with SOA, but not if you are installing GRC to run with a pre-existing SOA or without SOA.
7. At a Configure the Administration Server prompt, enter the IP address of the machine running the WebLogic Server. Also select an unused port for it.
8. If you are installing GRC to run FAACG, or GRC with SOA , a Configure Man-aged Servers prompt appears:
• For GRC with FAACG, click the Add button. In the row that appears, enter a name for the GRC server and the IP address of the machine running the WebLogic Server. Then continue at step 9.
• For GRC with SOA, confirm that the Configure Managed Servers prompt displays a row for a SOA Server. This row appears as a result of GRC-specific configuration you’ve already completed. Note the IP address and port, which you’ll need to enter later in a GRC Worklist page. Continue at step 9.
If you are installing GRC without SOA, or to run with a pre-existing SOA, you need not create a managed server. The Configure Managed Servers page and several other Configuration Wizard pages do not appear. Skip ahead to step 12.
9. Skip the Configure Clusters page.
10. In a Configure Machines page, select the Unix Machine tab. Click Add. Assign any name, and accept defaults for all other fields.
11. In the Assign Servers to Machines page, select the servers listed in the left box. Move them to machine you created in step 10, which is listed in the right box.
12. In the Summary page, select Create.

Preparing Additional Files

Complete these additional steps when the config.sh script finishes running:

1. Copy the following files from /oracle_common/modules/oracle.adf.model_11.1.1, to /user_projects/domains//lib:
• adfm.jar
• adfdt_common.jar
• adfmweb.jar
2. Copy the following files from /lib to /user_projects/domains//lib:
• groovy-all-1.6.3.jar
• xdoparser-10.1.3.4.jar
If you are installing GRC to run FAACG, invoke the WebLogic scripting tool — wlst.sh — from /oracle_common/common/bin. Use it to apply the JRF template to the GRC managed server you created in step 8 of “Creating a WebLogic Domain” ( in the following example):
applyJRF('','/user_projects/domains/')
If you do not intend to run FAACG, skip this step.
4. Create a directory called grc864 (for example, /grc864). This directory should be entirely distinct from the directory you created as you downloaded GRC files.
5. Navigate to /dist, and locate the file grc.ear. Copy it to the grc864 directory, and extract its contents there.
In addition, as you complete GRC installation procedures, you will use scripts named startWeblogic.sh and stopWeblogic.sh to start and stop the WebLogic Administration Server. First, edit the stopWeblogic.sh file as follows:
1. Open /wlserver_10.3/common/bin/stopWeblogic.sh in a text editor.

==Detailed Steps End Here==

(9)

Perform Configuration Steps in a Weblogic Server Administration Console, and modify memory and other settings to confirm to GRC requirements.

== Detailed Steps (9) ==

For any installation, use the WebLogic Server Administration Console to complete additional configuration steps:
1. Make sure you are logged in to the WebLogic Console (see step 2 of “Creating the SOA Admin User and Enabling Embedded LDAP,” page 2-13).
2. In the Change Center pane, click Lock & Edit.
3. In the Domain Structure pane, click on Deployments.
4. In the Summary of Deployments pane, select the Control tab.
5. In the Summary of Deployments pane, click on the Install button.
6. In the Path field of the Install Application Assistant pane, enter the full path to the grc864 directory you created earlier (see step 3 of “Preparing Additional Files” on page 2-5). Select “grc864 (open directory)” under Current Location.
7. In the Install Application Assistant pane, press next.
8. In the Install Application Assistant pane, choose Install this deployment as an application in the “Choose targeting style” section.
9. In the Install Application Assistant pane, press Next. Then:
• If you are installing GRC to run FAACG, select the GRC managed server you created in step 8 of “Creating a WebLogic Domain” (page 2-5).
• If you are installing GRC with SOA, select the Administration Server.
• If you are installing GRC to run without SOA or with a pre-existing SOA, you are not presented with an opportunity to select a server here. Skip to step 10.
10. In the Install Application Assistant pane, choose I will make this deployment accessible from the following location in the “Source accessibility” section. Accept all other defaults.
11. In the Install Application Assistant pane, press Next.
12. In the Install Application Assistant pane, choose Yes, take me to the deploy-ment’s configuration screen in the “Additional configuration” section.
13. In the Install Application Assistant pane, press Finish.
14. In the Install Application Assistant pane, press Save, then Activate Changes. On the Deployments screen, the state of the grc864 application will be Prepared.
15. Select the grc864 application. Click Start, select Servicing all requests, click Yes on Start Application Assistant, and wait until the application status changes to Active.

Modifying Settings
Next, modify settings in a file called setDomainEnv.sh, which is located in the /user_projects/domains//bin directory.
1. Stop the SOA Server (if you are installing EGRCM with SOA) and the Administration Server.
2. Navigate to setDomainEnv.sh and open it in a text editor.
3. In the file, locate the following lines:
# IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
if [ "${USER_MEM_ARGS}" != "" ] ; then
4. Insert the following lines between those two lines:
case "${SERVER_NAME}" in "AdminServer") USER_MEM_ARGS="-Xms4g –Xmx16g" ;; "bi_server1") USER_MEM_ARGS="-Xms2g –Xmx8g" ;; "soa_server1") USER_MEM_ARGS="-Xms2g –Xmx4g" ;; "sample_server1") USER_MEM_ARGS="-Xms4g -Xmx16g" ;; "sample_server2") USER_MEM_ARGS="-Xms4g -Xmx16g" ;; *) echo "Unknown Server Detected!!. Memory set as Xms1g Xmx2g."; USER_MEM_ARGS="-Xms1g -Xmx2g" ;; esac
USER_MEM_ARGS="${USER_MEM_ARGS} -XX:PermSize=256m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=128M -Djava.awt.headless=true -Djbo.ampool.maxpoolsize=600000"
Replace “placeholder” names (AdminServer, bi_server1, soa_server1, sample_server1, and sample_server2) with the names of your Administration Server and any managed servers included in your installation.
You may use a maximum memory setting (-Xmx) larger than 16G if your server has enough memory to support the larger value.
5. Locate the following section of the file and ensure that “-da” appears after each of two “${enableHotSwapFlag}” elements:
if [ "${debugFlag}" = "true" ] ; then
JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
export JAVA_DEBUG
JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -da -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole..."
export JAVA_OPTIONS
else
JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -da"
export JAVA_OPTIONS
fi
6. Locate the EXTRA_JAVA_PROPERTIES section of the file. In it, remove the following string:
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
7. Save and close the file. Start the Administration Server and (if appropriate) SOA Server.

==Detailed Steps End Here==

(10)

Perform Configuration Steps in GRC Manage Application Page.

== Detailed Steps (10) ==

GRC Configuration

Regardless of whether you use WebLogic or Tomcat, open a Manage Application Configurations page to perform GRC-specific configuration:

1. Access GRC at
http://host:port/grc
In this URL, replace host with the FQDN of your GRC server. Select one of the following values for port:
• If you use WebLogic and are installing GRC to run FAACG, enter the port number you chose for the GRC managed server as you created a WebLogic domain. (See step 8 of “Creating a WebLogic Domain” on page 2-5.)
• If you use WebLogic and are performing any other installation, enter the port number you chose for the Administration Server as you created a WebLogic domain. (See step 7 of “Creating a WebLogic Domain” on page 2-5.)
• If you use Tomcat, replace port with 8080 (if you accepted the default value when you installed Tomcat) or your configured value (if you changed the default during Tomcat installation).
2. A ConfigUI page appears. In the Installation Configuration section, type or select appropriate property values:
• User Name: Supply the user name for the GRC database.
• Password: Supply the password for the GRC database.
• Confirm Password: Re-enter the password for the GRC database.
• Port Number: Supply the port number at which the GRC database server communicates with other applications.
• Service Identifier: Supply the service identifier (SID) for the GRC database server, as configured in the tnsnames.ora file. Or, if your GRC database sup-ports RAC, enter the RAC service name configured for your RAC database.
• Server Name: Supply the FQDN of the database server. Or, if your GRC database supports RAC, enter RAC@, where is the IP address/host name of the SCAN address configured for your RAC database.
• Maximum DB Connections: Default is 50. You can edit this value.
• Report Repository Path: Supply the full path to the Report Repository directory discussed in “Creating GRC Repositories” on page 2-3.
Log Threshold: Select a value that sets the level of detail in log-file entries. From least to greatest detail, valid entries are error, warn, info, and debug.
• Transaction ETL Path: Enter the full path to the directory you created to hold ETL data used by Enterprise Transaction Controls Governor (see “Creating GRC Repositories” on page 2-3).
• App Server Library Path: Enter the full path to the library subdirectory of your web application server (for use in the upload of custom connectors for AACG). If you are installing GRC to run FAACG, set this value to /grc/WEB-INF/lib.
3. In the Language Preferences section of the ConfigUI page, select the check boxes for up to twelve languages in which you want GRC to be able to display information to its users.
4. In the Performance Configuration section of the ConfigUI page, select or clear check boxes:
• Optimize Distributed Operation: Select the check box to increase the speed at which GRC performs distributed operations such as data synchronization.
• Optimize Appliance-Based Operation: Select the check box to optimize performance if the GRC application and GRC schema reside on the same machine. Do not select this check box if the GRC application and schema do not reside on the same machine. When you select this check box, an ORACLE_HOME Path field appears. In it, enter the full, absolute path to your Oracle Home — the directory in which you have installed the Oracle data-base that houses the GRC schema.
• Enable Era-Based ETL Optimization: “Data synchronization” enables both ETCG and AACG to recognize data changes in the business applications subject to their models and controls. For ETCG only, select this check box to cause synchronization to operate only on data entered in business applica-tions after a specified date.
When you select this check box, an Analysis Start Date field appears. In it, enter a date from which you want synchronization runs to recognize data changes. When you click in the field, a pop-up calendar appears. Click left- or right-pointing arrows to select earlier or later months (and years), and then click on a date in a selected month.
• Externalize Report Engine: Select the check box to enable the reporting engine to run in its own java process, so that the generation of large reports does not affect the performance of other functionality. However, select the check box only if you have installed GRC on hardware identified as “certi-fied” in the Oracle Enterprise Governance, Risk and Compliance Certifica-tions Document; clear the check box if you use hardware identified as “sup-ported.”
• Enable Parallel Processing: Select this check box to enable multiple models and controls to be processed simultaneously. However, this feature requires, at minimum, 16 GB of RAM; 24 GB is preferred.
When you select the Enable Parallel Processing check box, two fields appear. In a Number of Cores Available for Processing field, enter the number of processor cores you wish to devote to parallel processing; one core is devoted
to each model or control selected for analysis, until as many cores as you select are in use. In a Maximum Megabytes of Physical RAM Available field, specify an amount of memory for use in parallel processing. As a rule of thumb, enter total RAM minus 8 GB; you may need to adjust this value if other processes run slowly.
• Enforce Allocated Analysis Time Per Filter: Select this check box, and enter a number in the Minutes field, to limit the time that transaction models and controls can run.
A model or control consists of filters, each of which defines some aspect of a risk and selects transactions that meet its definition. When the Allocated Analysis Time feature is enabled, each filter runs no longer than the number of minutes you specify. If time expires, the filter passes records it has selected to the next filter for analysis, but ignores records it has not yet examined. So a filter may not capture every record that meets its definition, and the model or control results are labeled “partial” in GRC job-management pages.
Once enabled here, this feature may be disabled for individual models (and for the controls developed from those models). This feature applies only to transaction models and controls, not to access models and controls, and not to EGRCM objects.
5. In the ConfigUI page, click on Actions → Save. GRC tests the values you’ve entered and, if they are valid, saves them. (If any are invalid, an error message instructs you to re-enter them.)
6. Exit the ConfigUI page.

==Detailed Steps End Here==

(11)

Run Weblogic to Complete Installation.

== Detailed Steps (11) ==

With components in place and properly configured, complete the installation, in effect by running your web application server.
1. Shut down your server — the Administration Server if you’re using WebLogic, or the Tomcat application server if you’re using Tomcat. Then restart the server.
2. In a web browser, enter the GRC URL (see step 1 of “GRC Configuration” on page 2-18).
3. Wait for a pop-up message to report, “Database upgrade and initialization process complete.” Click on its OK button.
4. You are redirected to a GRC logon page. Log on to the application. For a fresh installation, use the default logon values admin for user ID and admin for password. GRC requires you to change the password the first time you log on. If you are upgrading, you can use the password established for the previous version.
If you are installing GRC without SOA and have not set up an external OID LDAP repository to manage users, basic GRC installation is complete. (You may, however, choose to set up SSL, embed GRCI, or complete other procedures described later in this chapter and in following chapters.)

If you have installed GRC with SOA (or to run with a pre-existing SOA), or if you have set up an OID LDAP repository, complete some additional steps:
1. If you use SOA, ensure that the SOA Server is up and running. (If you have installed GRC with SOA, the SOA Server is the managed server discussed in step 8 of “Creating a WebLogic Domain,” page 2-5. If you have installed GRC to run with a pre-existing SOA instance, this is the SOA server created for that instance.)
2. In GRC, select Navigator → Setup and Administration → Setup → Manage Application Configurations.
3. If you need to configure SOA, select the Worklist tab and enter these values:
• Worklist Server User Name: Keep the default value, soaadmin.
• Worklist Server Password. Enter the password you created for the soaadmin user (see step 3 of “Creating the SOA Admin User and Enabling Embedded LDAP” on page 2-13).
• Worklist Server Confirm Password: Re-enter the Worklist Server Password.
• Worklist Server URL: http://host:port, in which host is the IP address of your SOA server, and port is its port number.
• Worklist Server Protocol: Select the communications protocol —SOAP or RMI — used by the GRC application to send and receive SOA requests.
4. If you need to configure external OID LDAP, select the User Integration tab and enter the following values:
• Enable Single Sign On: Select the check box to make use of Single Sign On, which establishes a single set of log-on credentials for each user in varying applications. (Or, clear the check box if you do not wish to use Single Sign On.)
• Enable Integration: Select the check box to permit integration with LDAP to occur.
• User Name: Supply the user name (common name) to log in to the LDAP server. This user should have admin privileges. (This is the value specified for “Principal” in step 7 of “Configuring External OID LDAP,” page 2-6.)
• Password: Enter the password for the user identified in the User Name field (established in step 7 of “Configuring External OID LDAP”).
• Confirm Password: Re-enter the password for the user identified in the User Name field.
• Port Number: Enter the port number at which the LDAP server communi-cates with other applications (established in step 7 of “Configuring External OID LDAP”).
• Server Name: Enter the host name of the LDAP server. (This is the “Host” value from step 7 of “Configuring External OID LDAP.”)
• Bind DN Suffix: Enter the “User Base DN” from step 7 of “Configuring External OID LDAP.”
• Enable SSL Authentication: Select the box to allow GRC to access the LDAP server through SSL. The LDAP server must be configured to support SSL.
2-22 Oracle Enterprise Governance, Risk and Compliance Installation Guide
• Perform LDAP Recursive Search: Select the check box to search recursively for users in subfolders along with those in the base path specified in the Bind DN Suffix field.
• Unique User Identifier: uid
5. In the Manage Application Configurations page, click on Actions → Save. Then log off of GRC.
6. Stop the GRC Deployment in the WebLogic Console:
a Log in to the WebLogic Console at
http://host:port/console
Replace host with the FQDN of your GRC server, and port with the number you selected for the WebLogic Administration Server. (See step 7 of “Creating a WebLogic Domain” on page 2-5.)
b From the Domain Structure menu, select Deployments.
c From the Deployment page, locate the GRC deployment and verify the state is Active.
d Click the checkbox next to the GRC deployment.
e From the toolbar, click Stop → Force Stop Now.
7. Start the GRC Deployment in the WebLogic Console:
a From the Domain Structure menu, select Deployments.
b From the Deployment page, locate the GRC deployment and verify the state is Prepared.
c Click the checkbox next to the GRC deployment.
d From the toolbar, click Start → Servicing All Requests.

== Detailed Steps End Here==

(12)

Skip the SSL Configuration of GRC Weblogic Admin Sever at this time. SSL should be enabled after GRCI is implemented to avoid issue with GRCI installation.

(13)

Accessing the GRC

== Detailed Steps (13) ==

After configuring SSL successfully, access the GRC application at https://host:SSLport/grc, in which host is the FQDN of your GRC server, and SSLport is the port you selected to support SSL. (If you use WebLogic, see step 7 on page 2-24. If you use Tomcat, see step 4 above.)
Because you are using a self-signed certificate, which is not signed by an official Certificate Authority, you get a security warning when you open GRC at this URL.
• For Internet Explorer, the warning reads, "There is a problem with this website’s security certificate.” Dismiss this warning by choosing “Continue to this website (not recommended).”
• For Firefox, the warning reads, “This Connection is Untrusted.” Dismiss this warning by clicking “I Understand the Risks,” and then “Add Exception.”

== Detailed Steps End Here==

GRCI 8.6.4.5000 Step by Step Installation will follow in next article.

Starting My Blog back again based on my field expeience Since 2008 where I left this blog (Step by Step Oracle Product Implementaton Series )

noreply@blogger.com (Ramnik Gupta) — Sat, 3 Aug 2013 18:48:00 -0700

I am back on my blog and will start writing Step by Step series on Oracle Database 12c,Exadata, Golden Gate, RAC,ASM,EBS R12, Fusion Applications, Fusion Middleware products (IDM/IAM/Web Center/Spaces/SOA), OBIEE/OBIA, Goverance, Risk and Complance GRC/GRCI/CCG/PCG), SSL and many more articles on various Oracle products which can help Oracle Community. Also I am going procure a high end server soon so that I can build Step by Step Oracle Series with Integration of these products which may take some time. I would like to mention here as time allows you will see always step by step instruction to build these enviornments at your home ,office and where you are located. I promise to as detailed as I always use to be in my previous posts." I would highly appreciate if you provide your feedback what you would like to see more on my blog and don't find in other great blogs. Feedback is really appreciated and help me to get going to this long journey. Regards, Ramnik Gupta Author of this Blog and serving Oracle Community by sharing my field experience

Oracle Applicaitons (EBS)11.5.9CU2 upgrade to R12.1.3 includes Platform Migration from HP-UX 11.23 to HP-UX 11.31 and Integration with Portal/SSO/SSL

noreply@blogger.com (Ramnik Gupta) — Sun, 12 Oct 2008 19:27:00 -0700

Oracle Application 11.5.9CU2 upgrade to Oracle application R12.1.3. This upgrade includes upgrade from Portal 3.0.9 , Portal Login server/SSL to Portal 10g/SSO/SSL. Also database upgrade from 9.2.0.7 to 10.2.0.4 patchset. Also I am going to discuss about various paths to upgrade to R12..

The most important aspect of the upgrade to assess you current EBS 11i system techinically and functionally.

Here in the article will be going to cover the technically aspect but will give some guidance on functional aspect.

On Hold.

Step by Step Information on R12 - How to Validate APPS Schema

noreply@blogger.com (Ramnik Gupta) — Tue, 12 Aug 2008 19:30:00 -0700

In day to day activity DBA's encounter issues related to invalid objects. Common solution to the problem is running adadmin utility and utlrp script. In this post we are going to discuss invalid APPS schema not objects.

Now the question must be in your mind in what situations you really needs to validate the APPS Schema.

Here we go....

If face any problem with AD_DDL package at runtime

When patch is applied. You can run this only once even you apply more then one patches at a time.

If you upgraded Oracle applications or applied Maintenance pack

After migration using export/import

After Custom development of APPS Schema

Methods to validate APPS Schema

On Unix:
1. Run system/passowrd @$AD_TOP/admin/sql/advrfapp.sql
2. Using adadmin utility and opt for "1. Validate APPS Schema" under "Maintain Applications Database Entities".

Steps to Validate APPS Schema

1.Run adadmin utility. Select the option "Maintain Applications Database Entities" from main menu of AD Administration.

2.Select "Validate APPS Schema" from sub-menu of "Maintain Applications Database Entities".

3. Now review the output file located at $APPL_TOP/admin/SID/out. The report name will be .lst. Look for any missing or invalid pacakges , synonyms or invalid objects in APPS schema. Also check and verify for table or sequences in APPS and base schema. Follow the instruction in the file to resolve any issues.

Hope this helps.

Step by Step Information on Oracle Applications R12 Control Scripts

noreply@blogger.com (Ramnik Gupta) — Wed, 23 Jul 2008 13:10:00 -0700

In this post you will come to know about Oracle Applications Control Scripts. It is very important for an APPS DBA to know the location and its usage while handling APPS DBA duties.

The application Tier server process control scripts are used to start and stop server processes on the applications tier like adcmctl.sh (Concurrent manager start/stop control script) and adapcctl.sh (HTTP Server start/stop control script).

The following question can be arise in your mind regarding control scripts on Application Tier.

Now you will think where this control scripts are located in Application Tier

How these control scripts are created.

Is it possible to recreate these control scripts.

Here you go...The answer to the above queries are...

Control scripts are located in the $ADMIN_SCRIPTS_HOME (i.e, $INST_TOP/admin/scripts) directory. It is created by Rapid Install during the installation and you can recreate using AutoConfig (i.e,adautocfg.sh control script) as and when required.

The syntax of the control scripts is [stop or start]

$./adalnctl.sh stop (To stop the Apps Listener)
$./adalnctl.sh start (To start the Apps Listener)

You can use other Application Tier server process control scripts for all server processes to stop and start at the same time.

$./adstrtal.sh (Apps username/password)
$./adstpall.sh (Apps username/password)

To stop or start Forms server in socket mode.

$./adfrmsrvctl.sh

To stop or start Forms OC4J instance in servlet mode.

$./adfrmctl.sh

To stop or start Application Listener.

$./adalnctl.sh

To stop or start concurrent managers.
(This control script required the APPS username and password).

$./adcmctl.sh

To stop or start the HTTP server.

$./adapcctl.sh

Hope you like this post. Please let me know what Topic you would like to see on my blog. Based on request I will start including other stuff too. I am taking my family time to write these articles so I will be on / off from the blogs. You inputs are highly appreciated to improve my blog.

Step by Step Information on Oracle Application R12 Environment files - Part 2

noreply@blogger.com (Ramnik Gupta) — Wed, 23 Jul 2008 07:47:00 -0700

I started in my last post about environment files..

In todays post I am going to discuss some more environment files which an APPS DBA should know.

adovars.env file

adovars.env file which is located under $APPL_TOP/admin, and called from <CONTEXT_NAME.env>. This files specifies various types of file location using various environment variables like

JAVA_TOP -> All java files are copied here and it is the top-level directory

CLASSPATH -> It lists the directories and zip file for java class files needed at runtime.

OA_JRE_TOP -> JRE installation location.

OAD_TOP -> Context-sensitive documentation files are copied at this location.

LD_LIBRARY_PATH -> To list the directories for dyanmic library files needed at runtime.

OAH_TOP -> HTML files are copied at this location.

fndenv.env File

This default values should not be modified of this file. This file is located under $FND_TOP direcotry. It sets additional environment varialbes used by Oracle AOL (i.e, Applcation Object Library).

devenv.env file

This file is located under $FND_TOP and is called by fndenv.env for the purpose of compile and link custom Oracle Forms user exits and concurrent program with Oracle Applications. It sets variable that help you link third-party software and your own custom applications with Oracle Applications.

adconfig.txt File

This file is located under $APPL_TOP/admin directory and AD utility perform a variety of database and file management task for which they require acces to specific configuration information. This information is specified when Oracle Application is installed. It is stored in the adconfig.txt file.

Hope this helps to my blog reader community.

Step by Step Information on Oracle Application R12 Environment files - Part 1

noreply@blogger.com (Ramnik Gupta) — Wed, 16 Jul 2008 10:46:00 -0700

Received numerous emails from my blog readers to start working on blog. Thanks for all of your appreciation ,support and encouragement to start again. My todays post will be based on Oracle Application R12. As I received request from my blog reader to continue with the series of R12. I will continue with R12 articles also going to cover other areas like Database 11g, Oracle Application server, SOA suites etc in my future posts. In this post I am going to discuss about R12 Oracle Environment files.

Environment Files and Control scripts:

Environment files are in place to manage the setup and configuration within the Oracle Application R12 system.Rapid install generates/create number of different environment files.

<CONTEXT_NAME>.env => $ORACLE_HOME (10.2.0.2) => Oracle Server Ent. Edition

<CONTEXT_NAME>.env => $ORACLE_HOME (AS 10.1.2)=> Oracle Tools Tech Stack

<CONTEXT_NAME>.env=> $ORACLE_HOME (AS 10.1.3)=> Java Tech Stack

<CONTEXT_NAME>.env => $APPL_TOP => Oracle Applications

APPS<CONTEXT_NAME>.env => $APPL_TOP =>Consolidated Environment file

Here CONTEXT_NAME is referred to _.CONTEXT_NAME.env is called environment setup file. Whereas APPS <CONTEXT_NAME>.env.env is called a consolidated environment file which reside under APPL_TOP directory.

Now question must be arise in your mind what is in CONTEXT_NAME.env environment file.

As pre R12 DBA must be aware of and fresher might be thinking what it consist of.

So here comes the answer....

CONTEXT_NAME.env consist of :

Product Directories and Subdirectories

Product Directories Paths

Other environment information

Oracle application have important and core environment file is <CONTEXT_NAME>.env

Also you should know what parameters are part of <CONTEXT_NAME>.env environment file.

Here you go to know the description of these parameters.

APPLFENV - This parameter refers to name of the <CONTEXT_NAME>.env environment file.

APPL_TOP - This parameter refers to top-level directory for this installation of Oracle applications.

INST_TOP - This parameter refers to top-level directory for this instance.

FND_TOP - This parameter refers to path to AOL directory. For e.g /d01/oracle/apps/apps_st/appl/fnd/12.0.0

AU_TOP - This parameter refers to path to the applications utilities directory. For e.g /d01/oracle/apps/apps_st/appl/au/12.0.0.

NLS_LANG - This parameter refers to territory,language and character set installed in the database. For e.g AMERICAN_AMERICA.UTF8

NLS_DATE_FORMAT - This parameter refers to National language support date format.For e.g The default is "DD-MON-RR", e.g 16-JUL-08.

NLS_NUMERIC_CHARACTERS - This parameter refers to National language support numberic separators. The defulat is period and comman (".,").

<PROD>_TOP - This parameter refers to path to a product's top directory

GWYUID - This parameter refers to the user name/password that give access to the initial sign on.

APPLDCP - This parameter refers to whether PCP is being used. This should be set to OFF if not using PCP.

APPLTMP - This parameter refers to directory for temp file in Oracle Applications.

APPLPTMP - This parameter refers to directory for temp PL/SQL output files.

APPLCNAM - This parameter refers to 8.3 file name convention for concurrent manager log and output files format.

APPLLOG - This parameter refers to concurrent manager log subdirectory.

APPLOUT - This parameter refers to concurrent manager output files subdirectory.

APPLCSF - This parameter refers to the top-level directory for concurrent manager log and output files if they are consolidated into single direcotry for all products.

PATH - This parameter refers to sets directory search path

FNDNAM - This parameter refers to the name of the schema to which the system
administration responsibility connects.

ADMIN_SCRIPTS_HOME - This parameter refers to directory under $INST_TOP that identifies the location of control scripts.

PLATFORM - This parameter refers to the O/S currently in use. The value of this parameter should match with $APPL_TOP/admin/adpltfrom.txt

I will continue with other environment files in my next post..coming soon...

Steps involved in Cloned Target System in R12 EBS Enviornment

noreply@blogger.com (Ramnik Gupta) — Tue, 5 Feb 2008 19:11:00 -0800

1. Prepare the Source system database and application Tier for cloning.

2. Copy the Source System to Target System

3. Configure the Target System

4. Post Clone Tasks.

Steps involved in Adding a Node using Advance Cloning Options in R12 EBS

noreply@blogger.com (Ramnik Gupta) — Tue, 5 Feb 2008 18:51:00 -0800

In this post I am going discuss steps involved in Adding a Node using Advance Cloning Options in R12 EBS

1. Rapid Clone can be used to setup a new node being added to an existing application system.

2. On your new node can either run the Same services as the source node or different services.

3. Prepare the Source system, copy it to the new node and configure it as applicable.

4. Once the adcfgclone.pl completes, set up the environment and run adaddnode.pl on the target system.

cd $COMMON_TOP/clone/bin

perl adaddnode.pl

Steps Involved in Cloning for Mulit-Node Systems in R12 EBS Enviornment

noreply@blogger.com (Ramnik Gupta) — Tue, 5 Feb 2008 17:29:00 -0800

I am going discuss in this post Steps involved in Cloning Mulit-Node Systems in R12 EBS environemnt. Rapid clone also used for Mulit-Node System cloning like Single-Node System.

In R12 Release,only one copy of the files for the application tier nodes needs to be copied to the target system as new feature of unified APPL_TOP introduced. In which all files required for all application tier services are included with every applications node, with multiple nodes being differentitated by the services started on each.You can clone using shared file system too.You can specify the services to start for each target node while entering response to the prompts during configuration steps.

To add non-shared applications nodes,carry out the copy and configure steps in the same way as on Primary Node.

Clone a Single-Node System to Mulit-Node System

This method of cloning allows the original node system to be cloned into a multi-node system.

Pre-Steps on the source and all target nodes.

a. Verify source and target node software versions
b. Apply the latest Rapid Clone patch (if required or applicable)
c. Set up Rapid Clone on the Apps Tier.
d. Set up Rapid Clone on the DB Tier.

Steps involved in Cloning procedure

a. Prepare the source system
b. Copy the Source system to the Target System
c. Configure the Target System
d. Post clone Steps like Profile update,utl_file_dir,Printer update, Workflow mailer etc.

Cloning a Mulit-Node System to a Mulit-Node System

1. A multi-node system can be cloned if the number of nodes and distribution of servers inthe target system matches that of the source system.

2. To clone a multi-node system to multi-node system perform the cloning process on each node.

Special Note: Always cloned database instance first.

Steps involved in Refreshing a Target System in R12 EBS Environment

noreply@blogger.com (Ramnik Gupta) — Tue, 5 Feb 2008 16:57:00 -0800

In this post I am going to discuss about Refresh a Target System in R12 E-Business Suite environment.

The system to be clone is called as "Source System" and newly created(or cloned) system is called as "Target System".

Step 1: Ref in my previous post "Steps Involved in Cloning R12 e-Business Suites Environment (Single Node)" to prepare the source system.

Step 2: Copy any parts of the application tier file system that have been updated on the source system. It may require to refresh the target system's APPL_TOP,COMMON_TOP,or Tech Stack.

Step 3: You need to Refresh your database node at the same time. For database node refresh, Copy the database node file system ($ORACLE_HOME - RDBMS HOME).

Step 4: To configure the Target System to be Refreshed by specifying the exisiting Target System when running adcfgclone.pl.

perl adcfgclone.pl dbTier <CONTEXT FILE ON TARGET SYSTEM ON DATABASE NODE>

perl adcfgclone.pl appsTier <$INST_TOP/appl/admin/<CONTEXT FILE ON TARGET SYSTEM ON APPS TIER>>

Step 5: Once Refresh is finished. If you have customized environment then change post clone profile options, utl_file_dir etc.

Test your Refreshed environment and enter the below URL in your browser

http://r12b.quickoracle.com:8000

or

http://<hostname>.<domain_name>:<HTTP port>

Steps Involved in Cloning R12 e-Business Suites Environment (Single Node)

noreply@blogger.com (Ramnik Gupta) — Thu, 31 Jan 2008 10:22:00 -0800

Cloning is the process of creating an identical copy of an existing Oracle Application System. The new and existing systems must have component versions and platform type identical for cloning.

I am going to discuss the steps involved to Clone a Single Node system in R12 EBS.

Source Instance Name : r12a.quickoracle.com
Target Instance Name : r12b.quickoracle.com

Preparation to clone the Oracle Application System (Source).

1) sudo su - appl <sid> user.

2) execute the Consolidated Applications enviornment file.

$cd $APPL_TOP
$.APPS<context_name>.env

3) zip utility should be in your PATH.

$ PATH=$PATH:<Location of zip utlity installed on your system>
$ export PATH

4) Stop all Apps Tier Server processes.

$ cd $INST_TOP/admin/scripts
$ adstpall.sh APPS/<passwd of APPS user>

5) Verify latest Rapid Clone patches on metalink and apply if required.(Not applicable)

6) On Apps Tier run AutoConfig and after that on Database Tier.

Apps Tier:

$ cd $INST_TOP/admin/scripts
$ adautocfg.sh

DB Tier:

RDBMS HOME = $ORACLE_HOME
$ cd $ORACLE_HOME/appsutil/scripts/<context_name>
$ adautocfg.sh

Pre-Clone Steps Starts from Here

1. DB Tier preparation for Cloning :

On Source System:

a) login in as Oracle user : $ sudo su - oracle

b) Run the following commands:

RDBMS HOME = $ORACLE_HOME

$ cd $ORACLE_HOME/appsutil/scripts/<context_name>
$ perl adpreclone.pl dbTier

2. Verify the errors and warnings in the log.

RDBMS_HOME = $ORACLE_HOME

Location of the log file StageDBTier_.log

$cd $ORACLE_HOME/appsutil/log/<context_name> directory

3. Apps Tier preparation for Cloning

a) $ sudo su - appl<sid>

b) Run Pre-Clone on all the nodes that contains an APPL_TOP.

$cd $INST_TOP/admin/scripts
$perl adpreclone.pl appsTier

4. Verify the errors and warnings in the log.

Location of the log file StageAppsTier_<time>.log

$cd $APPL_TOP/admin//log directory

Pre-Clone Steps End Here and Clone Steps Start From Here

1. Copy or Tar ball or sftp source system application tier file system to the target system.

Note: You need not to shutdown your source system application node for this step.

File System which need to be Tar ball or sftp to target system from Source System
includes:

APPL_TOP

COMMON_TOP

ORACLEAS_10.1.2_ORACLE_HOME

ORACLEAS_10.1.3_ORACLE_HOME

2. copy or TAR ball or sftp source system database tier file system to the target system.

a) This step require you bring down your source sytem (i.e database node) as user oracle.
b) Shutdown normal the source system database
c) copy the database (.dbf) files from the source to the target system
d) copy or TAR ball or sftp the source database ORACLE_HOME to the target system.

3. DBTier Configuration and then start the Target System database Server.

a) sudo su - oracle on target system
b) Run adcfgclone.pl on DB Tier. You will be prompted wfor the values specific to the target system like SID,port etc.

RDBMS_HOME = $ORACLE_HOME

$ cd $ORACLE_HOME/appsutil/clone/bin

$ perl adcfgclone.pl dbTier

4. Verify errors and warnings in the log

Location of the log file ApplyDBTier_<time>.log

$ cd $ORACLE_HOME/appsutil/log/<context_name>

5. Apps Tier configuration on Target system application Server nodes.

a) $sudo su - appl<sid>
b) Run adcfgclone.pl on Apps Tier. You will be prompted wfor the values specific to the target system like SID,port etc.

$cd $COMMON_TOP/clone/bin
$perl adcfgclone.pl appsTier

6. Verify the errors and warnings in the log.

Location of log ApplyAppsTier_<time>.log

$cd $APPL_TOP/admin/<context_name>/log

7.Once clone is finished. If you have customized environment then change post clone profile options, utl_file_dir etc.

Clone Steps End Here

Test your cloned environment and enter the below URL in your browser

http://r12b.quickoracle.com:8000

or

http://<hostname>.<domain_name>:<HTTP port>

Where is Administration Server Component in R12 EBS

noreply@blogger.com (Ramnik Gupta) — Sun, 27 Jan 2008 11:34:00 -0800

Pre-11i & 11i DBA's now say goodbye to Administration Server component.Administration Server in R12 is now a history or the right way to say "Obsolete".

There no such component in R12 Architecture and by default any application tier node used to perform the below operations.

Apply DB patches to Apps: In Oracle application most of the time you will observe in most of the patches consists of files and scripts that update the file system and DB objects. To apply these patch (i.e, which includes cumulative and minipacks and maintenance packs patches). You use adpatch utility (also called AutoPatch utility) to perform any updates.

Maintain Apps:AD Administration Utility (adadmin) require maintenance to optimize system performance and enables you to perform other file system and database maintenance tasks.

R12 Java Servlet Access using HTML Applications

noreply@blogger.com (Ramnik Gupta) — Sat, 26 Jan 2008 06:47:00 -0800

In this post I am going discuss access path use by HTML interface module when using a JSP.

a)User access a function on a browser (HTML hyperlink access)
b)then the browser generate a URL request to the web server.
c)Web listener talk to servlet engine (Jserv)then runs a JSP.
d)JSP then contact Application tables to obtain contents and use metadata dictionary information to build a HTML page.
e)The HTMP page which is build in previous step sent back to the browser with the help of web server.

R12 Oracle Application Framework

noreply@blogger.com (Ramnik Gupta) — Sat, 26 Jan 2008 06:09:00 -0800

In this post I am going to discuss about R12 Oracle Applicaiton Framework Components and it processing.

Oracle Application Framework is the development platform for HTML-based applications. It consist of a java-based application tier framework and associated services. It designed to facilitate the rapid deployment of HTML-based applications.

Oracle Application Framework uses below components:

AOL JAVA or AOL/J

It provides the OAF with underlying security and applicaiton Java Services.Also OAF with its connection to the DB and with application-specific functionality for e.g attachments and flexfields.

BC4J

JDeveloper incluedes BC4J. Java Business components are created by BC4J for representing business logic. It seperates the business logic from UI by mapping the relational tables to java objects.

Java Controller

It processes the programmatic UI definition.

Metadata UI Definition

Apache Jserv module provides the Java servlet engine uses metadata dictionary to to construct the Framework UI.

HTML Generator UIX

UIX , the HTML Generator

HTML-based applicaiton uses the following path with OAF on application Tiers. The steps are discussed below.

a)User click a function on browser (HTML hyperlink access).
b)URL request to the web listener sent by browser.
c)User access validated by AOL/J.
d)Page definition is loaded from the metadata dicitionary on the DB tier into the application Tier (i,e. Metadata UI definition)
e)BC4J objects that contain the application logic and access the database are instantiated.
f)Java controller programatically manipulates the page definition as necessary, based on dynamic UI rules.
g)HTML UI Generatior (UIX)interprets the page definition. It creates the related HTML based on UI standards, and send the page to the browser.

Step By Step Installation of VMWARE on WinXP Professional - Part I

noreply@blogger.com (Ramnik Gupta) — Sun, 13 Jan 2008 13:54:00 -0800

In this post I am going to discuss about Step by Step Installation of DB11gR1 Clusterware on OL4 Update 5 using VMWare (Virtual Servers) on WinXP. I tested this configuration on my laptop.

Objective: This installation procedure for learning and testing purpose. This kind of configuration is not suitable for any Production and Test Environment.

Hardware Requirements

Lenovo Thinkpad Laptop
Windows XP Professional 5.1.2600,Service Pack 2 (Host O/S)
Intel(R) Core(TM)2 Duo CPU
T7300 @2.00 GHZ
200 GB HDD (Actual Installation required by one node is 35 GB + 10 GB to Stage Software required by you and for future use)
2 GB RAM
Note: As far as my experience with this installation you should have minimum 3GB RAM. I faced few issues like one node goes down and if you are running any memory intensive program. Better to have minimum 3 GB RAM. I used 800 MB for each node and rest for host operating system.
Oracle Enterprise Linux 4 (Update 5) (Guest O/S)
VMWare Server 1.0.4

Software Requirements

Oracle 11g (11.1.0.6) Database & Clusterware Software

Oracle Enterprise Linux 4 (Update 5)

VMware Server 1.0.4

General

Follow the sequence to Install RAC11g+ASM on clusterware using OL4 update 5(On VMWare).

Step By Step Installation of VMWARE on WinXP Professional - Part I

Step by Step Installation of Oracle Enterprise 4 Update 5 using VMWare on WinXP Professional - Part 2

Step by Step Installation of Oracle Enterprise 4 Update 5 using VMWare on WinXP Professional - Part 3

Step by Step Installation of Clusterware11gR1 on Oracle Linux 4 Update 5 using VMWare on WinXP - Part 4

Step By Step Installation of ASM and Oracle DB11gR1 on Oracle Enterprise Linux 4 Update 5 using VMWare on WinXP - Part5

Step By Step Installation of VMWARE on WinXP Professional - Part I - Start Here

Start the installation by double clicking the VWWare software you downloaded from VMWare Site. There is free Trial product key is allocated for you to use this product. Screen Shots are Self Explantory to Install VMWare. Please Follow the snapshots. If you are not able to read the text inside the snapshot please click on snapshot and it will take you to picasa web album and you can see slide show to view more clearly.

Step By Step Installation of VMWARE on WinXP Professional - Part I - End Here

VMWare Virtual Machine Configuration- Start Here
Configure the First Virtual Host - rglinux1
Follow the self explantory snapshots to install your first Virtual host "rglinux1". You can give any name to your vitual machine

To Start "VMWare Server Console" click on your VMWare shortcut on your desktop - Select the default option "Local Host"

To Configure Virtual Machine Select "New Virtual Machine" under Virtual Machine Options

The "New Virtual Machine Wizard" will start, Click Next

Select "Custom" under Virtual Machine Configuration

Select "Linux" under Guest Operating System and change the version to "RedHat Enterprise Linux 4"

Name the Virtual Machine "rglinux1" under Virtual Machine Name. Enter the Location "C:\vms\rglinux1" (Single Node Configuration). To Configure Linux Cluster (Multi-Node Configuration) for RAC configuration. You can change the path as "C:\vms\RAC\ASM11g\rac1" and Machine Name for RAC Setup is ASM_11gRAC1

Set Access Rights - Uncheck this option. The default is shown in snapshot

startup/Shutdown Options - Select Default "User that powers on the virtual machine"

Select "Number of Processor" depending on your machine - Default is one - I select as Two as per my machine configuration

Memory for Virtual Machine - I configured initially with 824 MB. The best for RAC11g configuration is 3GB and you can allocate 1024 Machine for each Virtual Machine and rest for Host Operating system (WinXP

Select Network Type as "Use Bridged Networking"

Select I/O Adapter Types as "LSI Logic"

Select a Disk as "Create a new Virtual Disk"

Select a Disk Type as "SCSI"

Specify Disk Capacity - Select the second option as split disk into 2GB disks. Uncheck the first option shown in snapshot - I just Enter 35GB to configure other products of oracle on same box. Ref 11g RAC docs for Disk Space Requirement

Enter virtual disk filename (rglinux1.vmdk in snapshot). I changed for my RAC configuration to localdisk.vmdk.

Creating a Disk - This is for Single Node Installation not for RAC Configuration on Linux Clusters. This step can be skipped if you are configuring Linux Cluster for RAC11g.

View of First Virtual Machine name "rglinux1" or You can give name as ASM_11gRAC1 for linux cluster for RAC11g Configuration.

VMWare Virtual Machine Configuration- End Here

To Install Linux on Your First Virtual Machine. Please follow the post "Step by Step Installation of Oracle Enterprise 4 Update 5 using VMWare on WinXP Professional - Part 2"

Step by Step Installation of Oracle Enterprise 4 Update 5 using VMWare on WinXP Professional - Part 2

noreply@blogger.com (Ramnik Gupta) — Sun, 13 Jan 2008 13:52:00 -0800

In my previous post we Configure the First Virtual Machine as rglinux1 or ASM_11gRAC1.In this post I am going to discuss further configuration of First Virtual Machine and then we will Install Linux on First Virtual Machine.

For RAC11g Configuration First we need to Add the Shared Disks and an additional Network Card (to handle private network for interconnect). Select "Edit Virtual Machine from VMWare Server Console". A new pop-up windows of Virtual Machine Settings will come. Select Add to "Add New Hardware". Select "Ethernet Adpater" to configure private Interconnect (2nd NIC or Ethernet Card). Select "Next" to go for next screen of "Network Type" and Select option as "Host-Only:A private network shared with the host". Please verify that "connect at power on" should be selected.

Again start the "New Hardware Wizard" to configure Disk for RAC11g Configuration.

You need to configure based on below information provided for database file,OCR and Voting disk.

Disk Table

Database files => 3Gb => SCSI 1:0 =>datadisk1.vmdk

Database files => 3Gb => SCSI 1:1 =>datadisk2.vmdk

Database files => 3Gb => SCSI 1:2 =>datadisk3.vmdk

OCR => 300Mb =>SCSI 1:3=>ocrdisk.vmdk

Voting Disk => 300Mb => SCSI 1:4=>votingdisk.vmdk

Select "Hard Disk" to add a new Hard Disk. Click on "Next" to go to next screen to select a Disk. Select "Create a new Virtual Disk" then Select Disk Type as "SCSI". Click on "Next" to go to next screen to allocate Disk Space mentioned above for Database files. Please select "Allocate all disk space now" option to configure these disks. On next screen Specify data file please give name of this disk as "datadisk1.vmdk" and browse the path to share directory under "C:\vms\RAC\ASM11g\share" to save this file. Once the Disk is create then select the same harddisk and click on Advanced configuration to change the virtual device node as mentioned above in "Disk Table". Change Virtual Device node from existing value to SCSI 1:0. and select "Indepedent" and "persistent" disk option. You can repeat this step for all other disk to configure disk for RAC11g configuration.

When all disk are configured. Close the "Virtual Machine Settings" to confirm the changes to Virtual Machine configuration file.Now edit the virtual machine confiuration file (i.e, Red Hat Enterprise Linux 4) and the parameters where # sign is shown. Remove this # sign to use these parameters as part of you configuration file.
Configuration File - Start Here
config.version = "8"
virtualHW.version = "4"
numvcpus = "2"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "900"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "localdisk.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "D:"
ide1:0.deviceType = "cdrom-raw"
floppy0.present = "FALSE"
Ethernet0.present = "TRUE"
displayName = "ASM_11gRAC1"
guestOS = "rhel4"
priority.grabbed = "normal"
priority.ungrabbed = "normal"

#disk.locking = "FALSE"
#diskLib.dataCacheMaxSize = "0"
#diskLib.dataCacheMaxReadAheadSize = "0"
#diskLib.dataCacheMinReadAheadSize = "0"
#diskLib.dataCachePageSize = "0"
#scsi1.sharedBus = "virtual"

scsi1.present = "TRUE"
scsi1:0.present = "TRUE"
scsi1:0.fileName = "C:\vms\ASM11g\share\datadisk1.vmdk"
scsi1:0.mode = "independent-persistent"
#scsi1:0.deviceType = "disk"

scsi1:1.present = "TRUE"
scsi1:1.fileName = "C:\vms\RAC\ASM11g\share\datadisk2.vmdk"
scsi1:1.mode = "independent-persistent"
#scsi1:1.deviceType = "disk"

scsi1:2.present = "TRUE"
scsi1:2.fileName = "C:\vms\RAC\ASM11g\share\datadisk3.vmdk"
scsi1:2.mode = "independent-persistent"
#scsi1:2.deviceType = "disk"

scsi1:3.present = "TRUE"
scsi1:3.fileName = "C:\vms\RAC\ASM11g\share\ocrdisk.vmdk"
scsi1:3.mode = "independent-persistent"
#scsi1:3.deviceType = "disk"

scsi1:4.present = "TRUE"
scsi1:4.fileName = "C:\vms\RAC\ASM11g\share\votingdisk.vmdk"
scsi1:4.mode = "independent-persistent"
#scsi1:4.deviceType = "disk"

scsi1.virtualDev = "lsilogic"
ide1:0.autodetect = "FALSE"
Ethernet1.present = "TRUE"
Ethernet1.connectionType = "hostonly"

scsi0:0.redo = ""
scsi1:0.redo = ""
scsi1:1.redo = ""
scsi1:2.redo = ""
scsi1:3.redo = ""
scsi1:4.redo = ""
ethernet0.addressType = "generated"
ethernet1.addressType = "generated"
uuid.location = "56 4d f6 04 91 f9 39 2c-b9 3f 19 f1 c4 af 8a 39"
uuid.bios = "56 4d f6 04 91 f9 39 2c-b9 3f 19 f1 c4 af 8a 39"
ethernet0.generatedAddress = "00:0c:29:af:8a:39"
ethernet0.generatedAddressOffset = "0"
ethernet1.generatedAddress = "00:0c:29:af:8a:43"
ethernet1.generatedAddressOffset = "10"

ide1:0.startConnected = "TRUE"

tools.syncTime = "TRUE"

workingDir = "."
Configuration File - End Here

Linux Installation - Start Here

"Edit The Virtual Machine Setting" under VMWare Server Controls

Select The "CD-ROM" under Hardware Tab

Change the Connection on right Pane of CD-ROM from Use Physical Drive to Use ISO Image. You can place you Linux ISO Image on your Hard Drive Or copy the ISO Image on CD-ROM. I Staged the Oracle Enterprise Linux on my Hard Drive C:\Software.

Select the Second option "Use ISO Image" under Connection.

Browse the First ISO Image of Oracle Enterprise Linux (disc1) under "Use ISO Image" and Click on "OK"

Click on "Start this Virtual Machine and You will see Linux boot: Prompt. Press Enter to Continue with Linux Installation.

Linux Driver Installation Screen

Linux O/S is test CD on this step. Press Tab to Skip this test

Probing for Video Card

Click Next to Continue with Linux Installation

Linux O/S Language Selection - By Default "English(English)"

Select appropriate Keyboard for the System (U.S English). Click "Next" and a Warning Message will display. Press "Yes" to Continue.

Keep Default selection on this page and Select "Next" to Continue with Linux Installation.