DSXchange

Unfortunately, the two stars seem to indicate something it cannot fix: >VERIFY.SQL TABLE /appl/Ascential/DataStage/Projects/DEV_XXX/DS_TEMP1 Checking file permissions. ** No SQL catalog data for schema '' in UV_SCHEMA. 1 verify operation discontinued. Items marked with a '!' are information messages...

Add $NLS_LANG as a Project level parameter and set its value to $ENV so it doesn't immediately effect every job in the project. Then add it as a job parameter to your job and override the default value to UTF8 there, it will now be included in your job's environment when it runs.

Actually, the 2.2GB limit is for 32bit hashed files, creating them with the -64BIT option effectively removes that limit. Sometimes a lookup can be replaced by a join in a database, perhaps that is an alternative for you?

Searching would also reveal discussions of "workarounds" for this.

The same project where I have the Cannot find job TEST posting has thrown me another curve. Thinking to verify the integrity of the project and see if it could find the issue (and possibly FIX it as well afterwards) I ran the following command: VERIFY.SQL SCHEMA <MySchemaName> It then output this fo...

FYI

(courtesy of Mr McBurney)

I'm not aware of anywhere you can simply check it or have it tell you what they are... you just need to know. Who set them up?

While you can create new columns in the Modify stage, you cannot do so with "hard coded values" i.e. constants. Nor can you do "if-then-else" logic - both of those are the domain of the Transformer, which there really isn't any reason to avoid nowadays.

Looks like the answer is 'yes': LIST DS_JOBOBJECTS WITH NAME EQ "TEST" 09:57:29am 29 Sep 2009 PAGE 1 Object type........ J Object record id... 1358 Object record name. V77S0P1 Description........ Object type........ J Object record id... 1358 Object record name. V0S251P6 Description..........

You just code it as the derivation of the 'previous value' column since you know the only two values it could be: If Col = 'Y' Then 'N' else 'Y' As for the Oracle error, post the complete unedited version along with any other messages that seem relevant (those kind don't usually occur alone). ORA-01...

OK... you know what's coming first: "Invalid user name (wasadmin) or password". Are you sure of the userid? Made sure the password hasn't expired? Etc etc.

Nope.

'Ordered records in the target table'?

As noted, there's really no such thing and it is generally a waste of time to sort the data before writing it to a database.

How so? Index just finds strings and doesn't extract strings. Would you mind posting your complete solution to help other searchers?

I'll check. I don't recall DS_JOBOBJECTS having 'name' in it anywhere...