The tables were fine, it was something to do with the SCN's being out of sync between the databases. Doing the export/import routine back and forth synced the SCN's, which evidently streams uses to monitor changes and figure out which to send and/or apply. ------------------------------------------------------------ Bill Ferguson U.S. Geological Survey - Minerals Information Team PO Box 25046, MS-750 Denver, Colorado 80225 Voice (303)236-8747 ext. 321 Fax (303)236-4208 > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Ron Rogers > Sent: Wednesday, July 06, 2005 11:56 AM > To: oracle-l@xxxxxxxxxxxxx; William B Ferguson > Subject: RE: help in streams setup > > Bill, > Thanks for the hint. > How did exporting from one database and then back correct the problem? > didn't the import set the table up correctly the forst time? > Thanks, > Ron > > >>> William B Ferguson <wbfergus@xxxxxxxx> 07/06/05 1:34 PM >>> > I ran through that same article a few weeks ago myself, and > kept having all kinds of problems. It turns out that I was > skipping a step, where I had to export from database "A", > import into database "B", then export database "B' and import > into database "A". Only then did everything work correctly. > Eveidently the (apparent) duplication of steps, just > reversed, are necessary to get the SCN's synced between both > instances. > > However, I did it with an entire schema, not just a table as > you appear to have done. Not sure if this would make any > difference or not. > > > ------------------------------------------------------------ > Bill Ferguson > U.S. Geological Survey - Minerals Information Team PO Box > 25046, MS-750 Denver, Colorado 80225 Voice (303)236-8747 ext. > 321 Fax (303)236-4208 > > > -- > //www.freelists.org/webpage/oracle-l > -- //www.freelists.org/webpage/oracle-l