I’ve found a little problem with refreshdb when used on some platforms, so a bug fix was required. It was just a silly little typo that meant when the MAXPROC_UNLOAD or MAXPROC_LOAD limits were reached, the script would exit. This was because I used == instead of = in a test statement, me thinks I must have being too much Ab Initio work at the time!

Sorry for any inconvenience, please download version 2.1 from the usual place.

A new version of refreshdb is now available from my software index page.

refreshdb 2.0 has (quite aptly) only two changes:

• Implemented MAXPROC_UNLOAD and MAXPROC_LOAD as replacement of MAXPROC parameter to allow a differing number of parallel processes for the unload and load stages. This was implemented because it was found that in most cases there are less issues with multiple unloads than loads, more could be done at once. Splitting MAXPROC into two parameters allowed for this tuning.
• Only show one “MAXPROC* level (num) hit…” message per wait, instead of wasting log space by repeating the same message unnecessarily.

Hope these little changes are useful to someone (they are to me)!

I have released another version of my Informix database refresh script called refreshdb after discovering a serious flaw, the below describes what’s changed:

Fixed daft “feature” that enabled triggers, indexes and constraints after each chunk of data was loaded. Now enables after all chunks loaded. Seriously improves the speed of the script!

Various small updates to supporting files and added contact details.

You can get the latest version of refreshdb from the refreshdb software page.

Oops, I’ve found a little bug whereby one more process was run than requested. Not a big bug, but annoying, so I’ve fixed it.

Also, I seem to have let the -a option creep back in for the split of the unload file, now banished!

You can get version 1.5 of refreshdb from this page.

A new version of refreshdb has been released!

This version has a few small bug fixes and updates to comments, as well a major change in the position of the process flow for splitting the unload files ready for load into the target database tables.

The split of the unload file now happens as soon as the data has been unloaded from the source table. This enables the refreshdb script to be used to load data into more than one database at the same time, as long as the -u option is used to suppress any further unloads. For normal operation you will not see any real difference in how refreshdb works.

Hope you find this change and the little fixes useful.

Please scoot over to the refreshdb page for more information about refreshdb and to download it.

refreshdb v1.3 is available here.

WARNING: Regardless of the version, this software should always be regarded as Beta quality, I can not, and will not, take any responsibility for any damage that using this software may cause. I regard it as software that gets the job done, it’s not pretty, and not a true reflection of my skills, but it did the job for me!

Having said that, go download it, read the source, and if you like it have a go at creating a test or development copy of your favourite Informix IDS 7.x/9.x database!

If you can’t understand the source please don’t use it.