(Opening defect in v10.5 fp9 since there is no v9.7 family
available)
1. Problem description
After upgrade from AIX 6.1 to AIX 7.1, Db2 stored procedure
fails with following error in db2diag.log (see below)
sudo -nu $DB2INSTANCE db2 -v "call
ifta.if9000p('IF0090P','NYS',?,?,?)"
call ifta.if9000p('IF0090P','NYS',?,?,?)
SQL1131N Stored procedure process has been terminated
abnormally.
SQLSTATE=38503
(from Db2 CLP)
Database Connection Information
Database server = DB2/AIX64 9.7.7
SQL authorization ID = DB2D
Local database alias = IFTADVM
call ifta.if9000p('IF0090P','NYS',?,?,?)
SQL1131N Stored procedure process has been terminated
abnormally.
SQLSTATE=38503
2. Operating system and level:
(from Benny)
On AIX 6.1 6100-07-08-1339 I am not seeing a problem.
However on AIX 7.1 7100-03-05-1524 I do get the same SEGV the
customer was seeing.
3. Client, server, and gateway information
5. Diagnostic information
2017-12-07-16.34.10.632181-300 E8793A828 LEVEL: Error
(OS)
PID : 20578458 TID : 1 PROC : db2fmp
(3600) 0
INSTANCE: db2d NODE : 000 DB : IFTADVM
APPID : *LOCAL.db2d.171207213408
EDUID : 1 EDUNAME: db2fmp (3600) 0
FUNCTION: DB2 UDB, oper system services,
sqloAIXLoadModuleTryShr, probe:130
CALLED : OS, -, dlopen
OSERR : ENOEXEC (8) "Cannot run a file that does not have a
valid format."
MESSAGE : Attempt to load specified library failed.
DATA #1 : Library name or path, 26 bytes
/dvm/ifta/function/IF9000P
DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
65538
DATA #3 : String, 133 bytes
0509-022 Cannot load module /dvm/ifta/function/IF9000P.
0509-026 System error: Cannot run a file that does not
have a valid format.
2017-12-07-16.34.10.720591-300 E9622A983 LEVEL: Error
(OS)
PID : 20578458 TID : 1 PROC : db2fmp
(3600) 0
INSTANCE: db2d NODE : 000 DB : IFTADVM
APPID : *LOCAL.db2d.171207213408
EDUID : 1 EDUNAME: db2fmp (3600) 0
FUNCTION: DB2 UDB, oper system services,
sqloAIXLoadModuleTryShr, probe:140
CALLED : OS, -, dlopen
OSERR : ENOEXEC (8) "Cannot run a file that does not have a
valid format."
MESSAGE : Attempt to load specified library augmented with
object name failed.
DATA #1 : Library name or path, 36 bytes
/dvm/ifta/function/IF9000P(shr_64.o)
DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
327682
DATA #3 : String, 250 bytes
0509-022 Cannot load module
/dvm/ifta/function/IF9000P(shr_64.o).
0509-153 File /dvm/ifta/function/IF9000P is not an
archive or
the file could not be read properly.
0509-026 System error: Cannot run a file that does not
have a valid format.
2017-12-07-16.34.10.737508-300 I10606A448 LEVEL: Severe
PID : 7864408 TID : 3600 PROC : db2sysc
0
INSTANCE: db2d NODE : 000 DB : IFTADVM
APPHDL : 0-7 APPID: *LOCAL.db2d.171207213408
AUTHID : DB2D
EDUID : 3600 EDUNAME: db2agent (IFTADVM) 0
FUNCTION: DB2 UDB, routine_infrastructure,
sqlerDisassociateWithFmp, probe:30
RETCODE : ZRC=0xFFFFFB95=-1131
2017-12-07-16.34.10.737770-300 I11055A551 LEVEL: Severe
PID : 7864408 TID : 3600 PROC : db2sysc
0
INSTANCE: db2d NODE : 000 DB : IFTADVM
APPHDL : 0-7 APPID: *LOCAL.db2d.171207213408
AUTHID : DB2D
EDUID : 3600 EDUNAME: db2agent (IFTADVM) 0
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary
logging func, probe:0
MESSAGE : dissassociate failed
DATA #1 : Hexdump, 4 bytes
0x0A0000000CBF6614 : FFFF FBEE
* * * 28115008.1.000.app_trap.txt
*******************************************
* *
* DB2 USERS : *
* ----------- *
* A db2fmp process terminated abnormally. *
* This may have been caused by a prog- *
* ramming error in the routine. *
* A stack trace-back follows. *
* *
*******************************************
DB2 build information: DB2 v9.7.0.7 s121002 SQL09077
timestamp: 2017-12-07-21.34.11.605313
instance name: db2d.000
EDU ID : 1
Signal #11
uname: S:AIX R:1 V:7 M:00CF02C74C00 N:unpift01
process id: 28115008
thread id : 1 (0x1)
kthread id : 59310245
-------Frame------ ------Function + Offset------
0x0000E0A0 ?unknown + 0x0
0xD01086B8 load1 + 0x118
0xD01089EC load + 0x12C
Nested signal handlers detected
6. How to reproduce the problem
(Include the name of the bucket and snippet of existing or
planned test unit that exposed the failure described above. A
"repro" should be as small as possible. Also, include the degree
of difficulty of the repro. A repro is Easy if it can be done
on demand, Medium if it can be done after several attempts, and
Hard if it is not possible.)
7. Did anything in particular seem to cause this problem?
8. Is this problem a regression? If so, please provide details
on the last successful build level similar to (3) above. |
