DSXchange

I've already tried to import the same job to attempt to overwrite the job. It results in the error: Cannot open file RT_BP806.O I've made sure I'm logged out of Designer and Director when trying to delete the job. Yes, I'm using dsadm to delete. BTW, some of the directories are owned by user "k...

When trying to import into the same project, I get the same error:
Cannot open file RT_BP806.O

If I rename the job, I still can't delete the job. But this allows me to import the job without error (at which point I have two of the same jobs, just one is renamed).

ok, DS.CHECKER looked like it did some good... created missing files and deleted old ones... So now, I can compile the job successfully. But I still can't delete the job. When I try, I get this: Cannot open file RT_BP806.O Here's the directory and its contents: drwxrwxrwx 2 dsadm dstage 4096 Jan 10 ...

What about option #4 to Check Integrity of Job Files? Option #4 on my DS.TOOLS is something different. I'll try the DS.CHECKER command. DataStage Tools Menu 1. Report on project licenses 2. Rebuild Repository indices 3. Set up server-side tracing >> 4. Administer processes/locks >> 5. Adjust job tu...

I've already rebuilt the indexes on the project using the Rebuild Repository indices (option #2) in DS.TOOLS. Is there anything else I can try before moving the jobs to a new project?

By the way, I already tried cleared all the locks, and have now rebooted, but I still can't delete the job.

I have a similar problem where we seemed to be able to delete a job partially, but the job still displays in Manager, but not Director. When trying to delete the first time, Manager froze. From then on, attempting to delete results in this error message: Cannot open executable job file RT_CONFIG806 ...

...edit the table definition immediately after it has been imported (before it's used in a job design). This would be a simple work-around (which I had already suggested to our developers), except that all of the jobs have the "replace" write method, and so each table will be re-created e...

Hello, We are running DS EE 7.5.1A on Linux with NLS installed. Using the Oracle stage with the "replace" write method, any columns defined with the "unicode" Extended option are created in Oracle with the column length multiplied by 4. For example, a column defined in the Oracle...

ok, thanks. Yes, that's what I was trying to explain... All of the missing columns are always at the end. All other columns should always be in the correct order, which will load properly according to the mapping.

Are there any other ways to do this using any DataStage functionality?

thanks for the reply, kcbland. To do what I'm asking, I would need some functionality to either place nulls (or a default value) into the missing columns, or completely ignore the missing columns. The reason I think this could work, is because the load would assume that each column does correlate to...

Hello, We've got a problem with loading a tab delimited sequential file with records with varying number of columns. For example, the target table has 10 columns. The sequential file may have 10 columns in the first row, 5 columns in the second, and 8 columns in the third row. Sequential_File_0,0: D...

kumar_s wrote:Its always good to update the post with resolution. And so don't you wish to mark the post as resolved?

ah, gotcha. I actually didn't know we could do that.

I'm sure you've already found a work-around for this, but I thought I'd update this thread, since I've run into the same issue. I've found that this error occurs when using the "table" read method in combination with partitioned Oracle tables (and views which access partitioned tables). As...

By the way, you will still need to enclose the password in double quotes after the patch is applied! Also, the patch required both server and client side patches.

FYI, we received a patch for this some time ago. Here's the info. PATCH REPORT FOR ECASE: 84857 PRODUCT: DSEE VERSION: 751A PROBLEM REPORTED: Cannot use '#' or '$' in Oracle passwords CAUSE OF PROBLEM: FIX SUMMARY: Fixed so that oraupsert, oraread, and orchdbutil will work with '#' or '$' in passwor...