I think all you problem can be solved if your Subscriber (oracle
database) already has a pre-defined table to receive the data. This
will take care of issue 1 and 3. As for the datetime field, make
sure your Oracle table is using date data type, then the HH:MI:SS will
> SQL's Heterogenous Subscriber is my choice. And I tried to use DTS, but
> it seems Heterogemous replication doesn't support it! Do you have any
> idea about it? I know oracle keeps the time up to seconds, but after replication
> the HH:MI:SS was truncated??
> > How are you replicating your SQL data to Oracle? It's hard to tell
> > where things go wrong without knowing which way you are doing this.
> > You should probably try DTS and make sure your transformation is done
> > correctly.
> > Oracle keeps the time up to seconds. Try
> > select to_char(datefield, 'MM/DD/YY HH:MI:SS') from mytable;
> > JH
> > > All,
> > > I'm trying to replicate from sql server to oracle, and issues come up:
> > > 1: DATETIME data type is converted to short DATE , such as
> > > "mm/dd/yy h,m,s" will be "mm/dd/yy", after replication;
> > > 2: Clustered primary key can't be replicate to oracle , I checked the error
> > > that's because the sql statement generated by sql server including CLUSTERED
> > > key word which oracle doesn't support;
> > > 3: Sql server only push the first column to oracle as primary key for
> > > Non-clustered
> > > primary key in it. Such as PK(col1,col2,col3) will be PK(col1) in oracle
> > > after replication.
> > > Could any expert give me some suggestion? Thanks a lot.
> > > Bob
> > > --