Topic
3 replies Latest Post - ‏2012-10-17T07:58:30Z by PMartir
PMartir
PMartir
9 Posts
ACCEPTED ANSWER

Pinned topic OPM repository database issue

‏2012-10-14T10:03:18Z |
Hi,

sometimes a lot of messsages (every 15 minute) flooding the db2didag.log from the OPM repository database:
********************************************************************************
2012-10-13-19.37.01.168000+120 I40300096F500 LEVEL: Error
PID : 3348 TID : 1812 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PERFDB
APPHDL : 0-4957 APPID: *LOCAL.DB2.121013173701
AUTHID : WSP_ADMIN
EDUID : 1812 EDUNAME: db2agent (PERFDB) 0
FUNCTION: DB2 UDB, data management, sqldTableDrop, probe:352
DATA #1 : String, 63 bytes
Unable to drop table.
RC=80020032, Pool=11, Object=462, Class=0
********************************************************************************
Tablespace id 11 -- SHORTTERM_3

Table id 462 -- DB2PM_3 .TMP_FACT_BUFFERPOOL_4
********************************************************************************
list tablespaces :
...
Tablespace ID = 11
Name = SHORTTERM_3
Type = Database managed space
Contents = All permanent data. Large table space.
State = 0x0020
...
********************************************************************************
********************************************************************************
Environment:

OS Name: Microsoft Windows Server 2008 R2 Standard
OS Version: 6.1.7601 Service Pack 1 Build 7601

D:\Program Files\IBM\SQLLIB\BIN>pelevel
InfoSphere Optim Performance Manager Server for DB2 for Linux, UNIX and Windows
Version 5.1.1.0.4087, code levels: opmc-5.1.1.0.4087,common-5.1.1.0.4087,pdq-3.110.103

D:\Program Files\IBM\SQLLIB\BIN>db2level
DB21085I Instance "DB2" uses "64" bits and DB2 code release "SQL09075" with
level identifier "08060107".
Informational tokens are "DB2 v9.7.500.702", "s111017", "IP23287", and Fix Pack
"5".
Product is installed at "D:\PROGRA~1\IBM\SQLLIB" with DB2 Copy Name "DB2COPY1".
********************************************************************************
Has anyone seen this behaviour and found a solution?

See the attached file for more details.
Updated on 2012-10-17T07:58:30Z at 2012-10-17T07:58:30Z by PMartir
  • PMartir
    PMartir
    9 Posts
    ACCEPTED ANSWER

    Re: OPM repository database issue

    ‏2012-10-16T11:44:34Z  in response to PMartir
    This is happening after the OPM performed a LOAD operation into a table. The table space switches to backup-pending state and OPM try and can't drop the table from this TS. Could the OPM team please explain this behaving.
  • UteBaumbach
    UteBaumbach
    55 Posts
    ACCEPTED ANSWER

    Re: OPM repository database issue

    ‏2012-10-16T12:58:43Z  in response to PMartir
    Hi,
    seems that archive logging is configured for the repository database and since OPM uses a LOAD FROM CURSOR operation to aggregate data from level 3 to level 4, it happens in OPM 511 that the tablespaces go into backup pending. The LOAD FROM CURSOR can be disabled by setting a property. OPM 5111 recognizes it automatically if the repository database uses archive logging and disables LOAD FROM CURSOR automatically. Steps:
    1) Stop OPM server
    2) Take action to get the tablespaces into a normal state. E.g. backup the database to remove the BACKUP pending.
    3) Disable load from cursor aggregation
    Set in the db2pesrv.prop file:
    aggregation.high_volume_agg_level = 5
    4) Start OPM server.
    5) Note, that the log space usage will be higher on the repository database than before setting the property

    Regards
    Ute Baumbach
    • PMartir
      PMartir
      9 Posts
      ACCEPTED ANSWER

      Re: OPM repository database issue

      ‏2012-10-17T07:58:30Z  in response to UteBaumbach
      Hi,
      thank you for the explanation and help. We really use the archive logging for the repository database. I set the above settings and it has helped.

      Regards
      Pavel