Re: Re: Multi-Partition Instance Creation

Re: Re: Multi-Partition Instance Creation

 

  

Hi Yogesh,

When I'm trying to run the db2set command in the second machine i.e machine2 its giving error

DBI1306N The instance profile is not defined.

Explanation:

The instance is not defined in the target machine registry.

User Response:

Specify an existing instance name or create the required
instance.

Can you help me on this...

AB


On Thu, 25 Mar 2004 Yogesh Kansal wrote :
>
>
>
>
>Hi Amit,
>
> Please check the following things :
>
>First set the following db2 registry variables:
>
> db2set DB2PORTRANGE=DB2_ese810db:DB2_ese810db_END
> db2set COMM=TCPIP
>and again try to start the instance.
>
>If that doesn't work then change the db2nodes.cfg to
>
>0 machine1 0
>1 machine2 1
>
>
>I hope this will resolve your problem .Please let me know ff you still face
>some problem .
>
>Regards,
>Yogesh Kansal
>
>
>
>
>
> "amit b"
> <[Email Address Removed] To: [Email Address Removed] fmail.com> cc:
> Subject: Multi-Partition Instance Creation
> 24/03/2004 18:53
> Please respond to
> "amit b"
>
>
>
>
>Hi All,
>
>I was trying to set up a multi-partitioned instance on the Linux boxes over
>here. Everything went fine with the installation and creation of instance
>but the real problem started when I tried to add the entries in the
>db2nodes.cfg file and start the instance.
>
>Here are a few of the information
>-------------------------------------------
>
>Entries in db2nodes.cfg :
>
>0 machine1 0 - this is the instance owning node
>1 machine2 0 - this is the machine that will be
>participating as a physical node
>
>Entries in the /etc/services file on both the machine :
>
>db2cese810db 35000/tcp
>db2iese810db 35001/tcp
>DB2_ese810db 50000/tcp
>DB2_ese810db_1 50001/tcp
>DB2_ese810db_2 50002/tcp
>DB2_ese810db_END 50003/tcp
>
>where ese810db is the name of my instance.
>
>The error that I'm getting is :
>
>03-24-2004 13:19:59 0 0 SQL6048N A communication error occurred
>during START or STOP DATABASE MANAGER processing.
>03-24-2004 13:20:00 1 0 SQL6048N A communication error occurred
>during START or STOP DATABASE MANAGER processing.
>SQL1032N No start database manager command was issued. SQLSTATE=57019
>
>I checked the rsh and rlogin and both of them are working fine. I tried to
>establish rsh and rlogin connection from machine1 to machine2 and its
>working fine.
>
>The moment I'm dropping the node information from the db2nodes.cfg file I'm
>able to start the instance. I checked the dbm cfg parameter for SVCENAME
>and its set correctly to the correct connect port number i.e 35000 in the
>above case.
>
>Any solution would be of great help to me.
>
>Thanks in Advance
>AB
>
>
>---------------------------------------------------------------------
>PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
>Get today's cartoon: http://www.LazyDBA.com
>To unsubscribe, e-mail: db2udbdba-[Email Address Removed] additional commands, e-mail: db2udbdba-[Email Address Removed]DB2 & UDB email list listserv db2-l LazyDBA home page