This post covers overview of Repository Creation Utility(RCU) which is first thing you need to do, if you are planning to implement/install Oracle Fusion Middleware 11g R1 (11.1.1.0).

Metadata Repository - contains metadata for Fusion Middleware Components (SOA, Webcenter, Identity Management) . There are various types of Repository - Metadata Services (MDS), Audit Services (IAU), Oracle Internet Directory (OID), Single Sign-On (SSO), SOA Infrastructure (SOAINFRA), Business Activity Monitoring (BAM) , User Messaging (ORASDPM) , Oracle WebCenter (WEBCENTER) , WebCenter Portlets (PORTLETS) , Oracle Content Server (OCSERVER) , Portal (PORTAL), Discoverer (DISCOVERER), Oracle Identity Federation (OIF) , Discussions (DISCUSSIONS) and Wiki and Blog (WIKI)

Repository could be Database-based or File-based, most component (Webcenter, SOA, OID…) requires Database-based Repository.
.

How to create Database-based repository ?
RCU - Repository Creation Utility is tool to create schema and load repository in existing database for Fusion Middleware components. 

Download RCU from here

.

Key points for Repository Creation Utility (RCU) in FMW

1. RCU can be run in two mode - GUI (Graphical User Interface) & CLI (Command Line Interface)

2. For Fusion Middleware 11g R1 (11.1.1.X) , RCU can only load schema in Oracle Database (version 10.2.0.4 and higher or 11.1.0.7 and higher)

3. You can run RCU locally (same machine where Database is running) or Remotely (Database is on remote machine)

4. By default RCU creates default schema and load repository in default tablespaces. RCU provides flexibility to change schema or tablespace name. (Only exception to this is Oracle Internet Directory (OID) schema)

5. You could load multiple repository (like Portal, webcenter, SOAINFRA) in single database. You could also load different version of same repository (like dev_soainfra, test_soainfra for DEV & Test instance resp.) in same database. (This is interesting feature for using single database for multiple Fusion Middleware Instances)

6. You can start RCU (Repository Creation Utility) from $RCU_SOFTWARE/bin/ rcu (for Unix) or rcu.bat (for Windows) ; This will start RCU in GUI mode. For CLI mode use “rcu [-silent | -interactive] {<command> <options>}”

7. RCU log file is written to the RCU_SOFTWARE_DIR/ rcu/ log/ logdir.<date_timestamp>/ rcu.log

8.For step by step Fusion Middleware Repository Creation Utility with screen-shots click here

.

What to do after creating Fusion Middleware Database-based Repository ?
Before you can use Repository for fusion middleware component (soa, webcenter), you need to register Repository with Oracle WebLogic Server domain . (How to register Database-based with WebLogic domain ? coming soon…)

. 

References

• RCU Download Link
• FMW Repository Creation Utility Documentation 
• RCU Database Requirement
• Managing Oracle Metadata Repository 

Share This

Oracle today launched its much awaited Fusion Middleware 11g  

Main component in Oracle Fusion Middleware 11g

1) Oracle WebLogic Server (J2EE Application Server)
2) Oracle WebCenter (Composer, WC Framework, WC Services, WC Spaces)
3) Oracle SOA Suite (Adapters, Service Bus, Business Rules, BAM, B2B, BPEL)
4) Oracle Identity Management (OID, DIP, Federation, OVD, Role Manager, OAAM, Entitlements, Directory Services Manager)
5) Oracle Business Intelligence (Discoverer, Portal, Reports, Forms) 
6) Oracle Application Component(Dev Tools, HTTP Server, Webcache, Web Services, DAS)
7)  Oracle Metadata Repository  

_____________ 

You can download Oracle Fusion Middleware 11g  from here

If you are confused about which component to download, check Oracle Fusion Middleware 11g download FAQ 

Share This

This post covers installation of Oracle Application Management Pack (AMP) on existing Oracle Enterprise Manager Grid Control Component (Oracle Management Service & Oracle Management Agent) . To know more about OEM Grid Control components click here

