HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide

Transcription

1 HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide HP Part Number: Published: May 2013 Edition: J06.14 and subsequent J-series RVUs; H06.25 and subsequent H-series RVUs

2 Copyright 2013 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Intel, Itanium, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java is a registered trademark of Oracle and/or its affiliates. Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks and IT DialTone and The Open Group are trademarks of The Open Group in the U.S. and other countries. Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material. 1990, 1991, 1992, 1993 Open Software Foundation, Inc. This documentation and the software to which it relates are derived in part from materials supplied by the following: 1987, 1988, 1989 Carnegie-Mellon University. 1989, 1990, 1991 Digital Equipment Corporation. 1985, 1988, 1989, 1990 Encore Computer Corporation Free Software Foundation, Inc. 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. 1988, 1989 Massachusetts Institute of Technology. 1988, 1989, 1990 Mentat Inc Microsoft Corporation. 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. 1990, 1991 Siemens Nixdorf Informationssysteme AG. 1986, 1989, 1996, 1997 Sun Microsystems, Inc. 1989, 1990, 1991 Transarc Corporation. This software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.

3 Contents About this manual...6 Supported release version updates (RVUs)...6 Audience...6 Related documentation...6 New and changed information...8 What this manual does not cover...8 Document organization...9 Notation conventions...9 General syntax notation...9 Publishing history...11 HP encourages your comments Preparing to install SQL/MX...12 Hardware requirements...12 Software requirements...12 Verifying correct versions of independent software products...13 Starting TMF Installing SQL/MX...14 Summary of installation tasks...14 Preinstallation tasks...14 Using the InstallSqlmx script...14 Phases of InstallSqlmx...15 InstallSqlmx syntax...16 InstallSqlmx command options...16 InstallSqlmx error messages...16 Installing SQL/MX...17 Verifying the SQL/MX installation...18 Overview of automatic file installations...18 Verify that files are licensed...21 Starting MXCI...21 Summary of installed SQL/MX files...22 Verifying executable file versions...25 Post-Installation tasks...26 Reviewing and setting system defaults...26 Installing visual query planner...26 Installing the SQL/MX online help...27 Installing the Windows-hosted SQL/MX C and C++ preprocessor...27 Installing the Windows-hosted SQL/MX COBOL preprocessor Installing a sample database Overview of SQL/MX system upgrade...30 Terminology...30 Upgrading SQL/MX system...30 Guidelines for conducting the system upgrade...31 Conducting the initial upgrade in a test environment...31 Running baseline tests and gathering data at each upgrade phase...31 Assessing the success of the upgrade...31 Assistance with upgrade...31 Product support for NonStop servers...31 NonStop solutions development and implementation...31 Contents 3

4 5 Considerations for upgrading the system to SQL/MX Release System upgrade path...33 Compatibility of SQL/MX Release 3.2 systems...33 Considerations for mixed-node network...34 Working with v3200, v3100, v3000, and v1200 objects in SQL/MX Release New features in SQL/MX Release Considerations for using the Similarity Check feature...36 Implementing the new functionality Upgrading the system to SQL/MX Release Planning for release downgrade...37 Upgrading the system from SQL/MX Release 2.3.x to SQL/MX Release System upgrade sequence...37 Preinstallation...38 Installing SQL/MX Release Accessing the database...39 Upgrading the metadata after system upgrade...40 Migrating applications after system upgrade...40 Upgrading the system from SQL/MX Release 3.0 or Release 3.1 to SQL/MX Release System upgrade sequence...41 Preinstallation...42 Installing SQL/MX Release Accessing the database...42 Upgrading the metadata after system upgrade...42 Migrating applications after system upgrade...42 Upgrading the metadata and using new features on existing and new databases Falling back from SQL/MX Release Fallback paths...46 Fallback sequence...48 Fallback considerations...50 Preinstallation...51 Downgrading the metadata for a system fallback...51 Stopping TMF...52 Installing SQL/MX Release 3.0 or Release Installing SQL/MX Release Accessing the database...53 Converting the CPU list format from SQL/MX Release 3.2 to SQL/MX Release 2.3.x...53 Installing SQL/MX Release 2.x...54 Migrating applications after system fallback...54 Changes required after falling back...54 A Removing security administrator grants...55 B Identifying tables that contain an IDENTITY Column...58 C Identifying tables where the ownership has changed...59 D Version management and interoperability...60 SQL/MX releases...60 SQL/MX releases on systems running H-Series RVUs and J-Series RVUs...60 Naming scheme for SQL/MX releases...60 Product version and SPR identifiers...62 Availability of SQL/MX releases...62 Delivery of SQL/MX releases...62 RVUs and supported SQL/MX releases...62 Interoperability of SQL/MX releases...63 Versions of SQL/MX software components Contents

5 Version identification of SQL/MX software components...63 SQL/MX system software version (MXV)...64 SQL/MX database object versions...64 SQL/MX query plan and module versions...65 Interoperability across schema versions...66 E Conversions...67 Conversions from numeric to char or varchar...67 Index...69 Contents 5

