Skip to main content

OCDB Driver and machine serial number

  • March 31, 2023
  • 2 replies
  • 1 view

Daniel Martin

ODBC Driver.

Good day all, thanks for the help with the previous post. Its given me plenty to work on. Along with this, I've had another issue that has risen this week.

When Live Partition Mobile'ing a AIX Server, we hit problems with the OCDB driver. Namely that the server moves live with no issue, until you restart UniVerse, then we get license problems. If the server is moved back to the original machine, the license problem still occurs. So it needs to be reset. Now I know that on our Redhat VMware environments this is not a problem, and I'm sure its something that I could fix, but before I re-invent the wheel, I figured I'd ask here.

Thanks,



------------------------------
Daniel Martin-Corben
Rocket Forum Shared Account
------------------------------

2 replies

Jonathan Smith
Forum|alt.badge.img+4

ODBC Driver.

Good day all, thanks for the help with the previous post. Its given me plenty to work on. Along with this, I've had another issue that has risen this week.

When Live Partition Mobile'ing a AIX Server, we hit problems with the OCDB driver. Namely that the server moves live with no issue, until you restart UniVerse, then we get license problems. If the server is moved back to the original machine, the license problem still occurs. So it needs to be reset. Now I know that on our Redhat VMware environments this is not a problem, and I'm sure its something that I could fix, but before I re-invent the wheel, I figured I'd ask here.

Thanks,



------------------------------
Daniel Martin-Corben
Rocket Forum Shared Account
------------------------------

Daniel,

UniVerse (and UniData) take a hardware signature (combining several elements) of the machine when installed and licenced. If they detect that something has changed in that signature then they will become unlicensed. We have seen that on VMware that moving instances doesn't always trigger a change in the generated hardware signature, hence does not become unlicenced. The AIX LPM (Live Partition Mobility) must change something that results in one or more of the elements of hardware signature changing, so there is nothing you can fix.

Before anyone asks we will not be disclosing what makes up the signature :-)


Regards,



------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------

Daniel Martin
  • Author
  • Participating Frequently
  • March 31, 2023

Daniel,

UniVerse (and UniData) take a hardware signature (combining several elements) of the machine when installed and licenced. If they detect that something has changed in that signature then they will become unlicensed. We have seen that on VMware that moving instances doesn't always trigger a change in the generated hardware signature, hence does not become unlicenced. The AIX LPM (Live Partition Mobility) must change something that results in one or more of the elements of hardware signature changing, so there is nothing you can fix.

Before anyone asks we will not be disclosing what makes up the signature :-)


Regards,



------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------

Thanks for the clarification. I'm guessing there is no way round this, apart from re-licensing the machine the next time UniVerse needs to start. In AIX's case I was assuming that it was a change of the serial number of the machine. As its a virtual machine, the serial would be the main thing that changes, everything else is kept the same by the OS due to the virtualised devices/system.



------------------------------
Daniel Martin-Corben
Rocket Forum Shared Account
------------------------------