New to Oracle -- desperately seeking advice [message #270719] |
Thu, 27 September 2007 18:47  |
magicofbeliving
Messages: 2 Registered: September 2007 Location: Northeast
|
Junior Member |
|
|
My company is just starting to move from a legacy mainframe COBOL system to Oracle. A question that continues to come up is how do we know that a data file with 100 records sent from the mainframe is received inbound with 100 records to Oracle? In the past we have had issues where our network has hiccuped and 'lost' either entire files or just parts of the file.
Has anyone else dealt with an issue like this?
How did you go about file verification?
Is there any best practice we should be following?
Any guidance is greatly appreciated!
|
|
|
|
Re: New to Oracle -- desperately seeking advice [message #270743 is a reply to message #270720] |
Thu, 27 September 2007 22:59   |
rleishman
Messages: 3728 Registered: October 2005 Location: Melbourne, Australia
|
Senior Member |
|
|
David's suggestion of file numbering to ensure that all expected files are received is a good one.
Two other issues are:
- How to stop Oracle from reading the file until COBOL has finished sending it.
- How to make sure the file transfer did not hiccup.
The most common techniques I have seen for these are:
- Get COBOL to send a zero-byte ("indicator") file only AFTER it has finished successfully sending the main file. Then program Oracle to IGNORE the data file until it sees an indicator file that is NEWER than the data file; this means the data file is complete and ready to read.
- Get COBOL to include a trailer record in the data file that contains a rowcount and a checksum (tricky with EBCDIC vs ASCII)of the detail records. The receiving process (Oracle) counts and hashes the detail records and validates against the trailer record.
Ross Leishman
|
|
|
|
|
Re: New to Oracle -- desperately seeking advice [message #271205 is a reply to message #270719] |
Sun, 30 September 2007 16:39   |
magicofbeliving
Messages: 2 Registered: September 2007 Location: Northeast
|
Junior Member |
|
|
Thanks for all the good suggestions. I have requested that each file being sent, send a second file indicating date of creation and number of records. The issue I am having is that management believes (wrongly) that there will be no changes needed to the legacy systems and they are poo-pooing my fears of data loss.
I like the idea of having Oracle send a transmission back to the mainframe -- right now it looks like everything will be FTP'd -- but that is still going to require mainframe development, something management is trying to avoid.
Anyone else out there have any ideas -- or have you dealt with this situation before and how did you get around it?
|
|
|
|
Re: New to Oracle -- desperately seeking advice [message #271788 is a reply to message #271533] |
Tue, 02 October 2007 23:00  |
rleishman
Messages: 3728 Registered: October 2005 Location: Melbourne, Australia
|
Senior Member |
|
|
I would avoid sending anything back to the COBOL machine.
Sending something back implies that they will do something with it. The fact is, YOU want the data, THEY are giving it to you grudgingly. Asking THEM to do anything more than give you the data you want is wishful thinking.
In my experience, it is best to keep as much of the hand-shaking with the receiving system as possible.
I've also seen implementations like @anacedent described - where the sending party renames the file after it is sent. That's a great technique (preferable even!) if you can get the source system to use it. Sadly many will restrict themselves to send-only operations as they have a semi-automated wrapper around FTP with limited capabilities.
Ross Leishman
|
|
|