SysID and flat files import

[CatPlus]

We need to bring all transactions beginning 01/01/2004 exported to a CSV file from an Access application brought over into our Oracle application

The Oracle guys tells us records generate SysID which prohibits doing so.

Please explain how SysID play roles in related tables and whether these could be turned off during the import procedure.

Can a SysID be defined by us? For example if table "PO_HEADER" has a column "VENDOR_ID" and PO line items have a columns "VENDOR_ID", can the SysID be equal to "VENDOR_ID"? .....or can the SysID be disabled when the process of import is being carried out....

And if all of the above questions are replied as NO.... then how can records be brought in considering its the records (vital INFORMATION of the business) that the IT (Information Technology) says we cannot have!

Thanks for your input

Mickey

 

[SantaMufasa]

Mickey,

Sounds to me like your Oracle guys are perhaps "taking you on a Snipe Hunt" with the SysID issue. I have no clue what on earth they are talking about.

If your Access application simply produces standard comma-separated values (.CSV) files, then Oracle can accommodate them nicely. You can even create an "EXTERNALLY-DEFINED TABLE" that literally reads your .csv file and treats it like a standard Oracle table as far as SELECTing data is concerned.

If you can get your Oracle folks to explain more about the SysID issue to which they refer, then perhaps we can understand what they are talking about. But at this point, it seems to me to be a Snipe Hunt.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I can provide you with low-cost, remote Database Administration services: see our website and contact me via www.dasages.com]