on 12-31-2021 11:29 PM
I'm in the process of replacing a VM (old=SUSE 11 / new=Ubuntu 20.04).
I've been able to get all but one of my SAP/Sybase software installations migrated successfully:
ASE 15.7 SP140 # failure (more below)
ASE 16.0 SP03 PL07 # success
RS 15.7.1 SP306 # success
RS 16.0 SP03 PL07 # success
Data Assurance 16.0 SP03 PL06 # success
SYSAM_2_4 # success
The ASE 15.7 software installation completes successfully and I can successfully create a new ASE instance. There's just one issue, ASE's SYSAM component thinks the hostid is null (see last line from this errorlog snippet):
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel SySAM: The hostid of this system does not match the hostid
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel SySAM: specified in the license file.
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel SySAM: License feature name: ASE_CORE
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel SySAM: License hostid: 000011223344
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel SySAM: License search path: /opt/sybase/ASE_157_SP140/SYSAM-2_0/licenses/ASE.EV.lic:
00:0000:00000:00000:2021/12/31 15:44:03.03 kernel SySAM: FLEXnet Licensing error:-9,57. System Error: 19 "(null)"
NOTES:
I've also verified this behavior (hostid=null) with the associated SYSAM/cpuinfo:
sybase:/opt/sybase/ASE_157_SP140/SYSAM-2_0/bin
$ ./cpuinfo
License hostid: <<<=== no hostid is displayed
Detected 4 logical processor(s), 4 core(s), in 2 chip(s)
The RS 15.7.1 version of SYSAM/cpuinfo, running on the same VM, does show the hostid:
sybase:/opt/sybase/RS_1571_SP306/SYSAM-2_0/bin
$ ./cpuinfo
License hostid: 000011223344 <<<=== correct hostid displayed
Detected 4 logical processor(s), 4 core(s), in 2 chip(s)
KBA 2993255 looks like a possible match (ASE 15.0, invalid host, hostid = ' null').
KBA 2422577 looks like a match for the `cpuinfo` program generating hostid=null.
Question: Could someone with access to KBAs 2993255 and 2422577 respond with the resolutions to these issues?
Thanks,
Mark
Hi Mark,
We had a similar situation some years ago when we started using NIC binding - using multiple ethernet network adapters in the same server. The solution was to rename the connection to eth0, SySam 2.0 wouldn't work otherwise with what our network admin had named the connection.
HTH
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hector,
I've only got the one ethernet/network adapter on this VM but it was named ens33 so after making sure I had a good VM snapshot it was off to chat with Mr Google about how to change the name to eth0 ...
After a bit of OS wrangling (and a few restores back to that VM snapshot) I was able to rename the ethernet/network adaptor to eth0.
I've finally got my ASE 15.7 instance up and running under a (served) EV license!
General notes:
Thanks for the tip!
Mark
User | Count |
---|---|
78 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.