Sybase proxy tables synchronize across server data

Sybase ASE Proxy table synchronizes across server data

Before double did the Sybase server data synchronization, use the proxy table. Recently replaced Server1, the initial installation of Sybase when the local server name is different, SERVER1 data directly dump, the completion of the data can be read, but in the execution of proxy table data inserted into the local table in the wrong times. After query

SELECT @ @servername

This place name is DB3

Query the original server named charge

Delete formerly

Sp_dropserver DB3

Set a new name, which is the original Server1 name

sp_addserver charge,local

Restart Sybase to take effect.

Execute the stored procedure again, synchronize the data and insert successfully.

Another: I have Sybase version, 12.5.2. Another 12.5.3 Chinese version of the patch upgrade package, online query days without fruit, recover hard disk data obtained. Use OK. Contact me in need: [email protected]

The details of establishing the proxy table synchronization steps are as follows (for reference):

1. Verify that the system Component Integration Services (CIS) is configured correctly.

A turn on CIS components

Use master

sp_configure "Enable CIS", 1

If you set this option, you will need to restart the server to take effect. This feature component is turned on by default after ASE-12.

b Configuring RPC

In ASE-15, this setting defaults to 0 and needs to be turned on

sp_configure "cis RPC handling", 1

C Set the allowed maximum number of connections for CIS

In ASE-15, this setting defaults to 0 and is best tuned to more than 20.

sp_configure "max CIS remote Connections", 20

D Set the allowed maximum number of connections for CIS

2. Add the interfaces server information in both server

Interfaces files in vi/syb64bit/ase-15/

Add local server name

Use the isql connection to enter the server Server1,server2

1>select @ @servername

2>go

To determine that the server local name is in effect

If NULL is returned,

1>sp_addserver server_name,local

2>go

server_name should be consistent with the server name used in interfaces

Remove existing server local name

Sp_dropserver server_name

Restart the server and let the local name take effect, confirming that the CIS integration service is started.

3. Add remote server information and login information

A adding remote server information

Execute the following command on the Server1:

Isql-usa-p-sserver1

exec sp_addserver Server2, asenterprise, Server2

B. Adding remote login information

Isql-usa-p-sserver1

exec sp_addremotelogin Server2, SA, SA

exec sp_remoteoption Server2, SA, SA, trusted, true

Go

Or

Isql-usa-p-sserver1

exec sp_addexternlogin Server2, SA, SA, xxxxxx (xxxxxx password for SA on remote server Server2) (may not be SA, the user will have logon rights)

4, Build proxy table

Set up tables in Server2 database PUBS2 t_testproxy

CREATE TABLE T_testproxy (ID int,name char (10))

Adding proxy table information to the SERVER1 database test

Use test

Go

Create Proxy_table t_testproxy at "Server2.pubs2.dbo.t_testproxy"

Proxy table name can be different from the original table name

5. Scripts

A success Script

sp_addserver Shz_tulip01_srv,asenterprise,shz_tulip01_srv

Sp_addexternlogin Shz_tulip01_srv,tulip,tulip,password

Create Proxy_table Tulip. Usr00noc at "SHZ_TULIP01_SRV.tulipdb.tulip.USR00NOC"

Grant SELECT on Tulip. Usr00noc to Tulip

b Delete script on failure

Sp_dropserver Shz_tulip01_srv

Sp_dropexternlogin Shz_tulip01_srv,tulip

drop table Tulip. Usr00noc

Sybase proxy tables synchronize across server data