error in db2diag.log and crash

db2aix · #1 (**permalink**) 09-09-09, 14:51

We have DB2 v8.2 on AIX. Getting following error in the db2diag.log and the instance comes down.

FUNCTION: DB2 UDB, oper system services, sqloseekwrite64, probe:40
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
CALLED : OS, -, unspecified_system_function
OSERR : EFBIG (27) "File too large"

Has anyone encountered this error before?

n_i · #2 (**permalink**) 09-09-09, 15:02

IBM - Configuring fsize for Large File Support

db2aix · #3 (**permalink**) 09-09-09, 17:43

I checked this link. Our filesystem is JFS2 and ulimit is unlimitted.

n_i · #4 (**permalink**) 09-09-09, 18:53

Quote:

Originally Posted by db2aix

I checked this link. Our filesystem is JFS2 and ulimit is unlimitted.

...and it was created with large file support, right?

db2aix · #5 (**permalink**) 09-10-09, 10:30

According to our AIX SA, large file support is for JFS only. JFS2 don't need this to be set.

stolze · #6 (**permalink**) 09-10-09, 12:58

Do you see some more information on the specific file that shall be accessed? Maybe it is for log files and not data containers or something else altogether?

db2aix · #7 (**permalink**) 09-10-09, 13:32

db2diag.log doesn't show the specific file name. This is what I see after EFBIG error:

CALLED : OS, -, unspecified_system_function
OSERR : EFBIG (27) "File too large"
DATA #1 : Device number, 8 bytes
9223372221538369537
DATA #2 : Inode number, 8 bytes
611
DATA #3 : File mode, 4 bytes
33152
DATA #4 : User id, 4 bytes
5100
DATA #5 : User id, 4 bytes
5100
DATA #6 : File size, 8 bytes
63963136000
DATA #7 : soft file resource limit, 8 bytes
1073741312
DATA #8 : hard file resource limit, 8 bytes
1073741312

I'll increase the diaglevel.

n_i · #8 (**permalink**) 09-10-09, 13:38

Quote:

Originally Posted by db2aix

DATA #4 : User id, 4 bytes
5100
DATA #5 : User id, 4 bytes
5100
DATA #6 : File size, 8 bytes
63963136000
DATA #7 : soft file resource limit, 8 bytes
1073741312
DATA #8 : hard file resource limit, 8 bytes
1073741312

I think the above tells you everything you need to know.

The ulimit does not seem to be "unlimited", after all.

db2girl · #9 (**permalink**) 09-10-09, 14:12

ulimit may be set to unlimited but that is not what was in effect when the error occured. Please check the following technote:
IBM - Why are the instance owner ulimits ignored when the instance is started with the DB2 fault monitor?

Internet Services

Web Development

Digital Marketing

Consumer Tech