Re: Domino DB access in a High Availability environment. -- DOMINO400

Your deployment is unique. I think you will need to engage someone that
can take the time to consider all your unique configuration solutions.

Walter Scanlan
Senior Software Engineer
Sent from Lotus Traveler

rob@xxxxxxxxx --- Re: Domino DB access in a High Availability environment.
---

From: "" <rob@xxxxxxxxx>
To "Lotus Domino on the iSeries / AS400" <domino400@xxxxxxxxxxxx>
Date: Wed, Dec 19, 2012 8:13 AM
Subject Re: Domino DB access in a High Availability environment.

--------------------------------------------------------------------------

Right now I have SystemA.
SystemA runs our ERP and has domino servers DOM01A, DOM02A, DOM03A,
DOM04A.
SystemB is a Mimix backup of our ERP and has no domino data or software.
Mail2 has Domino servers DOM01B, DOM02B, DOM03B, DOM04B.
Mail3 has Domino servers DOM01C, DOM02C, DOM03C, DOMP4C.
DOM01A, DOM01B, DOM01C are clustered.
DOM02A, DOM02B, DOM02C are clustered.
and so on.

On Mail2 we have
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(system *IP)
On SystemA we have
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
On systemB we have the same
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
Notice, no rdb for either systema or systemb? Instead systemA and systemB

both think their local entry is just system.

If a domino application running on DOM01B on Mail2 tries to execute
If Not Con.ConnectTo ("SYSTEM", "UserID", "Password") Then Exit sub
and our DNS points SYSTEM to the same IP address as systemA then it should

connect to systemA and process.
If during the switch the dns starts pointing SYSTEM to the same IP address

as systemB then the domino app should process DB2 data on systemB.

The problem is if you run Domino on the same server as your DB2 server, as

we do with DOM01A on SystemA, then it will ignore the DNS and run the
Domino application on the local system because of the ADDRDBDIRE there for

SYSTEM.

If I change SystemA from
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
to
ADDRDBDIRE RDB(SYSTEMA) RMTLOCNAME(*LOCAL *IP)
and SystemB from
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
to
ADDRDBDIRE RDB(SYSTEMB) RMTLOCNAME(*LOCAL *IP)
and try the sample code of
If Not Con.ConnectTo ("SYSTEMA", "UserID", "Password") Then Con.ConnectTo
("SYSTEMB", "UserID", "Password")
The application will try to connect to SYSTEMA as soon as it can. but we
may not want it to because we're in failover mode and while you can
connect to systema we'd rather you process the data on systemb and let
Mimix replicate the changes over.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Walter Scanlan <wscanlan@xxxxxxxxxx>
To: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>,
Cc: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>,
domino400-bounces@xxxxxxxxxxxx
Date: 12/19/2012 08:37 AM
Subject: Re: Domino DB access in a High Availability environment.
Sent by: domino400-bounces@xxxxxxxxxxxx

On System b, If you don't have a WRKRDBDIRE for SYSTEM A , the Domino
server on System b has no route to connect to system A for SQL.

Walter Scanlan
Senior Software Engineer
Certified L3 Senior IT Specialist
WPLC & Cloud Computing
Office: 1 720 342 5837
Cell: 507-990-4539

From: rob@xxxxxxxxx
To: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
Date: 12/19/2012 06:52 AM
Subject: Re: Domino DB access in a High Availability environment.
Sent by: domino400-bounces@xxxxxxxxxxxx

Nice idea. However, if Domino is running on SYSTEMA wouldn't the
Con.ConnectTo say it worked? But when I actually tried to access the data

it would error out because Mimix has a lock on all the DB2 data to prevent

someone from accessing this system when they should be accessing the other

system?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Walter Scanlan <wscanlan@xxxxxxxxxx>
To: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>,
Cc: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>,
domino400-bounces@xxxxxxxxxxxx
Date: 12/18/2012 07:17 PM
Subject: Re: Domino DB access in a High Availability environment.
Sent by: domino400-bounces@xxxxxxxxxxxx

Oh,
Easy

If Not Con.ConnectTo ("SYSTEMA", "UserID", "Password") Then Con.ConnectTo

("SYSTEMB", "UserID", "Password")

Walter Scanlan
Senior Software Engineer
Certified L3 Senior IT Specialist
WPLC & Cloud Computing
Office: 1 720 342 5837
Cell: 507-990-4539

From: rob@xxxxxxxxx
To: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
Date: 12/18/2012 10:20 AM
Subject: Re: Domino DB access in a High Availability environment.
Sent by: domino400-bounces@xxxxxxxxxxxx

