How to increase the number of JVM and required memory in 11i/R12

How to increase the number of  oacore process type(JVM) and required memory in R12

Name of the file: opmn.xml
Location in R12:$INST_TOP/apps/SID_HOSTNAME/ora/10.1.3/opmn/conf/opmn.xml

1. To increase number of  oacore process type (JVM) in R12.

Go to $INST_TOP/apps/SID_HOSTNAME/ora/10.1.3/opmn/conf/

Take a backup of opmn.xml file before editing,

A)Open the opmn.xml file and go to line no-128 and increase

numprocs=4

2. How to increase the JVM Memory in R12:
   
   

To increase the memory for JVM.

In the same file go to line no-114

FROM:-server -verbose:gc -Xmx512M -Xms128M -XX:MaxPermSize=160M - XX:NewRatio=2
-XX:+PrintGCTimeStamps

Example :

to increase set :
Xms128M to Xms512M = Memory allocated upfront to the JVM
Xmx512M to Xmx1024M = Maximum Memory allocated to the JVM

TO:
server -verbose:gc –Xmx1024M -Xms256M -XX:MaxPermSize=256M -XX:NewRatio=2
-XX:+PrintGC

How to increase the number of JVMs in 11i

You can edit the xml file and make the change as follows to increase (earlier 1 - now 2)the oacore JVMs and then run autoconfig :

<oacore_nprocs oa_var="s_oacore_nprocs">2</oacore_nprocs>

Set the number of jvm as required and run autoconfig .

This will affect the jserv.conf (following line)

ApJServGroup OACoreGroup 1 1 /u03/oracle/prodora/iAS/Apache/Jserv/etc/jserv.properties


Alternatively : Manually increase the number of JVMs in $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.conf
and bounce Apache

How to increase the JVM Memory in 11i:

To increase the memory for oacore JVM, edit the file $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties

wrapper.bin.parameters=-verbose:gc -Xmx512M -Xms128M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB
to
wrapper.bin.parameters=-verbose:gc -Xmx1024M -Xms512M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB


- We normally allocate 2 or 4 jvms - We do not allocate 10 / 15


Example - refer to : oc4j_socket_recvfull-timed-out-Connect-failed

RDBMS Upgrade : 10.2.0.4 to 11.2.0.2

nitiserver[oracle]_test> mkdir -p /nitiserver/dba01/oracle/test/upgrade11gR2

nitiserver[oracle]_test> cp /nitiserver/testdb/oracle/product/11.2.0.2/rdbms/admin/utlu112i.sql $ORACLE_HOME/test/upgrade11gR2

nitiserver[oracle]_test> cd  $ORACLE_HOME/test/upgrade11gR2

nitiserver[oracle]_test> pwd
/nitiserver/dba01/oracle/test/upgrade11gR2

nitiserver[oracle]_test> ls -ltr
total 204
-rw-r--r--  1 oracle dba 204205 Apr 15 03:43 utlu112i.sql

nitiserver[oracle]_test> sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 15 03:43:48 2012
Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining Scoring Engine and Real Application Testing options
SQL> spool upgrade_info.log
SQL> @utlu112i.sql

Oracle Database 11.2 Pre-Upgrade Information Tool 04-15-2012 03:44:22
Script Version: 11.2.0.2.0 Build: 001
.
**********************************************************************
Database:
**********************************************************************
--> name:          test
--> version:       10.2.0.4.0
--> compatible:    10.2.0.2.0
--> blocksize:     8192
--> platform:      Linux IA (32-bit)
--> timezone file: V4
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 389 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 211 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 318 MB
.
**********************************************************************
Flashback: OFF
**********************************************************************
**********************************************************************
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 32-bit database.
**********************************************************************
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
WARNING: --> "shared_pool_size" needs to be increased to at least 236 MB
.
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB
.
**********************************************************************
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No renamed parameters found. No changes are required.
.
**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
--> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"
--> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"
.
**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> Oracle Catalog Views         [upgrade]  VALID
--> Oracle Packages and Types    [upgrade]  VALID
--> OLAP Analytic Workspace      [upgrade]  VALID
--> Oracle OLAP API              [upgrade]  VALID
.
**********************************************************************
Miscellaneous Warnings
**********************************************************************
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 10.2.0.4.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER testBA has 2 INVALID objects.
.... USER SYSTEM has 11 INVALID objects.
.... USER testBAPRD has 27 INVALID objects.
.... USER SYS has 2 INVALID objects.
.
**********************************************************************
Recommendations
**********************************************************************
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
    EXECUTE dbms_stats.gather_dictionary_stats;
**********************************************************************
Oracle recommends reviewing any defined events prior to upgrading.
To view existing non-default events execute the following commands
while connected AS SYSDBA:
  Events:
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
      WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'
  Trace Events:
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
      WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'
Changes will need to be made in the init.ora or spfile.
**********************************************************************


SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql

SQL> SHUTDOWN IMMEDIATE


#############################################################################

cd /nitiserver/oracle/bin
cp test_11202 test

nitiserver[oracle]_test> vi /etc/oratab
# This file is used by ORACLE utilities.  It is created by root.sh
# and updated by the Database Configuration Assistant when creating
# a database.
# A colon, ':', is used as the field terminator.  A new line terminates
# the entry.  Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
#   $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home
# directory of the database respectively.  The third filed indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#test:/nitiserver/testdb/oracle/product/test_10.2.0.4:N
test:/nitiserver/testdb/oracle/product/11.2.0.2:N

######################################################################################
nitiserver[oracle]_test> cat /etc/oraInst.loc

#inventory_loc=/nitiserver/testdb/oracle/product/test_10.2.0.4/oraInventory
inventory_loc=/nitiserver/testdb/oracle/product/11.2.0.2/oraInventory
inst_group=dba
############################################################################################
Change the init paramete
diagnostic_dest=/nitiserver/dump01/oracle/test/bdump
diagnostic_dest=/nitiserver/dump01/oracle/test/udump
core_dump_dest=/nitiserver/dump01/oracle/test/cdump

compatible=11.2.0.2.0
shared_pool_size=263402291

##############################################################################################

nitiserver[oracle]_test> ln -s $SID_HOME/pfile/init$ORACLE_SID.ora $ORACLE_HOME/dbs/init$ORACLE_SID.ora

nitiserver[oracle]_test> ls -ltr $ORACLE_HOME/dbs/
total 4
-rw-r--r--  1 oracle dba 2851 May 15  2009 init.ora
lrwxrwxrwx  1 oracle dba   50 Apr 15 04:37 inittest.ora -> /nitiserver/dba01/oracle/test/pfile/inittest.ora

nitiserver[oracle]_test> cd $SID_HOME/upgrade11gR2
nitiserver[oracle]_test> pwd
/nitiserver/dba01/oracle/test/upgrade11gR2

SQL> STARTUP UPGRADE;
ORA-00371: not enough shared pool memory, should be atleast 263402291 bytes
#################################################################################################
[oracle@nitiserver ~]$ sqlplus
SQL*Plus: Release 11.2.0.2.0 Production on Fri Apr 15 06:36:42 2012
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Enter user-name: / as sysdba
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> !echo $ORACLE_SID
test
SQL> STARTUP UPGRADE;

ORACLE instance started.
Total System Global Area  481275904 bytes
Fixed Size                  1344952 bytes
Variable Size             339741256 bytes
Database Buffers          134217728 bytes
Redo Buffers                5971968 bytes
Database mounted.
Database opened.
SQL> SET SERVEROUTPUT ON
SQL> purge dba_recyclebin;
DBA Recyclebin purged.
SQL> TRUNCATE TABLE SYS.DST$TRIGGER_TABLE;
Table truncated.
SQL> TRUNCATE TABLE SYS.DST$AFFECTED_TABLES;
Table truncated.
SQL> TRUNCATE TABLE SYS.DST$ERROR_TABLE;
Table truncated.
SQL> EXEC DBMS_DST.BEGIN_UPGRADE(11);
An upgrade window has been successfully started.
PL/SQL procedure successfully completed.
SQL> column PROPERTY_NAME format a30
column VALUE format a30
SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;
SQL> SQL>   2    3    4
PROPERTY_NAME                  VALUE
------------------------------ ------------------------------
DST_PRIMARY_TT_VERSION         11
DST_SECONDARY_TT_VERSION       4
DST_UPGRADE_STATE              UPGRADE
SQL> EXEC DBMS_DST.BEGIN_UPGRADE(14);
BEGIN DBMS_DST.BEGIN_UPGRADE(14); END;
*
ERROR at line 1:
ORA-56920: a prepare or upgrade window or an on-demand or datapump-job loading
of a secondary time zone data file is in an active state
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.DBMS_DST", line 1158
ORA-06512: at line 1

