Home » RDBMS Server » Server Administration » Help! Oracle Error 27062 - AIO wait timeout
Help! Oracle Error 27062 - AIO wait timeout [message #54971] Fri, 20 December 2002 15:27 Go to next message
Tony
Messages: 190
Registered: June 2001
Senior Member
Hi,
One of our databases (size rougly 18Gigs. Used - < 10Gigs) recently went down on an AIO (Asynchronous IO ) wait timeout error (The error from the log is at the bottom). The database initially was created with 4 gigs and grew so much in few months. I looked at the Sun's documentation on this error (here's the link- Please refer to it: http://www.sun.com/solutions/blueprints/0101/SunOracle.pdf)
and found that we have to follow some standards for large databases. Could someone give me clear details on how I can go ahead and tune this database for proper IO. I'm new to such big databases. So please give me clear details. I've also pasted the initbigdb.ora file after the error. Let me know if I can change anything in that. Thanks in advance.

Error from log:

Thu Dec 19 13:42:09 2002
ARC0: Beginning to archive log# 1 seq# 3181
Thu Dec 19 13:42:09 2002
Thread 1 advanced to log sequence 3182
Thu Dec 19 13:42:09 2002
Current log# 2 seq# 3182 mem# 0: /opt/dbsdta11/sam/redo2asam.dbf
Current log# 2 seq# 3182 mem# 1: /opt/dbsdta21/sam/redo2bsam.dbf
Thu Dec 19 13:42:29 2002
ARC0: Completed archiving log# 1 seq# 3181
Thu Dec 19 14:31:27 2002
WARNING: aiowait timed out 1 times
WARNING: aiowait timed out 2 times
DBW0: terminating instance due to error 27062
Instance terminated by DBW0, pid = 600

initbigdb.ora

#
# Copyright (c) 1991, 2000 by Oracle Corporation
#
##############################################################################
# Example INIT.ORA file
#
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
#
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
#
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
#
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
#
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
#
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
#
###############################################################################

db_name = "bigdb"
db_domain = mydomain.com

instance_name = bigdb

service_names = bigdb.mydomain.com

# db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE

control_files = ("/opt/dbsdta01/bigdb/control01.ctl",
"/opt/dbsdta11/bigdb/control02.ctl")

open_cursors = 300
max_enabled_roles = 30
# db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE

db_block_buffers = 550
# db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE

shared_pool_size = 25728640
# shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE

large_pool_size = 614400
java_pool_size = 10971520
#java_pool_size = 20971520

log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800

processes = 100 # INITIAL
# processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE

log_buffer = 163840 # INITIAL
# log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE

# audit_trail = false # if you want auditing
# timed_statistics = false # if you want timed statistics
# max_dump_file_size = 10000 # limit trace file size to 5M each

# Uncommenting the lines below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
log_archive_start = true
log_archive_dest_1 = "location=/opt/Oracle_8.1.7/rdbms/log/archbigdb"
log_archive_format = arch_%t_%s.arc

# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
rollback_segments = ( R01, R02, R03, R04 )

# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/10 = 4:
# transactions = 40
# transactions_per_rollback_segment = 10

# Global Naming -- enforce that a dblink has same name as the db it connects to
# global_names = false

# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain

# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = true

# define directories to store trace and alert files
#background_dump_dest = /opt/Oracle_8.1.7/admin/sjc/bdump
#core_dump_dest = /opt/Oracle_8.1.7/admin/sjc/cdump
#Uncomment this parameter to enable resource management for your database.
#The SYSTEM_PLAN is provided by default with the database.
#Change the plan name if you have created your own resource plan.# resource_manager_plan = system_plan
# user_dump_dest = /opt/Oracle_8.1.7/admin/bigdb/udump

db_block_size = 8192

#remote_login_passwordfile = exclusive

os_authent_prefix = ""

# The following parameters are needed for the Advanced Replication Option
job_queue_processes = 4
job_queue_interval = 60
distributed_transactions = 10
open_links = 4

# mts_dispatchers = "(PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)"
# Uncomment the following line when your listener is configured for SSL
# (listener.ora and sqlnet.ora)
# mts_dispatchers = "(PROTOCOL=TCPS)(PRE=oracle.aurora.server.SGiopServer)"

compatible = "8.1.0"
sort_area_size = 65536
sort_area_retained_size = 65536
Re: Help! Oracle Error 27062 - AIO wait timeout [message #54989 is a reply to message #54971] Mon, 23 December 2002 06:23 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
add the following to the init.ora

disk_asynch_io = false
dbwr_io_slaves = any value other than 0 (as per ur need..mostly a value of 1 will do..IT JUST NEEDS TO BE A NON_ZERO value).
change the following
sort_area_size = Atleast 5 times the current value
sort_area_retained_size = sort_area_size
look into
tuning your checkpoints
Re: Help! Oracle Error 27062 - AIO wait timeout [message #54999 is a reply to message #54989] Mon, 23 December 2002 15:25 Go to previous message
Tony
Messages: 190
Registered: June 2001
Senior Member
Thank You. I'll check into this. Happy Holidays.
Previous Topic: Tables created with NOLOGGING
Next Topic: ORA-01658: unable to create INITIAL extent for segment in tablespace SYSTEM
Goto Forum:
  


Current Time: Sat Dec 28 05:01:24 CST 2024