DB2 commands encounter 0x83000299 mapping to OS Error 0x299 = 665 while writing data to media
While running any commands in DB2 which are responsible for writing data to media users might encounter below errors :
SQL2025N An I/O error occurred. Error code: code. Media on which this error occurred: dir_or_devices.
SQL2024N The utility encountered an I/O error code while accessing the file type file-type.
Error messages returned to application and in db2diag.log
The RC 0x83000299 maps to OS Error 0x299 = 665 which suggests that the operation could not continue due to a file system limitation.
Diagnosing the problem
In the db2diag.log, there will be more information related to the SQL2025N or SQL2024N error codes. It will contain something similar to following :
yyyy-mm-dd-mm.ss.ms.+ t LEVEL: Severe
PID : 1028 TID : 2468 PROC : db2syscs.exe
INSTANCE: db2_instance_name NODE : 000
EDUID : 2468 EDUNAME: db2pfchr (db name) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndWrite, probe:4154
MESSAGE : ZRC=0x83000299=-2097151335
Checking the ZRC :
$ db2diag -rc -2097151335
Input ZRC string '-2097151335' parsed as 0x83000299 (-2097151335).
ZRC value to map: 0x83000299 (-2097151335)
V7 Equivalent ZRC value: 0xFFFFB299 (-19815)
ZRC class :
Unexpected Operating System error (Class Index: 3)
Unknown component (Component Index: 0)
Undefined as of DB2 v188.8.131.52; s120629
Operating system reason code (errno):
0x00000299 (665) = Error 665 occurred.
NOTE: Errno value 665 is excessively large.
It is possible that this error code is not a ZRC value.
This directly maps to OS error 0x299 == 665 ERROR_FILE_SYSTEM_LIMITATION
665 (0x299) : The requested operation could not be completed due to a file system
Hence, it is the OS, which fails to complete the DB2 write request to the media due to the above file limitation error and thus, DB2 fails with error codes SQL2025N and/or SQL2024N.
Resolving the problem
Please refer to IBM Information center for error codes SQL2025N and/or SQL2024N.
There are several Microsoft technotes, which provide information for this type of problem, here are a couple of them :
If users still get the same error after applying the proposed Microsoft patches, please engage Microsoft support to further assist on finding the root cause.