DB2 Hostname Change

[Former Member]

Dear All,

Our SAP Servers use Linux Suse 11 for OS with DB2 v10.1.0.2 which run on VMware virtualization on Blade Server.

Because of that our DRC planning will be done by restoring VMware images.

But, there are issues when we try to restore the Production servers images (seperated between PROD-CI and PROD-DB)

On OS level, IP,  Hostname also the SAP parameters has been replaced with the new ones (named PROD-CIDR and PROD-DBDR), the issues came up when we try to change to change DB2 hostname parameter using :

    db2set -g DB2SYSTEM=[new DB2 server hostname]

we got this error:

     DBI1309E  System error.

     Explanation:

     The tool encountered an operating system error.

     User response:

     A system error was encountered during registry access. Ensure that there

     is enough space on the file system where the registry is located, and

     that there is a valid LAN connection if the registry is remote.

when we looked at the db2diag.log, we got this info:

FUNCTION: DB2 Common, Generic Registry, GenRegBin::Change, probe:240

MESSAGE : ECF=0x900001EE=-1879047698=ECF_GENREG_RECORDBUF_FREEMEM_FAILURE

          Failed to free recordbuf memory

CALLED  : DB2 Common, OSSe, ossMemFree

RETCODE : ECF=0x900003EE=-1879047186=ECF_MEM_NULL_POINTER

          The address provided is NULL

---------------------------------------------------------------------------------------------------------------------------------------------------

FUNCTION: DB2 Common, OSSe, ossMemFree, probe:20

MESSAGE : ECF=0x900003EE=-1879047186=ECF_MEM_NULL_POINTER

          The address provided is NULL

DATA #1 : String, 75 bytes

          NULL pointer for memory allocation address found at: GenRegBin.C, line 1453

---------------------------------------------------------------------------------------------------------------------------------------------------

FUNCTION: DB2 Common, Generic Registry, GenRegBin::Change, probe:70

MESSAGE : ECF=0x900001BC=-1879047748=ECF_GENREG_FAILED_TO_LOCK_REGISTRY

          Failed to lock the registry

CALLED  : DB2 Common, Generic Registry, GenRegFile::Lock

RETCODE : ECF=0x900001DA=-1879047718=ECF_GENREG_UNABLE_TO_OPEN_LOCK_FILE

          Unable to open the lock file

---------------------------------------------------------------------------------------------------------------------------------------------------

FUNCTION: DB2 Common, Generic Registry, GenRegFile::Lock, probe:50

MESSAGE : ECF=0x900001DA=-1879047718=ECF_GENREG_UNABLE_TO_OPEN_LOCK_FILE

          Unable to open the lock file

CALLED  : DB2 Common, OSSe, OSSHFile::open

RETCODE : ECF=0x90000001=-1879048191=ECF_ACCESS_DENIED

          Access denied

---------------------------------------------------------------------------------------------------------------------------------------------------

Does anyone have this issue before?

Kindly help,

Regards,

Stan

[Former Member]

Dear All,

Finally I got the chance to give an update...

Just yesterday, I finally succeed to replicate and configure the DR server of our QA system.

Our steps are:

• Replicate the QA Server
• Build new server as DR server, set networking not to connect at power on
• After power on the server, I change some setting, which is
  • Change /etc/hosts value,

               Need to change the IP address, set the new IP and leave the hostname as it is

• Change Network Setting from YAST,

               When we create new server from replication, they will create new connection properties (set as eth1), where the new assigned network hardware set. The old connection properties (set as eth0) contain the old IP, and will not contain hardware information/empty. So we need to delete the old connection properties and set the new IP to the new connection properties (also change the conf name from eth1 to eth0)

• Connect DR server to the network

        After this, we already can ping the DR server

• Start SAP services

Then, the SAP DR can be accessed by SAP Logon by adding new connection while the real QA is still online.

So far, we've tested it up to that point and haven't try to insert some transaction and also haven't check any issue related to SAP parameters.

If there's no trouble, we intended to replicate the Production servers...

Any inputs / suggestions about this? Is there any point that we need to check first at this point?

Regards,

Stan Beta

[former_member188883]

Hi Stan,

Please refer SAP note

70856 - DB2 specific actions when renaming DB host

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Dear Deepak,

Thank you for your reply,

When I tried the command mentioned in the SAP node, I got this result:

     "SQL1027N The node directory cannot be found"

Does it mean that there issue on the DB2 installation?

Regards,

Beta

[former_member188883]

Hi Stan,

Please check and update correct hostname under db2nodes.cfg file.

Secondly check whether command works fine or not

db2 list node directory

If you landup with error message using above command you may be required to catalog the database using the command

db2 catalog database <SID> as <SID> on /db2/<SID>

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Dear Deepak,

Sorry for the late reply,

I already updated the hostname under db2nodes.cfg several weeks ago, so I executed those command under the new db2nodes.cfg

I tried to execute the command you suggested, and here are the result:

- when I want to list the node directory, it said the directory cannot be found

- but when i want to create catalog database P01, the catalog P01 was already existed

Regards,

Beta

[former_member188883]

Hi Beta,

Please refer to below link for resolution steps on SQL1005N

http://publib.boulder.ibm.com/tividd/td/TSLA/SC32-1240-00/en_US/HTML/sl21tmst59.htm

You may need to recreate db.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Dear Deepak,

I'm sorry for the late reply, been busy with work beside the DR...

I've talked with my office networking team, and they checked the server, and there's a probability that we can try to replicate an then just change only the server DR IPs, without changing the hostnames and aliases.

If this way still got another error, maybe I'll try to recreate the DB...

Thank you.

Regards,

Stan Beta

[former_member188883]

Thanks for the information Stan. Keep us posted.

[brian_lawrence]

Hi Stan

I think the command should be (as root) :

db2iset -g DB2SYSTEM=<new host name>

Also ensure that your db2nodes.cfg file contains the new host name.

Regards

Robert

[Former Member]

Dear Robert,

Thank you for your reply,

As seen in the picture I attached below, I tried to use the db2iset command as root, but the OS said that it doesn't recognize the command. I also tried to use db2set as root, still showed the same result.

Then I tried to login as db2admin [db2p01], and tried the db2iset command, but they said it is a wrong command and tried to fix it as db2set. And there's the result, the same as what I mentioned before.

So the DB2SYSTEM value is still using the old hostname

Regards,

Stan