UNSOLVED

Can2

updated

15 years ago

C

Can2

1 Rookie

•

100 Posts

0

993

December 20th, 2011 04:00

Informix module license problem

Hi,

  We are using nw server 7.6.2 as a networker server version on aix. There are some clients and nw informix module installed on that clients. Our problem is that informix module installed clients both use networker module for informix license and nmda license as you can see like at below. Is there any idea ?

NetWorker Module for Databases and Applications, Unix Client/1

                     Available: 11

                          Used: 11

                     Remaining: 0

             Connected Clients: inis1db1, inis2db1, omcadn1,

                                sysank1, sysant1, sysavr2,

                                sysbur1, sysdyb1, syserz1,

                                sysizm1, syssam1;

NetWorker Module for Informix, Unix Client/1

                     Available: 8

                          Used: 8

                     Remaining: 0

             Connected Clients: omcadn1, sysant1, sysavr2,

                                sysbur1, sysist2, sysist3,

                                sysizm1, syssam1;

  • Daniea3

    123 Posts

    324

    0

    Posted January 5th, 2012 03:00

    Hi,

       I can see the following clients common with both the license.omcadn1,sysant1,sysavr2,sysbur1,sysist2,sysist3,sysizm1,syssam1. Do you have NMDA and Networker Module for Informix installed on these clients. Also do you have multiple client instances for these clients to backup DB using NMDA and NMI?

    -Arun

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    324

    0

    Posted January 10th, 2012 08:00

    This can happen if you use NMI license and NMDA module.  In such case, just ignore it.

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    324

    1

    Posted January 10th, 2012 13:00

    OK, let's start from scratch.  You have some clients where you have Informix and you do backup with module - correct?

    Now, which licenses do you use - NMDA or NMI or mixed?  If mixed, I can see where problem may arise, but in case you use only NMI then not.  I assume this is mixed.  The problem there is that NW allocates licenses dynanically and in certain versions you will see (at least up to 7.5SP3, but I suspect later too) that after some idle time some license usage is gone from nsrlic report until next backup will run.  I do not have details on how does NW allocate and forget about this under the hood, but this is something I see on regular basis.  Second question is - do you use NMI or NMDA module on those hosts.  Again, this may depend on NW server version, but I assume based on initial string query from module NW server should know which license to check if available if already not allocated to client.  The specific confusion may arise here because when NMDA was introduced then EMC decided that oldish licenses can be used with NMDA (but would be used only for that specific product while NMDA license alone I believe could be used for any supported NMDA database or application).  With that in mind, and if we assume that server would allocate anything to support Informix, one can see that confusion such as in your case may arise.  In case where you use NMI for Informix and NMDA for something else you may get in situations where both are allocated to Imix clients and you lack NMDA licenses for rest of the landscape at the end - is this what you see?  If that would be the case then you could either exchange licenses to have them all in one type or, EMC could make some sort of code change not to allocate 2 lcenses for host for the same backup type (something you can control within backup command of NMDA for example).  However, it all comes down what is really going on and how is your setup which is still unknown. Best bet would be support in this case to verify this and fix it if what I said before is your case.

  • Can2

    1 Rookie

    •

    100 Posts

    324

    0

    Posted January 10th, 2012 13:00

    Hi Hrvoje,

      It is using 2 license and cause license problem, how can we ignore it ?