SQL> SELECT OWNER, TABLE_NAME, UPGRADE_IN_PROGRESS
  FROM ALL_TSTZ_TABLES
 WHERE UPGRADE_IN_PROGRESS='YES';
  2    3
no rows selected
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP
ORACLE instance started.
Total System Global Area  481275904 bytes
Fixed Size                  1344952 bytes
Variable Size             339741256 bytes
Database Buffers          134217728 bytes
Redo Buffers                5971968 bytes
Database mounted.
Database opened.
SQL> set serveroutput on
VAR numfail number
BEGIN
SQL> SQL>   2  DBMS_DST.UPGRADE_DATABASE(:numfail,
  3  parallel => TRUE,
  4  log_errors => TRUE,
  5  log_errors_table => 'SYS.DST$ERROR_TABLE',
  6  log_triggers_table => 'SYS.DST$TRIGGER_TABLE',
  7  error_on_overlap_time => FALSE,
  8  error_on_nonexisting_time => FALSE);
  9  DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail);
 10  END;
 11  /
Failures:0
PL/SQL procedure successfully completed.
SQL> VAR fail number
BEGIN
DBMS_DST.END_UPGRADE(:fail);
DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail);
END;
SQL>   2    3    4    5
  6  ;
  7
  8  /
;
*
ERROR at line 6:
ORA-06550: line 6, column 1:
PLS-00103: Encountered the symbol ";"

SQL>  VAR fail number
BEGIN
DBMS_DST.END_UPGRADE(:fail);
DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail);
END;
SQL>   2    3    4    5  /
An upgrade window has been successfully ended.
Failures:0
PL/SQL procedure successfully completed.
SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;
SELECT * FROM v$timezone_file;
  2    3    4
PROPERTY_NAME                  VALUE
------------------------------ ------------------------------
DST_PRIMARY_TT_VERSION         11
DST_SECONDARY_TT_VERSION       0
DST_UPGRADE_STATE              NONE
SQL> SQL>
FILENAME                VERSION
-------------------- ----------
timezlrg_11.dat              11
SQL> EXEC DBMS_DST.BEGIN_UPGRADE(14);
BEGIN DBMS_DST.BEGIN_UPGRADE(14); END;
*
ERROR at line 1:
ORA-56926: database must be in UPGRADE mode in order to start an upgrade window
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.DBMS_DST", line 1195
ORA-06512: at line 1

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> SQL> startup
ORACLE instance started.
Total System Global Area  481275904 bytes
Fixed Size                  1344952 bytes
Variable Size             339741256 bytes
Database Buffers          134217728 bytes
Redo Buffers                5971968 bytes
Database mounted.
Database opened.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> SQL> startup
ORACLE instance started.
Total System Global Area  481275904 bytes
Fixed Size                  1344952 bytes
Variable Size             339741256 bytes
Database Buffers          134217728 bytes
Redo Buffers                5971968 bytes
Database mounted.
Database opened.
SQL> SELECT comp_name, version, status FROM dba_registry;
COMP_NAME
--------------------------------------------------------------------------------
VERSION                        STATUS
------------------------------ -----------
Oracle Database Catalog Views
11.2.0.2.0                     VALID
Oracle Database Packages and Types
11.2.0.2.0                     VALID
OLAP Analytic Workspace
11.2.0.2.0                     VALID

COMP_NAME
--------------------------------------------------------------------------------
VERSION                        STATUS
------------------------------ -----------
Oracle OLAP API
11.2.0.2.0                     VALID


SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP UPGRADE;
ORACLE instance started.
Total System Global Area  481275904 bytes
Fixed Size                  1344952 bytes
Variable Size             339741256 bytes
Database Buffers          134217728 bytes
Redo Buffers                5971968 bytes
Database mounted.
Database opened.
SQL> purge dba_recyclebin;
DBA Recyclebin purged.
SQL> TRUNCATE TABLE SYS.DST$TRIGGER_TABLE;
Table truncated.
SQL> TRUNCATE TABLE SYS.DST$AFFECTED_TABLES;
Table truncated.
SQL> TRUNCATE TABLE SYS.DST$ERROR_TABLE;
Table truncated.
SQL> EXEC DBMS_DST.BEGIN_UPGRADE(14);
PL/SQL procedure successfully completed.
SQL> column PROPERTY_NAME format a30
column VALUE format a30
SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;
SQL> SQL>   2    3    4
PROPERTY_NAME                  VALUE
------------------------------ ------------------------------
DST_PRIMARY_TT_VERSION         14
DST_SECONDARY_TT_VERSION       11
DST_UPGRADE_STATE              UPGRADE
SQL> SQL> SELECT OWNER, TABLE_NAME, UPGRADE_IN_PROGRESS
  FROM ALL_TSTZ_TABLES
 WHERE UPGRADE_IN_PROGRESS='YES';
  2    3
