DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
dskid
Participant



Joined: 19 Jun 2006
Posts: 13
Location: uk
Points: 179

Post Posted: Wed Apr 18, 2018 10:04 am Reply with quote    Back to top    

DataStage® Release: 11x
Job Type: Parallel
OS: Unix
Additional info: migrating jobs from 8.5 to 11.7
Hello everyone,
i am in the process of migrating parallel jobs from 8.5 to 11.7. some of my jobs use surrogate key's and we are using Surrogate key falte files in transformer stage. i copied all the *.key files from old to new environment but when i run the jobs in v11.7 , it is unable to read the surrogate key files and throwing error "APT_CombinedOperatorController(1),1: Internal Error: (start <= end): surrkey/keystate.C: 107 "
we want to maintain same seq number for our loads, so we need the old files to generate surrogate keys.
We tar surrogate key files from old environment and untar in new environment. When i try to open the file it is in binary format so its unreadable.
Any help is appreciated.
chulett

Premium Poster


since January 2006

Group memberships:
Premium Members, Inner Circle, Server to Parallel Transition Group

Joined: 12 Nov 2002
Posts: 42617
Location: Denver, CO
Points: 219422

Post Posted: Wed Apr 18, 2018 10:26 am Reply with quote    Back to top    

Check with support, while there may be nothing wrong with the mechanism you're using there could very well be an incompatibility in the file format when you jump ahead so many years / versions.

Or wait and see if anyone here actually knows...

_________________
-craig

And I'm hovering like a fly, waiting for the windshield on the freeway...
Rate this response:  
Not yet rated
UCDI



Group memberships:
Premium Members

Joined: 21 Mar 2016
Posts: 331

Points: 3352

Post Posted: Wed Apr 18, 2018 10:43 am Reply with quote    Back to top    

it looks like it wants the keys to be in numerical order, and they were not.
If they are supposed to be in order in the binary file, but are not, I would check to see if the sizes changed (eg 32 to 64 bit understanding of the bytes) and that they have the same byte order as before (most significant byte on far left or far right??).

A good hex editor will open the file and tell you the numerical value of the data in various formats (int 8, 16, 32, 64 for example). If you know what the first key in a file is somehow, you could use a hex editor to see what is going on there. It can also find a numeric value in the data if you tell it how wide the value to look for should be...

If it is a very simple binary file converting it back to text may be easy and doable, and you could also see that by looking at it.


you may want to generate a small test file in both versions and compare the differences to see what to do.
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours