Management Console - A system temporary table space insuff.

dataservices administration
1

We are installing DI 11.7 and I am able to log onto the Management Console but when selecting Batch Job Status I receive the following error message:
A system temporary table space with sufficient page size does not exist

Can someone tell me what TS size I need? We currently have a 4k size but obviously require more.

Thanks.

Longrun4fun (BOB member since 2008-10-22)

2

you will get this error for DB2 repository, is your DI repository on DB2 ?
if so, then create a buffer pool with size 8K or 16K in the repository database and create temp space using that buffer pool

manoj_d (BOB member since 2009-01-02)

3

manoj_d - once I had that changed I received a new error message:

[IBM][CLI Driver][DB2/SUN64] SQL0420N Invalid character found in a character string argument of the function “DECIMAL”. SQLSTATE=22018

Any idea of what could be causing this? We are updating from 11.5 to 11.7.

Thanks.

Longrun4fun (BOB member since 2008-10-22)

4

I think for this you will need to change the view definition in DI Repository for view ALVW_HISTORY

in the view definition you will find the following comparison, which is cause this problem
change this
L.OBJECT_KEY = CAST ( SC.VALUE as numeric)
to
CAST (L.OBJECT_KEY as char) = SC.VALUE

if you are on DB2 Fix Pack 17, then you will run into another issue the history will dispaly the same job multiple time, the work around for that is to reverse the order of comparison with constant
move the constant from left hand side to right hand side of the comparison
change following
‘SYSTEM_CONFIG_INFO’ = SC.NAME
to
SC.NAME - ‘SYSTEM_CONFIG_INFO’
do this for all the constant in the view definition

these issues is fixed in 12.0

manoj_d (BOB member since 2009-01-02)

5

Made those changes and now when in the Management Console (after clicking on repository name) it hangs.

Opening page http://im4w084:28080/diAdmin/servlet/AwBatchJobHistory?ACTIVE_VIEW=Batch+Job+Status&REPOSITORY_NAME=djpboxi1&SHOWR

Longrun4fun (BOB member since 2008-10-22)

6

the hanging issue is also related to view definition

I think you resloved similiar issue or same issue earlier, refer the following thread, is this happening in the same env again ?

Modify the view definition as below

CREATE VIEW ALVW_HISTORY
SELECT H1.OBJECT_KEY, H1.MACHINE, H1.SERVER, H1.TYPE, H1.SERVICE, H1.CONTAINER
, H1.INST_MACHINE, H1.INST_SERVER, H1.INST_SERVER_PORT, H1.INST_REPO,
H1.INST_EXEC, H1.INST_EXEC_KEY, H1.RUN_SEQ, H1.START_TIME, H1.END_TIME,
H1.EXECUTION_TIME, H1.STATUS, H1.HAS_ERROR, H1.IGNORE_ERROR,
H1.NORM_MACHINE, H1.NORM_SERVER, H1.NORM_TYPE, H1.NORM_SERVICE,
H1.NORM_CONTAINER, H1.NORM_INST_MACHINE, H1.NORM_INST_SERVER,
H1.NORM_INST_REPO, H1.NORM_INST_EXEC, L.NAME, SC.VALUE, SG.VALUE, EL.VALUE
, TL.VALUE, ML.VALUE
FROM AL_HISTORY H1
LEFT JOIN AL_HISTORY_INFO SC
ON H1.OBJECT_KEY = SC.OBJECT_KEY
AND SC.NAME = ‘SYSTEM_CONFIG_INFO’
LEFT JOIN AL_LANG L
ON L.OBJECT_TYPE = 43
AND CAST (L.OBJECT_KEY as char) = SC.VALUE
LEFT JOIN AL_HISTORY_INFO SG
ON H1.OBJECT_KEY = SG.OBJECT_KEY
AND SG.NAME = ‘SERVER_GROUP_NAME’
LEFT JOIN AL_HISTORY_INFO EL
ON H1.OBJECT_KEY = EL.OBJECT_KEY
AND EL.NAME = ‘ERROR_LOG_INFO’
LEFT JOIN AL_HISTORY_INFO TL
ON H1.OBJECT_KEY = TL.OBJECT_KEY
AND TL.NAME = ‘TRACE_LOG_INFO’
LEFT JOIN AL_HISTORY_INFO ML
ON H1.OBJECT_KEY = ML.OBJECT_KEY
AND ML.NAME = ‘MONITOR_LOG_INFO’

manoj_d (BOB member since 2009-01-02)