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.

Why DDL error in DSI can't be resumed?

3 posts in General Discussion Last posting was on 2012-04-27 03:17:13.0Z
Eisen Posted on 2012-04-26 03:52:05.0Z
Sender: 7246.4f98c2c9.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Why DDL error in DSI can't be resumed?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f98c665.72f4.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 25 Apr 2012 20:52:05 -0700
X-Trace: forums-1-dub 1335412325 172.20.134.41 (25 Apr 2012 20:52:05 -0700)
X-Original-Trace: 25 Apr 2012 20:52:05 -0700, 172.20.134.41
Lines: 43
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9202
Article PK: 870364

Dear all
Today in a MSA environment, someone create a user table
by "select into" from a temporary table on source site, so
this table was not created on replciate site in sync. And
after a while he/she dropped that user table by explict
"drop table " statement, and this statement made DSI down.
Here is the error message:
E. 2012/04/26 11:14:10. ERROR #1028 DSI EXEC(112(1)
sybwpmdr00.fawpmmo0) - dsiqmint.c(4292)
Message from server: Message: 3701, State 1, Severity 11 --
'Cannot drop the table 'TEMP_WR', because it doesn't exist
in the system catalogs.
'.
H. 2012/04/26 11:14:10. 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 #3701 which is
mapped to STOP_REPLICATION. See logged data server errors
for more information. The data server error was caused by
output command #5 mapped from input command #1 of the failed
transaction.

I found this, and create a same user table with same name on
replicate site and execute "resume connection to " to resume
DSI, I think the RS can drop that table and go on with
followed trans in queue. But to my surprise I found RS can't
push forward to drop that table and always reported --
E. 2012/04/26 11:32:27. ERROR #5152 DSI(112
sybwpmdr00.fawpmmo0) - dsisched.c(3989)
There is a system transaction whose state is not known. DSI
will be shutdown.
I. 2012/04/26 11:32:27. The DSI thread for database
'sybwpmdr00.fawpmmo0' is shutdown.

Until I used "resume connection ... skip tran", then the DSI
got up. Then I checked the exception in RSSD, and found it's
only one "drop table TEMP_WR". I can't understand why RS
can't drop the table I created on replicate site? Would
anyone kindly explain it to me? Thanks in advance for any
help.

Best Regards
Eisen


Luc Van der Veurst Posted on 2012-04-26 11:27:47.0Z
From: "Luc Van der Veurst" <dba_azvub@hotmail.com>
Newsgroups: sybase.public.rep-server
References: <4f98c665.72f4.1681692777@sybase.com>
Subject: Re: Why DDL error in DSI can't be resumed?
Lines: 71
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-RFC2646: Format=Flowed; Original
X-Forwarded: by - (DeleGate/5.8.7)
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4f993133@forums-1-dub>
Date: 26 Apr 2012 04:27:47 -0700
X-Trace: forums-1-dub 1335439667 10.22.241.152 (26 Apr 2012 04:27:47 -0700)
X-Original-Trace: 26 Apr 2012 04:27:47 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9203
Article PK: 870367

Hi,

The message you got is :

> E. 2012/04/26 11:32:27. ERROR #5152 DSI(112
> sybwpmdr00.fawpmmo0) - dsisched.c(3989)
> There is a system transaction whose state is not known. DSI
> will be shutdown.

User transactions are executed at the replicate site by the maintenance
user,
but DDL transactions are executed with the same logon as they were
executed on the primary site. Therefore the name 'system transaction'.

You have to include the option 'execute transaction' when you resume the
connection.

Rob's replication server book mentions that this option should only be
used when you get error 5152.
Exact the error you reported.

Hth,
Luc.


