DSXchange

chulett

Hmmm... somehow I'm guessing this isn't a TX question. Please repost it in the proper forum and then people will be happy to answer it.

chulett

I'm asuming you mean 'over' 49MB. Try using the 'URL/Filepath' option in the XML Input stage with only the first column declared in the Folder. Remove the second one that passes in the full contents of the file, let the XML Input stage do that.

chulett

Welcome. :D Your Key Expression would simply be the column EFFDT so that it is passed to the ODBC lookup, everything critical is setup there. I'd suggest you first let the ODBC stage generate the SQL so you can see the syntax and then modify it. It will produce SQL for an equi-join and you'll need t...

chulett

Apparently not.

I'm assuming that, at the very least, dsjob was hosed up by your actions. Simple enough to check. Compare the output of these commands from DEV and PROD:

Code: Select all

cd $DSHOME/bin
file dsjob
ls -l dsjob

And then - as noted - if dsjob was affected, what else might have been?

chulett

Just to confirm, yes - the advice you got from Minhajuddin was PX specific, so not at all applicable to Server.

ps. I would try 'type' rather than 'copy'.

chulett

How about:

Code: Select all

Ans=Output<14>

Assuming I counted correctly.

chulett

Or if they need to run in a serial fashion:

Code: Select all

Job1 --OK--> Job2 --OK--> Job3

chulett

All that requires in the use of 'OK (Conditional)' triggers between jobs.

chulett

And typically indexes created as well, else it will be slow as the proverbial dog. Guess I should have been more pedantic and specified a hashed file stage 'join'.

chulett

Can you explain what this "bad copy/paste" was all about? Have you destroyed / overwritten any of the bin components?

chulett

Yes, the grants needed are specific to the Oracle Enterprise stage because of how it operates. There are several "sys" grants you will need, all are documented.

chulett

Sorry, but I'm curious which part of the message is unclear? The Enterprise Stage is documented as requiring certain unique privileges to be able to operate, privileges that your user does not have.

chulett

Interesting... I pretty much stick with Exact Match searches, but did run a couple of All Terms ones and you seem to be correct. The results don't go back very far.

chulett

There ya go.

chulett

Truncate the table once in a separate step, then do your inserts. ODBC really limits your options there, AFAIK you'll need another job for this. Perhaps another link will work, constrained to @OUTROWNUM = 1?

Search found 42189 matches