Db2

Db2

Where DBAs and data experts come together to stop operating and start innovating. Connect, share, and shape the AI era with us.


#Data


#Data
#Databases
#Operatingsystems
#Db2
#Databasesolutions
 View Only

  • 1.  DMC and DROPED TABLE RECOVERY

    Posted 07/27/21 01:39 PM
    Hi,

    just a hint for all DMC users.

    According to Db2 docs, the default for creating new tablespaces uses DROPPED TABLE RECOVERY = ON. See: Recovering a dropped table
    If you use this script to create your tablespaces for DMC, you might get heaps of messages in your Recovery History File db2rhist.asc of your database of IBM_RTMON tables dropped and recreated in TS4MONITOR.
    I ended up having a very imperformant db2rhist.asc file with 2.4 GB in size and millions of entries.  :-(

    At least the KC should be updated to include DROPPED TABLE RECOVERY OFF on this page.
    SET STMT = 'CREATE TABLESPACE TS4MONITOR IN CONSOLEGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 100M MAXSIZE 2G BUFFERPOOL CONSOLEPOOL DROPPED TABLE RECOVERY OFF';

    Kind regards

    ------------------------------
    Roland Schock
    Distinguished Engineer
    ARS Computer und Consulting GmbH
    Muenchen
    ------------------------------

    #Db2


  • 2.  RE: DMC and DROPED TABLE RECOVERY

    Posted 07/28/21 09:23 AM

    Hi IBM,

    I have the same problem! What's the reason creating these tables again and again??


    Regards

    Gerald



    ------------------------------
    Gerald Zottl
    ------------------------------



  • 3.  RE: DMC and DROPED TABLE RECOVERY

    Posted 07/29/21 04:59 AM
    @KAI DING May you pls advise if this is valid problem in DMC v3.1.5? ​

    ------------------------------
    Su Li Hou
    ------------------------------



  • 4.  RE: DMC and DROPED TABLE RECOVERY

    Posted 07/30/21 04:03 AM
    Hi Su Li,

    good question! A colleague of mine is maintaining the DMC image in OKD, but he's on holiday now.

    1. DMC does not mention any version number in its splash screen during sign-on
    2. After I solved my issues with signing on (details on that below, IBM case is following too), I could not find a decent spot, where DMC clearly states, I'm version 3.1.4 or 3.1.5. I just can find a "Productinfo" panel, which says: Build20210510-134804

    Or is there another method for finding out, which version is running, if you don't know, what image of DMC was started?

    P.S.: The logon issue: Due to German security regulations from BSI, my user was moved into the AD group "Protected Users Security Group" (see also https://docs.microsoft.com/en-us/windows-server/security/credentials-protection-and-management/protected-users-security-group ). DSM is configured to lookup the users in AD via LDAP integration and as long as my user is in that group, logon is not possible. The security admin removed my group membership temporarily and now I was able to login again. I was told, here is something IBM has to fix in the logon process to allow such a logon.

    Kind regards

    ------------------------------
    Roland Schock
    Distinguished Engineer
    ARS Computer und Consulting GmbH
    Muenchen
    ------------------------------

    Original Message


  • 5.  RE: DMC and DROPED TABLE RECOVERY

    Posted 07/30/21 05:26 AM
    Hi Roland

    I think it is a good addition to show DMC version in the log-in screen. For the production information panel there should also be version info (like v3.1.5, v3.1.5.1) as well as specific build# (which usually contains timestamp) . @Yue Yang may you pls help check?

    For the log in issue regarding to AD group "Protected Users Security Group" , pls open DMC case with all the reference information. I can connect with dev owner to evaluate the enhancement needed here.

    The original issue you reported turns to be a valid issue. Dev team is going to fix it in next mod release. Thanks for raising this!
    ​​​​

    ------------------------------
    Su Li Hou
    ------------------------------

    Original Message


  • 6.  RE: DMC and DROPED TABLE RECOVERY

    Posted 07/29/21 10:07 PM
    Hi

    Thank you for reporting this issue and your suggestion on it. Our engineering team have done the investigation, adding DROPPED TABLE RECOVERY OFF to the tablespace DDL can eliminate the extension of db2rhist.asc file effectively. It will be optimized in the near future release: https://github.ibm.com/tools-for-aps/zh/issues/25646.

    ------------------------------
    Rui Li
    ------------------------------



Related Content