Results 1 to 9 of 9
  1. #1
    Join Date
    Apr 2008
    Location
    Iasi, Romania
    Posts
    561
    Provided Answers: 2

    Unanswered: Workgroup licence problem

    DB2 9.7 FP6 on Windows 2008
    I am opening Licence Center and I see:
    Licence type: CPU Option
    Expiry date: Permanent

    I am using Generate Compliance report and I see:
    Workgroup Server Edition Violation

    After I Reset Compliance Report, licence appears In compliance. However, few days later it's violation again. And so on.

    I've run all the queries from here: IBM DB2 9.7 for Linux, UNIX and Windows Information Center but didn't find anything.
    Any ideas?
    Florin Aparaschivei
    DB2 9.7, 10.5 on Windows
    Iasi, Romania

  2. #2
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Hard to advise , without seeing the full output of db2licm -l, and the full report .
    Could it be that you are using some feature that requires a different license...

  3. #3
    Join Date
    Apr 2008
    Location
    Iasi, Romania
    Posts
    561
    Provided Answers: 2
    db2licm -l

    Product name: "DB2 Workgroup Server Edition"
    License type: "CPU Option"
    Expiry date: "Permanent"
    Product identifier: "db2wse"
    Version information: "9.7"
    Max amount of memory (GB): "64"
    Enforcement policy: "Soft Stop"
    Florin Aparaschivei
    DB2 9.7, 10.5 on Windows
    Iasi, Romania

  4. #4
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Is there any additional information from db2diag.log ?

    See
    Compare the distributed DB2 9.7 database servers

  5. #5
    Join Date
    Jan 2010
    Posts
    335
    Hi,

    what is the Sizing of your Server? Does it have more than 64 GB RAM. How many CPU-Cores do you have? (Limit ist 16 Cores and 64 GB RAM).
    You could set your "Enforcement policy" to HARD, then you'll get some errors in db2diag.log. Ok, not suitable for a Production Environment ...

    Other Points: WLM, Table Partitioning

  6. #6
    Join Date
    Apr 2008
    Location
    Iasi, Romania
    Posts
    561
    Provided Answers: 2
    It's a 2 CPU with 16 GB RAM so it's not about the limits. Also, I do not use WLM or table partiioning.

    However, there is a trial DB2 Connect that is expired that might cause this. I will investigate this on Acceptance environment.
    Florin Aparaschivei
    DB2 9.7, 10.5 on Windows
    Iasi, Romania

  7. #7
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Ignore the db2-connect expired license, this is always the case unless you have installed and licensed the "db2 connect" product variants for connecting to Z/OS or AS/400 environments. You do not need db2-connect for any other purpose.

    Your problem is most likely to be that you are using some feature that is not valid for workgroup edition for your version of db2, although you might not be aware of it yet...

  8. #8
    Join Date
    Apr 2008
    Location
    Iasi, Romania
    Posts
    561
    Provided Answers: 2
    Quote Originally Posted by db2mor View Post
    Your problem is most likely to be that you are using some feature that is not valid for workgroup edition for your version of db2, although you might not be aware of it yet...
    I know, but I cannot find it. When I'm generating the report it appears in compliance and after several hours it appears as violation.
    I've changed the policy to HARD, but still no message in db2diag.
    Florin Aparaschivei
    DB2 9.7, 10.5 on Windows
    Iasi, Romania

  9. #9
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Try db2licm -x
    before next report
    and monitor what goes in db2diag.log after the db2licm -x and the next violation (if it happens)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •