DSXchange

If you're familiar with the dsenv file for DataStage, all you need to do is copy the environment variables pertaining to your DB2 connect installation location. You're correct, they go into the .ctl file for the analysis server. Make sure you restart the analysis server in order to make the changes ...

I see what you're saying now, Roy. You really do need to profile each sub-schema of the flat file independently. Which would mean spinning those related records into separate sequential files. That should still be possible in DataStage (CFF Stage to Transformer to multiple Sequential Files). dscnn, ...

I have a complex file that needs to be profiled. There is a post on this earlier and it was suggested to break up similar rows into seperate bunches and then profile them. But what is the use of buying the tool if it has to be done manually? Is there any other better way to profile complex format d...

Actually, you can call ProfileStage packages at the command line. You posted the same question on Developer Net, so check there for my response.

Sorry, good ol' USA support engineers. :wink: Yes we did receive a patch, and it resolved the SIGBUS/SIGSEGV errors that were coming from this bug. We now have been able to reenable time-based monitoring. Check with your support engineer for the patch under ecase e74035. We received a patch for both...

One annoying thing about ProfileStage is the fact that it doesn't cleanup after itself. For every action you perform (analyzing, importing metadata, etc), it generates several flat files to keep track of that job (*.log, *.ini, *.err, *cleanup.log, etc). Not to mention that the Analysis Server and M...

Just in case others were curious, the official word I got from Ascential was they wouldn't support using drivers other than DataDirect for ProfileStage. This isn't to say it's not possible, it's just not supported. I'm still waiting to hear back from them in regards to whether this will change with ...

Is it working on any other desktops? How about on a different project? That may indicate whether the problem is just on your computer, or with a specific project, or possibly with the Unix server.

Since this is Windows, you can use the tried and true method of reboot! Seriously, did you happen to install the Multi-Client Manager? If so, open that up, select the version that you have installed and change to that version (even if it's already selected). This goes through and registers all your ...

Yes, the sparse lookup is possible via the enterprise stage, but only when going against a non-mainframe UDB/DB2. You can only connect to mainframe using the API stage (unless on USS), which doesn't support sparse lookup. The trick on an AIX or Sun platform is that you have to make sure that all the...

Hi there, Who will use ProfileStage: Data Modeller or ETL developer? At which stage or stages of your project, do you use ProfileStage: project analyzing stage, data model, or ETL coding? Thanks, Yes and yes. Your data modeller and person developing your ETL designs will find it of most use. If you...

Y'know, trainee, I'd be interested to know if you had configured your DSN using the wired protocol driver, or just the standard Oracle driver. You shouldn't have had problems with TNSNAMES.ORA entries if using the wired protocol driver (or so says Data Direct!). That's supposed to bypass client soft...

Ray was correct in that ProfileStage error handling is unlike any of IBM/Ascential's other tools. That error is a generic error that means you've opened a socket to your database, but don't receive a timely response. I've gotten it trying to connect to DB2 and Oracle sources. The other common generi...

The PX engine is the same Orchestrate framework that Datastage uses. We don't presently have it licensed, but had an evaluation copy a while back, so I've configured it and used it briefly. It's pretty slick and easy to setup. However, you're not platformed properly. The PXEngine presently ONLY work...

I needed to understand how is it possible for multiple users (different users) to connect to the same profiling repository. If you're using Windows, use active directory to create a security group. Lump all users into that security group, and then add that security group to your SQL Server and pres...