Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to up DSI?

207 views
Skip to first unread message

DS

unread,
Jun 11, 2004, 2:53:46 AM6/11/04
to
When I execute :

admin who_is_down

It shows both DSI and DSI EXEC are down, how can I activate them? Is it
related to table premissions? Pls advise.

Thanks,
DS


Michael Peppler

unread,
Jun 11, 2004, 3:47:08 AM6/11/04
to

There could be quite a few reasons why the DSI has shutdown.
I suggest looking at the rep server error log to see what the problem
might be.

You'll see something like:

E. 2004/06/08 23:24:24. ERROR #1028 DSI EXEC(114(1) LUTHOR.payment_db) - dsiqmint.c(2968)
Message from server: Message: 2601, State 6, Severity 14 -- 'Attempt to
insert duplicate key row in object 'PaymentStateHistory' with unique index 'PAYMENTSTATEHISTORY_PK'
'.
I. 2004/06/08 23:24:24. Message from server: Message: 3621, State 0, Severity 10 -- 'Command has been aborted.
'.
H. 2004/06/08 23:24:24. THREAD FATAL ERROR #5049 DSI EXEC(114(1) LUTHOR.payment_db) - dsiqmint.c(2975)
The DSI thread for database 'LUTHOR.payment_db' is being shutdown. DSI received data server error #2601 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 #5 of the failed transaction.
I. 2004/06/08 23:24:24. The DSI thread for database 'LUTHOR.payment_db' is shutdown.

In this case it was a 2601 error (dupicate key error). You'll need to
correct the cause of the error, and then resume the connection.

Michael
--
Michael Peppler Data Migrations, Inc.
mpep...@peppler.org http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or
long term contract positions - http://www.peppler.org/resume.html

Javier Jirón

unread,
Jun 11, 2004, 12:17:01 PM6/11/04
to
I, have the same problem, but not have a duplicate key, second data base
is a MS SQL Server, in the server log show:

E. 2004/06/11 04:47:39. ERROR #1028 DSI(103 msss.prueba) - seful/cm.c(2756)
Message from server: Message: 30000, State 0, Severity 16 -- 'Login
failure. <SMR>'.
E. 2004/06/11 04:47:39. ERROR #1027 DSI(103 msss.prueba) - seful/cm.c(2756)
Open Client Client-Library error: Error: 67175468, Severity 4 --
'ct_connect(): protocol specific layer: external error: The attempt to
connect to the server failed.'.
E. 2004/06/11 04:47:39. ERROR #13045 DSI(103 msss.prueba) - seful/cm.c(2760)
Failed to connect to server 'msss' as user 'sa'. See CT-Lib and/or
server error messages for more information.
I. 2004/06/11 04:47:39. The DSI thread for database 'msss.prueba' is
shutdown.

The user sa is correct, what is the problem, I need other user?

Jeff Tallman

unread,
Jun 11, 2004, 4:00:51 PM6/11/04
to

No - most likely the password for sa is incorrect....look in the rssd -
specifically at rs_maintusers
0 new messages