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

migrations. If you or your customer deems this functionality to be critical to your project, send
a note and background on the project to [e-mail].
• Migration to format 2 SQL/MP tables. For more information, see the SQL/MP Installation and
Management Guide.
Document organization
This document is organized as follows:
Describes preinstallation requirements.“Preparing to install SQL/MX” (page 12)
Describes the steps for installing SQL/MX.“Installing SQL/MX” (page 14)
Describes the steps for installing SQL/MX sample database.“Installing a sample database” (page 28)
Defines upgrade terminology, provides planning
considerations, and describes where you can go for further
assistance.
“Overview of SQL/MX system upgrade” (page 30)
Discusses the factors that you must consider before
upgrading to SQL/MX Release 3.2.
“Considerations for upgrading the system to SQL/MX
Release 3.2” (page 33)
Describes SQL/MX releases, interoperability of SQL/MX
releases, versions of SQL/MX software components, query
plan versioning, and managing a mixed-node network.
“Version management and interoperability” (page 60)
Provides guidelines for upgrading to SQL/MX Release 3.2.“Upgrading the system to SQL/MX Release 3.2” (page 37)
Provides guidelines for downgrading to an earlier version
of SQL/MX.
“Falling back from SQL/MX Release 3.2” (page 46)
Provides example steps for removing any Security
Administrator grants prior to falling back to an earlier
release of SQL/MX.
“Removing security administrator grants” (page 55)
Provides example steps for removing any identifying tables
that contain an IDENTITY column as an aid to falling back
to an earlier release of SQL/MX.
“Identifying tables that contain an IDENTITY Column”
(page 58)
Provides examples to identify the list of objects in a catalog
whose owners are different from their parent schema
“Identifying tables where the ownership has changed”
(page 59)
owners, and the steps to change the ownership of those
objects.
Notation conventions
General syntax notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words.
Type these items exactly as shown. Items not enclosed in brackets are required. For
example:
MAXATTACH
lowercase italic letters. Lowercase italic letters indicate variable items that you
supply. Items not enclosed in brackets are required. For example:
file-name
computer type. Computer type letters within text indicate C and Open System
Services (OSS) keywords and reserved words. Type these items exactly as shown.
Items not enclosed in brackets are required. For example:
myfile.c
italic computer type.Italic computer type letters within text indicate C and
Open System Services (OSS) variable items that you supply. Items not enclosed in
brackets are required. For example:
Document organization 9