DSXchange

It looks like "ODBC_SQL_BYR" is your source stage name. This is a semi-educated guess... The first job log entry "ODBC_SQL_BYR: Connected to Microsoft SQL Server ..." is connecting in order to gather and/or validate metadata and check to see if it matches what you have defined on...

Just curious, what was different back when it used to take under an hour? What all has changed since then?

We standardized on using 2770 permissions and also follow it with a chmod -R o-rx command on the directory that holds the DataStage project subdirectory and all the related subdirectories of our own making.

I would recommend contacting Support to request a patch. If there's not already a patch available for that, then there should be.

Note that creation timestamp and last modified timestamp are two different fields and also just because the last modified timestamp is newer does not necessarily mean that the job was modified. It could simply indicate that the same existing job design was imported and overwritten.

Yep, since there weren't really any other topics about Blueprint Director, I figured the best chance to find out if anyone used it would be to "chime in" on a 5-year old topic with the very few folks who touted it back when it was new-ish.

While you're talking with Support, you may also want to ask what to replace the CDC Transaction stage with in the future after you upgrade to DataStage 11.7 or newer because that stage has been deprecated, and documentation on a replacement stage or migration path has not yet surfaced.

Did anyone ever find uses--creative or otherwise--for Blueprint Director? I noticed it was listed on the IBM License Information documents up through Information Server Enterprise Edition 11.3.1 but is no longer listed for 11.5 or 11.7. When I explored the tool myself, its value was not very clear t...

She has help many many a time over the years too. :) If you do go that route, make sure to import into a new project, as in newly created and empty, in order to lower the risk. Importing back into the same project would certainly be riskier! But I'm not against it, as I've been doing that way myself...

To Craig's point, we are not the official support provider, so it's too early to conclude that there is no way to connect. Contact support to confirm. I hope there is a way or there will be a way soon. If you do contact support, please let us know what you find out. There is also this IBM technote w...

A quick quote from https://blog.panoply.io/a-comparative-vmariadb-vs-mysql : MariaDB is a fork of MySQL (and yes, it is designed to be a drop-in replacement) ... - data and table definition files are compatible - client protocols, structures, and APIs are identical - MySQL connectors will work with ...

Just a guess: most likely it will be or has been replaced by Kafka. In fact, if you look in the DataStage Designer 11.7 on the palette under the Real Time category, there is a Kafka Connector stage where the CDC Transaction stage used to be. Furthermore, the CDC stage is still there in 11.7 if you l...

I would manually hand-select and export the jobs of interest to a dsx file and do a find/replace on the folder/category names then import into a new project. Not much risk there. I would not think to automate such a thing unless there are plans to repeat the same type of activity numerous times.

We copy the template file dssendmail_template.txt to a new file named dssendmail.txt and make our customizations on the new file, and we set permissions to 640 on each file. Check to see if you have this other file as well and check the permissions. Also check your recipient value to make sure it do...

The command and the options we ran it with essentially had the effect of immediately truncating several related XMETA database tables at once, so use with great care and caution... ./xmetaAdmin.sh deleteOneModel -dbfile ../conf/database.properties -model OMDModel Again, if you're on an older version...