DSXchange

Ok, in the UV stage there is no Transaction Size in the sense I'm used to in OCI, for instance. On the Transaction Handling tab there is an Isolation Level dropdown and a Rows per transaction box. Default is apparently an isolation level of 'None' and the Rows per Transaction is greyed out and show ...

Agreed - it is kinda creepy having it following me around and constantly peeping over my shoulder.

Ok, duly noted. Sigh... four hours of sleep just don't cut the mustard, whatever that means.

Not that I am aware of.

Thanks, Arnd - I'll check that out. Not sure I ever realized there was a Rows per Transaction option in there somewhere... duh. Suggestion would be to set it to one perhaps?

Use two links.

That's the odd thing. These are straight inserts, no updates. The update action is 'Clear table then insert'. No routine or anything fancy involved - read from Oracle, write to the UV. It's doing it as a UV table so we can built a composite index over some of the key fields and then use it in a look...

I'm seeing all kinds of new things tonight. Was would cause a message like this when writing to a UV stage? INSERT INTO tablename(fields) VALUES(?) SQLSTATE=S1000, DBMS.CODE=950280[DataStage][SQL Client][UNIVERSE]READU threshold reached, lock on "<list of key values" denied! It's a UV table in the p...

Wish I'd had the presence of mind to capture what I was seeing, but alas no...

Possibly premature, but I was the only person connected to the Project at the time and there were only two or three jobs running total. I'd tried the list_readu command, but as noted it wasn't outputing anything I recognized, just screenfuls of what looked like very long hexidecimal numbers. Many sc...

Resorted to putting it out of its misery by bouncing DataStage. It was at a point where 'Cleanup Resources' hung when trying to switch on the display of 'all' processes and 'list_ready' from the command line was returning pages and pages of basically garbage. The bounce got everything back to 'norma...

Interesting, though, is the fact that I can query the RT_LOG111 hashed file from the Administrator and read through all the records in it without an error.

Was monitoring a job running in Production. Switched out to another job's log and when I came back, got the following alert box: DataStage Repository Interface Cannot get access to log file for job XXXXXXX (111) Don't recall seeing this before. 111 is the job number of the job in question and as bes...

Comes with the product, in the sdk category under the Utility sub-category. Technically it's the UtilityHashLoop routine. Pop it open, the Long Description describes how it works and you can always read the code.

Good catch.