Thanks for your update and nice to know your issue has resolved!

But now, now question is , how can we trash a rssd database with minimal effort, as per your last post?

Please share your suggestions, guys. Thanks.

(01-20-2010 10:14 PM)asifm Wrote:  

(01-20-2010 04:28 PM)asifm Wrote:  Thanks for the response guys. I tried the suggestions above.

It appears that this error is a known bug in RS 15.5

I dont have any backups, but I have the 'go ahead' to trash the rssd and start again.......any ideas how to do this?

sorry guys, i've now resolved this. There was a (de)materialization queue hanging in the system and I simply dropped it with

sysadmin drop_queue queue number, queue type

I then had to clean up the stable queues with

sysadmin sqm_purge_queue queue number, queue_type

Finally, I quiesced the replication system and retstarted the server, problem solved! I'm not sure if this is a bug with RS 15.5, I have to verify this.....thanks guys!

I think you would just have to shutdown Rep Server and then dump/load a previous rssd ??

Or you can just blast away the rssd completely and start it from scratch....i'm not sure what the proper procedure would be..

Agreed ! I was thinking same, but suppose we dont have the latest rssd dump.


In that case, I am seeing only rssd setup from scratch , but suppose if we have very large setup in RSSD, it would be very time consuming and complicating, to build the replication setup again. Thats why I was thinking, any alternate way with minimal effort.

It also proofs one more point recommended by Sybase too, before doing any minor or major change in any system dbs, even for a single row , we should have latest backup, as Best DBA Practice.


If you guys/techsupport know any alternate way, kindly share with forum.

Thanks.