APAR status
Closed as program error.
Error description
During the patch management process, any invalid objects in the database (for example, views) are automatically recreated and any invalid packages are rebound. This step is failing with SQLCODE -901 and generating messages similar to the following in the db2diag.log, and generating FODC directories. 2017-05-26-11.02.38.982897-240 E17039253E817 LEVEL: Error PID : 720298 TID : 140736875980544 PROC : db2sysc 0 INSTANCE: bigsql NODE : 000 DB : BIGSQL APPHDL : 0-75 APPID: *N0.bigsql.170526150237 AUTHID : BIGSQL HOSTNAME: testsystem.ibm.com EDUID : 27 EDUNAME: db2agent (BIGSQL) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:30 MESSAGE : ADM14005E The following error occurred: "AppErr". First Occurrence Data Capture (FODC) has been invoked in the following mode: "Automatic". Diagnostic information has been recorded in the directory named "/var/ibm/bigsql/diag/DIAG0000/FODC_AppErr_2017-05-26-11.02.38.9 82755 _720298_27_000/". 2017-05-26-11.54.05.439215-240 E1207835E603 LEVEL: Severe PID : 720298 TID : 140736875980544 PROC : db2sysc 0 INSTANCE: bigsql NODE : 000 DB : BIGSQL APPHDL : 0-86 APPID: *N0.bigsql.170526150501 AUTHID : BIGSQL HOSTNAME: testsystem.ibm.com EDUID : 27 EDUNAME: db2agent (BIGSQL) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:200 MESSAGE : ADM0001C A severe error has occurred. Examine the administration notification log and contact IBM Support if necessary. 2017-05-26-11.54.05.439648-240 I1208439E940 LEVEL: Severe PID : 720298 TID : 140736875980544 PROC : db2sysc 0 INSTANCE: bigsql NODE : 000 DB : BIGSQL APPHDL : 0-86 APPID: *N0.bigsql.170526150501 AUTHID : BIGSQL HOSTNAME: testsystem.ibm.com EDUID : 27 EDUNAME: db2agent (BIGSQL) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 61 sqlerrmc: Big SQL Scheduler is not enabled while accessing Hadoop table sqlerrp : SQLRL03E sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFF3C (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate:
Local fix
Ensure any invalid objects are recreated or dropped and any invalid packages are rebound before starting the patch installation. The following query can be used to check for the existence of invalid objects: 'SELECT * FROM SYSCAT.INVALIDOBJECTS' The objects can be recreated by running 'CALL SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS()' repeatedly until the number of objects in SYSCAT.INVALIDOBJECTS is zero or no longer decreases. Packages can be rebound by running 'db2rbind bigsql -l <output log file> -r any'
Problem summary
See error description
Problem conclusion
The problem is fixed in Version 5.0.1.0 and later fix packs
Temporary fix
Comments
APAR Information
APAR number
PI82525
Reported component name
INFO BIGINSIGHT
Reported component ID
5725C0900
Reported release
420
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-02
Closed date
2018-03-01
Last modified date
2018-03-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Unknown
Fix information
Fixed component name
INFO BIGINSIGHT
Fixed component ID
5725C0900
Applicable component levels
R425 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"420","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
25 August 2020