OMS- Oracle Management Service component of OEM Grid Control communicates with Agents and upload data to repository. OMS is also responsible to display data from repository to console (end user’s browser)

OMA- Oracle Management Agent sits on node (machine) which you wish to monitor using OEM Grid Control, OMA uploads managed data to OEM repository (database) via OMS.
.

Points good to know for AMP 3.0 (Application Management Pack) Installation

1.Latest version of Application Management Pack (AMP) is 3.0 and available via Patch 8333939 on Oracle My Support(pka Metalink)

2. Oracle Enterprise Manager (OEM) Grid Control should already be running and minimum version of OEM Grid control should be 10.2.0.3 (latest OEM grid control version as of 21 June is 10.2.0.5)

3. If you don’t have OEM grid control, first install OEM Grid control 10.2.0.1 and then upgrade it to 10.2.0.3, 10.2.0.4 or 10.2.0.5

4. There are two parts in Application Management Pack 3.0
i) Grid Control Plug-in for Oracle E-Business Suite Management Pack
ii) Management Agent Plug-in for Oracle E-Business Suite Management Pack

Install “Grid Control Plug-in for Oracle E-Business Suite Management Pack” in OMS (Oracle Management Service) ORACLE_HOME of OEM Grid Control.

Install “Management Agent Plug-in for Oracle E-Business Suite Management Pack” in Management Agent (OMA) ORACLE_HOME of OEM Grid Control.

To understand this better assume below setup
a. Oracle E-Business Suite Database and Concurrent Manager is running on node1
b. Oracle E-Business Suite Form Server is running on node2
c. Oracle E-Business Suite Web Server is running on node3
d. OEM Grid Control 10.2.0.3 or higher(Management Repository, Management Service and Management Agent) is running on node4 then to monitor Oracle E-Business Suite using OEM Grid control follow this process

i) Install OEM Grid Management Agent on Node1, Node2, Node3
ii) Install “Grid Control Plug-in for Oracle E-Business Suite Management Pack” part of AMP 3.0 in OMS_HOME on node4
iii) Install “Management Agent Plug-in for Oracle E-Business Suite Management Pack” part of AMP 3.0 in AGENT_HOME on node1, node2 and node3

5. After installation of AMP 3.0, Discover Oracle E-Business Systems in OEM Grid Control. There are two ways to discover Oracle E-Business Suite System in OEM Grid.
i) Using Discovery Wizard in OEM Grid Console : Target -> Oracle Applications -> Discovery Wizard (in Related Links section)

ii) Command line using ebsdiscovery.sh on OMS HOME of Grid Control : $OMS_HOME/ sysman/ admin/ scripts/ ebs/ cli/ amp/ disc/ ebsdiscovery.sh

6.“Oracle Applications” subtab in OEM Grid Control console will be visible only to SYSMAN user. To enable this link to other users, click on Preferences -> Target Subtabs : move “Oracle Applications” from “Available Target” to “Selected Target”

.

Install Application (11i/R12) Management Pack 3.0 with OEM Grid Control

Prereq. apply Interoperability patches according to yourE-Business Suite version. For complete list check Metalink Note 812315.1 [thanks to Ashish for pointing this out]

1. Setup Provisioning Framework Software Library  (Directory on Management Service Server) Login to OEM Grid Control Console -> Deployments -> Provisioning -> Software Library Configuration

To know more about Software Library click here

2. Install Grid Control Plug-in for Oracle E-Business Suite Management Pack (repeat this in all OMS_HOME of OEM Grid)
2.1 Set ORACLE_HOME to OMS_HOME

2.2 Upload patch 8333939 to OMS Server and unzip patch

2.3 Start Installation from $UNZIP_Location/Disk1/runInstaller

2.4 Select “Grid Control Plug-in for Oracle E-Business Suite Management Pack” from Product List

2.5 In Destination Home select existing OMS home (Install Grid Control Plug-in in existing OMS HOME)
.

3. Install Management Agent Plug-in for Oracle E-Business Suite Management Pack (repeat this in all AGENT_HOME)