6 About this manual This manual explains how to install SQL/MX Release 3.2 on an HP NonStop server, upgrade metadata, and migrate applications from SQL/MX Release 2.3.x, SQL/MX Release 3.0, SQL/MX Release 3.1 to SQL/MX Release 3.2, and how to manage different versions of SQL/MX. SQL/MX is a relational database management system for the HP NonStop server and is based on the ANSI/ISO/IEC 9075:1999 SQL standard, commonly referred to as SQL:1999. Throughout this manual, references to SQL/MX Release 2.x indicate SQL/MX Release 2.0, SQL/MX Release 2.1, SQL/MX Release 2.2, and subsequent releases. SQL/MX Release 3.x indicates SQL/MX Release 3.0 and subsequent releases until otherwise indicated in a replacement publication. Supported release version updates (RVUs) Audience This publication supports J06.14 and all subsequent J-series RVUs and H06.25 and all subsequent H-series RVUs, until otherwise indicated by its replacement publications. Additionally, all considerations for H-series throughout this manual will hold true for J-series also, unless mentioned otherwise. This manual is intended for database administrators (DBAs), HP support personnel, and others responsible for the installation and configuration of the initial or new versions of SQL/MX software. NOTE: If SQL/MX is already installed, see the Upgrading the system to SQL/MX Release 3.2 (page 37) to ensure that versioning restrictions are considered. Refer to this manual when you plan and implement the upgrade of metadata and the migration of database applications from SQL/MX Release 2.3.x, SQL/MX Release 3.0, and SQL/MX Release 3.1 to SQL/MX Release 3.2. Readers of this manual must have prior knowledge about: The fundamentals of SQL/MX The fundamentals of the NonStop system Related documentation This manual is part of the HP NonStop SQL/MX library of manuals, which includes: Introductory Guides SQL/MX Comparison Guide for SQL/MP Users SQL/MX Quick Start Describes SQL differences between NonStop SQL/MP and SQL/MX. Describes basic techniques for using SQL in the SQL/MX conversational interface (MXCI). Includes information about installing the sample database. Reference Manuals SQL/MX Reference Manual SQL/MX Connectivity Service Administrative Command Reference DataLoader/MX Reference Manual Describes the syntax of SQL/MX statements, MXCI commands, functions, and other SQL/MX language elements. Describes the SQL/MX administrative command library (MACL) available with the SQL/MX conversational interface (MXCI). Describes the features and functions of the DataLoader/MX product, a tool to load SQL/MX databases. 6

7 SQL/MX Messages Manual SQL/MX Glossary Describes SQL/MX messages. Defines SQL/MX terminology. Programming Manuals SQL/MX Programming Manual for C and COBOL Specialized Guides Describes how to embed SQL/MX statements in ANSI C and COBOL programs. SQL/MX Installation and Upgrade Guide SQL/MX Management Manual SQL/MX Query Guide SQL/MX Report Writer Guide SQL/MX Connectivity Service Manual SQL/MX Guide to Stored Procedures in Java NSM/web Installation Guide Describes how to plan to install, create, and upgrade a SQL/MX database. Describes how to manage a SQL/MX database. Describes how to understand query execution plans and write optimal queries for a SQL/MX database. Describes how to produce formatted reports using data from a SQL/MX database. Describes how to install and manage the SQL/MX Connectivity Service (MXCS), which enables applications developed for the Microsoft Open Database Connectivity (ODBC) application programming interface (API) and other connectivity APIs to use SQL/MX. Describes how to use stored procedures that are written in Java within SQL/MX. Describes how to install NSM/web and troubleshoot NSM/web installations. Migration Guides SQL/MP to SQL/MX Database and Application Migration Guide Describes how to migrate databases and applications from SQL/MP to SQL/MX. Online Help The SQL/MX Online Help consists of: Reference Help Messages Help Glossary Help NSM/web Help Visual Query Planner Help SQL/MX Database Manager Help Overview and reference entries from the SQL/MX Reference Manual. Individual messages grouped by source from the SQL/MX Messages Manual. Terms and definitions from the SQL/MX Glossary. Context-sensitive help topics that describe how to use the NSM/web management tool. Context-sensitive help topics that describe how to use the Visual Query Planner graphical user interface. Contents and reference entries from the SQL/MX Database Manager User Guide. The NSM/web, SQL/MX Database Manager, and Visual Query Planner help systems are accessible from their respective applications. You can download the Reference, Messages, and Glossary online help from the HP Software Depot at For more information about downloading the online help, see Downloading online help (page 27). Related documentation 7

