IDS replication Solaris->Linux
Posted in 2000
Paul asked whether IDS 7.3 (or IDS 2000) could replicate from Solaris to a cheap Linux instance. Madison Pruet (Informix) answered that HDR won't work across different platforms, but Enterprise Replication (ER, the proper name for CDR) will; he also noted a few 7.31 features missing from 9.20 (e.g. ANSI outer join) that were restored in 9.21. Paul objected that ER rules out SERIAL columns, but Rudy Fernandes clarified that SERIAL can be used under ER — the documented caveats only matter when multiple databases are updated — so a simple primary-to-read-only-target setup should be fine.
Topics: Stored Procedures & SPL, Connectivity: ODBC / JDBC / .NET, Platform-Specific Issues, Versions, Editions & End-of-Life
I'm /currently/ running IDS v7.3 on Solaris. I would like to be able to replicate from this master server to a cheap-and-cheerful instance of IDS running on Linux. Firstly, is this possible with IDS 7.3? Instinct tells me that it isn't at the moment :*( However I've heard rumour that this is possible on IDS 2000 - is this true? And if so, are there any known "issues" migrating from IDS 7.3 to IDS 2000? Such as stored procedures, BLOBs, JDBC and Perl::DBI connectivity? Many thanks, Paul
ER can be used between solaris and Linux, HDR will not work. There were a few items in 7.31 that did not make it into 9.20, such as Ansi Outer Join, but the 9.21 release has 'caught-up' with the missing features. Paul Harman wrote: > I'm /currently/ running IDS v7.3 on Solaris. I would like to be able to > replicate from this master server to a cheap-and-cheerful instance of IDS > running on Linux. > > Firstly, is this possible with IDS 7.3? Instinct tells me that it isn't at > the moment :*( > > However I've heard rumour that this is possible on IDS 2000 - is this true? > And if so, are there any known "issues" migrating from IDS 7.3 to IDS 2000? > Such as stored procedures, BLOBs, JDBC and Perl::DBI connectivity? > > Many thanks, > > Paul -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================
Madison Pruet <mpruet@informix.com> wrote in message news:38B1A9B9.9183BF5D@informix.com... > ER can be used between solaris and Linux, HDR will not work. What's "ER"? Sorry to be a thicko, but I've only heard of CDR and HDR - and I know that I can't use CDR because of the serial problem. Paul
Madison Pruet <mpruet@informix.com> wrote in message news:38B2D101.520F1675@informix.com... > ER (Enterprise Replication) is the actual name for CDR. Oh. So let me get this straight: The only replication you can use Solaris->Linux is the one that means you can't use serials in any of your tables? What bloody use is *that* to man or beast? Paul
ER (Enterprise Replication) is the actual name for CDR. Paul Harman wrote: > Madison Pruet <mpruet@informix.com> wrote in message > news:38B1A9B9.9183BF5D@informix.com... > > ER can be used between solaris and Linux, HDR will not work. > > What's "ER"? Sorry to be a thicko, but I've only heard of CDR and HDR - and > I know that I can't use CDR because of the serial problem. > > Paul -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================
Actually, the serial column can be used under ER. Because of the nature of ER (unlike HDR, any of the DBs under ER may be updated), the obvious limitations of serial (serial on primary DB may be used by an independently inserted row on the secondary, serial built-in logic can be overridden by using a value) will apply. RTFM for more details on the limitations of serial under ER. If your replication is the simple Primary-Target with no updates on Linux, you should not have any problems. Rudy Paul Harman wrote: > Madison Pruet <mpruet@informix.com> wrote in message > news:38B2D101.520F1675@informix.com... > > ER (Enterprise Replication) is the actual name for CDR. > > Oh. > > So let me get this straight: > > The only replication you can use Solaris->Linux is the one that means you > can't use serials in any of your tables? > > What bloody use is *that* to man or beast? > > Paul
Rudy Fernandes <rferdy@americasm01.nt.com> wrote in message news:38B30AAD.C8550181@americasm01.nt.com... > Actually, the serial column can be used under ER. Because of the nature of > ER (unlike HDR, any of the DBs under ER may be updated), the obvious > limitations of serial (serial on primary DB may be used by an independently > inserted row on the secondary, serial built-in logic can be overridden by > using a value) will apply. RTFM for more details on the limitations of > serial under ER. > > If your replication is the simple Primary-Target with no updates on Linux, > you should not have any problems. Well I'll believe it when I see it, but thanks for the advice };*) - Yes, the intention is to have the primary Solaris machine handling all the updates and the Linux box will be a read-only one for searching and producing reports. Looking for the FM as we speak... };*) Paul