TXT

aio-expdp

By Phillip Stewart,2014-01-28 11:16
9 views 0
aio-expdp aio-expdp aio-expdp aio-expdp

    ORA-00604,ORA-01115,ORA-01110,ORA-27091,ORA-27072,IBM AIX RISC System/6000 Error

    ×?Õß netbanker 07:06 | ??Ì?Á??ÓÍøÖ? | ×îÐÂ?Ø?? (0) | ÒýÓà (0) | oracle

    ORA-00604: error occurred at recursive SQL level 1 ORA-01115: IO error reading block from file 1 (block # 81) ORA-01110: data file 1: '/u03/oradata/rmspprd/system01.dbf' ORA-27091: skgfqio: unable to queue I/O

    ORA-27072: skgfdisp: I/O error

    IBM AIX RISC System/6000 Error: 5: I/O error

    but when checked filesystem and datafile, it is healthy and no single block of errors.

DBVERIFY - Verification complete

Total Pages Examined : 4096000

Total Pages Processed (Data) : 1691912

Total Pages Failing (Data) : 0

Total Pages Processed (Index): 2365756

Total Pages Failing (Index): 0

Total Pages Processed (Other): 19296

Total Pages Processed (Seg) : 0

Total Pages Failing (Seg) : 0

Total Pages Empty : 19036

Total Pages Marked Corrupt : 0

Total Pages Influx : 0

    Highest block SCN : 3276801276104 (762.4036196552)

    check: IO Interoperability Issue between IBM ML05 and Oracle Databases ( Note:390656.1)

    All Oracle 9i, 10gR1 and 10gR2 Database Customers running on AIX 5L V5.3 Technology Level 5 (TL 5300-05) must install an IBM AIX fix and an Oracle Database patchto bring the OS and Database environments to the correct levels. install patch: 5496862problem solved, has hit at least 10 bugs for the past 2 months using AIX is it IBM on purpose to compete with it's DB2? :-)

    ORA-27091 on AIX there can be a misconfigred AIO 2009-06-19 13:30 Purpose

    Analyze AIX IO problem. If you get ORA-27091 on AIX there can be a misconfigred AIO.

Other errors related to this problem:

ORA-01110: data file <#> : '/oracle/xyz.dbf'

    ORA-27091: skgfqio: unable to queue I/O

    ORA-27072: skgfdisp: I/O error

    IBM AIX RISC System/6000 Error: 5: I/O error

    ORA-06512: at "owner.table", line n

    ORA-01115: IO error reading block from file <#> (block # <12345>)

    For each disk are 10 AIO processes required. (use "smitty aio" at command line to get this number) Sample output of smitty:

     Change / Show Characteristics of Asynchronous I/O

Type or select values in entry fields.

    Press Enter AFTER making all desired changes.

     [Entry Fields]

     MINIMUM number of servers [80] #

     MAXIMUM number of servers per cpu [160] #

     Maximum number of REQUESTS [16384] #

     Server PRIORITY [39] #

     STATE to be configured at system restart available +

     State of fast path enable +

    The number of servers depends on # of CPU's. Use NMON for example to

    get the number of CPU's. Now you have to know the number of disks in your system. Use "lspv | wc -l" to count the number of disks.

    IBM recommends to have 10 AIO servers for each disk. On a very busy database system it is required to have more than that. System shown above had 4 CPU's and should have a maximum of 64 disks total but had 200 disks.

    You can use smitty to increase the number of servers or

chdev -l aio0 -a maxservers='m' -a minservers='n'

    ÎÒÕýÔÚÍæËѺüÎ??????ìÀ????Ø×???ÎÒ??ÁË?âÎÒµÄ×îÐÂ??Ì??É??

    ORA-01115: IO error reading block from file <file id> (block # <block number>

    ORA-01110: data file <file id>: <file name>

    ORA-27091: skgfqio: unable to queue I/O

    ORA-27072: skgfdisp: I/O error

    IBM AIX RISC System/6000 Error: 5: I/O error

- The errors are not reported in the alert log file.

    - Running dbv against datafiles from the error messages shows no errors. - All the mandatory OS patches are applied.

    - Oracle patch for Bug 5496862 - IO READING PROBLEMS AFTER INSTALLING IBM

    TECHNOLOGY LEVEL 5 (5300-05) was installed before patching the OS.

Changes

    Patch IBM Technology Level 6 (5300-06) or higher was applied to the OS.

Cause

    The value of maxreqs (4096) was too low. This asynchronous I/O parameter specifies the maximum number of asynchronous I/O requests that can be outstanding at any one time and has as default value 4096.

Solution

    Increase maxreqs to a value greater than or equal to 8192.

Steps:

    1. run aioo -a command to double check current setting for aio0 device 2. run aioo -o maxreqs=<value> to set maxreqs dynamically 3. chdev -l aio0 -a maxreqs=<value> -P to set the value of maxreqs permanently for next reboot

    4. run aioo -a to confirm change

    5. restart oracle

    NOTE: Values that fixed the errors: 8192, 16384 or 32768.

?â?ö????

    Increase maxreqs to at least 8192.

Steps:

    1. run aioo -a command to double check current setting for aio0 device 2. run aioo -o maxreqs=8192 to set maxreqs dynamically 3. chdev -l aio0 -a maxreqs=<value> to set the value of maxreqs permanently for next reboot

    4. run aioo -a to confirm change

    5. restart oracle

    QUOTE:

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

    Ô?ÌûÓÉ fay1127 ÓÚ 2010-5-17 15:40 ???í

    ORA-01115: IO error reading block from file (block # ORA-01110: data file :

    ORA-27091: skgfqio: unable to queue I/O

    ORA-27072: skgfdisp: I/O error

    IBM AIX RISC System/6000 Error: 5: I/O error

- The errors are not reported in the alert log file.

    - Running dbv against datafiles from the error messages shows no errors. - All the mandatory OS patches are applied.

    - Oracle patch for Bug 5496862 - IO READING PROBLEMS AFTER INSTALLING IBM

    TECHNOLOGY LEVEL 5 (5300-05) was installed before patching the OS.

Changes

    Patch IBM Technology Level 6 (5300-06) or higher was applied to the OS.

Cause

    The value of maxreqs (4096) was too low. This asynchronous I/O parameter

    specifies the maximum number of asynchronous I/O requests that can be outstanding at any one time and has as default value 4096.

Solution

    Increase maxreqs to a value greater than or equal to 8192.

Steps:

    1. run aioo -a command to double check current setting for aio0 device 2. run aioo -o maxreqs= to set maxreqs dynamically

    3. chdev -l aio0 -a maxreqs= -P to set the value of maxreqs permanently for next reboot

    4. run aioo -a to confirm change

    5. restart oracle

    NOTE: Values that fixed the errors: 8192, 16384 or 32768.

    ORA-27091 on AIX there can be a misconfigred AIO 2009-06-19 13:30 Purpose

    Analyze AIX IO problem. If you get ORA-27091 on AIX there can be a misconfigred AIO.

Other errors related to this problem:

ORA-01110: data file <#> : '/oracle/xyz.dbf'

    ORA-27091: skgfqio: unable to queue I/O

    ORA-27072: skgfdisp: I/O error

    IBM AIX RISC System/6000 Error: 5: I/O error

    ORA-06512: at "owner.table", line n

    ORA-01115: IO error reading block from file <#> (block # <12345>)

    For each disk are 10 AIO processes required. (use "smitty aio" at command line to get this number) Sample output of smitty:

     Change / Show Characteristics of Asynchronous I/O

Type or select values in entry fields.

    Press Enter AFTER making all desired changes.

     [Entry Fields]

     MINIMUM number of servers [80] #

     MAXIMUM number of servers per cpu [160] #

     Maximum number of REQUESTS [16384]

#

     Server PRIORITY [39] #

     STATE to be configured at system restart available +

     State of fast path enable +

    The number of servers depends on # of CPU's. Use NMON for example to get the number of CPU's. Now you have to know the number of disks in your system. Use "lspv | wc -l" to count the number of disks.

    IBM recommends to have 10 AIO servers for each disk. On a very busy database system it is required to have more than that. System shown above had 4 CPU's and should have a maximum of 64 disks total but had 200 disks.

You can use smitty to increase the number of servers or

chdev -l aio0 -a maxservers='m' -a minservers='n'

Report this document

For any questions or suggestions please email
cust-service@docsford.com