DSXchange

Is the routine very large? There is a bug in that version of Manager which stops it from loading a routine with source code greater than 32Kb. You can create one this big and save it, but then you cant open it again. You can get around this by putting the routine in a file and using a $Include to lo...

Hello, everyone. I am currently experiencing a runtime error in DataStage Manager that I cant seem to find any solutions for, perhaps someone out there have encountered this problem before... The version of DataStage is Rel. 3.51. The problem occurs when I am in DataStage Manager, and tried to bring...

Hi all,

Does anyone have experience with the feature Release Job?

Could anyone with some experience give me a short explanation of how this work. What are the pros and cons?

Thanks for your responses in advance,

NSP

Hi Brad, The SDK routines/transforms referred-to by Wolfgang should be in release 4. They are in SDKDataType. There may be one there to suit your needs, but be aware that some of the formats are "standard" and others are manufacturer-specific. You also need to watch out for any conversions that your...

Xiong, Did you look through the fairly long message I sent you yesterday after looking at you job? (Im hoping that I actually clicked the send button and that it is not still open on my PC at home). The message that I am trying to get across is stop looking to the rollback segments for a solution. Y...

Hi, Nowell, David I would like to specify my job problem clearer. 1. This job is in an overnight processing batch job. 2. It abort with the same problem, ORA-01555: snapshot too old: rollback segment number 13 with name "RBS12" too small, but please notice each time, the seg number is changed. 3. I ...

By chance, has anyone slapped together or are they aware of a routine/transformer/function that can be used in DataStage to properly read a numeric signed field from an FTP-ed mainframe file? Im not concerned so much with packed fields, just those with an overpunch in the last position indicating th...

David is right on the money with this one. I concur with Davids suggestion to more quickly extract your source data. DataStage acts like a pipeline between two passive stages. If your source stage is read data from a source (file or table) and writing to a target (file or table), the slowest part of...

I have a copy in DEV that became READ_ONLY when I demoted from TEST to DEv and had the default
of READ ONLY.....and now I CANNOT get it to be NON READ-ONOLY so I can make Changes in my DEV JOB

Thank You,

Patricia Desiano
Anheuser-Busch, Inc.
MSG - BudNET Data Warehouse
314-577-7558

Thanks David.. very insightful. David Barham wrote: Clarification time. I was not suggesting that queries are assigned rollback segments. I was saying the same thing as you, in that queries use the rollback segments to maintain read consistency. The problem you talk about with running out of rollbac...

Clarification time. I was not suggesting that queries are assigned rollback segments. I was saying the same thing as you, in that queries use the rollback segments to maintain read consistency. The problem you talk about with running out of rollback space does not result in ORA-01555. It results in ...

Xiong, David, Please let us know when you get the rollback segment issue resolved, and what solution worked for you. One of the largest issues as many of us know is Datastage vs. Oracle interaction. User-defined SQL especially has been a source of difficulty in the past. Its good to see these types ...

Sorry, but this is a pointless exercise. At best, this may change the probabilities of this error occurring, but it does not address the fundamental problem. The DataStage job is reading the same rows of a table that another process is updating. This is primarily a design issue and needs to be addre...

Xiong, Heres the steps forwarded by our DBAs: 1. Take problem rollback segments offline (not SYSTEM rollback segment). 2. Drop the tablespace containing problem RBS. 3. Recreate the tablespace. 4. Recreate all the RBS and keep them of the same size. If need be increase the INTIAL_EXTENT, NEXT_EXTENT...

Xiong, We have run across this error here as well. I agree with what you say David as far as reading data. However, rollback segments CAN cause problems though if you have your transaction size of 0. The reason is that rollback segments not only provide read consistency, but they are used for rollba...