SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)

nonstop_sqlmx_<system>.system_schema.cat_references cr
where cs.replication_rule = 'A'
and cs.cat_uid = cr.cat_uid
and cr.replication_rule = 'M';
Unregister these catalogs from the corresponding systems using the UNREGISTER CATALOG
command. For UNREGISTER CATALOG considerations, see the SQL/MX Reference Manual.
• Remote catalog registrations — Check if the catalogs on the systems that must remain at lower
release are registered on the systems that need to be upgraded. Execute the following query
on the system that must be upgraded to obtain the list of registered catalogs :
select cs.cat_name
from nonstop_sqlmx_<system>.system_schema.catsys cs
where cs.replication_rule = 'M';
Unregister these catalogs from the system to be upgraded using the UNREGISTER CATALOG
command. For UNREGISTER CATALOG considerations, see the SQL/MX Reference Manual.
• RDF replication — You can use RDF to replicate from a system running earlier SQL/MX release
to a system running later SQL/MX release. You cannot use RDF and replicate from a system
running a later SQL/MX release to a system running an earlier SQL/MX release. Do not use
RDF to replicate from an SQL/MX Release 3.x system to an SQL/MX Release 2.3.x system.
Working with v3200, v3100, v3000, and v1200 objects in SQL/MX
Release 3.2
In SQL/MX Release 3.2, a catalog can contain v1200, v3000, v3100 or v3200 schemas, but
not a mixture of the versions.
A CREATE SCHEMA statement creates a new schema of the same version as those schemas that
already exist in the catalog. For example, suppose that a catalog contains some v3000 schemas.
The version of a new schema that is created in that catalog will be 3000.
By default, schemas created in new catalogs are v3200. You do not have to perform additional
steps to create v3200 schemas.
You must perform these additional steps only when a v1200 or v3000 or v3100 schema is required
in a new catalog that does not already contain any schema.
For example, to create a v3100 schema in a new catalog, you must enter the following control
query default command before you issue the CREATE SCHEMA statement:
control query default create_definition_schema_version '3100'
If the system schema version is 3000 or later, you cannot create a v1200 schema. After executing
the UPGRADE ALL METADATA command, you cannot create v1200 schemas.
Irrespective of the schema version, no explicit action is needed to create or maintain individual
database objects such as tables, indexes, and views.
For more information on commands, see the SQL/MX Release 3.2 Reference Manual.
New features in SQL/MX Release 3.2
SQL/MX Release 3.2 introduces the following new database features:
• Similarity Check for Views
• Subqueries in WHEN clause for AFTER triggers
• Calling SPJs from Triggers
For more information on the new features, see the SQL/MX Reference Manual.
After upgrading to SQL/MX Release 3.2, you can use the new features on your 3.2 database and
new applications. You can also use the new features on older databases and applications. In this
scenario, you only need to upgrade the metadata in affected catalog to use the new features.
Working with v3200, v3100, v3000, and v1200 objects in SQL/MX Release 3.2 35