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

NOTE: Recompiling programs might result in different execution plans, causing a change
in performance.
• The online dumps taken on SQL/MX Release 3.2 cannot be used by TMF recovery on SQL/MX
Release 3.1, SQL/MX Release 3.0 or on SQL/MX Release 2.x. HP recommends that you take
new full TMF online dumps immediately after fallback.
• If security administrators have granted any privileges on database objects after upgrading to
SQL/MX Release 3.2, you should consider revoking those privileges before downgrading to
SQL/MX Release 3.0 or earlier. Although the privileges granted by security administrators to
database objects will apply in earlier SQL versions, attempts to modify those privileges through
REVOKE on those objects will fail because the security administrator grants will be viewed as
dependent privileges by earlier SQL versions. You can address this issue in one of the following
ways:
1. Prior to falling back to an earlier SQL version, all grants performed by security
administrators must be revoked. For steps to identify and revoke these grants, see
“Removing security administrator grants” (page 55). HP recommends this method unless
you want to retain the existing privileges (for example, for operational reasons), in which
case the second method must be considered.
2. After falling back, the owner of each object affected by security administrator grants must
GRANT, to the security administrator username (for example, “SECADMIN.USER1”), the
same privileges, WITH GRANT OPTION, that the security administrator had granted
while acting as a Security Administrator (GRANT ALL ...WITH GRANT OPTION can be
used). Alternatively, the super ID can be used to perform the GRANT instead of the object
owner. This action connects the "orphaned" security administrator grants to the owner.
The reconnected grants can then either be left in place, or removed by the owner (or the
super ID) using the REVOKE statement.
• Databases created after upgrading to SQL/MX Release 3.1 can include an IDENTITY column.
You cannot remove an IDENTITY column from a table. You must remove all tables with IDENTITY
columns before downgrading to an earlier version. You can save the data in tables with a
similar layout, but without the IDENTITY column, and retrieve after a downgrade. However,
using the saved tables instead of those with IDENTITY columns will require changes to the
applications. For steps to identify tables that contain an IDENTITY column, see “Identifying
tables that contain an IDENTITY Column” (page 58).
NOTE: This consideration is applicable only if you downgrade to SQL/MX Release 3.0 or
earlier.
• Using the Alter View statement, you must disable views that have Similarity Check enabled.
Preinstallation
You must complete the following steps before installing SQL/MX Release 3.1, SQL/MX Release
3.0 or SQL/MX Release 2.x:
• “Downgrading the metadata for a system fallback” (page 51)
• “Stopping TMF” (page 52)
Downgrading the metadata for a system fallback
You might have to use the DOWNGRADE utility when you perform a system fallback from SQL/MX
Release 3.2 to SQL/MX Release 3.1, SQL/MX Release 3.0 and to SQL/MX Release 2.3.4.
Preinstallation 51