no rows selected
SQL> SHUTDOWN IMMEDIATE
startup
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> ORACLE instance started.
Total System Global Area  481275904 bytes
Fixed Size                  1344952 bytes
Variable Size             339741256 bytes
Database Buffers          134217728 bytes
Redo Buffers                5971968 bytes
Database mounted.
Database opened.
SQL> set serveroutput on
VAR numfail number
BEGIN
SQL> SQL>   2  DBMS_DST.UPGRADE_DATABASE(:numfail,
  3  parallel => TRUE,
  4  log_errors => TRUE,
  5  log_errors_table => 'SYS.DST$ERROR_TABLE',
  6  log_triggers_table => 'SYS.DST$TRIGGER_TABLE',
  7  error_on_overlap_time => FALSE,
  8  error_on_nonexisting_time => FALSE);
  9  DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail);
 10  END;
 11  /
Failures:0
PL/SQL procedure successfully completed.
SQL> VAR fail number
BEGIN
DBMS_DST.END_UPGRADE(:fail);
DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail);
END;
/
SQL>   2    3    4    5  An upgrade window has been successfully ended.
Failures:0
PL/SQL procedure successfully completed.
SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;
  2    3    4
PROPERTY_NAME                  VALUE
------------------------------ ------------------------------
DST_PRIMARY_TT_VERSION         14
DST_SECONDARY_TT_VERSION       0
DST_UPGRADE_STATE              NONE
SQL> SQL> SELECT * FROM v$timezone_file;
FILENAME                VERSION
-------------------- ----------
timezlrg_14.dat              14

#################################################################################################

COMP_NAME                                     VERSION                        STATUS
--------------------------------------------- ------------------------------ -----------
Oracle Database Catalog Views                 11.2.0.2.0                     VALID
Oracle Database Packages and Types            11.2.0.2.0                     VALID
OLAP Analytic Workspace                       11.2.0.2.0                     VALID
Oracle OLAP API                               11.2.0.2.0                     VALID

###################################################################################################

LSNRCTL> start LSTNtest
Starting /nitiserver/testdb/oracle/product/11.2.0.2/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 11.2.0.2.0 - Production
System parameter file is /nitiserver/testdb/oracle/product/11.2.0.2/network/admin/test_nitiserver/listener.ora
Log messages written to /nitiserver/testdb/oracle/product/11.2.0.2/log/diag/tnslsnr/nitiserver/lstntest/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nitiserver)(PORT=1599)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=nitiserver)(PORT=1599)))
STATUS of the LISTENER
------------------------
Alias                     LSTNtest
Version                   TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date                15-APR-2012 05:37:37
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      ON
Listener Parameter File   /nitiserver/testdb/oracle/product/11.2.0.2/network/admin/test_nitiserver/listener.ora
Listener Log File         /nitiserver/testdb/oracle/product/11.2.0.2/log/diag/tnslsnr/nitiserver/lstntest/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nitiserver)(PORT=1599)))
Services Summary...
Service "test." has 1 instance(s).
  Instance "test", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
########################################################################################################

[oracle@nitiserver test_nitiserver]$ tnsping test
TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 15-APR-2012 05:38:30
Copyright (c) 1997, 2010, Oracle.  All rights reserved.
Used parameter files:

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = ( ADDRESS = (PROTOCOL = TCP) ( HOST = nitiserver)(PORT = 1599)) ( CONNECT_DATA = ( SID = test)))
OK (0 msec)

############################################################################################


 

Oracle 11g : Real Application Testing ( RAT )

As per my understanding  RAT is same like Metric Baseline or Database Replay feature which we had discussed in OEM12c presentation  and it is like a  recorder, allowing workload to be captured and replayed for testing and benchmarking purposes.  RAT captures transactions against the Oracle database (as made by an application) and allows them to be easily tested. 

·         RAT Includes:

1.        Database Replay

2.        SQL Performance Analyzer

·         Database Replay

§  Captures database workload on production system

§  Replays captured workload on test system

§  Optionally includes concurrency and timing characteristics

§  Generates reports and recommends changes

·         SQL Performance Analyzer

§  Identifies performance divergence between workloads on source and target platforms

§  Generates tuning recommendations

Capture Workload

