Hi again,
1) If DEV IFMX version is higher than the PROD version and both version are compatible in terms of in-place migration, ontape or onbar restore could be a candidate. In this case, you backup PROD and perform a cold(offline) restore on DEV, that will act as an in-place migration. But prerequistes are
* all chunks full paths names in production must be creatable in the DEV environment
* DEV environment disk space must be equal or higer than PROD
* ontape will take all the databases to DEV, you cannot select only one
* onbar could only take some of the dbspaces, but as you need to perform a cold restore, this won't work.
2) onunload / onload can be a good candidate if both IFMX versions are "compatible" ( ie not very different ). These tools are fast ( keep the IFMX binary pages ), and you can choose only one database. In addition, it will not recreate the full chunks on the DEV environment, which may be an issue with ontape/onbar.
3) most simple and with no constraints is:
* dbexport -ss databasename on prod
* drop databasename on dev
* dbimport databasename on dev
But it takes much more time if the prod database is big!
4) you are in version 10, so you cannot take benefit on EXTERNAL TABLES, so we'll have to forget about this one.
What are your constraints and try to get exact versions number for source and destination.
Thanks
Eric