Conference decwet::winnt-clusters

Reading through this notesfile, I have seen that people are using SQL 6.5 
plus SP2. Is there a service pack 2 for SQL 6.5 ? I am running 
	NT4.0 + SP2
	SQL 6.5 + SP1
CHris

    re .-1 > Is there a service pack 2 for SQL 6.5 ?
    
    Available at the Microsoft BBS softlib/mslfiles:
    12-23-96        S20395  65sp2ppc.exe    SQL Server 6.5 Service Pack
    212-23-96        S20394  65sp2mip.exe    SQL Server 6.5 Service Pack
    212-23-96        S20393  65sp2alp.exe    SQL Server 6.5 Service Pack
    212-23-96        S20392  65sp2x86.exe    SQL Server 6.5 Service Pack 2
    
    /Shaun

There is a release note for the situation you describe for SQL  RTM

IP:  You can't use an IP address that already exists on the Lan.  Reserve a
static address for the Cluster IP address

re -3

>IP:  You can't use an IP address that already exists on the Lan.  Reserve 
>a static address for the Cluster IP address

I understand, that and it is not my purpose to create an operational
IP object for an address which is already in use on the LAN. I am just 
stating/reporting that if you make a mistake/typo (I did it, I used an 
existing IP address to create an IP object), the cluster software will be 
in trouble.


>there is a release note for the situation you describe for SQL  RTM

I always (never say always :-) read the release notes but I may have 
misunderstood some point.

a) suspect flag
   Again, I am just telling that I could not successfully enroll a database             
without this database having the suspect flag first set by SQL.
   
b) enroll a second database

   Section 4.2.4 from the Release Notes 
    "If unrolled Databases Become Suspect after a failover" 
   explains that I should first enroll the database in a failover group 
   Before running the stored procedures.
   The pb is that I CANNOT enroll a second database, its suspect flag 
   being set or cleared :-) .


   I will see if applying SQL SP2 fixes the problem.


From release Notes

4.2.4 If Unenrolled Databases Become Suspect After a Failover
-------------------------------------------------------------
Cluster software now lets you enroll SQL databases in 
failover groups and unenroll them. If an unenrolled database
on a cluster share becomes suspect after a failover, you can
perform the following steps:

  1. Enroll the database in a failover group.

  2. In the SQL Enterprise Manager Query Tool, run the 
     following two procedures in order:

     sp_fallback_dec_clean
     sp_fallback_activate_svr_db

     These procedures are listed in the master database.

  3. Unenroll the database from the failover group.

There is a section in the release notes called "preparing an existing SQL
Database for a new cluster". For Beta V1.1 you must execute sp_dboption to
take the Database off-line before the  cluster installation.  After you
create the failover group put the databases on-line and enroll them.

But I am trying to create a database after the cluster installation.
I will see if sp_dboption helps in this case.

Gents

I just discovered the following new pb with Domino Web Server


1- Domino (partitioned) servers are running on a single machine in the 
cluster (the other system is down), failover is working as expected

2- the IP names for the Domino servers are (for example) 
	ServerA
	ServerB
   these names correspond to the IP failover objects. I have checked that
   the name resolution is OK on all the systems (cluster members and client 
   workstation)
 
3-  I use netscape to connect to http://ServerA

	ServerB responds !

	I stop Domino ServerA and connect again to http://ServerA

	ServerB responds !!! (argh)

4- I restart ServerA, ie ServerA and ServerB are again running on the same 
system.

5- I use the Notes client to connect to a database on ServerA

	=> it works as expected

	=> I stop Domino Server A and try to connect to ServerA again

	=> It fails (as expected)

To fix this, I tried to use the DOMCFG.NSF database to create virtual WEB 
servers and specify an IP address. This does not fix the Pb (same 
behaviour)


Any idea ? Did you test this point.

the Notes.ini files contain the following entry

TCPIP_TcpIpAddress=0,<floating IP addresss>:1352


Christophe

Re: .7

Did you try setting a different IP port
for one of the web servers, using the
HTTP settings (Public Address book, Server document)?

The default port for web servers is 80.
You'd have to set the port for a second web server
to a different port number (81, 82, etc.).
The user would need to specify the port number.

For example:  http:\\ServerA:81

re -1

>Did you try setting a different IP port

Yes, it works. But this is not very nice. If you are a provider and run
the Notes networks for five companies on your cluster, then the 
customers will have to enter http://www.mycompany.xxx.com:<portnumber>
It seems that the http machine in Domino is listening at all IP addresses 
enabled on the system. 

But this is probably not a Cluster issue, and I'll see if there is a Domino 
conference somewhere.

Thanks.

re: .9

I believe this is a general restriction (or feature :))
for web servers, not a Domino issue.