3.1 Set ORACLE_HOME to AGENT_HOME

3.2 Upload patch 8333939 to Server where agent is running and unzip patch

3.3 Start Installation from $UNZIP_Location/Disk1/runInstaller

3.4 Select “Management Agent Plug-in for Oracle E-Business Suite Management Pack” from Product List

3.5 In Destination Home select existing AGENT home (Install Plug-in in existing AGENT HOME)

.

Related/References

• 753584.1  Enterprise Manager Grid Control with Application Management Pack for Oracle E-Business Suite Installation Guide
• 812315.1  Oracle Application Management Pack for Oracle E-Business Suite, Release 3.0
• Oracle Application Management Pack for Oracle E-Business Suite Installation Guide
• Oracle Application Management Pack for Oracle E-Business Suite User’s Guide
• Steven Chan’s blog

Share This

There is three method available, you can use any of them to convert single instance to RAC instance.

a. using dbca

b. using EM

c. using rconfig utility

Here we are converting using DBCA (DataBase Configuration Assistant).

Conversion of single instance database to RAC database using DBCA consists of two part.

In first part, we take the backup of  single instance database.
In second part, we convert single instance database to RAC  database.

Part-I

Backup the original single instance database in easy nine steps.

( To see image in large, click on the image)

Step -1

Run oracle@rac$./dbca

Step-2

Step-3

Step-4

Step-5

step-6

step -7

step -8

step -9

Templates for existing single instance database has been created.

Go to $ORACLE_HOME/cgftoologs/dbca/templates and check generated backup of single instance.

Steps for conversion of this single instance templates to RAC instance,pl click this link

http://onlineappsdba.com/index.php/2009/07/05/single-instance-to-rac-conversion-using-dbca-part-ii/

Share This

This post covers installation of Oracle Enterprise Management (OEM) Grid Management Agents on Machine which you are planning to monitor using Oracle Enterprise Manager Grid Control.

What is OEM Grid Control Management Agent ?
Management Agent is software installed on node (machine) which you are planning to monitor. Agent collects information on target node (Host, Database, Listener, Application Server …) and transports that information to Oracle Management Service(OMS) which inturn pass on that information to Management Repository (Oracle Database). For overview of OEM Grid Control and various components Click Here

.

Installing OEM Grid Management Agent

There are various ways of installing agent on Nodes (which you wish to Monitor using OEM Grid control)

i) AgentDeploy Application - requires SSH, sudo access to run root.sh on remote target Node
ii) nfsagentinstall Script- limitation is one agent installation at a time, not supported on clusters (RAC databases) and  for OCFS file system. requires SSH, sudo access to run root.sh on remote target Node
iii) agentDownload Script - Download script from console is available from 10.2.0.5 version. For previous version download from here
iv) using Oracle Installer (OUI - Oracle Universal Installer)

.
i) AgentDeploy Application- useful for installing multiple Management Agents (mass deployment) remotely. AgentDeploy application connects to OMS (Oracle Management Service), copies files scripts required for Agent to target node and then run them to install Agent on remote Node.

To Use AgentDeploy Application - Login to OEM Grid Console -> Click Deployments -> Click Install Agent

ii) nfsagentinstall Script- software to install Management Agent is shared on remote nodes using NFS. To start Management Agent installation using this menthod execute script ./nfsagentinstall  -s <EMSTATE Directory location> -p <port number>

iii) agentDownload Script- This method uses pull technology, run agentDownload script from target node. This script creates directory for Agent Software, downloads response file from OMS (Management Server) Web Server and starts installation of Management Agent in Silent Mode.

iv) using OUI-  This method of installing Oracle Management Agent uses Oracle Universal Installer (OUI). Start Installer , when prompted for “Installation Type” select “Additional Management Agent” .

References

• Installing Grid Management Agent
• OEM 10g R2 Management Agent Deployment Best Practices
• Mass Agent Deployment
• 438158.1  How to Cleanly De-Install the EM 10g Agent on Windows and Unix

