How to Upgrade a Replicated SQL 2000 MetaFrame XP Feature Release 3 Environment
How to Upgrade a Replicated SQL 2000 MetaFrame XP Feature Release 3 Environment How to Upgrade a Replicated SQL 2000 MetaFrame XP Feature Release 3 Environment
Citrix states in their article: CTX110738
Document ID: CTX110738, Created on: Aug 1, 2006, Updated: Aug 1, 2006
Products: Citrix MetaFrame Presentation Server 3.0 for Microsoft Windows 2000, Citrix MetaFrame Presentation Server 3.0 for Microsoft Windows 2003, Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft Windows 2003, Citrix Presentation Server 4.0 for Microsoft Windows 2000, Citrix Presentation Server 4.0 for Microsoft Windows 2003
Summary
This article describes the process of upgrading a replicated SQL 2000 MetaFrame XP Feature Release 3 environment to a MetaFrame Presentation Server 3.0 or a Citrix Presentation Server 4.0 environment.
Background
See CTX101739 – Microsoft SQL Server 2000 Data Store Replication.
Citrix Systems supports transactional replication with immediate updating subscribers because of the design of the data store database. The MetaFrame XP database is initially published with that version of the schema. When MetaFrame Presentation Server 3.0 was introduced, the data store schema was modified to make queries to the database more efficient. The schema was further modified with the addition of a new index on the Indextable which indexes Microsoft hotfix information. The schema modifications are as follows:
On MetaFrame Presentation Server 3.0:
New table: DELETETRACKER
New triggers: OnKeyTableDelete, OnKeyTableInsertUpdate
New column on the KEYTABLE: changestamp
On Citrix Presentation Server 4.0:
MetaFrame Presentation Server 3.0 schema
New index on the INDEXTABLE: INDEXTABLEINDEX2
Symptoms
When a MetaFrame XP server configured to point to the publisher database is upgraded to MetaFrame Presentation Server 3.0 or Citrix Presentation Server 4.0, it successfully modifies the existing schema of the publisher (also referred to as the master) data store database to the current version. These changes are not replicated to the subscriber database.
When a server that is configured to point to the subscriber database is upgraded to 3.0 or 4.0, it successfully upgrades the subscriber (also referred to as the replica) schema to the newest version.
When replication is reinitialized for any reason, the original publication schema is replicated out to all of the subscribers. This modifies the existing schema with the one contained in the publication (MetaFrame XP Feature Release 3) since it is not modified during the upgrade process.
At this point the subscription data store schema has now been reverted back to the original MetaFrame XP Feature Release 3 schema.
When any MetaFrame Presentation Server 3.0 or Citrix Presentation Server 4.0 server that has been configured to point to this subscriber either has the IMA Service restarted or the server is rebooted, the IMA Service fails to start because it cannot find the changestamp column on the KEYTABLE.
Resolution
Caution! Before beginning the upgrade process, replication must be disabled between all replicated sites by deleting the publication and its corresponding subscriptions.
Upgrade the data collector that is configured to point to the SQL server designated as the publisher to MetaFrame Presentation Server 3.0 or Citrix Presentation Server 4.0.
Have the database administrator (DBA) verify that the updated schema articles have been created in the upgraded database.
Re-publish the updated Presentation Server database and reconfigure replication to the previous subscription sites following the steps documented in CTX101739 – Microsoft SQL Server 2000 Data Store Replication.
Ensure that the updated schema is replicated to the new subscription sites.
More Information
See CTX109394 – Upgraded MetaFrame XP Servers to Presentation 3.0 or 4.0 using SQL Replication Fail to Replicate New Schema Changes.
User login
Who's new
- Choodogek
- zepsleltpap
- layersepavy
- moneytome12
- maczugaher