We do not replicate any Domino data via Mimix. Repeat, we omit all Domino

directories from the IFS from Mimix replication. There is no Domino data
on SystemB. Domino is not even loaded on SystemB.
All Domino data is replicated using Domino clustering only. Domino
servers on SystemA are clustered with Domino servers on mail2 and with
Domino servers on mail3.

What I am trying to solve is, let's say you have a Domino database. Let's

call it MfgPortal.nsf. And in that database you have some code like the
following (see SYSTEMA below):

Option Public
Option Declare

UseLSX "*LSXODBC"

Sub Initialize
Dim Con As New ODBCConnection
Dim Query As New Odbcquery
Dim rs As New Odbcresultset

Con.SilentMode = True

If Not Con.ConnectTo ("SYSTEMA", "UserID", "Password") Then Exit
sub

Set query.Connection = Con

query.SQL = "Select iprod, idesc from erplxf.iiml01"

Set rs.Query = query

rs.cacheLimit = 200
rs.FetchBatchSize = 100

If Not rs.Execute Then Exit Sub

If rs.Isendofdata() Then Exit Sub

rs.Nextrow
Print rs.Getvalue("iprod")+" - "+rs.Getvalue("idesc")

rs.Close(DB_CLOSE)
Con.Disconnect

End Sub

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Walter Scanlan <wscanlan@xxxxxxxxxx>
To: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>,
Cc: domino400-bounces@xxxxxxxxxxxx
Date: 12/18/2012 10:20 AM
Subject: Re: Domino DB access in a High Availability environment.
Sent by: domino400-bounces@xxxxxxxxxxxx

It would appear rather than using Domino clustering you are trying to use
the foundations of Cluster proven.
(Are you ASP switching or are you trying to use mimix to cluster
the IFS rather than Domino clustering).
Assuming you don't want immediate access to the application (which Domino
cluster provides),
Here are the concerns I would have.
ASP swtich,
If Domino crashes (unscheduled outage) on SystemA before the data
can be read on Systemb a consistency check of data will be required.
TLogging will not work as the server names are not the
same.
If the databases are large this can take a long time.

Mimix replication of IFS data.
I would defer to your vender but I have a couple of customers
trying to do this and all are still working on feature issues with mimix.
The biggest issue is write lock management, but again, contact
your vendor.
My experience has been you will not have complete data on a
mirror.

Walter Scanlan
Senior Software Engineer
Certified L3 Senior IT Specialist
WPLC & Cloud Computing
Office: 1 720 342 5837
Cell: 507-990-4539

From: rob@xxxxxxxxx
To: domino400@xxxxxxxxxxxx
Date: 12/18/2012 08:58 AM
Subject: Domino DB access in a High Availability environment.
Sent by: domino400-bounces@xxxxxxxxxxxx

Let's say I have a Domino server, Domino01, on SystemA.
Now I drop that Domino server.
I also perform an H/A switch (Mimix in our shop). So instead of running
DB2 on SystemA it's now running on SystemB. And people are running their
Domino applications on Domino server Domino02 on SystemC.
If I follow the instructions in these two links will this behave?
http://visionsolutions.custhelp.com/app/answers/detail/a_id/3067/p/350
http://www-912.ibm.com/8625680A007CA5C6/1AC66549A21402188625680B0002037E/31D82AB263AE401F8625717E0068D44F

Now let me complicate the issue a little bit.
I did this switch on Friday night. On Saturday afternoon our work is
pretty much done. However we don't switch back until Sunday night at 6pm
so that the brief outage during the switch is consistent and shipping can
be planned around it. But I figure, why not start Domino01 on SystemA at
this time? So, if I have an application running on Domino01 will it try
to access DB2 locally, or, will it behave and access DB2 on SystemB?

Let me give a little more information.
During this switch we modify our DNS to point 'System' from the ip address

associated with SystemA to the IP address associated with SystemB.
However, I've run into a few applications which INSIST that there be an
actual host table entry on SystemA for System.
Knowing this, I suspect Domino would use the host table entry, and the
WRKRDBDIRE entries, locally and keep trying to connect to DB2 on SystemA.

Is this the incentive to create a new lpar, let's call it MAIL1, and move
the Domino servers off of SystemA and put them on MAIL1? Actually, this
would be more in keeping with our other servers. We have a mail2
(strictly for Domino) separate from SystemB. And we have a mail3. Guess
where Domino2 and Domino3 run?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

_________________________
______________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_________________________
______________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_________________________
______________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_________________________
______________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_________________________
______________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_________________________
______________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.

_________________________
______________________
This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
To post a message email: Domino400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/domino400
or email: Domino400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.