DSXchange

Hi Arnd No custom routines, just a very basic job to read data from a number of Oracle tables, using generated SQL, and writing to the hash file. Three columns read, 3 columns written to file with the same Metadata on both sides. The only difference I can see is that the column names are altered on ...

Hi all I'm in the process of upgrading from v7.1.r1 to v8.0.1a, and am having trouble with a couple of jobs. The jobs are very simple but I keep getting the same issue - DataStage Job 586 Phantom 12518 Abnormal termination of DataStage. Fault type is 11. Layer type is BASIC run machine. Fault occurr...

In your installation directory there is a command line utility called 'dscc' that will allow you to compile your routines. When releasing code to new projects I invoke the following to ensure everything is compiled - dscc /h <host> /u <user> /p <password> <Project> /j * /r * /f /rd <logfile> /rt T /...

Hi Kenneth

Just checked with the Unix Admin who told me that the SAN swapped a disk out at about that same time. Looks like all is now OK.

Thanks for the prompt response.
:D

Hi During the production run last night one of the jobs finished with the following warning - DataStage Job 61 Phantom 23353 Program "DSD.StageRun": Line 571, Read operation failure. Program "DSD.StageRun": Line 571, Internal file corruption detected. File must be repaired. DataS...

BTW, have also logged this with IBM / Ascential support, who suggested that I restore the project directory. The last backup was from Friday night, so we renamed the current directory, and restored from the backup. This seemed to make the 'problem' go away, but I have lost some work in the version c...

When this started happening yesterday, next thing I tried was to put a brand new job into the project, which 'initiaized' fine...just couldn't promote it.

Sorry...put this in the wrong forum...please move to Server.

Hi all I have an issue that has manifested itself in the last 24 hours, and was hoping someone may have some insight into where I can go next in tryin to resolve this issue. We are utilising Version Control for all our promotion processes, and up until yesterday all has been going along well. Our pr...

At that time....'Employee'...no overtime 'it's part of your job'

Not there anymore.

I actually wrote the code, with a lot of help from someone else, in version 6, and have implemented it at 2 different sites I've worked at very successfully. Checkpoint restart was not available in V6, and when you are running a job stream containing over 1500 jobs, you don't want to have to run the...

You may need to be a little careful...one thing I have noted is that the Checkpoint Restart information must be held within the jobs information in Universe, and if for some reason you need to re-build the job you can lose that restart capability (depending on were the error was). :shock: Another so...

Use Export command from the Manager, edit dsx using a text editor, find 'ReadOnly' and change from 1 to 0, and then re-import.

Thanks Ray...

Actually I had the BUILD.INDEX further down in my routine, but seeing as how I couldn't get the CREATE.INDEX to work, the BUILD.INDEX was being bypassed due to the CREATE.INDEX failing....I supplied a code snippet, not the whole routine.

Cheers

Did some more digging and altered the command to now be - Command="CREATE.INDEX " : vHashFile : " " : vIndexCol Call DSExecute('UV', Command, Output, SystemReturnCode) Silly mistake on my part.... :oops: :!: (had local variable within quoted string, instead of concatinating it al...