DSXchange

Upgrade.

If that doesn't help, post the exact text of your 'abort' message.

I meant you should do this before using the 'bad' metadata in any jobs. If you've already used it, then you'll need to correct all of the jobs individually. And no, NLS plays no role in this as far as I know.

It's a bug or 'feature' of importing via the OCI plug-in, correct it manually after doing the initial import.

You'll also have to include the key fields in your select statement as well, such that you select the same fields in the same order as they are defined in the stage.

Rather than posting again to explain why it happened, next time just edit the duplicate post and then select the 'Delete' option. They can be deleted as long as there is no reply posted.

Ok, so something is making it believe that you have no sql statement in the stage for that link. Why would that be? What update action are you using and where exactly is your statement in the stage?

Post the exact error.

You need to check and confirm that each 'line' of the file is intact and whole. Are you familiar with vi? A ":set list" command will show you all characters in the file, including a $ to mark the end of each line/record.

Make sure none of the lines have been 'broken in two' accidentally.

Do you have another project you can copy it over from? Nothing about it is project specific, so any other project will do.

What does that mean?

I wasn't asking if you could spawn a new shell or not, but if doing so before you issued those commands 'fixed' your problem. Specifically:


Does that change the behaviour at all?

Bash? Hmmm... what happens if you pop a different shell before doing all that? For example, sh or ksh?

Or, as Arnd notes, your dsenv file is horked.

dsenv is a file, not a directory and as such is inappropriate for use in a PATH statement. Replace it with these statements:


Then continue on with your scriptage.

Hmmm... since the routine seems to work when run stand-alone and only has issues when launched from your job control, perhaps we should look there rather than focus on the routine itself? If you are willing to post the code which calls the routine, that is. And it might help explain what you meant b...

If the format was wrong (dashes and such) you'd throw a -4 error, the -3 says there isn't a parameter with that name in your job. Don't exclude the $ when doing this, it might be as simple as that. And as Ray notes, dates will need to be in YYYY-MM-DD format.

Let us know if you get this working.