dbTalk Databases Forums  

Error #1028 Dsi Exec

comp.databases.sybase comp.databases.sybase


Discuss Error #1028 Dsi Exec in the comp.databases.sybase forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
nileshpathak
 
Posts: n/a

Default Error #1028 Dsi Exec - 07-08-2003 , 05:56 AM







Hello,

Please check the error log showing in my replication log.

E. 2003/07/04 17:51:50. ERROR #1028 DSI EXEC(105(1) db name) - ds
iqmint.c(2774)
Message from server: Message: 1622, State 2, Severity 18 --
'Type '1' no
t implemented.
H. 2003/07/04 17:51:50. THREAD FATAL ERROR #5049 DSI EXEC(105(1) db
name) - dsiqmint.c(2781)
The DSI thread for database db name' is being shutdown.
DSI received data server error #1622 which is mapped to
STOP_REPLICATION. See logged data server errors for more information.
The data server error was caused by output command #1 mapped from input
command #15873 of the failed transaction.


Anyone having any idia whats going worng?

--
Posted via http://dbforums.com

Reply With Quote
  #2  
Old   
Jason
 
Posts: n/a

Default Re: Error #1028 Dsi Exec - 07-09-2003 , 06:35 AM






nileshpathak wrote:
Quote:
Hello,

Please check the error log showing in my replication log.

E. 2003/07/04 17:51:50. ERROR #1028 DSI EXEC(105(1) db name) - ds
iqmint.c(2774)
Message from server: Message: 1622, State 2, Severity 18 --
'Type '1' no
t implemented.
H. 2003/07/04 17:51:50. THREAD FATAL ERROR #5049 DSI EXEC(105(1) db
name) - dsiqmint.c(2781)
The DSI thread for database db name' is being shutdown.
DSI received data server error #1622 which is mapped to
STOP_REPLICATION. See logged data server errors for more information.
The data server error was caused by output command #1 mapped from input
command #15873 of the failed transaction.


Anyone having any idia whats going worng?

--
Posted via http://dbforums.com
Whenever I get these obscure messages I log on to www.sybase.com/support
andd go to the solved cases area. Just type in the error number (in
this case 1622) and see if anyone else has had the problem.

The one case I found had the following resolution:
Customer found that 1622 was being raised when the application was
passing a varbinary(258) where as the maximum is 255. Made application
changes to pass varbinary(255) and that took care of both the errors.

Question - What versions of primary/replicate servers are you using ?
What was the results of syadmin log_first_tran ?
Are you trying to replicate a data type which is not supported at the
replicate ?

Cheers,
Jason



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.