Share This

i have a small script which will generate and copy the files to your desired destinations and makes your task easy

Login to server A

#ssh-keygen -t rsa -b 2048

follow the instructions and complete the key generation with empty passphrase.

#cd /tmp

#vi sshkeycopy.sh

#-------- end of the script -----------

#! /bin/bash

 PATH="/bin:/usr/bin" if [ ! -e ~/.ssh/id_rsa.pub ]; then

 echo "RSA public key file ~/.ssh/id_rsa.pub not found!"

 exit 1

 fi

for desthost in $@; do

 ssh -q "${USER}@${desthost}" \

 "if [ ! -d ~/.ssh ]; then mkdir -m 0700 ~/.ssh; fi; \

 echo $(cat ~/.ssh/id_rsa.pub) >> ~/.ssh/authorized_keys; \

 chmod 0600 ~/.ssh/authorized_keys" || echo "Unable to connect to $desthost"

 done
#-------- start of the script -----------

Save the test using :wq and quit.

# chmod 700 sshkeycopy.sh

Now you are ready to copy the generated keys to the destination servers

# cd /tmp

#./sshkeycopy.sh serverB.linuxgurus.com serverC.linuxgurus.com

For the first time, it will ask password for the destination servers to copy the authorized_keys.

Now you can scp or ssh into destination servers from the current server without any passwords.

- Shankar

Share This

Oracle Enterprise Manager (OEM) Grid Control is monitoring software for Oracle Database, Fusion MiddleWare (FMW including OAS & SOA Suite), Oracle E-Business Suite, Siebel, SAP ….

This post covers overview of various components in OEM Grid Control

Oracle Enterprise Manager (OEM) / Grid Control Component

1. Oracle Management Agent: is software that sits on all nodes(machines) which you would like to monitor. Configuration file for Management Agent is $OH/ <hostname>_<sid>/ sysman/ config/ emd.properties. Agent uploads managed data (from server its monitoring) to Management Service via HTTP Server (URL of management Service HTTP Server is defined by REPOSITORY_URL parameter in emd.properties)
     Management Agent software also includes inbuilt HTTP Listener (different from standalone HTTP Server) to accept messages(data) from Management Service and this URL is defined by parameter EMD_URL in emd.properties.

Management Agent Log & Trace files are in $AGENT_HOME (or $OH/ <hostname>_<sid>) / sysman/ emagent.log, emagent.trc, emagentfetchlet.log, emagentfetchlet.trc , emagent.nohup

.
2. Oracle Management Service : Management Service upload data (from Management Agent via HTTP Server) to Management Repository (sysman schema in oracle database) using JDBC. Configuration file for Management Service is $OH/<hostname>_<sid>/ sysman/ config/ emoms.properties.
               Repository connection details are defined by parameter emdRepSID, emdRepServer, emdRepConnectDescriptor and emdRepUser in emoms.properties
  Management Service also monitors Management Agent (to check its up and running), submit enterprise manager jobs and other functions using EMD_URL (Management Agent runs inbuilt HTTP listener) defined in emoms.properties

Management Service Log & Tracefiles are in $AS_HOME (or $OH/ <hostname>_<sid>)  / sysman/ emoms.log, emoms.trc
.

3. Oracle Management Repository : is Database Schema (sysman) to store Enterprise Manager Data. Management Service connects to Management Repository using JDBC

4. Oracle Enterprise Manager (OEM) Grid Control Console: is browser based tool to monitor and manage targets.  Administrator uses console (URL on browser using webcache post of Grid Control Server) which connects to Webcache Port of OEM Grid Console.  
       Webcache in turn forward request to HTTP server of OEM Grid Middle Tier. HTTP Server retrieve data from Management Repository via Management Service.

5. HTTP Server: recieve requests from webcache, pulls data from Repository via Management Serviceand return response back to Webcache. HTTP Server also receive data from Management Agents, forward it to Management Service to store them in Management Repository.

6. Webcache : acts as web accelerator; forward request from Users (console) to HTTP Server and response back from HTTP server to Users (Console)

