Hi All,
I've installed db2 v8.2 on AIX 5.2 ($ oslevel -r shows 5200-06)
db2level shows the following...
DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL08020"
with level identifier "03010106".
Informational tokens are "DB2 v8.1.1.64", "s040812", "U498350", and FixPak "7".
Product is installed at "/usr/opt/db2_08_01".

When I try to start the database using db2start I'm getting the error
$ db2start
exec(): 0509-036 Cannot load program db2start because of the following errors:
0509-130 Symbol resolution failed for /usr/lib/threads/libc.a(aio.o) because:
0509-136 Symbol kaio_rdwr (number 0) is not exported from
dependent module /unix.
0509-136 Symbol listio (number 1) is not exported from
dependent module /unix.
0509-136 Symbol acancel (number 2) is not exported from
dependent module /unix.
0509-136 Symbol iosuspend (number 3) is not exported from
dependent module /unix.
0509-136 Symbol aio_nwait (number 4) is not exported from
dependent module /unix.
0509-130 Symbol resolution failed for /usr/opt/db2_08_01/lib/libdb2e.a(shr.o) because:
0509-136 Symbol aio_nwait (number 591) is not exported from
dependent module /usr/lib/threads/libc.a(aio.o).
0509-150 Dependent module libdb2e.a(shr.o) could not be loaded.
0509-026 System error: Cannot run a file that does not have a valid format.
0509-192 Examine .loader section symbols with the
'dump -Tv' command.

I saw this solution in http://www.developer.ibm.com/isv/tec...sp?oid=1:82522
Also same solution in (DB2 8.1 problem..)

The error you see was caused by AIX asynchronous I/O not being enabled. Please do the following:
1. smitty aio
2. Change / Show Characteristics of Asynchronous I/O
3. Set "STATE to be configured at system restart" to "available"
4. Apply the changes, reboot the AIX box

so when I checked the settings fof Asynchronous I/O it is already set to AVAILABLE. So may I know what else is the cause for this problem and how should i resolve the same ?

thanks,
Vij.

This is what I got from IBM db2 support.This looks same to what you already did.

Problem
The db2start command returns messages similar to the following:

exec(): 0509-036 Cannot load program db2start because of the following
errors:
0509-130 Symbol resolution failed for
/usr/lib/threads/libc.a(aio.o) because:
0509-136 Symbol kaio_rdwr (number 0) is not exported from
dependent module /unix.

Cause
The KAIO (Kernel Asynchronous I/O) is not active.

Solution
The db2start command returns messages similar to the following:
---------------------------------------------------------------------------------------
exec(): 0509-036 Cannot load program db2start because of the following
errors:
0509-130 Symbol resolution failed for
/usr/lib/threads/libc.a(aio.o) because:
0509-136 Symbol kaio_rdwr (number 0) is not exported from
dependent module /unix.
0509-136 Symbol listio (number 1) is not exported from
dependent module /unix.
0509-136 Symbol acancel (number 2) is not exported from
dependent module /unix.
0509-136 Symbol iosuspend (number 3) is not exported from
dependent module /unix.
0509-136 Symbol aio_nwait (number 4) is not exported from
dependent module /unix.
0509-130 Symbol resolution failed for
/usr/opt/db2_08_01/lib/libdb2e.a(shr.o) because:
0509-136 Symbol aio_nwait (number 416) is not exported from
dependent module /usr/lib/threads/libc.a(aio.o).
0509-192 Examine .loader section symbols with the
'dump -Tv' command.
-----------------------------------------------------------------------------------------

First, confirm that the KAIO is installed:

#lslpp -l |grep -i async

You should see output similar to the following:

bos.rte.aio 5.1.0.35 COMMITTED Asynchronous I/O
Extension devices.common.IBM.async.diag
bos.rte.aio 5.1.0.10 COMMITTED Asynchronous I/O
Extension

Next, to activate the KAIO, perform the following steps using SMIT
(Syatem Management Interface Tool):

1. $ smitty chgaio

2. From the menu, select "STATE to be configured at system restart"

3. Change the value for this option to "available" and then press enter

4. To exit SMIT, press the F10 key

5. Reboot the system

After the reboot, db2start should be successful.

regards,

mujeeb