Using a FIFO file with db2 can result in a
0x870F0002=-2029060094=SQLO_BPSE "Debug logic error detected"
error being reported. This is a misleading error as on AIX we
should NOT try and lock a FIFI file, as it is expected to get a
error when we try.
This occur even after the follow APAR has been addressed:
IC87160: EXPORT TO PIPE MAY FAIL WITH ERROR SQL3001C
db2diag.log:
2014-05-20-11.00.17.933138+060 E4560A1297 LEVEL: Error
(OS)
PID : 30736556 TID : 1 PROC : db2bp
INSTANCE: db2insta NODE : 000 DB :
SAMPLE
APPID : *N0.db2insta.140520100017
HOSTNAME: cromarty
EDUID : 1
FUNCTION: DB2 UDB, oper system services, sqloflock, probe:100
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic
error detected"
DIA8501C A buffer pool logic error has occurred.
CALLED : OS, -, fcntl
OSERR : EINVAL (22) "A system call received a parameter that
is not valid."
DATA #1 : Codepath, 8 bytes
1:7
DATA #2 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes
File Handle = 5
File System Block Size = 0 bytes
File System Type = UNKNOWN
File Handle Flags :
Require Sector Align = No
DIO/CIO Mode = No
Raw Block Device = No
Reserved Handle = No
Flush On Close = Yes
Thread-Level Lock = No
Write-through Mode = No
File Not Tracked = No
DATA #3 : Hex integer, 1 bytes
0x01
DATA #4 : Hex integer, 1 bytes
0x03
DATA #5 : unsigned integer, 8 bytes
0
DATA #6 : String, 105 bytes
Search for ossError*Analysis probe point after this log entry
for further
self-diagnosis of this problem.
REPRODUCTION:
TIME=$(date +%Y_%m_%d_%H_%M_%S);export TIME
mkfifo export_out.$$
cat export_out.$$ | gzip -c > STAFF.$TIME.unl.gz &
db2 connect to SAMPLE
db2 -x export to export_out.$$ of del select \* from
$USER.STAFF with ur
rm export_out.$$ |
