SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)
Table Of Contents
- HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide
- Contents
- About this manual
- 1 Preparing to install SQL/MX
- 2 Installing SQL/MX
- Summary of installation tasks
- Preinstallation tasks
- Using the InstallSqlmx script
- Installing SQL/MX
- Verifying the SQL/MX installation
- Post-Installation tasks
- 3 Installing a sample database
- 4 Overview of SQL/MX system upgrade
- 5 Considerations for upgrading the system to SQL/MX Release 3.2
- 6 Upgrading the system to SQL/MX Release 3.2
- 7 Falling back from SQL/MX Release 3.2
- A Removing security administrator grants
- B Identifying tables that contain an IDENTITY Column
- C Identifying tables where the ownership has changed
- D Version management and interoperability
- SQL/MX releases
- Interoperability of SQL/MX releases
- Versions of SQL/MX software components
- E Conversions
- Index
You are now in the OSS environment.
2. Enter the mxci command to start MXCI. Enter the command in lowercase as the OSS
environment is case-sensitive.
The MXCI session begins, and the MXCI prompt (>>) appears.
For more information about MXCI commands, see the SQL/MX Reference Manual.
Summary of installed SQL/MX files
After the SUT is installed, these SQL/MX files are installed on your system as described next. You
must run all OSS files from OSS.
Executable files
Where InstalledDescriptionFile Name
/usr/tandem/sqlmx/binThe OSS file for the ANSI names server process (ANSP),
which provides ANSI-to-Guardian name mapping for
NonStop utilities.
ansp.exe
/usr/tandem/sqlmx/binThe OSS tool for reprocessing module files.mxrpm
$SYSTEM.SYSTEMThe SQL/MX audit fixup server, a licensed Guardian code
800 file, which performs audit fixup for online MODIFY
MXAUDSRV
and POPULATE INDEX operations after a fuzzy data copy
is created. During MODIFY and POPULATE INDEX
processing, the MXAUDSRV is started and stopped
automatically as required. Do not attempt to run
MXAUDSRV.
$SYSTEM.SYSTEMThe SQL/MX compiler, a licensed Guardian code 800
file, which compiles DML queries, and executes DDL and
utility commands.
MXCMP
$SYSTEM.SYSTEMThe SQL/MX executor server process, a licensed Guardian
code 800 file used for parallel execution of queries.
MXESP
MXESP processes are started and stopped automatically
as required. Do not attempt to run MXESP.
$SYSTEM.SYSTEMA licensed Guardian code 100 file that acts as an external
bridge to provide a link between SQL/MX and NonStop
MXRTDSRV
SQL/MP through the SQL/MX compiler (MXCMP).
MXRTDSRV processes are started and stopped
automatically as required. Do not attempt to run
MXRTDSRV.
$SYSTEM.SYSTEMA Guardian 800 code file which acts as a layer of
software between the SQL/MX executor and JVM that
MXUDR
supports SPJs in SQL/MX. MXUDR processes are started
and stopped automatically as required. Do not attempt to
run MXUDR.
For more information on SPJs, see the SQL/MX Guide to
Stored Procedures in Java.
$SYSTEM.SYSTEMA licensed Guardian code 800 file for the materialized
view feature, which is not supported with SQL/MX Release
MXUTP
3.2. MXUTP processes are started and stopped
automatically as required. Do not attempt to run MXUTP.
$SYSTEM.SYSTEMA message file associated with MXCS.MXOMSG
$SYSTEM.SYSTEMThe IMPORT utility, which resides in the Guardian file
space and is a licensed Guardian code 800 file.
IMPORT
$SYSTEM.SYSTEMAn OSS command-line utility, which is a licensed Guardian
code 800 file, performs various utility functions such as
fixup, goaway, info, verify, and cleanup.
MXTOOL
22 Installing SQL/MX