1.        Create an operating system directory

                                   [oracle@nitiserver]$ mkdir -p /cfspshr/backup/oracle/testp/oracle/testp1/rat

2.        Create an Oracle directory

SQL> CREATE DIRECTORY dir1 AS ‘/cfspshr/backup/oracle/testp/oracle/testp1/rat';

Directory created.

3.        Start the capture process

BEGIN

  DBMS_WORKLOAD_CAPTURE.START_CAPTURE (name => 'May12_Peak',

                           dir => 'RAT',

                           duration => 600);

END;

/

PL/SQL procedure successfully completed.

4.        Run the workload - Do some random works and transactions etc. Finish the capture process

SQL> BEGIN dbms_workload_capture.finish_capture; END;

  2  /

PL/SQL procedure successfully completed.

OEM Method :

Database Replay Database Replay allows workloads to be captured from production systems and re-executed with high fidelity on test copies of production databases. This enables detailed analysis of how the proposed changes may affect production systems; for instance, patching or upgrading database software. Page Refreshed May 21, 2012 6:24:36 AM EDT

Task List Expand All | Collapse All Task Name Description Go to Task Capture Production Workload Initiate or schedule a workload capture, export AWR data after capture, and copy captured files to the workload staging area. Capture Workload Capture a workload from the production environment. This can be scheduled to accommodate a database restart if desired. Export AWR Data Export AWR data to provide a better performance comparison between captured and replayed workloads. Copy to Workload Staging Area Copy captured files away from production to the workload staging area for later preprocessing. For a cluster database, captured files from different database instances can be consolidated in the workload staging area. Prepare Test Database Set up a test database from production, upgrade or otherwise modify the test database, and isolate the test database prior to replay. Set Up Test Database Clone the production database to a test environment. The test database should be restored to match the capture database at the start of capture. You may make any changes to the test environment as needed. Isolate Test Database Isolate the test system from production environment prior to the workload replay. This task must be performed on the test database target. Prepare for Replay Prepare the workload capture files for replay (preprocess), copy the preprocessed workload files to the workload staging area, deploy the Replay Clients, and copy the preprocessed workload files to the Replay Client hosts. Preprocess Workload Preprocessing prepares a captured workload for replay. You must do this once for every captured workload. Preprocessing is best performed in the test database. The captured workload must be accessible from the test database. Copy to Workload Staging Area Copy preprocessed workload files to the workload staging area. The preprocessed workload files must be accessible by the database server and the Replay Clients during replay. Deploy Replay Clients Deploy the Replay Client to one or more host machines. Replay Clients are used to replay the preprocessed workload. Copy Workload to Replay Client Hosts Copy the preprocessed workload to one or more Replay Client host machines. Each Replay Client must be able to access the preprocessed workload during replay. Replay Workload on Test Database Set up the workload replay on the test database, copy the replay results to the workload staging area, and analyze the results. Replay Workload Replay the preprocessed workload on a test copy of the production database. Copy to Workload Staging Area Copy replay results to the workload staging area for comparision analysis with future replays. Analyze Results Analyze the effects of changes on workload performance.

In a sense, RAT has many of the same features as the Quest "Benchmark Factory" product.

E-Business Suite 12.2

There are lots of updates coming in this release, but from a technology stack perspective, EBS 12.2 will be notable for two things:

1.               Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g

2.               Online Patching support via 11gR2 Edition-Based Redefinition

Native Technology Stack Installation

• Now tech. stack has better integration with Oracle Universal Installer

• Another big one. Yes, Faster Technology Stack Installation. At least 25% much faster.

• Silent-mode calls to install and configure Oracle Database 11.2, WebLogic Server (WLS) and Oracle HTTP Server (OHS)

• AutoConfig is tightly integrated with native technology stack installation

Database RMAN Restore

• Simplifies Integration with Grid Infrastructure.

• Seamless integration with different storage methods (OCFS2, NFS, etc)

• Faster integration with Automatic Storage Management (ASM)

Dual File System

• A must needed feaure,  dual file system capability is instrumental for 12.2’s Online Patching feature that allows users to continue using the application while patching.

• Dual File System allows replacing files with minimum downtime that leads to improved High Availability

Dual Port Configuration

As part of online patching feature, Oracle requires DPC (Dual Port Configuration)

• Dual Port Pool configuration

• Easier port assignments

• Allows port customization in run-time and patching file systems

Optional 11g Home for Upgrades

I always wonder why we can’t simply try to use an existing Oracle home during configuration. Well, Oracle incorporated this capability in 12.2.

