Installing Oracle 10R2 for SOA Suite

Enterprise manager login page

 Installing patch 10.2.0.2

applprod@gvasoa:/stage/oracle10g/10gR2/4547817/Disk1 $ ./runInstaller
Upgrade the database

Xxxxxxxxxxxx
Xxxxxxxxxxxxxxxxx
Xxxxxxxxxxxxxxxxxx
TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UPGRD_END 2009-06-12 20:24:32
.
Oracle Database 10.2 Upgrade Status Utility 06-12-2009 20:24:32
.
Component Status Version HH:MM:SS
Oracle Database Server VALID 10.2.0.2.0 00:08:42
JServer JAVA Virtual Machine VALID 10.2.0.2.0 00:01:56
Oracle XDK VALID 10.2.0.2.0 00:00:39
Oracle Database Java Packages VALID 10.2.0.2.0 00:00:35
Oracle Text VALID 10.2.0.2.0 00:00:16
Oracle XML Database VALID 10.2.0.2.0 00:00:47
Oracle Data Mining VALID 10.2.0.2.0 00:00:16
OLAP Analytic Workspace VALID 10.2.0.2.0 00:00:13
OLAP Catalog VALID 10.2.0.2.0 00:00:39
Oracle OLAP API VALID 10.2.0.2.0 00:00:33
Oracle interMedia VALID 10.2.0.2.0 00:04:35
Spatial VALID 10.2.0.2.0 00:00:31
Oracle Expression Filter VALID 10.2.0.2.0 00:00:10
Oracle Enterprise Manager VALID 10.2.0.2.0 00:00:38
Oracle Rule Manager VALID 10.2.0.2.0 00:00:08
.
Total Upgrade Time: 00:20:46
DOC>#######################################################################
DOC>#######################################################################
DOC>
DOC> The above PL/SQL lists the SERVER components in the upgraded
DOC> database, along with their current version and status.
DOC>
DOC> Please review the status and version columns and look for
DOC> any errors in the spool log file. If there are errors in the spool
DOC> file, or any components are not VALID or not the current version,
DOC> consult the Oracle Database Upgrade Guide for troubleshooting
DOC> recommendations.
DOC>
DOC> Next shutdown immediate, restart for normal operation, and then
DOC> run utlrp.sql to recompile any invalid application objects.
DOC>
DOC>#######################################################################
DOC>#######################################################################
DOC>#
SQL> spool off;
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup open;
ORACLE instance started.

Total System Global Area 608174080 bytes

Fixed Size 1262272 bytes
Variable Size 205524288 bytes
Database Buffers 398458880 bytes
Redo Buffers 2928640 bytes
Database mounted.
Database opened.
SQL> @/u01/SOA/app/product/10.2.0/db_1/rdbms/admin/utlrp.sql;

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN 2009-06-13 10:59:22
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END 2009-06-13 11:17:36
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#

OBJECTS WITH ERRORS

-------------------
0
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#

ERRORS DURING RECOMPILATION

---------------------------
0
SQL>

Load ORABPEL, ORAESB, ORAWSM schemas into Database

------------------------------------------------------------------------------------

cd /extracted_soa_directory/install/soa_schemas/irca

sh irca.sh (IRCA stands for Integration Repository Creation Assistance)

applprod@gvasoa:/stage/SOA/install/soa_schemas/irca $ sh irca.sh
Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database "host port serviceName" [localhost 1521 orcl]: gvasoa.xxxx.com 1521 soa.xxxx.com
Enter sys password: soasys
Running IRCA for all product(s):
connection="gvasoa.xxxxx.com 1521 soa.xxxx.com", , orabpelUser=ORABPEL, esbUser=ORAESB,
orawsmUser=ORAWSM

Validating database ...

Validating database character set ...
WARNING: The target database character set is WE8ISO8859P1
For multi-byte support, the AL32UTF8 character set is recommended.

Running prerequisite checks for ORABPEL ...

Enter password for ORABPEL: orab
Loading ORABPEL schema (this may take a few minutes) ...
Running prerequisite checks for ORAESB ...
Enter password for ORAESB:
Loading ORAESB schema (this may take a few minutes) ...
Running prerequisite checks for ORAWSM ...
Enter password for ORAWSM:
Loading ORAWSM schema (this may take a few minutes) ...

INFO: ORABPEL schema contains 225 valid objects.

INFO: ORAESB schema contains 180 valid objects.

INFO: ORAWSM schema contains 90 valid objects.

IRCA completed.
Please check for any ERROR message above and also check the log file irca2009-06-13_02-03-
14PM.log for any error or other information.

Installing the SOA component

applprod@gvasoa:/stage/SOA $ ./runInstaller
Starting Oracle Universal Installer...

Checking installer requirements...

Checking operating system version: must be redhat-Red Hat Enterprise Linux AS release 3, redhat-
Red Hat Enterprise Linux AS release 4, redhat-Red Hat Enterprise Linux ES release 3, redhat-Red Hat
Enterprise Linux ES release 4 or SuSE-9
Passed

All installer requirements met.

Checking Temp space: must be greater than 400 MB. Actual 2627 MB Passed
Checking swap space: must be greater than 512 MB. Actual 5122MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 4294967296 Passed
Checking if CPU speed is above 300 MHz. Actual 2402 MHz Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-06-13_05-42-36PM. Please
wait .
Provide database connection information (This is the database we installed and upgraded in
previous post)

on clicking next if you get error message like ORABPEL is not available on specified Oracle
Database , Make sure you executed irca.sh as mentioned above
http://gvasoa.xxxs.com:7777/em
The log file containing the details of Configuration Assistants is located in
/u01/SOA/app/product/10.2.0/ias/cfgtoollogs

Documentation

Online documentation for Oracle Application Server is available at:

http://download.oracle.com/docs/cd/B31017-01/index.htm.

In order to keep your system up-to-date we encourage you to regularly check for the latest
certification and software updates via Oracle Metalink.

Oracle Metalink (http://metalink.oracle.com) will help you get the most out of your Oracle products
by providing access to technical information and assistance from Oracle Support Services, including
information about: product availability, certification, product alerts, bug information, patches,
technical solutions, logging service requests, and more.
f you need to find more information on Oracle Integration Products please visit
(http://otn.oracle.com/products/integration)

Oracle Technology Network (http://otn.oracle.com/bpel) also provides services and resources that
developers need to build, test, and deploy applications using Oracle BPEL Process Manager.

You can access the list of ports used by the following command :
/u01/SOA/app/product/10.2.0/ias/opmn/bin/opmnctl status -l

Access the Oracle Web Services Manager through the following URL
http://gvasoa.xxxx.com:7777/ccore
Access the Oracle Business Rules Author through the following URL
http://gvasoa.xxxxx.com:7777/ruleauthor

Access the Oracle Enterprise Service Bus through the following URL
http://gvasoa.xxxx.com:7777/esb
Access the Oracle BPEL Process Manager Control through the following URL
http://gvasoa.xxxx.com:7777/BPELConsole

Please refer to the following file for a summary of this installation.

This file also contains the URLs for the various OWSM components.

Filename: owsmsetupinfo.txt
Location: /u01/SOA/app/product/10.2.0/ias/install

Geoffrey Shelton Okot

Senior Oracle Apps DBA
Geneva
Switzerland