RBThe Data Warehouse Company

Transcription

1 RBThe Data Warehouse Company RED BRICK WAREHOUSE Version 5.1 INSTALLATION AND CONFIGURATION GUIDE for UNIX Platforms

2 The information in this document is subject to change without notice and does not represent a commitment by Red Brick Systems. The software and/or databases described in this document are furnished under a license agreement and can be used or copied only in accordance with the terms of the agreement. Except as permitted by such license, no part of this document and/or database may be reproduced or transmitted in any form or by any means, electronic or mechanical (including photocopying and recording), or transferred to information storage and retrieval systems without the written permission of Red Brick Systems. Restricted Rights: Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at 48 CFR , as applicable. Copyright Red Brick Systems, Inc. All rights reserved. Printed in the USA. RISQL, Red Brick, the Red Brick logo (RB), and The Data Warehouse Company are registered trademarks of Red Brick Systems, Inc. Red Brick Data Mine, Red Brick Data Mine Builder, Red Brick Vista, STARindex, STARjoin, TARGETindex, and TARGETjoin are trademarks of Red Brick Systems, Inc. All other trademarks are the properties of their respective companies. Revision number: 1 January, 1998 Part number: Red Brick Systems, Inc. 485 Alberto Way Los Gatos, California USA Telephone: RBThe Data Warehouse Company

3 Contents Contents About This Document Purpose vii Audience vii Organization viii Related Documentation ix Conventions xii Customer Support xiii Support Solutions Warehouse xiii General and Technical Questions xiii Troubleshooting Tips xv Documentation Questions and Comments xv 1 Preparing for an Installation Preview of Preparation Tasks 1-2 Determining the System Shell 1-3 Verifying Operating-System Version and Disk Space 1-4 Operating-System Version 1-5 Disk Space 1-7 Considerations for NFS Filesystems 1-8 Configuring Operating-System Parameters 1-9 Determining the Locale 1-10 Locale Components 1-10 Defining the Warehouse Locale 1-11 Selecting a Warehouse Logical Name 1-12 Selecting an IPC Key for the Warehouse Daemon 1-13 Identifying a Shared Memory Map File 1-15 Determining the TCP/IP Port for the Red Brick Warehouse Daemon 1-16 Creating the redbrick Account 1-17 Creating the redbrick Directory 1-18 Providing License Keys 1-18 Choosing an Installation Procedure 1-19 Checklist of Preparation Steps 1-20 Installation and Configuration Guide iii

4 Contents 2 Installing Red Brick Warehouse Before You Begin 2-2 Preview of Installation Tasks 2-3 Mounting and Unmounting the CD-ROM Device 2-4 Mounting the CD-ROM Device 2-4 Unmounting the CD-ROM Device 2-5 Running the Installation Script 2-6 Stopping the Installation 2-8 Specifying the Warehouse Directory 2-8 Specifying the Locale 2-9 Installing the Administration Database 2-12 Installing the Sample Database 2-12 Specifying the Tape Device (Tape Installation Only) 2-13 Providing IPC Key or Memory Map File and User Information 2-13 Specifying the TCP/IP Port for the Red Brick Warehouse Daemon 2-14 Specifying the Maximum Number of Servers 2-14 Finishing the First Phase of Installation 2-15 Enabling Red Brick Warehouse and Optional Products 2-16 Product Licenses for Red Brick Warehouse 2-17 Product Licenses for Red Brick Warehouse for Workgroups 2-17 Entering License Keys 2-18 Starting the Red Brick Warehouse Daemons 2-19 Verifying the Red Brick Warehouse Installation 2-22 Checklist of Installation Tasks Installing a New Release Running Two Releases of Red Brick Warehouse 3-3 Preview of Installation Tasks 3-4 Installing Red Brick Warehouse 3-4 Redirecting Client Applications for Test Purposes 3-5 Migrating Databases to the New Release 3-5 Upgrading Databases 3-6 Migrating Users to the New Release 3-7 Replacing an Existing Warehouse with the New Release 3-8 Shutting Down the Daemons 3-8 Installing the New Release 3-9 Starting the Daemons 3-9 Upgrading Existing Databases 3-9 Announcing the New Release 3-9 Checklist of Installation Tasks 3-10 iv Installation and Configuration Guide

5 Contents 4 Installing Red Brick Client Products Before You Begin 4-2 Mounting and Unmounting the CD-ROM Device 4-2 Running the Installation Script 4-3 Installing Client Products 4-6 Specifying the Installation Directory 4-6 Specifying the Host Name 4-6 Specifying the TCP/IP Port for the Red Brick Warehouse Daemon 4-7 Installing Additional Red Brick Client Products 4-8 Enabling RISQL Reporter 4-9 Checklist of Installation Tasks Miscellaneous Administrative Tasks Administering Warehouse Daemons 5-2 Checking Active Daemons 5-2 Stopping Active Daemons 5-2 Configuring Daemons for Automatic Startup 5-2 Changing the Simultaneous Connections Limit 5-3 Changing the redbrick User ID 5-4 Adding a New User ID 5-4 Changing the Name of the User ID 5-5 A Warehouse Directories and Files B Recommended Locale Specifications C Platform-Specific Information: IBM RISC System/6000 Configuring Operating-System Parameters C-1 General Guidelines C-1 Number of Users and Parallel Query Processes C-2 Limits File Settings C-2 Configuring Daemons for Automatic Startup C-3 D Platform-Specific Information: Digital AlphaServer Configuring Operating-System Parameters D-1 General Guidelines D-1 Number of Users and Parallel Query Processes D-2 Kernel Parameters D-2 Configuring Daemons for Automatic Startup D-5 E Platform-Specific Information: HP 9000 Computer Configuring Operating-System Parameters E-1 General Guidelines E-1 Number of Users and Parallel Query Processes E-2 Kernel Parameters E-2 Configuring Daemons for Automatic Startup E-5 Installation and Configuration Guide v

