Kevin,
I would not use replication for U2 for 6x. I was given the mandate to use
then IBM replication at a company I used to work for, and it didn't work.
It wasn't on problem, but a whole hosts of problem. I set up two test boxes
four different times and tested it. The 4th time I had 30
We are using Double-Take to replicate.
--- On Wed, 12/9/09, BraDav broadri...@comcast.net wrote:
From: BraDav broadri...@comcast.net
Subject: Re: [U2] Unidata 6.1 Replication
To: U2 Users List u2-users@listserver.u2ug.org
Date: Wednesday, December 9, 2009, 8:33 AM
Kevin,
I would not use
Replication is QUITE useful at 7.1.20 and later I know -- we have lots of
people using it now!
Before this time, it had issues with large records, multiple overwrites one
the same key, etc. At 7.1.20 they also improved the monitoring.
Don't bother at less than 7.1.20 IMHO
David W.
Doubletake is an O/S answer -- but you cannot use the 'DoubleTake' data to
host a reporting server, can you? UniData Replication is great for being
able to have the database in two places at once with for either backup, hot
spare, or 'query only' access.
-Original Message-
From:
This may be a total red herring, but I would try setting both subroutine
arguments to something, not just the first one - even if you only set
them to String.Empty. How is the subroutine catalogued BTW?
As for your connection pooling issue - Make sure you are:
1. using a UniObjects DLL that
Awesome, great feedback my friends. Appreciate it very much.
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
I found a VMark article... written by Brian Leach... for UniData
indicating... Send an eMail to Vmark for UniVerse info.
Is the referenced companion article for UniVerse available. I am
struggling with setting up BCI on our HP-Ux machine. I have the IBM
10.3 BASIC SQL Client Interface Guide
which user did you install Universe as. They become the user with SQL DBA
rights.
Check the UV_USERS file which is documented in the SQL Catalog section of the
SQLREF guide
root needs DBAuth permission to be in this file.
Hope this guides you down the right path in resolving and understanding
You need to change the the READ parameter in the HS_FILE_ACCESS record
for the UV file to READ_WRITE, then run HS.UPDATE.FILEINFO in that
file's account. At that point a SQL insert to the file from the windows
side should be allowed. See the UV ODBC guide for more detailed info.
-John
