InstallSqlmx script

This subsection describes the informational messages that the InstallSqlmx script generates:

  • Errors Install0001 through Install0011 are generated when the InstallSqlmx script sets up the anchor file.

  • Errors Install0012 through Install0019 are generated when InstallSqlmx initializes NonStop SQL/MX.

Install0002

Install0002: SQL/MX cannot find any instance of metadata on this system. You cannot use the rebuild option. The SQL/MX installation has aborted.

Cause You attempted to use the Rebuild (-b) option on a system that has not performed an INITIALIZE SQL operation.

Effect The operation fails.

Recovery If you believe that the system metadata exists, contact your service provider. Otherwise, run the InstallSqlmx script without specifying the Rebuild (-b) option.

Install0003

Install0003: Multiple instances of metadata exist on this system. You cannot use the rebuild option.

Cause You attempted to use the Rebuild (-b) option while multiple instances of the system metadata exist on the system.

Effect The operation fails.

Recovery Multiple instances of system metadata are not allowed on the same system. Contact your service provider.

Install0004

Install0004: SQL/MX is already installed in volume.

Cause You cannot install NonStop SQL/MX at the volume volume . NonStop SQL/MX has already been installed.

Effect The operation fails.

Recovery None.

Install0005

Install0005: The anchor file does not exist, but metadata tables exist on volume. Use the -b (Rebuild Anchor File) option to recreate the anchor file.

Cause There is a mismatch between the system metadata and the anchor file. The anchor file no longer exists. However, the system metadata still exists at the volume volume.

Effect The operation fails.

Recovery Use the Rebuild Anchor File (-b) option to recreate the anchor file.

Install0006

*** ERROR [Install0006] A location for the system metadata must be specified using the -l option.

Cause You specified the InstallSqlmx Location (-l) option more than once.

Effect The operation fails.

Recovery Remove duplicate entries for the Location (-l) option and retry the request.

Install0007

Install0007: A volume name for the metadata must be specified along with the -l option.

Cause You did not specify a system metadata location.

Effect The operation fails.

Recovery Rerun the InstallSqlmx script and use the Location (-l) option to specify a volume name.

Install0008

Install0008: The -nofcheck option must be specified after the -l option.

Cause The -nofcheck option must be specified after the -l option. You specified it before.

Effect The operation fails.

Recovery Rerun the InstallSqlmx script and specify the -nofcheck option after you specify the -l option.

Install0009

Install0009: The -n option must be specified after the -l option.

Cause The -n option must be specified after the -l option. You specified it before.

Effect The operation fails.

Recovery Rerun the InstallSqlmx script and specify the -l option before you specify the -n option.

Install0010

Install0010: The command line argument argument is invalid.

Cause You specified an invalid argument with argument .

Effect The operation fails.

Recovery Enter one of these three options (-l, -b, or -help) and retry the request.

Install0011

Install0011: Invalid character set specified with the -n option. Valid character sets are ISO88591,UCS2,KANJI or KSC5601.

Cause You specified an invalid character set.

Effect The operation fails.

Recovery Specify a valid character set and retry the request.

Install0012

Install0012: The SQL/MX initialization failed. Check /usr/tandem/sqlmx/bin/initlog for details. Phase 3 failed.

Cause The initialization operation failed because of an error.

Effect The operation fails.

Recovery Check other errors that are returned to determine the cause of the failure. After the failure has been fixed, retry the request.

Install0013

*** ERROR [Install0013] The MXCS initalization failed. Check /usr/tandem/sqlmx/bin/mxcslog for details.

Cause MXCS is installed by creating a special MXCS_SCHEMA. The process of creating this schema has failed.

Effect The operation fails.

Recovery Check other errors that are returned to determine the cause of the failure. After the failure has been fixed, retry the request.

Install0014

Install0014: Missing file: filename Reinstall the missing SQL/MX files from the SUT and restart the SQL/MX installation.

Cause SQL/MX files installed from the SUT are missing.

Effect The operation fails.

Recovery Reinstall the missing SQL/MX files from the SUT and restart installation.

Install0015

Install0015: Missing file: filename. Not all metadata tables and MXCS tables were created and initialized properly.

Cause The process of creating the metadata tables or MXCS tables has failed.

Effect The operation fails.

Recovery Check other errors that are returned to determine the cause of the failure. After the failure has been fixed, retry the request.

Install0016

Install0016: Could not create directory-name directory.

Cause A directory needed for installation could not be created.

Effect The operation fails.

Recovery Determine the cause of the directory creation failure. After the failure has been fixed, retry the request.

Install0017

Install0017: Only the SUPER.SUPER user can execute InstallSqlmx.

Cause You attempted to execute Installsqlmx, but you are not the super ID. Only the super ID can perform this function.

Effect The operation fails.

Recovery Log on as the super ID before executing this command.

Install0018

Install0018: A processor on the system does not meet the hardware requirements for SQL/MX.

Cause One or more processors in the system do not meet the minimum hardware requirements for installing NonStop SQL/MX. All processors in a node on which NonStop SQL/MX Release 2.0 (or a superseding product) is installed must be Model 1954 (S72000) or newer.

Effect The operation fails.

Recovery See the SQL/MX Installation and Management Guide to verify that your system meets all the hardware requirements for installing NonStop SQL/MX.

Install0019

Install0019: File file-name was not found, but is present only if the DDL licensing product was not installed. If the DDL licensing product was installed, refer to the SQL/MX Messages Manual for recovery details.

Cause The SQL/MX file file-name is not present.

Effect The installation of NonStop SQL/MX continues. This warning can be ignored if the DDL licensing product (T0394) was not installed. If the DDL licensing product was installed, NonStop SQL/MX is not fully functional, and the steps described under Recovery must be performed.

Recovery If the DDL licensing product was installed, reinstall the missing SQL/MX file from the SUT. If the missing file was MXGNAMES, issue these commands from OSS:

cp/usr/tandem/sqlmx/bin/mxgnames/G/SYSTEM/ZMXTOOLS/MXGNAMES

gtacl -c 'fup alter \$SYSTEM.ZMTOOLS.MXGNAMES code 700'