6 Contents F Platform-Specific Information: Sun SPARC-Based Systems Configuring Operating-System Parameters F-1 General Guidelines F-1 Number of Users and Parallel Query Processes F-2 Kernel Parameters F-2 Configuring Daemons for Automatic Startup F-5 G Platform-Specific Information: Silicon Graphics Servers Configuring Operating-System Parameters G-1 General Guidelines G-1 Number of Users and Parallel Query Processes G-2 Kernel Parameters G-2 Configuring Daemons for Automatic Startup G-4 H Platform-Specific Information: Sequent Symmetry System Configuring Operating-System Parameters H-1 General Guidelines H-1 Number of Users and Parallel Query Processes H-2 Kernel Parameters H-2 Configuring Daemons for Automatic Startup H-6 I Platform-Specific Information: NCR WorldMark Servers Configuring Operating-System Parameters I-1 General Guidelines I-1 Number of Users and Parallel Query Processes I-2 Kernel Parameters I-2 Configuring Daemons for Automatic Startup I-5 J Platform-Specific Information: Unisys U6000 System Configuring Operating-System Parameters J-1 General Guidelines J-1 Number of Users and Parallel Query Processes J-2 Kernel Parameters J-2 Configuring Daemons for Automatic Startup J-5 Loading Data from ANSI Standard-Labeled Tapes J-6 Index vi Installation and Configuration Guide

7 About This Document Purpose Audience This Installation and Configuration Guide describes how to install Red Brick Warehouse and configure it for use on the following UNIX platforms: IBM RISC System/6000 with the AIX operating system. Digital AlphaServer with the Digital UNIX operating system. HP 9000 Computer with the HP-UX operating system. Sun SPARC based system with the Solaris operating system. Silicon Graphics Server with the IRIX operating system. Sequent Symmetry System with the DYNIX/ptx operating system. NCR WorldMark Server with the NCR UNIX SVR4 MP-RAS operating system. Unisys U6000 with the Unisys UNIX System V operating system. Appendixes C through J of this guide also contain platform-specific information for Red Brick Warehouse running on each of the supported platforms. Information common to all UNIX platforms is found in the Warehouse Administrator s Guide for UNIX Platforms. The intended users of this guide are system administrators and database administrators who plan the warehouse installation, configure the operating system, install the software, and maintain the data warehousing environment. Knowledge of the operating system and basic system administration procedures is assumed. Installation and Configuration Guide vii

8 About This Document Organization Organization This guide is divided into five chapters; however, not all chapters are appropriate for all readers. If you are installing Red Brick Warehouse for the first time, read: Chapter 1, Preparing for an Installation Chapter 2, Installing Red Brick Warehouse Chapter 5, Miscellaneous Administrative Tasks The appropriate appendix for your UNIX platform If you already have Red Brick Warehouse running at your site and want to install a new release, read Chapter 3, Installing a New Release, instead of Chapter 2. If you are installing an update or patch release, first refer to the instructions delivered with the release media, then read the section about upgrading warehouse databases on page 3-6 of this guide (if upgrading is necessary). If you want to install Red Brick client products (RISQL Entry Tool, RISQL Reporter, Red Brick ODBCLib), refer to Chapter 4, Installing Red Brick Client Products. Appendix A, Warehouse Directories and Files, illustrates the structure of the directories and files you have installed and configured, and briefly describes their contents. Appendix B, Recommended Locale Specifications, identifies the languages, territories, character sets, and collation sequences supported by the Red Brick products. Appendixes C through J describe platform-specific administration and configuration tasks. viii Installation and Configuration Guide

9 About This Document Related Documentation Related Documentation The standard documentation set for Red Brick Warehouse includes the following documents: Installation and Configuration Guide Warehouse Administrator s Guide Table Management Utility Reference Guide SQL Reference Guide SQL Self-Study Guide RISQL Entry Tool and RISQL Reporter User s Guide Messages and Codes Reference Guide Release Notes Installation and configuration information, as well as platform-specific material, about Red Brick Warehouse and related products. Customized for either UNIX-based or Windows NT systems. Description of warehouse architecture, supported schemas, and other concepts relevant to warehouse databases. Procedural information for designing and implementing a warehouse database, maintaining a database, and tuning a database for performance. Includes a description of the system tables and the configuration file (rbw.config). Customized for either UNIX-based or Windows NT systems. Description of the Table Management Utility, including all activities related to loading and maintaining data. Also includes information about data replication and the rb_cm copy management utility. Complete language reference for the Red Brick Systems SQL implementation and RISQL extensions for warehouse databases. Example-based review of SQL and introduction to the RISQL extensions, the macro facility, and Aroma, the sample database. Complete guide to the RISQL Entry Tool, a command-line tool used to enter SQL statements, and the RISQL Reporter, an enhanced version of the RISQL Entry Tool with report-formatting capabilities. Complete listing of all informational, warning, and error messages generated by warehouse products, including probable causes and recommended responses. Also includes event log messages that are written to the log files. Information pertinent to the current release that was unavailable when the documents were printed. Installation and Configuration Guide ix