<Eisen> wrote in message news:4f98c665.72f4.1681692777@sybase.com...
> Dear all
> Today in a MSA environment, someone create a user table
> by "select into" from a temporary table on source site, so
> this table was not created on replciate site in sync. And
> after a while he/she dropped that user table by explict
> "drop table " statement, and this statement made DSI down.
> Here is the error message:
> E. 2012/04/26 11:14:10. ERROR #1028 DSI EXEC(112(1)
> sybwpmdr00.fawpmmo0) - dsiqmint.c(4292)
> Message from server: Message: 3701, State 1, Severity 11 --
> 'Cannot drop the table 'TEMP_WR', because it doesn't exist
> in the system catalogs.
> '.
> H. 2012/04/26 11:14:10. 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 #3701 which is
> mapped to STOP_REPLICATION. See logged data server errors
> for more information. The data server error was caused by
> output command #5 mapped from input command #1 of the failed
> transaction.
>
> I found this, and create a same user table with same name on
> replicate site and execute "resume connection to " to resume
> DSI, I think the RS can drop that table and go on with
> followed trans in queue. But to my surprise I found RS can't
> push forward to drop that table and always reported --
> E. 2012/04/26 11:32:27. ERROR #5152 DSI(112
> sybwpmdr00.fawpmmo0) - dsisched.c(3989)
> There is a system transaction whose state is not known. DSI
> will be shutdown.
> I. 2012/04/26 11:32:27. The DSI thread for database
> 'sybwpmdr00.fawpmmo0' is shutdown.
>
> Until I used "resume connection ... skip tran", then the DSI
> got up. Then I checked the exception in RSSD, and found it's
> only one "drop table TEMP_WR". I can't understand why RS
> can't drop the table I created on replicate site? Would
> anyone kindly explain it to me? Thanks in advance for any
> help.
>
> Best Regards
> Eisen


Eisen Posted on 2012-04-27 03:17:13.0Z
Sender: 7d5e.4f9911d7.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Re: Why DDL error in DSI can't be resumed?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f9a0fb9.266c.1681692777@sybase.com>
References: <4f993133@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 26 Apr 2012 20:17:13 -0700
X-Trace: forums-1-dub 1335496633 172.20.134.41 (26 Apr 2012 20:17:13 -0700)
X-Original-Trace: 26 Apr 2012 20:17:13 -0700, 172.20.134.41
Lines: 77
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9206
Article PK: 870368

Hi Luc
I got it. Thanks a lot.

Best Regards
Eisen

> Hi,
>
> The message you got is :
>
> > E. 2012/04/26 11:32:27. ERROR #5152 DSI(112
> > sybwpmdr00.fawpmmo0) - dsisched.c(3989)
> > There is a system transaction whose state is not known.
> > DSI will be shutdown.
>
> User transactions are executed at the replicate site by
> the maintenance user,
> but DDL transactions are executed with the same logon as
> they were executed on the primary site. Therefore the name
> 'system transaction'.
>
> You have to include the option 'execute transaction' when
> you resume the connection.
>
> Rob's replication server book mentions that this option
> should only be used when you get error 5152.
> Exact the error you reported.
>
> Hth,
> Luc.
>
>
> <Eisen> wrote in message
> > news:4f98c665.72f4.1681692777@sybase.com... Dear all
> > Today in a MSA environment, someone create a user
> > table by "select into" from a temporary table on source
> > site, so this table was not created on replciate site in
> > sync. And after a while he/she dropped that user table
> > by explict "drop table " statement, and this statement
> > made DSI down. Here is the error message:
> > E. 2012/04/26 11:14:10. ERROR #1028 DSI EXEC(112(1)
> > sybwpmdr00.fawpmmo0) - dsiqmint.c(4292)
> > Message from server: Message: 3701, State 1, Severity 11
> > -- 'Cannot drop the table 'TEMP_WR', because it doesn't
> > exist in the system catalogs.
> > '.
> > H. 2012/04/26 11:14:10. 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 #3701
> > which is mapped to STOP_REPLICATION. See logged data
> > server errors for more information. The data server
> > error was caused by output command #5 mapped from input
> > command #1 of the failed transaction.
> >
> > I found this, and create a same user table with same
> > name on replicate site and execute "resume connection to
> > " to resume DSI, I think the RS can drop that table and
> > go on with followed trans in queue. But to my surprise I
> > found RS can't push forward to drop that table and
> > always reported -- E. 2012/04/26 11:32:27. ERROR #5152
> > DSI(112 sybwpmdr00.fawpmmo0) - dsisched.c(3989)
> > There is a system transaction whose state is not known.
> > DSI will be shutdown.
> > I. 2012/04/26 11:32:27. The DSI thread for database
> > 'sybwpmdr00.fawpmmo0' is shutdown.
> >
> > Until I used "resume connection ... skip tran", then the
> > DSI got up. Then I checked the exception in RSSD, and
> > found it's only one "drop table TEMP_WR". I can't
> > understand why RS can't drop the table I created on
> > replicate site? Would anyone kindly explain it to me?
> > Thanks in advance for any help.
> >
> > Best Regards
> > Eisen
>
>