Logically related, nonpartitioned databases

A partitioned and nonpartitioned database can be logically related. When converting logically related databases to partitioned, only one of the databases need to be converted at a time. It is not necessary to convert all logically related databases to partitioned at the same time, although it is recommended that all logically related databases be partitioned.

Besides orderly migration, another advantage of allowing a partitioned and nonpartitioned database to be logically related is when a logically related database violates the restrictions for partitioned databases.

Logically Related, Nonpartitioned Databases

image2018-12-20_10-6-10.png

If a database has virtually logical children, the database with the logical parent can still be converted to a partitioned database as long as symbolic logical parent pointers are used. The logical parent in the partitioned database can have logical child pointers to the logical child in a nonpartitioned database.

Prefix resolution and update are required when reorganizing a nonpartitioned database with logical child or direct logical parent pointers from a partitioned database. If the logically related partitioned database is also being reorganized, all the partitions must be reorganized because Prefix Resolution requires records from all partitions. If only the partitioned database is being reorganized, prefix resolution and update are not required, and individual partitions can be reorganized.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*