10 About This Document Related Documentation In addition to the standard documentation set, the following documents are included for specific sites: Red Brick Vista User's Guide SQL-BackTrack for Red Brick Warehouse User's Guide Client Connector Pack Installation Guide ODBC Connectivity Guide Red Brick Data Mine User s Guide Red Brick Data Mine Builder User s Guide Description of the Red Brick Vista aggregate navigation and advice system, including procedures for rewriting queries and getting advice on the best set of aggregate tables and views to create. Includes detailed examples of queries whose performance can be dramatically increased by using aggregate navigation. Complete guide to SQL-BackTrack for Red Brick Warehouse, a command-line interface for backing up and recovering warehouse databases. Includes procedures for defining backup configuration files, performing online and checkpoint backups, and recovering the database to a consistent state. Procedures for installing and configuring the Red Brick ODBC Driver, the RISQL Entry Tool, and the RISQL Reporter on client systems. Included for those sites that purchase the Client Connector Pack. Information about ODBC conformance levels as well as instructions for compiling and linking an ODBC application using the Red Brick ODBClib SDK. Description of the data mining process, and procedural information for using the Red Brick Data Mine SQL-based interface to find hidden or unpredictable relationships among the data in a data set. Included for those sites that purchase the Red Brick Data Mine option. Description of the data mining process, and procedural information for performing data mining using Red Brick s GUI-based product in a Microsoft Windows environment. Additional references you might find helpful include: An introductory-level book on SQL An introductory-level book on relational databases Documentation for your hardware platform and operating system: IBM RISC System/6000: Getting Started: Managing RISC System/6000 (GC ) RISC System/6000 Hypertext Information Base Library (CD-ROM SC ) x Installation and Configuration Guide

11 About This Document Related Documentation HP 9000 Computer: System Administration Tasks Manual, HP 9000 Series 800 Computers Sequent Symmetry System: DYNIX/ptx System Administration Guide DYNIX/ptx System Configuration and Performance Guide ptx/tcp/ip Administration Guide NCR WorldMark Server: Administrator Guide: Command Line Interfaces General Administration (Volume 1) Administrator Guide: Command Line Interfaces System Configuration (Volume 3) Sun SPARC-Based Systems: System Configuration and Installation Guide Administering Security, Performance, and Accounting Open Issues and Late Breaking News for System Administrators The above three documents are published by SunSoft for Solaris 2.4, 2.5.1, and 2.6. Digital AlphaServer: System Administration manual Network Configuration manual Sharing Software on a Local Network manual Digital UNIX Release Notes Unisys U6000 Unisys UNIX System V Release 4.0 System Administrator s Guide Unisys UNIX System V Release 4.0 Release Notes Silicon Graphics Servers: IRIX Advanced Site and Server Administration Guide Online Documentation The English version of the Red Brick Warehouse documentation is also available in Adobe Acrobat format (PDF) on a separate CD-ROM. Installation and Configuration Guide xi

12 About This Document Conventions Conventions Throughout Red Brick Systems technical publications, the following notation and syntax conventions are used. Computer input and output, including commands, code, and examples, appear in Courier. Information that you enter or that is being emphasized in an example appears in Courier bold to help you distinguish it from other text. Filenames, system-level commands, variables, and document titles appear in Palatino italic or Courier italic, depending on the context. Names of database tables and columns are capitalized (Sales table, Dollars column). Names of system tables and columns are in all uppercase (RBW_INDEXES table, TNAME column). Syntax Notation This guide uses the following conventions to describe the syntax of operating-system commands: Command Element Example Convention Values and parameters table_name Items that you replace with an appropriate name, value, or expression are in italic type style. Optional items [ ] Optional items are enclosed by square brackets. Do not type the brackets. Choices ONE TWO Choices are separated by vertical lines; choose one if desired. Required choices {ONE TWO} Required choices are enclosed in braces; choose one. Do not type the braces. Default values ONE TWO Default values are underlined, except in graphics where they are in bold type style. Repeating items name,... Items that can be repeated are followed by a comma and an ellipsis. Separate the items with commas. Language elements ( ), ;. Parentheses, commas, semicolons, and periods are language elements. Use them exactly as shown. xii Installation and Configuration Guide

13 About This Document Customer Support Customer Support Please review the following information before contacting the Customer Support Center at Red Brick Systems. Support Solutions Warehouse The Support Solutions Warehouse is the Customer Support Center s external web site, an online resource that registered Red Brick customers can use to: Submit new cases. Read release notes. Find answers to frequently asked questions (FAQs). Search the Problems and Solutions database. To use the Support Solutions Warehouse, point your web browser to the following URL and enter your registered username and password: If you do not have a registered username and password, contact the Customer Support Center by telephone, fax, or . General and Technical Questions If you have general sales-related questions or technical questions about Red Brick products or services, contact Red Brick Systems as follows: Telephone General Questions Technical Questions FAX General Questions Technical Questions Internet General Questions Technical Questions World Wide Web (408) or 1 (800) (408) or 1 (800) (408) (408) info@redbrick.com support@redbrick.com Installation and Configuration Guide xiii

