Thanks for sharing your experience.

I am using OEL5.3

Cheers!!!
Saurabh Sood

One was the need to use the “-ignoreInternalDriverError” switch in the runInstaller command (Metalink article 970166.1). This was the biggest hurdle to a smooth install.

Another problem was that you have to run the updnodelist.pl script right after the infrastructure installation completes. This is necessary to have the database software installer see the servers as belonging to a valid cluster (Bug 9190547).

I just wanted to pass those along to help other DBAs out. It’s hard to find information on these two problems. I hope this helps someone else out.

The first slideshow i.e grid Infrastructure installation lists down steps for ASM setup. Click on following link.

http://askdba.org/technical/11gr2_database_install/11gr2_grid_infra_viewlet_swf.html

cheers
Amit

As a thumb rule, set SGA_TARGET to 256mb * Number of CPU’s i.e 1024 M in your environment.
Can also set shared_pool_size to 256M so that you do not see reloads/invalidations. May be before touching these values, you can look at hard parses or reloads/invalidations in V$librarycache or your statspack/awr reports.

Regards
Amit

Thanks for your response. I just wanted you to check the variables defined like sga etc. If this is OK then I will certainly log an SR for resolution.

Regards
Vinod

I think instead of looking at alert log, you should try generating AWR/Statspack report for 30-60 mins and try to see what is consuming time in database. Also if any specific session is slow, you can trace it with 10046 event.
You can also log a SR for same and Oracle specialists can assist you in diagnosing and resolving the issue.

Regards
Amit

Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 – type 586, 2 Physical Cores
Process Affinity : 0×00000000
Memory (Avail/Total): Ph:3671M/4094M, Ph+PgF:5646M/5971M, VA:1941M/2047M
Fri Feb 05 09:32:08 2010
Starting ORACLE instance (normal)
Fri Feb 05 09:32:09 2010
Specified value of sga_max_size is too small, bumping to 612368384
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 500
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
resource_limit = TRUE
sga_max_size = 612368384
__shared_pool_size = 121634816
__large_pool_size = 50331648
__java_pool_size = 8388608
__streams_pool_size = 0
spfile = F:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILEORCL.ORA
sga_target = 612368384
control_files = F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 423624704
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = F:\oracle\product\10.2.0/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
license_max_users = 500
db_domain =
dispatchers = (protocol=TCP)
shared_servers = 10
job_queue_processes = 10
audit_file_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 300
pga_aggregate_target = 203423744
PMON started with pid=2, OS id=1100
MMAN started with pid=4, OS id=1036
PSP0 started with pid=3, OS id=296
DBW0 started with pid=5, OS id=1644
LGWR started with pid=6, OS id=1648
CKPT started with pid=7, OS id=1608
SMON started with pid=8, OS id=1588
RECO started with pid=9, OS id=1592
CJQ0 started with pid=10, OS id=1892
MMON started with pid=11, OS id=1896
MMNL started with pid=12, OS id=1956
Fri Feb 05 09:32:12 2010
starting up 1 dispatcher(s) for network address ‘(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))’…
starting up 10 shared server(s) …
Fri Feb 05 09:32:14 2010
alter database mount exclusive
Fri Feb 05 09:32:18 2010
Setting recovery target incarnation to 2
Fri Feb 05 09:32:19 2010
Successful mount of redo thread 1, with mount id 1237934366
Fri Feb 05 09:32:19 2010
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Fri Feb 05 09:32:19 2010
alter database open
Fri Feb 05 09:32:19 2010
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Fri Feb 05 09:32:20 2010
Started redo scan
Fri Feb 05 09:32:20 2010
Completed redo scan
403 redo blocks read, 113 data blocks need recovery
Fri Feb 05 09:32:20 2010
Started redo application at
Thread 1: logseq 639, block 3015
Fri Feb 05 09:32:21 2010
Recovery of Online Redo Log: Thread 1 Group 2 Seq 639 Reading mem 0
Mem# 0 errs 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
Fri Feb 05 09:32:21 2010
Completed redo application
Fri Feb 05 09:32:21 2010
Completed crash recovery at
Thread 1: logseq 639, block 3418, scn 44383502
113 data blocks read, 113 data blocks written, 403 redo blocks read
Fri Feb 05 09:32:22 2010
Thread 1 advanced to log sequence 640
Thread 1 opened at log sequence 640
Current log# 3 seq# 640 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Successful open of redo thread 1
Fri Feb 05 09:32:22 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Feb 05 09:32:22 2010
SMON: enabling cache recovery
Fri Feb 05 09:32:23 2010
Successfully onlined Undo Tablespace 1.
Fri Feb 05 09:32:23 2010
SMON: enabling tx recovery
Fri Feb 05 09:32:24 2010
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=28, OS id=3052
Fri Feb 05 09:32:30 2010
Completed: alter database open
Fri Feb 05 09:32:30 2010
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.

I am facing a lot of problems with regards to performance. The goes dead slow. Kindly suggest the changes to be done.

Thanks & Regards
Vinod