DSXchange

When I attempt to view the log for a job, I get this message: Error selecting from log file RT_LOG12 Command was: SSELECT RT_LOG12 WITH @ID LIKE '1N0N' AND @ID >= 7115 COUNT.SUP Error was: Read operation failure. Internal file corruption detected. File must be repaired. I ran DS.CHECKER and it did n...

If you have a Failed trigger this takes precedence over the automatic handling. I left the job with the "Execution Activity" set to "Validate Only" and added a stage for the "Otherwise" trigger that resets the job when the validation fails. I found out that there was a...

That's what I think I tried. I ran it again to confirm. All the jobs succeed ("Finished") except for the validate job ("Validation failed") and the sequence ("Abort"). Looking in the log, I saw this: seqExportCompliance..JobControl (@ValidateFocus): Controller problem:...

That's fine, allow the "is the DB there?" job to abort. Have its triggers handle the abort condition, only proceeding with subsequent processing if the database is available. Particularly for this job's Job activity, set "do not checkpoint run" (so that it executed always), and ...

[If this has already been answered somewhere, please just direct me to that page. I searched but didn't find anything that seemed to be related.] Background When an attempt is made to connect to SQL Server via the OLE DB stage, it will report an error (80004005) if that database cannot be found; i.e...

Were the working ones compiled in an earlier version of DataStage and have not been recompiled since? No. The same modules were pushed to the two projects using Version Control and compiled upon delivery. Both projects are on the same server using the same datastage engine. But I understand what yo...

Just noticed that the item marked as running is an instance (uses an invocation id). When I select the job itself, "Clear status" is enabled. It is only when I select the instance of the job that "Clear status" is disabled. That makes sense... So, I should just be able to delete ...

I did find this article in the Ascential KB that recommends one solution: https://www.ascential.com/eservice/know ... =T30760501

Going to give it a try....

Update: IBM tells me that this is a known issue and there is a fix in 7.5.1A and 7.5.2 so we're looking into that upgrade. In the meantime, I removed the time from the value. I expect it will work tomorrow morning. We'll see... I tried creating a small sequence that used the same model and it had th...

5) I went into the job menu in the director but clear status file option is not available as the job is still running... No such... it is always available regardless of status, which is why it does the 'Are you really sure you want to do this?' stuff. You have to 'Enable job administration in Direc...

Yes. If you don't want to go the file route, split your timestamp in two - send each portion separately. Ok, I am willing to accept this -- except: I have this exact same ETL running in a test environment and on production (both promoted to the enviroment from the same source in version control). I...

Have you tried revisiting Set Defaults in the Director's Job menu and clicking on "Set to Default" or "All to Default"? Yes, I tried the "Reset All" button. I tried deleting the scheduled job and recreating it. It always quotes the parameters. But not all of them, just...

I have other parameters with spaces and they do NOT get quotes around them. Though the values that "work" are read in from a file as opposed to being defaults or entered. Maybe that is the solution: read the rest of the defaults from a file. Seems an unnecessary work-around. And if it is t...

I have a similar, but slightly different problem than I found in the thread "scheduled job picks wrong value of parameter" ( http://www.dsxchange.com/viewtopic.php?t=91345 ). Since it seemed the opposite problem I felt to post a new topic. Both of these issues occur only when scheduled via...

Thanks for the replies. Sounds like I am in the right direction. I look forward to Ken's input.

Ray: We are actually looking at the IBM Business Glossary and Metadata Workbench. Very impresive capability. The challenge (of course) is getting management and IBM to agree on a price.