ERROR #1028 DSI Message 17231 No login with the specified name exists

[jmtorres]

Good day

A question regarding this error un rep server( threads in RS are down for 2 databases) :

E. 2016/03/08 15:17:32. ERROR #1028 DSI EXEC(124(1) huasco.FIN700_GLB) - neric/dsi/dsiqmint.c(4781)

>>>>  Message from server: Message: 17231, State 1, Severity 16 -- 'No login with the specified name exists.'. <<<<

H. 2016/03/08 15:17:32. THREAD FATAL ERROR #5049 DSI EXEC(124(1) huasco.FIN700_GLB) - neric/dsi/dsiqmint.c(4794)

  The DSI thread for database 'huasco.FIN700_GLB' is being shutdown. DSI received data server error #17231 which is mapped to STOP_REPLICATION. See logged data server errors for more information. The data server error was caused by output command #0 mapped from input command #0 of the failed transaction.

I. 2016/03/08 15:17:32. The DSI thread for database 'huasco.FIN700_GLB' is shutdown.

I. 2016/03/08 15:17:38. ...... connected to server 'huasco' as user 'priv_db_maint'.

E. 2016/03/08 15:17:38. ERROR #1028 DSI EXEC(121(1) huasco.priv_db) - neric/dsi/dsiqmint.c(4781)

>>>  Message from server: Message: 17231, State 1, Severity 16 -- 'No login with the specified name exists.'. <<<<

H. 2016/03/08 15:17:38. THREAD FATAL ERROR #5049 DSI EXEC(121(1) huasco.priv_db) - neric/dsi/dsiqmint.c(4794)

  The DSI thread for database 'huasco.priv_db' is being shutdown. DSI received data server error #17231 which is mapped to STOP_REPLICATION. See logged data server errors for more information. The data server error was caused by output command #0 mapped from input command #0 of the failed transaction.

I. 2016/03/08 15:17:38. The DSI thread for database 'huasco.priv_db' is shutdown.

Is it enough running  RESUME CONNECTON TO <DS>.<DB> SKIP TRANSACTION   to clear this error?

Thank you

Regards

Jose

[former_member285566 · Accepted solution]

Hi Jose,

You can log the system transaction before you skip it.

sysadmin log_first_tran, DS, DB

go

conenct to RSSD

go

rs_helpexception

go

Find the newly logged transaction ID <xact_id#> to display the DDL commmand

rs_helpexception <xact_id#>, v

go

disconnect

go

Then, you run "RESUME CONNECTION TO DS.DB SKIP TRANSACTION" to clear the error. Later you correct the logged command and apply it to the target database if it is needed.

Regards,

Binh Liu

[jmtorres]

Avinash/Binh Liu

Thanks a lot. !!

regards

Jose

[former_member89972]

On the RS  as 'sa' do

sysadmin log_first_tran, <ReplicateDS>, <ReplicateDB>

Then go to (e)RSSD and run rs_helpexception to get details of the latest transaction logged

Do following :

exec rs_helpexception <TXN>, 'v'

It will show the details of transaction being attempted at RDS+RDB

Skipping a transaction should be your last resort !!

On RDS + RDB try and fix what is causing the issue and then resume without skipping

HTH

Avinash