14 About This Document Customer Support Existing Cases If you want to inquire about the status of an existing case, please have the case number ready. The case number will always be given to you by the support engineer who logs the case or first contacts you. This number is used to keep track of all the activities performed during the resolution of each problem. New Cases If you want to log a new case, please have the following information ready: Red Brick Warehouse version Platform and operating-system version Error messages returned by Red Brick Warehouse or the operating system Concise description of the problem, including any commands or operations performed prior to the occurrence of the error message List of Red Brick Warehouse and/or operating-system configuration changes made prior to the occurrence of the error message If you think the problem concerns client-server connectivity, please have the following additional information ready: Name and version of the client tool in use Version of Red Brick ODBC Driver in use (if applicable) Name and version of client network and/or TCP/IP stack in use Error messages returned by the client application xiv Installation and Configuration Guide

15 About This Document Customer Support Troubleshooting Tips You can often reduce the time it takes to close your case by providing the smallest possible reproducible example of your problem. The more you can isolate the cause of the problem, the more quickly the support engineer can help you resolve it. For SQL query problems, try removing columns or functions, or restating WHERE, ORDER BY,orGROUP BY clauses until you can isolate the part of the statement causing the problem. For TMU load problems, verify the datatype mapping between the source file and the target table to ensure compatibility. Try loading a small test set of data to determine whether the problem concerns volume or data format. For connectivity problems, verify that the network is up and running by issuing the rbping command from the client to the host. If possible, try another client tool to see if the same problem arises. Documentation Questions and Comments If you have questions or comments about the Red Brick Warehouse documentation, please contact the Technical Publications Department at Red Brick Systems as follows: Telephone (USA only) Internet docs@redbrick.com Installation and Configuration Guide xv

16 About This Document Customer Support RB xvi Installation and Configuration Guide

17 1 Preparing for an Installation This chapter will help you gather information and set up your environment in preparation for installing Red Brick Warehouse or Red Brick Warehouse for Workgroups. After you have worked through this chapter, you will be ready to respond to the prompts from the installation script, and you will have configured some required operating-system parameters ahead of time. If you are installing Red Brick Warehouse for the first time, complete the preparation steps discussed here before beginning the procedure in Chapter 2, Installing Red Brick Warehouse. If Red Brick Warehouse is already installed on your system and you want to install a new release, review this chapter before following the instructions in Chapter 3, Installing a New Release. If you want to install only Red Brick Client products, follow the procedures in Chapter 4, Installing Red Brick Client Products. Note: Whether you are installing your first warehouse or a new release, read the release notes that accompany the software before beginning the preparation tasks. The procedures in this chapter apply to both Red Brick Warehouse and Red Brick Warehouse for Workgroups, unless otherwise stated. Installation and Configuration Guide 1-1

18 Preparing for an Installation Preview of Preparation Tasks Preview of Preparation Tasks Before installing Red Brick Warehouse or Red Brick Warehouse for Workgroups, you need to complete the following tasks: Determine the operating-system shell. Verify that your operating system version and available disk space meet Red Brick Warehouse requirements. Configure operating-system parameters. Determine the warehouse locale. Select a warehouse logical name. Select an IPC key (All operating systems except DYNIX/ptx) for the warehouse daemon. or Identify a shared memory map file (DYNIX/ptx only). Determine the TCP/IP port for the warehouse daemon. Create the redbrick account for warehouse administration. Create the redbrick directory for the warehouse software. Note: Some steps in this chapter require superuser (root) privileges and are typically performed by the operating-system administrator. If the operating-system administrator is not also the warehouse administrator, administration activities must be carefully coordinated to ensure the success of the warehouse installation. Platform-Specific Considerations The following operating systems include both System V and BSD UNIX commands: Sun SPARC-based systems (throughout this document, Solaris 2.4, 2.5.1, or 2.6 implies a Sun SPARC-based system; likewise, Sun SPARC-based system implies hardware running Solaris software.) NCR UNIX SVR4 MP-RAS Silicon Graphics IRIX Unisys UNIX System V All instructions and examples in this document are based on System V. To ensure you are using System V, verify that /bin precedes /usr/ucb in the path definition for the redbrick user account. 1-2 Installation and Configuration Guide

