replication on informix v. 7.31
Hi All:
I am trying to get replication started with Informix 7.31. Once the physical
restore was complete on the secondary, the following commands were executed:
on primary = onmode -cl; onmode -d primary secondary1
on secondary = onmode -d secondary primary1
For reasons unknown, the synchronization of the logs is not happening. The
data replication status appears to be ready to accept logical logs. See onstat
-g dri below. When the onmode command is executed, the primary LAST DR Log is
from 1 week ago. I would expect the Last DR Ckpt to be the logical log that
was active when the backup started. The message logs from the primary and the
secondary server are below. Is there some other configuration or status that
needs to be reset before the replication can be turned on. Note: there are
other databases on each the primary and secondary for which replication was
activated without any problems. Any information is welcome.
Primary status before onmode -d command
Data Replication:
Type State Paired server Last DR CKPT (id/pg)
standard off -1 / -1
DRINTERVAL 5
DRTIMEOUT 90
DRAUTO 0
DRLOSTFOUND /informix/drlostfound/dr_s1.lostfound
Primary Message Log
16:07:11 Checkpoint Completed: duration was 0 seconds.
16:09:52 DR: new type = primary, secondary server name = secondary1
16:09:52 DR: Trying to connect to secondary server ...
16:09:59 DR: Primary server connected
16:09:59 DR: Server type incompatible
16:09:59 DR: Failure recovery error (2)
16:10:00 DR: Turned off on primary server
16:10:00 Process exited with return code 1: /bin/sh /bin/sh -c
/informix/bin/log_full_alarm.sh 3 15 "Data Replication f
ailure." "DR: Turned off on primary server"
16:10:01 Checkpoint Completed: duration was 0 seconds.
16:10:01 DR: Cannot connect to secondary server
16:10:02 Process exited with return code 1: /bin/sh /bin/sh -c
/informix/bin/log_full_alarm.sh 3 15 "Data Replication f
ailure." "DR: Cannot connect to secondary serv
16:10:14 DR: Primary server connected
16:10:16 DR: Server type incompatible
16:10:16 DR: Failure recovery error (2)
16:10:17 DR: Turned off on primary server
16:10:17 Checkpoint Completed: duration was 0 seconds.
Secondary message log
16:09:56 DR: new type = secondary, primary server name = primary1
16:09:56 Warning: Invalid dbspace 'tmpdbs01ifx1' listed in DBSPACETEMP.
16:09:56 Warning: Logging dbspace 'altdbsifx1' ignored in DBSPACETEMP on DR
secondary.
16:09:56 DR: Trying to connect to primary server ...
16:09:59 DR: Secondary server connected
16:09:59 DR: Server type incompatible
16:09:59 DR: Failure recovery error (2)
16:09:59 DR: Turned off on secondary server
16:09:59 Process exited with return code 1: /bin/sh /bin/sh -c
/informix/bin/log_full_alarm.sh 3 15 "Data Replication f
ailure." "DR: Turned off on secondary server"
16:10:14 DR: Secondary server connected
16:10:14 DR: Server type incompatible
16:10:14 DR: Failure recovery error (2)
16:10:15 DR: Turned off on secondary server
16:10:15 Process exited with return code 1: /bin/sh /bin/sh -c
/informix/bin/log_full_alarm.sh 3 15 "Data Replication f
ailure." "DR: Turned off on secondary server"
16:10:28 DR: Secondary server connected
16:10:28 DR: Server type incompatible
16:10:28 DR: Failure recovery error (2)
16:10:43 DR: Server state incompatible
16:10:55 DR: Server state incompatible
16:11:10 DR: Server state incompatible
16:11:26 DR: Server state incompatible
16:11:42 DR: Server state incompatible
Primary replication status after onmode -d command
Data Replication:
Type State Paired server Last DR CKPT (id/pg)
standard off secondary1 390438 / 2722
DRINTERVAL 5
DRTIMEOUT 90
DRAUTO 0
DRLOSTFOUND /informix/drlostfound/dr_s1.lostfound
I hope you are using the same IDS binaries for primary/secondary server.
Is primary/secondary on the same operating system with same patch level etc
?
Regards,
Nilesh
ids-bounces@iiug.org wrote on 05/14/2008 04:09:58 PM:
> Hi All:
>
> I am trying to get replication started with Informix 7.31. Once the
physical
> restore was complete on the secondary, the following commands were
executed:
>
> on primary = onmode -cl; onmode -d primary secondary1
>
> on secondary = onmode -d secondary primary1
>
> For reasons unknown, the synchronization of the logs is not happening.
The
> data replication status appears to be ready to accept logical logs.
> See onstat
> -g dri below. When the onmode command is executed, the primary LAST DR
Log is
> from 1 week ago. I would expect the Last DR Ckpt to be the logical log
that
> was active when the backup started. The message logs from the primary and
the
> secondary server are below. Is there some other configuration or status
that
> needs to be reset before the replication can be turned on. Note: there
are
> other databases on each the primary and secondary for which replication
was
> activated without any problems. Any information is welcome.
>
> Primary status before onmode -d command
> Data Replication:
> Type State Paired server Last DR CKPT (id/pg)
> standard off -1 / -1
>
> DRINTERVAL 5
> DRTIMEOUT 90
> DRAUTO 0
> DRLOSTFOUND /informix/drlostfound/dr_s1.lostfound>
> Primary Message Log
> 16:07:11 Checkpoint Completed: duration was 0 seconds.
> 16:09:52 DR: new type = primary, secondary server name = secondary1
> 16:09:52 DR: Trying to connect to secondary server ...
> 16:09:59 DR: Primary server connected
> 16:09:59 DR: Server type incompatible
> 16:09:59 DR: Failure recovery error (2)
> 16:10:00 DR: Turned off on primary server
> 16:10:00 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Turned off on primary server"
> 16:10:01 Checkpoint Completed: duration was 0 seconds.
> 16:10:01 DR: Cannot connect to secondary server
> 16:10:02 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Cannot connect to secondary serv
> 16:10:14 DR: Primary server connected
> 16:10:16 DR: Server type incompatible
> 16:10:16 DR: Failure recovery error (2)
> 16:10:17 DR: Turned off on primary server
> 16:10:17 Checkpoint Completed: duration was 0 seconds.
>
> Secondary message log
> 16:09:56 DR: new type = secondary, primary server name = primary1
> 16:09:56 Warning: Invalid dbspace 'tmpdbs01ifx1' listed in DBSPACETEMP.
> 16:09:56 Warning: Logging dbspace 'altdbsifx1' ignored in DBSPACETEMP on
DR
> secondary.
> 16:09:56 DR: Trying to connect to primary server ...
> 16:09:59 DR: Secondary server connected
> 16:09:59 DR: Server type incompatible
> 16:09:59 DR: Failure recovery error (2)
> 16:09:59 DR: Turned off on secondary server
> 16:09:59 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Turned off on secondary server"
> 16:10:14 DR: Secondary server connected
> 16:10:14 DR: Server type incompatible
> 16:10:14 DR: Failure recovery error (2)
> 16:10:15 DR: Turned off on secondary server
> 16:10:15 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Turned off on secondary server"
> 16:10:28 DR: Secondary server connected
> 16:10:28 DR: Server type incompatible
> 16:10:28 DR: Failure recovery error (2)
> 16:10:43 DR: Server state incompatible
> 16:10:55 DR: Server state incompatible
> 16:11:10 DR: Server state incompatible
> 16:11:26 DR: Server state incompatible
> 16:11:42 DR: Server state incompatible
>
> Primary replication status after onmode -d command
> Data Replication:
> Type State Paired server Last DR CKPT (id/pg)
> standard off secondary1 390438 / 2722
>
> DRINTERVAL 5
> DRTIMEOUT 90
> DRAUTO 0
> DRLOSTFOUND /informix/drlostfound/dr_s1.lostfound>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> LINDA COLE
> Sent: Wednesday, May 14, 2008 2:10 PM
> To: ids@iiug.org
> Subject: replication on informix v. 7.31 [12118]
>
> Hi All:
>
> I am trying to get replication started with Informix 7.31. Once the
> physical
> restore was complete on the secondary, the following commands were
> executed:
>
> on primary = onmode -cl; onmode -d primary secondary1
>
> on secondary = onmode -d secondary primary1
>
> For reasons unknown, the synchronization of the logs is not happening.
> The
> data replication status appears to be ready to accept logical logs.
See
> onstat> -g dri below. When the onmode command is executed, the primary LAST DR
> Log is
> from 1 week ago. I would expect the Last DR Ckpt to be the logical log
> that
> was active when the backup started. The message logs from the primary
> and the
> secondary server are below. Is there some other configuration or
status
> that
> needs to be reset before the replication can be turned on. Note: there
> are
> other databases on each the primary and secondary for which
replication
> was
> activated without any problems. Any information is welcome.
>
> Primary status before onmode -d command
> Data Replication:
> Type State Paired server Last DR CKPT (id/pg)
> standard off -1 / -1
>
> DRINTERVAL 5
> DRTIMEOUT 90
> DRAUTO 0
> DRLOSTFOUND /informix/drlostfound/dr_s1.lostfound>
> Primary Message Log
> 16:07:11 Checkpoint Completed: duration was 0 seconds.
> 16:09:52 DR: new type = primary, secondary server name = secondary1
> 16:09:52 DR: Trying to connect to secondary server ...
> 16:09:59 DR: Primary server connected
> 16:09:59 DR: Server type incompatible
> 16:09:59 DR: Failure recovery error (2)
> 16:10:00 DR: Turned off on primary server
> 16:10:00 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Turned off on primary server"
> 16:10:01 Checkpoint Completed: duration was 0 seconds.
> 16:10:01 DR: Cannot connect to secondary server
> 16:10:02 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Cannot connect to secondary serv
> 16:10:14 DR: Primary server connected
> 16:10:16 DR: Server type incompatible
> 16:10:16 DR: Failure recovery error (2)
> 16:10:17 DR: Turned off on primary server
> 16:10:17 Checkpoint Completed: duration was 0 seconds.
>
> Secondary message log
> 16:09:56 DR: new type = secondary, primary server name = primary1
> 16:09:56 Warning: Invalid dbspace 'tmpdbs01ifx1' listed in
DBSPACETEMP.
> 16:09:56 Warning: Logging dbspace 'altdbsifx1' ignored in DBSPACETEMP
> on DR
> secondary.
> 16:09:56 DR: Trying to connect to primary server ...
> 16:09:59 DR: Secondary server connected
> 16:09:59 DR: Server type incompatible
> 16:09:59 DR: Failure recovery error (2)
> 16:09:59 DR: Turned off on secondary server
> 16:09:59 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Turned off on secondary server"
> 16:10:14 DR: Secondary server connected
> 16:10:14 DR: Server type incompatible
> 16:10:14 DR: Failure recovery error (2)
> 16:10:15 DR: Turned off on secondary server
> 16:10:15 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/bin/log_full_alarm.sh 3 15 "Data Replication f
> ailure." "DR: Turned off on secondary server"
> 16:10:28 DR: Secondary server connected
> 16:10:28 DR: Server type incompatible
> 16:10:28 DR: Failure recovery error (2)
> 16:10:43 DR: Server state incompatible
> 16:10:55 DR: Server state incompatible
> 16:11:10 DR: Server state incompatible
> 16:11:26 DR: Server state incompatible
> 16:11:42 DR: Server state incompatible
>
> Primary replication status after onmode -d command
> Data Replication:
> Type State Paired server Last DR CKPT (id/pg)
> standard off secondary1 390438 / 2722
>
> DRINTERVAL 5
> DRTIMEOUT 90
> DRAUTO 0
> DRLOSTFOUND /informix/drlostfound/dr_s1.lostfound>
First off, I assume that "primary1" and "secondary1" are names of db
instances, NOT hostnames.
Assuming that, are the two servers trusted, i.e., via ~informix/.netrc
or /etc/hosts.equiv files?
What is in your sqlhosts file?
HTH,
Paul M.
primary1 and secondary1 are the aliases for the instances with corresponding
entries in the sqlhosts.
Primary Sqlhosts
primary1 onsoctcp 10.10.70.10 sqlexec_3
secondary1 onsoctcp 10.10.70.6 sqlexec_3
Secondary Sqlhosts
secondary1 onsoctcp 10.10.70.6 sqlexec_3
primary1 onsoctcp 10.10.70.10 sqlexec_3
The etc/services on both servers points to port 1540/tcp
Primary onconfig
DBSERVERALIASES primary1
Secondary onconfig
DBSERVERALIASES secondary1
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> LINDA COLE
> Sent: Thursday, May 15, 2008 6:44 AM
> To: ids@iiug.org
> Subject: Re: replication on informix v. 7.31 [12127]
>
> primary1 and secondary1 are the aliases for the instances with
> corresponding
> entries in the sqlhosts.
>
> Primary Sqlhosts
> primary1 onsoctcp 10.10.70.10 sqlexec_3
> secondary1 onsoctcp 10.10.70.6 sqlexec_3>
> Secondary Sqlhosts
> secondary1 onsoctcp 10.10.70.6 sqlexec_3
> primary1 onsoctcp 10.10.70.10 sqlexec_3>
> The etc/services on both servers points to port 1540/tcp
>
> Primary onconfig
> DBSERVERALIASES primary1>
> Secondary onconfig
> DBSERVERALIASES secondary1>
Looks like that *should* work. However, I always set up separate ports,
i.e.:
/etc/services (put BOTH entries on BOTH boxes):
sqlexec_3 1540/tcp
sqlexec_4 1541/tcp
Primary sqlhosts:
primary1 onsoctcp 10.10.70.10 sqlexec_3
secondary1 onsoctcp 10.10.70.6 sqlexec_4
Secondary sqlhosts:
secondary1 onsoctcp 10.10.70.6 sqlexec_4
primary1 onsoctcp 10.10.70.10 sqlexec_3
HTH,
Paul M.
Related threads
- Posting from the Informix-list
- Migrating from IDS 9.40.UC6 to 11.50.UC3
- Ip for a network session
- questions onstat -g