.
Communication between Management Agent & Service

Management Agent connect to Management Service via HTTP Server of Grid Control Middleware where as Management Service connect directly (using HTTP protocol) to Management Agent (Agent software include inbuilt http server)
 
.

References

• Enterprise Manager Advanced Configuration Guide 

Share This

1. There are two version of Discoverer
i) Standalone Discoverer - No support for Oracle SSO, Portlet Provider or Discoverer Connection Management
ii) Discoverer with OracleAS Infrastructure (OID/SSO)  (use OracleAS Infrastructure which is part of 10.1.4 Identity Management instead of 10.1.2 OAS)

Both Type of installation includes
a) Discoverer Server
b) Discoverer Plus
c) Discoverer Viewer

2. Install Discoverer 10.1.2 on same (R12 server) or different server under its own ORACLE_HOME (You can’t share discoverer ORACLE_HOME with R12 ORACLE_HOMEs)

3. Oracle Apps R12 VisionInstance contains a pre-installed Discoverer 10.1.2 End User Layer (EUL) but Production Install of R12 (a.k.a. Fresh install) does not contain a pre-installed Discoverer End User Layer (use eulapi to create new Discoverer EUL).

4. Standalone Discoverer is available as “Business Intelligence“  and Discoverer with SSO is available as “Application Server 10g Release 2“  here

5. It is possible to integrate standalone Discoverer to OracleAS infrastructure for SSO support

.

Installation/Configuration Overview

1. Install Discoverer (standalone or with 10gAS Infrastructure)
2. Copy dbc file from Apps R12 to Discoverer Middle Tier
3. Add entry in tnsnames.ora of Discoverer Middle Tier pointing to R12 Database
4. Create End User Layer (EUL) in R12 Database using eulapi - * only for Prod version (Non VISION instance)
5. Configure java plug-in in discoverer (to run Discoverer Plus) to same version as Apps R12
6. Configure variable s_disco_url in context file in R12 pointing to Discoverer URL

For complete step by step doc check Metalink Note 373634.1

.

References/Related

• 373634.1  Using Discoverer 10.1.2 with Oracle E-Business Suite Release 12
• Discoverer Configuration Guide 
• Discoverer Software 

Share This

If automatic updates are enabled on your Windows Client machine (Windows XP check here or Widows Vista here ) then there is high probability of FRM-92101 There was failure in the Form Server during Startup error while accessing forms in 11i or R12.

  One of our Apps DBA trainee faced this issue during hands-on exercise. (Next Apps DBA Batch starting 27 June)

Root Cause : Automatic Updates on windows upgraded IE (Internet Explorer) from version 7 to version 8. IE8 is not yet certified with Oracle Apps 11i or R12 (More info on Steven Chan’s blog here )

Fix: Quick fix is to uninstall IE8 from XP or Vista using steps mentioned here  and block automatic IE8 upgrade using steps mentioned here

Note * - There could be other reasons for FRM-92101 (Check Metalink note 189867.1  Forms: 9.x and 10.x: Troubleshooting FRM-92050, FRM-921xx)

.

References/Related

• Uninstall or Remove IE8 
• 760326.1  When Will IE 8 Be Certified With E-Business Suite?
• 811734.1  Is Oracle Forms Certified With Internet Explorer 8.0 ?
• 189867.1  Forms: 9.x and 10.x: Troubleshooting FRM-92050, FRM-921xx
• IE 8 Blocker
• Oracle Forms 10g Release 2 (10.1.2.x): Client Platform Support 
• Remove/Uninstall IE8

Share This

In a single database instance environment, there will be only one set of shared memory segments for the database. In other words, the buffer cache and shared pool are local to that particular instance; at any point in time the processes attached to that particular instance will be accessing only one set of memory structures.

However, in the RAC environment, multiple instances share the same database. The buffer cache is split among these multiple instances; each instance has its own buffer cache and other well-known SGA structures. It is possible for a buffer to be in the buffer cache of one of the instances on another node. The remote instance’s Lock Manager Service (LMS) processes will be accessing the global buffer cache, and the DBWR process will be accessing the local buffer cache.

