Home » RDBMS Server » Server Administration » Data not right after convert from mssql to oracle10g(OMWB)
icon9.gif  Data not right after convert from mssql to oracle10g(OMWB) [message #129599] Mon, 25 July 2005 21:55 Go to next message
edcas
Messages: 38
Registered: July 2005
Member
pls help...

did anyone come across this problem? After I've successfully migrating and loading data from Ms-SQL 2k to Oracle10g, i've found that the data are not right.

Hexadecimal digit define in Ms-SQL, are different after converted to Oracle. First half of the values are shuffled Shocked, and second half of the values are correct.

DataType defined in MsSQL is UniqueIdentifier. After migration to Oracle10g, is RAW(16)

GUID_Trx
--------------------------------
F2E5AC92-99E4-4BB1-BE95-4C349BAAB4EA (Ms-SQL)
92ACE5F2E499B14BBE954C349BAAB4EA (Oracle)

D7046C03-8991-418F-9435-9B865657860C (Ms-SQL)
036C04D791898F4194359B865657860C (Oracle)

Re: Data not right after convert from mssql to oracle10g(OMWB) [message #129685 is a reply to message #129599] Tue, 26 July 2005 04:56 Go to previous messageGo to next message
Achchan
Messages: 86
Registered: June 2005
Member
You should set data type conversion in omwb.Go to options tab and you will find that.You should do that before creating Oracle model.
BTW,Which version of omwb did you use Successfully? Wink
Re: Data not right after convert from mssql to oracle10g(OMWB) [message #129704 is a reply to message #129685] Tue, 26 July 2005 05:26 Go to previous message
edcas
Messages: 38
Registered: July 2005
Member
hi thanks for ur reply, after changing the size of the type... i still don get the result right. i thought Ms-SQL UniqueIdentifier data type is equivalent to Oracle RAW(16) data type??!?? Rolling Eyes how??


i have tried out 2 so far which are 10.1.0.2.0 & 10.1.0.4.0

Version 10.1.0.2.0 is okay, but not with the latest version. In version 10.1.0.2.0, it will generate more variables to control each of the process like ...

StoO_selcnt INTEGER;
StoO_error INTEGER;
StoO_rowcnt INTEGER;
StoO_crowcnt INTEGER := 0;
StoO_fetchstatus INTEGER := 0;
StoO_errmsg VARCHAR2(255);
StoO_sqlstatus INTEGER;


But, in the lastest version those variables seem remove from there. Somehow, some of the checking are still calling those variables but OMWB never declare or initialise it... This is the problem i've faced so far in the latest version. wat bout u? Razz

Previous Topic: problems during shutdown
Next Topic: mount database in restricted mode
Goto Forum:
  


Current Time: Thu Sep 26 22:48:20 CDT 2024