• Allow integration with an existing 11gR2 Oracle Home

• Simplified Technology Stack Upgrade

• Reduced Upgrade time

WebLogic Server Features

As middleware technology stack is based on the new improved Weblogic that has atleast the following key capabilities to help manage the EBS environment better. As WLST 11gR2 is what is slated to get bundled with 12.2, its interesting to know if Oracle will WLST 12c into the mix over 11gR2

• WebLogic Scripting Tool (WLST)

• High Availability & Failover

• Consolidated Administration, Configuration and Deployment

• Enhanced Monitoring & Messaging via centralized service administration.

• Troubleshooting framework

• Integration with OAM

• WLS-Specific configuration setups

• Proactive Management via Server & Performance Monitoring

• Easier Problem Solving & Performance Tuning

• Better resource planning via historical reporting

 Online Patching

In 12.2 all patching operations are online. In other words, Oracle E‐Business Suite will remain available to users during patching operations.  EBS 12.2 will take advantage of 11gR2 Database’s Edition-Based Redefinitionfeatures to provide support for Online Patching.  Edition-Based Redefinition enables you to upgrade the database component of an application while it is in use, thereby minimizing or eliminating down time.

• Downtime will be measured in minutes not hours or days

• Downtime windows will be very predictable

• Patches are applied while the Production Application remains online

• Allows an application to efficiently store multiple editions of its Application Definition in the same database

• Provides an isolation mechanism (The Edition) that allows pre-upgrade and post-upgrade schemas to co-exist

• Client code chooses the particular “Edition” that it wants to connect to.

Refrences :

Steven ChanSunthar Tharmalingam

ORA-12838: cannot read/modify an object after modifying it in parallel

Cause:	Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted.
Action:	Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation.

Oracle 11g : ADRCI

Allows interaction with ADR from OS prompt

• Can invoke IPS with command line instead of EM
• DBAs should use EM Support Workbench:
• Leverages same toolkit/libraries that ADRCI is built upon
• Easy to follow GUI

 ADRCI> show incident

ADR Home = /u01/app/oracle/product/11.1.0/db_1/log/diag/rdbms/test/test:

****************************************************************************************

INCIDENT_ID PROBLEM_KEY CREATE_TIME

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

1681 ORA-600_dbgris01:1,_addr=0xa9876541 17-May-12 09.17.44.843125000

 1682 ORA-600_dbgris01:12,_addr=0xa9876542 18-May-12 09.18.59.434775000

 2 incident info records fetched

ADRCI>

SQL> SELECT * FROM V$DIAG_INFO;

NAME VALUE

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

Diag Enabled TRUE

ADR Base /u01/app/oracle

ADR Home /u01/app/oracle/diag/rdbms/test/test

Diag Trace /u01/app/oracle/diag/rdbms/test/test/trace

Diag Alert /u01/app/oracle/diag/rdbms/test/test/alert

Diag Incident /u01/app/oracle/diag/rdbms/test/test/incident

Diag Cdump /u01/app/oracle/diag/rdbms/test/test/cdump

Health Monitor /u01/app/oracle/diag/rdbms/test/test/hm

Default Trace File /u01/app/oracle/diag/rdbms/test/test/trace/orcl_ora_11424.trc

Active Problem Count 3

Active Incident Count 8

adrci>>show alert -tail

ADR Home = /u01/app/oracle/diag/rdbms/test/test:

*************************************************************************

2007-04-16 22:10:50.756000 -07:00

ORA-1654: unable to extend index SYS.I_H_OBJ#_COL# by 128 in tablespace

SYSTEM

2007-04-16 22:21:20.920000 -07:00

Thread 1 advanced to log sequence 400

Current log# 3 seq# 400 mem# 0: +DATA/orcl/onlinelog/group_3.266.618805031

Current log# 3 seq# 400 mem# 1: +DATA/orcl/onlinelog/group_3.267.618805047

Thread 1 advanced to log sequence 401

Current log# 1 seq# 401 mem# 0: +DATA/orcl/onlinelog/group_1.262.618804977

Current log# 1 seq# 401 mem# 1: +DATA/orcl/onlinelog/group_1.263.618804993

DIA-48223: Interrupt Requested - Fetch Aborted - Return Code [1]

adrci>>

adrci>>SHOW ALERT -P "MESSAGE_TEXT LIKE '%ORA-600%'"

ADR Home = /u01/app/oracle/diag/rdbms/test/test:

*************************************************************************