Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 349384

Summary: [DB] Table Creation does not occur when using raw replication with offline clone and Derby database
Product: [Modeling] EMF Reporter: Steve Robenalt <steve>
Component: cdo.dbAssignee: Eike Stepper <stepper>
Status: NEW --- QA Contact: Eike Stepper <stepper>
Severity: normal    
Priority: P3    
Version: 4.13   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Stack trace none

Description Steve Robenalt CLA 2011-06-14 18:39:50 EDT 
Build Identifier: CDO SDK 4.0.0.v20110523-1736

When initially creating a new offline clone, tables are not created in the local (offline) database if raw replication is selected. During the initial sync phase, errors are reported regarding the missing tables, and the initial sync fails.

Workaround: Switching raw replication off allows the tables to be created and the databases to be sync'd, after which raw replication works properly.

Bug #331775 affects raw replication, but not Derby, so it may not be related. 

Stack trace will follow.


Reproducible: Always

Steps to Reproduce:
1.Start with an offline clone and master configuration using raw replication and Derby databases.
2.Delete the offline clone database (or start a new offline clone to force initial creation).
3.Error occurs on initial SYNCING phase, causing sync to fail.
Comment 1 Steve Robenalt CLA 2011-06-14 18:42:30 EDT 
Created attachment 197988 [details]
Stack trace

Stack trace for exception from missing table.
Comment 2 Steve Robenalt CLA 2011-06-14 18:43:32 EDT 
Fixing CDO version (4.0)
Comment 3 Eike Stepper CLA 2011-07-06 04:00:56 EDT 
I can see nothing Derby-specific here, although this doesn't mean there is nothing. Steve, are you sure your problem is not caused by your special setup / usage?
Comment 4 Steve Robenalt CLA 2011-07-06 11:05:16 EDT 
(In reply to comment #3)
> I can see nothing Derby-specific here, although this doesn't mean there is
> nothing. Steve, are you sure your problem is not caused by your special setup /
> usage?

I'm not sure the problem is Derby-specific. I reported it that way because it's the only database I have tested. As far as my configuration, I don't think there is anything unusual about it. It's pretty close to the offline clone example. And since it works normally with raw replication turned off, I would think my setup is probably not the cause of the issue.

Now that we've gone live with the software, I'll go back and dig deeper into this to see what's going on.
Comment 5 Eike Stepper CLA 2012-08-14 22:50:29 EDT 
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 6 Eike Stepper CLA 2013-06-29 12:16:08 EDT 
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Comment 7 Eike Stepper CLA 2015-07-14 02:07:36 EDT 
Moving all open bugzillas to 4.5.
Comment 8 Eike Stepper CLA 2016-07-31 00:50:29 EDT 
Moving all unaddressed bugzillas to 4.6.
Comment 9 Eike Stepper CLA 2017-12-28 01:20:59 EST 
Moving all open bugs to 4.7
Comment 10 Eike Stepper CLA 2019-11-08 02:12:25 EST 
Moving all unresolved issues to version 4.8-
Comment 11 Eike Stepper CLA 2019-12-13 12:44:57 EST 
Moving all unresolved issues to version 4.9
Comment 12 Eike Stepper CLA 2020-12-11 10:43:09 EST 
Moving to 4.13.