19 Preparing for an Installation Determining the System Shell Determining the System Shell Some steps in the installation procedure are shell-dependent. To determine the shell, enter: $ ps -p $$ The ps utility returns a line indicating which shell you are using. The line will look somewhat different depending upon your platform, but will end with one of the following: 1 ksh sh csh Korn shell Bourne shell C shell For example, the following result of a ps -p command on an HP-UX system shows that the Korn shell is being used: PID TTY TIME COMMAND ttys1 0:00 ksh The operating system command-line prompt is shell-specific, with the following default prompts: Korn and Bourne shells: $ C shell: % For all shells, the default superuser prompt is a pound symbol (#). The Korn shell prompt ($) is used throughout this guide, except for commands specific to the C shell, which are shown with the C-shell prompt (%). Installation and Configuration Guide 1-3

20 Preparing for an Installation Verifying Operating-System Version and Disk Space Verifying Operating-System Version and Disk Space To install and run Red Brick Warehouse, you must be running the appropriate version of your operating-system software, depending upon your platform. (Contact your Red Brick Systems representative for information about the most current supported software versions). The operating-system versions currently supported are: Platform Supported Operating-System Versions IBM RISC/System 6000 AIX Version 4.1 or 4.2 Digital AlphaServer Digital UNIX Version 4.0 HP 9000 Computer HP-UX Release 10.0 NCR WorldMark Server NCR UNIX SVR4 MP-RAS Version 2.03 or 3.0 Sequent Symmetry System DYNIX/ptx Version 4.x Sun SPARC-Based System Solaris Version 2.4, 2.5.1, or 2.6 Silicon Graphics Server IRIX Version 6.2 or 6.4 Unisys U6000 System Unisys UNIX System V Release 4.0 Level 1.3 (or later) You must also have the following system hardware and memory available: A CD-ROM drive. A minimum of 100 megabytes of free disk space on the filesystem where Red Brick Warehouse will be installed. A minimum of 32 megabytes of RAM, with at least 128 megabytes preferred for large-system configurations supporting 20 or more concurrent users. In addition to the disk space required to install Red Brick Warehouse itself, you need sufficient disk space to store and manage the databases in Red Brick Warehouse. For information about how to estimate the disk space required for your database, refer to the Warehouse Administrator s Guide. 1-4 Installation and Configuration Guide

21 Preparing for an Installation Verifying Operating-System Version and Disk Space Operating-System Version Perform the following steps to verify that you have the correct operating-system version for Red Brick Warehouse. To determine the operating-system version, at the system prompt, enter the following command: 1 Operating System AIX Digital UNIX HP-UX DYNIX/ptx Solaris Silicon Graphics IRIX NCR UNIX SVR4 MP-RAS Unisys UNIX System V Command $ uname -a $ cat /etc/.relid $ pkginfo -l osversion The system returns operating-system information similar to that shown in the following table. The information highlighted in bold type indicates the operating-system version. Installation and Configuration Guide 1-5

22 Preparing for an Installation Verifying Operating-System Version and Disk Space Operating System Operating-System Information AIX AIX spock A000 Digital UNIX OSF1 moe.redbrick.com V alpha HP-UX HP-UX larry B C 9000/ user license NCR UNIX RELEASE Version 01 OS SVR4 MP-RAS DYNIX/ptx Solaris shemp shemp 4.0 v4.03 i386 SunOS joey.redbrick.com 5.4 Generic_ sun4d sparc Silicon Graphics IRIX Unisys UNIX System V Note: Solaris 2.4, 2.5.1, and 2.6 are operating environments built on the SunOS 5.4, 5.5.1, and 5.6 operating systems, respectively; verify that the operating system is SunOS and that the version is 5.4 or IRIX64 curly IP19 PKGINST: osversion NAME: osversion CATEGORY: system VERSION: 1.3 TAKE 18.7 STATUS: completely installed 1-6 Installation and Configuration Guide

23 Preparing for an Installation Verifying Operating-System Version and Disk Space Disk Space Determine how much disk space is available on the filesystem where you want to install the warehouse. Be sure to use a filesystem with enough free space to provide the storage needed for Red Brick Warehouse, other optional Red Brick products, and the sample database. Use the operating-system df command to determine the available disk space on your filesystems: 1 Operating System AIX HP-UX DYNIX/ptx NCR UNIX SVR4 MP-RAS Unisys UNIX System V Solaris Digital UNIX Silicon Graphics IRIX Command Default Block Size $ df 1,024 bytes (1 kilobyte) $ df -k 512 bytes (1/2 kilobyte) The system responds with a list of the various filesystems and available disk space on each. Because the commands display the available space in 1-kilobyte blocks, look for a filesystem with at least 100,000 kilobytes (100 megabytes) for Red Brick Warehouse. If you need more information about how to identify the amount of disk space available on your system, refer to your operating-system documentation or man pages, or check with your system administrator. Installation and Configuration Guide 1-7

24 Preparing for an Installation Verifying Operating-System Version and Disk Space Considerations for NFS Filesystems Warehouse databases must be created and loaded on the same type of computer as the computer from which they will be accessed: For example, if you create and load the database using an AIX server, the database can be accessed only from an AIX server. The physical files holding the database can reside on any filesystem accessible via NFS, even a filesystem exported from a different hardware type, providing that compatible POSIX locking is available. Support for NFS, however, is limited to read-only access. Update and load operations must be performed on the system to which the warehouse disk is attached. As with all database products, optimum performance of Red Brick Warehouse depends on a high-performance disk storage subsystem. In general, NFS filesystems are unable to provide the same high level of I/O throughput as local disk drives. Therefore, performance is better when the database is stored on local disk drives. Red Brick Warehouse creates a zero-length file (.connection_name.lockfile) in the directory containing the rbw.config file and uses this file as the target of lock requests. Because the performance of such lock requests to NFS filesystems is substantially slower than those directed to local filesystems, the directory containing the rbw.config file should be located on a local filesystem. However, the Red Brick Warehouse program and support files can be located on an NFS filesystem with no significant performance degradation. 1-8 Installation and Configuration Guide

25 Preparing for an Installation Configuring Operating-System Parameters Configuring Operating-System Parameters Red Brick Warehouse is a high-performance server designed to support the needs of tens, hundreds, or thousands of users in a distributed client/server computing environment. In order to provide sufficient resources for this large number of client users, certain operating-system configuration parameters may require modification. 1 Refer to the appropriate appendix for information about configuring operating-system parameters for your platform: Operating System AIX Digital UNIX HP-UX Solaris Silicon Graphics IRIX NCR UNIX SVR4 MP-RAS DYNIX/ptx Unisys UNIX System V Appendix Appendix C Appendix D Appendix E Appendix F Appendix G Appendix H Appendix I Appendix J Installation and Configuration Guide 1-9

26 Preparing for an Installation Determining the Locale Determining the Locale During the installation process, you will be asked to specify a locale. A locale is the unique combination of a language and a location. The locale you specify will apply to all databases created for this installation. For more information about locale specifications, refer to the Warehouse Administrator s Guide. Locale Components A locale consists of four components: Language Territory Character set Collation sequence Language Territory Each component is described briefly in the following sections. The language component (in conjunction with the territory) controls which translation is used. In general, text strings are accepted and displayed in the user s chosen language. These strings include information and warning messages, object names, month and day names, and character data returned in query results. However, the fixed elements of a programming language, such as the keywords used in SQL commands, are not translated. The territory component controls country-dependent information such as currency symbols, numeric and monetary formatting rules, and date and time formats. For example, although English is used in both the United States and the United Kingdom, and Spanish is used in both Spain and Mexico, the use of these languages differs according to location. (Sometimes, a single territory applies to more than one country in a region.) Character Set The character set, or code page, component specifies the character encoding or character set used to format and display information Installation and Configuration Guide

27 Preparing for an Installation Determining the Locale Collation Sequence The sort component of the locale, or collation sequence, defines the rules used to compare character strings and arrange them in the correct order. There are two main types of character comparisons: binary and linguistic. Defining the Warehouse Locale 1 During the installation of the Red Brick Warehouse software, a locale specification is requested for the data warehouse. The locale supplied during installation is stored as the NLS_LOCALE LOCALE parameter in the rbw.config file. If no locale is supplied, the default value of this parameter is used: English_UnitedStates.US-ASCII@Binary This locale specification applies to the whole Red Brick Warehouse installation, regardless of the number of databases that will be created for that installation. (An installation is defined by the contents of the rbw.config file found in the directory referenced by the RB_CONFIG environment variable.) If you want to specify a locale that is different from the default locale specification, you must define each of its four components language, territory, character set, and collation sequence. Refer to Appendix B for a list of locale specifications supported by Red Brick Warehouse. Record your warehouse locale specification here: Locale specification: (English_UnitedStates.US-ASCII@Binary by default) Language: Territory: Character set: Collation sequence: Installation and Configuration Guide 1-11

28 Preparing for an Installation Selecting a Warehouse Logical Name Selecting a Warehouse Logical Name The default for the warehouse logical name is the literal name RB_HOST. This name corresponds to the name assigned to the memory mapped file (Sequent Symmetry System) or the IPC key (SHMEM) (all other platforms) in the rbw.config file. For a full description of the rbw.config file, refer to the Warehouse Administrator s Guide. For standard installations, the installation script provides a default value for the warehouse logical name (RB_HOST). If you are planning to run two versions (for example, Version 5.0 and Version 5.1) simultaneously or if you want to use a name that is different from the default value, record a different warehouse logical name here: Logical name of warehouse daemon: (RB_HOST by default) 1-12 Installation and Configuration Guide

29 Preparing for an Installation Selecting an IPC Key for the Warehouse Daemon Selecting an IPC Key for the Warehouse Daemon Note: If you are installing Red Brick Warehouse on a Sequent Symmetry System, this section does not apply to you. Refer to Identifying a Shared Memory Map File on page The Red Brick Warehouse server uses a shared memory segment for communication with client processes such as the RISQL Entry Tool. You must select an interprocess communication (IPC) key value for Red Brick Warehouse to use for its shared memory communication and supply this value during the installation process. 1 The Red Brick Warehouse daemon allocates IPC resources based on the IPC key value, which is supplied by the user for the RB_HOST SHMEM entry in the rbw.config file during the installation process. This value allocates additional IPC resources for each additional server that will be supported by the warehouse daemon, as specified by the MAX_SERVERS entry in the rbw.config file. The IPC key value has two requirements: The number must be different from any other IPC key value so that Red Brick Warehouse processes do not conflict with other processes. Note: When running two versions of Red Brick Warehouse simultaneously for new-release testing purposes, you must use unique IPC key values for each version. The number forms the base for a list of IPC entries in the shared memory environment. This list must allow at least as many entries as the maximum number of users who will have concurrent access to the warehouse. Therefore, select an IPC key that allows at least that many free IPC slots before the next reserved entry. For example, if MAX_SERVERS is set to 50, and 100 is specified as a base IPC key value: RBWAPI MAX_SERVERS 50 RBW_HOST1 SHMEM 100 then any additional IPC key values specified must be greater than 100 by at least 32 (50 in decimal is 32 in hexadecimal). For example, a new IPC key value of 120 might result in a resource conflict, while a value of 140 would provide sufficient range between the IPC keys to accommodate the specified MAX_SERVERS value: RBW_HOST2 SHMEM 140 Installation and Configuration Guide 1-13

30 Preparing for an Installation Selecting an IPC Key for the Warehouse Daemon You can examine the current shared memory settings and IPC configuration using the operating-system ipcs command. For most system environments, the default value of 0x100 (hexadecimal) is an appropriate selection. Record the selected IPC key here for use during installation; the installation procedure requires that you specify this value with a hexadecimal number: Base IPC Key (base 16 integer): Example The warehouse daemon logical name and IPC key value that you specify during the installation procedure are stored in the rbw.config file as follows: # The following is used for IPC key values. Note that for shared memory # and semaphores, the key values will range from the IPC key number to # IPC key + MAX_SERVERS. # RB_HOST SHMEM 100 # Daemon IPC key logical name For more information about the rbw.config file, refer to the Warehouse Administrator s Guide Installation and Configuration Guide

31 Preparing for an Installation Identifying a Shared Memory Map File Identifying a Shared Memory Map File Note: This section applies only to the installation of Red Brick Warehouse on a Sequent Symmetry System. If you are installing Red Brick Warehouse on another UNIX platform, refer to Selecting an IPC Key for the Warehouse Daemon on page The Red Brick Warehouse Server uses a shared memory map file for communication with client processes such as the RISQL Entry Tool. By default, this file is created in the same directory as the rbw.config file and is named.rb_host.mapfile. (RB_HOST is the connection name.) 1 The interprocess communication (IPC) key for each process is generated automatically by the daemon based on the file used for the shared memory map. If you do not want to use the default shared memory map file, you can specify another file during the installation procedure or modify the rbw.config file after installation. In general, there is no reason to change the default value unless you are specifically advised to do so by Red Brick Systems. Record the filename in the space provided: Shared memory map filename: Example: Shared Memory Map Filename and Warehouse Daemon Logical Name in rbw.config File The shared memory map filename and warehouse daemon logical name that you specify during the installation procedure are stored in the rbw.config file: # The following is used for IPC key values. Note that for shared memory # and semaphores, the key values will range from the IPC key number to # IPC key + MAX_SERVERS. # RB_HOST SHMEM 100 RB_HOST MAPFILE /redbrick_dir/.rb_host.mapfile # Daemon Full pathname of the warehouse daemon memory map file # logical name Installation and Configuration Guide 1-15

32 Preparing for an Installation Determining the TCP/IP Port for the Red Brick Warehouse Daemon Determining the TCP/IP Port for the Red Brick Warehouse Daemon The Red Brick Warehouse installation process asks you to supply a TCP/IP port. Determine this port number as follows: 1. Ensure that the operating-system command netstat is in your path (typically /usr/etc/netstat). 2. Determine whether the default Red Brick Warehouse daemon TCP/IP port is in use: $ netstat -an grep 5050 The system responds with a list of information about the default port, if any. If the system returns no information, the default port (5050) is not currently in use and can be used for this Red Brick Warehouse daemon configuration. If information is returned, the default port (5050) is in use and you must select another port. For information about using the netstat command to display a list of available ports, refer to your operating-system documentation. Note: The netstat command lists only those ports currently in use; it does not list ports used by processes that are not currently active. If you are uncertain about obtaining a unique number, ask your system administrator for advice. Use the default port, if it is not already in use. Otherwise, use a number between 2048 and that is not being used. Because numbers between 1024 and 2048 are commonly used for standard system ports, Red Brick Warehouse installation and configuration utilities do not accept values below Use a number above 4098 to minimize the chance of conflict. If you plan to run two versions of Red Brick Warehouse simultaneously, you must specify a different port number for each one. 3. Record the Red Brick Warehouse daemon port here: Red Brick Warehouse Daemon port: 1-16 Installation and Configuration Guide

33 Preparing for an Installation Creating the redbrick Account Creating the redbrick Account Before you begin installing Red Brick Warehouse, you must create a user account to be used for warehouse installation and all subsequent database administration activity. This account is also used as the effective execution user ID for warehouse server processes (rbwsvr), and all database files and directories are owned exclusively by this user. The default name for this account is redbrick, although you can choose any name. Throughout the Red Brick Warehouse documentation, this user account is referred to as redbrick, and this user ID is used for all warehouse administration activities at the operating system level. 1 As a superuser, create the redbrick account using the appropriate system management tool, depending upon your platform. The following table lists the system management tools for each platform; for more information about each tool, refer to your operating-system documentation or man pages. Platform AIX Digital UNIX HP-UX NCR UNIX SVR4 MP-RAS Unisys UNIX System V DYNIX/ptx Solaris Silicon Graphics IRIX System Management Tool AIX System Management Interface Tool (SMIT) Digital UNIX adduser script System Administration Manager tool (SAM) NCR UNIX SVR4 MP-RAS sysadm tool Unisys UNIX System V sysadm tool ptx/admin tool Solaris Administration Tool Graphical system manager tool You do not need to create additional operating-system user accounts if all users of the data warehouse will connect via client tools. However, if the warehouse will be accessed by local users via the RISQL Entry Tool or RISQL Reporter, you need to create accounts that give those users login access to the system. Also, you must provide database access for all Red Brick Warehouse users (whether they connect via client tools or the RISQL tools) by using the SQL GRANT authorization command. For details, refer to the Warehouse Administrator s Guide. Note: Users connecting to a Red Brick Warehouse database via RISQL Entry Tool or RISQL Reporter running on a remote system do not need operating-system user accounts. Installation and Configuration Guide 1-17

34 Preparing for an Installation Creating the redbrick Directory Access to the redbrick Account To ensure that correct access is provided for files created by the redbrick user, make sure the umask for this account is set to 077. Look for the following line at the end of both the.cshrc and.profile files for the redbrick user: umask 077 If this line is not present in both files, enter it as shown above. This umask setting provides the following file access for the redbrick user: redbrick: group: other: rwx (read, write, execute) --- (none) --- (none) Creating the redbrick Directory The redbrick user must have read, write, and execute access to the directory where the warehouse software will be installed. Throughout this document, this directory is referred to as the redbrick directory (redbrick_dir in examples), although you can name it whatever you choose. Create this directory in the filesystem where you have decided to install the warehouse software. In most cases, this directory is the home directory for the redbrick user created in the previous section. Providing License Keys Red Brick Warehouse requires that you provide a valid license key before you start the warehouse daemon. In addition, if you have purchased optional Red Brick products (for example, the Enterprise Control and Coordination option), you must enable these products with license keys before using them. The menu-driven installation script provides an interface for entering license keys directly into the Red Brick Warehouse configuration file. This procedure is described in Chapter 2 of this guide. A license key for a licensed option is provided on a one-page document that is delivered with Red Brick Warehouse when an optional product is purchased Installation and Configuration Guide

35 Preparing for an Installation Choosing an Installation Procedure Choosing an Installation Procedure If you are installing Red Brick Warehouse for the first time, you are ready to begin the installation procedure described in Chapter 2, Installing Red Brick Warehouse. If you already have Red Brick Warehouse and wish to install and work with a new version of the software before converting your existing databases to that new version, refer to Chapter 3, Installing a New Release. 1 Installation and Configuration Guide 1-19

36 Preparing for an Installation Checklist of Preparation Steps Checklist of Preparation Steps Action Page 1. Determine the operating-system shell Verify that you are running the correct version of your operating system. 3. Verify that you have sufficient disk space to install and run the software, and configure NFS filesystems, if applicable. 4. Set up your environment by configuring the operating-system parameters discussed in the appropriate appendix for your platform Note: Refer to the Warehouse Administrator s Guide for guidelines on estimating disk space Determine a locale for your installation Note: Refer to the Warehouse Administrator s Guide for guidelines on defining a locale. 6. Select a warehouse logical name (default is RB_HOST) Select an IPC key for the warehouse daemon. (All operating systems except DYNIX/ptx) or Identify a shared memory map file for the warehouse daemon. (DYNIX/ptx only) 8. Determine the TCP/IP port for the warehouse daemon. 9. As a superuser, create the redbrick account and verify file access for the redbrick user (umask 077 should appear in the.cshrc and.profile files). 10. Create the redbrick directory in the filesystem where you will install the software. 11. Have your license keys ready; one for each product or option you have purchased is provided in a separate document delivered with the CD-ROM. 12. Go to Chapter 2 or 3 for installation instructions: First-time warehouse Chapter 2 Existing warehouse Chapters 2 and Installation and Configuration Guide

37 2 Installing Red Brick Warehouse This chapter explains how to install Red Brick Warehouse or Red Brick Warehouse for Workgroups. The procedures in this chapter apply to both products, unless otherwise stated. The installation procedure installs the software, as well as a sample database named Aroma, a utility directory named util, and all optional Red Brick products (for example, Enterprise Control and Coordination). As part of the installation procedure, you also have to enable the license keys for Red Brick Warehouse and any optional products you have purchased. The installation procedure uses a script named INSTALL.ISO (install.iso for Unisys UNIX System V), which displays a menu of installation options. You can use the script to do any of the following: Install a full-feature or maintenance release of Red Brick Warehouse Install a partial update, or patch, release. Enable optional Red Brick products with a license key. For more information about installing an update release, refer to the release notes distributed with your update release CD-ROM and Chapter 3, Installing a New Release. Red Brick Warehouse installation is typically done by the system or database administrator. However, you can start the installation procedure and the administration and log daemon processes (rbwadmd, and rbwlogd) as the redbrick user. Installation and Configuration Guide 2-1

38 Installing Red Brick Warehouse Before You Begin Before You Begin Read the release notes delivered with the software and complete the pre-installation tasks described in Chapter 1, Preparing for an Installation. The release notes discuss important information that was unavailable when this document was printed. The procedures described in the following sections describe the basic installation process for Red Brick Warehouse. If you plan to run two concurrent releases of Red Brick Warehouse or if you are replacing the current release with a new release, refer to Chapter 3 for additional information. The following conditions will prevent you from successfully installing the software: Incorrect user privileges Insufficient disk space Media failure (damaged CD-ROM) If you see an error message during installation, make sure you have read/write privileges on the redbrick directory and that you have sufficient disk space for the warehouse software. For more information about system requirements, refer to Verifying Operating-System Version and Disk Space on page 1-4. If you are still unable to install the warehouse and the sample database, or if the CD-ROM is damaged, contact Customer Support at Red Brick Systems as described on page xiii. 2-2 Installation and Configuration Guide