DSXchange

chulett

ODBC and UV are the only two stages that support a 'multi-row result set' - otherwise all you ever get is one record back.

chulett

You can't use the NOTFOUND constraint with database lookups, it just doesn't work - it only seems to be valid for Hashed based ones. You need to check for null returns or whatever your query passes back when no rows are found.

chulett

You need a command delimiter between the two, otherwise all that happens in the 'cd' I'd wager. While you could use ";" I'd suggest the much nicer "&&" which tells the second command to execute only if the first is successful: cmd = "cd /opt/isproj/ctl/ && ./ctlAccess 2" Ca...

chulett

chulett wrote:Assuming a direct OCI reference lookup, you'll need two key columns - ID and DAY - and then user-defined sql to get the 'between' in there. Suggest you start off letting the stage generate your sql and then 'adjust' it from there so you get the basic syntax correct.

chulett

As noted, confusion reigns. With two selects, the 'second' OCI stage must be a reference lookup, but it would be best if you could be more explicit and do a better job of describing the job design. Assuming a direct OCI reference lookup, you'll need two key columns - ID and DAY - and then user-defin...

chulett

If the confusion is where exactly your Projects directory is located, let's see if this helps. Assuming a standard setup, try: cd $DSHOME cd ../Projects/<YourProjectName>/RT_BP1217 If the first step doesn't seem to work, try: cd `cat /.dshome` cd ../Projects/<YourProjectName>/RT_BP1217 One of the tw...

chulett

Meaning what? You don't know where your Projects are on the server? You don't know 'cd' or 'vi'? All the steps are spelled out in my post, what part are you having a problem with?

chulett

pratyusha wrote:I am sorry.There was a mistake
The job does not abort now but the log stops here

What was 'the mistake' and what did you change? As noted, it sounds like the command is hanging, the question is why.

chulett

Simply mark the output field as a Key field and it will automatically be used in any generated update 'where' clause.

chulett

The job number for the 'RT_BPnnn' subdirectory is already noted in the message - in your case 1217. So you would cd to the Project directory in question, then the RT_BP1217 sub-directory there and then finally 'vi' the file noted in the message: " JOB.282366356.DT.1473640285.TRANS2 ". Check at and a...

chulett

Again, you've neither explained what you are trying to accomplish nor what isn't working for you.

chulett

ray.wurlod wrote:"FastExport" indicates extraction from Teradata.

Well, ok... doesn't tell us much other than that.

chulett

Here is the combined wsdl we ended up using, hope it helps: <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://www.rhd.com/dpc/matchService/1.0" xmlns:soapenc="http://schemas.xmlso...

chulett

Can't help you with that one.

chulett

Put "#$SHELL_SCRIPT_PATH#p3.ksh #$CARS_OUTBOUND_EXTRACT_PATH#" in the 'parameters' box, without the quotes of course.

Search found 42189 matches