Error #1028 Dsi Exec

Error #1028 Dsi Exec

Post by nileshpatha » Wed, 09 Jul 2003 18:56:30



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

 
 
 

Error #1028 Dsi Exec

Post by Jaso » Thu, 10 Jul 2003 19:35:29



> 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