SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide—523353-004
2-10
Additional Installation Considerations
Additional Installation Considerations
Installation of SQL/MP might require installation of a specific version of related
software. For versioning requirements of products associated with SQL/MP, check the
documentation supplied with your software.
If you install an SPR to the T6570 - National Language Character Processing product,
you must SQL compile the collation compiler manually. For more information, see Step
8 on page 2-4.
If you plan to define large numbers of partitions for tables and indexes in the database,
consider using the =_SQL_CAT_HEAP_LIMIT DEFINE to increase the heap space
size limit for the catalog manager process. For more information, see the SQL/MP
Reference Manual or SQLCI online help. You can specify this DEFINE in the
TACLCSTM file for TACL sessions running applications or interactive queries.
Reinstalling SQL/MP Software
To reinstall SQL/MP on a node that has previously run the software, follow the steps
listed under Installing SQL/MP on page 2-2.
Note that if you have installed SQL/MP on your node before, you do not need to re-
create the system catalog.
Migrating to a Newer Software Version
To replace an existing version of the SQL/MP software, install the newer version of the
software as described under Installing SQL/MP on page 2-2.
After you install the new version of SQL/MP software, follow these guidelines:
•
Continue to run existing applications without recompilation.
•
Continue to use existing local user catalogs until you are ready to start using the
new features provided with the newer version of SQL/MP. You can continue to use
your existing system catalog indefinitely, unless you plan to register newer version
objects in the system catalog.
•
Continue to access all local and remote objects in your database, except for
remote objects registered in catalogs whose versions are newer than the version of
the SQL/MP software on either the local or remote node. For information about
managing a network that has multiple versions of software, catalogs, and objects,
see the SQL/MP Version Management Guide.
•
Test the newly installed software before you use new features. This evaluation
might require running the new software for several days of testing or simply
running your applications under the new software for however long is appropriate.
You can also test the new software by using the sample database distributed with
your older RVU or by using your own test database.