DSXchange

Ok I went back to a job that worked and compiled the job and I had no errors. I then copied the job an renamed it. Then I tried to compile the new job and BOOM!!! I got the same errors. So something is going on with copying.

Ok ill check out the other postings and see if it helps. Really nothing has changed from a job perspective. We have 20+ jobs that use the same transformer and aside from the fieldnames it does the same thing. I went back to some of the other jobs that worked and compiled them and no errors popped up...

We have several jobs that are set up the same way. Each job contains a transformer in which we add the DSJobStartTimestamp as well as reassign the change data capture code 1,2,3 to I,D,C other then that the only difference are the fields. All the jobs work but one. When trying to compile it fails at...

Our dsadm removed the locks from the RT_ folders using the process described above. Thanks for your help.

>unlock 64606 USERNO all
Insufficient privileges to perform lock maintenance.


I guess I need to will get with the admin and see if this works for him.
Thanks

You don't need to delete the job. You still have a lock, just not on the job itself. Your lock is on a supporting file, either a RT_STATUSnnnn, RT_CONFIGnnnn, or RT_LOGnnnn. You need to identify the internal job storage number, then look in the lock table for one of these three. Use the UNLOCK USER ...

While working on a job it got locked up. We located the locked job and removed the lock. We were then able to open it in designer but are unable to compile (we get an executable file not available job may be being monitored error ). We then tried to delete the job in the designer but we get the Cann...

Ok I just want to get the right resolution out here in case someone has the same issue. The literal spaces come into datastage fine and can flow through a transformation,lookup or filter as in our flow. The problem shows up in the final load to the oracle table. In our process we were using the LOAD...

The $APT_ORACLE_PRESERVE_BLANKS works but unfortunatley it pads all spaces for all fields. So if a field had 36 characters and only used 10 the parallel job brings in all 36 (the 10 plus the 26 spaces). Basically it will not work. For now we have decided to default all literal spaces to '0' and just...

I used $APT_ORACLE_PRESERVE_BLANKS set to True as a parameter at the job level and it has worked so far. Thanks

Is that something I will need to get the datastage admin to change or can I bring it in as a parameter and change it. When i bring APT_STRING_PADCHAR in as an environment variable it has 0x0 as the default. My guess is 2x0 for the relacement.

Im not saying that the space is a null its a really 3 spaces in a varchar2(9) datatype. Somewhere in datastage it is converting the spaces to nulls during the parallel job. After a change data capture it tries to insert null values into the change table when really it should be trying to insert the ...

The system we are acessing is old and allows literal spaces ' ' as part of the key on some of their tables. During the change data capture it works fine because it compares a null to a null and finds no difference. However when it goes to load the changes into the final table it will not allow the N...

I would want to access the file in a parallel job (i think that is your question)

So the functionality is there it just needs to be setup. Is that something each user would have to establish or will the DBA's need to set it up on the box? If I sent your previous post to the DBA's would it give them enough info to figure it out.