ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-14
Restoring an Old NonStop ODBC Server System
3. Back up all the old NonStop ODBC Server SQL/MP catalog tables and views from
the desired user catalogs. A BACKUP command such as the one in the preceding
example works if there are no user table names starting with the letters ZN or ZV.
4. Back up all the old NonStop ODBC Server software and any associated
configuration information (such as the SCS configuration files). These should be
put into a single location, allowing them to be referenced by the NOSU200 utility.
5. If your old NonStop ODBC Server system supported stored procedures and you
have stored procedures installed, there is usually nothing you need to do for a
NonStop ODBC Server upgrade. If, however, you are backing up an entire
NonStop ODBC Server system, including the Pathway systems used for stored
procedures, there is one issue to consider: the stored procedure names registered
with the NonStop ODBC Server.
When you back up the NonStop ODBC Server catalogs, the registered names are
included. The name of the Pathmon process for the Pathway system and the
server class name are part of the information registered with the stored procedure
name.
If you later restore the system, you must verify this information. The utility
statements VALIDATE and REFRESH do not include this information, so you must
do it manually. If any of the information has changed (for example, the Pathway
system is restored differently), you must use NOSUTIL to delete the stored
procedure name and then reregister it.
After the backup procedure is complete, the NonStop ODBC Server can be installed
according to the instructions under NonStop System Installation on page 2-15. If, after
the NonStop ODBC Server is installed, you want to revert to the old NonStop ODBC
Server, you must restore the older system you backed up.
Restoring an Old NonStop ODBC Server System
The restoration process is as follows:
1. Deinstall the new NonStop ODBC Server:
a. Stop all SCS processes to prevent new connections and to stop all processes
associated with the NonStop ODBC Server.
b. Use NOSCOM to deinstall the system catalog and all user catalogs. Note that
any SQL/MP objects created through the NonStop ODBC Server are also
dropped.
c. Remove all NonStop ODBC Server software.
Note. It is generally not necessary to back up SQL/MP objects owned by users. The
restoration process described in the next subsection resynchronizes the old catalogs with
the SQL/MP objects. However, if the database is very small, it might be more convenient
to back up everything.