> Hi,
>
> I am new to replication and sybase. I have configured
> replication using one warm standby ASE server. I am
> wondering what is causing this errors at the rep server - as
> both databases are in sync. No errors are reported in my
> primary server so why are they occuring in the rep server?
>
> E. 2009/02/19 14:52:19. ERROR #1028 DSI EXEC(104(1)
> mscrown.msdata) - dsiqmint.c(3249)
> Severity 14 -- 'Attempt to insert duplicate key row in
> object 'file_version' with unique index 'idx_f
> ile_ver_file_id'
> '.
> I. 2009/02/19 14:52:19. Message from server: Message: 3621,
> State 0, Severity 10 -- 'Command has been aborted.
> '.
> H. 2009/02/19 14:52:19. THREAD FATAL ERROR #5049 DSI
> EXEC(104(1) mscrown.msdata) - dsiqmint.c(3256)
> being shutdown. DSI received data server error #2601 which
> is mapped to STOP_REPLICATION. See logg
> ed data server errors for more information. The data server
> error was caused by output command #1 mapped from input
> command #3 of the failed transaction.
> I. 2009/02/19 14:52:19. The DSI thread for database
> 'mscrown.msdata' is shutdown.
>
> How can I configure my database so these errors no longer
> occur?
>
> If there isnt a complaint in my primary about duplicate rows
> I dont understand how these exist in the rep server?
>
> Thanks a million,
>
> Lorraine
There are various reasons why you see "duplicate key" errors at
replicate but not at primary
(1) check if you have same type of indexes in primary and replicate
(2) check if you are replicating identity columns which is causing
"duplicate key" error
(3) check if you have triggers enabled at replicate side
(4) check if the data is out of sync at replicate
You stated that data is in sync in primary and replicate therefore
check first 3 points.Whenever you see duplicate key issue, go to
replicate replication server and execute sysadmin log_first_tran , go
to ASE server hosting RSSD and check exception log by issuing
sp_helpexception id,v and see what is causing duplicate key issue
> I did think about create error_classes but is this just avoiding the issue?
That is right, its not a good idea to create error_classes to avoid
duplicates, it might cause replicate database to go out of sync
-HTH
Manish Negandhi
[TeamSybase]
|