cancel
Showing results for 
Search instead for 
Did you mean: 

License Key Issue

Former Member
0 Kudos

Hi All

I am in the midst of upgrading the BI  Production System  from 7.0 to 7.3 , received the following error message in the Configuration Phase.

WARNING: Your message server host bizprodv differs from your upgrade host sapprd02. Therefore you have to install a temporary license valid for the hardware key of host sapprd02.

This is required for the shadow system and also for the system during the downtime where a temporary message server on sapprd02 is run.

This error in the message server .Please advice how to resolve this issue.

Please also refer to the attachment attach all the license installed.Thanks

Regards

Clement

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member184544
Participant
0 Kudos

Hi Clement,

Can you post the output of saplicense -get execute it on each host  on the host file.

Former Member
0 Kudos

Hi Vasu

Here you go refer to host file I posted  earlier :-

Output from 10.10.58.194

sapprd02:bipadm 27> saplicense -get

saplicense: HARDWARE KEY = O1262146913

Output from 10.10.58.201

sapprd02:bipadm 26> saplicense -get

saplicense: HARDWARE KEY = O1262146913

former_member189725
Active Contributor
0 Kudos

Please use the command

# saplikey -show pf=<instance_profile> (saplicense -show was used with NW 640 and lower version)

Also this seems to be an issue with hosts file and this is because of the cluster configuration.

Can you please ask the cluster administrator to stop the cluster services till the upgrade is going on.

Temporarily change the hosts file as below in consultation with the cluster administrator.

**************************************************************************************************

10.10.58.201bizprodv bizprodv.sapura.com.my bizprodv_ha

#######################################################

10.10.58.194    sapprd02   sapprd02.sapura.com.my

10.10.58.195    sapprd01   sapprd01.sapura.com.my

10.10.58.196    sapprd03   sapprd03.sapura.com.my

#Used by Serviceguard for Heartbeat

192.168.1.2    sapprd01_hb

192.168.1.3    sapprd02_hb

192.168.1.4    sapprd03_hb

#Used by Serviceguard Package

10.10.58.201    bizprodv bizprodv.sapura.com.my     bizprodv_ha

10.10.58.200    erpprodv erpprodv.sapura.com.my     erpprodv_ha

10.10.58.202    bobprodv bobprodv.sapura.com.my     bobprodv_ha

10.10.58.191    erpdev erpdev.sapura.com.my

10.10.58.192    bizdev bizdev.sapura.com.my

**********************************************************************************************

The SAPup is considering hostname of the system as sapprd02 which should ideally be bizprodv so that this deviation can be avoided during the upgrade.

This is just a suggestion from  my end . Please consult with cluster team before going ahead.

Once you change , you might have to start the upgrade from scratch. But try restarting once .

Regards

Ratnajit

former_member189725
Active Contributor
0 Kudos

I suggest you get the hardware key for the host sapprd02, then in the service market place generate the license  based on this hardware key . Import this new license into the system using SLICENSE tcode in the main instance . Once it this done , continue with upgrade . SAPup/SUM should be able to install a temporary license for the shadow instance . Since the message server of the shadow instance runs on a different host than the main instance message server , hence the issue has come.

Regards

Ratnajit

Former Member
0 Kudos

Hi

I am quite new to this HP Service Guard behavior for SAP

It is strange behavior, when I check in system status it is pointing to 31.12.9999.

Content of my host file

#######################################################

10.10.58.194    sapprd02   sapprd02.sapura.com.my

10.10.58.195    sapprd01   sapprd01.sapura.com.my

10.10.58.196    sapprd03   sapprd03.sapura.com.my

#Used by Serviceguard for Heartbeat

192.168.1.2    sapprd01_hb

192.168.1.3    sapprd02_hb

192.168.1.4    sapprd03_hb

#Used by Serviceguard Package

10.10.58.201    bizprodv bizprodv.sapura.com.my     bizprodv_ha

10.10.58.200    erpprodv erpprodv.sapura.com.my     erpprodv_ha

10.10.58.202    bobprodv bobprodv.sapura.com.my     bobprodv_ha

10.10.58.191    erpdev erpdev.sapura.com.my

10.10.58.192    bizdev bizdev.sapura.com.my

I working on 10.10.58.94  to do the upgrade and the message server is 10.10.58.201,I have login both and both has the similar hardware key , both output as follows :-

LICENSE system: BIP hardware key: TEMPLICENSE expiration_date: 20110125

        installation no: INITIAL    key: CKCDYPO3YZAIVAB9A9LHGR1Z

        userlimit: 0 productid: R3_ORA

        system-nr: INITIAL_SYSTEM_IDX

        *** license expired ***

Regards

Clement

former_member184544
Participant
0 Kudos

Hi Clement ,

The license is checked with the hardware id of the system on which message server resides .If you are using a high availability system then you need to install license for each system that will be used by the message server during failover. Refer note 181543 for more information

Regards,

Vasu