The following changes in Adaptive Server version 15.0 affect upgrade and server functionality:
System catalogs use row “anchors” that are stored in a per-database pseudo-catalog named sysanchors. Like sysgams, sysanchors is not a normal database table and cannot be queried.
Most system catalogs are row-locked.
An object’s partition ID is unique to that object.
The following are additional issues that you should consider when you migrate to Adaptive Server 15.0 and later:
What Adaptive Server called “partitions” in previous releases are now called “slices,” and are obsolete. When you upgrade from version 12.5.x and earlier, Adaptive Server 15.0 and later changes all database tables, including the slice-partitioned tables supported in version 12.5.x, into unpartitioned tables. Indexes do not change; they remain global and unpartitioned. If you want partitioned tables, you must repartition them manually after the upgrade.
During migration syspartitions is renamed sysslices. This data is used only during upgrade, after which it is removed. sysslices remains as an empty table after the upgrade process completes.
This release uses more procedure cache than previous releases. The amount of procedure cache varies with the application, but generally, Adaptive Server 15.0 uses appoximately 10% more than previous releases.
Adaptive Server restricts you from running load tran commands that reissue a create index that require a redo of a sort from older Adaptive Server releases. Adaptive Server recovers logs containing this operation up to the point that the create index first occurs, and invalidates subsequent load tran commands. You cannot run another load tran command until you first run a load database command.
