Download Latest Version
tpc-c-ifmx.tar.gz (392.7 kB)
Get an email when there's a new version of IIUG Software Repository
| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| map_dbspaces.ksh | 2021-01-01 | 2.2 kB | |
| myexport | 2021-01-01 | 12.5 kB | |
| myimport | 2021-01-01 | 15.9 kB | |
| to_external.awk | 2021-01-01 | 969 Bytes | |
| tst2.map | 2021-01-01 | 65 Bytes | |
| tst.map | 2021-01-01 | 115 Bytes | |
| ak_launcher.c | 2021-01-01 | 12.9 kB | |
| from_external.awk | 2021-01-01 | 1.3 kB | |
| Mapfiles.README | 2021-01-01 | 1.9 kB | |
| README.1st | 2021-01-01 | 12.8 kB | |
| myexport.tar.gz | 2020-05-11 | 45 Bytes | |
| README | 2019-03-04 | 12.6 kB | |
| complex.dbspace.file | 2014-07-29 | 629 Bytes | |
| makefile | 2009-09-10 | 27 Bytes | |
| simple.dbspace.file | 2009-09-10 | 36 Bytes | |
| Totals: 15 Items | 74.1 kB | 0 | |
This document describes how to create and use dbspace map files: If myimport is executed with the -T <dbspace-map> option the named map file will be used to remap source schema dbspace names to target schema space names. The the map file should contain specifications as described below, one per line. There are three whitespace separated fields the first two of which are required, the third field is optional: source-name target-name type source-name is the name of a dbspace in the source schema file. target-name is the name of the dbspace to replace the source name with in the target database. type is an optional flag to specify which types of dbspaces are to be replaced. The options are: D - table spaces only, I - index spaces only, S - SmartBlob spaces only, B - dumb Blob spaces only (dumb blobs support the special "dbspace" name "TABLE" indicating that the source or target should be move from or to tablespace. If no type field is included the mapping will be applied to all objects placed in the source dbspace. Order of the specifications is important as they are each applied to all matching lines sequentially. This can have some interesting ramifications. For example, you could swap all objects between two dbspaces like this: fromdb1 temp1 fromdb2 fromdb1 temp1 fromdb2 Examples: The following moves all data spaces (tables) from dbspace1 to new_dbs1 and all index spaces from dbspace1 to new_idx1. dbspace1 new_dbs1 D dbspace1 new_idx1 I One caviat: The current version of myimport uses sed for the mapping and cannot differentiate between PARTITION clauses for tables and those for indexes, so "D" type mappings will also map partitioned index partitions that were stored in the source dbspace as well as tables and table partitions. Future releases may fix this issue.