Command of cataloging the databse

[Former Member]

Hello,

i have done a distributed installation CI on node A & DB on node B

details

CI - HOSTNAME - ECCCI

DB - HOSTNAME - ECCDB

SID - PRD

When i move DB vg on node A ,what command i have to use to catalogog a database

i have the command format. please suggest me the exact command

1. command to add the TCP/IP node to the node directory:

db2 catalog tcpip node node_alias_name remote DB2_server_host_name server DB2_port

2. command to catalog the database.

db2 catalog db database_name as database_alias at node node_alias_name

in my case what command should be used?

Thanks & Regards

[malte_schuenemann · Accepted solution]

First, you need to catalog the database on the local host, To do this, use

db2 uncatalog db <sid>
db2 catalog database <sid> on <path>
db2stop
db2start

As you obviously moved the DB to the CI, this should be sufficient to enable the CI to connect. On the SAP side, you might have to maintain the SAPDBHOST variable in the profiles.

Malte

[Former Member · Accepted solution]

When i have to use this command

1. when CI is on node A and DB is on node B - sap is working

2. when Ci is on node B and DB is on node B - sap is working

3 when CI is on node A and DB is on node A - sap is not connected to database

do i have to use is this command in 3rd case is there any othere post activities to do.

[Former Member · Accepted solution]

db2 uncatalog db PRD

db2 catalog database PRD on <path>

db2stop

db2start

what i have to put in stead of <path>

[Former Member · Accepted solution]

Hi,

sounds like a cluster installation right?

Which Operating System?

[Former Member · Accepted solution]

AIX/DB2/HACMP

[former_member256962]

Hi Uppal,

Instead of catalogging in CI host you can use Thin Client which will have a file in global directory sharing the details of db host and port(even thats y thin client was introduced)

If it is fat client as in your case.Please proceed with following two commands from CI host

--->db2 catalog TCPIP NODE ECCDB REMOTE ECCDB SERVER sapdb2PRD (sapdb2PRD should exists in services file reserving a port)

-

---

>db2 catalog db PRD at node ECCDB

This will make ur R3trans to work for sure once dscdb6.conf file exists in global directory.To create the same use dscdb6up utility of your kernel which will keep the password of your schema in an encrypted way

[former_member256962]

Hi Uppal,

Instead of catalogging in CI host you can use Thin Client which will have a file in global directory sharing the details of db host and port(even thats y thin client was introduced)

If it is fat client as in your case.Please proceed with following two commands from CI host

--->db2 catalog TCPIP ECCDB REMOTE ECCDB SERVER sapdb2PRD (sapdb2PRD should exists in services file reserving a port)

-

---

>db2 catalog db PRD at node ECCDB

This will make ur R3trans to work for sure once dscdb6.conf file exists in global directory.To create the same use dscdb6up utility of your kernel which will keep the password of your schema in an encrypted way