Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

How to make MSA to support "alter table ... modify"

7 posts in General Discussion Last posting was on 2012-03-10 08:52:38.0Z
Eisen Posted on 2012-03-08 03:13:12.0Z
Sender: 492c.4f580722.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: How to make MSA to support "alter table ... modify"
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f5823c8.4ffb.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 7 Mar 2012 19:13:12 -0800
X-Trace: forums-1-dub 1331176392 172.20.134.41 (7 Mar 2012 19:13:12 -0800)
X-Original-Trace: 7 Mar 2012 19:13:12 -0800, 172.20.134.41
Lines: 25
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9179
Article PK: 870342

Dear all
I've configured a MSA environment to do DDL replication,
but today one error raised --

H. 2012/03/08 10:20:50. THREAD FATAL ERROR #5049 DSI
EXEC(112(1) sybwpmdr00.fawpmmo0) - dsiqmint.c(4305)
The DSI thread for database 'sybwpmdr00.fawpmmo0' is
being shutdown. DSI received data server error #226 which is
mapped to STOP_REPLICATION. See logged data server errors
for more information. The data server error was caused by
output command #2 mapped from input command #1 of the failed
transaction.
I. 2012/03/08 10:20:50. The DSI thread for database
'sybwpmdr00.fawpmmo0' is shutdown.

I realized -- since in the manual it's said that the "alter
table" is supported in RS, but in practice, since my "alter
table ... modify" on primary side wiill be auto-packed with
a "begin tran... commit" by RS itself, so this "alter table
.. modify" will never be acceptable on the replicate side.
I'm wondering if there any configuration to this issue?
Thanks in advance for your help.

Best Regards
Eisen


"Mark A. Parsons" <iron_horse Posted on 2012-03-08 03:30:08.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: How to make MSA to support "alter table ... modify"
References: <4f5823c8.4ffb.1681692777@sybase.com>
In-Reply-To: <4f5823c8.4ffb.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4f5827c0$1@forums-1-dub>
Date: 7 Mar 2012 19:30:08 -0800
X-Trace: forums-1-dub 1331177408 10.22.241.152 (7 Mar 2012 19:30:08 -0800)
X-Original-Trace: 7 Mar 2012 19:30:08 -0800, vip152.sybase.com
Lines: 31
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9180
Article PK: 870345

I'd suggest you grab a copy of the transaction that brought down your DSI (eg, after the DSI goes down issue 'sysadmin
log_first_tran, sybwpmdr00, fawpmmo0').

It's not apparent from your post if a 'alter table' command is what brought down the DSI.

On 03/07/2012 20:13, Eisen wrote:
> Dear all
> I've configured a MSA environment to do DDL replication,
> but today one error raised --
>
> H. 2012/03/08 10:20:50. THREAD FATAL ERROR #5049 DSI
> EXEC(112(1) sybwpmdr00.fawpmmo0) - dsiqmint.c(4305)
> The DSI thread for database 'sybwpmdr00.fawpmmo0' is
> being shutdown. DSI received data server error #226 which is
> mapped to STOP_REPLICATION. See logged data server errors
> for more information. The data server error was caused by
> output command #2 mapped from input command #1 of the failed
> transaction.
> I. 2012/03/08 10:20:50. The DSI thread for database
> 'sybwpmdr00.fawpmmo0' is shutdown.
>
> I realized -- since in the manual it's said that the "alter
> table" is supported in RS, but in practice, since my "alter
> table ... modify" on primary side wiill be auto-packed with
> a "begin tran... commit" by RS itself, so this "alter table
> .. modify" will never be acceptable on the replicate side.
> I'm wondering if there any configuration to this issue?
> Thanks in advance for your help.
>
> Best Regards
> Eisen