Hi,
Go to thread http://www.baanboard.com/baanboard/showthread.php?threadid=24423 for bdbpost.
bdbreconfig6.1 [-uUvVscinmfTZ] [-t dir] [-o file] [-p pack.comb]
[-e file] [-N table(s)] [-d Dr type] [-I file]
[-C company number(s)]
bdbreconfig6.1 reads a table name and company number(s) given as arguments and converts them into a new table definition matching the new data dictionary definition. It requires a new data dictionary with a `.new' extension, the current data dictionary (e.g.dtimcs016) and tables matching those in the current data dictionary. After successful completion, old tables are deleted and new tables are generated. bdbreconfig6.1 finds the optimum way to reconfigure and if there is no real change in two data dictionaries (e.g. dtimcs016 and dtimcs016.new) it prints the message "No conversion required". Furthermore it sees to it that a database remains consistent. When more than one table is given to be reconfigured and if an error occurs in the middle of the operation, it reverts to the original state.
In some situations reconfiguration is done by just modifying the old data dictionary, otherwise the reconfiguration steps are:
1. Compare two (current and .new) data dictionaries.
2. If reconfiguration is required, create a sequential dump
(R.<table name>, e.g. R.timcs016244) for the specified tables.
3. Delete old tables.
4. Build new tables from sequential dump matching the new data dictionary definition.
The following options are available with bdbreconfig6.1:
-U/u: Usage information.
-V/v: Version information.
-p : Name of used package combination.
-s : Suppress Messages
This will suppress error messages and other information.
-T : Reconfigure only in case of record format change.
-R : Force to use dump for recovery.
-B : Backup table in stead of dropping
-Z : Reorganize (clean up) table.
-i : Ignore errors during reconfiguration.
-n : Ignore referential integrity constraints.
-m : Disable domain constraints.
-f : Fast rebuild of table (first rows, then indexes)
-N : List of tables to be reconfigured.
-d : Database Driver type, see bdbpre6.1 for
specifications.
-c : This will compare two data dictionaries and will
only check for reconfiguration.
-t : Directory name for (temporary) dump files.
-I : File with table names to reconfigure.
-o : File with successfully reconfigured tables.
-e : File with unsuccessfully reconfigured tables.
-C : Company number(s) for given table (2 formats)
1. Specific company number(s) (e.g. 001 002 ...)
2. Range of company numbers (e.g. 001-010)
bdbreconfig6.1 will reconfigure only one table of given company number(s) at a time.
Example:
bdbreconfig6.1 -Ntimcs016 -C001 reconfigures timcs016 for company no. 001
bdbreconfig6.1 -Ntimcs016 -C000-010 reconfigures timcs016 for a range of company numbers.
If used without the -c option the exit status will be either 0 or 1 depending on successful or unsuccessful completion. If exit status is 1 (unsuccessful) the file specified at option -o contains tables which can be reconfigured, the file at option -e contains the tables which cannot. If used with the -c option the file specified at option -o contains table names which are find correct, the file specified at option -e contains table names which must be reconfigured. In case of interrupted reconfiguration while the R.<table> file
still exists, the following command: bdbreconfig6.1 -N ttadv100222+ will use the dump R.ttadv100222 to rebuild the table. (Warning: make copy of dump before doing this !!)
EXAMPLES
bdbreconfig6.1 -Ntimcs016 -C000-003
Reconfigures timcs016 for some company numbers according to the new data dictionary, provided that dtimcs/dtimcs016 and dtimcs/dtimcs016.new are present. bdbreconfig6.1 -dbisam -Ntimcs016 -C000
Viplov