The V10.5 LUW Infocenter says that you can use db2setup with a response-file (*addpart.rsp) to add a new physical node to an existing partitioned instance.
Reference:
Setting up a partitioned database environment
I'm using RHEL x64 Version 6.4 and the GA release of DB2 V10.5.
I'm setting up a trivial DPF environment with 2 physical nodes (1 node per box).
I've done a root-install with db2setup for a partitioned instance, which created the *addpart.rsp file, and then I did a root db2setup -r *addpart.rsp on another machine.
Both of the db2setup commands completed without errors or warnings.
There is no database created as yet, in the instance, but the instance on the instance-owning partition starts OK when single-partitioned.
But on the machine where i used the db2setup -r *addpart.rsp, the command 'db2set DB2RSHCMD=/usr/bin/ssh' fails with "DBI1306N The instance profile is not defined.".
(The same command ran fine on the instance-owning node).
The *addpart.rsp has no information about the partitioned-instance, so I'm not sure how the db2setup is supposed to know how to join the existing partitioned instance.
If I add a line to db2nodes.cfg for the second node then both db2_all date, and rah date run correctly, giving results from both nodes, but db2start cannot start the second node (SQL6032W) probably due to the *addpart.rsp installation being incomplete in some respects. Though I cannot see what I've missed if I interpret the docs correctly.
Any suggestions as to how the *addpart.rsp method is supposed to work if the addpart response file has no information about the partitioned instance?
Reference:
Setting up a partitioned database environment
I'm using RHEL x64 Version 6.4 and the GA release of DB2 V10.5.
I'm setting up a trivial DPF environment with 2 physical nodes (1 node per box).
I've done a root-install with db2setup for a partitioned instance, which created the *addpart.rsp file, and then I did a root db2setup -r *addpart.rsp on another machine.
Both of the db2setup commands completed without errors or warnings.
There is no database created as yet, in the instance, but the instance on the instance-owning partition starts OK when single-partitioned.
But on the machine where i used the db2setup -r *addpart.rsp, the command 'db2set DB2RSHCMD=/usr/bin/ssh' fails with "DBI1306N The instance profile is not defined.".
(The same command ran fine on the instance-owning node).
The *addpart.rsp has no information about the partitioned-instance, so I'm not sure how the db2setup is supposed to know how to join the existing partitioned instance.
If I add a line to db2nodes.cfg for the second node then both db2_all date, and rah date run correctly, giving results from both nodes, but db2start cannot start the second node (SQL6032W) probably due to the *addpart.rsp installation being incomplete in some respects. Though I cannot see what I've missed if I interpret the docs correctly.
Any suggestions as to how the *addpart.rsp method is supposed to work if the addpart response file has no information about the partitioned instance?