8 These manuals are part of the SQL/MP library of manuals and are essential references for information about SQL/MP Data Definition Language (DDL) and SQL/MP installation and management: Related SQL/MP Manuals SQL/MP Reference Manual SQL/MP Installation and Management Guide Describes the SQL/MP language elements, expressions, predicates, functions, and statements. Describes how to plan, install, create, and manage an SQL/MP database. Describes installation and management commands and SQL/MP catalogs and files. New and changed information This manual ( ) includes the following changes: Added a note in Migrating applications after system upgrade (page 42). Added a new section, Considerations for mixed-node network (page 34). The new manual ( ) includes the following changes: The HP NonStop SQL/MX Release 3.1 Installation and Management Guide is consolidated with HP NonStop SQL/MX Release 3.1 Migration Manual and is split into two manuals: HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide Starting with SQL/MX Release 3.2, information related installation and upgrade of SQL/MX is available in this single manual. HP NonStop SQL/MX Release 3.2 Management Manual The contents related to management of an installed SQL/MX database is included in this manual. Added information for mxrpm tool. Added Converting the CPU list format from SQL/MX Release 2.3.x to SQL/MX Release 3.2 (page 39) Added Converting the CPU list format from SQL/MX Release 3.2 to SQL/MX Release 2.3.x (page 53). Included new definitions in Terminology (page 30). Updated vproc information in Verifying executable file versions (page 25). Updated the illustrations to reflect the version changes. What this manual does not cover Migration from SQL/MP to SQL/MX. For more information, see the SQL/MP to SQL/MX Database and Application Migration Guide. Migration from other database vendors to SQL/MX. For assistance, contact your service provider. For more information, see Assistance with upgrade (page 31). Migration of SQL/MX, SQL/MP, and Enscribe databases and applications from an HP NonStop S-series system to an HP Integrity NonStop NS-series system. For more information, see the NonStop NS-Series Database Migration Guide. Migration from Enscribe databases and applications to SQL/MX. An automated tool to convert Enscribe databases and applications to SQL/MX does not exist. The Escort SQL product converts Enscribe databases and applications to NonStop SQL/MP. For more information, see the ESCORT SQL User s Guide, which you can obtain from Carr Scott Software Inc. at If there is sufficient market demand, Carr Scott Software Inc. might consider modifying Escort SQL to support direct Enscribe-to-SQL/MX 8

9 migrations. If you or your customer deems this functionality to be critical to your project, send a note and background on the project to harry.scott@carrscott.com. Migration to format 2 SQL/MP tables. For more information, see the SQL/MP Installation and Management Guide. Document organization This document is organized as follows: Preparing to install SQL/MX (page 12) Installing SQL/MX (page 14) Installing a sample database (page 28) Overview of SQL/MX system upgrade (page 30) Considerations for upgrading the system to SQL/MX Release 3.2 (page 33) Version management and interoperability (page 60) Upgrading the system to SQL/MX Release 3.2 (page 37) Falling back from SQL/MX Release 3.2 (page 46) Removing security administrator grants (page 55) Identifying tables that contain an IDENTITY Column (page 58) Identifying tables where the ownership has changed (page 59) Notation conventions General syntax notation Describes preinstallation requirements. Describes the steps for installing SQL/MX. Describes the steps for installing SQL/MX sample database. Defines upgrade terminology, provides planning considerations, and describes where you can go for further assistance. Discusses the factors that you must consider before upgrading to SQL/MX Release 3.2. Describes SQL/MX releases, interoperability of SQL/MX releases, versions of SQL/MX software components, query plan versioning, and managing a mixed-node network. Provides guidelines for upgrading to SQL/MX Release 3.2. Provides guidelines for downgrading to an earlier version of SQL/MX. Provides example steps for removing any Security Administrator grants prior to falling back to an earlier release of SQL/MX. Provides example steps for removing any identifying tables that contain an IDENTITY column as an aid to falling back to an earlier release of SQL/MX. Provides examples to identify the list of objects in a catalog whose owners are different from their parent schema owners, and the steps to change the ownership of those objects. This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c italic computer type.italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: Document organization 9

