Cchetty: 1 revision

2010-12-10T02:49:56Z

1 revision

← Older revision

Revision as of 02:49, 10 December 2010

Cchetty: /* Configuration data is not synchronized between Primary and Secondary Servers */

2010-11-24T19:20:26Z

Configuration data is not synchronized between Primary and Secondary Servers

New page

== Configuration data is not synchronized between Primary and Secondary Servers ==

{| border="1"
|-
! '''Problem Summary'''
| When Secondary Server joins Primary Server in the same cluster, configuration data is not synchronized between the two servers after all services are activated on Secondary Node.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| This happens because, when Secondary Node joins the cluster, it takes a data snapshot from Primary Node, and then sets up data replication. There is a small window between the two steps, during which data will get out of sync between the two servers.
|-
! '''Recommended Action'''
|
Run the following CLI command on Secondary Node after all services are activated, to sync up config data with Primary Node:

<blockquote><code>run db_synchronization db_ora_config</code></blockquote>

That command will launch Informix data repair jobs. Run the following CLI command on Secondary Node to monitor the status of the jobs:

<blockquote><code>show db_synchronization status db_ora_config </code></blockquote>

When all status is "C" (completed), jobs have completed successfully and config data is in sync between the two nodes.

See the ''Installation and Admin Guide for Cisco Media Capture Platform'', Chapter 8, for more information on the CLIs.
|-
! '''Release'''
| Release 8.5(1).
|-
! '''Associated CDETS #'''
| CSCti87080
|-
|}

[[Category:Cisco MediaSense, Release 8.5]]

Configuration: Configuration data is not synchronized between Primary and Secondary Servers - Revision history

Cchetty: 1 revision

Cchetty: /* Configuration data is not synchronized between Primary and Secondary Servers */