Description

The bdbpre tool reads selected tables for given company numbers, exports the data from the tables into sequential data, and writes the data to a standard output. You can then redirect this output to a file that can be used as input for bdbpost.

The bdbpre tool prints information such as names, the number of records, and any errors. You can use the –s option to suppress the messages that are produced by bdbpre at run time. This option is useful when you use the output of bdbpre as the direct input to bdbpost.

ION Workflow operation

If a table is part of a Workflow model, it is checked whether all tables that are part of the workflow model are selected for the dump. The table list is verified against the workflow models to see whether all tables of a model are included in a dump, and whether a table has been deployed in a company.

If a table is part of a Workflow model, additional information is dumped in the table dump headers. This information includes the model and the deployment that are related to the tables dumped. This information is used by bdbpost to validate the dumped model and deployment against the model and deployment in the environment during import.

To control some of the workflow related actions, see the –W <dbcm options>.

To find information on DBCM related trace output, use the –X <trace options>. Add -Y to add even more trace output.

Note: The –t or –x options are not supported when dumping workflow data, unless you use the –W ignoredbcm option.

Table dump headers are only added to the dump if a table with DBCM is enabled and deployed.

The fd6.2.package combination file is always used to search dictionary information.

You can use bdbpre in these ways:

Specify a range of company numbers to convert a database table for more than one company number, for example:
```
bdbpre –Ntimcs099 –C000-005 > timcs099_dump
```
Convert a database table for given company numbers, for example:
```
bdbpre –Ntimcs088 –C000 004 005 > timcs088_dump
```
Specify all the tables for which you want to create a sequential dump in some file in package module format. The –I option reads this file and creates a sequential dump for each table and the specified company numbers, for example:
```
bdbpre –Iseqfile –C000-009 > BIGdump 
The contents of the seqfile: 
timcs001
timcs002
timcs003
........
timcs099
```

Possible options:

–u/U
Print usage information.
–v/V
Print information about the version of bdbpre.
–p package combination
The name of package combination that is to be used.
–s
Suppress error messages, statistics, and so on.
–C
Company numbers for a given table, in these two formats:
- Specific company numbers, for example, 001 002 003
- Range of company numbers, for example, 001-999
–d
Specify a specific driver. If you use this option, bdbpre bypasses the tabledef6.2 file.

You can use the -d option to copy data from one instance of a database to another, for example:
```
-d “oracle(ORACLE_HOME=/usr/oracle, ORACLE_SID=D1)”
```
Explicit specification of database driver:
```
bdbpre -doracle8 -Ntimcs000 -C000-004 >
timcs000_dump
```
The database driver is retrieved from $BSE/lib/tabledef6.2:
```
bdbpre -Ntimcs000 -C000-005 >
timcs000_dump
```
-g
Skip export of logical linked tables.

Without using –g all tables will be exported, also the tables that originate in another physical company.
–N table [table...]
Database table name. Specify specific table names, for example, –N timcs000 timcs016. The –I and –N options are mutually exclusive.
–I file
Input file with table names. The –I and –N options are mutually exclusive.
–E file
Redirects errors and information to file.
–O file
Redirects output to file.
–q output file
Deprecated: Use –E and –O instead.

Redirect terminal output to the output file.
-F
Include referential integrity counters. This option is used to prevent running refint after importing the dump. When you use this option, ensure to export and import a complete set of tables. Only a complete set contains actual valid values of the referential integrity counters. Importing a partial set will result in invalid counter values, causing possible data loss.
–k
Drop table after the dump is created.
–K
Drop table. Create a backup before dropping. You can only use this option if supported by the DBMS.
–t separator character
Create a sequential file in which the fields have variable length and are separated by the separator character ( | ). Whenever you specify the –t option, a sequential file (.S) is created for each table in the current directory, unless the –o option is specified.
```
bdbpre -t"|" -Ntimcs016 -C000
```
Creates timcs016000.S in the current directory. This sequential file is an ASCII dump of the timcs016000 table, in which case the separator character separates the fields.

The -x and -t options are mutually exclusive.
-L lang
In an environment where multiple data languages are used, you can make a dump with just one data language. The –L option can be used to specify the data language to be exported. The data language is a code according to ISO639.2 and must be configured in the target environment.

The default behavior, without using the –L option, is to export all data languages.
–x
Create a sequential file in which the fields have a fixed length and are not separated with a separator character. Whenever you specify the –x option, a sequential file (.F) is created for each table in the current directory, unless the –o option is specified.

bdbpre –x –Ntimcs016 –C000 creates timcs016000.F, which is an ASCII dump with fixed-length records.
–o
This can be specified with the options –x and –t to specify the directory name in which the sequential file is created (.S or .F).
–M size
This can be specified with the options –x, and –t to specify the maximum size of the output file. If the maximum file size is reached, a new file with a sequence number is opened and filled. You can specify size as any number of bytes, or a number followed by K, M, or G, for kilobytes, megabytes, or gigabytes, respectively. The maximum size is 2 GB.
-W all
Create a dump with both checked-in and checked-out data if applicable.
-W ci
Create a table dump with only checked-in data.
-W nomodelcheck
Allow to dump a table that is part of a model where other tables that are part of this model are not dumped. Workflow information is dumped in the table dump headers and incomplete modules are marked as incomplete.
-W notablesharingcheck
Allow to dump tables and companies where not all the companies are present in the company set(s) that define a deployment. This applies only to models and deployments that use the ForeignCompnr in the Relation section of an object model.
-W ignoredbcm
Completely ignore DBCM information. No checked-out data is dumped and no workflow information is stored in the table dump headers.
-W type=dbcm model type
Dump all tables which are found in <dbcm model type>.

For example, this command dumps all tables found in model chm100:
```
bdbpre –W type=chm100 –C000-005 > dbchm100_dump
```
The options -W type=dbcm model type -I and -N are mutually exclusive.

You can specify multiple -W type=type options on the command line. This can be useful if a table is shared among multiple models.
-X stderr
Redirect bdbpre trace information to stderr.
-X filename
Redirect trace output to filename.
-Y
Do not allow UTC times later than 2038-01-19 03:14:07 (numerical value above signed 32-bit maximum 2147483647).
-Y
Additional tracing information.