|
Based on the location of the assertion in the code that you provided, the tool has determined that there is a difference between at least one publications that has a synchronization subscription associated with it, but when it goes to iterate through the publication to determine the exact difference so it can generate a START SYNCHRONIZATION SCHEMA CHANGE statement, it doesn't find any real differences and asserts. We would need the reload.sql generated when you run dbunload -n against the two databases to figure out exactly what's going wrong here. Reg 2
Thanks Reg! With this lead, we were able to make some adjustments to publications and synchronization subscriptions and this error does not populate now.
(14 Jun, 08:59)
bgreiman
|
Please be aware that the SAP SQL Anywhere Forum will be shut down on August 29th, 2024 when all it's content will be migrated to the SAP Community.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 11 Jun, 14:22
question was seen: 259 times
last updated: 14 Jun, 08:59
I should mention we are using v17.0.11.7312 at each database.
Is there a stack that is generated?
This is what shows in the UI: An unknown error has occurred. java.lang.AssertionError
In the Event Viewer: : [13136] 07:26:11 ***ERROR (:0): Java assert: Assertion in sybase.dbcloud.dbdiff.Dbdiff.getStartSyncSchemaChangeStatement(Dbdiff.java:919)
If it helps, the assertion in dbdiff is "assert !schemaChangeSubscriptions.isEmpty()".