[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

783.0. "Further problem on dual SQL setup" by NNTPD::"[email protected]" (HKTS) Fri May 02 1997 07:51

Under Dual SQL on v1.1 clusters environment there is some issue still
outstanding:
 
I found on the servers side, both servers were well-behaved only if primary
server initiate the failover.  However, once backup server initiate the
failover
followed by a failover, primary server got error messages as before, I've 
mentioned in DECnotes, but clients still can access all databases. 
 
Anybody encounter same/similar problem??  I have tried several times and got
same
error messages:  
 
>Error from ClimFmSqlGetDBInfoArray = -1073741819 
>Unknown error code 3221225477 (sev=3,fac=0x0,id=0x5)   
 
followed by, 
 
>Error initializing 
>Error getting SQL databases from CLUMGMT.DLL = -1073741819 
 
However, I've already found both servers more stable and no database
duplication happened.   
  
 
Best Regards, 
 
Eddy 
HK Tech Support 
 
:>


[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
783.1Any Help appreciated.ZPOVC::CSNAQSFri May 23 1997 06:0269
    Currently, I am trying to setup a Dual SQL Server in the NT Cluster
    V1.1. I believe that you have successfully setup the NT Cluster on Dual
    SQL at your Site.
    
    I would appreciate if you would help me to get my NT Cluster on Dual
    SQL Server up and running as we need to get it up at my Customer place
    as they have bought the Cluster Solution.
    
    I have managed to get both Server up and running but have some problems
    trying to get the Client up and running.
    Below is my setup details:
    
    Cluster Alias: NT_Cluster1
                                         
    AlphaServer 1000 4/500 ( Primary )	    AlphaServer 1000 4/500 (Failover)
    Server hostname : WILMA			Server Hostname:  BETTY
    IP Address: 10.61.77.47		        IP Address:10.61.77.47
    Subnet mask: 255.255.255.0			Subnet mask: 255.255.255.0
    Failover Group created: wilmadisks		Failover Group created:
    bettydisk
    
    SQL Server					SQL Server
    Database Device created: Finance		Database Device created: HR
    Database created: Profit			Database created:Employee, 
    								Promotion
    
    wilmadisks 					bettydisk 
    |___ Profit 				|___ Employee
    |___ 10.61.77.82 (IP Failover Object)       |___ Promotion
    						|___ 10.61.77.83 (IP Failover 
    								  Object)
    
    
    I have loaded the SQL Client on my PC running Windows95. When I login
    to the NT_Cluster1 using the ISQL_W, I could only see one database
    Profit. Although I have read the notes conference on Note 765.11 which
    specified that an Alternate Pipe is required, but I could not get it
    up. I have tried to do this ( refer to the Admin manual ), but was
    unsuccessful.
    
    Could you able to help me ? I am not too sure what to input as refer to
    the Admin manual. I am not familiar with SQL Server.
    
    According to the manual:
    
    SQL Server Box, create an SQL Server database alias. What should I type
    ?
    
    On Client Configuration Utility 
    
    Default Network: Named Pipes -> Advanced
    
    Server : ????? ( What should it type ? )
    DLL Name: dbnmp3.dll ( Is this Correct ? )
    Connection String:\\NT_Cluster1\pipe\bettydisk\query ( Is this Correct
    ? )
    
    Do I also need to create another Connection String for wilmadisks ?
    
    Can I also connect the Client to the Cluster through TCP/IP ?
    What should I input on the Client Configuration for TCP/IP connection ?
    
    Server :?? (What should I Type ? )
    DLL Name:dbnmp3.dll ( Is this Correct ? )
    Connection String:10.61.77.82 ( Is this Correct ? )
    
    Please advise. Thanks
783.2How to configure TCP/IP client connectionsDECWET::CAPPELLOFMy other brain is a polymerTue May 27 1997 17:5925
    With NT 4.0 and Digital Clusters V1.1, we recommend using TCP/IP for
    SQL client connections.  In your example, you must create a different
    "SQL Server Database Alias" for each failover group.  Use the SQL
    Client Configuration utility on your clients to set up the following
    aliases:
    
    Server: WilmaDatabases
    DLL Name: TCP/IP Sockets
    Connection String: 10.61.77.82
    
    Server: BettyDatabases
    DLL Name: TCP/IP Sockets
    Connection String: 10.61.77.83
    
    Actually, the server alias names can be any string you want.  However,
    you should use names that are unique in your network.
    
    Also, when you set up SQL Server, make sure you enable TCP/IP Sockets
    connections to the server.  (You can use SQL Setup "Change Network
    support" to enable this option.)
    
    After you do the steps I described above, you should be able to use
    ISQL/W to connect to "WilmaDatabases" or "BettyDatabases".  The
    connection will go to the server that currently has the corresponding
    databases online.