Global Buffer Cache in Real Application Clusters

The data buffer cache is shared by more than one instance, and the buffer cache is called the global cache. Each instance has its own buffer cache local to that particular instance, and all of the buffer caches together create the global cache.

Global Cache waits:

The most common wait events in the RAC environment related to the global cache are:

1. Global cache cr request

2. Global cache busy

1. Global Cache cr Request:

When a process requires one or more blocks, Oracle first checks whether it has those (blocks) in its local cache. When a session requests a block(s) that was not found in its local cache, it will request that the resource master grant shared access to those blocks. If the blocks are in the remote cache, then the blocks are transferred using the interconnect to the local cache. The time waited to get the blocks from the remote cache is accounted in the global cache cr request wait event.

Global cache cr request waits are followed by the db file sequential/scattered read waits. Excessive waits for global cache cr request may be an indication of a slow interconnects.

You can use the oradebug ipc command to verify if the private network is used for cache transfer between instances.

SQL> oradebug setmypid

Statement processed.

SQL> oradebug ipc

Information written to trace file.

SQL> oradebug tracefile_name

/apps/oracle/asm/product/10.2.0/db_1/admin/RAC/udump/rac1_ora_4749.trc

SQL> host

[oracle@rac1 bin]$ cat /apps/oracle/asm/product/10.2.0/db_1/admin/RAC/udump/rac1

_ora_4749.trc  (trace file content the detail of the IPC configuration)

admno 0×2b360ab admport:

SSKGXPT 0xcc1df2c flags SSKGXPT_READPENDING     info for network 0

socket no 7     IP 192.168.1.134        UDP 27278

sflags SSKGXPT_UP

info for network 1

socket no 0     IP 0.0.0.0      UDP 0

sflags SSKGXPT_DOWN

active 0        actcnt 1

context timestamp 0

From the trace file, it is clear that the private network 192.168.1.134 is used for the cache fusion traffic and the protocol used is UDP.

Global Cache Statistics

The statistics related to global cache are available from the V$SYSSTAT view.

SQL> select name,value

2  from v$sysstat

3  where name like ‘gc%’;

NAME                                                                  VALUE

————————————————————— ———-

gcs messages sent                                                     7064

gc cr blocks served                                                   198

gc cr block build time                                               2

gc cr block flush time                                               38

gc cr block send time                                               17

gc current blocks served                                         3509

gc current block pin time                                        10

gc current block flush time                                      7

gc current block send time                                     174

gc cr blocks received                                               178

gc cr block receive time                                          357

gc current blocks received                                     118

gc current block receive time                                195

gc blocks lost                                                            0

gc claim blocks lost                                                  0

gc blocks corrupt                                                     0

gc CPU used by this session                                  2223

17 rows selected.

2. Global Cache Busy

In a cluster environment, each instance might be mastering its own set of data. Depending on the state of that buffer in the remote instance, the pin times may increase proportionally with the time it takes to service the block request.

If the buffer is busy at the cache level, you can use the following SQL to get the operations that are keeping the buffer busy.

SQL> select a.kcbwhdes “module”,
2   b.why0 “calls”,
3   b.why2 “waits”,
4  b.other_wait “caused waits”
5  from  x$kcbwh a,x$kcbsw b
6   where a.indx = b.indx
7  and b.other_wait > 0
8  order by b.other_wait;

module                         calls          waits      caused_waits
—————————————————————- —-
kdswh02: kdsgrp       53440      0              2

kdswh01: kdstgr        4402        0              2

Common Operations Causing buffer busy waits

Module: Definition

Kdsgrp: Performs get row piece. Typically, row pieces are affected only in case of chained and migrated rows. Row chaining has to be analyzed and fixed.

Kdstgr: Performs full table scan get row. Rows are accessed by a full table scan. Check the number of FULL table scans

Kdiixs: Perform index range scan

Share This