10 pathname [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X D ] address { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [, new-value ] [ - ] { } An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char " Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: error := NEXTFILENAME ( file-name ); LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ); If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line 10

11 Publishing history by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [, attribute-spec ] This guide supports HP NonStop SQL/MX Release 3.2 until otherwise indicated by its replacement publication. The publication date and part number indicate the current edition of the document. Part Number Product Version HP NonStop SQL/MX Release 3.2 HP NonStop SQL/MX Release 3.2 Publication Date May 2013 August 2012 HP encourages your comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com. Include the document title, part number, and any comment, error found, or suggestion for improvement concerning this document. Publishing history 11

12 nl 1 Preparing to install SQL/MX Before you install SQL/MX Release 3.2, check that you have met the following installation requirements : Hardware requirements (page 12) Software requirements (page 12) Verifying correct versions of independent software products (page 13) Starting TMF (page 13) Hardware requirements Before you install SQL/MX Release 3.2, your HP Integrity NonStop server must meet these prerequisites. You must install SQL/MX Release 3.2 software from an H-series or J-series RVU or SPR and run it on an Integrity NonStop server with Open System Services (OSS). Hardware Disk Minimum Requirement Minimum three disks: $SYSTEM disk SQL objects disk TMF audit disk Recommended: Minimum 6 disks to include mirrors for the 3 disks Disk space 2 GB of OSS file space 3 GB of $SYSTEM disk 200 MB for the compressed and uncompressed.tar files of the NonStop Server for Java CPU Memory 2 CPUs A minimum of 4 GB for each processor Software requirements To use SQL/MX Release 3.2, you must install the Site Update Tape (SUT) for the H06.25 or J06.14 or a later RVU on your Integrity NonStop system. For more information about installing the NonStop system software, see the H06.25 or J06.14 NonStop Software Installation and Upgrade Guide. The H06.25 and J06.14 or later RVU contains the correct product versions for these key software products that are used with SQL/MX. NOTE: When you install the SUT, the installation automatically copies the files for these software requirements, along with other SQL/MX executables, libraries, and OSS files, to their default locations. Software Requirements Open System Services (OSS), configured TNS/E native C, C++, and COBOL run-time libraries (RTLs) SQL/MX* Installation Manual Open System Services Management and Operations Guide H06.25 or J06.14 Software Installation and Upgrade Guide or TNS/R Native Application Migration Guide (for existing TNS applications) SQL/MX Installation and Upgrade Guide SQL/MX Management Manual 12 Preparing to install SQL/MX

13 Software Requirements TMF HP NonStop TCP/IP Installation Manual TMF Planning and Configuration Guide TCP/IP Configuration and Management Manual *For installation instructions and the latest version requirements, see the Softdoc file delivered with the product, either on the product CD or on the website for Scout for NonStop Servers, at HP NonStop eservices portal: Verifying correct versions of independent software products If you intend to develop and execute Java programs that perform SQL operations or Stored Procedures for Java (SPJs) on your NonStop system, verify that you have installed the correct versions of these independent software products: NonStop Server for Java JDBC/MX driver These independent products need to be ordered separately from the software products provided with the latest product release. For the latest product release information for the JDBC/MX driver, see the JDBC Softdoc and JDBC Driver for SQL/MX Programmer s Reference. The product numbers are minimum versions on systems running H-series or J-series RVUs. For installation instructions and the latest version requirements, see the Softdoc file delivered with the product, either on the product CD or on the website for Scout for NonStop Servers, at HP NonStop eservices portal https//onepoint.nonstop.compaq.com/. Starting TMF To install and then use SQL/MX, it is required that TMF be running and configured for all the data volumes on which SQL/MX objects are created. For more information about TMF auditing requirements, configuration guidelines, and considerations for SQL/MX, see SQL/MX Management Manual and the TMF Planning and Configuration Guide. The product version of TMF provided on the SUT must be compatible with the SQL/MX software provided with the SQL/MX SPR you install. When you start the TMF subsystem, only the accessible configured data volumes are started for transaction processing. You must ensure that the volumes you intend to use for SQL/MX metadata and audited objects are configured and started for transaction processing. You must also ensure that the TMF subsystem as a whole is started for transaction processing. You can request status from TMFCOM by entering the TMFCOM command at the operating-system command interpreter prompt and then issuing specific STATUS commands through TMFCOM. For more information on TMF configuration information, see the TMF Reference Manual. Verifying correct versions of independent software products 13

14 2 Installing SQL/MX Summary of installation tasks If this is the first installation of SQL/MX on your NonStop system, read Using the InstallSqlmx script (page 14) to acquaint yourself with the InstallSqlmx script and its functions during the installation of SQL/MX. If any version of SQL/MX already exists on your NonStop system, see Overview of SQL/MX system upgrade (page 30). To install SQL/MX Release 3.2: 1. Perform the preinstallation tasks described in Preinstallation tasks (page 14) to ensure that your system meets all the hardware and software requirements and that TMF is properly configured and running. 2. Install SQL/MX Release As required, perform the tasks described in Verifying the SQL/MX installation (page 18). These include verifying whether the SUT files were installed in their default locations, checking the SQL/MX files on your system, and verifying the versions of installed executable files. 4. As required, perform the post-installation tasks described in Post-Installation tasks (page 26). Preinstallation tasks 1. Confirm that your NonStop system meets all the hardware and software requirements identified in Preparing to install SQL/MX (page 12). 2. Ensure that TMF is configured and running on the system where you will install SQL/MX. See the guidelines for starting TMF in Preparing to install SQL/MX (page 12). Also, see the TMF Planning and Configuration Guide for TMF installation guidelines. TMF is required for SQL compilation and for execution of all SQL/MX utilities and all DDL and DML statements that require TMF transactions. Note that all SQL/MX objects must reside on volumes audited by TMF. SQL/MX program files need not reside on audited volumes. After verifying the system requirements and performing the preinstallation tasks, you can install the SQL/MX software and the SQL/MX sample database that is distributed with it. You are encouraged to install the SQL/MX sample database and acquaint yourself with SQL/MX and its statements, utilities, and MXCI commands. The sample database is the source for many examples used in the SQL/MX manuals. For instructions on installing the SQL/MX sample database, see Installing a sample database (page 28). Using the InstallSqlmx script The InstallSqlmx script is used only for the first install of SQL/MX, and does the following: Verifies that all processors on the system are valid processor types for SQL/MX Release 3.2. If InstallSqlmx detects a problem, it generates a non-sqlcode error message that identifies the processor or processors that have not met the hardware requirements. For more information about InstallSqlmx error messages, see the SQL/MX Messages Manual. For more information about hardware requirements for SQL/MX Release 3.2, see Hardware requirements (page 12). Verifies that the SQL/MX SPRs are laid down correctly from the SUT installation. Creates an anchor file that specifies the volume location of system metadata tables. CAUTION: The user who runs InstallSqlmx must have super ID (SUPER.SUPER) privileges on the affected node. InstallSqlmx does not support user aliases of SUPER.SUPER. 14 Installing SQL/MX

15 After creating the anchor file, InstallSqlmx assigns a security of N--- to the anchor file. CAUTION: After InstallSqlmx assigns a security of N--- to the anchor file, do not change this setting. If the anchor file is modified, SQL/MX ceases to operate on the system. Initializes SQL/MX after successfully creating the anchor file. Implements the national character set specified with the -n option. Initializes the SQL/MX Connectivity Service (MXCS) after successfully initializing SQL/MX. Verifies that the system metadata tables are created in the specified volume. Performs FCHECK on all volumes on the local node to locate and possibly correct the labels of SQL/MP tables with added columns. This step is optional if NOFCHECK is specified. By default, FCHECK is performed. Phases of InstallSqlmx The following table describes the six phases of activity performed by InstallSqlmx. If InstallSqlmx cannot successfully initialize SQL/MX, it aborts generating a log file. Table 1 The Phases of InstallSqlmx Phase Phase Activities InstallSqlmx verifies that the SQL/MX objects are laid down correctly from the SUT installation. If any required SQL/MX objects are missing from their default locations, InstallSqlmx notifies the user about the missing objects and aborts the installation. For more information on filename and default locations, see Overview of automatic file installations (page 18). Also, see the SQL/MX Management Manual. InstallSqlmx creates an anchor file that contains the location of the SQL/MX system metadata tables. The anchor file is a simple text file with ASCII tokens that identifies the volume where system metadata will reside. The file resides in the Guardian space $SYSTEM.ZSQLMX.MXANCHOR and is assigned a security of N---. InstallSqlmx issues an INITIALIZE SQL statement to initialize SQL/MX. If SQL/MX cannot be successfully initialized, the installation is aborted and the anchor file is removed. Whether initialization is successful or not, InstallSqlmx creates a log at /usr/tandem/sqlmx/bin/initlog. The viewable log file initlog contains status information about the initialization of SQL/MX. The INITIALIZE SQL operation also creates metadata tables for the schema MXCS_SCHEMA in the system catalog. InstallSqlmx also implements the national character set specified with the -n option. The national character set is associated with NCHAR and NATIONAL CHARACTER types and with N string literals, host variables, and SQL functions and predicates. InstallSqlmx loads MXCS metadata tables in the MXCS_SCHEMA of the system catalog with their default values. After loading MXCS metadata tables, InstallSqlmx creates a log at /usr/tandem/sqlmx/bin/mxcslog. The viewable log file mxcslog contains status information about the MXCS initialization operation. InstallSqlmx verifies that the system metadata tables are created in the volume specified with the -l option of the InstallSqlmx command. If the -nofcheck option is not specified, InstallSqlmx performs FCHECK on volumes of the local node to locate SQL/MP tables with added columns. If an SQL/MP table with an added column was duplicated, the addedcolumn flag might not be carried over to the duplicated table, resulting in problems. FCHECK correctly sets this flag for SQL/MP tables with added columns. InstallSqlmx also creates a viewable log at/usr/tandem/sqlmx/bin/fchecklog, that contains details about the FCHECK operation. Using the InstallSqlmx script 15

16 Table 1 The Phases of InstallSqlmx (continued) Phase Phase Activities NOTE: If a large number of disk drives are attached to the local node, the FCHECK portion of InstallSqlmx can take a long time to complete. To avoid this delay, run FCHECK before you run InstallSqlmx. InstallSqlmx syntax InstallSqlmx [-help -h ] options options are: { -l\$volume [-n national_charset_name] [-charset charset_name] [-initmxcs] [-b] [-nofcheck] volume is: the DP2 volume in which to install the system metadata tables You must always specify the -l option first. You can specify other options in any order. InstallSqlmx command options The following table describes the command options for InstallSqlmx. Table 2 InstallSqlmx Command Options Option -b -help -initmxcs -l volume Description Use this option to rebuild the anchor file if it is corrupted. When the -b option is specified, InstallSqlmx searches the system for the system metadata subvolume ZSD0, which must exist at only one location on a system. If InstallSqlmx is run multiple times with multiple -l values then multiple ZSD0s occurs. When InstallSqlmx locates ZSD0, it drops the current anchor file, re-creates it, and adds the correct volume. Use this option to display help information about InstallSqlmx, including command syntax, phase descriptions, option descriptions, syntax examples, and diagnostics information. Use this option to reload the MXCS metadata tables in the MXCS_SCHEMA schema of the system catalog if the default values were not successfully loaded during the first run of InstallSqlmx. Use this option to specify the volume in which InstallSqlmx installs SQL/MX system metadata tables. It is not recommended to specify $SYSTEM. InstallSqlmx determines whether system metadata tables already exist. If they already exist, an error message appears and InstallSqlmx terminates. For more information, see the InstallSqlmx error message information in the SQL/MX Messages Manual. You must always specify the -l option first in the InstallSqlmx script command-line. -n national_charset_name Use this option to specify the name of the national character set for NCHAR/NCHAR VARYING columns. The value for the -n option can be ISO88591, UCS2, KANJI, or KSC5601. If you do not specify a value for the -n option, the national character set defaults to UCS2. -charset charset_name -nofcheck Use this option to specify the default character set [ISO88591 SJIS UNICODE]. If you do not specify, the character set defaults to ISO Use this option to specify that FCHECK must not be performed on local volumes to locate SQL/MP tables with added columns. If this option is not specified, InstallSqlmx automatically performs FCHECK. InstallSqlmx error messages For more information about the non-sqlcode error messages generated by InstallSqlmx, see the SQL/MX Messages Manual. 16 Installing SQL/MX

17 Installing SQL/MX 1. Log on to the NonStop server using SUPER.SUPER (user ID 255,255). 2. Install the required H-series or J-series SUT. Follow all the instructions provided in the associated software release document and any instructions that come with the SUT. For more information about installing the SUT, see the H06.25 and J06.14 Software Installation and Upgrade Guide. 3. As needed, use DSM/SCM to install SPRs to obtain the functionality and defect repair for SQL/MX Release 3.2. For more information about using DSM/SCM, see the DSM/SCM User s Guide. For more information about installing SPRs using DSM/SCM, see the H06.25 or J06.14 Software Installation and Upgrade Guide. Table 3 SQL/MX Release Information for H-Series RVUs Your H-Series RVU H06.25/J06.14 Default SQL/MX Release for this RVU SQL/MX Release If you are using DSM/SCM and your version requires it, run the TACL COPYOSS macro from $SYSTEM.ZOSSUTL. For more information, see the Open System Services Management and Operations Manual and Overview of automatic file installations (page 18). MXCS is automatically installed from the SUT to the Guardian environment, but you must initialize using InstallSqlmx script. For more information on setup and configuration, see the SQL/MX Connectivity Service Manual. NSM/web is automatically installed from the SUT. For setup and configuration information, see the NSM/web Installation Guide. 5. FCHECK is a Guardian program to check the internal consistency of DP2 structured files. For more information, see the DP2 FCHECK User's Guide. If you want to run FCHECK independently of the InstallSqlmx script, do it before you run InstallSqlmx in Step 7. If a large number of disk drives are attached to the local node on your system, the FCHECK portion of InstallSqlmx can take a long time to complete. To run FCHECK independently of InstallSqlmx, issue the command for the volumes you want to check: FCHECK -MXCHECK -VOL $volume If you run FCHECK independently, make sure you specify the -nofcheck option when you run InstallSqlmx. 6. From a TACL prompt, start the OSS shell by entering: osh You are now in the OSS environment. Initializing SQL/MX: The following are the steps to initialize SQL/MX: NOTE: The InstallSqlmx script is required only for the first installation of SQL/MX, or to regenerate the MXANCHOR file deleted accidentally. You can skip the next three steps for a release upgrade. 7. Before running the InstallSqlmx script, change to the correct directory by entering cd /usr/tandem/sqlmx/bin For a detailed description of InstallSqlmx command syntax, command options, and informational messages, see Using the InstallSqlmx script (page 14). Enter all the commands Installing SQL/MX 17

18 in the appropriate case as the OSS environment is case-sensitive. You must be logged on as the super ID user to execute the InstallSqlmx script. CAUTION: InstallSqlmx creates the anchor file and assigns it a security of N----. Do not attempt to change this setting. If you change the security setting, and the anchor file is modified, SQL/MX ceases to operate on the system. 8. Check if this is the first installation of SQL/MX on your system. For example, check if SQL/MX anchor file exists in /G/system/zsqlmx/mxanchor. Running InstallSqlmx more than once with different values of the -l parameter results in a corrupt SQL/MX environment. If no anchor file exists, run the InstallSqlmx script by entering: InstallSqlmx -l \$volume [ -n national_charset_name ] [ -charset charset_name ] [ -nofcheck ] [ -initmxcs ] [ -b ] You must always enter the -l option first. The other options are optional and can be entered in any order. In this next example, the volume $dat215 is specified as the location to which InstallSqlmx installs the SQL/MX system metadata tables. InstallSqlmx -l \$dat215 CAUTION: The volume you specify in the InstallSqlmx command-line identifies the system catalog location for the system metadata tables. The specified volume must be audited. This should not go on the $SYSTEM disk volume. If you replace any disk containing the metadata information, you lose the system metadata information. 9. To develop and execute Java programs that perform SQL operations or SPJs, install NonStop Server for Java and JDBC/MX on your NonStop system. For detailed download and installation instructions, see the README files on the product CDs for NonStop Server for Java and JDBC/MX. Also, see Verifying correct versions of independent software products (page 13). 10. You are now ready to start using SQL/MX. Verifying the SQL/MX installation After you have installed SQL/MX, perform these verification tasks as defined by the features and requirements of your SQL/MX database environment. For more information about The SQL/MX files that are automatically installed during SUT installation The files that need to be licensed and how to verify that they have been properly licensed Descriptions of the SQL/MX files that were installed on your system The executable SQL/MX files installed on your system See Overview of automatic file installations (page 18) Verify that files are licensed (page 21) Summary of installed SQL/MX files (page 22) Verifying executable file versions (page 25) Overview of automatic file installations This subsection identifies the activities that automatically occur during installation of the H06.25 or J06.14 or later H-series or J-series RVU: 18 Installing SQL/MX

19 1. The H06.25 or J06.14 or later H-series or J-series RVU includes SQL/MX executables and libraries. When you install the SUT, the installation automatically copies these files to their default locations: To $SYSTEM.SYSTEM, the files IMPORT,MXTOOL, MXIMPDDL, MXAUDSRV, MXCMP, MXESP, MXOMSG, MXRTDSRV, MXUDR, MXUTP, SQLCLIO, and ESQLCLIO. To $SYSTEM.ZMXTOOLS, the files MXGNAMES, MXVQP, T0607SET,and T0610SET. To $SYSTEM.ZMXODBC, the files MXOAS, MXOCFG, MXODSN, MXOSRVR,and TDMODBC. 2. The SUT installation automatically copies these PAX files to $SYSTEM.ZOSSUTL, a temporary OSS directory on your system: T0517PAX, which contains the setmxdb script file. T0611PAX, which contains the system module and user module files. T1050PAX, which contains the SQL/MX internal module files. T1051OBJ, which contains the object files sqlcli.o, esqlcli.o, and the ANSI names server process executable, ansp.exe. T1051PAX, which contains the header files Platform.h, mxmaintain, and sqlcli.h. T1052PAX, which contains mxsqlc, the SQL/MX C/C++ preprocessor. T1053PAX, which contains mxsqlco, the SQL/MX COBOL preprocessor. T1054PAX, which contains mxci, the SQL/MX conversational interface. T1056PAX, which contains mxtool, import, mximportddl, and mxexportddl. T1056INI, which contains InstallSqlmx. T1057PAX, which contains the SQL/MX agent (tdm_br.tlo). T1058PAX, which contains mxcierrors.cat, the MXCI-related error messages file. T1231PAX, which contains the SQL/MX language manager files mxlangman.jar and mxlangman.policy. 3. The SUT installation automatically installs the public DLLs ZCLIDLL and ZCLIPDLL to the $SYSTEM.ZDLLnnn subvolume, where nnn is a number picked by the public DLL installation during the SYSGEN operation. The SQL/MX Release 3.2 installs YCLIDLL, which is a 64-bit version of ZCLIDLL. CAUTION: It is expected that DSM/SCM is installed on each Integrity NonStop system on which you install the DLLs. DSM/SCM handles DLL licensing automatically. If you do not use DSM/SCM to install the DLLs, you must license the DLLs by other means. Processor halts can occur if the DLLs are not licensed properly. Verifying the SQL/MX installation 19

20 4. The SUT installation automatically installs the EMS events file, ZMXSTMPL, to $SYSTEM.ZTEMPL. 5. In addition, DSM/SCM automatically uses the COPYOSS macro to install these OSS files to these OSS directories: a. COPYOSS installs these files in the OSS directory /usr/tandem/sqlmx/bin: InstallSqlmx mxci mxcierrors.cat mxcompileusermodule mxexportddl mxsqlc mxsqlco setmxdb ansp.exe mxrpm b. COPYOSS installs these system module files in the OSS directory, /usr/tandem/sqlmx/systemmodules: NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.CMNAMEMAPSQLM NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.CMSMDIOREADM NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.CMSMDIOWRITEM NONSTOP_SQLMX_NSK.MXCS_SCHEMA.CATANSIMX NONSTOP_SQLMX_NSK.MXCS_SCHEMA.CATANSIMXGTI NONSTOP_SQLMX_NSK.MXCS_SCHEMA.CATANSIMXJAVA NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.READDEF NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.RFORK NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.SQLHIST NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.SQLUTILS NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.SQLJ NONSTOP_SQLMX_NSK.SYSTEM_SCHEMA.ANSINAMES c. COPYOSS installs these user module files in the OSS directory, /usr/tandem/sqlmx/usermodules: NONSTOP_SQLMX_NSK.SCH.MXGNAMES d. COPYOSS installs these files in the OSS directory /usr/tandem/sqlmx/include: Platform.h sqlcli.h tdm_br.tlo e. COPYOSS installs these files in the OSS directory, /usr/tandem/sqlmx/lib: sqlcli.o esqlcli.o f. COPYOSS installs these SPJ product files in the /usr/tandem/sqlmx/udr directory: mxlangman.jar 20 Installing SQL/MX

21 mxlangman.policy mxudr.mak mxt_install.ksh mxtool_install_procs mxtool_verify.jar CAUTION: Do not move the mxlangman.jar file to a location outside the installation directory, /usr/tandem/sqlmx/udr. If you do, you will encounter problems invoking SPJs. For more information, see the SQL/MX Guide to Stored Procedures in Java. Verify that files are licensed Make sure that all these files are licensed in $SYSTEM.SYSTEM: IMPORT MXUTP MXIMPDDL MXAUDSRV MXCMP MXESP MXRTDSRV ZCLIPDLL (this is found under $SYSTEM.ZDLLnnn) MXTOOL Starting MXCI To verify that these files are licensed: 1. From a TACL prompt, issue a FILEINFO command on each of the files. IMPORT, MXAUDSRV, MXCMP, MXESP, MXRTDSRV, MXUTP, MXIMPDDL and MXTOOL reside in $SYSTEM.SYSTEM.ZCLIPDLL resides in $SYSTEM.ZDLLnnn. To find out if a file (for example, MXCMP) is licensed, enter FILEINFO MXCMP 2. Verify that each of these file shows an L after the file code. The L confirms that the file is licensed. For example: $SYSTEM.SYSTEM CODE EOF LAST MODIFIED OWNER RWEP PExt SExt MXCMP 800L JAN2011 1:17 255,255 NUNU MXCI runs as an OSS process and must be started from within the OSS environment. NOTE: Check that the file mxci in the OSS directory /usr/tandem/sqlmx/bin is secured for read and execute access to your node. If it is not secured for execute access, you cannot start it. If necessary, use the OSS command chmod to change the options. To start MXCI: 1. At a TACL prompt, start the OSS shell by entering: osh Verifying the SQL/MX installation 21

22 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 Executable 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. File Name ansp.exe mxrpm MXAUDSRV MXCMP MXESP MXRTDSRV MXUDR Description The OSS file for the ANSI names server process (ANSP), which provides ANSI-to-Guardian name mapping for NonStop utilities. The OSS tool for reprocessing module files. The SQL/MX audit fixup server, a licensed Guardian code 800 file, which performs audit fixup for online MODIFY 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. The SQL/MX compiler, a licensed Guardian code 800 file, which compiles DML queries, and executes DDL and utility commands. The SQL/MX executor server process, a licensed Guardian code 800 file used for parallel execution of queries. MXESP processes are started and stopped automatically as required. Do not attempt to run MXESP. A licensed Guardian code 100 file that acts as an external bridge to provide a link between SQL/MX and NonStop SQL/MP through the SQL/MX compiler (MXCMP). MXRTDSRV processes are started and stopped automatically as required. Do not attempt to run MXRTDSRV. Where Installed /usr/tandem/sqlmx/bin /usr/tandem/sqlmx/bin $SYSTEM.SYSTEM $SYSTEM.SYSTEM $SYSTEM.SYSTEM $SYSTEM.SYSTEM A Guardian 800 code file which acts as a layer of $SYSTEM.SYSTEM software between the SQL/MX executor and JVM that 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. MXUTP MXOMSG IMPORT MXTOOL A licensed Guardian code 800 file for the materialized view feature, which is not supported with SQL/MX Release 3.2. MXUTP processes are started and stopped automatically as required. Do not attempt to run MXUTP. A message file associated with MXCS. The IMPORT utility, which resides in the Guardian file space and is a licensed Guardian code 800 file. An OSS command-line utility, which is a licensed Guardian code 800 file, performs various utility functions such as fixup, goaway, info, verify, and cleanup. $SYSTEM.SYSTEM $SYSTEM.SYSTEM $SYSTEM.SYSTEM $SYSTEM.SYSTEM 22 Installing SQL/MX

23 File Name MXIMPDDL MXGNAMES import mxci mxcompile nl UserModule mxexportddl mxsqlc mxsqlco mxtool Description An OSS command-line utility, which is a licensed Guardian code 800 file, replicates the DDL definition and statistics of SQL/MX objects. The Guardian code 800 file for the MXGNAMES utility. The symbolic OSS link to the IMPORT utility that resides in Guardian file space. The OSS file for the SQL/MX conversational interface (MXCI). To run mxci, you must be in the OSS environment. The command-line tool used to produce compiled module definitions for embedded applications. For more information, see the SQL/MX Programming Manual for C and COBOL. The OSS file for the mxexportddl utility. See SQL/MX Management Manual. Where Installed $SYSTEM.SYSTEM $SYSTEM.ZMXTOOLS /usr/tandem/sqlmx/bin /usr/tandem/sqlmx/bin /usr/tandem/sqlmx/bin /usr/tandem/sqlmx/bin The OSS-based C preprocessor to preprocess embedded /usr/tandem/sqlmx/bin SQL statements in C/C++ programs. The preprocessor replaces SQL statements in C/C++ programs with C function calls to the call-level interface (CLI). For details on mxsqlc, see the SQL/MX Programming Manual for C and COBOL. The OSS-based COBOL preprocessor to preprocess embedded SQL statements in COBOL programs. For details on mxsqlco, see the SQL/MX Programming Manual for C and COBOL. A link to $system.system.mxtool utility. /usr/tandem/sqlmx/bin /usr/tandem/sqlmx/bin SPJ product files These product files are necessary for developing and executing stored procedures in Java (SPJs) in SQL/MX: File Name mxlangman.jar mxlangman.policy Description A JAR file that contains Java bytecode that implements part of the SQL/MX language manager, an application program interface (API) that the SQL/MX UDR server calls to load, invoke, and unload SPJs. For more information on SPJs, see the SQL/MX Guide to Stored Procedures in Java. A policy file that ensures the security and proper operation of SPJs in SQL/MX. For more information on the policy file, see the SQL/MX Guide to Stored Procedures in Java. Where Installed /usr/tandem/sqlmx/udr /usr/tandem/sqlmx/udr Verifying the SQL/MX installation 23