Welcome, Guest. Please login or register. Did you miss your activation email? Samker's Computer Forum - SCforum. SCF Advanced Search. SCF Portal Stats. January Reply Print. Quick Reply.
If the network location of a subscription server changes after subscriptions have been created, the publication server metadata must be updated with the new network location, otherwise a communication failure occurs between the publication server and the subscription server that is made apparent by the following message that appears when you open the EPRS Replication Console.
Step 1: The publication server whose metadata you want to change must be running. The Update Subscription Servers dialog box appears.
Step 3: Enter the new network location for each subscription server in the list whose network location has changed. If an error message appears, investigate and correct the cause of the error.
Step 5: If the subscription server with the new network location manages subscriptions associated with publications in other publication servers, repeat steps 1 through 4 for these other publication servers.
Release Notes. Installation and Uninstallation. Single-Master Replication Operation. Multi-Master Replication Operation. Common Operations. Selecting Tables with the Wildcard Selector. Creating a Schedule.
Managing a Schedule. Viewing Replication History. Managing History. Check the Save Login Information box. Step 4: Click the Update button. If the dialog box closes, then the update to the server login file was successful. If an error message appears after clicking the Update button, the server login file is not modified.
Investigate and correct the cause of the error. Repeat steps 1 through 4. This login information is used whenever a session needs to be established with the subscription database. See Section 5. The steps described in this section show you how to update the subscription database login information stored in the control schema should any of these attributes of the actual, physical database change. If you have already added subscriptions, you must not change any attribute that alters access to the schema where the subscription tables were created.
Attributes you must not change if there are existing subscriptions include the following:. The database server network location if the new network location references a database server that does not access the database that already contains the subscription tables.
The database identifier if the new database identifier references a different physical database than where the subscription tables already reside. Attributes you may change include the following:. The database server network location if the corresponding location change was made to the database server that accesses the subscription database. The database identifier such as the Oracle service name, SQL Server database name, or Postgres database name if the corresponding name change was made on the database server.
All attributes may be changed if there are no existing subscriptions. Step 1: Make sure the database server that you ultimately wish to save as the subscription database definition is running and accepting client connections. Step 2: Make sure the subscription server whose node is the parent of the subscription database definition you wish to change is running and has been registered in the xDB Replication Console you are using.
Step 3: Select the Subscription Database node corresponding to the subscription database definition that you wish to update. Alternatively, click the secondary mouse button on the Subscription Database node and choose Update Database. The Update Database Source dialog box appears. Step 5: Enter the desired changes. See Step 3 of Section 5. Step 6: Click the Test button. If an error message appears investigate the cause of the error, correct the problem, and repeat steps 1 through 6.
When a subscription is created, certain attributes of the subscribed publication are stored as part of the metadata for the subscription in the control schema. These include the following:. The network IP address of the host running the publication server that is the parent of the subscribed publication. The port number of the publication server. If the preceding attributes of the publication server change in the replication system environment, then the corresponding subscription metadata must also be changed so the subscription server can communicate with the correct publication server.
Step 1: Make sure the subscription server whose node is the parent of the subscription you wish to change is running and has been registered in the xDB Replication Console you are using. Step 2: Select the Subscription node whose attributes you wish to update. Step 3: From the Subscription menu, choose Update Subscription.
Alternatively, click the secondary mouse button on the Subscription node and choose Update Subscription.
0コメント