Page 1 of 2
XML error:Caught unknown exception from runLocally()
Posted: Thu Jun 17, 2010 2:18 am
by g_rkrish
we are doing an upgrade in DS in which we have a job where source is a data set and we store that in a XML and get back from xml and that particluar stage shows up an error saying "Caught unknown exception from runLocally()".I have no clue how to approach this error.any help.
Posted: Thu Jun 17, 2010 2:32 am
by ray.wurlod
"Unknown" means just the same to us as it means to you. Contact your official support provider and they'll suggest what logs to look at. More information about exactly what you were doing will almost certainly be required by your support provider.
Posted: Thu Jun 17, 2010 3:55 am
by Sainath.Srinivasan
This error is normally accompanied with another warning / error. Do you see any ?
Posted: Thu Jun 17, 2010 4:14 am
by g_rkrish
Sainath.Srinivasan wrote:This error is normally accompanied with another warning / error. Do you see any ?
I did not get any error on that XML stage rather am geting the usual warning of cannot preserve partitioning on the sort stage.
Posted: Thu Jun 17, 2010 6:07 am
by eostic
It's probably nothing to do with your xml "in particular"....that's pretty generic. Can you get "any" XML to work? What release are you upgrading from/to? Do you have other Jobs with xml that are working? What is the size of the xml that you are moving around on the links? It could be a lot of things. When I get that error it is usually during initial design where I have forgotten something or put in a completely non-sensical property value, etc. Of course, you have an existing Job, but you never know....review all of it carefully. You may need to break it down into smaller pieces.
Ernie
Posted: Thu Jun 17, 2010 9:47 am
by g_rkrish
Can you get "any" XML to work?
Yes,but the XML O/P stage fails for that particular job when i just use as o/p and read from that as well.But same job runs fine in 7.1 version when imported to 8.1 it fails.
But when i use the same XML o/p stage just to write also fails with same error.
Do you have other Jobs with xml that are working?
Yes XML works for most of the jobs for that job and similar jobs where i get data from Dataset it fails.
What is the size of the xml that you are moving around on the links?
Less than 100 recs for testing.
any more details Ernie Pls do ask me.got struck with this.
Do any thing need to be done when write and read from same XML.
Posted: Thu Jun 17, 2010 9:58 am
by chulett
g_rkrish wrote:Do any thing need to be done when write and read from same XML.
Wait, wait, wait... are you saying this only happens when you are writing back
to the same xml file that you are reading?
Posted: Thu Jun 17, 2010 7:05 pm
by eostic
ok...so following on Craig's note, tell us more about "that" Job...what makes it unique?
Ernie
Posted: Thu Jun 17, 2010 9:37 pm
by g_rkrish
eostic wrote:ok...so following on Craig's note, tell us more about "that" Job...what makes it unique?
Ernie
that job has source Dataset and has a copy stage goes to the lkp stage then other link from the copy goes to the transformer where we do some trnsformation goes to the XML and from that XML goes to the LKP stage where constraint in LKP is lkp--> failed--> failed.And then to transformer goes on but the error is into the XML and LKP beacuse data not getting loaded to the XML and in the LKP it fails and eventually fails the JOB.
This is what happens in the job,there is another job where we don't have any lkp stage we have transformer-->XML--->Xfrmr fails with same error.
Any more information pls ask?
Posted: Thu Jun 17, 2010 9:45 pm
by chulett
XML stages are typically
end points in a process, with the possible exception of an immediately following Sequence File stage to write the output to disk. I have no clue what kind of 'lookup' you would be doing or what kind of 'transformations' would be happening after the XML stage, can you clarify what
exactly it is you are attempting to do? What kind of "xml" are you generating? What lookup? What transformations? We can't do anything other than
guess without details from you.
And just for grins can you clarify what "the XML" means - an
XML Output stage, I'm assuming but sometimes those assumptions get us in trouble.
Posted: Thu Jun 17, 2010 9:59 pm
by g_rkrish
chulett wrote:XML stages are typically
end points in a process, with the possible exception of an immediately following Sequence File stage to write the output to disk. I have no clue what kind of 'lookup' you would be doing or what kind of 'transformations' would be happening after the XML stage, can you clarify what
exactly it is you are attempting to do? What kind of "xml" are you generating? What lookup? What transformations? We can't do anything other than
guess without details from you.
And just for grins can you clarify what "the XML" means - an
XML Output stage, I'm assuming but sometimes those assumptions get us in trouble.
Sorry I think i am kind of confused you guyz
Code: Select all
Dastset--------->Cpy-->RemoveDup---------------->LKP---------------Xfrm--
| |
| xfrmr
| |
| |
sorter--->Xfrmr------->XmlO/p
Dataset has twokey columns and we are removing dups(Keeping first) by thoese two key coulmns but when we go to sorter it goes with single key
column then goes to transfor where we assign toe the XML columns from the XML we have that single key column tehn it goes to Xfrmr and to the LKP
Pls leteme know any more info needed
Posted: Thu Jun 17, 2010 10:17 pm
by ray.wurlod
Wrap your "ASCII art" in Code tags so that spacing is preserved. Then we may have some possibility of understanding what's connected to what.
Posted: Thu Jun 17, 2010 10:30 pm
by chulett
g_rkrish wrote:Sorry I think i am kinda confused you guyz
Way more than 'kinda', that first explanation was indecipherable.
Posted: Fri Jun 18, 2010 5:23 am
by eostic
Time to start breaking it down.... It looks like both the xml output link and the other primarily link are fed into the lookup? Create another Job and remove the whole top path..... just write the xml output in a straight line...does it still fail? This is probably a problem of stages in some sort of combination.
Ernie
Posted: Fri Jun 18, 2010 5:45 am
by g_rkrish
eostic wrote:Time to start breaking it down.... It looks like both the xml output link and the other primarily link are fed into the lookup? Create another Job and remove the whole top path..... just write the xml output in a straight line...does it still fail? This is probably a problem of stages in some sort of combination.
Ernie
Yeah i tried that Ernie Still fails showing up the same error.