The best way of doing this is inserting a record for the table in the MDSYS.USER_SDO_GEOM_METADATA table in Oracle, containing the right SRID.
If you create the table using FME, you can do that using the parameters section on the table.
The best way of doing this is inserting a record for the table in the MDSYS.USER_SDO_GEOM_METADATA table in Oracle, containing the right SRID.
If you create the table using FME, you can do that using the parameters section on the table.
thanks dear @erik_jan
yes i can set SRID to 4326 and the SRID section of geometry data will change from null to 4326 like data below
before:
{2002,4326,null,{1,2,1},699956.85,3853005.3,5700031.07,3852978.66,5700057.01,3852973.81,5700069.08,3852975.18,5700082.09,3852980.66,5700092.13,3852987.72,5700099.65,3852995.49,5700105.59,3853004.61,5700110.37,3853017.6,5700110.83,3853031.29,5700106.04,3853042.69,5700096.69,3853055.02,5700078.43,3853068.69,5700010.33,3853109.78}}
after
{2002,4326,null,{1,2,1},699956.85,3853005.3,5700031.07,3852978.66,5700057.01,3852973.81,5700069.08,3852975.18,5700082.09,3852980.66,5700092.13,3852987.72,5700099.65,3852995.49,5700105.59,3853004.61,5700110.37,3853017.6,5700110.83,3853031.29,5700106.04,3853042.69,5700096.69,3853055.02,5700078.43,3853068.69,5700010.33,3853109.78}}
but the problem is in vector data that doesnt't seem to be converted correctly cause i know the correct format of 4326 is like sample below
xx.xxxxxxx
the problem solved
i find out that my postgis source data was in 900913 format that is not an official format of SRID and this is why FME Software couldn't convert properly
i converted my geometry data to 4326 format using script below
update planet_osm_roads set way = ST_Transform(way, 4326)
and now when i convert my postgis to oracle by FME everything is all right.