SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

HP NonStop SQL/MX Database and Application Migration Guide—540435-005
12-1
12
Falling Back to NonStop SQL/MP
This section describes falling back from NonStop SQL/MX to NonStop SQL/MP. Plan
for a potential fallback to NonStop SQL/MP before you install NonStop SQL/MX and
start developing SQL/MX applications and database objects. That way, if necessary,
you can fall back from NonStop SQL/MX more easily. For more information, see
Planning for Fallback
on page 9-3.
If you encounter a serious problem with NonStop SQL/MX and need to fall back to an
SQL/MP environment, read this section carefully and understand it fully before
attempting the fallback procedure.
Steps for Falling Back to NonStop SQL/MP
Because NonStop SQL/MP and NonStop SQL/MX can coexist on a NonStop system
and because NonStop SQL/MP is available on each RVU of the NonStop system,
falling back to NonStop SQL/MP from SQL/MX Release 2.x does not require that you
reinstall a previous RVU.
SQL/MX Release 2.x applications that you develop before falling back to SQL/MP
database objects are not usable if you drop referenced SQL/MX objects or if you
uninstall NonStop SQL/MX.
To fall back to NonStop SQL/MP:
1. Stop using the SQL/MX applications.
2. Resume using the SQL/MP applications and database objects.
3. To reclaim the space used by the SQL/MX database objects, identify and drop all
the SQL/MX database objects, including both user tables and system metadata
tables.
a. To determine a complete list of SQL/MX schemas on the system, query the
system metadata. For example, this command returns all the schemas,
including system schemas, that are visible on the node named FIGARO:
>> set schema nonstop_sqlmx_figaro.system_schema;
>> select substring(schema_name,1,30) as schema_name,
substring(cat_name,1,20) as cat_name, node_name
from schemata s, catsys c, cat_references cr
where s.cat_uid=c.cat_uid
Note. If you encounter the problem when using new features that are specific to NonStop
SQL/MX, consider discontinuing the use of those features instead of falling back.