DSXchange

We're running PX 8.5 on Unix and during a run, we received a warning message stating that a table was not found. I know from previous experiences with Datastage that it would abort when this happens. The difference I see is, we are using Aliases and there was no data to load.

We are running on DB2.

Has anyone ever experienced this and opened a PMR regarding it.

Thanks in advance

"Table not found" is very different from "table exists but has no rows to process". DataStage will abort in the former case but will happily process those zero rows in the latter case.

Check again that you have spelled the table/alias name correctly, that the alias does actually exist, and that your credentialled user has privileges to SELECT. Also that you're executing in the correct schema.

The table really doesn't exist and Datastage is throwing a warning. First time I see this. Other jobs that use this table in other Projects abort. I have setup project and never seen a Error Severity switch to set the different levels. This one is really weird.

We found the answer. When there are no input records and the target table is missing, Datastage throws a warning. As soon as we have records from the input, the Datastage Job aborts.

How can you have records from the input if the table is missing?

Target table.

Would you believe I once worked on a project where there was a source table called TARGET? Should've been SALES_TARGET, but I didn't have enough weaponry with me at the time to mount a convincing argument.

I think Raftsman was pointing towards empty source(file/table) and missing target table...

I guess I need to clarify information in more detail, my apologies.

Source Records = 0

Target Table Missing

Datastage response: Warning


Source Records = 10

Target Table Missing

Datastage Response: Fatal

Raftsman wrote:I guess I need to clarify information in more detail, my apologies.

No, not really.