Exporting and Importing Partition Policies and Details

Partition Policies and Partition Policy Details can be dumped and loaded in standard ABL .d format using standard Data Admin Utilities. Note that the utility only know these by their physical table name _partition-policy and _partition-policy-detail and display this in the user interface and expect this as input in the dump and load .p APIs. This also includes OEM table dump and load support. The DataAdmin Utilities allows both the class name and physical database name to be used.

The data that are written to the .d does NOT correspond to the physical storage. These tables have relations that are stored with internal identifiers that cannot be used to export for the purpose of importing (recreating) the tables in another database instance.

The standard .d backwards compatibility rule/contract applies in the sense that the order of the data in the .d will not change in future releases and new fields/properties will always be added to the end of the exiting list to ensure that a .d can be safely imported in a new version.

The export and import methods of the collections for these classes also support the .d format in addition to the JSON format. The type is specified and identified by the extension of the file name passed in the file name parameter.

WARNING: These methods do not support or handle code page and format information in the .d file and will use current session settings both for export and import. They should thus only be used for short lived export/import in the same session or in cases where this is controlled. It is important to use the Data Admin table dump and load tools for regular data management purposes to ensure that the data includes code page and format settings that allows data to be safely loaded independent of session settings.

One benefit of the export and import methods versus data admin table utilities is that the collections can be filtered allowing export of subsets of data.