DSXchange

Each connected client takes a shared lock on a non-existent record. list_readu | grep DS.ADMIN should give you a list of connected clients. Pipe through wc -l to get a count of connected clients. The DS_LICENSE table has five fields, though only one is defined in its dictionary. Field 1 - client lic...

I usually claim that the keyboard can't spell in these cases.

There is no such thing as "DataStage for DataWarehousing". There are four separate products. What they have in common is that they all perform extraction, transformation and loading (ETL). The target does not need to be a data warehouse for any of them. DataStage server DataStage parallel DataStage ...

Run it from your own script, capturing the start and finish times therein.

Try something like

I think you've successfully isolated it to be associated with the Orchestrate environment. Were APT_CONFIG and APT_ORCHHOME set for the user ID with which you started the Analysis Server? Not that that should matter, I'm clutching at straws a bit here. You don't even need DataStage and Analysis Serv...

Welcome aboard. :D The link row count tells you how many rows DataStage sent to Oracle. It does not tell you how many were accepted by Oracle. Look in the job log (Director client, Log view) to see whether any warnings were generated by Oracle. Chances are that there is one (or two maybe) for each r...

Does your job design include an after-stage or after-job subroutine?

If not, then you have incompatible versions of the internal DataStage routines DSP.Open and DSP.Close installed - check with your support provider.

True. I was. There ain't no such thing as a DataStage EXE, as Ken has pointed out. DataStage server jobs are best thought of as executing in a virtual machine called the "DataStage run machine". You can only run DataStage jobs where this is installed. But you can remotely execute using dsjob (which ...

A Difference or Compare stage may be better suited to your requirements. With a Change Capture stage you lose information about one of the sources.

No, but I've never created a job with so many stages. What does your support provider have to say?

Which makes it more likely that the cause is lack of SELECT privilege on the relevant system tables.

The best command to see what's happening with licences is uv -admin. uv -admin -lic_report - also available as dslictool - shows server licence usage. uv -admin -info shows connected clients (and, implicitly, client licence usage). dslictool clean_lic -a can be used to recover disused licence seats.

Be patient. It's not far off now. If you were to read a readme file from the beta versions it may turn out to be inaccurate.

After you run the start command, is there a process ID 721044 (check with ps -ef | grep 721044 | grep -v grep)?

Did you check the log files on the Analysis Server ? They should be in a directory called logs if I recall correctly.