HP Database Manager (HPDM) User Guide

Transcription

1 HP Database Manager (HPDM) User Guide HP Part Number: Published: July 2010 Edition: HP Neoview Release 2.5

2 Copyright 2010 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, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java is a U.S. trademark of Sun Microsystems, Inc. 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. The OSF documentation and the OSF 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.OSF 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 Table of Contents About This Guide...13 Publishing History...13 New and Changed Information...13 Intended Audience...14 Related Documentation...15 Neoview Customer Library...15 Resources on the Web...17 Send Feedback to HP About HPDM...19 What Is HPDM?...19 What Are the HPDM Features?...19 Which Servers Are Compatible With the HPDM Client? Install and Start HPDM...23 Install the HP Database Manager...23 Uninstall the HP Database Manager...23 Start the HP Database Manager...23 Exit the HP Database Manager Connect and Disconnect...25 Connect to a System...25 Use the Connect / Edit System Dialog Box...26 Password Considerations...27 Disconnect From a System...27 Log On and Off...28 Use the Systems Tool...28 Add a System...29 Use the Add System Dialog Box...30 Edit a System...32 Add a System Like...33 Remove a System...33 Test a System...33 Set the Connection Timeout Navigate HPDM...35 See the Parts of the HPDM Interface...35 Select an Area...35 Control the Display of an Area...37 Use the Navigation Tree Pane...37 Use the Right Pane...39 Use the My Favorites Pane...40 Create a Favorite...40 Use a Favorite...40 View a List of Favorites...40 Create a Folder to Store Favorites...41 Add a Favorite to a Folder...41 Share Your Favorites With Others...41 Table of Contents 3

4 Remove a Favorite...41 Remove a Favorites Folder...41 See the HPDM Banner...41 Use Menu Bar Commands...42 Use the File Menu Options...42 Use the Edit Menu Options...42 Use the Tools Menu Options...43 Use the Windows Menu Options...43 Use the Help Menu Options...43 Use the HPDM Toolbar...44 Work With Windows, Tabs, and Panes...45 Manage Multiple Open Windows...45 Clone Tabs...46 Expand and Collapse Panes Perform Basic HPDM Operations...47 Get Version and Build Information...47 Resolve Errors and Error Messages...47 Sort and Move Data Columns...47 Work With Data Grids...48 About Data Grids...48 Get Row Details for a Data Grid...49 Copy Data-Grid Information...50 Customize the Data Grid...52 Search the Data Grid...52 Export Data...53 Export Data to the Clipboard...53 Export Data to a File...53 Save Data in CSV Format...53 Save Data in HTML Format...53 Save Data to a Spreadsheet...53 Export Data to a Browser...53 Communicate System Messages to Users...53 Use the System Message Tab...54 Create a System Message...54 Clone the System Message Tab...55 Save and Import System Definitions...55 View Event Messages...56 View Dial Out and Database Events...56 See the Trace Event Message Format...56 Resource Statistics Event Message Format...57 Session Statistics: Connection Information...58 Session Statistics: Session Summary Information...58 Statement Statistics: SQL Statement...59 Statement Statistics: SQLExecute...59 Statement Statistics: SQLExecDirect...60 Statement Statistics: SQLPrepare...61 Statement Statistics: SQLFetch Display Database Objects...63 Display Schemas and Their Objects...63 Attributes Tab...64 Tables Tab Table of Contents

5 Materialized Views Tab...64 Materialized View Groups Tab...64 Views Tab...65 Procedures Tab...65 Synonyms Tab...65 DDL Tab...65 Privileges Tab...66 Schema Size...66 Display Tables and Their Properties...66 Columns Tab...67 Primary Key Tab...68 Hash Key Tab...68 Unique Constraints Tab...68 Foreign Keys Tab...69 Attributes Tab...69 Partitions Tab...69 Usage Tab...69 DDL Tab...70 Statistics Tab...70 Privileges Tab...70 Tables Summary...71 Display Table Indexes and Their Properties...71 Columns Tab...72 Attributes Tab...72 DDL Tab...73 Partitions Tab...73 Table Indexes Summary...73 Display Views and Their Properties...74 Columns Tab...74 Usage Tab...75 DDL Tab...75 Privileges Tab...75 Display Materialized Views and Their Properties...76 Attributes Tab...77 Partitions Tab...78 Usage Tab...79 DDL Tab...79 Privileges Tab...79 Materialized Views Summary...80 Display Materialized View Indexes and Their Properties...80 Columns Tab...81 Attributes Tab...81 DDL Tab...82 Partitions Tab...82 Materialized View Indexes Summary...82 Display Materialized View Groups and Their Properties...83 Attributes Tab...84 Members Tab...84 DDL Tab...84 Display Procedures and Their Properties...84 Attributes Tab...85 Parameters Tab...86 Usage Tab...86 Privileges Tab...86 Display Synonyms and Their Properties...87 Table of Contents 5

6 Attributes Tab...88 Usage Tab...89 DDL Tab...89 Display Triggers and Their Properties...89 Attributes Tab...90 Usage Tab...91 DDL Tab...91 Display Schema DDL and Their Properties...91 DDL Tab...92 Show DDL...92 Display Table Statistics and Their Properties...93 Display Table Column Statistics...93 Viewing Sampled Statistics Manage Roles...95 About Roles...95 Display All Roles...95 Display the Users Who Belong to a Role...96 Display All the Roles for a User...96 Display the SQL Privileges for a Role...96 Add a Role...97 Delete a Role...98 Grant a Role to a User...98 Use the Grant Role Dialog Box...99 Revoke a Role From a User...99 Change the Password or Expiration for a Role Use the Change Role Password Dialog Box Manage Users and Passwords About Users Database Users Display All Database Users Add a Database User Use the Add Database User Dialog Box Use the Select User Role Dialog Box Add Multiple Database Users Use the Add Multiple Database Users Dialog Box Copy a Database User Control the Display of the Add Database User Dialog Box Change Role or Password Information for a Database User Use the Edit User Dialog Box Delete One or More Database Users Change Your Own Default Role Platform Users Display All Platform Users Add a Platform User Copy a Platform User Use the Add Platform User (or Edit User) Dialog Box Edit a Platform User Delete One or More Platform Users Passwords for Users Change Your Own Password at Logon Change Your Own Password After Logon Table of Contents

7 Use the Change Password Dialog Box Change a Password or Password Expiration Settings by Editing a User Manage Security Policies About Security Policies Display Security Policies Change a Security Policy Use the Certificate & Connection Tab for Security Policies Use the Password Tab for Security Policies Use the Logging Tab for Security Policies Use the Power Role Management Tab for Security Policies Manage Certificates About Certificates Specify a Certificate File at Connect Time Generate a Self-Signed Certificate Use the Self-Signed Certificate Tab Obtain and Install a CA Certificate and Private Key Generate a Certificate Signing Request (CSR) Use the Generate CSR Tab Install Root and Intermediate Certificates on the Neoview Platform Use the Deploy CA Signed Certificate Tab About the Auto Download Certificate Option Manage Directory Servers About Directory Servers Display the Configured Directory Servers Add a Directory Server Use the Add Directory Server Dialog Box Understand Configuration Parameters Considerations for Adding Directory Servers Example: LDAP Server Example: Active Directory Server Edit a Directory Server Use the Edit Directory Server Dialog Box Copy a Configured Directory Server Delete a Directory Server Manage Data Sources Display Data Sources Create a Data Source Use the General Properties Tab Understand Processing-Node Numbering Add or Modify Resource Management Policy Use the DEFINEs and SETs Tab Use the Control Query Defaults Tab Use the Controlled Tables Tab If-Locked Option of Controlled Tables Tab MDAM Option of Controlled Tables Tab Priority Option of Controlled Tables Tab Similarity Check Option of Controlled Tables Tab Table Lock Option of Controlled Tables Tab Table of Contents 7

8 Timeout Option of Controlled Tables Tab Copy a Data Source Start a Data Source Stop a Data Source Update a Data Source Delete a Data Source Manage Connectivity Display NDCS Servers Learn About the Association Servers Stop an NDCS Server Display NDCS Services Start an NDCS Service Stop an NDCS Service Start and Stop Server Traces Learn About Server Traces Manage NDCS Privileges Display NDCS Privileges Grant NDCS Privileges Revoke NDCS Privileges Manage Procedures Display Procedures Upload a JAR File Download a JAR File Rename a JAR File Delete a JAR File Create a Procedure Use the Create Procedure Dialog Box Use a Method in a Procedure Drop a Procedure Use the System Monitor Display the System Monitor See the Parts of the System Monitor Understand the Performance Metrics Use Tooltips to Show the Value of a Performance Metric About the Timeline Tab About the Hybrid Tab Understand the System Status Icons Get Details About System Status Icons Configure System Monitor Options Use the System Monitor With Segment Aggregation Change a Color Option Respond to Alerts Display the Alerts Tab See the Parts of the Alerts Tab Understand Alerts Understand Privileges for Viewing and Updating Alerts Table of Contents

9 Get Information About Alerts Understand Row Detail Information for Alerts Use the Alerts Options Dialog Box Control the Refresh of Alerts Use the Update Alert Dialog Box Update an Alert Update Multiple Alerts Make Notes About an Alert About the Console Tab Find Offending Processes and Queries About System Offender Display the System Offender Tab See the Parts of the System Offender Understand System Offender Privileges Find Offending Processes and Queries Get Process Detail Information Get Pstate Information Get Children Process Information Use the Children Processes Dialog Box Understand Row Details for System Offender Get Query Workload Information Use the Workload Detail Dialog Box Query Information Understand the Warning Information Compiler Statistics Runtime Statistics Cancel a Query From System Offender Alter System Offender Parameters Use the Alter Offender Parameters Dialog Box Control the Refresh of System Offender Use the System Offender History Use the SQL Whiteboard About the SQL Whiteboard Display the SQL Whiteboard Learn About the SQL Whiteboard Panes Learn About the Statement List Pane Learn About the Statement Pane Understand Parameter Prompts Understand Page Mode Cut, Copy, Paste, Undo, and Redo Execute Highlighted Text Cancel a Query From the SQL Whiteboard Learn About the Statement Details Pane Reuse a Connection Load and Save SQL Statements to a File Highlight SQL Syntax Manage the Layout of Panes Use Metric Miner About Metric Miner Compare Metric Miner, SQL Whiteboard, and Neoview Reports Table of Contents 9

10 Launch Metric Miner See the Parts of Metric Miner Use the Metric Miner Toolbar Create Report Folders Create a Report Folder Delete a Report Folder Refresh the Report Explorer Run Statements Run a SQL Statement Using Metric Miner Use the SQL Designer Add Parameters to Statements Cancel a Query From Metric Miner Resolve Out-of-Memory Errors Export Metric Miner Data Control the Refresh of Metric Miner Information Use the Data Grid Features of the Report Results Pane See a History of Your SQL Statements Create and Manage Reports Create a Report Use the Report Configuration Dialog Box Display and Run a Saved Report Modify a Saved Report Close a Report Delete a Report Rename a Report or Report Folder Copy a Report Share a Report With Another User Use Preconfigured Reports Included With Metric Miner Import Neoview Reports Link and Drill Down Link Reports in Metric Miner Use the Select Report Dialog Box Use the Link Reports Dialog Box Drill Down Through Linked Reports in Metric Miner Launch the Neoview Command Interface (NCI) Learn About NCI Locate the NCI Program Launch NCI Set Auto Logon Options Manage Disk Space About Space Management Display the Space Management Area See the Parts of Space Management Understand Space Usage Statistics About the Monitoring Tab View the Over Threshold Summary View the System Overall View the System Detail View SQL Objects View the SQL Objects Detail View Partition Distribution Across Disks Table of Contents

11 View Table Growth By Table Tab Top Fastest Growing Tables Tab Understand Historical Space Data About the Configuration Tab About the General Tab Inventory Control Space Reference Settings Inventory Process Detail Status About the Advanced Tab Inventory Options Update Space Reference Tables Snapshot Periods Table Tab Classification Rule Table Tab System Registry Table Tab About Space Management Tracing Options Glossary Index Table of Contents 11

12 12

13 About This Guide This guide describes how to use the HP Database Manager (HPDM) to monitor and manage a Neoview Data Warehousing Platform for Business Intelligence. Publishing History (page 13) New and Changed Information (page 13) Intended Audience (page 14) Related Documentation (page 15) Resources on the Web (page 17) Send Feedback to HP (page 17) Publishing History This guide supports HP Neoview Release 2.5 and all subsequent Release 2.5 product versions until otherwise indicated by its replacement publication. The publication date and part number indicate this document s current edition: Part Number Product Version HP Neoview Release 2.5 HP Neoview Release 2.4 Service Pack 2 HP Neoview Release 2.4 Service Pack 1 HP Neoview Release 2.4 Publication Date July 2010 March 2010 October 2009 April 2009 Online Help Build Date: July 12, 2010 New and Changed Information The README for the current release or service pack describes the new features for this update of HPDM. You can find the README with the rest of the Neoview documentation. See Resources on the Web (page 17). These are the principal changes for this edition of the HPDM documentation: Added these new chapters and all the topics within them: About HPDM (page 19) Manage Roles (page 95) Manage Users and Passwords (page 103) Manage Security Policies (page 117) Manage Certificates (page 125) Manage Directory Servers (page 131) Manage Data Sources (page 141) Manage Connectivity (page 155) Manage NDCS Privileges (page 161) Manage Procedures (page 163) Use Metric Miner (page 219) Added these new topics in existing chapters: Set the Connection Timeout (page 34) Use the File Menu Options (page 42) Use the Edit Menu Options (page 42) Use the Tools Menu Options (page 43) Publishing History 13

14 Use the Windows Menu Options (page 43) Use the Help Menu Options (page 43) Use the HPDM Toolbar (page 44) Updated the illustration in Get Version and Build Information (page 47). Resolve Errors and Error Messages (page 47) Understand Page Mode (page 214) Made these miscellaneous changes: Added role and default-schema information to Use the Connect / Edit System Dialog Box (page 26). Added user role information to Use the Systems Tool (page 28). Added role and default-schema information to Use the Add System Dialog Box (page 30). Revised Use the Navigation Tree Pane (page 37) to include information about the My Systems folder. Removed references to Neoview Reports in Understand Parameter Prompts (page 214). Updated these topics: What Are the HPDM Features? (page 19) Select an Area (page 35) Use the Workload Detail Dialog Box (page 201) Added these new glossary terms: Ad-hoc Report association server database user LDAP locally authenticated database user Metric Miner MXAS2 MXOAS My Systems NDCS (Neoview Database Connectivity Service) NDCS Service operator privilege page mode platform user power role power user Procedure Code File Tool remotely authenticated database user report role NDCS server Deleted these glossary terms: My Active Systems My Other Systems Intended Audience This guide is intended for those who perform standard database administration tasks. It provides basic concepts and task information to get you started quickly and easily. 14

15 Related Documentation This guide is part of the HP Neoview library, which includes: Neoview Customer Library (page 15) Neoview Customer Library The manuals in the Neoview customer library are listed here for your convenience. Customer library manuals are available on the customer documentation Web site. Resources on the Web (page 17). Administration Neoview User Management and Security Administration Guide Neoview Character Sets Administrator's Guide Neoview Database Administrator s Guide Neoview Guide to Stored Procedures in Java Neoview Query Guide Neoview Transporter User Guide Information about security features on the Neoview platform, including user and role management for database and platform users, support for integration with Lightweight Directory Access Protocol (LDAP) directory servers, password encryption, and database security. Information for database administrators and end users of the Neoview Character Sets product, including rules for defining and managing character data using SQL language elements, capabilities and limitations of Neoview client applications, troubleshooting character set-related problems, and enabling Pass-Through mode in the ISO88591 configuration. Introduction to the Neoview database, database users and IDs, database management, and management tools. Information about how to use stored procedures that are written in Java within a Neoview database. Information about reviewing query execution plans and investigating query performance of Neoview databases. Information about processes and commands for loading data into your Neoview platform or extracting data from it. README files for installing Administration client products README for the HP Neoview Windows Client Package README for the HP Neoview Transporter Java Client Management HP Database Manager (HPDM) Online Help HP Database Manager (HPDM) User Guide Neoview Command Interface (NCI) Guide Neoview Performance Analysis Tools Online Help Neoview Performance Analysis Tools User Guide Neoview Repository User Guide Help topics that describe how to use the HP Database Manager client to monitor and manage a Neoview data warehousing platform. Information for database administrators about how to monitor and manage a Neoview data warehousing platform using the HP Database Manager. Information about using the HP Neoview Command Interface to run SQL statements interactively or from script files. Context-sensitive help topics that describe how to use the Neoview Performance Analysis Tools to analyze and troubleshoot query-related issues on the Neoview data warehousing platform. Information about how to use the Neoview Performance Analysis Tools to analyze and troubleshoot query-related issues on the Neoview data warehousing platform. Information about using the Repository, including descriptions of Repository views and guidelines for writing Neoview SQL queries against the views. Related Documentation 15

16 Neoview Workload Management Services Guide README files for installing Management client products Information about using Neoview Workload Management Services (WMS) to manage workload and resources on a Neoview data warehousing platform. README for the HP Neoview Windows Client Package README for the HP Database Manager (HPDM) README for the HP Neoview Command Interface (NCI) README for the HP Neoview Performance Analysis Tools Connectivity Neoview JDBC Type 4 Driver API Reference Neoview JDBC Type 4 Driver Programmer s Reference Neoview ODBC Drivers Manual Neoview ADO.NET Provider Manual ODBC Client Administrator Online Help README files for installing Connectivity client products Reference information about the HP Neoview JDBC Type 4 Driver API. Information about using the HP Neoview JDBC Type 4 driver, which provides Java applications on client workstations access to a Neoview database. Information about using HP Neoview ODBC drivers on a client workstation to access a Neoview database. Information about using HP Neoview ADO.NET to access data and services stored on the Neoview database. Context-sensitive help topics that describe how to use the ODBC Data Source Administrator. README for the HP Neoview Windows Client Package README for the HP Neoview JDBC Type 4 Driver README for the HP Neoview ODBC Driver for Windows README for the HP Neoview ODBC Drivers for UNIX README for the HP Neoview ADO.NET Provider Reference Mapping Tables for Neoview Character Sets Neoview SQL Reference Manual Neoview Client and Platform Compatibility Reference Neoview Messages Manual README for HP Neoview Release 2.5 A hyperlinked collection of East Asian characters supported by Neoview character set functionality. Reference information about the syntax of SQL statements, functions, and other SQL language elements supported by the Neoview database software. Information about compatibility of client products and the version of the Neoview release installed on the Neoview platform. Cause, effect, and recovery information for error messages. Information about new features for the current release, including where to download software and obtain documentation. 16

17 Resources on the Web Neoview Customer Documentation HP Software Depot Send Feedback to HP HP encourages your comments concerning this document or this product. We are committed to providing products and documentation that meet your needs. Send any errors found or suggestions for improvement to Include the document title and part number shown below: Document Title: HP Database Manager (HPDM) User Guide Part Number: Resources on the Web 17

18 18

19 1 About HPDM What Is HPDM? The HP Database Manager (HPDM) is an integrated graphical client that allows you to connect to and manage multiple HP Neoview platforms. HPDM provides database-object browsing and monitoring capabilities that are superior to the Neoview DB Admin product. NOTE: While you can use HPDM to browse and monitor database objects, you cannot use HPDM to create such objects. To create objects such as tables, indexes, and views, you must use the Neoview Command Interface (NCI). You can open an NCI window from within HPDM. See Launch NCI (page 239). HPDM requires the HP ODBC 2.0 client driver for Windows to connect to an HP Neoview platform. Download the HP ODBC 2.0 client driver from the HP Software Depot download site and install it prior to running the HP Database Manager. See Resources on the Web (page 17). What Are the HPDM Features? (page 19) What Are the HPDM Features? HPDM provides these features: Platform Monitoring Provides performance monitoring capabilities Provides the ability to monitor alerts and alarms. Enables the monitoring of offending workloads. Database-Object Browsing Provides database-object browsing capabilities Displays partition information for individual Neoview SQL objects Displays a partition summary for groups of objects (for example, all tables in a schema) Displays schema size information Displays sequence numbers in table columns Provides a DDL tool to generate and save the DDL script for a group of Neoview SQL objects Displays table profile and statistics information Generates and displays system status messages Space Management Allows you to monitor and display SQL space-related data Displays six panes of detailed SQL-space usage statistics Presents SQL space by user, by schema, by table, and by partition Helps you identify and react to fast-growing tables by looking at historical trends SQL Whiteboard Executes DDL/DML statements Persists queries across sessions for reuse Exports query results to a spreadsheet Allows a portion of an SQL statement to be highlighted and executed (syntax highlighting) Cancels an executing query Opens/saves query text to a file What Is HPDM? 19

20 HPDM Framework Provides connection management for widgets Supports persistence for widget and application data Includes menu management Implements area management (hide, show, and deploy) Exports grid contents to a spreadsheet Manages options for an HPDM application as a whole and for individual areas and widgets Launches the Neoview Command Interface (NCI) Supports character sets for ISO, SJIS, or Unicode based on a single-client locale (only one character set can be configured for each install). Enhanced user interface Area buttons include full-color icons The navigation tree pane is simplified with all system definitions residing in the My Systems folder New icons for nodes in the tree pane show the connected state of the system A toolbar provides fast access to commonly used functions and tools, such as NCI, the SQL Whiteboard, and Metric Miner The HPDM banner provides more information about connection, system, role, and user information Data-source and connectivity management features allow users who have operator privileges to: Create, update, and delete data sources Start and stop data sources Stop sessions Start and stop NDCS services Grant operator privileges (to allow other users to manage data sources) Display user privileges User- and role-management features Display roles and the users who belong to them Add and delete roles Grant a role to a user or revoke a role from a user Display summary information about all database and platform users Add, edit, copy, and delete database users Add, edit, copy, and delete platform users Change user passwords Metric Miner reporting tool Execute a SQL statement or query and view the results within HPDM Save the statement or query as a report that includes descriptive information, statement parameters, and version information Link reports so that the value of a row in one report can be passed to another report System Offender Helps you find processes and queries that use excessive CPU resources or memory Provides workload detail information for individual queries, including connection rule, compilation rule, and execution rule information Provides process detail, PSTATE, and children process information 20 About HPDM

21 Support for stored procedures in Java (SPJs) Display a list of jar files uploaded by users in your current role Display a list of classes in a jar file Display a list of methods in a class file Download one or more jar files from the Neoview platform to the workstation Upload jar files from a workstation to the Neoview platform Rename or remove an uploaded jar file Create an SPJ by using a jar file uploaded by you or another user in your current role Delete an SPJ created by you or another user in your current role Deploy jar files either to a public folder accessible by all users for a given role or to a private folder accessible only by the given user Security features Manage certificates, including the ability to generate self-signed certificates or use certificates signed by a certificate authority Add and edit directory servers in LDAP installations Manage security policies, which include policies for certificates, passwords (user and role), and the logging of user activities Which Servers Are Compatible With the HPDM Client? The Release 2.5 HPDM client can connect to platforms running Neoview Release 2.4 and later. However, not all features available in the current release are available in down-rev releases. If a feature is not available, HPDM either hides the feature or returns an error message. For more information about client/server compatibility, see the Neoview Client and Platform Compatibility Reference available with the Neoview customer documentation. Get Version and Build Information (page 47) Resources on the Web (page 17) Which Servers Are Compatible With the HPDM Client? 21

22 22

23 2 Install and Start HPDM Install the HP Database Manager The HP Database Manager is installed with a Windows installer. You can install the client by itself or as part of a bundle of Neoview clients provided by the Neoview Windows Client Package. Information about the installers can be found on the HP Software Depot web site. Instructions for installing the software are contained in the README for the HP Database Manager (HPDM). See Resources on the Web (page 17). HPDM has these installation requirements: Requirement Computer Display resolution Memory Disk space Operating system ODBC Additional HP Neoview release Description Windows compatible PC workstation 1024 x 768 pixels Recommended minimum 512 MB Minimum 10 MB for installation and 64 MB free space Microsoft Windows XP/Microsoft Windows Vista 32/64 bit ODBC driver for Neoview Release 2.5 Microsoft.NET Framework 3.5 or later Release 2.5 Uninstall the HP Database Manager After HP Database Manager is installed, you can uninstall it by using the Uninstall feature in the Start > All Programs > HP Database Manager menu or use the Control Panel, Add and Remove Programs feature. Note these considerations for uninstalling: Normally, you do not have to uninstall the client before installing a new client application. When upgrading from an older version to a newer version, HPDM overwrites the files for the older version. When downgrading from a newer version to an older version of HPDM, HP recommends that you uninstall the current version before installing the down-rev version. Uninstalling does not remove favorites or system definitions. However, uninstalling and then installing a down-rev client can remove the system definitions. If you uninstall from the Start menu, a prompt asks if you want to repair or remove the HP Database Manager. Selecting Repair is non-destructive and simply verifies the program files. Selecting Remove begins the uninstall process. Get Version and Build Information (page 47) Save and Import System Definitions (page 55) Start the HP Database Manager To start the HP Database Manager, use either of these methods: Double-click the HP Database Manager icon on your desktop: Install the HP Database Manager 23

24 From the Start menu, select Start > All Programs > HP Database Manager > HP Database Manager. NOTE: Most HPDM features require you to connect to the Neoview data warehousing platform through the ODBC client driver. For more information, see Connect to a System (page 25). Exit the HP Database Manager To exit HPDM, close the HP Database Manager main window by selecting File > Exit or clicking the Close button ( ) in the upper right corner of the main window. Exiting the application securely disconnects all active sessions. To disconnect from a single active session without exiting HPDM or closing other active sessions, use the Disconnect command. See Disconnect From a System (page 27). 24 Install and Start HPDM

25 3 Connect and Disconnect Connect to a System If this is the first time you are attempting to connect to a system, you must create a system definition. See Add a System (page 29). If a system definition is already created, use these steps to connect: 1. Enter the Connect command by using one of these methods: In the navigation tree pane, right-click the system icon, and select Connect. In the navigation tree pane, click the icon for a disconnected system (see Use the Navigation Tree Pane (page 37)). Unless the Monitoring area is selected, the Connect / Edit System information appears in the right pane. If the Monitoring area is selected, click the Connect button ( ) on the HPDM toolbar. Display the Systems Tool by selecting Tools > Systems Tool from the menu bar. Then double-click the system definition that you want to connect to. Or select the system definition, and click [ Edit ]. The Connect / Edit System dialog box appears. 2. Enter connection information into the Connect / Edit System dialog box. See the descriptions of each field in Use the Connect / Edit System Dialog Box (page 26). 3. Click one of these buttons: Button [ Save ] [ Connect ] [ Cancel ] Description Creates the new system definition, but does not attempt to connect to the system. Attempts to connect to the system using the entries specified in the Connect / Edit System dialog box: If the connection is successful, the entry for the system is created and appears in the Systems Tool window. The system name also is added to the My Systems folder. If the connection attempt is not successful, HPDM displays an error message. Cancels the operation. Add a System (page 29) Use the Connect / Edit System Dialog Box (page 26) Log On and Off (page 28) Disconnect From a System (page 27) Terms My Systems Systems Tool system definition Connect to a System 25

26 Use the Connect / Edit System Dialog Box This table shows reference information for the Connect / Edit System dialog box: Field Your Name for System Data Source User Name Role Name Password Host Port Number Default Schema Driver Certificate File Example Production Sys 1 DSN_PROD1 user-465 ROLE.DBA User 1!uPzTa4 User/Role 1!uPzTa4/98_Lzrew ABC0101.abc.def.com USR HP ODBC 2.0 C:\Certificates \SEC01Active.cer Description A label to identify this Neoview platform. The name can be up to 32 characters in length and consist of letters, digits, and the underscore character. This is a required field. Specifies the name of the client-side or server-side data source. If no data source is specified, or if the specified client-side data source cannot be found, the client connects to the default server-side data source (TDM_Default_DataSource). Your user name. This is a required field. Neoview role. Note these considerations: If you are a platform user, leave this field blank. If you are a database user and you leave this field blank, HPDM uses your default role. For database users, if you specify a role and then need to log on using a different role, you must disconnect and specify the new role when you reconnect to the system. NOTE: It is possible for database users to run multiple active sessions while logged on as the same user but with different roles. To do this, you must configure system definitions having different roles. See Add a System Like... (page 33). Your Neoview password. This is a required field. For more information, see Password Considerations (page 27). The DNS name or IP address for the target Neoview platform. This is a required field. The NDCS server port number. This is a required field. The default schema to use if composing a query. If this field is left blank, the default schema is either of: The schema matching your user name, with any lowercase characters upshifted. The schema matching your role name, with any lowercase characters upshifted. Whether or not the schema is based on your user name or role name depends on certain default settings. CAUTION: If the Default Schema name is a reserved word in Neoview SQL (for example, USER), you must enclose the schema name in double quotes ( USER ). Otherwise, the connection will fail. For a list of reserved words, see the Neoview SQL Reference Manual. The installed Neoview ODBC driver to be used with this Neoview platform. This is a required field. The certificate file to use when connecting to the system. The certificate file can be downloaded by the driver to the client during connection. However, if the Auto Download Certificate option is disabled, the certificate file is not downloaded. Without a certificate file, the connection fails. This field allows you to browse to and select a certificate file on your workstation, if needed. NOTE: If you connect to a Neoview system running Release 2.4 or earlier, this field is ignored by the driver. 26 Connect and Disconnect

27 In the Connect / Edit System dialog box, these buttons allow you to add a new system definition, connect to a system, or close the system definition. Button [ Save ] [ Connect ] [ Cancel ] Description Creates the new system definition but does not attempt to connect to the system. Attempts to create the new system using the entries specified in the fields of the Connect / Edit System dialog box: If the connection is successful, the entry for the system is created and appears in the Systems Tool window. The system name also is added to the My Systems folder. If the connection attempt is not successful, HPDM displays an error message. Closes the dialog box without making changes. Edit a System (page 32) Connect to a System (page 25) Display Security Policies (page 117) About the Auto Download Certificate Option (page 129) Terms My Systems system definition TDM_Default_DataSource NDCS server role data source Password Considerations To connect to a Neoview system using the Connect / Edit System dialog box or the Add System dialog box, you must supply a password. Depending on security policies in force at your site, you might have to supply passwords not only for yourself but also for the role you are using. Roles that might require you to specify both your own password and the role password are: ROLE.MGR ROLE.SECMGR ROLE.DBA SUPER.SUPER HP.VTS SAP.USER Roles that always require you to specify both your own password and the role password are: SUPER.SERVICES HP.SDI For more information about security policy options, see the Neoview User Management and Security Administration Guide. Use the Connect / Edit System Dialog Box (page 26) Use the Add System Dialog Box (page 30) Disconnect From a System Disconnecting closes all ODBC connections with a system. To disconnect from a selected system: Password Considerations 27

28 1. Enter the Disconnect command by using one of these methods: In the navigation tree pane, right-click the icon for the connected system, and select Disconnect. In the navigation tree pane, click the icon for a connected system (see Use the Navigation Tree Pane (page 37)). Then click the Disconnect button ( ) on the HPDM toolbar. Display the Systems Tool by selecting Tools > Systems Tool from the menu bar. Select a system definition, then click [ Disconnect ]. The Confirm dialog box appears. 2. In the Confirm dialog box: Click [ Yes ] to disconnect the selected system, and close the Confirm dialog box. Click [ No ] to retain a connection with the selected system, and close the Confirm dialog box. Once you have disconnected, the system icon and icon label change to reflect the disconnected status. To disconnect from all systems, see Exit the HP Database Manager (page 24). Use the Systems Tool (page 28) Exit the HP Database Manager (page 24) Terms disconnect Systems Tool Log On and Off You log on to HPDM as part of connecting to a system. See Connect to a System (page 25). To connect to a system, you must create a system definition. The system definition is saved and can be reused over and over again. After a system definition is created, you need only specify a password to connect to a system. The tool you use to manage system definitions is the Systems Tool. See Use the Systems Tool (page 28). You log off from a system by performing either of these operations: Disconnecting. Disconnecting closes all ODBC connections with a system without removing the system definition or exiting the HPDM client application. See Disconnect From a System (page 27). Exiting the HPDM client application. Exiting disconnects all active sessions (all systems) simultaneously without removing the system definitions. See Exit the HP Database Manager (page 24). Connect to a System (page 25) Use the Systems Tool (page 28) Disconnect From a System (page 27) Exit the HP Database Manager (page 24) Terms system definition Systems Tool Use the Systems Tool The Systems Tool contains the components used to define, add, edit, remove, duplicate, test, and open existing systems on the Neoview platform. To open the Systems Tool, use one of these methods: Click the Systems Tool button ( ) on the HPDM toolbar. From the menu bar, select Tools > Systems Tool. 28 Connect and Disconnect

29 The Systems Tool window displays these settings: Setting State System Name Data Source User Name User Role Host Port Number Default Schema DriverString Description The current state of the system definition (Connected or Disconnected). The label that identifies this Neoview platform. The system name can be up to 32 characters in length, and can consist of letters, digits, and the underscore character. Specifies the name of the client-side or server-side data source. If no data source is specified, or if the specified client-side data source cannot be found, the client connects to the default server-side data source (TDM_Default_DataSource). Your user name. The Neoview role (for example, ROLE.DBA) that was specified for the system definition. If this field is not specified in the system definition, HPDM uses the default role for the user. The DNS name or IP address for the target Neoview platform. The ODBC server port number. The default entry for the system (optional). The ODBC driver. The button options for the Systems Tool are: Button [ Test ] [ Edit ] [ Add ] [ Add Like ] [ Remove ] [ Disconnect ] [ Done ] Function Tests a selected system and displays the results in the Connection Test Result dialog box. [ Test ] is enabled if one or more systems are selected. Launches the Connect / Edit System dialog box with the selected systems current settings. [ Edit ] is enabled if one or more systems are selected. Launches the Add System dialog box with blank settings, except for the port number (which defaults to 18650). The ODBC driver defaults to 2.0. [ Add ] is always enabled. Launches the Add System Like dialog box with the selected systems current settings. You can use these settings as a starting point for adding a new system. [ Add Like ] is enabled if only one system is selected. Launches the Confirm dialog box. [ Remove ] is enabled if one or more systems is selected. Launches the Confirm dialog box. [ Disconnect ] is enabled if one or more systems is selected. Closes the Systems Tool. Terms system data source TDM_Default_DataSource Add a System If no system definitions are present from a previous session, regardless of whether the currently running version of HPDM is a new, updated, or an existing installation, you must create a new system definition. Add a System 29

30 NOTE: HPDM can connect to platforms running Neoview Release 2.3 and later. However, not all features available in the current release are available in down-rev releases. If a feature is not available, HPDM returns an error message. To create a new system definition: 1. Use either of these methods to open the Add System dialog box: In the navigation tree pane, right-click the My Systems folder, and select Add System. Display the Systems Tool by selecting Tools > Systems Tool from the menu bar. Then click [ Add ]. 2. Enter information into the Add System dialog box. See the descriptions of each field in Use the Add System Dialog Box (page 30). 3. Click one of these buttons: NOTE: Once a system is added, the system definition persists from session to session unless it is removed. Button [ Add ] [ Connect ] [ Cancel ] Description Creates the new system definition, but does not attempt to connect to the system. Attempts to create the new system using the entries specified in the Add System dialog box: If the connection is successful, the entry for the system is created and appears in the Systems Tool window. If the connection attempt is not successful, HPDM displays an error message. Cancels the operation. Use the Add System Dialog Box (page 30) Connect to a System (page 25) Terms system definition Use the Add System Dialog Box This table shows reference information for the Add System dialog box: Field Your Name for System Data Source User Name Example Production Sys 1 DSN_PROD1 user-465 Description A label to identify this Neoview platform. The name can be up to 32 characters in length and consist of letters, digits, and the underscore character. This is a required field. Specifies the name of the client-side or server-side data source. If no data source is specified, or if the specified client-side data source cannot be found, the client connects to the default server-side data source (TDM_Default_DataSource). Your user name. This is a required field. 30 Connect and Disconnect

31 Field Role Name Password Host Port Number Default Schema Driver Certificate File Example ROLE.DBA User 1!uPzTa4 User/Role 1!uPzTa4/98_Lzrew ABC0101.abc.def.com USR HP ODBC 2.0 C:\Certificates \SEC01Active.cer Description Neoview role. Note these considerations: If you are a platform user, leave this field blank. If you are a database user and you leave this field blank, HPDM uses your default role. For database users, if you specify a role and then need to log on using a different role, you must disconnect and specify the new role when you reconnect to the system. NOTE: It is possible for database users to run multiple active sessions while logged on as the same user but with different roles. To do this, you must configure system definitions having different roles. See Add a System Like... (page 33). Your Neoview password. This is a required field. For more information, see Password Considerations (page 27). The DNS name or IP address for the target Neoview platform. This is a required field. The NDCS server port number. This is a required field. The default schema to use if composing a query. If this field is left blank, the default schema is either of: The schema matching your user name, with any lowercase characters upshifted. The schema matching your role name, with any lowercase characters upshifted. Whether or not the schema is based on your user name or role name depends on certain default settings. CAUTION: If the Default Schema name is a reserved word in Neoview SQL (for example, USER), you must enclose the schema name in double quotes ( USER ). Otherwise, the connection will fail. For a list of reserved words, see the Neoview SQL Reference Manual. The installed Neoview ODBC driver to be used with this Neoview platform. This is a required field. The certificate file to use when connecting to the system. The certificate file can be downloaded by the driver to the client during connection. However, if the Auto Download Certificate option is disabled, the certificate file is not downloaded. Without a certificate file, the connection fails. This field allows you to browse to and select a certificate file on your workstation, if needed. NOTE: If you connect to a Neoview system running Release 2.4 or earlier, this field is ignored by the driver. Use the Add System Dialog Box 31

32 In the Add System dialog box, these buttons allow you to add a new system, add and connect to a new system, or cancel the operation. Button [ Add ] [ Connect ] [ Cancel ] Description Creates the new system definition, but does not attempt to connect to the system. Attempts to create the new system using the entries specified in the Add System dialog box: If the connection is successful, the entry for the system is created and appears in the Systems Tool window. If the connection attempt is not successful, HPDM displays an error message. Cancels the operation. Add a System (page 29) Display Security Policies (page 117) About the Auto Download Certificate Option (page 129) Terms system definition TDM_Default_DataSource My Systems NDCS server role data source Edit a System You cannot edit an active system definition. If you need to edit a system definition for a system that is currently connected, you must first disconnect from the system. To edit a system definition: 1. Use either of these methods to open the Connect / Edit System dialog box: In the navigation tree pane, right-click the icon for a disconnected system, and select Connect or Edit. Display the Systems Tool by selecting Tools > Systems Tool from the menu bar. Select a system definition that is currently disconnected, then click [ Edit ]. 2. Enter information into the Connect / Edit System dialog box. See the descriptions of each field in Use the Connect / Edit System Dialog Box (page 26). 3. Click one of these buttons: Button [ Save ] [ Connect ] [ Cancel ] Description Creates the new system definition, but does not attempt to connect to the system. Attempts to create the new system using the entries specified in the Add System dialog box: If the connection is successful, the entry for the system is created and appears in the Systems Tool window. If the connection attempt is not successful, HPDM displays an error message. Cancels the operation. Disconnect From a System (page 27) Use the Connect / Edit System Dialog Box (page 26) 32 Connect and Disconnect

33 Add a System Like... To add a system by copying another system definition: 1. Use either of these methods to open the Add System Like dialog box: In the navigation tree pane, right-click any system name, and select Add System Like This. The Add System Like dialog box is displayed. Display the Systems Tool by selecting Tools > Systems Tool from the menu bar. Select the system definition that you want to copy. Then click [ Add Like ]. The Add System Like dialog box is displayed. 2. In the Add System Like dialog box: a. Specify a new name in the Your Name for System field. b. Validate the information specified for the selected system, changing the required fields as needed. The title bar displays the system whose settings are being used as a template for the new system. For reference, see Use the Add System Dialog Box (page 30). c. Click one of these buttons: Button [ Add ] [ Connect ] [ Cancel ] Description Creates the new system definition, but does not attempt to connect to the system. Attempts to create the new system using the entries specified in the Add System dialog box: If the connection is successful, the entry for the system is created and appears in the Systems Tool window. If the connection attempt is not successful, HPDM displays an error message. Cancels the operation. Use the Add System Dialog Box (page 30) Terms system definition Remove a System To remove a selected system: 1. Use either of these methods to issue the Remove System command: In the navigation tree pane, right-click the system, and select Remove System. The Confirm dialog box is displayed. Display the Systems Tool by selecting Tools > Systems Tool from the menu bar. Select the system that you want to remove, and click [ Remove ]. The Confirm dialog box is displayed. 2. In the Confirm dialog box, click one of these buttons: [ Yes ] removes the system definition, and closes the Confirm dialog box. [ No ] retains the system definition and closes the Confirm dialog box. Test a System To test the validity of the ODBC connection to a system, use either of these methods: Initiate a test from the navigation tree pane: 1. Connect to the system as described in Connect to a System (page 25). Add a System Like... 33

34 2. Right-click the system icon, and select Test System. Initiate a test from the Systems Tool: 1. Connect to the system as described in Connect to a System (page 25). 2. Display the Systems Tool by selecting Tools > Systems Tool from the menu bar. 3. Select the connected system that you want to test. 4. Click [ Test ]. Selecting the Test System or [ Test ] command: Causes an attempt to make a connection to the Neoview platform specified in the selected system definition. Returns a validating result in the Connection Test Result dialog box. Terms system definition My Systems Set the Connection Timeout If you frequently receive connection timeout errors, you might want to increase the connection timeout value. The ODBC driver default for login timeout is 15 seconds. However, when a system is heavily loaded, establishing an ODBC connection can take more than 60 seconds, and sometimes HPDM connections can time out under these conditions. HPDM allows you to override the connection timeout specified in the client data source: Note these considerations before setting the connection timeout: The default value for the connection timeout option is 180 seconds (3 minutes). The range is an integer value from 0 to 2,147,483,647 seconds. Setting a value of 0 means no timeout. Setting the connection timeout in this way does not address timeouts that might occur on query execution. To set the connection timeout: 1. Click the Options button ( ) on the HPDM toolbar, or select Tools > Options to display the Options dialog box. 2. Click the plus sign (+) next to the General option to display the suboptions, and select Framework. 3. In the right pane of the Options dialog box, type the number of seconds that you want to specify for the connection timeout. 4. Click [ OK ]. Control the Display of an Area (page 37) Use the HPDM Toolbar (page 44) 34 Connect and Disconnect

35 4 Navigate HPDM See the Parts of the HPDM Interface Use the HPDM Toolbar (page 44) See the HPDM Banner (page 41) Use the Navigation Tree Pane (page 37) Use the Right Pane (page 39) Use the My Favorites Pane (page 40) Use Menu Bar Commands (page 42) Select an Area Areas are broad categories of features that you can monitor or manage using HPDM. To select an area, click one of the blue bars below the navigation tree pane: See the Parts of the HPDM Interface 35

36 Area Space Management Security Description Provides information about SQL-space usage on the system. Provides tools to manage certificates, directory servers, security policies, users, and passwords. See for More Information Manage Disk Space (page 241) Manage Certificates (page 125) Manage Directory Servers (page 131) Manage Security Policies (page 117) Manage Roles (page 95) Manage Users and Passwords (page 103) Monitoring Provides alert and alarm information for the system. Provides the system message, as well as any other system-wide information that might be informative to an administrator or user. Use the System Monitor (page 171) Database Connectivity Provides information about the database objects. See Display Database Objects (page 63). Data sources and connectivity services. Display Database Objects (page 63) Manage Connectivity (page 155) HPDM displays the currently selected area below the menu bar ( See the Parts of the HPDM Interface (page 35)). When an area is selected, HPDM displays the characteristics of that area for all connected systems. Control the Display of an Area (page 37) 36 Navigate HPDM

37 Terms area Control the Display of an Area By default, HPDM displays all of the areas that the currently installed server software supports displaying. However, any user can show or hide an area by using the Options menu. To display the Options menu, click the Options button ( Tools > Options: ) on the HPDM toolbar, or select To hide an area: 1. Deselect the option for the area in the Show/Hide Area Options group box. 2. Click [ OK ]. To show an area that is hidden: 1. Select the option for the area in the Show/Hide Area Options group box. 2. Click [ OK ]. Select an Area (page 35) Terms area Use the Navigation Tree Pane The navigation tree pane is the left pane of HPDM below the My Favorites pane. See the Parts of the HPDM Interface (page 35). The navigation tree pane displays all systems that have been added using the Systems Tool. System icons appear under the My Systems folder. A green check mark identifies connected systems: Control the Display of an Area 37

38 When the Database area is selected, the navigation tree pane allows you to expand a connected system, showing the database objects underneath it in hierarchical form. You can switch between different systems and manage multiple Neoview systems from one user interface. The right pane displays more detail about any object selected in the navigation tree pane. See Use the Right Pane (page 39). If no systems are defined, the right pane displays this message: In order to use a system you must have added it. You can do so by clicking the Add System button below. If you add a system and its settings are complete and correct, it will be added to the My Systems folder. If the system s settings are incomplete and/or incorrect, it will be added to the My Systems folder. In either case, you will be able to edit the system later. To add a new system, click [ Add System ] at the bottom of the right pane. If systems have been added previously, the right pane displays the active systems. To display options for the My Systems folder, right-click the My Systems folder: Option Add to Favorites Refresh Add System Description Opens the New Favorite dialog box if a system definition is present and selected. If no system definition is present or selected, this command has no effect. Refreshes the object and all children for the object in the navigation tree. Creates a new system. See Add a System (page 29). To display options for a connected system in the My Systems folder, right-click the icon for the connected system: Option Add to Favorites Refresh Disconnect Test System Add System Like This Remove System Dial Out Events Database Events Description Creates a shortcut for the object under My Favorites. The New Favorite dialog box is launched to provide an alias for the object. See Use the My Favorites Pane (page 40). Refreshes the object and all children for the object in the navigation tree. Closes all ODBC communication with the system. See Disconnect From a System (page 27). Tests the validity of a system. See Test a System (page 33). Adds a system like the selected system s current settings. See Add a System Like... (page 33). Removes a selected system. See Remove a System (page 33). Opens a browser window allowing you to view system events that are dialed out to HP Support. See View Dial Out and Database Events (page 56). Opens a browser window allowing you to view events related to database activity, data loads, and queries. See View Dial Out and Database Events (page 56). To display options for a disconnected system in the My Systems folder, right-click the icon for the disconnected system: Option Add to Favorites Refresh Connect Description Creates a shortcut to the selected system on the navigation tree pane. See Use the My Favorites Pane (page 40). Refreshes the object and all children for the object in the navigation tree. Uses the values defined in the system definition to establish an ODBC connection with the system. See Connect to a System (page 25). 38 Navigate HPDM

39 Option Edit Add System Like This Remove System Description Edits an active system. See Edit a System (page 32). Adds a system like the selected system s current settings. See Add a System Like... (page 33). Removes a selected system. See Remove a System (page 33). See the Parts of the HPDM Interface (page 35) Add a System (page 29) Use the My Favorites Pane (page 40) Use the Right Pane (page 39) Disconnect From a System (page 27) View Dial Out and Database Events (page 56) Terms My Systems Use the Right Pane The right pane displays information about the selected objects in the My Favorites pane or the navigation tree pane. When the My Systems folder is selected, the buttons that are displayed in the bottom right pane are: Button [ Test ] [ Edit ] [ Add ] [ Add Like ] [ Remove ] [ Disconnect ] Function Tests a selected system and displays the results in the Connection Test Result dialog box. [ Test ] is enabled if one or more systems is selected. Launches the Edit System dialog box with the selected systems current settings. [ Edit ] is enabled if one or more systems is selected. Launches the Add System dialog box with blank settings, except for the port number (which defaults to 18650). The ODBC driver defaults to 2.0. [ Add ] is always enabled. Launches the Add Like System dialog box with selected systems current settings. You can use these settings as a starting point for adding a new system. [ Add Like ] is enabled if only one system is selected. Launches the Confirm dialog box. [ Remove ] is enabled if one or more systems is selected. Launches the Confirm dialog box. [ Disconnect ] is enabled if one or more systems is selected. If tabular data is displayed in the right pane, the buttons available at the bottom of the right pane are: Button [ Data to Clipboard ] [ Data to Browser ] [ Data to Spreadsheet ] [ Data to File ] Function Copies the table data to the Windows clipboard. See Export Data (page 53). Opens a browser to display the data in a tabular format. See Export Data (page 53). Opens the Excel application and displays the data. See Export Data (page 53). Exports the data to a file in CSV format. See Export Data (page 53). See the Parts of the HPDM Interface (page 35) Export Data (page 53) Terms Use the Right Pane 39

40 right pane navigation tree pane Use the My Favorites Pane A favorite is a shortcut to an object on the navigation tree pane. Favorites save you the trouble of having to scroll through and expand numerous parent objects. Favorites are displayed in the My Favorites pane. HPDM enables you to create favorites and organize them in folders. Use the Navigation Tree Pane (page 37) See the Parts of the HPDM Interface (page 35) Select an Area (page 35) Terms favorite My Favorites pane Create a Favorite Use a Favorite To create a favorite, use either of these methods: Drag and drop an object into the My Favorites pane: 1. Optional: If you want the favorite to reside in a folder in the My Favorites pane, and the folder does not exist yet, you must create the folder first. See Create a Folder to Store Favorites (page 41). 2. In the navigation tree pane, navigate to the object. 3. Click and drag the object into the My Favorites pane, letting go of the object when your cursor is above either a folder name or My Favorites. A dialog box asks you to enter a name for the favorite. 4. Type a name for the favorite (names must be less than 256 characters), and click [ OK ]. If you selected a folder in the first step, the favorite is added to the folder. If not, the favorite is added to the My Favorites top-level hierarchy. Right-click an object and use menu commands to create the favorite: 1. Optional: If you want the favorite to reside in a folder in the My Favorites pane, select the folder. If the folder does not exist, see Create a Folder to Store Favorites (page 41). 2. In the navigation tree pane, navigate to the object. 3. Right-click the object, and select Add To Favorites. A dialog box asks you to enter a name for the favorite. 4. Type a name for the favorite (names must be less than 256 characters), and click [ OK ]. If you selected a folder in the first step, the favorite is added to the folder. If not, the favorite is added to the My Favorites top-level hierarchy. To use a favorite, click the favorite in the My Favorites pane. Information about the favorite is displayed in the right pane. View a List of Favorites To view a list of current favorites and folders in the My Favorites top-level hierarchy, including the path to each favorite, double-click My Favorites In the My Favorites pane. To view a list of favorites contained in a folder, including the path to each favorite, double-click the folder. 40 Navigate HPDM

41 Create a Folder to Store Favorites In the My Favorites pane, you can create folders at the top level or folders within folders: 1. In the My Favorites pane, right-click My Favorites, and select New Folder. NOTE: To create a folder within a previously configured folder, right-click the folder, and select New Folder. 2. Type a name for the folder, and click [ OK ]. Add a Favorite to a Folder You can create a favorite and store it in a folder, but you cannot: Move a favorite from one folder to another folder. Move a favorite that already exists in the top-level hierarchy of the My Favorites pane into a folder. To add a favorite to a folder: 1. If necessary, create the folder. See Create a Folder to Store Favorites (page 41). 2. Create a favorite in the desired folder by performing the steps in Create a Favorite (page 40). Share Your Favorites With Others You can save your favorites (and other personalized client settings) by saving and sharing a copy of your system definitions. See Save and Import System Definitions (page 55). Remove a Favorite To remove a favorite, right-click the favorite, and select Remove. Remove a Favorites Folder To remove a folder, right-click the folder, and select Remove. The folder and all favorites contained within it are removed. See the HPDM Banner The HPDM banner appears above the right pane. For example: The banner displays the: Name of the system definition Host and port information for the current connection Currently connected data source WMS service Default schema User name information Role name information See the Parts of the HPDM Interface (page 35) See the HPDM Banner 41

42 Use Menu Bar Commands The menu bar is the list of commands at the top of the HPDM main window. The menu bar commands are: File, Edit, Tools, Windows, and Help. Menu Bar Command File Edit Tools Windows Help See for More Information Use the File Menu Options (page 42) Use the Edit Menu Options (page 42) Use the Tools Menu Options (page 43) Use the Windows Menu Options (page 43) Use the Help Menu Options (page 43) Use the File Menu Options The File menu options are: Menu Option Import Persistence Save Persistence Export Persistence Exit Description Imports persistence data from a file that was saved earlier by HPDM. NOTE: All of the current settings are replaced by the settings in the file being imported. See Save and Import System Definitions (page 55). Saves the configuration. The current state is saved when the application closes or when certain events happen within HPDM. Saves the configuration to any file. The Export Persistence option can be used when exporting a specific configuration to other users in the organization. See Save and Import System Definitions (page 55). Securely disconnects all active sessions. See Exit the HP Database Manager (page 24). See the Parts of the HPDM Interface (page 35) Save and Import System Definitions (page 55) Exit the HP Database Manager (page 24) Use Menu Bar Commands (page 42) Terms menu bar persistence file system definition Use the Edit Menu Options The Edit menu options are: Menu Option Undo Redo Cut Copy Description Cancel the last operation. Cancel the last Undo command. Remove the selected text and copy it to the clipboard. Copy the selected text to the clipboard without removing it. 42 Navigate HPDM

43 Menu Option Paste Select All Description Insert the selected text at the cursor position. Highlight all text. Use Menu Bar Commands (page 42) Use the Tools Menu Options The Tools menu options are: Menu Option SQL Whiteboard Metric Miner Neoview Command Interface Systems Tool Options Description Opens the SQL Whiteboard. See Use the SQL Whiteboard (page 211). Opens the Metric Miner. See Use Metric Miner (page 219). Opens NCI. See Launch the Neoview Command Interface (NCI) (page 239). Displays the Systems Tool. See Use the Systems Tool (page 28). Displays the Options dialog box. See these topics: Control the Display of an Area (page 37) Set the Connection Timeout (page 34) Set Auto Logon Options (page 240) Control the Display of the Add Database User Dialog Box (page 108) About Space Management Tracing Options (page 266) Use Menu Bar Commands (page 42) Use the HPDM Toolbar (page 44) Use the Windows Menu Options The Windows menu options are: Menu Option Windows Manager Close All Windows Except Main Window Description Displays the Windows Manager. See Manage Multiple Open Windows (page 45). Closes all open Windows except for the main window. Use Menu Bar Commands (page 42) Use the Help Menu Options The Help menu options are: Menu Option Contents Index Description Opens the HPDM online help and displays the Contents tab. Opens the HPDM online help and displays the Index tab. Use Menu Bar Commands 43

44 Menu Option Search About Description Opens the HPDM online help and displays the Search tab. Displays the About dialog box. See Get Version and Build Information (page 47). Use Menu Bar Commands (page 42) Use the HPDM Toolbar HPDM toolbar buttons quickly allow you to perform many common operations: Button Connect / Edit System Disconnect Systems Tool Function Displays the Connect / Edit System dialog box, allowing you to make a connection to or modify a system definition. This icon is usable when a disconnected system is selected in the navigation tree pane. Displays the confirmation dialog box for disconnecting the currently selected system. This icon is usable when a connected system is selected in the navigation tree pane. Displays the Systems Tool, allowing you to define, add, edit, remove, duplicate, test, and open connections to a Neoview system using HPDM. See for More Information Use the Connect / Edit System Dialog Box (page 26) Disconnect From a System (page 27) Use the Systems Tool (page 28) Import Persistence Opens the Import Persistence dialog box, allowing you to use system definitions from a saved persistence file. Save and Import System Definitions (page 55) Save Persistence Cut Copy Paste SQL Whiteboard Saves the current persistence settings. Removes the selected text and copies it to the clipboard. Copies the selected text to the clipboard. Inserts the selected text at the cursor position. Displays the SQL Whiteboard, allowing you to execute statements against the Neoview SQL database. Save and Import System Definitions (page 55) Use the Edit Menu Options (page 42) Use the Edit Menu Options (page 42) Use the Edit Menu Options (page 42) About the SQL Whiteboard (page 211) 44 Navigate HPDM

45 Button Metric Miner Neoview Command Interface Options Function Displays the Metric Miner, allowing you to configure, execute, and organize reports. Opens the Neoview Command Interface (NCI). Displays the Options dialog box, allowing you to configure special options and views. See for More Information About Metric Miner (page 219) Neoview Command Interface (NCI) Guide or Launch NCI (page 239) Use the Tools Menu Options (page 43) Windows Manager Go to Parent Go to Previous Go to Next Displays the Windows Manager, listing all of the open windows and providing functions for displaying and closing these windows. Selects the next highest object in the navigation tree pane hierarchy. For example, if a table is currently selected, clicking Go to Parent selects the table folder. Clicking the icon again selects the schema icon. Selects the previous object (if any) in the navigation tree pane hierarchy. If no other objects exist, Go to Previous is disabled. Selects the next object (if any) in the navigation tree pane hierarchy. If no other objects exist, Go to Next is disabled. Manage Multiple Open Windows (page 45) Help Displays the online help. See the table of contents for this guide. See the Parts of the HPDM Interface (page 35) Work With Windows, Tabs, and Panes HPDM provides all of the conventional user-interface controls present in other Windows applications. HPDM windows can be resized by dragging the window corner or border. If a border is dragged, the window size changes only on the side of the border. If a corner is dragged, the two adjoining sides to the corner change size at the same time. When a window is resized, graphical objects in a window get resized, if necessary. When a window is resized, vertical and horizontal scroll bars in a window get resized, if necessary. If a window has a minimum size, it cannot be resized smaller than the minimum size. HPDM also provides some special features for displaying information. You can: Manage multiple open windows from one dialog box (see Manage Multiple Open Windows (page 45)) Clone windows and tabs (see Clone Tabs (page 46)) Expand and collapse window panes (see Expand and Collapse Panes (page 46)) Manage Multiple Open Windows The HPDM cloning feature makes it easy to display information in a separate window without having to launch a new instance of HPDM. To help you manage multiple windows, HPDM provides a Windows Manager that lists all of the open windows and provides functions for displaying and closing these windows. Work With Windows, Tabs, and Panes 45

46 To open the Windows Manager, click the Windows Manager button ( ) on the HPDM toolbar, or select Windows > Windows Manager from the menu bar. The Windows Manager buttons are: Button [ Window(s) To Front ] [ Close Window(s) ] [ Main Window To Front ] [ OK ] Description Moves the selected windows to the front. Closes the selected windows but leaves the main window open. Displays the main window. Closes the Windows Manager. Clone Tabs HPDM allows you to clone some tabs in a new window. This feature creates a copy of the selected tab and its information in a new window that can be resized and compared side-by-side with other cloned windows. This feature is especially useful if you want to monitor multiple systems or multiple aspects of the same system at the same time. To clone a tab, double-click the tab name, or right-click a tab name and select Clone in Window. NOTE: Cloning is not currently supported for these tabs: Bar Graph tab Timeline tab Hybrid tab System Offender tab Privileges tab Tabs in the Space Management area Clone the System Message Tab (page 55) Expand and Collapse Panes Some HPDM windows contain controls that quickly allow you to resize, expand, or collapse a pane or part of a pane: 46 Navigate HPDM

47 5 Perform Basic HPDM Operations Get Version and Build Information Version and build information appears in the About HP Database Manager box. To access the About box, select the Help > About menu in HPDM. The About HP Database Manager dialog box displays the current build information about HPDM. The HPDM.exe version information and the version procedure (VPROC) information is displayed. For example: The About dialog box also displays information about the installed components: Installed Components displays the components currently installed in this HPDM product version. Description describes the components. Click the installed component to view a brief description of the component. Resolve Errors and Error Messages If HPDM returns an error message that you don't understand or an error message that contains a number, see the Neoview Messages Manual. This manual can be found with the Neoview customer documentation on the Web site indicated by Resources on the Web (page 17). Resources on the Web (page 17) Related Documentation (page 15) Sort and Move Data Columns You might want to see rows in an HPDM display (for example, a list of schemas) grouped by a specific type of information. You can sort the displayed data based on column values. You can also change the order of the columns by dragging a column heading to the left or right. Get Version and Build Information 47

48 To change the sort order of a displayed column: Click the title of the column that you want to sort. A triangle appears to the right of the heading to indicate ascending or descending order: To sort on multiple columns: 1. Click a column heading. 2. Hold down the Ctrl key and click another column heading. 3. Continue holding down the Ctrl key and clicking additional column headings until you have selected all of the desired columns for the multicolumn sort. HPDM numbers the selected columns and sorts the data based on the order in which the columns were selected: To move a displayed data column: 1. Click and drag a column heading to the left or right, and release the column in a new position. A shaded outline of the column heading facilitates placement: 2. Repeat as necessary until the columns are arranged the way you want them. Work With Data Grids About Data Grids The Alerts tab, System Offender tab, SQL Whiteboard Statement Details pane, Metric Miner Report Results pane, and some Space Management panes, such as the Over Threshold Summary, 48 Perform Basic HPDM Operations

49 display information in a data grid. The data grid is a simple table with columns and some special features for displaying and manipulating data. Data grids allow you to do some or all of these tasks: Get details about a specific cell or row. Issue commands by right-clicking to display a context menu Sort data within a column. Rearrange columns. Copy cell or row information. Customize the display of information. Search for information in the grid. Some HPDM tabs (the tabs in the Database area, for example) do not provide data-grid features. You can usually sort and export the data in these tabs, but you can't get row detail information, search for items, or display context menus. See the Parts of the Alerts Tab (page 181) See the Parts of the System Offender (page 194) See the Parts of Metric Miner (page 220) Get Row Details for a Data Grid (page 49) Copy Data-Grid Information (page 50) Customize the Data Grid (page 52) Search the Data Grid (page 52) Terms data grid Get Row Details for a Data Grid To get more information about any row in a data grid, use either of these methods: Right-click any cell in the row, and select Row Details. Double-click any cell in the data grid. The Row Details dialog box is displayed. For example, this is the Row Details dialog box for Alerts: Work With Data Grids 49

50 The Row Details dialog box displays all possible column information, whereas the data grid shows only the grid columns that are currently configured using the Show/Hide Grid Columns command. Arrows at the top of the dialog box allow you to display detail information for other rows in the data grid without leaving the Row Details dialog box: About Data Grids (page 48) Customize the Data Grid (page 52) Copy Data-Grid Information To copy data-grid information, use the Copy command in the context menu. For example: NOTE: Only one cell at a time can be copied in the System Offender tab. To copy the data in contiguous cells, select the cells you want to copy by clicking and dragging, then right-click and select the Copy command: 50 Perform Basic HPDM Operations

51 To copy the data in noncontiguous cells, hold down the Ctrl key, and select the cells you want to copy. Then right-click, and select Copy: The cell values are loaded into the Windows clipboard, from which you can paste them into other Windows applications. About Data Grids (page 48) Customize the Data Grid (page 52) Work With Data Grids 51

52 Customize the Data Grid The columns in data grids are fully customizable: To Show or hide columns Change the order of displayed columns Do this 1. Right-click a column heading in any data grid, and select Show/Hide Grid Columns. The Show/Hide Grid Columns dialog box appears. 2. Select the columns that you want to display, and click [ OK ]. NOTE: Click [ Defaults ] at any time to restore the default column selections. Use either of these methods: In the Show/Hide Grid Columns dialog box, select a column, then click the up or down arrows to change the position of the column: Then click [ OK ]. In the data grid, click and drag the column to a new position. See Sort and Move Data Columns (page 47). Sort information in the columns See Sort and Move Data Columns (page 47). Changes you make are persisted across HPDM sessions. About Data Grids (page 48) Search the Data Grid Select any cell in the data grid, then type the first few characters of a string that you want to search. HPDM jumps to the first occurrence of a cell within the same column that contains the search string. Use Alt + and Alt + to jump to the next or previous occurrence of the search string: About Data Grids (page 48) 52 Perform Basic HPDM Operations

53 Export Data Export Data to the Clipboard [ Data to Clipboard ] saves the data to the clipboard. Each value is a double-quoted string. The clipboard can then be pasted to any Windows document (for example, Excel, Notepad, or Word). Export Data to a File [ Data to File ] (if enabled) displays a window to export the contents to a file. There are two format types available for [ Data to File ]: Save Data in CSV Format (page 53) Save Data in HTML Format (page 53) Save Data in CSV Format In Comma Separated File Format (CSV) the data is saved in a comma separated format [.csv]. In the Save As dialog box: Navigate to a location where a copy of the data can be saved. Enter a name for the content in the Save As box. Select Save As Type (with the.csv extension) The default location is the %HOME% dir or the user's default application directory, if %HOME% is not defined. Save Data in HTML Format In HTML format the data is saved using the table <tr>, <td> tags. In the Save As dialog box: Navigate to a location where a copy of the data can be saved. Enter a name for the content in the Save As box. Select Save As Type (with the.html extension) The default location is the %HOME% dir or the user's default application directory, if %HOME% is not defined. Save Data to a Spreadsheet [ Data to Spreadsheet ] transparently saves the table data to a temporary local file in standard HTML table format and then executes the file. Executing the temporary local file into an Excel file launches Excel on a windows system if Excel is installed. Export Data to a Browser [ Data to Browser ] invokes Internet Explorer or a default browser displaying the table data. The data is exported internally in standard HTML format. Internet Explorer is then invoked on this HTML file. The file is a temporary file. You can then use Internet Explorer to save the contents. NOTE: The Export buttons are disabled if the table has no data. Communicate System Messages to Users If you are a system administrator for a Neoview platform, you may need to communicate information to users of HPDM. For example, this information might include current software configuration or maintenance notifications. HPDM provides a location, activated by clicking the System Message tab in Monitoring area (see Select an Area (page 35)) where users can obtain the latest information provided by system administrators. Export Data 53

54 Use the System Message Tab The System Message tab contains a system message control to convey information to users. The system message can be updated by a special role of user called a Publisher. The list of publishers is fixed and is comprised of: SUPER.SERVICES ROLE.MGR ROLE.DBA Any user belonging to one of these roles can modify a system message. All other users can only view messages. The system message is updated by a publisher and is comprised of the message body and the time of its last update. The message body is a text area The text area supports cut, copy, paste, undo and redo capabilities that are accessible through keyboard shortcuts and a context menu that appears when the text area is right-clicked. This figure shows a system message and context menu: Create a System Message To create a system message: 1. Log on as a Publisher user (SUPER.SERVICES, or a member of ROLE.MGR or ROLE.DBA). 2. Click the Monitoring area. For more information, see Select an Area (page 35). 3. In the right pane, click the System Message tab. 4. Type the system message text in the right pane. 5. Click [ Apply ]. The text area is displayed as an editable window if the user is connecting to the system as a Publisher user. Otherwise, the text area is read-only for all other users. The button bar contains [ Apply ] and [ Refresh ]. [ Apply ] is enabled if a Publisher modifies the text within the text area. When clicked, the text is updated to the server. [ Refresh ] causes the text area to be synchronized with the data from the server. If there are changes made to the text area since the last refresh, a confirmation dialog box asks if it is okay to lose the local changes. For all other users, [ Apply ] is hidden and only [ Refresh ] appears. See the HPDM Banner (page 41) 54 Perform Basic HPDM Operations

55 Clone the System Message Tab If you double-click the System Message tab, the control is cloned into a new window. When the contents of the system message are modified in any window (the main HPDM window or any cloned window), the change is immediately visible in all copies. Therefore, if the user types in one window, all of the other windows show the updated text. In addition, applying and refreshing any window affects the behavior in all other copies. Save and Import System Definitions Suppose that your company has many different HPDM users, and you have used the Systems Tool to configure numerous system definitions. HPDM allows you to save these definitions and share them for use on other workstations. System definitions are saved in a persistence file. The persistence file is a binary file that contains state and user preference information. This information includes: System definitions User-specified options Favorites Statements executed from the SQL Whiteboard SQL Whiteboard layout information The persistence file typically is located in the default directory for your Windows user name. For example, if your user name is janedoe, the persistence file is located at: Windows XP: C:\Documents and Settings\janedoe\HPDatabaseManager Windows Vista: C:\Users\janedoe\HPDatabaseManager However, the persistence file might be saved to a different location if a different directory is specified for the HOME environment variable for your workstation. To save the currently defined system definitions, use one of these methods: Click the Save Persistence button ( ) on the HPDM toolbar. On the HPDM menu bar, click File > Save Persistence. NOTE: Normally, it is not necessary to save persistence. The persistence file is saved automatically when you exit HPDM. To save a copy of the currently defined system definitions: NOTE: The file you save by performing these steps is not a true persistence file. It is simply a data file that can be used to transfer new information to the true persistence file. 1. On the menu bar, click File > Export Persistence. The Export Persistence dialog box appears. 2. Specify a file name and location for the copied persistence file. 3. Click [ OK ]. The file is saved with the.hpdm extension. To import system definitions from a saved.hpdm file: 1. Click the Import Persistence button ( ) on the HPDM toolbar, or select File > Import Persistence on the menu bar. The Import Persistence dialog box appears. 2. Select the previously saved.hpdm file, and click [ Open ]. The Confirm dialog box appears. 3. Click [ Yes ] to proceed or [ No ] to cancel the operation. If you click [ Yes ], HPDM loads the information from the.hpdm file into the persistence file and requires you to reconnect if you were connected to active systems. Save and Import System Definitions 55

56 Use Menu Bar Commands (page 42) Use the HPDM Toolbar (page 44) Terms persistence file system definition Systems Tool View Event Messages View Dial Out and Database Events You can view dial out and database events with any area selected. Dial out events are system events that are dialed out to HP Support. Database events are events related to database activity, data loads, and queries. In the current release, only these users can view dial out and database events: SUPER.SUPER SUPER.SERVICES Any user having administrative privileges NOTE: Event-message diagnostic information is primarily for use by HP support. If you have questions about event messages, contact your HP support representative. To view dial out or database events: 1. Under My Systems, right-click the Neoview platform for which you want to view events, and select Dial Out Events or Database Events. A browser window appears. 2. Enable the browser window to run JavaScript. (JavaScript is used to process the user name and password.) Usually, this can be done by activating a menu near the top of the page and selecting Allow Blocked Content. However, some browsers might require other steps. If you are unsure how to enable JavaScript, check your browser documentation. 3. Enter your user name and password, and click [ Submit ]. A new window opens to display events. Messages in red are critical. Messages in green are informational. NOTE: If the browser indicates that there is a problem with the Web site's security certificate, you might need to use facilities provided by your Certificate Authority (CA) to specify Subject Alternate Names (SANs) for all segments, or at least for all slave segments (for example, NEO0102 to NEO0116). This information is not present in the original CSR but is required to enable use of the event viewer. If your CA does not allow you to specify SANs, define a procedure for your users to follow if they encounter browser security messages. One approach is to instruct users to view the certificate, if possible, to check the vailidity of the displayed information. 4. For more detail about a message, click a message number. NOTE: Event information does not update automatically. You must either click Refresh or close and reopen the window to ensure the most current information. For more information about messages, see the Neoview Messages Manual in the Neoview Customer Library, located on the customer documentation Web site. See Resources on the Web (page 17). See the Trace Event Message Format This is the message format for: 56 Perform Basic HPDM Operations

57 Message Parameter NDCS Trace session-id function sequence number function-input-parameters function-exit-parameters Attribute Session ID: session-id Function: Enterfunction Sequence Number: sequence-number function-input-parameters or Session ID: session-id Function: Exitfunction Sequence Number: sequence-number function-exit-parameters Unique session ID generated by the SQL server at the time the connection is established. The SQL server function that is being traced. Messages too large for one message template are divided into smaller messages. Sequence number indicates which part of the message you are viewing. The sequence number is 0 for the first or only part of a message, and 1 for the additional parts, if any. List of input parameters to the function. List of output parameters from the function See above. Cause A trace informational message. Effect None Recovery Informational message only; no corrective action is needed. Resource Statistics Event Message Format Message Parameter NDCS Statistics message-attribute session-id message-attribute sequence number statistics-information Attribute Session ID: session-id Message Attribute: message-attribute Sequence Number:sequence-number Message Info:statistics-information { SESSION:ConnectionInformation } { SESSION: SessionSummary } { Statement: SQLStatement } { Statement: SQLExecDirect } { Statement: SQLExecute } { Statement: SQLPrepare } { Statement: SQLFetch } Unique session ID generated by the Neoview SQL server at the time the connection is established. Name of the statistics option you selected. Messages too large for one message template are divided into smaller messages. Sequence number indicates which part of the message you are viewing. The sequence number is 0 for the first or only part of a message, and 1 for additional parts, if any. The statistics collected for the session or statement options selected. View Event Messages 57

58 21035 See above. Cause Effect Recovery A resource statistics informational message. None Informational message only; no corrective action is needed. Session Statistics: Connection Information Session statistics are written to the alternate EMS collector at the time the connection is made (listed in the order written in the event message): Statistic Session ID Message Attribute Sequence Number Component UserName UserId ClientId ApplicationId DataSource NodeName CpuPin Description Unique session ID generated by the NDCS server at the time the connection is established. SESSION:ConnectionInformation (the statistics option that was selected). Message sequence number generated by NDCS. The number begins with zero (0) and is incremented by 1 with each new record. Name of the NDCS component to which the statistics apply. User name logged into the session (the logical name used at the time of connection). User ID that is logged into the session. Client workstation TCP/IP name or the NetBios/network name. Client application name or the main window caption. Client data source name used at the time of connection. Name of the Neoview platform used by the data source. Operating system CPU number in which the NDCS server is running, followed by the process ID of the server. Session Statistics: Session Summary Information Session statistics are written to the alternate EMS collector when the session is terminated (listed in the order written in the event message): Statistic Session ID Message Attribute Sequence Number StartTime EndTime StartPriority TotalOdbcExecution Time TotalOdbcElapsedTime Description Unique session ID generated by the NDCS SQL server at the time the connection is established. SESSION:Summary (the statistics option that was selected). Message sequence number generated by NDCS. The number begins with zero (0) and is incremented by 1 with each new record. Time when the connection request was received. Time when the session was terminated due to an application request or a server idle timeout. Execution priority of the NDCS process at the time the connection request is received. Total NDCS SQL server CPU process time, in microseconds, from the time the connection started to the time the connection closed; does not include Neoview SQL compiler time. Total NDCS SQL server real time, in microseconds, from the time the connection started to the time the connection closed. 58 Perform Basic HPDM Operations

59 Statistic TotalInsertStmtsExecuted TotalDeleteStmtsExecuted TotalUpdateStmtsExecuted TotalSelectStmtsExecuted TotalCatalogStmts TotalPrepares TotalExecutes TotalFetches TotalCloses TotalExecDirects TotalErrors TotalWarnings Description Total number of SQL INSERT statements sent by the HP ODBC driver to the NDCS SQL server; does not include internally generated SQL statements. Total number of SQL DELETE statements sent by the HP ODBC driver to the NDCS SQL server; does not include internally generated SQL statements. Total number of SQL UPDATE statements sent by the HP ODBC driver to the NDCS SQL server; does not include internally generated SQL statements. Total number of SQL SELECT statements sent by the HP ODBC driver to the NDCS SQL server; does not include internally generated SQL statements. Total number of SQL Catalog statements sent by the HP ODBC driver to the NDCS SQL server. Total number of SQLPrepare calls. Total number of SQLExecute calls. Total number of SQLFetch calls. Total number of SQLClose calls. Total number of SQLExecDirect calls. Total number of SQL statement execution errors detected by the NDCS SQL server. Total number of SQL statement execution warnings detected by the NDCS SQL server. Statement Statistics: SQL Statement Statement statistics are written to the alternate EMS collector at the time a PREPARE statement is received (listed in the order written in the event message): Statistic Session ID Message Attribute Sequence Number StatementID SQL Text Description Unique session ID generated by the NDCS SQL server at the time the connection is established. STATEMENT:SQLStatement (the statistics option that was selected). Message sequence number generated by NDCS. The number begins with zero (0) and is incremented by 1 with each new record. Unique statement ID generated by the NDCS SQL server at the time the PREPARE statement is received. Text of the SQL statement. This field can be distributed in multiple messages. Statement Statistics: SQLExecute SQLExecute statistics are written to the alternate EMS collector at the time an EXECUTE statement is received (listed in the order written in the event message): Statistic Session ID Message Attribute Sequence Number StatementID Description Unique session ID generated by the NDCS server at the time the connection is established. STATEMENT:SQLExecute (Statistics option that was selected.) Message sequence number generated by NDCS. The number begins with zero (0) and is incremented by 1 with each new record. Unique statement ID generated by the NDCS SQL server at the time the PREPARE statement is received. View Event Messages 59

60 Statistic ODBCElapsedTime ODBCExecutionTime NumberOfRows ErrorCode RowsAccessed RowsRetrieved DiscReads MsgsToDisc MsgsBytesToDisc LockWaits LockEscalation Description Total NDCS SQL server real time, in microseconds, from the time the execute started to the time the results are sent back. Total NDCS SQL server CPU process time, in microseconds, from the time the execute started to the time the response is sent back to the client with the results error code. (ins/upd/del) Number of rows that were inserted, updated, or deleted. Execute error code, if any. A zero (0) indicates that the execute was successful. Cumulative number of rows accessed. Cumulative number of rows retrieved. Cumulative number of disk reads. Number of messages sent to the disk process. Size, in bytes, of the total number of messages sent to the disk process. Number of lock waits (this is the concurrency cost). Cumulative number of times record locks are escalated to file locks. Statement Statistics: SQLExecDirect SQLExecDirect statistics are written to the alternate EMS collector at the time an EXECUTE statement is received (listed in the order written in the event message): Statistic Session ID Message Attribute Sequence Number StatementID EstimatedCost StatementType ODBCElapsedTime ODBCExecutionTime NumberOfRows ErrorCode RowsAccessed RowsRetrieved DiscReads MsgsToDisc MsgsBytesToDisc LockWaits LockEscalation Description Unique session ID generated by the NDCS SQL server at the time the connection is established. STATEMENT:SQLExecDirect (Statistics option that was selected.) Message sequence number generated by NDCS. The number begins with zero (0) and is incremented by 1 with each new record. Unique statement ID generated by the NDCS SQL server at the time the PREPARE statement is received. Estimated query cost returned by the SQL compiler. Valid types are: Insert, Delete, Update, Select. Total NDCS SQL server real time, in microseconds, from the time the execdirect started to the time the results are sent back. Total NDCS SQL server CPU process time, in microseconds, from the time the execdirect started to the time the results are sent back. (ins/upd/del) Number of rows that were inserted, updated, or deleted. Execdirect error code, if any. A zero (0) indicates that the execdirect was successful. Cumulative number of rows accessed. Cumulative number of rows retrieved. Cumulative number of disk reads. Number of messages sent to the disk process. Size, in bytes, of the total number of messages sent to the disk process. Number of lock waits (this is the concurrency cost). Cumulative number of times record locks are escalated to file locks. 60 Perform Basic HPDM Operations

61 Statement Statistics: SQLPrepare SQLPrepare statistics are written to the alternate EMS collector at the time a PREPARE statement is received (listed in the order written in the event message): Statistic Session ID Message Attribute Sequence Number StatementID EstimatedCost StatementType SQLCompileTime ErrorCode Description Unique session ID generated by the NDCS SQL server at the time the connection is established. STATEMENT:SQLPrepare (Statistics option that was selected.) Message sequence number generated by NDCS The number begins with zero (0) and is incremented by 1 with each new record. Unique statement ID generated by the NDCS SQL server at the time the PREPARE statement is received. Estimated query cost. Valid types are: Insert, Delete, Update, Select. Total NDCS SQL server real time, in microseconds, from the time the prepare started to the time it returns to the client with the compile results. Prepare error code, if any. A zero (0) indicates that the prepare was successful. Statement Statistics: SQLFetch SQLFetch statistics are written to the alternate EMS collector at the time a statement is closed (listed in the order written in the event message): Statistic Session ID Message Attribute Sequence Number StatementID RowsAccessed RowsRetrieved DiscReads MsgsToDisc MsgsBytesToDisc LockWaits LockEscalation TotalOdbcElapsedTime TotalOdbcExecutionTime TotalExecutes Description Unique session ID generated by the NDCS SQL server at the time the connection is established. STATEMENT:SQLFetch/SQLClose (Statistics option that was selected.) Message sequence number generated by NDCS The number begins with zero (0) and is incremented by 1 with each new record. Unique statement ID generated by the NDCS SQL server at the time the PREPARE statement is received. Cumulative number of rows accessed. Cumulative number of rows retrieved. Cumulative number of disk reads. Number of messages sent to the disk process. Size, in bytes, of the total number of messages sent to the disk process. Number of lock waits (this is the concurrency cost). Cumulative number of times record locks are escalated to file locks. Total NDCS SQL server real time, in microseconds, from the time the fetch was prepared to the time it was closed. Total NDCS SQL server CPU process time, in microseconds, from the time the fetch was prepared to the time it was closed. Total number of executes performed on the statement. View Event Messages 61

62 62

63 6 Display Database Objects This section describes how to display schemas, tables, table indexes, views, materialized views, materialized view indexes, materialized view groups, procedures, synonyms, and triggers in HPDM. Display Schemas and Their Objects To display the schema names and attributes for the schema: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. HPDM displays a list of existing schemas and their owners. 3. Select a system in My Systems in the navigation tree. 4. In the navigation tree pane, expand the All Schemas folder, and select a schema. In the right pane, these tabs are displayed: Attributes tab Tables tab Materialized Views tab Materialized View Groups tab Views tab Procedures tab Synonyms tab Display Schemas and Their Objects 63

64 Attributes Tab Tables Tab DDL tab Privileges tab To display the schema attributes and values that belong to the schema: 1. Navigate to the Schema folder and click the name of the schema to see information about the schema and its objects. 2. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the schema. Owner: The owner of the schema. Version: Specfies the version of the schema. To display the table names that belong to the schema: 1. Select a Schema in the navigation tree. 2. Click the Tables tab in the right pane, or open the Tables folder. In the right pane, these attributes are displayed: Name: Name of the table. Each table name is hyperlinked and detailed information about the table is displayed. Creation Time: Time and date when the table was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the table was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Materialized Views Tab To display the materialized views that belong to the schema: 1. Select a Schema in the navigation tree. 2. Click the Materialized Views tab in the right pane, or open the Materialized Views folder. In the right pane, these attributes are displayed: Name: Name of the materialized view. Each materialized view is hyperlinked and detailed information about the materialized view is displayed. Creation Time: Time and date when the materialized view was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the materialized view was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Materialized View Groups Tab To display the materialized view groups that belong to the schema: 1. Select a Schema in the navigation tree. 2. Click the Materialized View Groups tab in the right pane, or open the Materialized View Groups folder. In the right pane, these attributes are displayed: 64 Display Database Objects

65 Views Tab Name: Name of the materialized view group. Each materialized view group is hyperlinked and detailed information about the materialized view group is displayed. Creation Time: Time and date when the materialized view group was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the materialized view group was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the views that belong to the schema: 1. Select a Schema in the navigation tree. 2. Click the Views tab in the right pane, or open the Views folder. Procedures Tab In the right pane, these attributes are displayed: Name: Name of the view. Each view is hyperlinked and detailed information about the view is displayed. Creation Time: Time and date when the view was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the view was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the procedures that belong to the schema: 1. Select a Schema in the navigation tree. 2. Click the Procedures tab in the right pane, or open the Procedures folder. Synonyms Tab DDL Tab In the right pane, these attributes are displayed: Name: Name of the procedure. Each procedure name is hyperlinked and detailed information about the procedure is displayed. Creation Time: Time and date when the procedure was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the procedure was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the synonyms that belong to the schema: 1. Select a Schema in the navigation tree. 2. Click the Synonyms tab in the right pane, or open the Synonyms folder. In the right pane, these attributes are displayed: Name: Name of the synonym. Each synonym name is hyperlinked and detailed information about the synonym is displayed. Creation Time: Time and date when the synonym was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the synonym was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the DDL output for the schema: Display Schemas and Their Objects 65

66 Privileges Tab Schema Size 1. Select a Schema in the navigation tree. 2. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). To display the privilege information for the schema: 1. Select a Schema in the navigation tree. 2. Click the Privileges tab in the right pane. The Privileges tab displays a table showing the access privileges: Grantee: The name of a role whose privilege is being described. Grantor: The name of the role that granted the privileges and the special SQL user names PUBLIC and SYSTEM. With Grant: Specifies an X to indicate if the role has grant privileges. Privileges: Describes the privilege of the role. The value is All Privileges or a list of granted privileges separated by a comma. DDL and DML privileges are grouped accordingly. For a complete list of privileges, see the GRANT SCHEMA statement information in the Neoview SQL Reference Manual. To display the size of the schema: 1. Select a Schema in the navigation tree. 2. Right-click the schema and select Show Schema Size. A separate window is displayed with the schema size. In the right pane, these attributes are displayed: Object Type: Name of the object (for example, table, table indexes, and so on). Current Size: The current size of the object. The schema size displayed is a snapshot of the schema at the timestamp shown on the top of the table display. [ Refresh ] refreshes the size information. Display Tables and Their Properties To display the table columns, primary key information, attributes, and usage information: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Under My Systems in the navigation tree, select a connected system. 4. In the navigation tree pane, expand the Tables folder, and select a table. 66 Display Database Objects

67 Columns Tab In the right pane, these tabs appear: Columns tab Primary Key tab Hash Key tab Unique Constraints tab Foreign Keys tab Attributes tab Partitions tab Usage tab DDL tab Statistics tab Privileges tab You can also expand Tables to display a table list in the left pane. Each table in the navigation tree contains a folder called Indexes and a folder called Triggers. The Indexes folder expands to show the indexes of a specified table. The Triggers folder expands to show the triggers of a specified table. To display the table columns: Display Tables and Their Properties 67

68 1. Select a Schema and table and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Columns tab in the right pane. Primary Key Tab Hash Key Tab In the right pane, these attributes are displayed: Primary Key: Specifies the icon or special symbol to indicate column is part of the primary key. Column Name: Name of the column (string). Data Type: SQL datatype of the column. Nullable: If a column is NOT NULLABLE NOT DROPPABLE, the value displayed is Not Nullable. If the column is NOT NULL, the value displayed is Not Nullable. If the column is NULL, the value is blank. Default: For schema version 2300 or earlier, the default value displayed is GENERATED BY DEFAULT AS IDENTITY. For schema version 2400, the default value displayed is GENERATED {ALWAYS BY DEFAULT} AS IDENTITY. To display the primary key column information: 1. Select a Schema in the navigation tree and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Primary Key tab in the right pane. In the right pane, these attributes are displayed: Position: The position of the column in the primary key order. Column Name: Name of the column (string). Data Type: SQL datatype of the column. Sort Order: Specifies the order as Ascending or Descending. Added By: Indicates if column was added by the System or User. To display the hash key column information: 1. Select a Schema in the navigation tree and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Hash Key tab in the right pane. In the right pane, these attributes are displayed: Position: The position of the column in the hash key order. Column Name: Name of the column (string). Sort Order: Specifies the order as Ascending or Descending. Unique Constraints Tab To display the unique constraints for the table: 1. Select a Schema in the navigation tree and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Unique Constraints tab in the right pane. In the right pane, these attributes are displayed: Constraint Name: Name of the unique constraint. Columns: The name of the columns that are constrained. 68 Display Database Objects

69 Foreign Keys Tab Attributes Tab Partitions Tab Usage Tab To display the foreign keys information on the table: 1. Select a Schema in the navigation tree and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Foreign Key tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the foreign key constraint. Foreign Table: Name of the foreign table. Local Column: Name of the local column of the foreign key. Foreign Column: Name of the foreign column of the foreign key. Enforced: Indicates if referential integrity is enforced. To display the table attributes with the attribute name and value: 1. Select a Schema in the navigation tree and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the table. Log Inserts Only: A string value of True or False. Reorganize Enabled: A string value of True or False. Update Statistics Enabled: A string value of True or False. Last Updated Statistics: The string value of Never or a timestamp of the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Maximum Size: Maximum size in megabytes to which a table can grow. If maximum size is 0, then the string Determined by system is displayed. Record Size: Row size in bytes in each logical record. Creation Time: Time and date when the table was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the table was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the table partition information: 1. Select a Schema in the navigation tree and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Partitions tab in the right pane. In the right pane, these attributes are displayed: Partition Number: The index number of the partition. Percent Allocated: The percentage full of the partition. Row Count: The current total number of rows in the partition. Max Size: The maximum size in bytes of the partition. Current EOF: The current data size of the partition in bytes. To display usage information defined on the table: Display Tables and Their Properties 69

70 DDL Tab Statistics Tab Privileges Tab 1. Select a Schema in the navigation tree and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Usage tab in the right pane. The Usage tab displays the usage relationships of the table with other objects, if any. The attributes displayed are : Relationship: Specifies the relationship of the table with the object specified. The values are: Uses, Used By, Has. Related Object Type: Specifies the object type of the related object. The values are: Table, Materialized View, View or Synonym. Related Object Name: Specifies the 2-part ANSI object name with a hyperlink to the object. Creation Time: Time and date when the table was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the table was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the DDL output for the table: 1. Select a Schema and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). To display the table profile or statistics information: 1. Select a Schema and click the table name in the right pane, or open the Tables folder and select a table name in the tree. 2. Click the Statistics tab in the right pane. The Statistics tab displays the histogram statistics for the table. For more information about displaying table statistics, see Display Table Statistics and Their Properties (page 93). To display the table privileges: 1. Select a Schema and click the table name in the right pane, or open the Tables folder and select a table in the tree. 2. Click the Privileges tab in the right pane. The Privileges tab displays a table showing the access privileges: Grantee: The name of the role whose privilege is being described. Grantor: The name of the role that granted the privileges and the special SQL user names PUBLIC and SYSTEM. With Grant: Specifies an X to indicate if the role has grant privileges. 70 Display Database Objects

71 Grant Level: The level at which the permissions are visible. The values displayed in this column are: Schema, Object, or Column. Schema indicates permissions have been applied to the schema. Object indicates permissions were applied directly to the object whose permissions are being displayed. Column indicates the permissions applied to the column. When an Object level privilege applies to all columns, the individual column privileges are not displayed, otherwise the individual column level permissions are listed. Privileges: Describes the privilege of the role. The value is All Privileges or a list of granted privileges separated by a comma. DDL and DML privileges are grouped accordingly. For a complete list of privileges, see the GRANT SCHEMA statement information in the Neoview SQL Reference Manual. Tables Summary To display a detailed summary of the table: 1. Select a Schema and right-click the Tables folder and select Show Summary Details. A separate window is displayed with a summary of the table. The table summary displays: Name: The name of the table. Statistics Last Updated: The timestamp in which the table statistics was last updated. Total Current Row Count: The total number of rows in each table. Total Maximum Size: The total maximum size of the table (in bytes). Total Current Size: The total current size of the table (in bytes). Percent Allocated: The percent full of the table. The detailed summary is a snapshot of the tables in the schema at the timestamp shown at the top of the table display. If you select [ Refresh ] the summary is refreshed. Display Table Indexes and Their Properties To display the indexes for tables, columns, and attributes: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Under My Systems in the navigation tree, select a connected system. 4. Select a Schema in the navigation tree. 5. In the navigation tree pane, expand the Indexes folder, and select an index. Display Table Indexes and Their Properties 71

72 Columns Tab Attributes Tab In the right pane, these tabs appear: Columns tab Attributes tab DDL tab Partitions tab To display the table index columns: 1. Select a Schema in the navigation tree. 2. Click the Tables folder and open the Indexes folder and select an index name. 3. Click the Columns tab in the right pane. In the right pane, these attributes are displayed: Column Name: Name of the column (string). Sort Order: Specifies the order as Ascending or Descending. Added By: Indicates if column was added by the System or User. To display the table index attributes: 72 Display Database Objects

73 DDL Tab Partitions Tab 1. Select a Schema in the navigation tree. 2. Click the Tables folder and open the Indexes folder and select an index name. 3. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the index. Unique: Specifies if the index is unique, the value is Yes or No. Populated: Specifies if the index has been populated, the value is Yes or No. Creation Time: Time and date when the table index was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the table index was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the DDL output for table indexes: 1. Select a Schema in the navigation tree. 2. Click the Tables folder and open the Indexes folder and select an index name. 3. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). To display the table index partition information: 1. Select a Schema in the navigation tree. 2. Click the Tables folder and open the Indexes folder and select an index name. 3. Click the Partitions tab in the right pane. In the right pane, these attributes are displayed: Partition Number: The index number of the partition. Percent Allocated: The percentage full of the partition. Row Count: The current total number of rows in the partition. Max Size: The maximum size in bytes of the partition. Current EOF: The current data size of the partition in bytes. Table Indexes Summary To display a detailed summary of the table indexes: 1. Select a Schema in the navigation tree. 2. Right-click the Indexes folder and select Show Summary Details. A separate window with a summary of the indexes is displayed The indexes summary displays: Name: The name of the index. Total Current Row Count: The total number of rows in each index. Total Maximum Size: The total maximum size of the index (in bytes). Total Current Size: The total current size of the index (in bytes). Percent Allocated: The percent full of the index. Display Table Indexes and Their Properties 73

74 The detailed summary is a snapshot of the indexes (tables indexes and materialized view indexes) in the schema at the timestamp shown at the top of the table display. If you select [ Refresh ] the summary is refreshed. A row is highlighted in red if the partition is equal to or greater than 80%. Display Views and Their Properties To display the view information: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Select a system in My Systems in the navigation tree. 4. Select a Schema in the navigation tree. 5. In the navigation tree pane, expand the Views folder, and select a view. Columns Tab In the right pane, these tabs appear: Columns tab Usage tab DDL tab Privileges tab To display the column information for a view: 74 Display Database Objects

75 Usage Tab DDL Tab Privileges Tab 1. Select a Schema in the navigation tree. 2. Click the Views tab, or open the Views folder and select a view. 3. Click the Columns tab in the right pane. The column information is displayed in each column. In the right pane, these usages are displayed: Column Name: Name of the column (string). Source Object: The name of the source object. If it is a computed object, this is blank. The name is hyperlinked to show that clicking on the source object name navigates you to the location of the object. Data Type: SQL datatype of the column. Nullable: If column is NOT NULL NOT DROPPABLE, the value displayed is Not Nullable. If the column is NOT NULL, the displayed value is Not Nullable. If the column is NULL, the value is blank. Default: The default of the column. To display the usage information for a view: 1. Select a Schema in the navigation tree. 2. Click the Views tab, or open the Views folder and select a view. 3. Click the Usage tab in the right pane. The usage information is displayed in each column. The Usage tab displays the usage relationships of the view with other objects, if any. The attributes displayed are: Relationship: Specifies the relationship of the view with the object specified. The values are: Uses, Used By, and Has. Related Object Type: Specifies the object type of the related object. The values are: Table, Materialized View, View, or Synonym. Related Object Name: Specifies the 2-part ANSI object name with a hyperlink to the object. Metadata UID:Unique ID of the view (a long value). Creation Time: Time and date when the related object was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local). Redefinition Time: Time and date when the related object was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local). To display the DDL output for a view: 1. Navigate to the Schema in the navigation tree. 2. Click the Views tab, or open the Views folder and select a view. 3. Click the DDL tab in the right pane. In the right pane, DDL output is displayed in the text box. For HP services, the internal format of the SHOWDDL output is displayed. For more information on the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). To display view privileges: Display Views and Their Properties 75

76 1. Select a Schema in the navigation tree. 2. Click the Views tab, or open the Views folder and select a view. 3. Click the Privileges tab in the right pane. The Privileges tab displays a table showing the access privileges. Grantee: The name of a role whose privilege is being described. Grantor: The name of the role that granted the privileges and the special SQL user names PUBLIC and SYSTEM. With Grant: Specifies an X to indicate if the role has grant privileges. Grant Level: The level at which the permissions are visible. The values displayed in this column are: Schema, Object, or Column. Schema indicates permissions have been applied to the schema. Object indicates permissions were applied directly to the object whose permissions are being displayed. Column indicates the permissions applied to the column. When an object level privilege applies to all columns, the individual column privileges are not displayed, otherwise the individual column level permissions are listed. Privileges: Describes the privilege of the role. The value is All Privileges or a list of granted privileges separated by a comma. DDL and DML privileges are grouped accordingly. For a complete list of privileges, see the GRANT SCHEMA statement information in the Neoview SQL Reference Manual. Display Materialized Views and Their Properties To display the materialized view information: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Select a system in My Systems in the navigation tree. 4. Select a Schema in the navigation tree. 5. In the navigation tree pane, expand the Materialized Views folder, and select a materialized view. 76 Display Database Objects

77 Attributes Tab In the right pane, these tabs appear: Attributes tab Partitions tab Usage tab DDL tab Privileges tab To display the materialized view attributes: 1. Navigate to the Schema in the navigation tree 2. Click the Materialized Views tab in the right pane and select a materialized view name, or open the Materialized Views folder and select a materialized view name in the tree. 3. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: External name of the materialized view. Refresh Type: Refresh policy displayed is (Recompute On Refresh On Statement). Display Materialized Views and Their Properties 77

78 Partitions Tab Recompute Derives the materialized view from scratch. This is used on the initial refresh of the materialized view and also to re-derive the materialized view if it is in an inconsistent state (for example, if the previous refresh was aborted abnormally). On Request Updates the materialized view at a time that you schedule. This allows for fast querying and a high update rate, but queries may read data that is not up-to-date with underlying tables. Select this if your application can tolerate "stale" data. On Statement Updates the materialized view immediately upon an update to the base tables. This slows the transaction speed because the materialized view refresh operation is coupled to the table update operation. Select this if your application relies on current data. Initialization Type: Initialization type displayed is (On Create On Refresh). On Create Initial entries to the materialized view are made when the view is created. A materialized view that is based on another materialized view can be initialized on create only if: The query expression does not include joins. The underlying materialized view is already initialized. On Refresh Initial entries to the materialized view are made on the first refresh after creation (default type). The materialized view is not available to select and rewrite until it has been refreshed. Refresh Commit Each: Specifies the number of rows that the refresh operation processes before committing a transaction and processing more rows. If an error occurs during the refresh, and the Refresh Commit Each attribute is set to a small number of rows, fewer rows will need to be rolled back as a result of the error. However, the smaller the value of this attribute, the greater the impact on the performance of the refresh. Refreshed At Timestamp: Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Creation Time: Time and date when the materialized view was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the materialized view was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the materialized view partitions: 1. Select a Schema in the navigation tree 2. Click the Materialized Views tab in the right pane and select a materialized view name, or open the Materialized Views folder and select a materialized view name in the tree. 3. Click the Partitions tab in the right pane. In the right pane, these attributes are displayed: Partition Number: The index number of the partition. Percent Allocated: The percentage full of the partition. Row Count: The current total number of rows in the partition. 78 Display Database Objects

79 Usage Tab DDL Tab Privileges Tab Max Size: The maximum size in bytes of the partition. Current EOF: The current data size of the partition in bytes. To display materialized view usage information: 1. Select a Schema in the navigation tree 2. Click the Materialized Views tab in the right pane and select a materialized view name, or open the Materialized Views folder and select a materialized view name in the tree. 3. Click the Usage tab in the right pane. The Usage tab displays the usage relationships of the materialized view with other objects, if any. In the right pane, these attributes are displayed: Relationship: Specifies the materialized views relationship with the object specified. The values are: Uses, Used By, and Has. Related Object Type: Specifies the object type of the related object. The values are: Table, Materialized View, View, or Synonym. Related Object Name: Specifies the 2-part ANSI object name with a hyperlink to the object. Creation Time: Time and date when the related object was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the related object was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the DDL output for the materialized view: 1. Select a Schema in the navigation tree. 2. Click the Materialized Views tab in the right pane and select a materialized view name, or open the Materialized Views folder and select a materialized view name in the tree. 3. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL SQL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). To display the privileges for the materialized view: 1. Select a Schema in the navigation tree. 2. Click the Materialized Views tab in the right pane and select a materialized view name, or open the Materialized Views folder and select a materialized view name in the tree. 3. Click the Privileges tab in the right pane. The Privileges tab displays a table showing the access privileges. Grantee: The name of a role whose privilege is being described. Grantor: The name of the role that granted the privileges and the special SQL user names PUBLIC and SYSTEM. With Grant: Specifies an X to indicate if the role has grant privileges. Grant Level: The level at which the permissions are visible. The values displayed in this column are: Schema, Object, or Column. Display Materialized Views and Their Properties 79

80 Schema indicates permissions have been applied to the schema. Object indicates permissions were applied directly to the object whose permissions are being displayed. Column indicates the permissions applied to the column. When an object level privilege applies to all columns, the individual column privileges are not displayed, otherwise the individual column level permissions are listed. Privileges: Describes the privilege of the role. The value is All Privileges or a list of granted privileges separated by a comma. DDL and DML privileges are grouped accordingly. For a complete list of privileges, see the GRANT SCHEMA statement information in the Neoview SQL Reference Manual. Materialized Views Summary To display a detailed summary of the materialized views: 1. Select a Schema and right-click the Materialized Views folder and select Show Summary Details. Clicking on Show Summary Details displays a separate window with a summary of the materialized views. The materialized views partition summary displays: Name: The name of the materialized view. Total Current Row Count: The total number of rows in each materialized view. Total Maximum Size: The total maximum size of the materialized view (in bytes). Total Current Size: The total current size of the materialized view (in bytes). Percent Allocated: The percent full of the materialized view. The detailed summary is a snapshot of the materialized view in the schema at the timestamp shown at the top of the table display. If you select [ Refresh ] the summary is refreshed. A row is highlighted in if the partition is equal to or greater than 80%. Display Materialized View Indexes and Their Properties To display the materialized view index information: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Select a system in My Systems in the navigation tree. 4. Select a Schema in the navigation tree. 5. Open the Materialized Views folder, select and open a Materialized View. 6. Open the Indexes folder and select a materialized view index in the tree. 80 Display Database Objects

81 Columns Tab Attributes Tab In the right pane, these tabs appear: Columns tab (user only) Attributes tab DDL tab Partitions tab To display the materialized view index columns: 1. Select a Schema in the navigation tree. 2. Open the Materialized Views folder, select and open a materialized view. 3. Open the Indexes folder and select a materialized view index in the tree. 4. Click the Columns tab in the right pane. In the right pane these attributes are displayed: Column Name: Name of the column (string). Sort Order: Specifies the order as Ascending or Descending. Added By: Indicates if column was added by the System or User. To display the materialized view attributes: 1. Select a Schema in the navigation tree. 2. Open the Materialized Views folder, select and open a materialized view. 3. Open the Indexes folder and select a materialized view index in the tree. 4. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Display Materialized View Indexes and Their Properties 81

82 DDL Tab Partitions Tab Name: Name of the materialized view index. Unique: Specifies if the materialized view index is unique, the value is Yes or No. Populated: Specifies if the materialized view index has been populated, the value is Yes or No. Creation Time: Time and date when the materialized view index was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the materialized view index was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display DDL output for the materialized view: 1. Select a Schema in the navigation tree. 2. Open the Materialized Views folder, select and open a Materialized View. 3. Open the Indexes folder and select a materialized view index in the tree. 4. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). To display partition information for a materialized view index: 1. Select a Schema in the navigation tree 2. Open the Materialized Views folder, select and open a Materialized View. 3. Open the Indexes folder and select a materialized view index in the tree. 4. Click the Partitions tab in the right pane. In the right pane, these attributes are displayed: Partition Number: The index number of the partition. Percent Allocated: The percentage full of the partition. Row Count: The current total number of rows in the partition. Max Size: The maximum size in bytes of the partition. Current EOF: The current data size of the partition in bytes. Materialized View Indexes Summary To display a detailed summary of the materialized view indexes: 1. Expand the Schema folder so that you can see the Materialized Views folder. 2. Expand the Materialized Views folder to display the materialized views within the folder. 3. Expand a materialized view so that you can see the Indexes folder. 4. Right-click the Indexes folder, and select Show Summary Details. The materialized views partition summary displays: Name: The name of the materialized view. Total Current Row Count: The total number of rows in each materialized view. Total Maximum Size: The total maximum size of the materialized view (in bytes). Total Current Size: The total current size of the materialized view (in bytes). Percent Allocated: The percent full of the materialized view. 82 Display Database Objects

83 The detailed summary is a snapshot of the materialized view in the schema at the timestamp shown at the top of the table display. If you select [ Refresh ] the summary is refreshed. A row is highlighted in red if the partition is equal to or greater than 80%. Display Materialized View Groups and Their Properties When you create a materialized view, a materialized view group is created automatically. It has the same name as the table that the materialized view references. To display the materialized view group information: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Select a system in My Systems in the navigation tree. 4. Select a Schema in the navigation tree. 5. Click the Materialized View Groups tab in the right pane, or open the MV Groups folder and select a materialized view group name in the tree. In the right pane, these tabs appear: Attributes tab Members tab DDL tab Display Materialized View Groups and Their Properties 83

84 Attributes Tab Members Tab DDL Tab To display the materialized view groups attributes: 1. Select a Schema in the navigation tree. 2. Click the Materialized View Groups tab in the right pane, or open the Materialized View Groups folder and select a materialized view group name in the tree. 3. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the materialized view group. Creation Time: Time and date when the materialized view was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the materialized view was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the names of the members of the materialized view group: 1. Select a Schema in the navigation tree. 2. Click the Materialized View Groups tab in the right pane, or open the Materialized View Groups folder and select a materialized view group name in the tree. 3. Click the Members tab in the right pane. In the right pane, the members are displayed in a table with the following attributes: Name: Name of the materialized view. The object names are 2-part ANSI names. Creation Time: Time and date when the materialized view was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the materialized view was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the DDL output for materialized view groups: 1. Select a Schema in the navigation tree. 2. Click the Materialized View Groups tab in the right pane, or open the Materialized View Groups folder and select a materialized view group name in the tree. 3. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). Display Procedures and Their Properties To display the procedures in a schema: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. In the navigation tree pane, select a Schema, and expand the schema so that you can see the object folders underneath it. 4. Expand the Procedures folder, and select a procedure. 84 Display Database Objects

85 Attributes Tab In the right pane, these tabs appear: Attributes tab Parameters tab Usage tab Privileges tab To display the procedure names and attributes: 1. Select a Schema in the navigation tree. 2. Click the Procedures tab in the right pane and select a procedure name, or open the Procedures folder and select a procedure name in the tree. 3. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: The name of the procedure. Dynamic Result Sets: The maximum number of result sets returned (integer). SQL Access: Specifies the way this procedure interacts with the SQL database. If the procedure does not perform SQL operations, this field displays NO SQL. Otherwise, this field displays CONTAINS SQL, MODIFIES SQL DATA, or READS SQL DATA. Signature: The parameter signature. For information on data types, see the Neoview Guide to Stored Procedures in Java. Display Procedures and Their Properties 85

86 Parameters Tab Usage Tab Privileges Tab Creation Time: Time and date when the procedure was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the procedure was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the procedure parameter information: 1. Select a Schema in the navigation tree. 2. Click the Procedures tab in the right pane and select a procedure name, or open the Procedures folder and select a procedure name in the tree. 3. Click the Parameters tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the parameter. Direction: The values displayed are: IN OUT INOUT. IN passes data to the procedure. OUT accepts data from the procedure. This is the default for array parameters. INOUT passes data to and accepts data from the procedure. SQL Data Type: Specifies an SQL data type that corresponds to the Java parameter of the procedure's Java method. For information on SQL data types, see the Neoview SQL Reference Manual. Java Data Type: Specifies a mappable Java data type. For information on Java data types, see the Neoview Guide to Stored Procedures in Java. To display the usage information for the procedure: 1. Select a Schema in the navigation tree. 2. Click the Procedures tab in the right pane and select a procedure name, or open the Procedures folder and select a procedure name in the tree. 3. Click the Usage tab in the right pane. In the right pane, these attributes are displayed: Relationship: Specifies the relationship of the procedure with the object specified. The value is References. Related Object Type: Specifies the object type of the object that the procedure references. The values are: Table, Materialized View, or View. Related Object Name: Specifies the two-part ANSI object name with a hyperlink to the object. Creation Time: Time and date when the procedure was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the procedure was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the privileges for the procedure: 86 Display Database Objects

87 1. Select a Schema in the navigation tree. 2. Click the Procedures tab in the right pane and select a procedure name, or open the Procedures folder and select a procedure name in the tree. 3. Click the Privileges tab in the right pane. The Privileges tab displays a table showing the access privileges. Grantee: The name of a role whose privilege is being described. Grantor: The name of the role that granted the privileges and the special SQL user names PUBLIC and SYSTEM. With Grant: Specifies an X to indicate if the role has grant privileges. Grant Level: The level at which the permissions are visible. The values displayed in this column are: Schema, Object, or Column. Schema indicates permissions have been applied to the schema. Object indicates permissions were applied directly to the object whose permissions are being displayed. Column indicates the permissions applied to the column. When an object level privilege applies to all columns, the individual column privileges are not displayed, otherwise the individual column level permissions are listed. Privileges: Describes the privilege of the role. The value is All Privileges or a list of granted privileges separated by a comma. DDL and DML privileges are grouped accordingly. For a complete list of privileges, see the GRANT SCHEMA statement information in the Neoview SQL Reference Manual. Display Synonyms and Their Properties To display the synonym names in the schema: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Select a system in My Systems in the navigation tree. 4. Select a Schema in the navigation tree. 5. In the navigation tree pane, expand the Synonyms folder, and select a synonym. Display Synonyms and Their Properties 87

88 Attributes Tab In the right pane, these tabs appear: Attributes tab Usage tab DDL tab To display the synonym names and attributes: 1. Select a Schema in the navigation tree. 2. Click the Synonyms tab in the right pane and select a synonym name, or open the Synonyms folder and select a synonym name in the tree. 3. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the synonym. Creation Time: Time and date when the related object was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the related object was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). 88 Display Database Objects

89 Usage Tab DDL Tab To display the synonym usage information: 1. Select a Schema in the navigation tree. 2. Click the Synonyms tab in the right pane and select a synonym name, or open the Synonyms folder and select a synonym name in the tree. 3. Click the Usage tab in the right pane. The Usage tab displays the usage relationships of the synonym with other objects, if any. These attributes displayed are: Relationship: Specifies the relationship of the synonym with the object specified. The value is References. Related Object Type: Specifies the object type of the object that the synonym references. The values are: Table, Materialized View, or View. Related Object Name: Specifies the 2-part ANSI object name with a hyperlink to the object. Creation Time: Time and date when the synonym was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the synonym was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the DDL output for the synonym: 1. Select a Schema in the navigation tree. 2. Click the Synonyms tab in the right pane and select a synonym name, or open the Synonyms folder and select a synonym name in the tree. 3. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). Display Triggers and Their Properties A trigger is a mechanism that resides in the database and specifies that when a particular action an insert, delete, or update occurs on a table, SQL should automatically perform one or more additional actions. To display the triggers: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Select a system in My Systems in the navigation tree. 4. In the navigation tree pane, expand the Triggers folder, and select a trigger. Display Triggers and Their Properties 89

90 Attributes Tab In the right pane, these tabs appear: Attributes tab Usage tab DDL tab To display the trigger attributes: 1. Select a Schema in the navigation tree. 2. Click the table name in the right pane, and then open the Triggers folder and select a trigger in the tree. 3. Click the Attributes tab in the right pane. In the right pane, these attributes are displayed: Name: Name of the trigger. Metadata UID: Unique ID of the trigger (a long value). Is Enabled: Specifies if the trigger is enabled. The value is 'Yes or 'No. Activation Time: Specifies when the trigger is activated. Used in combination with an operation. The value is Before or After. Operation: Specifies operation that causes the trigger to be activated. The values are (Insert Delete Update). Granularity: Specifies Row or Statement trigger. Row triggers are allowed for all Time/Event combinations. Statement triggers are allowed AFTER events. For more information, see the Neoview SQL Reference Manual. 90 Display Database Objects

91 Usage Tab DDL Tab Creation Time: Time and date when the trigger was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time: Time and date when the trigger was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). To display the trigger usage information: 1. Select a Schema in the navigation tree and click the table name in the right pane, and then open the Triggers folder and select a trigger in the tree. 2. Click the Usage tab in the right pane. In the right pane, these attributes are displayed: Relationship: Specifies the relationship between this trigger and the object. Related Object Type: Specifies the object type of the object. Related Object Name: Specifies the object name with a hyperlink to the object. Creation Time: Time and date when the related object was created. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Redefinition Time:Time and date when the related object was last redefined. Timestamp is in the format (yyyy-mm-dd HH:mm:ss.FFFFFF local time). Operation: Specifies what types of the operation performed on this object to activate the trigger. The value is one of the (Delete/Insert/Select/Update/Call). Is Subject Table: Specifies whether the target is a subject table. The value is True or False. To display the DDL output for the trigger: 1. Select a Schema in the navigation tree. 2. Click the table name in the right pane, and then open the Triggers folder and select a trigger in the tree. 3. Click the DDL tab in the right pane. The DDL tab displays DDL output from the SHOWDDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. For more information about the format of the SHOWDDL command, see the Neoview SQL Reference Manual. For more information about displaying DDL, see Display Schema DDL and Their Properties (page 91). Display Schema DDL and Their Properties To display schema DDL information, a DDL tab appears in the right pane when these objects are selected in the navigation tree: Schema Table Table Index View Materialized View Materialized View Index Materialized View Group Procedure Display Schema DDL and Their Properties 91

92 DDL Tab Show DDL Synonym Trigger The DDL tab displays DDL output from the Show DDL command in the right pane. You can highlight and copy contents, but you cannot edit the contents. The external format of the Show DDL output is displayed. For more information on the format of the Show DDL command, see the Neoview SQL Reference Manual. Show DDL allows you to select objects for which you want DDL output fetched and displayed. NOTE: Opening up Show DDL to the system-level allowing you to select different catalogs and schemas and their objects may cause performance issues. To avoid performance issues, Show DDL limits the selection to a specific schema. Select a node in the navigation tree, right-click the Show DDL menu and the Show DDL dialog box appears. The Show DDL menu is available only for a schema node and its child nodes in the navigation tree. The Show DDL menu is not available for catalogs folder or the catalog and schemas folder. In the Show DDL dialog box, the Select Objects pane displays a Selection Tree that displays a navigation tree. The Selection Tree has check boxes in front of the node names and you can select or deselect specific objects. If the Show DDL dialog box is invoked on a folder node in the main navigation tree, the Select Objects pane displays (by default) the selection tree with the corresponding folder node and all its child nodes with check boxes selected. If the Show DDL dialog box is invoked on a leaf node in the main navigation tree, the Select Objects pane displays (by default) the selection tree with the corresponding leaf node s check box selected. The option to select more objects or uncheck selected objects is always available. Objects can be selected from only one schema. If objects are selected from a different schema, an error message is displayed. 92 Display Database Objects

93 The DDL Output pane has a text box with scroll bars and the DDL output is displayed in the text box. The Show DDL dialog box options are: Button [ Load ] [ Append ] [ Clear All ] [ Save ] [ Clear ] [ Done ] Description Loads the Show DDL output of the selected objects (with check boxes selected) and replaces the contents in the DDL Output pane. Appends the selected objects to the existing contents in the DDL Output pane. Clears selected objects (with check boxes selected) in the Selected Objects pane. Saves the contents of the DDL Output text box using the File menu dialog box. Clears the DDL Output text box. Closes the Show DDL dialog box. Display Table Statistics and Their Properties HPDM allows you to display table profile or statistics information. The table profile or statistics information can be used to troubleshoot problem queries or to create additional indexes for help with query performance. Display Table Column Statistics To display table profile or statistics information: 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. Display Table Statistics and Their Properties 93

94 3. Select a Schema in the navigation tree. 4. Click the Statistics tab in the right pane. The Statistics tab displays the histogram statistics for the table. For each column in the table, the data is fetched from the HISTOGRAMS UMD table. The right pane displays these attributes: Name: Name of the column. Datatype: Specifies the column datatype. # Nulls: The number of null values for the column. An interval (bucket) with "(NULL) as the boundary value from the histogram_intervals table. Min Value: The Low_Value from histograms table for this column. Max Value: The High_Value the histograms table for this column. Skew: CV from histograms table for this column for schema version For older schema versions, the value is 0. UEC: Total_UECs from histograms table for this column. Column Cardinality: Rowcount from histograms table for this column. Last Stats Timestamp: The STATS_TIME from histogram table for this column. Viewing Sampled Statistics To display a sample view of the table column statistics, click on the hyperlink on the column name, or double-click any row in the right pane, or use the Sample Column Statistics button located at the top right pane. 1. Start the HP Database Manager and log on using any user ID. 2. Click the Database area. 3. Select a Schema in the navigation tree. 4. Click the Statistics tab in the right pane. 5. Click the hyperlink on the column name, or double-click on any row in the right pane, or use the View Sampled Statistics button located at the top of the right pane. The header displays the column name, the sampled percent, and the table name. The attributes displayed are: Column Name: Name of the column. Data Type: Displays the column datatype. # Nulls: The number of null values for the column. An interval (bucket) with "(NULL) as the boundary value from the histogram_intervals table. Skew: CV from histograms table for this column for schema version For older schema versions, the value is 0. The middle pane displays: Values: Displays the top 10 frequent values for the column. Cardinality: Rowcount from histograms table for this column. The bottom pane displays the histogram intervals for the column data boundaries. For each boundary it displays the data from the stats table and the result from the sample. The pane displays a side-by-side comparison of the histogram data to the sampled data. Interval Number: Name of the column. Min Boundary: The minimum value of the histograms table for this column. Max Boundary: The maximum value of the histograms table for this column. Stats UEC: The total UEC from histograms table of this column. Sampled UEC: The sampled_uec from histograms table for this column Stats Cardinality: The STATS_TIME from histogram table for this column. Sampled Cardinality: The sampled_uec from histograms table for this column. 94 Display Database Objects

95 7 Manage Roles About Roles A role is a vehicle for assigning data-access privileges to user IDs. On the Neoview platform, data-access privileges are not granted to individual users. Users are granted a role, and roles are granted privileges on database objects. In this way, all the users who are granted a role are granted the privileges associated with the role. The Neoview platform can have a maximum of 255 roles. Many users can be assigned to the same Neoview role. It is also possible for the same user to be assigned to multiple roles. If you have sufficient privileges, you can use HPDM or a set of commands in the Neoview Command Interface (NCI) to create, associate, and manage Neoview users and roles. For more information about users and roles, see the Neoview User Management and Security Administration Guide. Display All Roles (page 95) Display the Users Who Belong to a Role (page 96) Add a Role (page 97) Delete a Role (page 98) Change the Password or Expiration for a Role (page 100) Terms role power role Display All Roles Only a user belonging to the ROLE.MGR role can display all the roles. To display the list of roles: 1. Log on as a user belonging to the ROLE.MGR role. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles, including: Grant Count Default Role Count Created By Create Time The number of users assigned to the role. The number of users for whom the role is their default role. The owner of the role. The date and time when the role was created. This table describes the toolbar icons on the Roles screen: Button Name Stop data provider Description Stops the refresh. Refresh data Updates the display with the latest information from the server. For information about the following buttons, see Export Data (page 53): [ Data to Clipboard ] [ Data to Browser ] About Roles 95

96 [ Data to Spreadsheet ] [ Data to File ] Display the Users Who Belong to a Role (page 96) Add a Role (page 97) Grant a Role to a User (page 98) Export Data (page 53) Display the Users Who Belong to a Role Only a user belonging to the ROLE.MGR role can display the users who belong to a role. To display detailed information about a specific role or multiple roles, including all users associated with a role: 1. Log on as a user belonging to the ROLE.MGR role. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles. 4. Double-click the role for which you want detailed information. Or right-click the role, and select View Role Details. HPDM displays the Role Details dialog box, including all users belonging to the role. 5. If you are a power user, click the down arrow for the Role Name field to display a list of all roles. Power users can view detailed information about any role. Non-power users can view only information about their own role (the down arrow is not provided). About Roles (page 95) Display All Roles (page 95) Display the SQL Privileges for a Role (page 96) Terms power user Display All the Roles for a User To display all of the roles to which a user belongs, use one of these procedures: Display All Database Users (page 103) Display All Platform Users (page 111) NOTE: role. Database users can belong to multiple roles. Platform users can belong to only one Display the SQL Privileges for a Role Only a user belonging to the ROLE.MGR role can display the SQL privileges for a role. SQL privileges are granted to a role by using the GRANT statement. For more information about the GRANT statement, see the Neoview SQL Reference Manual. To display the SQL privileges for a role 1. Log on as a user belonging to the ROLE.MGR or SUPER.SUPER role. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles. 4. Double-click the role for which you want to view SQL privileges. Or right-click the role, and select View Role Details. HPDM displays the Role Details dialog box. 96 Manage Roles

97 Add a Role 5. Click [ View SQL Privileges ]. The SQL Privileges dialog box appears, displaying the following privilege information for the selected role: SCHEMA NAME OBJECT NAME OBJECT TYPE GRANTED BY PRIVILEGE TYPE COLUMN NAME NOTE: The PRIVILEGE TYPE column indicates whether the privilege is a schema privilege or a column privilege. For a column privilege, the COLUMN NAME column displays Update or Reference as the privilege. Before adding a role, review these considerations: To add a new role, you must be a user in the role of ROLE.MGR. You must precede the role name with the ROLE. prefix. The part of the role name that follows the prefix consists of 1 to 8 alphanumeric characters, the first of which may not be a number. The alphabetic characters in role names are not case-sensitive. HPDM allows you to add multiple roles separated by a comma. The Neoview platform supports a maximum of 255 roles, but three of these roles (ROLE.MGR, ROLE.DBA, and ROLE.SECMGR) are reserved, so you can create a maximum of 252 new roles. (You cannot use the name of an existing role when adding a new role.) The role(s) that you add using the Add Role(s) dialog box do not have passwords or password-expiration criteria. Only the preconfigured roles have passwords. To add a role or multiple roles: 1. Log on as a user belonging to ROLE.MGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles. 4. Use one of these methods to display the Add Role(s) dialog box: In the right pane, click [ Add ]. In the navigation tree pane, right-click the Roles folder, and select Add Role. 5. In the Add Role(s) dialog box, type the name of a role, or type multiple role names separated by commas: Example of Single Role Name ROLE.ITDBA Example of Multiple Role Names Separated by Commas ROLE.ITOPS, ROLE.SARA, ROLE.BOSTON4 6. Click [ OK ] to add the role(s). The right pane displays the new roles momentarily. About Roles (page 95) Display the Users Who Belong to a Role (page 96) Grant a Role to a User (page 98) Add a Role 97

98 Delete a Role (page 98) Terms role power role Delete a Role Before deleting a role, review these considerations: To delete a role, you must be a user in the ROLE.MGR role. Before deleting a role, you must revoke the role from any user who has it, and also revoke any database privileges that have been assigned to the role. To revoke a role from a user, see Revoke a Role From a User (page 99). To revoke privileges from a role, see the information about the REVOKE statement in the Neoview SQL Reference Manual. You may not delete: A role that is currently granted to one or more users. A role that has database permissions currently granted to it. The power roles: SUPER.SUPER, ROLE.MGR, ROLE.SECMGR, and ROLE.DBA. To delete a role or multiple roles: 1. Log on as a user belonging to ROLE.MGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles. 4. In the right pane, select the role(s) that you want to delete. To select more than one role, hold down the Ctrl key on your keyboard while selecting the role. 5. Click [ Delete ]. A confirmation box asks you to confirm the operation. Click [ Yes ] to delete the role(s). The roles are removed from the right pane momentarily. About Roles (page 95) Add a Role (page 97) Display the Users Who Belong to a Role (page 96) Revoke a Role From a User (page 99) Terms role power role Grant a Role to a User You must be a user in the ROLE.MGR role to grant a role to a user using this procedure. You can use this procedure to grant a role to one or many users. The role that is granted is an additional role. This procedure has no effect on the current default role of a user. To change the current default role, see Change Role or Password Information for a Database User (page 109) or Change Your Own Default Role (page 111). NOTE: If you have sufficient privileges, you can also grant an additional role to a user by editing the user definition. See Change Role or Password Information for a Database User (page 109) or Edit a Platform User (page 114). The predefined users USERMGR and SECURITYMGR are limited to the roles ROLE.MGR and ROLE.SECMGR, respectively. Neither of these predefined users can be granted additional roles. To grant an additional role to one or many users: 1. Log on as a user in the ROLE.MGR role. For more information about logging on, see Connect to a System (page 25). 98 Manage Roles

99 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles. 4. Double-click the role that you want to grant to another user. Or right-click the role, and select View Role Details. HPDM displays the Role Details dialog box, including all users belonging to the role. 5. Click [ Grant ]. The Grant Role dialog box appears, showing a list of users who do not yet belong to the selected role. 6. Fill in the fields in the Grant Role dialog box, and click [ Grant ]. For more information, see Use the Grant Role Dialog Box (page 99). Use the Grant Role Dialog Box (page 99) Terms role Use the Grant Role Dialog Box This table describes the fields in the Grant Role dialog box: Field Role Name Type User Name or Select From List Users [ Additional Users ] Description Displays the role to be granted during the grant operation. If you are a member of a power role, a down arrow is provided. You can use the down arrow to select a different role. Type a user name and press Enter on your keyboard to find a user in the list. Select a user, or hold down the Ctrl key on your keyboard and select multiple users to be granted the role. Click [ Additional Users ] to move the selected user(s) into the Selected Users field. Grant a Role to a User (page 98) Terms role power role Revoke a Role From a User Note these considerations for revoking a role: Generally, you must be a user in the ROLE.MGR role to revoke a role from a user using this procedure. However, a user in the role of ROLE.SECMGR can revoke the ROLE.SECMGR role from another user. If you revoke a secondary role, the role is removed. The primary, or default, role is unchanged. If you revoke a user's default role and the user has no additional roles, the user is removed from the system. If you try to revoke a user's default role and the user has additional roles, an error is returned. In this case, you must first change the default role to one of the user's additional roles and then retry revoking the former default role. NOTE: If you have sufficient privileges, you can also revoke a role from a user by editing the user definition. See Change Role or Password Information for a Database User (page 109) or Edit a Platform User (page 114). To revoke a role: Use the Grant Role Dialog Box 99

100 1. Log on as a user in the ROLE.MGR role. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles. 4. Double-click the role that you want to revoke from one or more users. Or right-click the role, and select View Role Details. HPDM displays the Role Details dialog box, including all users belonging to the role. 5. Select a user, or hold down the Ctrl key on your keyboard and select multiple users for whom membership in the specified role will be revoked. 6. Click [ Revoke ]. Grant a Role to a User (page 98) Terms role power role Change the Password or Expiration for a Role Depending on the user ID that you use to connect to a Neoview system, HPDM determines if you have the privileges to change the password or expiration information for a role. If you have insufficient privileges, the [ Change Password ] button is not active. Note that even if you have sufficient privileges, you can only change the password or expiration information for the predefined roles: Role ROLE.MGR ROLE.DBA ROLE.SECMGR SUPER.SUPER SUPER.SERVICES HP.VTS HP.SDI Database or Platform Role Database Database Database Platform Platform Platform Platform Role Required to Change the Password or Password Expiration ROLE.MGR ROLE.MGR ROLE.SECMGR ROLE.SECMGR SUPER.SERVICES SUPER.SERVICES SUPER.SERVICES An error message is generated if you try to make password changes to other roles. A user who can change the password for a role can also change the password-expiration attributes, but HP recommends against changing the password expiration. By default, the passwords of predefined roles do not expire. Whether a user ever needs to enter the role password in order to log on is determined by the security policy. See Use the Power Role Management Tab for Security Policies (page 122). To change the password or expiration settings for a role: 1. Log on as a user belonging to a role that can change the password for another role (see the preceding table). For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Roles folder. The right pane shows the list of roles. 4. In the right pane, select a role. 5. Click [ Change Password ]. The Change Role Password dialog box appears. 100 Manage Roles

101 NOTE: The [ Change Password ] button is active only if you have sufficient privileges to change the password for the selected role. 6. Fill in the fields in the dialog box, and click [ OK ]. For more information about the dialog box fields, see Use the Change Role Password Dialog Box (page 101). Use the Change Role Password Dialog Box (page 101) Terms power role Use the Change Role Password Dialog Box This table describes the fields in the Change Role Password dialog box: Field Role Name Old Password New Password Confirm New Password No Expiration Use Expiration Expires Every n Days Expiry Date date Description Shows the name of the selected role. Type the current password. This field is enabled only if the security policy for the system requires it. Type the new password. The password can consist of a maximum of 53 characters if you use 1024-bit encryption, or 64 characters if you use 2048-bit encryption. Type the exact same password as you typed in the New Password field. Select this option to set a password that does not expire. HP recommends that role passwords have no expiration. Select this option to configure an expiration interval (Expires Every n Days) or date (Expiry Date date) for the password. Enter the number of days, from the time the password is changed, after which it expires. Any integer value is valid. Enter the date on which the password expires. To enable the date field, click the check box to the left of the date. Then specify a date. If you do not click the check box, the Expiry Date field is disabled. Change the Password or Expiration for a Role (page 100) Use the Change Role Password Dialog Box 101

102 102

103 8 Manage Users and Passwords About Users The Neoview platform has several different types of users: database user A person or application that can use a Neoview client, such as ODBC, NCI, or HDPM, to log on to the Neoview database and operate on database objects. A database user can have one or more database roles (each having a name of the form ROLE.name), which determine the objects to which the user has access and the privileges the user has in relation to those objects. There are two types of database user: locally authenticated remotely authenticated A database user whose credentials (name and password) are maintained and validated on the Neoview platform. Such a user can log on even if no external directory server is running. A database user whose credentials (name and password) are maintained and validated on an external LDAP or Active Directory server. Such a user can log on only if the external directory server is running. Remotely authenticated database users must be registered on the Neoview platform and assigned Neoview database roles. platform user A person or program that has access to special tools used primarily for Neoview maintenance and troubleshooting. A platform user has exactly one platform role (with a name of the form HP.name, SUPER.name, or NEOVIEW.name), which determines the privileges that pertain to the user. Platform users can also log on to database interfaces, but have little or no access to data. For example, users in the role SUPER.SERVICES have no access to customer data, and HP.VTS can be used only by the Virtual Tape Subsystem. For more information about users, see the Neoview User Management and Security Administration Guide. Display All Database Users (page 103) Display All Platform Users (page 111) About Roles (page 95) Terms database user platform user locally authenticated database user remotely authenticated database user Database Users Display All Database Users You must be a user in the role of ROLE.MGR or ROLE.SECMGR to display all database users. To display all database users: 1. Log on as a user belonging to ROLE.MGR or ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). About Users 103

104 3. In the navigation tree pane, expand the folder for the logged on system, and select the Database Users folder. The right pane displays all database users, including this information about each user: User name Default role Additional roles Role that created the user User type (locally authenticated or remotely authenticated) NOTE: You can sort the user information by clicking a column heading. For example, to display all the database users belonging to a specific role, click the Default Role column heading. To sort the list of database users by remotely authenticated or locally authenticated users, click the User Type column heading. For more information, see Work With Data Grids (page 48). About Users (page 103) Add a Database User (page 104) Change Role or Password Information for a Database User (page 109) Delete One or More Database Users (page 111) Terms role database user locally authenticated database user remotely authenticated database user Add a Database User In general, a user belonging to the ROLE.MGR role adds all other users. However, only a user logged on in the role of ROLE.SECMGR can add another user in the ROLE.SECMGR role. Furthermore, ROLE.SECMGR is the only role that a user logged on as ROLE.SECMGR may assign. All other role assignments must be performed by a ROLE.MGR user. To add a database user: 1. If you are adding a remotely authenticated database user, make sure that the user you want to add is already configured on the LDAP server. An error message is generated if the user is not present in the LDAP server. 2. Log on as a user belonging to ROLE.MGR or ROLE.SECMGR. 3. Select the Security area. For information about how to select an area, Select an Area (page 35). 4. In the navigation tree pane, expand the folder for the logged on system, and select the Database Users folder. The right pane displays all database users. 5. Use one of these methods to display the Add Database User dialog box: In the navigation tree pane, right-click the Database Users folder, and select Add Database User. In the right pane, click [ Add ]. 6. Fill in the fields of the Add Database User dialog box. For more information about each field, see Use the Add Database User Dialog Box (page 105). 7. Click [ OK ]. Use the Add Database User Dialog Box (page 105) Add Multiple Database Users (page 106) Terms 104 Manage Users and Passwords

105 database user remotely authenticated database user Use the Add Database User Dialog Box This table describes the fields in the Add Database User dialog box: Group Box Role Password Password Expiration Policy Field/Option User Name [ Default Role ] [ Additional Roles ] Locally Authenticated User Password Confirm Password No Expiration Use Expiration Expires Every n Days Expiry Date date Description The name of a database user. This is the name that the user must enter when logging on to the Neoview platform. The name can consist of up to 128 characters, potentially including a domain name and a separator character (for example, elspeth.jordan@welt.com). Commas are not allowed. The user name is not case-sensitive. The default role is the role that the system associates with the user when no other role is specified. Click the down arrow to select from a list of configured roles. If the role you want to select does not exist, see Add a Role (page 97). Or click [ Default Role ] to display the Select User Role dialog box. For more information, see Use the Select User Role Dialog Box (page 106). Additional roles are roles to which the user belongs in addition to the default role. Click [ Additional Roles ] to display the Select User Role dialog box. For more information, see Use the Select User Role Dialog Box (page 106). Select this option to configure the password and password expiration setting for locally authenticated users. (Passwords for remotely authenticated users are configured on an LDAP server.) NOTE: You can control the default value of this option and thereby customize the display of the Add Database User dialog box by changing the value of a security option. See Control the Display of the Add Database User Dialog Box (page 108). The password to be assigned to the locally authenticated user. This password must comply with the password quality criteria specified in the current system security policy (see Use the Password Tab for Security Policies (page 120)). For information about the default password settings for locally authenticated database users, see the Neoview User Management and Security Administration Guide. Range: A maximum of 53 characters if you use 1024-bit encryption, or 64 characters if you use 2048-bit encryption. Type the password again to confirm it. Select this option to specify that the password never expires. Select this option to specify that the password expires on the schedule indicated by Expires Every n Days and Expiry Date date. The interval that controls password expiration. This is the number of days, from the time the password is changed, after which it expires. Range: The default password expiration date, if no other date is specified when the user is created. To enable the date field, click the check box to the left of the date. Then specify a date. If you do not click the check box, the Expiry Date field is disabled. Range: April 24, 2007 to Dec 31, 2999 Add a Database User (page 104) Database Users 105

106 Use the Select User Role Dialog Box (page 106) Control the Display of the Add Database User Dialog Box (page 108) Terms role locally authenticated database user Use the Select User Role Dialog Box The Select User Role dialog box helps you search for and specify a role (or multiple roles) when you add or edit users. This table describes the fields in the Select User Role dialog box: Group Box Roles Selected Roles Field/Option Type Role Name or Select From List [ Default Role ] [ Additional Roles ] Description Type a role name and press Enter on your keyboard to find a role in the list of roles. Select a role to specify as a default role, or hold down the Ctrl key on your keyboard and select multiple roles that you want to designate as additional roles. Click [ Default Role ] to move the selected role into the Default Role field. Click [ Additional Roles ] to move the selected role(s) into the Additional Roles field. Add a Database User (page 104) Change Role or Password Information for a Database User (page 109) Use the Add Database User Dialog Box (page 105) Terms role locally authenticated database user Add Multiple Database Users Use this procedure to add multiple remotely authenticated database users. You cannot use this procedure to add locally authenticated database users because you must specify password information for locally authenticated users. Therefore, you must add locally authenticated users one at a time. In general, a user belonging to the ROLE.MGR role adds all other users. However, only a user logged on in the role of ROLE.SECMGR can add another user in the ROLE.SECMGR role. Furthermore, ROLE.SECMGR is the only role that a user logged on as ROLE.SECMGR may assign. All other role assignments must be performed by a ROLE.MGR user. To add multiple database users: 1. Make sure that any remotely authenticated database users that you want to add are already configured on the LDAP server. An error message is generated if the users aren't present in the LDAP server. 2. Log on as a user belonging to ROLE.MGR or ROLE.SECMGR. 3. Select the Security area. For information about how to select an area, Select an Area (page 35). 4. In the navigation tree pane, expand the folder for the logged on system, and select the Database Users folder. The right pane displays all database users. 5. In the navigation tree pane, right-click the Database Users folder, and select Add Multiple Database Users. The Add Multiple Database Users dialog box appears. 6. Fill in the fields of the Add Multiple Database Users dialog box. For more information about each field, see Use the Add Multiple Database Users Dialog Box (page 107). 106 Manage Users and Passwords

107 7. Click [ OK ]. About Users (page 103) Add a Database User (page 104) Use the Add Multiple Database Users Dialog Box (page 107) Terms database user locally authenticated database user remotely authenticated database user Use the Add Multiple Database Users Dialog Box This table describes the fields in the Add Multiple Database Users dialog box: Group Box Role Field User Names [ Default Role ] [ Additional Roles ] Description The names of the database users that you want to add. For each new user, this is the name that the user must enter when logging on to the Neoview platform. Each name can consist of up to 128 characters and is not case sensitive. Separate each name with a comma. The default role is the role that the system associates with the users when no other role is specified. Click the down arrow to select from a list of configured roles. If the role you want to select does not exist, see Add a Role (page 97). Or click [ Default Role ] to display the Select User Role dialog box. For more information, see Use the Select User Role Dialog Box (page 106). Secondary roles are roles to which the user belongs in addition to the default role. Click [ Additional Roles ] to display the Select User Role dialog box. For more information, see Use the Select User Role Dialog Box (page 106). Add Multiple Database Users (page 106) Add a Database User (page 104) Terms database user locally authenticated database user Copy a Database User If you have many users to create and these users share similar characteristics, you can save time in creating them by copying the characteristics of an already configured user. You can do this by using the [ Add Like ] button on the list of database users. NOTE: Using the [ Add Like ] button, you can create only one user at a time. If you want to create multiple users having the same role and password characteristics, see Add Multiple Database Users (page 106). The same rules for creating a database user apply to copying a database user. In general, a user belonging to the ROLE.MGR role creates all other users. However, only a user logged on in the role of ROLE.SECMGR can add another user in the ROLE.SECMGR role. Furthermore, ROLE.SECMGR is the only role that a user logged on as ROLE.SECMGR may assign. All other role assignments must be performed by a ROLE.MGR user. To copy an already configured database user: 1. Log on as a user belonging to ROLE.MGR or ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). Database Users 107

108 3. In the navigation tree pane, expand the folder for the logged on system, and select the Database Users folder. The right pane displays all database users. 4. In the right pane, select a user. 5. In the right pane, click [ Add Like ]. The Add Database User Like dialog box appears. NOTE: The Add Database User Like dialog box is similar to the Add Database User dialog box. 6. Fill in the fields in the Add Database User Like dialog box. For more information about each field, see Use the Add Database User Dialog Box (page 105). 7. Click [ OK ]. About Users (page 103) Add a Database User (page 104) Add Multiple Database Users (page 106) Terms database user Control the Display of the Add Database User Dialog Box By default, HPDM displays the Add Database User dialog box with the Locally Authenticated User option selected, allowing you to specify the configuration for both locally and remotely authenticated users. However, you can control the default presentation of the dialog box. If your installation has few locally authenticated users, it can be useful to configure the dialog box to default to the remotely authenticated user presentation. NOTE: This option does not influence the display of the Add Multiple Database Users dialog box. The Add Multiple Database Users dialog box can only be used to add remotely authenticated database users. For more information, see Add Multiple Database Users (page 106). To change the default display setting for the Add Database User Dialog Box: NOTE: You do not need to connect to a system to perform this procedure. 1. Click the Options button ( ) on the HPDM toolbar, or select Tools > Options. The Options dialog box appears. 2. In the left pane of the Options dialog box, click Security. The right pane displays the Security Options. 3. Click the DefaultAddDatabaseUserLocally option to select it. A down arrow appears to the right of the option row. 4. Click the down arrow to change the option value: Value True False Description The Locally Authenticated User option is selected, and the Add Database User dialog box displays all fields for configuring locally and remotely authenticated users. The Locally Authenticated User option is deselected, and the Add Database User dialog box displays only the fields for configuring remotely authenticated users. Add a Database User (page 104) Use the Add Database User Dialog Box (page 105) Terms locally authenticated database user 108 Manage Users and Passwords

109 remotely authenticated database user Change Role or Password Information for a Database User Editing a database user allows you to change the default role, add additional roles, change the password, or configure a different password expiration date for the selected user. You can edit only one user at a time. You must be a user in the role of ROLE.MGR or ROLE.SECMGR to edit a database user. Only a ROLE.SECMGR user can change the password of a user who has only the ROLE.SECMGR role. To edit a database user: 1. Log on as a user belonging to ROLE.MGR or ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). 3. In the navigation tree pane, expand the folder for the logged on system, and select the Database Users folder. The right pane displays all database users. 4. In the right pane, select a user to edit. 5. Click [ Edit ], or double-click the user row. The Edit User dialog box appears. 6. Fill in the fields of the Edit User dialog box. For more information about each field, see Use the Edit User Dialog Box (page 109). 7. Click [ OK ]. Use the Edit User Dialog Box (page 109) Change Your Own Password After Logon (page 116) Terms database user locally authenticated database user Use the Edit User Dialog Box This table describes the fields in the Edit User dialog box: Database Users 109

110 NOTE: If the selected database user is remotely authenticated, a truncated version of the dialog box is displayed, showing only the User Name, Default Role, and Additional Roles fields. The password fields are not applicable to remotely authenticated database users. Group Box Role Password Password Expiration Policy Field/Option User Name [ Default Role ] [ Additional Roles ] Password Confirm Password No Expiration Use Expiration Expires Every n Days Expiry Date date Description The name of the selected database user. The name cannot be edited. However, if you need to change the user name, you can copy the user definition and assign a new name to the copied user definition. See Copy a Database User (page 107). The current default role of the selected database user. The default role is the role that the system associates with the user when no other role is specified. You can change the default role only to an additional role to which the user already belongs. Click the down arrow to select from a list of additional roles. If the role that you want to select is not present in the list, you might have to add it first by using the [ Additional Roles ] button. NOTE: Another way to change the default role is to click the [ Change Default Role ] button in the sign-on user info screen in the right pane. See Change Your Own Default Role (page 111). Additional roles are roles to which the user belongs in addition to the default role. Click [ Additional Roles ] to display the Select User Role dialog box and add additional roles. For more information, see Use the Select User Role Dialog Box (page 106). To revoke an additional role, delete the role from the list of additional roles. The password to be assigned to the locally authenticated user. To change the password, type a new password in this field. This password must comply with the password quality criteria specified in the current system security policy (see Use the Password Tab for Security Policies (page 120)). Type the password for a second time to confirm it. Click this option to specify that the password never expires. Click this option to specify that the password expires on the schedule indicated by Expires Every n Days and Expiry Date date. The interval that controls password expiration. This is the number of days, from the time the password is changed, after which it expires. Range: The default password expiration date, if no other date is specified when the user is created. To enable the date field, click the check box to the left of the date. Then specify a date. If you do not click the check box, the Expiry Date field is disabled. Range: April 24, 2007 to Dec 31, 2999 Change Role or Password Information for a Database User (page 109) Change Your Own Password at Logon (page 115) Change Your Own Password After Logon (page 116) Change Your Own Default Role (page 111) Terms database user role 110 Manage Users and Passwords

111 Delete One or More Database Users You must be a user in the role of ROLE.MGR to delete a database user. Note that this action does not delete a remotely authenticated database user from an external directory server. To delete one or more database users: 1. Log on as a user belonging to ROLE.MGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). 3. In the navigation tree pane, expand the folder for the logged on system, and select the Database Users folder. The right pane displays all database users. 4. In the right pane, select a user, or hold down the Ctrl key and select multiple users. 5. Click [ Delete ]. A confirmation dialog box appears. 6. Click [ OK ]. Delete One or More Platform Users (page 115) Add a Database User (page 104) Terms database user Change Your Own Default Role You can change your own default role, but you can only select as the new default role a role to which you already belong. For example, if your default role is ROLE.DBA and the only other role to which you belong is ROLE.USER, you can change your default role only to ROLE.USER. Unless you are granted additional roles, you cannot change your default role to any other role. NOTE: A user in the role of ROLE.MGR can change the default role of another user by using the HPDM Edit User dialog box. To change your own default role: 1. Connect to a system as described in Connect to a System (page 25). 2. Select the Security area. For information about how to select an area, Select an Area (page 35). The right pane shows your sign-on user information (user name and default role). 3. In the right pane, click the down arrow next to the Default Role field, and select from the list of roles that you can use for your new default role. 4. In the right pane, click [ Change Default Role ]. Change Role or Password Information for a Database User (page 109) Terms role Platform Users Display All Platform Users You must be a user in the role of ROLE.SECMGR to display all platform users. To display all platform users: 1. Log on as a user belonging to ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). Platform Users 111

112 3. In the navigation tree pane, expand the folder for the logged on system, and select the Platform Users folder. The right pane displays all platform users, including this information about each user: User name Role Role that created the user NOTE: You can sort the user information by clicking a column heading. For example, to display all the platform users by role, click the Role column heading. To sort the list of platform users by the role that created the user, click the Created By column heading. About Users (page 103) Add a Platform User (page 112) Copy a Platform User (page 112) Terms role platform user Add a Platform User Only a user belonging to the ROLE.SECMGR role can add a platform user. To add a platform user: 1. Log on as a user belonging to ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). 3. In the navigation tree pane, expand the folder for the logged on system, and select the Platform Users folder. The right pane displays all platform users. 4. Use either of these methods to display the Add Platform User dialog box: In the navigation tree pane, right-click the Platform Users folder, and select Add Platform User. In the right pane, click [ Add ]. 5. Fill in the fields of the Add Platform User dialog box. For more information about each field, see Use the Add Platform User (or Edit User) Dialog Box (page 113). 6. Click [ OK ]. Use the Add Platform User (or Edit User) Dialog Box (page 113) Add a Database User (page 104) About Users (page 103) Terms platform user Copy a Platform User If you have multiple platform users to create and these users share similar characteristics, you can save time by copying the characteristics of an already configured platform user. You can do this by using the [ Add Like ] button on the list of platform users. NOTE: Using the [ Add Like ] button, you can only copy one platform user at a time. The same rules for creating a platform user apply to copying a platform user. In general, a user belonging to the ROLE.SECMGR role creates all platform users. To copy an already configured platform user: 112 Manage Users and Passwords

113 1. Log on as a user belonging to ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). 3. In the navigation tree pane, expand the folder for the logged on system, and select the Platform Users folder. The right pane displays all platform users. 4. In the right pane, select a user. 5. In the right pane, click [ Add Like ]. The Add Platform User Like dialog box appears. 6. Fill in the fields in the Add Platform User Like dialog box. For more information about each field, see Use the Add Platform User (or Edit User) Dialog Box (page 113). NOTE: You must change the User Name. An error message is generated if you specify a user name that is the same as an existing user. 7. Click [ OK ]. About Users (page 103) Add a Database User (page 104) Use the Add Platform User (or Edit User) Dialog Box (page 113) Terms platform user Use the Add Platform User (or Edit User) Dialog Box This table describes the fields in the Add Platform User dialog box and the Edit Platform User dialog box, which are identical. Group Box Password Password Expiration Policy Field User Name User Role Password Confirm Password No Expiration Use Expiration Description The name of the platform-level user. The name must be unique on the local platform. The user name is not case-sensitive. The user name is a text string, with a maximum of 32 alphanumeric characters and these special characters: period (.), hyphen (-), and underscore (_). Click the down arrow to select from a list of configured roles. If the role you want to select does not exist, see Add a Role (page 97). A platform user can be assigned to only one of the following roles: HP.name, SUPER.name, or NEOVIEW.name. The password to be assigned to the platform user. The password can consist of a maximum of 53 characters if you use 1024-bit encryption, or 64 characters if you use 2048-bit encryption. This password must comply with the password quality criteria specified in the current system security policy (see Use the Password Tab for Security Policies (page 120)). For information about the default password settings for platform users, see the Neoview User Management and Security Administration Guide. Type the password again to confirm it. Click this option to specify that the password never expires. Click this option to specify that the password expires on the schedule indicated by Expires Every n Days or Expiry Date date. Platform Users 113

114 Group Box Additional Parameters Field Expires Every n Days Expiry Date date Default Subvolume* Initial Directory* Default Directory* Description The interval that controls password expiration. This is the number of days, from the time the password is changed, after which it expires. Range: The default password expiration date, if no other date is specified when the user is created. To enable the date field, click the check box to the left of the date. Then specify a date. If you do not click the check box, the Expiry Date field is disabled. Range: April 24, 2007 to Dec 31, 2999 In the Neoview operating system, the name of the logon default subvolume for the platform user. This optional parameter is for use by HP support. The initial directory in the Neoview file system. This optional parameter is for use by HP support. The logon default disk file security for the platform user. This optional parameter is for use by HP support. *When adding a platform user, this field is optional. If you don't specify a value, the system assigns a default value. After you have created the platform user, you can view the system-assigned value in the Edit User dialog box. When editing a platform user, this field is required. You can modify the field, but you cannot leave the field blank. Add a Platform User (page 112) Edit a Platform User (page 114) Terms platform user Edit a Platform User Normally, a user belonging to the ROLE.SECMGR role must be used to edit a platform user. Editing a platform user allows you to change all of the parameters that were defined when the user was added, except for the platform user name. This table shows which users are permitted to change the passwords and expiration settings of other platform users: Type of Account SUPER.SUPER user SUPER.SERVICES user HP.VTS user HP.SDI user Role Required to Change the Password or Password Expiration Settings ROLE.SECMGR ROLE.SECMGR SUPER.SERVICES ROLE.SECMGR To edit a platform user: 1. Log on as a user belonging to ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). 3. In the navigation tree pane, expand the folder for the logged on system, and select the Platform Users folder. The right pane displays all platform users. 4. In the right pane, click [ Edit ], or double-click the user row. The Edit User dialog box appears. 114 Manage Users and Passwords

115 5. Fill in the fields of the Edit User dialog box. For more information about each field, see Use the Add Platform User (or Edit User) Dialog Box (page 113). 6. Click [ OK ]. Use the Add Platform User (or Edit User) Dialog Box (page 113) Terms platform user Delete One or More Platform Users Only a user belonging to the ROLE.SECMGR role can delete a platform user. You may not delete any of the predefined users: SUPERUSER, USERMGR, HPSUPPORT, SECURITYMGR or VTS. Any attempt to do so will result in an error. To delete one or more platform users: 1. Log on as a user belonging to ROLE.SECMGR. 2. Select the Security area. For information about how to select an area, Select an Area (page 35). 3. In the navigation tree pane, expand the folder for the logged on system, and select the Platform Users folder. The right pane displays all platform users. 4. In the right pane, select a user, or hold down the Ctrl key and select multiple users. 5. Click [ Delete ]. A confirmation dialog box appears. 6. Click [ OK ]. Add a Platform User (page 112) Terms platform user Passwords for Users Change Your Own Password at Logon You can change your password at logon only if the password has expired or is about to expire and is within the grace period. In this scenario, HPDM displays the Change Password dialog box when you attempt to connect to a system. For example: Passwords for Users 115

116 Fill in the fields in the dialog box, as described in Use the Change Password Dialog Box (page 116). If your old password has expired and the security policy does not define a grace period for platform-user passwords, you can no longer change your own password, but a user in the role of ROLE.SECMGR can change your password. Use the Change Password Dialog Box (page 116) Change Your Own Password After Logon (page 116) Change Role or Password Information for a Database User (page 109) Terms database user locally authenticated database user Change Your Own Password After Logon Any locally authenticated user can change his or her own password after connecting to a system using HPDM. To change your password after logging on: 1. Connect to a system as described in Connect to a System (page 25). 2. Select the Security area. The right pane shows your sign-on user information (user name and default role). 3. In the right pane, click [ Change Password ]. 4. Fill in the fields in the Change Password dialog box. For more information, see Use the Change Password Dialog Box (page 116). 5. Click [ OK ]. Use the Change Password Dialog Box (page 116) Change Your Own Password at Logon (page 115) Change Role or Password Information for a Database User (page 109) Terms locally authenticated database user Use the Change Password Dialog Box This table describes the fields in the Change Password dialog box: Field System User Name Old Password New Password Confirm New Password Description The system for which you entered the Change Password command. Your current user name. Type your current password in this field. Type your new password in this field. The password can consist of a maximum of 53 characters if you use 1024-bit encryption, or 64 characters if you use 2048-bit encryption. This password must comply with the password quality criteria specified in the current system security policy (see Manage Security Policies (page 117)). Type your new password again to confirm that it matches. Change a Password or Password Expiration Settings by Editing a User For locally authenticated users, you can also change a password or expiration setting by editing a user. See Change Role or Password Information for a Database User (page 109) or Edit a Platform User (page 114). 116 Manage Users and Passwords

117 9 Manage Security Policies About Security Policies Various behaviors related to user management and security depend on policies that the Security Administrator can configure. HPDM groups these policies into the following categories: Certificate and Connection Policies Password Policies Logging Policies Power Role Management Policies Display Security Policies (page 117) Change a Security Policy (page 117) Display Security Policies To display the currently configured security policies: 1. Log on as a user belonging to ROLE.SECMGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Policies folder. The policies tabs appear in the right pane (under the Security tab), allowing you to configure the policy options. Change a Security Policy (page 117) Change a Security Policy Before changing a security policy, note these considerations: Only a user who belongs to the ROLE.SECMGR role can change a security policy. Changing these security policies requires stopping and restarting all NDCS services: Allow Down-rev Drivers to Connect Log Successful Database Logins Log Failed Database Logins Abort Database Login if Logging Fails Role Password Required at Login (any change applying to Database Users or Platform Users) NOTE: For changes to these policies, Security Administrators should notify all users in advance that a policy change will occur. Users should be instructed to disconnect from the Neoview platform before the policy change is made. After changing the policy, the Security Administrator should notify all users that they can reconnect to the Neoview platform. Changes to security policies generally take effect immediately. However, some changes can take longer. For example, changes to authentication logging can take up to five minutes to be implemented. To change a security policy: 1. Log on as a user belonging to ROLE.SECMGR. 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Policies folder. The policies tabs appear in the right pane (under the Security tab), allowing you to configure the policy options. About Security Policies 117

118 4. In the right pane, select the desired tab for the policy you want to change. For more information about each policy, see these topics: Use the Certificate & Connection Tab for Security Policies (page 119) Use the Password Tab for Security Policies (page 120) Use the Logging Tab for Security Policies (page 121) Use the Power Role Management Tab for Security Policies (page 122) 5. Make changes as needed, then click [ Apply ] to save the changes. NOTE: You must complete the remaining steps in this procedure only if you made a change to one of the following policies: Allow Down-rev Drivers to Connect Log Successful Database Logins Log Failed Database Logins Abort Database Login if Logging Fails Role Password Required at Login (any change applying to Database Users or Platform Users) These policies require you to stop and restart all NDCS services. 6. Select the Connectivity area. 7. In the navigation tree pane, under the system icon, expand the NDCS Services folder so that you can see the NDCS services. Typically, there are services for $MXAS2 and $MXOAS, but there might be other services. 8. Stop all of the NDCS services by using these steps: a. Right-click any service, and select Stop. The Stopping Service dialog box appears. b. Type a reason for stopping the service. c. Click [ Stop on Client Disconnect ]. The service transitions to the Stopping state, from which it can be restarted. d. Restart the service by right-clicking and selecting Start. e. Repeat steps a through d until all of the NDCS services have been stopped and restarted. 118 Manage Security Policies

119 This table describes the function of buttons that appear at the bottom of the policies tabs: Button [ Refresh ] [ Load Default ] [ Load Most Secure ] [ Apply ] Description Updates the display. Sets all fields to their factory-default settings. To enforce the new settings, you must click [ Apply ] and restart NDCS services as described in the steps preceding this table. CAUTION: Because using the [ Load Default ] button requires restarting NDCS services, HP recommends that Security Administrators notify all users in advance that policy changes will occur. Users should be instructed to disconnect from the Neoview platform before the policy changes are made. After changing the policies, the Security Administrator should notify all users that they can reconnect to the Neoview platform. Sets all fields to values that provide the highest security. To enforce the new settings, you must click [ Apply ] and restart NDCS services as described in the steps preceding this table. CAUTION: Because using the [ Load Most Secure ] button requires restarting NDCS services, HP recommends that Security Administrators notify all users in advance that policy changes will occur. Users should be instructed to disconnect from the Neoview platform before the policy changes are made. After changing the policies, the Security Administrator should notify all users that they can reconnect to the Neoview platform. Saves changes made to all tabs. [ Apply ] allows you to make changes to different tabs and save all changes in one operation. Use the Certificate & Connection Tab for Security Policies (page 119) Use the Password Tab for Security Policies (page 120) Use the Logging Tab for Security Policies (page 121) Use the Power Role Management Tab for Security Policies (page 122) Terms operator privilege Use the Certificate & Connection Tab for Security Policies The Certificate & Connection tab for security policies controls password encryption and certificate handling. These policies apply to any user who logs on to the Neoview platform from a workstation running ODBC or JDBC clients. This table shows reference information for the Certificate & Connection tab for security policies: Option Auto Download Certificate Enforce Certificate Expiry Description Specifies whether the certificate is automatically downloaded if not already present when a client connects. See About the Auto Download Certificate Option (page 129). Specifies whether the certificate ever expires. When checked, this option means that if a workstation connects with an expired certificate, the certificate must be replaced, either by automatic download or by some other means. Use the Certificate & Connection Tab for Security Policies 119

120 Option Allow Down-rev Drivers to Connect Optimized for Local Access Description Specifies whether login requests are accepted from clients that do not provide password encryption. Clients earlier than Neoview Release 2.5 do not provide password encryption. CAUTION: The initial state of Allow Down-rev Drivers to Connect is deselected. Some installations will, however, choose to enable this option for a period during which workstations are being upgraded from older versions of clients to newer ones. Once the upgrade is complete, it is best to deselect Allow Down-rev Drivers to Connect again. Using older clients with a Neoview platform running Release 2.5 compromises the security of communications between workstations and the Neoview platform. Specifies whether, in the interest of faster local authentications, the following security features are disabled: Requiring platform users to present two passwords for login to platform-level command interpreters Preventing database users from logging in to platform-level command interpreters Logging of direct platform access Display Security Policies (page 117) Change a Security Policy (page 117) Use the Password Tab for Security Policies The Password tab for security policies governs the content and handling of passwords used by platform users and locally authenticated database users, and for roles. Passwords of remotely authenticated database users are managed on the external LDAP server and governed by policies implemented there. This table shows reference information for the Password tab for security policies: Policy Password Quality Policy Option Do Not Allow to Contain Username Do Not Repeat a Character More than Once in Succession Minimum Length Password requires n following criteria: Uppercase Character Required Lowercase Character Required Numeric Character Required Special Character Required Description Specifies whether the password can include the user name. Specifies whether the password can contain more than two consecutive instances of the same character. For example, BooKKeepPer and taarnation6! are acceptable. AAARating and taaarnation6! are not acceptable. Minimum length, in characters, of a password for a platform user, locally authenticated database user, or a role. Range: 6-64 The number of character categories (that is, uppercase, lowercase, numeric, special) that must be represented in the password. This value must be greater than or equal to the number of the next four attributes that are selected. Range: 0-4 Specifies whether the password is required to contain at least one uppercase character. Specifies whether the password is required to contain at least one lowercase character. Specifies whether the password is required to contain at least one numeric character. Specifies whether the password is required to contain at least one nonalphanumeric character. 120 Manage Security Policies

121 Policy Password Control Policy Default Password Expiration Policy Option History Level Grace Period after Expiration (days) May Change before Expiration (days) Max Logon Attempts Login Failed Delay (secs) No Expiration Use Expiration Expires Every n Days Expiry Date date Description Number of previous passwords retained to prevent a user from repeating a previous password (for example, a value of 10 means that a new password is not allowed to be the same as any of the user's previous 10 passwords). The range is 0 to 60. Range: 0-60 Number of days during which a platform user or locally authenticated database user can log on with a password that has expired, for the purpose of changing the password. Once the grace period has expired, the user must ask a person in the ROLE.MGR or ROLE.SECMGR role (depending on whether the user is a database user or a platform user) to change the expired password. Range: Specifies how many days prior to expiration the user may change the password. For example, if the value is 3, the user can change the password 3 days before it expires (but no earlier than that). 0 means the user can change the password at any time. Range: Number of times a platform user can fail to log on before having to wait to retry. Range: 0-60 Number of seconds the user has to wait before retrying after exceeding the configured number of retry attempts. Range: Specifies whether or not the password expires. If this option is deselected, the password expires according to the schedule indicated by Expires Every n Days or Expiry Date date or both. When selected, specifies that the password expires on the schedule indicated by Expires Every n Days or Expiry Date date or both. Default number of days before a password expires after being reset, if no other number of days is specified when the user is created. Range: The default password expiration date, if no other date is specified when the user is created. To enable the date field, click the check box to the left of the date. Then specify a date. If you do not click the check box, the Expiry Date field is disabled. Range: April 24, 2007 to Dec 31, 2999 Display Security Policies (page 117) Change a Security Policy (page 117) Passwords for Users (page 115) Use the Logging Tab for Security Policies The Logging tab for security policies shows the user management and authentication policies that determine what information is logged for later exposure through user-management views and how long the information in those views is maintained. These policies apply to locally and remotely authenticated users. For information about user-management views, see the Neoview User Management and Security Administration Guide. Use the Logging Tab for Security Policies 121

122 This table shows reference information for the Logging tab for security policies: Option Log User Management Operations Log Change Passwords Log Successful Database Logins Log Successful Platform Logins Log Failed Database Logins Log Failed Platform Logins Log File Ages in (days) n Abort User Management Operation if Logging Fails Abort Change Password if Logging Fails Abort Database Login if Logging Fails Description Specifies whether to log user management actions, such as adding or deleting a user or changing the attributes of a user's account. Specifies whether to log password changes. Passwords themselves are, of course, not logged. Specifies whether to log successful logins to the Neoview database, whether the login was attempted by a database user or a platform user. Specifies whether to log successful logins to the Neoview platform (using tools not generally available to Neoview customers). Specifies whether to log failed attempts to log on to the Neoview database, whether the login was attempted by a database user or a platform user. Specifies whether to log failed attempts to log on to the Neoview platform (using tools not generally available to Neoview customers). Specifies the retention time for user-management log information. Range: Specifies whether a user-management action can be completed if it is impossible to log the action. Specifies whether a password change can be completed if it is impossible to log the action. Specifies whether a database login can be completed if is impossible to log the action. Display Security Policies (page 117) Change a Security Policy (page 117) Use the Power Role Management Tab for Security Policies The Power Role Management tab shows policies that provide an extra level of security in the handling of platform roles in general, the power platform role SUPER.SUPER, and the power database roles ROLE.MGR, ROLE.SECMGR, and ROLE.DBA. These policies apply to locally and remotely authenticated users. This table shows reference information for the Power Role Management tab for security policies: Policy or User Type Power Role Management Policy Role Password Required at Login Option Change Password for Power Roles Requires Old Password Change Password for Super Requires Old Password Description Specifies whether the Security Manager must supply the current password for ROLE.SECMGR, ROLE.MGR, or ROLE.DBA in order to change the role password. Specifies whether the Security Manager must supply the current password for SUPER.SUPER in order to change the role password. Enables you to specify whether database users and platform users must provide a role password in addition to an individual user password (for example, userpassword/rolepassword ), in order to log on. 122 Manage Security Policies

123 Policy or User Type Database Users Platform Users Option Power Database Users Are Required None Is Required All Platform Users Are Required Power Users Are Required None is Required Description When selected, specifies that ROLE.SECMGR, ROLE.MGR, and ROLE.DBA users must provide an individual password and a role password. When selected, specifies that an individual password is sufficient for any database user to log on. When selected, specifies that all platform users must provide an individual password and a role password (for example, userpassword/rolepassword ). When selected, specifies that a SUPER.SUPER user is required to provide an individual password and a role password. When selected, specifies that an individual password is sufficient for any platform user to log on. Display Security Policies (page 117) Change a Security Policy (page 117) Terms power role power user Use the Power Role Management Tab for Security Policies 123

124 124

125 10 Manage Certificates About Certificates The current release of the Neoview platform allows you to use either a self-signed certificate or a certificate signed by a Certificate Authority (CA) of your choice. This section describes how to: Specify a certificate file when you connect to a system Generate a self-signed certificate Obtain a CA certificate and private key Generate a Certificate Signing Request (CSR) Install a CA certificate on the Neoview platform Specify a Certificate File at Connect Time (page 125) Generate a Self-Signed Certificate (page 125) Obtain and Install a CA Certificate and Private Key (page 126) Generate a Certificate Signing Request (CSR) (page 127) Install Root and Intermediate Certificates on the Neoview Platform (page 128) Specify a Certificate File at Connect Time If the Auto Download Certificate option is disabled, the certificate file is not downloaded by the driver to the client during connection. If there is no certificate file, the connection fails. A system administrator can the certificate to specific users, and the users can save this certificate file to their local workstations. At connection time, they can specify the certificate file by completing the Certificate File field in the Connect / Edit System dialog box. About the Auto Download Certificate Option (page 129) Use the Connect / Edit System Dialog Box (page 26) Display Security Policies (page 117) Generate a Self-Signed Certificate To use this procedure, you must be logged on as a user in the role of ROLE.SECMGR. During installation or upgrade of your Neoview platform, HP support runs a post-installation script to create a self-signed server certificate and generate a 2048-bit private key. The private key is stored in a file accessible to ROLE.SECMGR. This procedure allows a user in the role of ROLE.SECMGR to replace the self-signed server certificate by creating and installing a new self-signed certificate. The certificate is downloaded to the workstation from which the command is run. A self-signed certificate expires 2 years from its creation date. Once you have created and installed a new certificate on the Neoview platform, subsequent requests from clients are handled as follows: If the Auto Download Certificate option is in effect, the new certificate is downloaded to the workstation. If the Auto Download Certificate option is not in effect, the connection request fails. In this case, you must either enable auto download or distribute the certificate by other means. To generate a self-signed certificate 1. Log on as a user belonging to ROLE.SECMGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). About Certificates 125

126 3. In the navigation tree pane, under the connected system, expand the Credentials folder, and click the Self-Signed Certificate folder. The Self-Signed Certificate tab appears in the right pane. 4. Fill in the fields in the Self-Signed Certificate tab. For more information, see Use the Self-Signed Certificate Tab (page 126). 5. Click [ Generate ]. The Save As dialog box appears. 6. Select a folder and specify a file name to save the certificate. 7. Click [ Save ]. Use the Self-Signed Certificate Tab (page 126) Display Security Policies (page 117) About the Auto Download Certificate Option (page 129) Use the Self-Signed Certificate Tab This table shows reference information for the Self-Signed Certificate dialog box: Field Common Name Organization Organizational Unit City / Locality State / Province Country / Region Key Size (bits) Example HPQ0101 Hewlett Packard Business Intelligence Cupertino California United States 1024 Description Identifies the Neoview platform on which you want to install the certificate. The name consists of the unqualified DNS name of the master segment. If the external network name is different from the internal name, use the internal name. The name of your company or business unit. Your organizational unit. Your city or community. Your state or province. Your country or region. The key size, which can be 1024 for 1024-bit encryption or 2048 for 2048-bit encryption. Generate a Self-Signed Certificate (page 125) Obtain and Install a CA Certificate and Private Key Although the Neoview platform automatically generates a self-signed certificate, it is a good security practice to generate a new server certfificate signed by a Certificate Authority (CA) and install it on the Neoview platform. NOTE: The Neoview security infrastructure does not provide verification of CA certificates. To deploy your own certificate using HPDM, you (as ROLE.SECMGR) must: 1. Use the Generate CSR tab on the HPDM CA Certificate screen to create a Certificate Signing Request (CSR). 2. Submit the CSR to the CA for signing. 126 Manage Certificates

127 NOTE: If possible, use facilities provided by the CA to specify Subject Alternate Names (SANs) for all segments, or at least for all secondary segments (for example, NEO0102 to NEO0116). This information will not be present in the original CSR but is required to enable use of the event viewer without displaying warnings. If your CA does not allow you to specify SANs, define a procedure for your users to follow if they encounter browser security messages. One approach is to instruct users to view the certificate, if possible, to check the vailidity of the displayed information. 3. Receive the signed certificate from the CA. This is sometiems called the root certificate. 4. Obtain the certificate of the CA that signed the certificate. This is sometimes called the intermediate certificate and is the one downloaded to each workstation for use in encrypting the password. In most cases, you can get the intermediate certificate from the CA, but if not, you can obtain it from your browser. The precise means of doing so varies with the browser and browser version, but be sure to export the intermediate certificate in Base-64 encoded X.509 (.CER) format. 5. If automatic download is not enabled by your security policy, distribute the new intermediate certificate to client workstations that will connect to the Neoview platform. To understand where a new CA certificate must be installed, see the Neoview User Management and Security Administration Guide. 6. Use the Deploy CA Signed Certificate tab on the HPDM CA Certificate screen to install the new certificates on the Neoview platform. If the Auto Download Certificate option is disabled, you must install the new certificate on client workstations before installing it on the Neoview platform. Otherwise, connection attempts from those workstations will fail. Related topics Generate a Certificate Signing Request (CSR) (page 127) Install Root and Intermediate Certificates on the Neoview Platform (page 128) Display Security Policies (page 117) About the Auto Download Certificate Option (page 129) Generate a Certificate Signing Request (CSR) To use this procedure, you must be logged on as a user in the role of ROLE.SECMGR. This procedure generates a certificate signing request (CSR) and allows you to save the CSR to a folder on the workstation. You may then submit the CSR to the certificate authority for signing, as described in Obtain and Install a CA Certificate and Private Key (page 126). Use these steps: 1. Log on as a user belonging to ROLE.SECMGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, under the connected system, expand the Credentials folder, and click the CA Signed Certificate folder. 4. In the right pane, click the Generate CSR tab. 5. Fill in the fields in the tab. For more information, see Use the Generate CSR Tab (page 128). 6. Click [ Generate ] to generate the certificate signature request. The Save As dialog box appears. 7. Select a folder and specify a file name. 8. Click [ Save ] to save the certificate and send the CSR to the Certificate Authority. Use the Generate CSR Tab (page 128) Generate a Certificate Signing Request (CSR) 127

128 Display Security Policies (page 117) Use the Generate CSR Tab This table shows reference information for the Generate CSR tab: Field Common Name Organization Organizational Unit City / Locality State / Province Country / Region Key Size (bits) Example HPQ0101 Hewlett-Packard Business Intelligence Cupertino California United States 1024 Description Identifies the Neoview platform on which you want to install the certificate. The name consists of the unqualified DNS name of the master segment. If the external network name is different from the internal name, use the internal name. The name of your company or business unit. Your organization unit. Your city or community. Your state or province. Your country or region. The key size, which can be 1024 for 1024-bit encryption or 2048 for 2048-bit encryption. Generate a Certificate Signing Request (CSR) (page 127) Display Security Policies (page 117) Install Root and Intermediate Certificates on the Neoview Platform This procedure installs two new certificates on a Neoview platform, one for use by client connections and one for use by the HPDM event viewer connections. To use this procedure, you must be logged on as a user in the role ROLE.SECMGR. The certificates you deploy in this way could, in theory, be self-signed, but the usual use of this command is to deploy CA-signed certificates. Once you have created and installed a new certificate on the Neoview platform, subsequent requests from clients are handled as follows: If a workstation already has the new certificate installed, the request succeeds. If the workstation has an old certificate and the Auto Download Certificate option is enabled, the new certificate is downloaded to the workstation. If the workstation has an old certficate and the Auto Download Certificate option is not in effect, the connection request fails unless a new certficate has been installed on the workstation in the location prescribed by the applicable ODBC or JDBC connection attributes. For more information about these attributes, see the Neoview User Management and Security Administration Guide. If a new certificate is present in the configured location, it is copied to the active certificate location. Use these steps: 1. Log on as a user belonging to ROLE.SECMGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, under the connected system, expand the Credentials folder, and click the CA Certificate folder. 4. In the right pane, click the Deploy CA Signed Certificate tab. 5. Fill in the fields in the tab. See Use the Deploy CA Signed Certificate Tab (page 129). 6. Click [ Deploy ] to install the new CA certificate on the Neoview platform. 128 Manage Certificates

129 Use the Deploy CA Signed Certificate Tab (page 129) Display Security Policies (page 117) About the Auto Download Certificate Option (page 129) Use the Deploy CA Signed Certificate Tab This table shows reference information for the Deploy CA Signed Certificate tab: Field System Name Root Certificate Intermediate Certificate Example HPQ0101 C:\Certs\ABC01.cer C:\Certs\CACerts\CA_ABC.cer Description Identifies the Neoview platform on which you want to install the certificate. This field is required. The name consists of the unqualified DNS name of the master segment. If the external network name is different from the internal name, use the internal name. The location on the workstation where the root certificate signed by the CA currently resides. This field is required. The certificate is uploaded from this location to the Neoview platform. Click [ Browse ] to select a path. The location on the workstation of the intermediate certificate corresponding to the root certificate identified in the Root Certificate field. This field is required. The certificate is uploaded from this location to the Neoview platform and later downloaded to each workstation if automatic download is in effect. Click [ Browse ] to select a path. Install Root and Intermediate Certificates on the Neoview Platform (page 128) About the Auto Download Certificate Option (page 129) About the Auto Download Certificate Option The Auto Download Certificate option controls whether or not a certificate is automatically downloaded if not already present when a client connects. In the Security area, this option is found on the Certificate and Connection tab of the Policies folder. On new systems, the Auto Download Certificate option is in effect by default. Only a user who has the role ROLE.SECMGR can change this option. Display Security Policies (page 117) Change a Security Policy (page 117) Use the Certificate & Connection Tab for Security Policies (page 119) Use the Deploy CA Signed Certificate Tab 129

130 130

131 11 Manage Directory Servers About Directory Servers You can configure the Neoview security infrastructure to communicate with external LDAP servers. The Neoview platform explicitly supports integration with openldap-compliant directory servers and Microsoft Active Directory. HPDM is the preferred interface for LDAP server configuration. To understand where LDAP server configuration fits in the context of other Neoview security tasks, such as adding users and registering them on the Neoview platform, see the Neoview User Management and Security Administration Guide. HP recommends that you review the guide before attempting to use HPDM for LDAP server configuration. Display the Configured Directory Servers (page 131) Add a Directory Server (page 131) Terms LDAP Display the Configured Directory Servers You must be a user in the role of ROLE.SECMGR to display the configured directory servers. To display the configured directory servers: 1. Log on as a user belonging to ROLE.SECMGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, select the Directory Servers folder. The configured directory servers appear in the right pane. NOTE: Default server information is not displayed in the list of directory servers. This table describes the displayed directory server information: Field Domain Name Usage Priority Host Name HostPortNumber LDAP Version Search User DN Encryption Last Updated Description The domain name of the LDAP server. Has the value NEOVIEWDIRECTORYSERVER for openldap and for the global catalog server in Active Directory. Relative usage priority of the server. Host name or IP address of the LDAP server. Port number for connecting to the LDAP server. LDAP protocol version (Version 2 or 3) supported by the server. Distinguished name that the Neoview platform uses to connect to the LDAP server. Encryption protocol used between the Neoview platform and the directory server. Date and time when the directory server configuration was created or last updated. Add a Directory Server You must be a user in the role of ROLE.SECMGR to add a directory server. To add a directory server, use either of these methods: Add the directory server from the navigation tree pane: About Directory Servers 131

132 1. Log on as a user belonging to ROLE.SECMGR. For more information about logging on, see Connect to a System (page 25). 2. Select the Security area. For more information about areas, see Select an Area (page 35). 3. In the navigation tree pane, expand the system folder. 4. Right-click the Directory Servers folder, and select Add Directory Server. Add the directory server from the Directory Servers display under the Security tab in the right pane: 1. Display the configured directory servers, as described in Display the Configured Directory Servers (page 131). 2. Click [ Add ]. The Add Directory Server dialog box appears. NOTE: To add a directory server using a copy of a currently configured directory server, you must first select the directory server that has the configuration you want to copy. Then click [ Add Like ]. See Copy a Configured Directory Server (page 140). 3. Fill in the dialog box fields. For information about each field, see Use the Add Directory Server Dialog Box (page 132). For considerations that apply to configuring the different types of directory servers, see Considerations for Adding Directory Servers (page 135). 4. Click [ OK ]. Use the Add Directory Server Dialog Box (page 132) Understand Configuration Parameters (page 134) Considerations for Adding Directory Servers (page 135) Use the Add Directory Server Dialog Box This table shows reference information for the Add Directory Server dialog box: NOTE: The following information also applies to the Edit Directory Server dialog box. Field Server Type Domain Type Domain Name Range LDAP, Active Directory Global Catalog, Domain Controller 1 50 characters Description The LDAP server type. Two options are provided: LDAP and Active Directory. If you choose Active Directory, the dialog box expands to include fields for the Domain Type and Domain Name. The domain type. This field is visible only when Active Directory is specified for the Server Type. The domain name of the LDAP server. This field is visible only when Active Directory is specified for the Server Type. The value is a text field. Any character is permitted. However: For openldap, the domain name should always be NEOVIEWDIRECTORYSERVER. Upon receiving a logon request, the LDAP daemon uses the highest-priority server named NEOVIEWDIRECTORYSERVER to search for and authenticate the target user. For Active Directory, the global catalog server, which the LDAP daemon uses for initial search operations, must have the domain name NEOVIEWDIRECTORYSERVER (HPDM enforces this restriction when you specify Global Catalog as the domain type). Other domain name values should match the domains in the active directory. 132 Manage Directory Servers

133 Field Host Name Host Port Number UsagePriority Search DN Password ConfirmPassword LDAP Version Range Maximum of 128 characters A positive integer in the range A signed integer in the range A maximum of 512 characters printable characters printable characters Version 2, Version 3 Description The host name or IP address of the LDAP server. This value is a text field with the following characteristics: The field can contain a maximum of 128 characters. The value that you specify must be a valid DNS name or IP address. If the LDAP server uses SSL or TLS, the host name: Must be fully qualified May not be specified as an IP address Must match the name specified in the SSL certificate on the machine where the external directory server is running The port number for connecting to the LDAP server. Standard port numbers for openldap are: Non-secure: 389 SSL: 636 TLS: 389 Standard port numbers for Active Directory are: Non-secure Global Catalog: 3268 Non-secure Domain Controller: 389 SSL Global Catalog: 3269 SSL Domain Controller: 636 TLS Global Catalog: 3268 TLS Domain Controller: 389 The usage priority of this server. When the Neoview LDAP daemon receives a logon request, it checks the domain name first and then uses the server with the highest priority to authenticate the request. If that server fails to respond, the LDAP daemon tries the server with the next highest priority. For example, if you are using Active Directory, the initial search operation is directed to the NEOVIEWDIRECTORYSERVER with the highest value of UsagePriority. A subsequent authentication request is directed to the highest-priority server that has the domainname under which the user is registered. The Distinguished Name of a user that the LDAP daemon uses to log on to the LDAP server to search for user entries. This DN is unrelated to any individual user's login credentials. NOTE: If you use NCI to create the directory server entry, and the Search DN contains commas, the DN must be enclosed in double quotation marks ("). These quotation marks are not needed in HPDM because HPDM supplies the quotation marks internally if they are needed. The password of the Search DN user that the LDAP daemon uses to log on to the LDAP server to search for user entries. This password is unrelated to any individual user's login credentials. The value is a text field with these restrictions: The value must have at least one and no more than 128 characters. Only printable characters are permitted. If the password includes commas, it must be enclosed in double quotation marks ("). To confirm the original password, retype it. The version of the LDAP protocol supported by the server. Use the Add Directory Server Dialog Box 133

134 Field Common Parameters Parameters Encryption Option Certificate Range N/A N/A No Encryption Use SSL Use TLS A maximum of 4096 characters Description Parameters that apply to all servers. To add a row in the Parameters grid, right-click and select Add Row. To delete a row, select the row. Then right-click and select Delete Row. For considerations, see Understand Configuration Parameters (page 134) and Considerations for Adding Directory Servers (page 135). For examples, see the Neoview User Management and Security Administration Guide. Parameters that are server specific. To add a row in the Parameters grid, right-click and select Add Row. To delete a row, select the row. Then right-click and select Delete Row. For considerations, see Understand Configuration Parameters (page 134) and Considerations for Adding Directory Servers (page 135). For examples, see the Neoview User Management and Security Administration Guide. Indicates whether a Transport Layer Security (TLS) or Secure Sockets Layer (SSL) interface is used for access to this LDAP server. No Encryption means to use neither TLS nor SSL. In this case, communication between the Neoview platform and the LDAP server is not encrypted.the value you supply must be consistent with the configuration of the port on the remote LDAP server. If you use TLS or SSL, you must provide the CA certificate. The contents of a certificate obtained from a directory Certification Authority (CA). This certificate is used as the digital signature for the connection between the LDAP daemon and the LDAP server. A certificate is required if the Encryption attribute has a value prescribing the use of SSL or TLS. The certificate file can contain a maximum of 4096 characters.to import a certificate from a file, click this button: In the Add Directory Server dialog box, the buttons function as follows: Button Import certificate from a file [ Reload ] [ OK ] [ Cancel ] Function Allows you to specify the location of the certificate file so that it can be imported. Clears all fields in the dialog box. Adds the directory server configuration. Closes the dialog box. Add a Directory Server (page 131) Understand Configuration Parameters (page 134) Considerations for Adding Directory Servers (page 135) Understand Configuration Parameters When you add an LDAP server, HPDM allows you to specify certain parameters that govern LDAP search behavior. HPDM divides these into Common Parameters and Parameters. Common parameters are parameters that must be common across servers or that should be used 134 Manage Directory Servers

135 by default if no value is specified when an individual server is configured. Parameters are server-specific and can be different on different servers or in different domains. The following table shows you the parameters that can be used in Common Parameters and Parameters fields for LDAP server configuration. Note that common parameters are evaluated at runtime. NOTE: If you use NCI for LDAP server configuration, you must create a default configuration description file. The configuration description file is a text file that assigns values to the common parameters. HPDM users do not need to create a configuration description file, but they should be aware of the file if it exists. If, for example, you use both HPDM and NCI at different times to manage the server configurations, changes that are made in the Common Parameters affect the default server configuration. Conversely, if you use NCI to alter a server configuration, specifying a new default configuration file, the values in that file will overwrite the values you specified earlier as Common Parameters in HPDM. For more information about the default configuration description file, see the Neoview User Management and Security Administration Guide. Supported Directory Server Type Parameter Description Active Directory openldap Comments DirectoryBase Specifies the top node for the directory server. Yes Yes Valid as a common parameter or server-specific parameter UniqueIdentifier Specifies the part of a user's DN that uniquely identifies the user. Yes Yes Valid as a common parameter or server-specific parameter UserIdentifier Specifies the directory attribute that uniquely identifies the user. Yes No Valid only as a common parameter UserIdentifierMapping Specifies how the user's login text is related to the contents of the attribute specified by UserIdentifier. Yes No Valid only as a common parameter UserIdentifierFormat Specifies the format of the logon string. Yes Yes Valid only as a common parameter DomainAttribute Specifies the attribute whose value includes the name of the user's domain. Yes No Valid only as a common parameter DomainAttributeFormat Specifies where the domain name occurs with the value of DomainAttribute. Yes No Valid only as a common parameter For more detailed information and examples of each parameter, see the Neoview User Management and Security Administration Guide. Considerations for Adding Directory Servers This table provides considerations and recommendations for configuring these three types of directory servers: Considerations for Adding Directory Servers 135

136 LDAP directory server Global Catalog for an Active Directory server Domain Controller for an Active Directory server Consideration Adding an LDAP Directory Server Adding a Global Catalog for an Active Directory Server Adding a Domain Controller for an Active Directory Server Server Type Specify LDAP. The server type is inserted into the configuration description (ConfigText) file as an additional parameter. Internally, HPDM uses the server type to differentiate the types of directory servers. For more information about the ConfigText file, see the Neoview User Management and Security Administration Guide. Specify Active Directory. Specify Active Directory. Domain Type This field is not visible when you select the LDAP Server Type. Specify Global Catalog. Specify Domain Controller. Domain Name This field is not visible when you select the LDAP Server Type. The field is implicitly set to NEODIRECTORYSERVER. The Domain Name is set to NEODIRECTORYSERVER and cannot be edited. Specify a name of 1 50 characters. Required Fields Host Name Host Port Number UsagePriority Search DN Password Confirm Password Host Name Host Port Number UsagePriority Search DN Password Confirm Password Domain Name Host Name Host Port Number UsagePriority Search DN Password Confirm Password Notes About Common Configuration Parameters The common configuration parameters are fetched from the CONFIGTXT table entry for the default server. Any changes made to the common configuration parameters are applied to the default directory server entry. The common configuration parameters are fetched from the CONFIGTXT table entry for the default server. Any changes made to the common configuration parameters are applied to the default directory server entry. The common configuration parameters are fetched from the CONFIGTXT table entry for the default server. The common parameters cannot be edited. To edit the common parameters, you would have to edit the common parameters of the Global Catalog. 136 Manage Directory Servers

137 Consideration Adding an LDAP Directory Server Adding a Global Catalog for an Active Directory Server Adding a Domain Controller for an Active Directory Server Inherited and Supported Common Parameters DirectoryBase UniqueIdentifier UserIdentifierFormat Comment DirectoryBase UniqueIdentifier UserIdentifier UserIdentifierFormat UserIdentifierMapping DomainAttribute DomainAttributeFormat Comment DirectoryBase UniqueIdentifier UserIdentifier UserIdentifierFormat UserIdentifierMapping DomainAttribute DomainAttributeFormat Comment Configuration Parameters The only values that you can enter as configuration parameters specific to this LDAP server are Comment, DirectoryBase, and UniqueIdentifier. The drop-down list in the Parameters box lets you select only one of these three options. The only values that you can enter as configuration parameters specific to this Global Catalog server are Comment, DirectoryBase, and UniqueIdentifier. The drop-down list in the Parameters grid lets you select only one of these three options. The only values that you can enter as configuration parameters specific to this domain controller are Comment, DirectoryBase, and UniqueIdentifier. The drop-down list in the Parameters grid lets you select only one of these three options. For examples, see the following topics and the Neoview User Management and Security Administration Guide. Example: LDAP Server (page 137) Example: Active Directory Server (page 138) Example: LDAP Server This table shows values specified in the Add Directory Server dialog box to create a simple LDAP server entry. The server entry has the underlying domain name of NEOVIEWDIRECTORYSERVER. The DIRECTORYBASE common parameter specifies cup.hp.com as the top node for searching all Neoview users. A user is defined as someone with a unique identifier belonging to the organization People or having the common name People. The user logon format requires only the user name. No server-specific parameters are defined for this server entry. TLS encryption is used, and the server entry includes the location of a certificate obtained from a Certification Authority. Field Server Type Host Name Host Port Number UsagePriority Search DN Password Confirm Password LDAP Version Common Parameters Parameters Example Value LDAP main_ldap.cup.hp.com uid=search_user,ou-people,dc=cup.hp.com Searchpd Searchpd Version 3 DIRECTORYBASE dc=cup.hp.com UNIQUEIDENTIFIER uid,ou=people UNIQUEIDENTIFIER cn,ou=people (none) Example: LDAP Server 137

138 Field Encryption Option Certificate Example Value TLS c:\ldap\hpca2ss Add a Directory Server (page 131) Use the Add Directory Server Dialog Box (page 132) Example: Active Directory Server This table shows values specified in the Add Directory Server dialog box to create a Global Catalog server for an active directory. The Global Catalog server entry is created with the internal domain name of NEOVIEWDIRECTORYSERVER: Field Server Type Domain Type Domain Name Host Name Host Port Number UsagePriority Search DN Password Confirm Password LDAP Version Common Parameters Parameters Encryption Option Certificate Global Catalog Entries Active Directory Global Catalog NEOVIEWDIRECTORYSERVER dc01.domaina.cup.hp.com cn=ad_search_user,cn=users,dc=domaina, dc=cup,dc=hp,dc=com 2Ldap_daemon_pwd 2Ldap_daemon_pwd 3 DIRECTORYBASE dc=cup,dc=hp,dc=com USERIDENTIFIER userprincipalname USERIDENTIFIERFORMAT domain\user USERIDENTIFIERMAPPING user@domain.* (none) No Encryption (none) This table shows values specified in the Add Directory Server dialog box to create two domain controller entries for the active directory example. In this example, the two domain controller entries are called DOMAINA and DOMAINB. The common parameters for the domain controller entries are inherited from the Global Catalog entry and can be changed only in the Gobal Catalog entry. This example supports the domain\user logon name format. For example, a user named John Smith might log on as: DOMAINA\SmithJ Field Server Type Domain Type First Domain Controller Active Directory Domain Controller Second Domain Controller Active Directory Domain Controller 138 Manage Directory Servers

139 Field Domain Name Host Name Host Port Number UsagePriority First Domain Controller DOMAINA dc01.domaina.cup.hp.com Second Domain Controller DOMAINB dc02.domainb.cup.hp.com Search DN cn=ad_search_user,cn=users,dc=domaina, dc=cup,dc=hp,dc=com cn=ad_search_user,cn=users,dc=domainb, dc=cup,dc=hp,dc=com Password Confirm Password LDAP Version Common Parameters Parameters Encryption Option Certificate 2Ldap_daemon_pwd 2Ldap_daemon_pwd 3 DIRECTORYBASE dc=cup,dc=hp,dc=com USERIDENTIFIER userprincipalname USERIDENTIFIERFORMAT domain\user USERIDENTIFIERMAPPING user@domain.* (none) No Encryption (none) 2Ldap_daemon_pwd 2Ldap_daemon_pwd 3 DIRECTORYBASE dc=cup,dc=hp,dc=com USERIDENTIFIER userprincipalname USERIDENTIFIERFORMAT domain\user USERIDENTIFIERMAPPING user@domain.* (none) No Encryption (none) Add a Directory Server (page 131) Use the Add Directory Server Dialog Box (page 132) Edit a Directory Server Only a user who has the ROLE.SECMGR role (for example, SecurityAdmin) can edit a directory server. To edit a configuration entry for a directory server: 1. Display the configured directory servers, as described in Display the Configured Directory Servers (page 131). 2. Select the directory server that you want to edit. 3. Click [ Edit ]. The Edit Directory Server dialog box appears. 4. Fill in the dialog box fields. See Use the Add Directory Server Dialog Box (page 132). 5. Click [ OK ]. Use the Add Directory Server Dialog Box (page 132) Use the Edit Directory Server Dialog Box Fields in the Edit Directory Server dialog box are the same as those found in the Add Directory Server dialog box. Fields that cannot be edited (for example, the Domain Name and UsagePriority) are grayed out. For detailed information about these fields, see Use the Add Directory Server Dialog Box (page 132). Edit a Directory Server (page 139) Use the Add Directory Server Dialog Box (page 132) Edit a Directory Server 139

140 Copy a Configured Directory Server To use the attributes of a currently configured directory server to create a new directory server configuration: 1. Display the directory server list as described in Display the Configured Directory Servers (page 131). 2. Select the directory server whose configuration you want to copy. 3. Click [ Add Like ]. The Add Directory Server dialog box appears, populated with the attributes for the selected directory server. 4. Fill in the fields. For more information, see Use the Add Directory Server Dialog Box (page 132). Delete a Directory Server Only a user who has the ROLE.SECMGR role (for example, SECURITYMGR) can delete a directory server. 1. Display the configured directory servers, as described in Display the Configured Directory Servers (page 131). 2. Select the directory server that you want to drop. 3. Click [ Delete ]. A warning dialog box appears. 4. Click [ Yes ], [ No ], or [ Cancel ], as needed. Display the Configured Directory Servers (page 131) Add a Directory Server (page 131) 140 Manage Directory Servers

141 12 Manage Data Sources Display Data Sources Any user can display all data sources. To display all data sources: 1. Under the navigation tree pane, click the Connectivity area. (For more information, see Select an Area (page 35).) 2. In the navigation tree pane, find the system that contains the data sources that you want to display. Expand the system and click the Data Sources folder: The right pane displays the Data Sources tab, showing a list of all data sources. This table describes the fields in the Data Sources tab: Field Data Source Name Maximum Start Ahead Available Description User-created name for the data source. Maximum number of servers configured for this data source. The number of NDCS servers that NDCS starts for the data source when the data source is started. Number of servers available to accept a connection. Display Data Sources 141

142 3. In the navigation tree pane, click a named data source. Detailed information about the data source appears in the right pane. This table describes the fields in the Data Source Status tab in the right pane: Field Data Source Name Service Name State Tracing Count Connected Maximum Start Ahead Available Last State Changed Description User-created name for the data source. NDCS service to which the process belongs. Current state of the data source. Current state of server tracing. This field is visible only to roles that have OPERATOR privileges. Total number of running servers. Number of servers connected to clients. Maximum number of servers configured for this data source. The number of NDCS servers that NDCS starts for the data source when the data source is started. Number of servers available to accept a connection. Date and time of the last update of the data source state (presented in the client's local time). Terms data source Create a Data Source Requirement: Only roles that have OPERATOR privileges can perform management tasks. To create a data source: 1. Under the navigation tree pane, click the Connectivity area. 2. Under My Systems, expand the tree for the Neoview platform for which you want to create a new data source until you can see the Data Sources heading. 3. Right-click Data Sources, and select Create New Data Source. The Create New Data Source window appears. 4. Configure the data source tabs, as described in: Use the General Properties Tab (page 143). Use the DEFINEs and SETs Tab (page 147) Use the Control Query Defaults Tab (page 148) Use the Controlled Tables Tab (page 149) 142 Manage Data Sources

143 NOTE: Some tabs provide tooltips that describe the use of an option or the range of values supported for a field. For example: 5. When you are finished, click [ Create ]. 6. If the new data source is not immediately visible, click the Data Sources folder in the navigation tree pane, and select Refresh. 7. To start the data source, see Start a Data Source (page 151). Terms operator privilege data source navigation tree pane Use the General Properties Tab Group Box Data Source Name Start Mode Performance Option or Check Box Name Automatic Manual Server Idle Timeout Description Enter a unique name for the new data source. The name can be a maximum of 128 characters (any characters) without leading or trailing spaces. Leading or trailing spaces are automatically removed before the name is sent to the server. Embedded spaces are not removed, and result in an error. A name that includes special characters should be delimited (enclosed) by double quotes. Special characters are characters other than: A through Z a through z Digits 0 through 9 Underscore (_) For more information about special characters and delimited identifiers, see the Neoview SQL Reference Manual. NDCS automatically starts the initial NDCS servers for the data source when the NDCS service is started. You must use HPDM to manually start the NDCS servers for the data source when the NDCS service is in the started state. This is the default value. The number of minutes that an NDCS server remains idle before it stops itself. This timeout occurs only under the following conditions: The idle server is not connected to a client. The number of servers exceeds the number of available servers configured for the data source. The system default is 10 minutes. Enter an integer from 1 to 2,147,483,647. Create a Data Source 143

144 Group Box Session Statistics Number of Servers Process Priority Node Utilization Option or Check Box Connection Idle Timeout Connection Information Session Summary Maximum Start Ahead Available Initial System Default Node Order System Default Description The number of minutes that a client-server connection remains idle before the NDCS server terminates the connection. The system default is 10 minutes. Enter an integer from 1 to 2,147,483,647. This value does not apply to servers that are included in the available count. Select this option to collect statistics about the connection and the session. Data source statistics are stored in the EMS log, event message For more information, see: Session Statistics: Connection Information (page 58). Resource Statistics Event Message Format (page 57) Select this option to collect statistics about individual SQL statements. Data source statistics are stored in the EMS log, event message For more information, see: Session Statistics: Session Summary Information (page 58) Resource Statistics Event Message Format (page 57) The maximum number of servers that NDCS should start for the data source. 1 is the default value. The range is 0 to specifies the system default, determined by the system at run time. If you use the default value of 1000 ports for NDCS during installation, the range for maximum is 1 through 997. If you configure more than 1000 ports for NDCS, the value for Maximum is the number of configured ports minus 3. In this case, the actual maximum number of NDCS servers can sometimes be greater than the number of ports configured. The number of NDCS servers that NDCS starts for the data source when the data source is started. The range is 0 to The default value is 0. This value cannot exceed the maximum server value. CAUTION: The sum of all the Start Ahead values for a given system should not exceed the number of ports specified when the NDCS service was started. HP recommends that this sum not exceed 200. The number of NDCS servers that NDCS should always have available for ODBC client connections when the data source is in the started state. The default value is 0. The range is 0 to This value cannot exceed the maximum server value. The priority assigned to a process started for this data source. The range is 1 to 199. The priority of the MXOAS process at the time the servers are created. The processing nodes (CPUs) you want to use for this data source. Enter a list of CPU numbers, individually or as a range, separated by commas. For example: 1,2,7-11,14-15, 20,21,22 NOTE: You must enter the numbers of a range in ascending order. If you do not, only the first number of the range is used. For example, in the range 10-4, only CPU 10 is used. For more information about processing-node numbering, see Understand Processing-Node Numbering (page 146). Let the Neoview software determine the node utilization automatically. 144 Manage Data Sources

145 Group Box Statement Statistics Resource Management Option or Check Box SQL Statement SQLExecute SQLExecDirect SQLPrepare SQLFetch Add Modify Remove Description Statistics about individual SQL statements. For more information, see Statement Statistics: SQL Statement (page 59). Statement Statistics: SQLExecute (page 59) Statement Statistics: SQLExecDirect (page 60) Statement Statistics: SQLPrepare (page 61) Statement Statistics: SQLFetch (page 61) See Add or Modify Resource Management Policy (page 146). See Add or Modify Resource Management Policy (page 146). Removes the selected resource management policy. Create a Data Source 145

146 Understand Processing-Node Numbering This table shows the processing-node numbers for each segment in a Neoview platform. For an 8-segment Neoview platform, processing nodes are numbered sequentially from 0 to 127. For example, segment 1 contains processing nodes 0 through 15. Segment 2 contains processing nodes 16 through 31, and so on. If you specify the processing-node list 2, 18, 3, 19 highlighted with underscores in the table the association server starts the first NDCS server in processing node 2 of segment 1, the second in processing node 2 of segment 2, the third in processing node 3 of segment 1, and the fourth in processing node 3 of segment 2. If more NDCS server processes are needed, the association server starts again at the beginning of the processing-node list; in this example, a fifth NDCS server process would be created on processing node 2. Client connections are allocated in the same order. Position in Segments 1 8 Processing Node Add or Modify Resource Management Policy The Resource Management box of the Create New Data Source dialog box displays each resource management policy that is currently in effect for a data source. You can add, modify, or remove a resource management policy for the selected data source. 146 Manage Data Sources

147 NOTE: You can enter only one resource management policy for each attribute name. Clicking [ Add ] or [ Modify ] displays a dialog box with these fields: Field Attribute Action Limit Description The name of a resource management policy attribute that limits the execution of user queries from a client application, based on cost. The action to be taken by NDCS when the limit is exceeded. In all cases, an event message is sent to the event log. Valid values are: LOG The user query continues execution. LOG_WITH_INFO The user query returns a warning message to the client; the query execution continues. STOP The user query returns an error message to the client; the query execution stops. The maximum value for the attribute. This value is any positive number; the maximum is the value of the LARGEINT SQL data type. Filling out the fields and clicking [ OK ] adds the new resource management policy to the attribute list or modifies the currently configured policy. Changes take effect on the next connection to a server in the data source. Use the DEFINEs and SETs Tab About DEFINEs NOTE: DEFINEs are used by HP support to customize or tune your Neoview platform. For this reason, limited documentation is provided. A DEFINE is a named set of attribute-value pairs associated with a process. Neoview SQL allows DEFINEs to be used as logical names for tables, views, or partitions in statements that query Neoview SQL objects. DEFINEs are primarily for use by HP support. DEFINE statements are stored as part of the configuration data for the data source. They are retrieved and set by the association server when it reads the startup values for the data source. Changes take effect on the next connection to a server in the data source. Button Functions on the DEFINEs Tab Button [ Add ] [ Modify ] [ Remove ] Function Displays the Add DEFINE dialog box. Displays the Edit DEFINE dialog box. Removes the selected DEFINE. About SETs NOTE: SET variables are used by HP support to customize or tune your Neoview platform. For this reason, limited documentation is provided. SET variables affect the behavior of NDCS. For example, you can set default catalog and schema names for servers running in this data source when they are not set at the client data source. (Client data source values take precedence over server data source values.) SETs are primarily for use by HP support. Create a Data Source 147

148 SET variables are stored as part of the configuration data for the data source. They are retrieved by the association server when it reads the startup values for the data source and then set by the data source server when a connection is established. Button Functions on the SETs Tab Button [ Add ] [ Modify ] [ Remove ] Function Displays the Add SET dialog box. Displays the Edit SET dialog box. Removes the selected SET. Note that some SET commands require you to specify a value in single quotes. For example, SET SESSION commands always require the value to be in single quotes. For example: Internally, HPDM concatenates the Name and Value fields to form the SET command. Therefore, you can specify the value alone in the value field and the rest of the command in the Name field, as shown in the previous example. Alternately, you can specify the type of the SET command in the Name field and the rest of the command in the Value field. HP recommends using this approach. For example: Use the Control Query Defaults Tab NOTE: CQDs are used by HP support to customize or tune your Neoview platform. For this reason, limited documentation is provided. To add or modify a CQD configured for a data source: 1. Under the navigation tree pane, click the Connectivity area. 2. Follow the initial steps for creating or modifying a data source (see Create a Data Source (page 142) or Update a Data Source (page 152)) until you see these tabs: 148 Manage Data Sources

149 3. Click the Control Query Defaults tab. 4. Click [ Add ] or [ Modify ]. 5. In the CQD Name field, enter a new name or change the existing name. 6. In the Value field, enter a new CQD value, or change the current value. NOTE: The names and values entered manually cannot be checked for validity at the time of entry. They are validated at execution time only. Use the Controlled Tables Tab The Controlled Tables Tab allows you to manipulate certain options for specific tables: Option Name If-Locked MDAM Priority Similarity Check Table Lock Timeout Description The table name. Determines the result if you attempt to access data with read committed or serializable access and the data is locked by another user. Specifies whether to use MDAM (MultiDimensional Access Method) for subsequently compiled DML (Data Manipulation Language) statements that access the index. Specifies the priority for subsequent file system requests to DAM. DAM uses the priority to ensure efficient performance in a mixed workload environment. Specifies whether to perform similarity checks for new and previous tables to avoid statement recompilation. This applies to tables only, not views. Determines whether to use table locks for subsequently compiled DML statements that access the table or view. The amount of time allowed to complete file-system requests from the DML operations. If the time elapses before the file system can grant a request to lock data, the DML statement fails and SQL/MX returns an error. NOTE: This timeout applies to static operations only. If-Locked Option of Controlled Tables Tab Value <Not Set> Return Wait Description The value used is the system default setting that exists at execution time. Returns the file-system error 73. For more information about file-system errors, see the Neoview Messages Manual. Neoview SQL waits for another user to release the lock, until the timeout period elapses. MDAM Option of Controlled Tables Tab Value <Not Set> Enable Off On Description The value used is the system default setting that exists at execution time. Neoview SQL determines whether to use MDAM. This is the default. Do not use MDAM. Use MDAM. Create a Data Source 149

150 Priority Option of Controlled Tables Tab Possible values are 1 through 9. Specify a higher priority for short-duration OLTP-type requests running with concurrent long-duration query requests. NOTE: activity. Using the highest possible value (9) can interfere with Neoview SQL system-level Similarity Check Option of Controlled Tables Tab Value <Not Set> Off On Description The value used is the system default setting that exists at execution time. Neoview SQL recompiles the statement at run time, depending on the outcome of late name resolution, timestamp comparison, or table redefinition. Neoview SQL performs similarity checks at run time to determine whether the new table is similar to the previous table. If similar, Neoview SQL uses the table without recompilation. Otherwise, the SQL statement is recompiled with the new table name. This is the default. Table Lock Option of Controlled Tables Tab Value <Not Set> Enable Off On Description The value used is the system default setting that exists at execution time. Neoview SQL decides whether to use table locks for the specified table or view. Do not use table locks. Use table locks. Timeout Option of Controlled Tables Tab Option <Not Set> No Timeout Will Not Wait Interval Description The value used is the system default setting that exists at execution time. No timeout is specified. Do not wait for a table lock. If the lock cannot be acquired, Neoview SQL returns an error. 1 though hundredths of a second. Copy a Data Source Requirement: Only roles that have OPERATOR privileges can perform management tasks. If you need to create a data source that is similar to an already-configured data source, you can use the configured data source as a template for the new data source. This procedure makes a copy of an existing data source configuration and allows you to modify the copy as needed. To make a copy of an existing data source: 1. Under the navigation tree pane, click the Connectivity area. 2. Under My Systems, expand the tree for the Neoview platform for which you want to create a data source until you can see the Data Sources heading and the data source names under the heading. 3. In the navigation tree pane, right-click the data source that you want to copy and select Create New Data Source Like. The Create New Data Source window appears. 150 Manage Data Sources

151 4. Modify the information in these tabs, as necessary: Use the General Properties Tab (page 143). NOTE: You must change the data source name. If you do not change the name, HPDM returns an error message indicating that the data source already exists. Use the DEFINEs and SETs Tab (page 147) Use the Control Query Defaults Tab (page 148) Use the Controlled Tables Tab (page 149) NOTE: If you made changes to the values in a tab, but you did not apply the changes, you can revert to the values previously stored on the server by clicking [ Reload ]. 5. Click [ Create ]. Terms operator privilege data source Start a Data Source Requirement: Only roles that have OPERATOR privileges can perform management tasks. When you start the NDCS service, data sources configured with the automatic startup option are started. You cannot start the Admin_Load_DataSource. This data source is always started so that HPDM can continue managing connectivity when all other data sources are stopped. To start a data source: 1. Verify that the association server for the data source is started: a. Check the NDCS Server Status display for the data source by performing the steps in Display NDCS Services (page 157). b. If the association server ($MXOAS or $MXAS2) is not available, start it by following the steps in Start an NDCS Service (page 158) 2. In the left navigation pane, click the data source that you want to start. 3. In the right pane, click the Data Source Status tab to display the list of services. 4. Select the association server Service Name that you want to use with the data source. NOTE: For optimal performance, always use MXAS2 with the Transporter data source and MXOAS with other data sources. For more information about association servers, see Learn About the Association Servers (page 156). 5. Click [ Start ]. Terms operator privilege association server data source Stop a Data Source Requirement: Only roles that have OPERATOR privileges can perform management tasks. You cannot stop the Admin_Load_DataSource. This data source is always started so that HPDM can continue managing connectivity when all other data sources are stopped. To stop a data source: 1. Under the navigation tree pane, click the Connectivity area. Start a Data Source 151

152 2. In the navigation tree pane, find the system that contains the data source(s) that you want to stop. Expand the system to display the list of data sources below it, and click a data source to select it. 3. In the right pane, click the Data Source Status tab. 4. Select all of the services in which the data source is configured. Normally, a data source is configured either on MXOAS or on MXAS2. See Learn About the Association Servers (page 156). 5. Click [ Stop ]. The Stopping Data Source dialog box appears. 6. In the Reason box, type a reason for stopping the data source. 7. Click one of these options: NOTE: After you click one of the stop options, you cannot cancel the operation. [ Stop on Client Disconnect ] [ Stop Immediately ] CAUTION: Use [ Stop Immediately ] with caution. [ Stop Immediately ] stops the data source without waiting for its associated NDCS servers to finish any current database statements or sessions. The transaction manager rolls back all uncommitted transactions held by these NDCS servers. All client connections are closed. [ Cancel ] Terms operator privilege Update a Data Source Requirement: Only roles that have OPERATOR privileges can perform management tasks. To update a data source: 1. Under the navigation tree pane, click the Connectivity area. 2. In the navigation tree pane, expand the system to display the list of data sources below it. 3. Right-click the data source name that you want to update, and select Edit. The Configuration tab appears. 4. Modify the information in these tabs, as necessary: Use the General Properties Tab (page 143). Use the DEFINEs and SETs Tab (page 147) Use the Control Query Defaults Tab (page 148) Use the Controlled Tables Tab (page 149) NOTE: If you made changes to the values in a tab, but you did not apply the changes, you can revert to the values previously stored on the server by clicking [ Reload ]. 5. Click [ Apply ]. Terms operator privilege Delete a Data Source Requirement: Only roles that have OPERATOR privileges can perform management tasks. 152 Manage Data Sources

153 NOTE: You cannot delete the two default data sources (TDM_Default_DataSource and Admin_Load_DataSource). A data source must be stopped before you can delete it. To delete a data source: 1. Stop the data source by performing the steps in Stop a Data Source (page 151). 2. In the navigation tree pane, right-click the data source, and select Delete. A dialog box asks you to confirm the data source deletion. 3. Click [ Yes ]. Terms operator privilege Delete a Data Source 153

154 154

155 13 Manage Connectivity Display NDCS Servers Any user can display NDCS servers. To display all NDCS servers for a system: 1. Under the navigation tree pane, click the Connectivity area. (For more information, see Select an Area (page 35).) 2. In the navigation tree pane, under the desired system, click NDCS Services. 3. In the right pane, click the NDCS Server Status tab. The list of NDCS servers and data source names appears. This table describes the fields in the NDCS Server Status tab: Display NDCS Servers 155

156 Field Process Name Service Name Data Source Name State PID Client Application Name User Name Client User Name Computer Name Node Server PIN Port Last Updated Time Description Operating system process name of the server. This field is visible only to roles that have OPERATOR privileges. NDCS service to which the process belongs. Operating system process name of the server. Current state of the server Process ID of the client connected to the server (or blank if there is no connection). Name of the client application connected to the server (or blank if there is no connection). Name of the user connected to the server (or blank if there is no connection). The connected user as identified by the workstation logon name. This field helps to uniquely identify the connected user when several users share the same Neoview logon name but connect from different workstations. Computer name where the client application is running (or blank if there is no connection). Processing node (CPU) number where the server is running. Operating system process ID assigned to the server. This field is visible only to roles that have OPERATOR privileges. Port number for the service. Date and time (in the client's local time) of the last update of the server's state. Terms NDCS server Learn About the Association Servers MXOAS and MXAS2 are the association servers. Association servers are persistent processes running on the master segment. They provide database connectivity to client applications, spawning NDCS server processes to handle database requests from clients. For example, in a cluster having segments NEO0001 to NEO0008, the MXOAS and MXAS2 servers run on the segment NEO0001 and spawn NDCS server processes on segments NEO0001 to NEO0008. MXOAS and MXAS2 are functionally the same but serve different purposes: MXOAS provides database connectivity for customer applications, which run on workstations attached to the routed LAN. MXAS2 provides database connectivity for the Neoview Transporter, which runs on data loader systems attached to a high-speed private LAN. NDCS server processes execute the database queries on behalf of clients. They can spawn executor server processes (ESPs) to achieve parallelism in the execution of queries. Configuration servers (MXOCFG) runs only on the master segment and maintains the NDCS configuration. Terms association server configuration server MXOAS MXAS2 NDCS server 156 Manage Connectivity

157 Stop an NDCS Server Requirement: Only roles that have OPERATOR privileges can perform management tasks. To stop an NDCS server: 1. Under the navigation tree pane, click the Connectivity area. (For more information, see Select an Area (page 35).) 2. In the navigation tree pane, find the system that contains the NDCS server(s) that you want to stop. 3. Expand the system, and click NDCS Services. 4. In the right pane, click the NDCS Server Status tab to display the list of NDCS servers. 5. Select the server that you want to stop. You can select more than one server. 6. Click Stop. The Stopping Server dialog box appears. 7. Click one of these options: NOTE: After you click a stop option, you cannot cancel the operation. [ Stop Immediately ] CAUTION: [ Stop Immediately ] stops the server without waiting to finish any current database statements or sessions. The transaction manager rolls back all uncommitted transactions held by these NDCS servers. All client connections are closed. [ Cancel ] Terms operator privilege NDCS server Display NDCS Services Any user can display NDCS services. To display all NDCS services for a system: 1. Under the navigation tree pane, click the Connectivity area. (For more information, see Select an Area (page 35).) 2. In the navigation tree pane, find the system that contains the NDCS services. 3. Expand the system, and click NDCS Services. Stop an NDCS Server 157

158 4. In the right pane, click the NDCS Services tab to display detailed information about the association and configuration servers: This table describes the fields in the NDCS Services tab: Field Service Name Service Type Process Name State Node Server PIN Port Last Updated Time Description The NDCS service to which the process belongs. Association server or configuration server. Internal operating system process name of the system in which the NDCS service is running. This field is visible only to roles that have OPERATOR privileges. Current state of the service. Processing node (CPU) number where the server is running. Operating system process ID assigned to the component. This field is visible only to roles that have OPERATOR privileges. Port number for the service. Date and time (in the client's local time) of the last update of the service state. Terms NDCS service Start an NDCS Service Requirement: Only roles that have OPERATOR privileges can perform management tasks. Starting an NDCS service changes the state of the service from Stopping to Available To start an NDCS service: 1. Under the navigation tree pane, click the Connectivity area. (For more information, see Select an Area (page 35).) 2. In the navigation tree pane, find the system that contains the NDCS services. 3. While still in the navigation tree pane, expand the NDCS Services list for the system. 4. Right-click the name of the service that you want to start, and select Start. This action enables the NDCS service and the following components: 158 Manage Connectivity

159 Association server Configuration server Data sources configured with the automatic startup option If the NDCS service state does not change to the Available state, contact HP support. Learn About the Association Servers (page 156) Terms operator privilege Association server Configuration server Data sources NDCS service Stop an NDCS Service Requirement: Only roles that have OPERATOR privileges can perform management tasks. When you stop an NDCS service, the configuration server remains Available, but the association server changes from the Available state to the Stopping state. This operation effectively stops any data source that is currently started, except for the Admin_Load_DataSource, which must remain started to allow HPDM to continue managing connectivity. Because the Admin_Load_DataSource remains started, the association server transitions to the Stopping state but does not transition to the Stopped state. To stop an NDCS service: 1. Under the navigation tree pane, click the Connectivity area. (For more information, see Select an Area (page 35).) 2. In the navigation tree pane, find the system that contains the NDCS service(s) that you want to stop. 3. Expand the system, and click NDCS Services. 4. While still in the navigation tree pane, right-click the name of the service that you want to stop, and select Stop. The Stopping Service dialog box appears. 5. Type a reason for stopping the service. 6. Click one of these options: NOTE: After you click a stop option, you cannot cancel the operation. [ Stop on Client Disconnect ] [ Stop Immediately ] CAUTION: The various stop options available in HPDM only disable the NDCS service. To fully stop the NDCS service, you must stop the association server process. [ Stop Immediately ] disables the NDCS service without waiting for the NDCS servers to finish current database statements or sessions. The transaction manager rolls back all uncommitted transactions held by these NDCS servers. All client connections are closed. [ Cancel ] cancels the stop operation. NOTE: After you click one of the Stop options, you cannot cancel the operation. Terms operator privilege association server Stop an NDCS Service 159

160 Start and Stop Server Traces Requirement: Only roles that have OPERATOR privileges can perform management tasks. To start tracing for a data source: 1. Under the navigation tree pane, click the Connectivity area. 2. In the navigation tree pane, find the system that contains the data source(s) that you want to trace. 3. Expand the system, and click NDCS Services. 4. In the right pane, click the Data Source Status tab to display the list of services. 5. In the Tracing column, click the Tracing check box for each data source that you want to trace. 6. Click [ Apply ]. To stop tracing for a data source: 1. Under the navigation tree pane, click the Connectivity area. 2. In the navigation tree pane, find the system that contains the data source(s) that you want to trace. 3. Expand the system, and click NDCS Services. 4. In the right pane, click the Data Source Status tab to display the list of services. 5. In the Tracing column, clear the Tracing check box for each data source that you want to stop tracing. 6. Click [ Apply ]. Learn About Server Traces (page 160) Terms operator privilege Learn About Server Traces Data from server traces is stored in the EMS log in message ( See the Trace Event Message Format (page 56)). The tracing facility generates a pair of messages for each function that is traced: First message contains the input parameters to the function Second message contains the output from the function Once a trace is enabled for a data source, all servers that can write to the EMS alternate collector begin writing the input and the output data for each function executed during the trace period. The following data is collected for each function: Session ID Component name Object reference Sequence number Input values to the function or output from the function Start and Stop Server Traces (page 160) View Dial Out and Database Events (page 56) 160 Manage Connectivity

161 14 Manage NDCS Privileges Display NDCS Privileges NDCS privileges define the type of access that the members of a role have to data source configurations and other connectivity information on the Neoview platform. Only a member of a role having OPERATOR privileges can display NDCS privileges. Initially, only users belonging to the following roles have OPERATOR privileges: SUPER.SUPER SUPER.SERVICES ROLE.DBA ROLE.SECMGR A role having the OPERATOR privilege can perform administrative tasks, such as managing data source configurations, NDCS services, data sources, and servers, by making changes to status and configuration. This example shows a system that has three roles with OPERATOR privileges. The Grantor column indicates the role that granted privileges to each NDCS operator: To display the current NDCS privileges and grantors: 1. Under My Systems, select the system for which you want to display privileges. 2. In HPDM, select the Connectivity area. For more information, see Select an Area (page 35). 3. In the right pane, click the NDCS Privileges tab. Grant NDCS Privileges (page 161) Revoke NDCS Privileges (page 162) Terms operator privilege Grant NDCS Privileges Initially, only users who belong to the following roles can grant OPERATOR privileges: SUPER.SUPER SUPER.SERVICES ROLE.DBA ROLE.SECMGR In addition, privileges can be granted only to roles, not to individual users. After privileges have been granted, users in the new OPERATOR role can grant OPERATOR privileges to other roles. To grant OPERATOR privileges to a role: Display NDCS Privileges 161

162 1. Under My Systems, select the system having the role for which you want to grant privileges. 2. In HPDM, select the Connectivity area. For more information, see Select an Area (page 35). 3. In the right pane, click the NDCS Privileges tab. 4. Click [ Grant ]. The Grant Operator Privilege dialog box appears. 5. In the Grantee Role Name field, specify the user role. 6. Click [ Grant ]. Display NDCS Privileges (page 161) Revoke NDCS Privileges (page 162) Terms operator privilege Revoke NDCS Privileges Only a member of a role having OPERATOR privileges can revoke NDCS privileges. In addition, only the grantor (the specific user ID that granted OPERATOR privileges) can revoke privileges for a grantee. Privileges for the SUPER.SUPER role cannot be revoked. To revoke NDCS privileges: 1. Under My Systems, select the system having the role for which you want to revoke privileges. 2. In HPDM, select the Connectivity area. For more information, see Select an Area (page 35). 3. In the right pane, click the NDCS Privileges tab. 4. Click to select the NDCS Operator whose privileges you want to revoke. If you are the user who granted OPERATOR privileges as indicated in the Grantor column, you can revoke these privileges. 5. Click [ Revoke ]. The Revoke dialog box asks you to confirm the operation. 6. Click [ Yes ] or [ No ]. Display NDCS Privileges (page 161) Grant NDCS Privileges (page 161) Terms operator privilege 162 Manage NDCS Privileges

163 15 Manage Procedures Display Procedures See Display Procedures and Their Properties (page 84). Upload a JAR File This procedure uploads an SPJ JAR file (or multiple JAR files) from a client workstation to the Neoview platform. When you upload a JAR file to the Neoview platform, the Procedure Code File Tool copies the JAR file(s) to one of two folders that you select: A folder corresponding to your user role on the Neoview platform. For example, if your role is ROLE.DBA1, the Procedure Code File Tool copies your uploaded JAR file(s) to the ROLE.DBA1 folder. All the members of your user role can access the files in this folder. A private folder corresponding to your user ID on the Neoview platform. For example, if your user ID is OPSDBA29, the Procedure Code File Tool copies your uploaded JAR file(s) to the OPSDBA29 folder. Only you can view and access the files in your private user folder. Note these considerations for uploading JAR files: If you upload a JAR file that has the same name as a JAR file that already exists in the folder corresponding to your role on the Neoview platform, HPDM prompts you for confirmation before overwriting the contents of the JAR file. The Procedure Code File Tool will not upload: A JAR file that is empty. A file that lacks a.jar extension. A file that exceeds an internal size threshold specified by a WMS service configured for HPDM. To upload a JAR file: 1. In HPDM, select the Database area. For more information, see Select an Area (page 35). 2. In the navigation tree pane, right-click a schema name, and select Procedure Code File Tool. The Procedure Code File Tool window appears. 3. In the left pane of the Procedure Code File Tool window, click the folder into which you want to upload the JAR file. If you click the folder corresponding to your role, all users belonging to that role can view the JAR file. If you click your private user folder, only you can view the JAR file. 4. Click Upload. The Upload Code Files dialog box appears. 5. Navigate to and select the SPJ JAR file(s) on your client workstation. 6. Click Open to upload the JAR file(s) to the Neoview platform. 7. In the left pane of the Procedure Code File Tool, open the folder for your Neoview role or user ID and notice that the JAR file(s) appear within it. NOTE: Note that if you selected the role folder, the Procedure Code File Tool shows all of the JAR files for the Neoview role that you used to connect to the current system. The role is your default role unless you specified a different role in the system definition. 8. Open the JAR file folder to display the class files within it, and click one of the class files to display the method names and signatures. 9. When done, click File > Exit or the Close button ( ) to close the Procedure Code File Tool dialog box and return to the HPDM main window. Display Procedures 163

164 Download a JAR File This procedure downloads one or more SPJ JAR files from the Neoview platform to a client workstation. When you download a JAR file to a client workstation, the original JAR file is retained on the Neoview platform. Use this procedure to download one or more JAR files: 1. In HPDM, select the Database area. For more information, see Select an Area (page 35). 2. In the navigation tree pane, right-click a schema name, and select Procedure Code File Tool. The Procedure Code File Tool window appears. 3. In the left pane of the Procedure Code Files Tool, open the folder for your Neoview role or user ID to display the JAR files within it. NOTE: If you select the folder for your role, the Procedure Code File Tool shows all of the JAR files for the Neoview role that you used to connect to the current system. The role is your default role unless you specified a different role in the system definition. 4. In the right pane, select the row for each JAR file that you want to download. TIP: To select a row, click the File Size value rather than the File Name. If you click the File Name, HPDM changes the display to provide detailed information about the selected JAR file. 5. Click [ Download ]. The Browse For Folder dialog box appears. 6. In the Browse For Folder dialog box, navigate to the folder on your client workstation where you want to download the JAR file(s). 7. Click [ OK ] to download the JAR file(s). 8. When you are done, click File > Exit or the Close button ( ) to close the Procedure Code File Tool dialog box and return to the HPDM main window. Rename a JAR File This procedure renames a JAR file on the Neoview platform. CAUTION: Renaming a JAR file might leave a dangling stored procedure reference in the Neoview database. A dangling reference might cause errors when an application tries to execute the stored procedure. To prevent dangling references, drop the stored procedure from the database before renaming the JAR file. After renaming the JAR file, re-create the stored procedure in the Neoview database. For information about dropping a stored procedure, see Drop a Procedure (page 169). To rename a JAR file: 1. In HPDM, select the Database area. For more information, see Select an Area (page 35). 2. In the navigation tree pane, right-click a schema name, and select Procedure Code File Tool. The Procedure Code File Tool window appears. 3. In the left pane of the Procedure Code Files Tool, open the folder for your Neoview role or user ID to display the JAR files within it. NOTE: If you selected the folder for your role, note that the Procedure Code File Tool shows all of the JAR files for the Neoview role that you used to connect to the current system. The role is your default role unless you specified a different role in the system definition. 4. Select the JAR file that you want to rename. You can select a JAR file icon in the left pane or the row for the JAR file in the right pane of the Procedure Code File Tool. 164 Manage Procedures

165 NOTE: You can rename only one JAR file at a time. TIP: To select a row, click the File Size value rather than the File Name. If you click the File Name, HPDM changes the display to provide detailed information about the selected JAR file. 5. Click Rename. A Confirm dialog box asks you to confirm the Rename operation. 6. Click Yes to continue. Otherwise, click No to end the operation. 7. When you are done, click File > Exit or the Close button ([ X ]) to close the Procedure Code File Tool dialog box and return to the HPDM main window. Delete a JAR File This procedure deletes one or more JAR files on the Neoview platform CAUTION: Deleting a JAR file might leave a dangling stored procedure reference in the Neoview database. A dangling reference might cause errors when an application tries to execute the stored procedure. To prevent dangling references, drop the stored procedure from the database before deleting the JAR file. For information about dropping a stored procedure, see Drop a Procedure (page 169). To delete a JAR file: 1. In HPDM, select the Database area. For more information, see Select an Area (page 35). 2. In the navigation tree pane, right-click a schema name, and select Procedure Code File Tool. The Procedure Code File Tool window appears. 3. In the left pane of the Procedure Code Files Tool, open the folder for your Neoview role or user ID to display the JAR files within it. NOTE: If you selected the folder for your role, note that the Procedure Code File Tool shows all of the JAR files for the Neoview role that you used to connect to the current system. The role is your default role unless you specified a different role in the system definition. 4. Select the JAR file(s) that you want to delete. TIP: To select a row, click the File Size value rather than the File Name. If you click the File Name, HPDM changes the display to provide detailed information about the selected JAR file. 5. Click Delete. A Warning dialog box asks you to confirm the Delete operation. 6. Click Yes to continue. Otherwise, click No to end the operation. 7. When you are done, click File > Exit or the Close button ( ) to close the Procedure Code File Tool dialog box and return to the HPDM main window. Create a Procedure Create Procedure registers an existing Java method as a stored procedure in Java (SPJ) within Neoview SQL. NOTE: HPDM creates procedures with default privileges only. For more information about privileges for SPJs, see the Neoview Guide to Stored Procedures in Java. Requirements: Delete a JAR File 165

166 You must be the owner of the schema or have SUPER.SUPER or SUPER.SERVICES privileges, and have read access to the.jar file that contains the SPJ Java method. The catalog and schema of the SPJ must already exist. To create a procedure: 1. In HPDM, select the Database area. For more information, see Select an Area (page 35). 2. Expand the navigation tree pane so that you can see the name of the schema in which you want to create the procedure and the Procedures folder under the schema. 3. Right-click the Procedures folder, and select Create Procedure. The Create Procedure dialog box appears. 4. In the Name field, enter a name for the stored procedure. For detailed information about the Name field, see Use the Create Procedure Dialog Box (page 167). 5. In the Code group box, click [ Browse ] to open the Procedure Code File Browser. Use the browser to select a method from a JAR file. NOTE: The left pane of the Procedure Code File Browser shows folders for your Neoview role and private user ID. If you select the role folder, the Procedure Code File Browser shows all of the JAR files for the Neoview role that you used to connect to the current system. The role is your default role unless you specified a different role in the system definition. If an SPJ JAR file does not exist on the Neoview platform, you can upload it. See Upload a JAR File (page 163). 6. In the Parameters group box, verify that the SQL parameters are mapped correctly to the Java parameters of the SPJ method. NOTE: The result set parameters (java.sql.resultset[]) in the Java signature do not have corresponding SQL parameters. a. To change an SQL parameter, such as the name of the parameter, the SQL data type, or the parameter mode (direction) select the parameter and click [ Edit ]. The Edit Parameter dialog box appears. b. In the Edit Parameter dialog box, enter a new name for the parameter, select a different SQL data type, if permitted, or select a different parameter mode (direction), if permitted. When changing the parameter name, note that the parameter name: Is not case-sensitive Must not be a reserved word Must not contain spaces Must begin with a letter, digit, or underscore When changing the SQL data type, select a data type that is appropriate for the parameter of the underlying Java method. For more information, see the Neoview Guide to Stored Procedures in Java. For information about SQL data types, see the Neoview SQL Reference Manual. For character string parameters, select either ISO88591 or UCS2 depending on the column definition and the character set configuration of your Neoview platform. For guidelines, see the Neoview Character Sets Administrator's Guide. c. Click [ OK ] to accept the changes, or click [ Cancel ] to quit the Edit Parameter dialog box. d. Repeat steps a to c for each parameter that you want to change. 7. In the Attributes group box, if your SPJ method returns result sets, enter the maximum number of result sets to be returned for Number of dynamic result sets. The valid range 166 Manage Procedures

167 is 1 to 255 inclusive. The actual number of result sets returned by the SPJ method can be less than or equal to this number. NOTE: The Number of dynamic result sets control is enabled only if the method signature contains a java.sql.resultset[] object. 8. If your SPJ method performs any SQL operations, select the Accesses Database option. NOTE: If you do not select the Accesses Database option and your SPJ method performs SQL operations, Neoview SQL returns an error when trying to execute the procedure. 9. Click [ Create ] to create the procedure. Use the Create Procedure Dialog Box (page 167) Use the Create Procedure Dialog Box This table shows reference information for the Create Procedure dialog box: Group Box Name Code Parameters Control or Field Name Code File Class Name Method Name Name Direction SQL Data Type Java Data Type [ Edit ] Action Enter a name for the new procedure. The name must be unique and must not exist for any procedure, table, or view in the same schema. The procedure name is not case-sensitive. Neoview SQL automatically qualifies the procedure name with the name of the schema in which you are creating the procedure. For example, if you enter monthlyorders as the procedure name, Neoview SQL stores the procedure as schema-name.monthlyorders. Click [ Browse ] to navigate to a.jar file. NOTE: Only.jar files that you have uploaded or.jar files that have been uploaded by members of the Neoview role to which you belong are visible to you. Select a class. When you select a class, the method names and parameter types for that class appear in the right pane. NOTE: Only methods that can be used in a procedure are visible. For details, see Use a Method in a Procedure (page 168). Is the name for this Neoview SQL parameter. IN passes data to a procedure INOUT passes data to and accepts data from a procedure. The parameter must be an array. OUT accepts data from a procedure. The parameter must be an array. Displays the Neoview SQL data type that is the best match for the Java signature in the Java Data Type column. Displays the signature for the Java method that you selected. Click to edit the selected parameter. Use the Create Procedure Dialog Box 167

168 Group Box Attributes Control or Field Number of dynamic result sets Accesses Database Action Controls the maximum number of result sets the procedure can return. This control is enabled only if the method signature contains a java.sql.resultset[] object. If the method contains a result set object, the valid range is 1 to 255. This value is automatically set to zero if the selected Java method does not have a java.sql.resultset[] object. If selected, the procedure performs SQL operations. If cleared, the procedure does not perform SQL operations. NOTE: Neoview SQL returns an error if this attribute is cleared and the procedure performs SQL operations. Create a Procedure (page 165) Use a Method in a Procedure To be used in a procedure, a Java method must: Be qualified as public static void. Have a java.sql.resultset[] parameter at the end of the method signature if the method uses result sets. NOTE: There can be more than one java.sql.resultset[] parameter, but they must all be at the end of the method signature. Have these parameter types: Parameter Type or Class character Type java.lang.string java.lang.string[] numeric java.lang.integer java.lang.integer[] java.lang.long java.lang.long[] java.lang.float java.lang.float[] java.lang.double java.lang.double[] java.math.bigdecimal java.math.bigdecimal[] date/timestamp java.sql.date java.sql.date[] java.sql.time java.sql.time[] java.sql.timestamp java.sql.timestamp[] 168 Manage Procedures

169 Parameter Type or Class primitive Type short short[] int int[] long long[] float float[] double double[] result sets java.sql.resultset[] For more information, see the Neoview Guide to Stored Procedures in Java. Drop a Procedure To drop a procedure, you must own the procedure, have SUPER.SUPER privileges, or have the necessary DDL privileges to drop the procedure. The schema owner can grant such privileges to other users or roles. For example, if the schema owner granted your role privileges to drop all objects, members of your role could drop procedures. For more information about the GRANT SCHEMA statement, see the Neoview SQL Reference Manual. To drop a procedure: 1. Under the navigation tree pane, click the Database area. 2. Under My Systems, expand the tree for the Neoview platform containing the procedure until you can see the schema folder and the Procedures folder underneath it. 3. Expand the Procedures folder. 4. Right-click the name of the procedure that you want to drop, and select Drop Procedure. HPDM asks you to confirm the operation. 5. Click [ Yes ] to continue or [ No ] to quit the operation. Drop a Procedure 169

170 170

171 16 Use the System Monitor Display the System Monitor The system monitor is a tool within HPDM that displays status and performance data for the Neoview platform. The displayed status and performance data includes seven performance metrics and four system status icons. NOTE: The system monitor is visible for both connected and disconnected systems. The system monitor uses TCP/IP UDP datagrams to communicate with a server component on the Neoview platform. UDP communication allows the system monitor to display useful information even without an active ODBC connection to the system. To display the system monitor: 1. In the navigation tree pane, select the system that you want to monitor. 2. Select the Monitoring area. For more information about areas, see Select an Area (page 35). 3. In the right pane, click the Monitoring tab. See the Parts of the System Monitor (page 171) Understand the Performance Metrics (page 172) See the Parts of the System Monitor The system monitor shows performance metrics and system status icons. You can display the performance metrics as a bar graph, a timeline, or a combination of both. In the bar graph (Bar Graph tab), each metric occupies a separate row with a footer. The footer shows the name of the metric. Each bar represents a processing node (CPU), and each column represents a segment. This figure shows a bar graph consisting of two segments (32 CPUs). Display the System Monitor 171

172 Configure System Monitor Options (page 176) Understand the Performance Metrics (page 172) Understand the System Status Icons (page 174) Terms segment Understand the Performance Metrics The system monitor shows seven performance metrics: Metric CPU Busy Disk I/O Cache Hits Dispatch Swap Free Memory Queue Length Description The average busy value of the specified processing node (CPU) over the last refresh interval. The average number of disk I/O operations over the last refresh interval. The average number of cache accesses over the last refresh interval. The average number of process-context switches over the last refresh interval. The average number of page faults (swaps) over the last refresh interval. The amount of free memory currently available (in megabytes). The number of processes currently waiting to be dispatched (on the ready queue). The default refresh rate for all performance metrics is 2 seconds. However, the refresh rate is configurable. See Configure System Monitor Options (page 176). Configure System Monitor Options (page 176) 172 Use the System Monitor

173 Use Tooltips to Show the Value of a Performance Metric (page 173) Use Tooltips to Show the Value of a Performance Metric When the system monitor bar graph (Bar Graph tab) is displayed, you can quickly obtain the current value of a metric for a given segment and CPU. To obtain the current value, hold the cursor over the bar for the CPU. A tooltip caption shows the segment number, the CPU number, and the approximate value of the bar at the instant the cursor moved over it: Terms segment About the Timeline Tab The Timeline tab shows a graph of each performance metric over time. The graph displays the aggregated (arithmetic mean) value for the entire system over time. Timelines enable you to see a trend for a given metric over a specified number of data points (the Max Range). A data point is a 2-second interval. The timeline graph has no units; a vertical scale is provided only for comparison. The trace lines use the same colors as the bar graph bars in the Bar Graph tab. You can configure the number of data points, the background color, and the trace line colors. Configure System Monitor Options (page 176) Use Tooltips to Show the Value of a Performance Metric 173

174 About the Hybrid Tab The Hybrid tab shows a bar graph and a set of timelines side by side: About the Timeline Tab (page 173) Configure System Monitor Options (page 176) Understand the System Status Icons The four system status icons (Connectivity, Disks, Transactions, and Alerts) provide an at-a-glance summary of the up or down state of various subsystems and tell you if any alerts are present: 174 Use the System Monitor

175 This table describes the icons: Icon Connectivity Disks Transactions Alerts Description Icon for the association servers. Indicates if $MXOAS and $MXAS2 are running. $MXOAS is the component of the Neoview Database Connectivity Service (NDCS) that receives client connection requests for database access and associates the requestor with a server to execute the requested access. $MXAS2 is the component of NDCS that receives connection requests from the Neoview Transporter and associates that requestor with a server to execute the requested database access. Icon for the disk subsystem. Indicates if the disk drives on all segments are accessible. If a disk volume (both the primary and the mirror) is down, the disk is reported as Down. Other errors are reported as a Warning, including the condition where status information cannot be obtained because of extremely high disk activity. Only disks with errors are reported. If all disks are operational, a message to that effect is displayed. Icon for the Transaction Management Facility (TMF), which provides transaction services. The icon shows if TMF is started or not (reported as a Down condition), if transactions can be created or not (reported as a Down condition), and if there are any hung transactions (reported as a Down condition). Errors, warnings, or informational messages that need your attention. See Get Information About Alerts (page 183). NOTE: The Alerts icon requires an ODBC connection and is gray until you connect to a system. The icon shape and color communicate the general health of each subsystem: Icon Color State Description Gray Connecting The client is waiting to establish a connection with the server. Green Up The subsystem is operating normally. Yellow Warning The subsystem has a minor problem. Red Down The platform has an alert. At least one component has failed or is down. Get Details About System Status Icons (page 175) Get Information About Alerts (page 183) Get Details About System Status Icons To get more information about the Connectivity, Transactions, or Disks icons, click any of these icons. An information dialog box appears. For example: Get Details About System Status Icons 175

176 For more information about the Alerts icon, see Get Information About Alerts (page 183). Understand the System Status Icons (page 174) Get Information About Alerts (page 183) Configure System Monitor Options The system monitor options pane allows you to control the display of performance metrics, including the bar colors, the refresh rate, and other parameters. To display the system monitor options pane: 1. Under the My Systems folder, select the system that you want to monitor. NOTE: You do not have to be connected to a system to use the system monitor. The system monitor communicates over UDP (not ODBC) with a server component on the Neoview platform. However, the Alerts icon and Alerts tab require an active ODBC connection. For Alerts, you must connect to the server. 2. Click the Monitoring area. For more information about areas, see Select an Area (page 35). 3. In the right pane, right-click anywhere in the Bar Graph, Timeline, or Hybrid tabs, and select Configure System Monitor Options. The system monitor options pane is displayed. To use the system monitor options pane, change a setting or select a new option and click [ Apply ]. To cancel any changes, click [ Cancel ]. Both the [ Apply ] and [ Cancel ] buttons return you to the system monitor tabs from which you started. 176 Use the System Monitor

177 This table describes the system monitor options and settings: Option or Setting Port Refresh Rate Options Active System Status Alerts System Status Location Metric and 100% Settings Description This option shows the Port Number for connecting to the Neoview platform. The default number is 4746, which should satisfy most installations. If the system monitor fails to return data and you suspect that a different port was assigned, contact your HP support representative. The Fixed Incoming option is provided for troubleshooting at sites where the client workstation is behind a firewall. Selecting this option activates a client port that you can specify. The default client port number is 0 (Windows reads 0 as a placeholder for the next available outgoing port). The Fixed Incoming option is useful because the System Monitor both receives and sends data to the Neoview platform. The System Monitor uses a dynamic port for incoming communications, which means it doesn't know the incoming port number until a connection is made. This requires opening a firewall to a large range of ports, which can be undesirable. To avoid opening up a large number of ports, you can specify a fixed incoming port using this option. The refresh rate is the amount of time that the client waits before requesting new data from the server. The default rate is 2 seconds. You can change the refresh rate to another value in the range 2 through 500 seconds. NOTE: The server does not always return the requested data immediately. For instance, if the refresh rate is set to 5 seconds, the client requests data from the server every 5 seconds. But the server can take an additional 2 to 4 seconds to respond with the data. In this sense, the refresh rate is closer to an update request interval. Options that allow you to show or hide these system status icons: Connectivity Transactions Disks Alerts To hide an icon, deselect the appropriate option. Controls where the system status icons appear. You can display the icons above or below the bar graph or timeline information. Control the bar/line color, show/hide option, and 100% setting for performance metrics. For example: The bar/line color is the color of the specified bar in the bar graph or the line in the timeline. See Change a Color Option (page 179). The show/hide option controls whether or not the metric is displayed. When a show/hide options is selected, the performance metric is displayed. When the option is deselected, the metric is hidden. The 100% setting is the highest non-error value that the system monitor is currently configured to display. A value higher than the 100% value causes the bar color to change. A value higher than the 100% setting is not reflected by the bar but is captured in the tooltip information. Chart Background Options Options that control the background colors for the timeline, bar graph, and the lost-connection condition. The Lost Connection Background Color is implemented only if the Timeout Color option is selected. See Change a Color Option (page 179). Configure System Monitor Options 177

178 Option or Setting Additional Color Options Aggregation Options Timeout Color Additional Settings Timeline Options Description Options that control the bar color for the mouse-over, threshold-exceeded, and CPU-down conditions. See Change a Color Option (page 179). Options that control the way data collected (aggregated) for each bar in the bar graph (Bar Graph tab): No Aggregation displays one bar per CPU (16 bars per segment). For example, the client shows 64 bars (16 CPUs per segment) for a four-segment platform. Segments displays one bar per segment. For example, the client shows four bars for a four-segment platform. Each bar represents the average value for a given metric for the segment. If a metric exceeds its 100% setting, the bar color changes to the Threshold Exceeded bar color. Special viewing features are available when segment aggregation is selected. See Use the System Monitor With Segment Aggregation (page 178). Controls the chart background color when the connection with the server is lost. If this option is selected, the Lost Connection Background Color is implemented when a connection is lost. The Lost Connection Background Color can help you recognize when the data provided by the client is no longer valid. The System Monitor retries the connection every couple of seconds for about 10 minutes. After 10 minutes, an error message is displayed. Controls the Show Separators option. Segment separators are the vertical lines on the system monitor screen that mark each segment in a Neoview platform. These lines appear by default, but you can hide them by deselecting this option. To specify the amount of time captured by a timeline, enter a number in the Max Range field. The default value is 50. This is the number of data points (intervals) that you want the timeline to display. Data points are collected approximately every 2 seconds. Therefore, specifying a Max Range of 50 intervals produces a timeline of about 100 seconds. Terms segment Use the System Monitor With Segment Aggregation If segment aggregation is selected in the system monitor options pane, the display changes to show only one bar per segment. For example, if your system has four segments, the system monitor shows four colored bars for each metric. Each bar represents the average (arithmetic mean) value for that segment. Clicking any of the segment bars in the bar graph area of the Bar Graph tab or Hybrid tab changes the display to drill down on that segment. The display shows one bar for every CPU in the selected segment. NOTE: When the display is focused on one segment, you can no longer view bar graph information for any other segments. To return to the full system aggregated view, click the Full System View link at the top of the system monitor pane: 178 Use the System Monitor

179 Configure System Monitor Options (page 176) Terms segment Change a Color Option Color options appear as bar/line-color buttons in the system monitor options pane. To change a color option: 1. Display the system monitor options pane, as described in Configure System Monitor Options (page 176). 2. Click the bar/line-color button for the metric or background whose color you want to change. The color palette dialog box appears. 3. Select a color from the color palette. 4. Click [ OK ]. 5. Click [ Apply ]. Configure System Monitor Options (page 176) Change a Color Option 179

180 180

181 17 Respond to Alerts Display the Alerts Tab NOTE: Diagnostic information displayed by the Alerts tab is intended for use by HP support. This information is not documented for customer use. If you have questions about an alert condition, contact your HP support representative. Special privileges are required to display the Alerts tab. See Understand Privileges for Viewing and Updating Alerts (page 182). To display the Alerts tab: 1. In the My Systems folder of the navigation tree pane, select the system for which you want to view alerts. 2. Select the Monitoring area. For more information about areas, see Select an Area (page 35). 3. Use either of these methods: In the right pane, click the Alerts tab. Double-click the Alerts system status icon. Understand Alerts (page 182) See the Parts of the Alerts Tab (page 181) Understand Privileges for Viewing and Updating Alerts (page 182) Understand the System Status Icons (page 174) See the Parts of the Alerts Tab Understand Alerts (page 182) Understand Privileges for Viewing and Updating Alerts (page 182) Display the Alerts Tab 181

182 Understand Alerts NOTE: Diagnostic information displayed by the Alerts tab is intended for use by HP support. This information is not documented for customer use. If you have questions about an alert condition, contact your HP support representative. Alerts are alarms or incident reports generated by internal subsystems. The system monitor provides a system status icon to summarize the alert condition, and the Alerts tab provides detailed information about specific alerts. Alerts information is displayed only if the Neoview platform is loaded with Release 2.4 Service Pack 1 (SP1) or later software and you have sufficient privileges to view the alerts. The Alerts tab fetches alert details from a Neoview Repository view: NEO.HP_METRICS.ALERTS_VW2 This view is a merge of the ALARMS and DIALOUTS tables in the repository. HPDM uses a query to fetch this information. The query results are displayed in the Alerts tab data grid with the most recent alerts at the top of the grid. The grid column names are the column names of the NEO.HP_METRICS.ALERTS_VW2 Repository view. By default, alert details are refreshed every 3 minutes, but the refresh rate is configurable. After 30 days (based on the alert creation date), alerts are no longer displayed, but you can change the display period by configuring the Time Range in the Alerts Options dialog box. Control the Refresh of Alerts (page 187) Use the Alerts Options Dialog Box (page 186) Understand Privileges for Viewing and Updating Alerts (page 182) Terms alert Understand Privileges for Viewing and Updating Alerts By default, SUPER.SUPER, SUPER.SERVICES, and ROLE.DBA can view and update alerts. Other users can view alerts if they are granted SELECT privileges on the NEO.HP_METRICS.ALERTS_VW2 view, or if they are granted administrator privileges by an administrator user. Users who have SELECT privileges on the NEO.HP_METRICS.ALERTS_VW2 view cannot necessarily update alerts. Users can update alerts if they are granted administrator privileges by an administrator user or if they are granted UPDATE privileges on these columns of the Alarms table: STATUS NOTES LAST_UPDATE_UTC_TS LAST_UPDATE_LCT_TS CLOSED_UTC_TS CLOSED_LCT_TS To view the alerts state and the details, a user must have SELECT privileges on the NEO.HP_METRICS.ALERTS_VW2 view. This view is created by the Neoview Repository and by default secured for SUPER.SUPER, SUPER.SERVICES, and ROLE.DBA. The SUPER.SUPER user has implicit update privileges. For all other users, HPDM checks the SQL privileges to verify that the current logged on user or role has update privileges for the MANAGEABILITY.METRICS.ALARMS base table. This includes SUPER.SERVICES, ROLE.DBA, and all other roles. HPDM checks for update privileges on the whole table first. If those privileges 182 Respond to Alerts

183 are not found, HPDM checks to see if the user has update privileges on the ALARM_STATUS column. If the current user has update privileges, the ALARM_STATUS column in the Alerts data grid displays a menu with selectable update states (ACKNOWLEDGED and USERCLOSED): In addition, the ALARM_NOTES column provides a [... ] button that opens the Alert Notes Editor dialog box: If the current user does not have update privileges, the menu and notes button are not displayed. Update an Alert (page 189) Make Notes About an Alert (page 190) Display Views and Their Properties (page 74) Terms administrator Get Information About Alerts The Alerts icon in the system monitor shows the alert status. When you position your pointer over the icon, a tooltip shows the number of open errors, warnings, and informational messages: Get Information About Alerts 183

184 Unlike the Connectivity, Disks, and Transactions icons, the Alerts icon requires an ODBC connection to fetch the alerts status. This table describes how to interpret the alert state based on the color of the Alerts icon: Alerts Icon Color Gray Red Yellow Green Description A gray icon signals one of these conditions: The system is not connected. The logged on user does not have the required privileges to view alerts. The repository view for alerts does not exist. At least one OPEN or ACKNOWLEDGED alert is present and has an ERROR alert level. At least one OPEN or ACKNOWLEDGED alert is present and has a WARN alert level. No ERROR or WARN alerts are present, but informational (INFO) alerts might be present. Understand Row Detail Information for Alerts (page 184) Understand the System Status Icons (page 174) Understand Row Detail Information for Alerts This table describes the row detail information for the Alerts data grid. For more information about displaying row details, see Get Row Details for a Data Grid (page 49). NOTE: Diagnostic information displayed by the Alerts tab is intended for use by HP support. If you have questions about an alert condition, contact your HP support representative. Field LEVEL ALARM_RESOURCE_NAME ALARM_SPECIFIC_PROBLEM ALARM_SEGMENT ALARM_SEVERITY ALARM_STATUS ALARM_CREATE_LCT_TS ALARM_TYPE Description A computed field with an icon that indicates the ERROR, WARN, or INFO status. The name of the resource that generated the alarm. Information to describe why the ALARM_PROBABLE_CAUSE occurred. For example, if the probable cause is an equipment malfunction, this field might say that the temperature exceeded normal limits. The segment number where the problem originated. CRITICAL, FATAL, INDETERMINATE, INFORMATION, MAJOR, MINOR, OTHER, or WARNING. The severity is determined by the underlying alarm. NOTE: The severity for Neoview Management Dashboard alarms is always INDETERMINATE. ACKNOWLEDGED: An operator acknowledged the alarm, but it is still open. AUTOCLOSED: Neoview software deleted the alarm, indicating that the problem no longer exists. OPCLOSED: An HP support person closed the alarm manually. OPEN: An alarm was created. USERCLOSED: An operator used HPDM to close the alarm. UNKNOWN: The status is unknown. The ANSI timestamp in local civil time (LCT) when the alarm was created. This is the local time for the Neoview platform. NVMD for Neoview Management Dashboard alarms. OSM for Open System Management alarms. 184 Respond to Alerts

185 Field ALARM_NOTES ALARM_PROBABLE_CAUSE ALARM_COUNTER IR_ID IR_SEVERITY IR_STATUS ALARM_CREATE_UTC_TS* ALARM_CLOSED_UTC_TS* ALARM_CLOSED_LCT_TS* ALARM_EVENT_NUMBER* ALARM_SSID* ALARM_IR_CREATED* ALARM_LAST_UPDATE_UTC_TS* ALARM_LAST_UPDATE_LCT_TS* IR_SEGMENT* IR_DETECTED_UTC_TS* IR_DETECTED_LCT_TS* IR_DELIVERED_UTC_TS* IR_DELIVERED_LCT_TS* IR_LAST_UPDATE_UTC_TS* Description Notes about the alarm that can only be added manually by an HPDM operator. The likely cause of the alarm. The number of internal events generated for the alarm. The segment-local identification number associated with the incident report (IR). The ID is incremented for every new incident report. CRITICAL, FATAL, INDETERMINATE, INFORMATION, MAJOR, MINOR, OTHER, or WARNING. The severity is determined by the underlying alarm. The delivery status of an incident report (IR). Possible values are: CREATED, DELIVERED, FAILED DELIVERY, and UNKNOWN. This column indicates that a dial-out was generated by the Neoview platform, but not necessarily that the dial-out was successfully received by HP support. The ANSI timestamp in universal coordinated time (UTC) when the alarm was created. The ANSI timestamp when the alarm was closed, using the generated timestamp in universal coordinated time (UTC). The ANSI timestamp when the alarm was closed in local civil time (LCT). The EMS event number associated with the alarm. The subsystem ID for the event that generated the alarm. An indication of whether or not an IR is expected to be created, with the values Y (yes) or N (no). The timestamp in universal coordinated time (UTC) when the alert row was last updated. An alarm can be updated because internal events are generated for the alarm or because someone updated the notes or status for the alert row in HPDM. The timestamp in local civil time (LCT) when the alert row was last updated. An alarm can be updated because internal events are generated for the alarm or because someone updated the notes or status for the alert row in HPDM. The segment where the incident report was originated. This is the same as the alarm segment. The timestamp in universal coordinated time (UTC) when the problem-management software detected the incident report. The timestamp in local civil time (LCT) when the problem-management software detected the incident report. The timestamp in universal coordinated time (UTC) when the incident report was successfully dialed out. NOTE: This column indicates that a dial-out was generated by the Neoview platform, but not necessarily that the dial-out was successfully received by HP support. The timestamp in local civil time (LCT) when the incident report was successfully dialed out. NOTE: This column indicates that a dial-out was generated by the Neoview platform, but not necessarily that the dial-out was successfully received by HP support. The timestamp in universal coordinated time (UTC) when the incident report was last updated. Understand Row Detail Information for Alerts 185

186 Field IR_LAST_UPDATE_LCT_TS* IR_NOTES* Description The timestamp in local civil time (LCT) when the incident report was last updated. Always blank (for future use). *This field is not displayed by default. Use the Show/Hide Grid Columns command to control the display of this field. See Customize the Data Grid (page 52). Get Row Details for a Data Grid (page 49) Customize the Data Grid (page 52) Terms alert segment Use the Alerts Options Dialog Box To display the Alerts Options dialog box: 1. Display the Alerts tab, as described in Display the Alerts Tab (page 181). 2. Click the [ Alter Alerts Configuration ] button: The Alerts Options dialog box appears. This table describes the alerts options and controls: Option or Control Open Alerts Only All Alerts Show Neoview Management Dashboard Alerts Description Causes the Alerts data grid to display only the open and acknowledged alerts. These are alerts for which the ALARM_STATUS value is OPEN or ACKNOWLEDGED. NOTE: Whether the system monitor is configured to display open alerts or open and closed alerts, the state of the OPEN/ACKNOWLEDGED alerts is used to compute the color of the Alert Status icon, and the closed alerts are purged by the problem-management backend software at periodical intervals. Causes the Alerts data grid to display open and closed alerts. The closed alerts include: Alarms that have been closed by an operator by using HPDM (USERCLOSED) Alarms that have been closed by using another tool (OPCLOSED) Alarms that have been automatically closed by the system (AUTOCLOSED) NOTE: Whether the system monitor is configured to display open alerts or open and closed alerts, the state of the OPEN/ACKNOWLEDGED alerts is used to compute the color of the Alert status icon, and the closed alerts are purged by the problem-management backend software at periodical intervals. Causes the alerts from the Neoview Management Dashboard (ALARM_TYPE NVMD) to be fetched. These alerts are not displayed by default. 186 Respond to Alerts

187 Option or Control Time Range (server side LCT) From Time To Time Day +/ and Hour +/ Buttons Severity/Alert Level Mappings Description Specifies the interval for which data is fetched in the server-side local civil time (LCT). By default, the Alerts data grid fetches alert details for the last 30 days. But you can select other time range options: Custom Range Last Hour Today Last 24 Hours Yesterday This Week Last 7 Days Last Week Last 14 Days Last 30 Days This Month Specifies the start time for fetching data when the Custom Range option is chosen for the Time Range. This is the server LCT time (local civil time). Specifies the end time for fetching data when the Custom Range option is chosen for the Time Range. This is the server LCT time (local civil time). Allow you to fine tune the From Time and To Time values by adding or subtracting days or hours when the Custom Range option is chosen for the Time Range. Allow you to map the Alert Level icons to different severities. The Alerts tab displays three different alert levels (Error, Warning, and Information). However, there are eight different severity levels: Fatal Critical Major Minor Warning Information Other Indeterminate You can map the Alert Level icons to different severities by pressing the down arrow next to an Alert Level column and selecting a different icon: Any mapping changes are persisted across future HPDM sessions. Control the Refresh of Alerts Alerts are refreshed automatically every 3 minutes. A refresh timer controls the refresh interval. When an update is in progress, the refresh timer is paused. If the update completes successfully, the refresh timer is restarted. If for any reason one or more updates fail, the refresh timer remains paused so that you can resolve the issue without losing any update information. You can control the refresh interval and other refresh attributes by using the toolbar buttons at the top of the Alerts tab. Control the Refresh of Alerts 187

188 Click this button... Stop Data Provider Refresh Data Pause Timer Resume Timer Set Refresh Time Alter Alerts Configuration To do this Stop the refresh. Refresh the System Offender data grid at any time. Pause the refresh. Restart the refresh after pausing. Change the refresh interval. See the steps for doing this later in this topic. Control the display of alerts. See Use the Alerts Options Dialog Box (page 186). To change the refresh interval: 1. Display the Alerts tab, as described in Display the Alerts Tab (page 181). 2. Click the [ Set Refresh Time ] button: 3. Select a refresh interval. The timer status bar counts down the new refresh interval in seconds. Suppose the refresh timer is set to a low value (for example, 30 seconds). If you are investigating an alert, you might want to pause the timer so that a refresh doesn't change the data displayed in the data grid. To pause the refresh: 1. Display the Alerts tab, as described in Display the Alerts Tab (page 181). 2. Click the [ Pause Timer ] button. The button changes to a [ Resume Timer ] button, and the timer status bar shows Refresh Paused. 3. To restart the timer click the [ Resume Timer ] button. About the Console Tab (page 191) See the Parts of the Alerts Tab (page 181) Use the Update Alert Dialog Box To display the Update Alert dialog box: 1. Display the Alerts tab, as described in Display the Alerts Tab (page 181). 188 Respond to Alerts

189 2. In the Alerts data grid, right-click any alert (or multiple alerts), and select Update Alert(s). The Update Alert dialog box appears. This table describes the options and fields in the Update Alert dialog box: Option or Field Status Select a predefined note or enter your own Update History Description Allows you to choose between the ACKNOWLEDGED and USERCLOSED statuses. Allows you to select from these options: Alert resolved flags the alert as resolved. False alert flags the alert as a false alarm. Duplicate alert flags the alert as a duplicate. Customer note allows you to type a note or message that relates to the alert(s). Shows information about previous updates, if any, for an alert. This field is present only if previous updates were made. The [ Apply ] button submits the update changes to the server. [ Cancel ] cancels any changes made in the Update Alert dialog box. Update an Alert Updating an alert means changing the status of the alert to a value other then OPEN. You can change the status to ACKNOWLEDGED or USERCLOSED. You can also add information about an alert, as described in Make Notes About an Alert (page 190). To update an individual alert, use either of these methods: NOTE: You must have the necessary privileges before you can update an alert. See Understand Privileges for Viewing and Updating Alerts (page 182). Update the alert directly in the ALARM_STATUS column: 1. Click the down arrow in the ALARM_STATUS column for the alert that you want to update, and select ACKNOWLEDGE or USERCLOSED. Use this value ACKNOWLEDGED USERCLOSED To indicate that... An operator has viewed the alert. You can make notes about the alert in the ALARM_NOTES field. When an alert is acknowledged, the status, notes, and last updated timestamp columns are updated in the MANAGEABILITY.METRICS.ALARMS base table. An operator has viewed and closed the alert. You can make notes about the alert in the ALARM_NOTES field. When an alert is closed, the status, notes, last update timestamp, and closed timestamp columns are updated in the MANAGEABILITY.METRICS.ALARMS base table. If the Alerts Options dialog box is set to display only open alerts, the closed alert will not be visible anymore. Update an Alert 189

190 2. Click the [ Apply ] button at the bottom of the Alerts tab: Use the steps for updating multiple alerts, but select only one row to update. Update Multiple Alerts (page 190) Make Notes About an Alert (page 190) Update Multiple Alerts You can update multiple alerts in the same operation. NOTE: You must have the necessary privileges before you can update alerts. See Understand Privileges for Viewing and Updating Alerts (page 182). To multiple update alert(s): 1. Display the Alerts tab, as described in Display the Alerts Tab (page 181). 2. Select cells in multiple rows corresponding to the alerts that you want to update. 3. Right-click and select Update Alert(s). The Update Alert dialog box appears. 4. Complete the Update Alert dialog box, as described in Use the Update Alert Dialog Box (page 188). 5. Click [ Apply ]. Make Notes About an Alert You can annotate an alert without changing the status of the alert. NOTE: You must have the necessary privileges before you can annotate an alert. See Understand Privileges for Viewing and Updating Alerts (page 182). To annotate an alert: 1. Display the Alerts tab, as described in Display the Alerts Tab (page 181). 2. In the ALARM_NOTES column, click the [... ] button for the alert that you want to annotate. The Alert Notes Editor dialog box appears. 3. Select a predefined note, or type a customer note, and click [ OK ]. 190 Respond to Alerts

191 4. Click the [ Apply ] button at the bottom of the Alerts tab to send the changes to the server. Update an Alert (page 189) About the Console Tab When either the Alerts tab or the System Offender tab is selected in the right pane, the Console tab is visible underneath it (unless the Console tab is hidden). The Console tab shows the queries that are used to gather data-grid information from the server. You can select and copy this information directly from the tab. To clear the console history, click the Clear Console History icon. To show or hide the Console tab, click the Fetch Status Bar. About the Console Tab 191

192 192

193 18 Find Offending Processes and Queries About System Offender System Offender is a tool that allows you to monitor system resources and detect processes and queries that use excessive CPU resources or memory. These are referred to as offending processes and queries. System Offender is a tab within the Monitoring area of HPDM. System Offender shows real-time data about processes and queries. The data is presented in a data grid. System Offender updates or refreshes the data grid at intervals that you control, and you can pause a refresh at any time to gather more information. System Offender is integrated with the Monitoring tab and system monitor. From the system monitor, you can drill down to obtain a list of related processes and queries and then obtain process detail, Pstate, or children-process information about each process. If the selected process has a query ID associated with it, you can check the plan, the compiler statistics, the runtime statistics, and memory usage counters. If necessary, you can cancel a runaway query and release allocated system resources. NOTE: Diagnostic information displayed by some System Offender dialog boxes is intended for use by HP support. This information is not documented for customer use. If you have questions about diagnostic information, contact your HP support representative. Display the System Offender Tab (page 193) See the Parts of the System Offender (page 194) Terms data grid offending process Display the System Offender Tab To display the System Offender tab: 1. In the My Systems folder of the navigation tree pane, select the system for which you want to find offending processes. 2. Select the Monitoring area. For more information about areas, see Select an Area (page 35). 3. In the right pane, click the Monitoring tab. 4. Click the System Offender tab. About System Offender (page 193) See the Parts of the System Offender (page 194) Understand System Offender Privileges (page 194) Find Offending Processes and Queries (page 194) About System Offender 193

194 See the Parts of the System Offender Understand System Offender Privileges (page 194) Find Offending Processes and Queries (page 194) Understand System Offender Privileges Administrator users (ROLE.DBA, SUPER.SERVICES, and SUPER.SUPER by default) can use all System Offender features. Only administrator users can alter System Offender server parameters, use the Pstate command, and cancel queries. Non-administrative users can alter System Offender client parameters and use all other System Offender features, which include displaying this information about a selected process: Workload detail information Process detail and parent process detail information Children process summary and detail information Terms administrator Find Offending Processes and Queries To find offending processes and queries, start your search in the system monitor. Then gather more information by using the System Offender: 1. Display the system monitor, as described in Display the System Monitor (page 171). 2. In the system monitor bar graph (Bar Graph tab or Hybrid tab), click one of the following areas: 194 Find Offending Processes and Queries

195 NOTE: Click once; you do not need to double-click. Click any CPU bar or header for these performance metrics... For example CPU Busy Disk I/O Cache Hits Dispatch Queue Length or... Free Memory Swap or... The System Offender tab displays a list of processes for the specified CPU (or all CPUs). The area you click in the System Monitor determines the System Offender active command. For example: When you click... The System Offender shows the active command as A CPU for a CPU-related metric A header for a CPU-related metric A CPU for a memory-related metric A header for a memory-related metric Find Offending Processes and Queries 195

196 3. In the System Offender data grid, see a list of processes: 4. Right-click a process that you want to learn more about, and select a command from the context menu: Terms NOTE: The Workload Detail command is active only if a query is associated with the selected process. The context menu commands provide detailed process information. For more information, see these topics. Get Query Workload Information (page 201) Get Process Detail Information (page 197) Get Pstate Information (page 197) Get Children Process Information (page 198) Understand Row Details for System Offender (page 199) 196 Find Offending Processes and Queries

197 data grid offending process Get Process Detail Information NOTE: Diagnostic information displayed by the Process Detail and Parent Process Detail dialog boxes is intended for use by HP support. This information is not documented for customer use. If you have questions about process detail information, contact your HP support representative. The Process Detail and Parent Process Detail commands, which are available from the context menu of the System Offender data grid, provide process information for a running process or a process that spawned another process (a parent process). For example: To obtain process detail information: 1. Display the System Offender tab, as described in Display the System Offender Tab (page 193). 2. Right-click a process in the data grid, and select Process Detail or Parent Process Detail. Find Offending Processes and Queries (page 194) Understand System Offender Privileges (page 194) Get Pstate Information NOTE: Diagnostic information displayed by the Pstate and Parent Pstate dialog boxes is intended for use by HP support. This information is not documented for customer use. If you have questions about Pstate information, contact your HP support representative. The Pstate and Parent Pstate commands, which are available from the context menu of the System Offender data grid, provide a snapshot of the status of a running process or a process Get Process Detail Information 197

198 that spawned another process (a parent process). These commands are available only to administrator users. To obtain Pstate information: 1. Display the System Offender tab, as described in Display the System Offender Tab (page 193). 2. Right-click a process in the data grid, and select Pstate or Parent Pstate. Find Offending Processes and Queries (page 194) Terms administrator Get Children Process Information A children process is a process that is spawned by another process (a parent process). To obtain children process information: 1. Display the System Offender tab, as described in Display the System Offender Tab (page 193). 2. Right-click a process in the data grid, and select Children Processes. The Children Processes dialog box appears. 3. To use and understand the information provided by the Children Processes dialog box, see Use the Children Processes Dialog Box (page 198). Use the Children Processes Dialog Box (page 198) Use the Children Processes Dialog Box To display the Children Processes dialog box, see Get Children Process Information (page 198). This table describes the dialog box fields: Field or Option Query ID Query Text Description The query identification number. The text of the Neoview SQL statement. 198 Find Offending Processes and Queries

199 Field or Option Parent Process Filter CPU Value [ Refresh ] Summary Table Tab Description The process that spawned the children processes described in the Detail tab. Controls which processes are displayed in the Detail tab based on CPU utilization. Set this value to the lowest CPU utilization that you want the dialog box to display. For example, if you set the CPU Value to 0, the tabs display all children processes in all CPUs. If you set the CPU Value to 50, the tabs display all children processes running in CPUs that are utilized at 50% or greater. Updates the information in the Summary Table and Detail tabs. Displays the number of children processes running in each CPU for all segments of a Neoview platform. Gray cells indicate CPUs or segments that are not available. A blue number indicates that the CPU utilization is less than 90%. A red number indicates that the CPU utilization is greater than or equal to 90%. For example, this Summary Table tab shows segment 1 CPUs 0, 1, 2, and 3 running at 90% or above: Detail Tab Displays detailed information about all children processes for the selected parent process. The information includes: SEGMENT CPU PIN PROCESS PRIORITY PROCESS TYPE CPU USAGE MEM USAGE PROGRAM NAME In the CPU USAGE column, a red number indicates CPU utilization of greater than or equal to 90%. A blue number indicates CPU utilization of less than 90%. This example shows zero CPU usage, so the number is displayed in black: Get Children Process Information (page 198) Understand Row Details for System Offender This table describes row detail information for the System Offender data grid. For more information about displaying row details, see Get Row Details for a Data Grid (page 49). Understand Row Details for System Offender 199

200 NOTE: Diagnostic information displayed by the System Offender tab is intended for use by HP support. If you have questions about an offending process, contact your HP support representative. Field SEGMENT CPU PIN PROCESS PRIORITY PROCESS TYPE CPU USAGE PERCENT* MEMORY USAGE MB* PROCESS NAME PROGRAM NAME* PARENT SEGMENT PARENT CPU PARENT PIN PARENTPROCESSPRIORITY PARENT PROCESS TYPE PARENT PROCESS NAME PARENTPROGRAMNAME* TCP PORT* TCP STATE* ELAPSED TIME WAIT TIME* HOLD TIME* QUERY ID Description The segment number. A Neoview platform typically consists of up to 16 segments with each segment containing up to 16 processing nodes. The processing node. The process identification number (PIN). The PIN is an unsigned integer that identifies a process in a processing node. The execution priority of the process (an integer in the range from 1 through 199 (1 is lowest priority)). The type of process, the display of which is controlled by the Process Type parameter in the Alter Offender Parameters dialog box. For example, if the current Process Type is set to SQL, the process types can be MXUDR, MXESP, MXCI, and MXOSRVR. If the Process Type is set to ALL, any process type can be displayed. For information about setting the process type, see Use the Alter Offender Parameters Dialog Box (page 208). The current CPU utilization from 0 to 100%. The current memory usage in megabytes (MB). A name that is assigned to a process when the process is created. A process name uniquely identifies a process or process pair in a system. A process name consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic. The name of the program. The number of the segment on which the parent process is running. The processing node in which the parent process is running. The process identification number (PIN) of the parent process. The PIN is an unsigned integer that identifies a process in a processing node. The execution priority of the parent process (an integer in the range from 1 through 199 (1 is lowest priority)). The type of parent process, the display of which is controlled by the Process Type parameter in the Alter Offender Parameters dialog box. For example, if the current Process Type is set to SQL, the process types can be MXUDR, MXESP, MXCI, and MXOSRVR. If the Process Type is set to ALL, any process type can be displayed. For information about setting the process type, see Use the Alter Offender Parameters Dialog Box (page 208). A name that is assigned to a parent process when the process is created. Includes the segment name. A process name uniquely identifies a process or process pair in a system. A process name consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic. The name of the parent program. The port to which the client process is connected. The state of the client connection. How long the query has been executing. How long the query has been in a waiting state. How long the query has been on hold. The query ID number (up to 160 characters). 200 Find Offending Processes and Queries

201 Field QUERY NAME QUERY TEXT ROLE NAME* USER NAME* DATASOURCE Description The name of the client workstation and application that generated the query. A preview of the actual query text (up to 254 characters). The role of the user who initiated the query. The user who initiated the query. The data source. *This field is not displayed by default on the data grid. To display this field, use the Show/Hide Grid Columns command available from the System Offender context menu. See Customize the Data Grid (page 52). Get Row Details for a Data Grid (page 49) Customize the Data Grid (page 52) Terms segment Get Query Workload Information The Workload Detail dialog box shows query workload information. This information includes: General query information Compiler statistics Runtime statistics Memory allocation and usage information Query text and automatic retry information NOTE: Diagnostic information displayed by the Workload Detail dialog box is intended for use by HP support. If you have questions about query diagnostic information, contact your HP support representative. Any user can view the workload detail information. To display the Workload Detail dialog box: 1. Display the System Offender tab, as described in Display the System Offender Tab (page 193). 2. In the data grid, right-click a process that has a query ID (as indicated in the QUERY ID column), and select Workload Detail. The Workload Detail dialog box appears. 3. To use and understand the information in the Workload Detail dialog box, see Use the Workload Detail Dialog Box (page 201). Cancel a Query From System Offender (page 207) Use the Workload Detail Dialog Box (page 201) Use the Workload Detail Dialog Box To display the Workload Detail dialog box, see Get Query Workload Information (page 201). Get Query Workload Information 201

202 NOTE: Diagnostic information displayed by the Workload Detail dialog box is intended for use by HP support. If you have questions about query diagnostic information, contact your HP support representative. The Workload Detail dialog box is mostly informational. If a query has a rule or service level associated with it, the Warn Level indicator indicates if the rule has been violated. The warning levels are: NOWARN (green) LOW (yellow) MEDIUM (orange) HIGH (red) For more information about workload management, see the Neoview Workload Management Services Guide. You can find this guide on the Neoview customer documentation Web site. See Resources on the Web (page 17). This table describes the Workload Detail buttons and options: Button [ View ] [ SQL Text ] [ SQL Plan ] [ Cancel Query ] [ Rules Assoc ] [ Repository Info ] [ Refresh ] Auto Refresh Description Displays the Warn Info dialog box, listing rules information for the query. This dialog box can show the status for multiple warning levels associated with the selected query. Displays the text for any query that belongs to a service that has text enabled in WMS or displays the text obtained from the repository if text is not available in WMS. Displays the query plan if SQL Plan is enabled in WMS. Cancels the query. See Cancel a Query From System Offender (page 207). Shows you the rules associated with a service. Select a rule or service and click [ Service Info ] or [ Rule Info ] to get more information about a rule or service. Shows the data that is currently registered in the Neoview Repository for the specified query. Use this button to validate information for long-running queries. Refreshes all workload information manually. When you refresh the display, some information appears in blue text. Blue text indicates a value that changed since the last refresh. To configure an automatic refresh, select the Auto Refresh option. Select this option, and move the slider below it to refresh the workload information automatically after an interval of seconds that you specify. Note that when the display refreshes, some information appears in blue text. Blue text indicates a value that changed since the last refresh. The following tables describe individual fields in the Workload Detail dialog box: Query Information Group Box Query Field ID State Substate Description Query identifier State of the query Substate of the query 202 Find Offending Processes and Queries

203 Group Box Warn Level Field Total Query Time Warn Level Description The total time that the query ran or is running (that is, the elapsed time), plus any time that the query spent in the waiting, holding, or suspended state. The display format is hhh:mm:ss for hours, minutes, and seconds. Warning level that is set for the query: NOWARN (green) LOW (yellow) MEDIUM (orange) HIGH (red) Click View for more details. See Understand the Warning Information (page 203). Understand the Warning Information Field Query ID Service Name Warn Type Warn Level Rule Name Expr Reason Description Query identifier Name of the WMS service CONN for a connection rule COMP for a compilation rule EXEC for an execution rule LOW, MEDIUM, or HIGH Name of the rule that triggered the warning Expression number in the rule, corresponding to the ordinal position of the expression for an OR operator or the total number of expressions for an AND operator Rule expression that triggered the warning Compiler Statistics Group Box Info Estimate Field Service Process Query Application Computer Role User DataSource Start Entry Cost Description Name of the WMS service Name of the master process of the query Internal name of the query containing the client host name concatenated with the application name Name of the application that initiated the query Client host name Name of the Neoview role associated with the query (that is, the role of the user who is running the query) Name of the user connected to the Neoview platform Name of the data source for the connection The time when the query was submitted into the Neoview system. The display format is yyyy-mm-dd (for year, month, and day) and hh:mm:ss.ssssss (for hours, minutes, and seconds). Unique identifier to indicate when the query entered the Neoview system. The display format is yyyy-mm-dd (for year, month, and day) and hh:mm:ss.ssssss (for hours, minutes, and seconds). Estimated cost of the query Use the Workload Detail Dialog Box 203

204 Group Box Other Field CPU I/O Message Idle Total Time Cardinality Total Memory Res. Usage Affinity Number Degree of Parallelism Transaction Needed Mandatory X Prod Missing Stats Number Joins Full Scan on Table Rows Full Scan EID Max Buffer Usage EID Rows Accessed EID Rows Used Conn Rule Comp Rule Exec Rule Description Estimated total amount of processor (CPU) time Estimated total amount of I/O time Estimated total amount of messaging time Estimated idle time Estimated total time Estimated number of rows returned by the query Estimated total amount of memory Estimated total resource usage Compiler affinity number, indicating the number of processors used Degree of parallelism Indicates whether a transaction is needed: 1 = true 0 = false Indicates whether a cross product exists: 1 = true 0 = false Indicates whether statistics are missing: 1 = true 0 = false Number of join operators that are required Indicates whether a full scan of the table is required: 1 = true 0 = false A condition of true indicates that the predicate was not using a key-field to restrict the number of records to search. Estimated number of rows accessed for a full scan Maximum buffer usage by the disk processor Estimated number of rows accessed in the disk process Estimated number of rows used in the disk process Displayed as rule-name:expr-num, where rule-name is the last connection rule evaluated for the query and expr-num is the total number of rule expressions Displayed as rule-name:expr-num, where rule-name is the last compilation rule evaluated for the query and expr-num is either the ordinal position of the expression that evaluated to true or ALL for all expressions evaluating to true Displayed as rule-name:expr-num, where rule-name is the last execution rule evaluated for the query and expr-num is either the ordinal position of the expression that evaluated to true or ALL for all expressions evaluating to true. 204 Find Offending Processes and Queries

205 Runtime Statistics Group Box Info Time Field Statement Type Statement ID Exec State SQL Code Stats Code Lock Waits Lock Escalations Num Rows IUD Parent QID Priority Transaction ID Num SQL Processes Processes Created Comp Start Comp End Exec Start Exec End Elapsed Wait Hold Description Type of SQL statement Statement identifier of the query, which is part of the query ID Execution state of the query Top-level error code returned by the query, indicating whether the query completed successfully or with warnings or errors. A positive number indicates a warning. A negative number indicates an error. Internal error code returned to the statistics collector from the runtime statistics (RMS) infrastructure Number of lock waits. This counter indicates the number of times the query had to wait on a conflicting lock. A value of 0 indicates that no locks were encountered while the query was executing. Number of lock escalations. This counter indicates the number of times row locks escalated into a file lock during the execution of the query. A value of 0 indicates that no locks were escalated while the query was executing. Number of rows inserted, updated, or deleted Identifier of the parent query. If there is no parent query ID associated with the query, NONE is displayed. Process priority of the master executor process Identifier of the transaction under which the query is executed. When there is no transaction, the transaction ID is -1. Number of SQL processes (excluding ESAM processes) involved in executing the query Number of Executor Server Processes (ESPs) created Time when the query compilation started (or when PREPARE started for the query). The display format is yyyy-mm-dd (for year, month, and day) and hh:mm:ss.sss (for hours, minutes, and seconds). Time when the query compilation ended (or when PREPARE ended for the query). The display format is yyyy-mm-dd (for year, month, and day) and hh:mm:ss.sss (for hours, minutes, and seconds). Time when the query started executing. The display format is yyyy-mm-dd (for year, month, and day) and hh:mm:ss.sss (for hours, minutes, and seconds). Time when the query finished executing. While the query is still executing, this field displays -1. When the query finishes executing, the display format is yyyy-mm-dd (for year, month, and day) and hh:mm:ss.sss (for hours, minutes, and seconds). Amount of time that the query ran or is running. For running queries, this is the time since the start of the query execution until the current time. For completed queries, this is the difference between the Exec Start and Exec End times. The display format is hhh:mm:ss for hours, minutes, and seconds. Amount of time the query waited before it started executing (that is, the time from entry into the system to the time when the query actually starts to execute). The display format is hhh:mm:ss for hours, minutes, and seconds. Amount of time the query was in the holding or suspended state. The display format is hhh:mm:ss for hours, minutes, and seconds. Use the Workload Detail Dialog Box 205

206 Group Box Usage Memory (KB) Derived Time Field First Row Returned SQL CPU (sec) Process Busy Time (sec) Open (sec) Process Create (sec) Est Accessed Rows Accessed Rows Est Used Rows Used Rows Message Count Message Bytes Stats Bytes Disk I/Os Rows Returned Req Message Count Req Message Bytes Reply Message Count Reply Message Bytes SQL Space Alloc SQL Space Used SQL Heap Alloc SQL Heap Used EID Space Alloc EID Space Used EID Heap Alloc EID Heap Used Total Mem Alloc Max Mem Used Total CPU (sec) Total Processor Description Timestamp when the first row was returned from the root operator of the master executor process. A value of -1 means that the first row has not yet been returned. Processor (CPU) utilization, in seconds, by Neoview SQL for the query Processor (CPU) utilization, in seconds, by the disk process Amount of time, in seconds, spent on opens Amount of time, in seconds, to create Executor Server Processes (ESPs) The compiler's estimated number of rows accessed Actual number of rows accessed The compiler's estimated number of rows returned after applying predicates Actual number of rows returned after the predicates were applied. In a pushed down plan, all the used rows might not be returned. Number of messages Number of message bytes sent while accessing the tables referenced by the query Number of bytes returned for the statistics counters Number of disk reads for accessing the tables referenced in the query Number of rows returned from the root operator of the master executor process Number of messages initiated from the master to ESPs or from an ESP to ESPs Number of message bytes that are sent from the master to ESPs or from an ESP to ESPs as part of the request messages Number of reply messages from the ESPs for the message requests Number of bytes sent as part of the reply messages Total space allocation by Neoview SQL for the query Total space used by Neoview SQL for the query Total heap allocation by Neoview SQL for the query Total heap used by Neoview SQL for the query Total space allocation by the executor in the disk process Total space used by the executor in the disk process Total heap allocation by the executor in the disk process Total heap used by the executor in the disk process Total memory allocated for the query, which is the sum of the SQL Space Used and SQL Heap Used Maximum memory used by the query, which is the sum of the SQL Space Alloc, SQL Heap Alloc, EID Space Alloc, and EID Heap Alloc Total amount of processor (CPU) time used by the query, which is the sum of the SQL CPU time, Process Busy Time, Open time, and Process Create time. The display is in seconds. Total amount of processor (CPU) time used by the query. The display format is hh:mm:ss.sss for hours, minutes, and seconds. 206 Find Offending Processes and Queries

207 Group Box Other Field Last Interval Processor Delta Processor Processor Usage/Sec Opens Error Before AQR AQR Num Retries Delay Before AQR Aggr Query Aggr Total Queries Aggr Secs Since Last Update Aggr Secs Total Time Query Text (Preview) Length Description Total amount of processor (CPU) time used by the query in the previous refresh interval. The display format is hh:mm:ss.sss for hours, minutes, and seconds. The difference between the current and previous sample of the processor (CPU) utilization, which is the Total Processor time minus the Last Interval Processor time Amount of processor (CPU) cycles the query is consuming (rate of processor usage), which is the Total CPU time divided by the Elapsed time Number of opens (one per partition), which is the number of OPEN calls performed by the Neoview SQL executor on behalf of the query Error code that triggered the Automatic Query Retry (AQR) for the recent retry Number of retries that occurred for this query until now Number of seconds that the SQL engine waited before it initiated an AQR Either YES or NO, indicating whether the query's statistics are aggregated Total number of queries in the aggregated query Difference in seconds between the current time and the last time that the aggregation was updated Difference in seconds between the current time and the first time that aggregation was updated Text of the SQL query Length of the query text, including spaces Cancel a Query From System Offender (page 207) Cancel a Query From Metric Miner (page 227) Cancel a Query From the SQL Whiteboard (page 215) Cancel a Query From System Offender Only an administrator user can cancel a query. To cancel a query by using the System Offender: 1. Display the Workload Detail dialog box as described in Get Query Workload Information (page 201). 2. Click [ Cancel Query ]. A confirmation dialog box appears. 3. Click [ Yes ] or [ No ]. NOTE: You can also cancel a query from the SQL Whiteboard. See Cancel a Query From the SQL Whiteboard (page 215). Get Query Workload Information (page 201) Use the Workload Detail Dialog Box (page 201) Terms administrator Cancel a Query From System Offender 207

208 Alter System Offender Parameters To display the Alter Offender Parameters dialog box and alter the parameters: 1. Display the System Offender tab, as described in Display the System Offender Tab (page 193). 2. In the toolbar, click the Alter Offender Parameters button ( ). The Alter Offender Parameters dialog box is displayed. 3. Configure the server and/or client parameters as described in Use the Alter Offender Parameters Dialog Box (page 208). 4. Click OK. Use the Alter Offender Parameters Dialog Box (page 208) Use the Alter Offender Parameters Dialog Box To display this dialog box, see Alter System Offender Parameters (page 208). You must be an administrator user to alter the Server Parameters. Any user can alter the Client Parameters. Altered parameters are persisted by HPDM. Group Box Server Parameters Parameter Sample Interval (sec.) Sample CPUs (# CPUs/sample) Description How often in seconds WMS fetches the offender sample data. The default value is 10, and the range is from 10 to 60 seconds. The number of CPUs that WMS checks during one sample. The default value is 2, and the range is 2 to 16. Sample Cache (# processes/segment) The number of offending processes that WMS displays per segment. The default value is 10, and the range is 10 to 100. Client Parameter Process Type SQL displays SQL processes, such as MXUDR, MXESP, MXCI, and MXOSRVR. All (the default setting) displays all processes. This table describes the buttons: Button [ OK ] [ Reset ] [ Cancel ] Description Sends the dialog box changes to the server. Restores the default values for the parameters that the user has privileges to change. Closes the dialog box without making changes. Alter System Offender Parameters (page 208) Control the Refresh of System Offender The System Offender data grid is refreshed automatically every 60 seconds. During a refresh, System Offender fetches new information from the server using the current active command. The active command appears under the System Offender tab. For example: 208 Find Offending Processes and Queries

209 A refresh timer controls the refresh interval. When an update is in progress, the refresh timer is paused. If the update completes successfully, the refresh timer is restarted. If, for any reason, one or more updates fail, the refresh timer remains paused so that you can resolve the issue without losing configured information. You control the refresh interval and other refresh attributes by using the toolbar buttons at the top of the System Offender tab: Click this button... Stop Data Provider Refresh Data Pause Timer Resume Timer Set Refresh Time Alter Offender Parameters History To do this Stop the refresh. Refresh the Alerts data grid at any time. Pause the refresh. Restart the refresh after pausing. Change the refresh interval. See the steps for doing this later in this topic. Control the information displayed by the System Offender. See Alter System Offender Parameters (page 208). Display all of the WMS commands sent to the server for the current session. See Use the System Offender History (page 210). To change the refresh interval: 1. Display the System Offender tab, as described in Display the System Offender Tab (page 193). 2. Click the [ Set Refresh Time ] button: Control the Refresh of System Offender 209

210 3. Select a refresh interval. The timer status bar counts down the new refresh interval in seconds. Suppose the refresh timer is set to a low value (for example, 30 seconds). If you are investigating an offending process, you might want to pause the timer so that a refresh doesn't change the data displayed in the data grid. To pause the refresh: 1. Display the System Offender tab, as described in Display the System Offender Tab (page 193). 2. Click the [ Pause Timer ] button. The button changes to a [ Resume Timer ] button, and the timer status bar shows Refresh Paused. 3. To restart the timer click the [ Resume Timer ] button. See the Parts of the System Offender (page 194) About the Console Tab (page 191) Use the System Offender History The System Offender History dialog box shows all of the WMS commands sent to the server for the current session. To display the History dialog box: 1. Display the System Offender tab as described in Display the System Offender Tab (page 193). 2. Click the History button ( ). The History dialog box appears. For example: The command history is more than simply a reference listing. You can select any row in the history and re-execute the selected command by clicking [ OK ]. To erase the history, click [ Clear ]. To update the history, click [ Refresh ]. 210 Find Offending Processes and Queries

211 19 Use the SQL Whiteboard About the SQL Whiteboard The SQL Whiteboard allows you to enter and execute SQL statements from within HPDM and provides execution information for each of the SQL statements. The list of SQL statements is persisted between HPDM sessions the same way that system configuration and favorites are persisted in HPDM. Currently, HPDM supports only one instance of the SQL Whiteboard. SQL statements can be parameterized by embedding parameter names surrounded by double dollar signs ($$). When the statement is executed, the SQL Whiteboard requests the values for the parameters in the statement and easily allows you to reuse recent values for those parameters. Display the SQL Whiteboard (page 211) Save and Import System Definitions (page 55) Display the SQL Whiteboard To display the SQL Whiteboard, use one of these methods: Click the SQL Whiteboard button ( ) on the HPDM toolbar. From the HPDM main menu, select Tools > SQL Whiteboard. Learn About the SQL Whiteboard Panes (page 211) Use the HPDM Toolbar (page 44) Learn About the SQL Whiteboard Panes The SQL Whiteboard contains these panes: Pane Statement List Statement Statement Details Description Displays a listing of the SQL statements that you added from the Statement pane. Allows you to enter any DML or DDL statement, including SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, GRANT, DROP, REVOKE, and so on. Displays detailed information about the execution results. About the SQL Whiteboard 211

212 Learn About the Statement List Pane (page 212) Learn About the Statement Pane (page 213) Learn About the Statement Details Pane (page 215) Learn About the Statement List Pane The Statement List pane provides a list of SQL statements that you added in a current session or earlier sessions of the SQL Whiteboard tool. The list of SQL statements is persisted between HPDM sessions the same way that connection information and favorites are persisted. From the Statement List pane, you can: View the name and statement that was previously added in the Statement pane. Optionally, you can explicitly add a statement to the statement list without executing it, using [ Add ]. Update an existing statement in the list using [ Update ] in the Statement pane. Sort the statements based on the statement name or statement text. If you want to discard unwanted statements, select the check box and use [ Discard ]. You can check or uncheck statements using [ All ] or [ None ]. 212 Use the SQL Whiteboard

213 The buttons across the top of the Statement List pane allow you to select individual statements or select all statements to be executed: Button [ All ] [ None ] [ Discard ] Function Selects all statements in the Statement List. Deselects all statements in the Statement List. Removes selected statements (marked checked boxes) or the statement results, or both, depending on the option you select in the dialog box. NOTE: You cannot discard a statement or results while the statement is executing. If a currently executing statement is part of a [ Discard ] selection, it will be skipped. Use the [ Discard ] button when you want to free up virtual memory or when HPDM indicates that system resources are running low. Until you exit the SQL Whiteboard, the result of every executed statement is cached. If you already executed several large statements in the current session, the results stay in memory, and less memory is available for newer executions. Understand Page Mode (page 214) describes how the SQL Whiteboard caches and displays large result sets. Learn About the Statement Pane The Statement pane allows you to enter any SQL command (DDL or DML) in the text box. The maximum number of characters you can enter in the text box is The maximum limit is enforced by the.net text box control. In the Statement pane, these fields define a statement: Field Name System Max Rows Schema Rows/Page Description Enter the name of the SQL statement. You can specify a name to uniquely identify the statement in the statement list. Use [ Add ] to add the statement to the statement list. Use [ Update ] to update an existing statement from the statement list. Select a system from the System drop-down box on which you want to execute the query. Specifies the maximum rows that you want returned and displayed in the details. The default is 500 rows, and the maximum is Select a schema name from the Schema drop-down box. If you do not explicitly qualify the query by specifying a 3-part ANSI name, the default schema is the currently selected value in the drop-down box. Select the number of rows to be fetched and displayed in one page of the statement result set. You can set the Rows/Pages value to between 1 and 100,000. Or use the default Rows/Page value (0), which causes HPDM to try to fetch and display the entire result set. If you specify a value of 1 or more for the Rows/Page, or if you use the default setting and HPDM cannot fetch and cache (for display purposes) the entire result set using available memory, HPDM automatically displays the result set in pages. For more information about page mode, see Understand Page Mode (page 214). To execute the statement, click [ Execute ]. The buttons across the bottom of the Statement pane allow you to test the statement and change it: Button [ Add ] [ Update ] [ Execute ] Function Allows you to add a new SQL statement or duplicate a statement to the Statement List. Allows you to update the statement. Make the required change, and then select [ Update ]. Causes the statement to be executed and shows the results in the Statement Details pane. Terms Learn About the Statement Pane 213

214 page mode Understand Parameter Prompts SQL statements can be parameterized by embedding parameter names surrounded by $$ (double dollar signs). When the statement is executed, the SQL Whiteboard prompts you for values for all parameters in that statement and easily allows you to reuse recent values for those parameters. Understand Page Mode When you execute a statement in the SQL Whiteboard, HPDM caches the results in virtual memory for display purposes. But the SQL Whiteboard can run out of memory if: A single query has a large result set (a result set consisting of a large number of columns or a large number of rows, or both). Several queries with large result sets are executed in a single SQL Whiteboard session. To prevent out-of-memory conditions and accommodate large result sets, the SQL Whiteboard can run in page mode. In page mode, the SQL Whiteboard breaks large result sets into pages and fetches one page at a time, rather than trying to fetch everything and display all rows in the grid. Page mode reduces the amount of memory used because only a partial result is held in memory and displayed in the Statement Details pane. Default Page Mode Operation By default, the SQL Whiteboard tries to display all the results of a statement. However, it automatically runs in page mode when: Insufficient memory is available to display the result set in one page. In this case, the SQL Whiteboard automatically displays the result in page mode. You specify a value from 1 to 100,000 in the Rows/Page field of the Statement Pane. In this case, the SQL Whiteboard automatically uses page mode and allocates the number of rows per page that you specified (memory permitting). Page Mode Considerations Note these considerations for page mode: During the course of statement execution, HPDM frequently computes the available virtual memory of the application. If the available virtual memory falls below an internal threshold, statement execution goes into page mode. The user has no control over this. In some cases, page mode must be used to prevent HPDM from running out of memory and generating an exception. When a statement is executed and the number of rows is less than the Rows/Page threshold, all rows in the results are fetched and displayed in the grid. When a statement is executed and the number of rows in the result set exceeds the Rows/Page threshold, the statement execution goes into page mode, in which partial results are fetched and displayed. When statement execution enters page mode, the Statement Details pane displays a [ Next Page ] button: Until you click [ Next Page ], the execution is paused, and the SQL cursor remains open. However, the Time Elapsed timer keeps running because it tracks the wall time. When you click [ Next Page ], the next page of results is fetched from the server. The first page is deleted from the grid when the new page is loaded. The process repeats until you either view all the pages or cancel the query. You cannot go back to the previous page because the ODBC cursor operates in FORWARD mode only. To display earlier results, you must re-execute the statement. 214 Use the SQL Whiteboard

215 Regardless of whether the number of rows in the result set exceeds the Rows/Page threshold, if the available virtual memory falls below the internal threshold, the statement execution goes into page mode and displays the results that have been fetched so far. In this situation, the grid might display fewer rows than the Rows/Page threshold. This situation continues until garbage collection kicks in and frees up the memory occupied by the pages that have been disposed. When system resources are low, the Statement Details pane displays a message to notify you that execution is entering page mode. Grid sorting works only on the currently displayed page. In page mode, these buttons export data for the current page only: [ Data to Clipboard ] [ Data to Browser ] [ Data to Spreadsheet ] [ Data to File ] To free up workstation memory, you can discard the results of the selected statement(s) cached in the Statement List pane. See Learn About the Statement List Pane (page 212). Cut, Copy, Paste, Undo, and Redo In the Statement pane, if you right-click the text box, these options are displayed: Execute Highlighted Text If you highlight text, you can execute part of a statement. Cancel a Query From the SQL Whiteboard Sometimes you need to cancel a running SQL query. It may be that you typed the wrong query, the query is inefficient, or the query is creating a performance bottleneck and needs to be stopped. After a query starts executing, the SQL Whiteboard [ Execute ] button changes to [ Cancel ]. Pressing [ Cancel ] terminates the SQL query. NOTE: You can also cancel a query from the Workload Detail dialog box of the System Offender. See Cancel a Query From System Offender (page 207). Learn About the Statement Details Pane The Statement Details pane contains statistics and details propagated from the selected statement in the Statement List pane. This is informational and has no interactive functionality. Statistics Learn About the Statement Details Pane 215

216 are shown only for statements that are loaded from the Statement pane. The values in the Statement Details pane are: The Execution Results tab displays the completion of SELECT statements: Field or Button Last Evaluated Time Elapsed Status [ Next Page ] Function Shows when the statement was last evaluated. Specifies the elapsed time in seconds. Displays the executed statement status. The Execution Results indicate the progress of the statement execution and the number of rows fetched so far. Once the statement has completed execution, it displays the status of success or failure, processing time, and the timestamp when the query was executed. If the execution is canceled, the status reflects the same. Displays the next set of execution results when statement execution is displayed in page mode. For more information about page mode, see Understand Page Mode (page 214). For DML statements such as INSERT, DELETE, or UPDATE, the results show how many rows were affected if the execution is successful. For other SQL commands, the results are displayed in text form. For SELECT statements, you can use the Export options to export the results to a file, clipboard, or spreadsheet. The export options are: [ Data to Clipboard ], [ Data to Browser ], [ Data to Spreadsheet ], and [ Data to File ]. The data is preserved only while the SQL Whiteboard remains open. The data is flushed when the SQL Whiteboard is closed. Also, when in page mode, only the data for the current page can be exported. For more information about page mode, see Understand Page Mode (page 214). Tab Execution Error Execution Parameters Executed Statement Function Shows the execution error that is displayed if a statement has an error. The exact error is returned from ODBC and SQL. This tab is present if the statement has parameters and shows the values chosen for the current or earlier execution. Displays the statement that was executed with the parameters (if any), replaced with their values. Export Data (page 53) Terms page mode Reuse a Connection The reuse connection feature is enabled by default in the SQL Whiteboard. This means that any query executed for the selected system uses the same connection unless explicitly closed. Use [ Close ] to explicitly close the connection. You may want to close the connection to free up system resources. The reuse connection feature allows you to execute a series of statements in a single session using the same connection. A good example is when you are using volatile tables. You create the volatile table first and then run queries on it. The volatile table is available only until the session ends. Load and Save SQL Statements to a File The SQL Whiteboard provides commands that allow you to import SQL statements from a text file into the Statement pane. You can also export SQL statements from the Statement pane into 216 Use the SQL Whiteboard

217 a specified text file. To import or export SQL statements, use these commands from the File menu: Command Load SQL Statement Save SQL Statement Description Reads the text of an SQL statement from an ASCII file into the Statement text box. Saves the current SQL statement text from the Statement text box to an ASCII file. Only the statement text is saved, not the statement results. To save the results, use the Data to Clipboard or Data To Spreadsheet options. Export Data (page 53) Highlight SQL Syntax To highlight SQL syntax in the Statement pane, use the Format > Highlight Syntax menu. This highlights the SQL keywords in the SQL text. Use this feature whenever you need to highlight syntax. Manage the Layout of Panes The SQL Whiteboard allows you to move or resize individual panes. After you have done so, it might be necessary to reset the layout to the original default configuration. To reset the layout of the Statement, Statement List, and Statement Details panes, use the File > Reset Layout command. Once a layout suits you, you can lock the layout using the File > Lock command. To unlock, use the File > Reset Layout menu. To explicitly persist the layout, use the File > Save Persistence command. The layout is persisted automatically when the SQL Whiteboard exits. The next time the SQL Whiteboard is launched (either in the current instance of HPDM or in a restarted HPDM instance), the layout is restored. Save and Import System Definitions (page 55) Highlight SQL Syntax 217

218 218

219 20 Use Metric Miner About Metric Miner Metric Miner is an HPDM utility that allows you to: Execute a SQL statement or query and view the results within HPDM. Save the statement or query as a report that includes descriptive information, statement parameters, and version information. Run multiple reports at the same time (subject to workstation memory limitations). Each report is self-contained and displayed in its own tab. Reuse, share, and link reports. Metric Miner replaces an earlier reporting product called Neoview Reports and has some features in common with the SQL Whiteboard utility, which is still supported within HPDM. You can use Metric Miner with Neoview platforms running releases earlier than Release 2.5, provided that SQL statements that you enter are supported on the earlier platforms. Compare Metric Miner, SQL Whiteboard, and Neoview Reports (page 219) About the SQL Whiteboard (page 211) Terms Metric Miner report Compare Metric Miner, SQL Whiteboard, and Neoview Reports This table compares the features of the SQL Whiteboard, Neoview Reports, and Metric Miner: Feature SQL Whiteboard Neoview Reports* Metric Miner Execute a SQL statement or query x x x Provide a multipane window for statements and results x x x Export statement results to a browser or spreadsheet x x x Support parameters in statements x x x Maintain a history of SQL statements x x Display or import Neoview Reports x x Save reports on the Neoview platform x Publish reports to the Neoview platform web space x Execute multiple statements or queries at the same time x Provide a toolbar for frequently used functions x Show row details for statement-result information x Save reports on the local workstation x Link reports to enable drill down to associated reports from the current report x Display a report in its own window x *Metric Miner replaces Neoview Reports in Release 2.5 and later releases. About Metric Miner 219

220 About Metric Miner (page 219) About the SQL Whiteboard (page 211) Terms Metric Miner Launch Metric Miner Any user can launch Metric Miner. To launch Metric Miner: 1. Start HPDM and log on using any user ID. For more information, see Connect to a System (page 25). 2. Use one of these methods to display the Metric Miner window: Click the Metric Miner button ( ) on the HPDM toolbar. For more information about the HPDM toolbar, see Use the HPDM Toolbar (page 44). From the Tools menu, select Metric Miner. Use the HPDM Toolbar (page 44) See the Parts of Metric Miner (page 220) Connect to a System (page 25) Terms Metric Miner See the Parts of Metric Miner Metric Miner consists of three main sections or panes. The Report Explorer occupies the left pane in the Metric Miner window: 220 Use Metric Miner

221 The user input fields, including the SQL Input Area and the Report Results Area occupy the middle panes of the Metric Miner window: The Status, Description, and Row Details tabs occupy the right pane in the Metric Miner window: See the Parts of Metric Miner 221

222 Use the Metric Miner Toolbar (page 222) Learn About the SQL Whiteboard Panes (page 211) Use the Metric Miner Toolbar Metric Miner toolbar buttons provide shortcuts to common operations: 222 Use Metric Miner

223 Button Stop data provider Function Stop the refresh (cancel the query). See for More Information Cancel a Query From Metric Miner (page 227) Refresh data Re-execute the SQL statement using any input parameters provided during the last statement execution. Control the Refresh of Metric Miner Information (page 228) Set refresh time Run the SQL statement Save the report configuration (Ad-hoc report) Save the report configuration (Saved report) Save the report configuration as a new report Expand the tab to occupy the full screen Export data to the selected format Display the SQL designer Close the report tab Configure a refresh interval. Executes the statement in the SQL input area. If input parameters are needed, Metric Miner prompts you to provide them. Displays the Report Configuration dialog box. Displays the Report Configuration dialog box. Copies a currently configured report Toggles the width of the SQL input area and results pane. Saves the data to the clipboard, a browser, a spreadsheet, or a.csv file. Displays the SQL Designer dialog box. Closes the currently active report tab. Control the Refresh of Metric Miner Information (page 228) Run a SQL Statement Using Metric Miner (page 225) Use the Report Configuration Dialog Box (page 231) Use the Report Configuration Dialog Box (page 231) Copy a Report (page 233) Export Metric Miner Data (page 228) Use the SQL Designer (page 225) Close a Report (page 233) See the Parts of Metric Miner (page 220) Use the Metric Miner Toolbar 223

224 Create Report Folders Create a Report Folder Before you start using Metric Miner, create a report folder. A report folder is any folder that contains reports. Reports are not visible to the Report Explorer until you create a report folder. The report folder can be located on your local workstation, or it can be a shared folder on a server to which you have access. You can create as many report folders as you want. However, Metric Miner allows you to create logical folders within each report folder. Logical folders allow you to further organize your reports, making it unnecessary to create numerous report folders. For more information about logical folders, see Use the Report Configuration Dialog Box (page 231). To create a report folder: 1. Launch Metric Miner as described in Launch Metric Miner (page 220). 2. In the Report Explorer pane, right-click the Reports icon, and select Add Report Folder. The Browse For Folder dialog box appears. 3. Select a folder or create a new folder, and click OK. The folder appears in the Report Explorer. CAUTION: Do not rename or remove a report folder once it has been created. If you create a report folder and the folder is later renamed or moved, the Report Explorer will no longer display the folder. See the Parts of Metric Miner (page 220) Rename a Report or Report Folder (page 233) Delete a Report Folder You can delete a report folder that contains reports; you do not have to delete the reports first. Deleting a report folder does not remove the folder (or the reports contained within it) from your workstation. It simply causes the Report Explorer to stop displaying the folder. As long as the folder isn't renamed or moved, you can later respecify the folder as a report folder, and the reports will be visible to the Report Explorer. To delete a report folder: 1. Close any open reports for the report folder that you want to delete. 2. In the Report Explorer, right-click the report folder icon, and select Remove Report Folder. A confirmation box asks if you want to continue. 3. Click Yes. Delete a Report (page 233) Create a Report Folder (page 224) Refresh the Report Explorer Sometimes the Report Explorer doesn't immediately display changes you have made to reports or report folders. To refresh the Report Explorer, right-click the Reports node or the node for any report folder, and select Refresh. If the Refresh command fails to update the Report Explorer, close and relaunch Metric Miner. See the Parts of Metric Miner (page 220) 224 Use Metric Miner

225 Run Statements Run a SQL Statement Using Metric Miner Using Metric Miner, you can run SQL statements in much the same way that you can run them by using the SQL Whiteboard. Saving the statement information as a report is optional. To run a SQL statement using Metric Miner: 1. Launch Metric Miner, as described in Launch Metric Miner (page 220). 2. In the SQL input area of the Ad-Hoc Report tab, type the SQL statement. If you don't see the Ad-Hoc Report tab, click the Ad-Hoc Report node in the Report Explorer pane to create the tab. NOTE: The SQL Designer tool simplifies the task of creating complex statements, and statements that you create by using the SQL Designer are inserted into the SQL input area. See Use the SQL Designer (page 225). If you don't explicitly qualify the statement by specifying a 3-part ANSI name, the default schema is the currently selected value in the Schema drop-down list. 3. Click the Schema button, and select the schema for the statement. 4. In the Rows field, type the number of result rows that you want Metric Miner to display in the Report Results pane. The default value is 500 rows. You can set this value to between 1 and 100,000. Or specify 0, which causes Metric Miner to try to fetch and display the entire result set. 5. Click the button to run the SQL statement ( ). If the report has input parameters, Metric Miner displays a Parameters dialog box so that you can enter the parameter values. For more information about parameters, see Add Parameters to Statements (page 226). 6. Enter the parameter values, if required, and click [ OK ]. If the statement is successful, results appear in the Report Results pane, and the Status Tab summarizes the execution status. If the statement is unsuccessful, an Errors tab appears under the Report Results pane. 7. If you want to create a report containing the statement, see Create a Report (page 230). If you do not need to save the statement as a report, click the button to close the report ( ). See the Parts of Metric Miner (page 220) Create a Report (page 230) Resolve Errors and Error Messages (page 47) Use the SQL Designer (page 225) Add Parameters to Statements (page 226) Understand Page Mode (page 214) Terms Ad-hoc Report Use the SQL Designer The SQL Designer is a tool that allows you to build a SQL statement by adding syntax items from a set of lists and using the keyboard to enter other required text. The resulting statement is then inserted into the SQL input area. The SQL Designer lets you select from lists of all the tables, views, columns, and functions for a given schema. To launch the SQL Designer, click the SQL Designer button ( To use the SQL Designer: ) on the Metric Miner toolbar. Run Statements 225

226 1. At the top of the dialog box, select a schema from the Schema drop-down menu. The SQL Designer populates the Tables/Views field based on the schema that you select. 2. At the bottom of the dialog box, double-click any of the following individual elements in addition to using the keyboard to add text in the Query box in the middle of the dialog box: SQL Statements Tables/Views Columns Functions NOTE: The SQL Statements and Functions menus are drop-down menus. Changing the menu value changes the choices presented in the box under the menu. The menu items are: SQL Statements CQD Statements DDL Statements DML Statements Transaction Statements Functions Numeric Functions String Functions System Functions Time/Date Functions The SQL Designer might provide SQL statements and functions that are not supported for customer use. If you are not sure about a supported statement or function, check the Neoview SQL Reference Manual, which documents all supported statements and functions. 3. When you have completed building the SQL statement, click [ OK ] to insert the query into the SQL input area. Add Parameters to Statements (page 226) Use the Metric Miner Toolbar (page 222) Run a SQL Statement Using Metric Miner (page 225) Resources on the Web (page 17) Add Parameters to Statements You can embed parameters in a SQL statement by inserting a parameter name surrounded by $$ (double dollar signs). For example, this statement causes Metric Miner to prompt you for a Table Name before executing the statement. select * from $$Table Name$$ The resulting parameter prompt is: This statement causes Metric Miner to prompt you for several parameters, including a time range, which is enabled by using both the $$ FROM_TIME$$ and $$ TO_TIME$$ parameters in the same query: SELECT [first $$Number Of Stmts_to Return$$] cast( (QUERY_END_DATETIME - QUERY_START_DATETIME)/60 as dec(12,2)) as Elapsed_Min, left(sql_text,40) as Abrev_Sql_Text, 226 Use Metric Miner

227 User_name as User_Name, query_start_datetime as Start_time, query_end_datetime as end_time, Datasource as datasource, start_priority as Pri, rows_accessed, rows_retrieved, num_rows_iud as Row_IUD, error_code, statement_state, process_name as Mstr_Exec, sequence_size as SQL_TXT_Size, sql_text as First_3k_text FROM ODBC_QUERY_STATS_V2 WHERE (QUERY_START_DATETIME) >= TIMESTAMP '$$ FROM_TIME$$' AND (QUERY_START_DATETIME) < TIMESTAMP '$$ TO_TIME$$' and STATEMENT_STATE <> 'MULTIROW' and statement_state = 'COMPLETE' order by Elapsed_min desc FOR READ UNCOMMITTED ACCESS ; The resulting parameter prompt is: For each parameter, Metric Miner stores the last 10 values that you supply so that they can be reused in later statement executions. These stored parameters are persisted across sessions (Metric Miner remembers the values even when you disconnect from HPDM). Once the report executes successfully, the parameters corresponding to the report are displayed in a Parameters tab next to the Description tab. Run a SQL Statement Using Metric Miner (page 225) Cancel a Query From Metric Miner Sometimes you need to cancel a running SQL query. It may be that you typed the wrong query, the query is taking too long, or the query is creating a performance bottleneck and needs to be stopped. After a query starts executing in Metric Miner, the Stop button changes to red and becomes active. To stop the query, click the Stop button ( ) on the Metric Miner toolbar. Run Statements 227

228 Use the Metric Miner Toolbar (page 222) Resolve Out-of-Memory Errors (page 228) Resolve Out-of-Memory Errors Metric Miner allows you to submit queries to the Neoview platform that can return large amounts of data. Metric Miner also allows you to run multiple SQL statements at the same time. These activities can potentially consume most or all of the memory on a workstation. When memory is completely consumed, it is possible to receive an out-of-memory exception error. If you receive an out-of-memory error, try one or more of these workarounds: Cancel the query. See Cancel a Query From Metric Miner (page 227). If multiple queries are executing in Metric Miner, cancel and close the tabs for each query until only a single query is running. Rerun the query with a lower value for the Rows field. See Run a SQL Statement Using Metric Miner (page 225). If a memory error leads to performance problems, close Metric Miner or HPDM, or both. If closing HPDM does not address any performance problems, restart the workstation. Export Metric Miner Data Metric Miner can export data from the Report Results pane to the clipboard, a browser, a spreadsheet, or a.csv file. You can also copy data from a single row or cell to the clipboard. To export Metric Miner data: 1. If it does not already appear in the Report Results pane, load the data that you want to export by running a SQL statement. See Run a SQL Statement Using Metric Miner (page 225). 2. Click the down arrow next to the Export button ( ), and select the export destination (Clipboard, Browser, Spreadsheet, File). All of the data in the Report Results pane is exported to the location that you selected. To copy data from a single row in the Report Results pane to the clipboard, right-click the row, and select Copy. Note that when you paste this data (into a text file, for example), Metric Miner includes the column headings for the row. To copy data from a single cell or contiguous cells: 1. Right-click the row, and select Row Details. The Row Details window appears. 2. In the Row Details window, select a cell, or click and drag to select contiguous cells. 3. Right-click anywhere in the selected cell(s), and select Copy. Use the Data Grid Features of the Report Results Pane (page 229) Control the Refresh of Metric Miner Information Suppose that you need to rerun a statement every 5 minutes. Metric Miner has a timer and other controls that make it possible to automatically rerun a statement. You can use buttons on the Metric Miner toolbar to set a refresh interval for the statement, after which the statement is rerun. The timer status bar (at the bottom of the window next to the fetch status bar) shows the number of seconds until the statement is refreshed: 228 Use Metric Miner

229 To set the refresh interval, click the Set Refresh Time button ( ), and select a refresh interval. NOTE: Once you select a refresh interval, the statement is always configured to refresh. You cannot undo the refresh setting, but you can pause the refresh. Also, when a refresh interval is selected, the Metric Miner toolbar shows an extra button. This button serves as the Pause or Resume Timer button, depending on the state of the refresh. To stop the refresh, click the Pause button ( ). To restart a paused timer, click the Resume Timer button ( ). Use the Metric Miner Toolbar (page 222) See the Parts of Metric Miner (page 220) About the Console Tab (page 191) Use the Data Grid Features of the Report Results Pane The Metric Miner Report Results pane is a data grid. Like other HPDM data grids, you can get detailed information about each column in the grid, sort the columns, search for data in a column, and customize the grid display for your own use. These topics provide more information about working with data grids: About Data Grids (page 48) Get Row Details for a Data Grid (page 49) Copy Data-Grid Information (page 50) Customize the Data Grid (page 52) Search the Data Grid (page 52) See a History of Your SQL Statements To see a history of the SQL statements executed using Metric Miner, click the History button ( ). NOTE: Metric Miner displays the History button only after you have successfully run two or more statements. The Metric Miner History dialog box appears. Double-click a row in the history to load the query into an Ad-hoc Report tab and display the Row Details dialog box. With the report loaded, you can rerun the report by clicking the button to run the SQL statement ( ). However, note that rerunning the report in this way uses any parameters passed to the report during the previous execution. See the Parts of Metric Miner (page 220) Terms Ad-hoc Report Run Statements 229

230 Create and Manage Reports Create a Report Reports that you create and store on a workstation: Are available to all users of the same workstation. Can be run against any Neoview platform to which the workstation can connect. To create a report: 1. If a report folder isn't present in the Report Explorer pane, create one. See Create a Report Folder (page 224). 2. Run the SQL statement that you want to save as a report. See Run a SQL Statement Using Metric Miner (page 225). NOTE: It is possible to create a report without running a statement, but running the statement first enables Metric Miner to display the column information in the Description tab. 3. Click the button to save the report configuration ( or ). The Report Configuration dialog box appears. 4. Fill in the fields in the Report Configuration dialog box. For more information about each field, see Use the Report Configuration Dialog Box (page 231). 5. Click [ Save ]. NOTE: Saving a report does not save the report results. It saves only the statement, the report description, and parameter information. Metric Miner does not save the results because it would require too much memory to do so. However, you can export the results, if necessary, before closing the report. See Export Metric Miner Data (page 228). 6. If needed, close the report by clicking the close button ( ). For more information, see Close a Report (page 233). Use the Report Configuration Dialog Box (page 231) Create a Report Folder (page 224) Share a Report With Another User (page 234) Delete a Report (page 233) Terms report 230 Use Metric Miner

231 Use the Report Configuration Dialog Box This table describes the fields in the Report Configuration dialog box: Tab Group Field Description General Attributes Query Drill Down Attributes Report Configuration Report Folder Location Name Title Description Author Query Version Server Version Folder Linked Reports Link Reason Linked Columns Specify the name of the report that you want to appear in the Report Explorer and in the tab title. You can also use this field to create logical folders. A logical folder is a subdivision of a report folder. To save the report to a logical folder within the report folder, append character to the name. For example, this name saves the Query 56 report to a logical folder called August Reports. August Reports@Query 56 You can also nest a logical folder within a logical folder. This name saves the Query 56 report to a logical folder called Prod Reports that is nested under the August Reports folder: August Reports@Prod Reports@Query 56 NOTE: Logical folders are not reflected in the tab title for a report. Specify the report title. This field is optional. Enter a description for the report. This field is optional. Enter the name of the report author. This field is optional. Enter the query version, if applicable. This field is optional. Enter the server version or release. This field is optional. Specify the location where you want to save the report. NOTE: Although this field controls where the report is stored, the location that you specify is not automatically designated as a report folder or visible to the Report Explorer. To designate a report folder, see Create a Report Folder (page 224). Shows the query that you typed in the SQL input area or allows you to specify a query if you haven't done so already. If you made a mistake in typing the query or if you need to make a modification, you can change the query in this tab, and changes will be saved in the report. Shows the list of reports that have been linked to the current report. Buttons are provided to add, edit, or remove linked reports. These buttons are described in the next table. Describes why a link was created. Shows the columns of the current report that are passed as parameters to the linked report. This table describes the button functions for the Drill Down Attributes tab of the Report Configuration dialog box. Button [ Add ] [ Edit ] [ Remove ] [ Save ] [ Cancel ] Description Displays the Link Reports dialog box allowing you to create new report mappings. See Link Reports in Metric Miner (page 235). Allows you to update existing mappings. See Link Reports in Metric Miner (page 235). Allows you to remove a mapping to a linked report. Saves any changes that you made to the report configuration. Cancels any changes and closes the dialog box. Create and Manage Reports 231

232 Create a Report (page 230) Create a Report Folder (page 224) Display and Run a Saved Report When you display a saved report, Metric Miner displays the statement and the report description, which can include the statement name, author, version and column information. The report results are not displayed because Metric Miner does not save the results. It would require too much memory to save the results. However, results can be exported, if necessary. To display, and optionally run, a saved report: 1. Find the report in the Report Explorer. You might need to expand the report folder and any logical folders so that you can see the icon for the report. 2. Click the icon for the report. Metric Miner opens a new tab for the report. The SQL input area shows the SQL statement, and the Description tab shows detail information for the report. NOTE: To compare one report with another report side by side, you can display any report in its own window. To do this, double-click the report tab. The report appears in a separate window. 3. If you want to run the report, check the Schema field to ensure that the selected schema is appropriate for the report. If you don't explicitly qualify the statement by specifying a 3-part ANSI name, the default schema is the currently selected value in the Schema drop-down list. 4. Click the button to run the SQL statement ( ). If the report has input parameters, a dialog box asks you to enter the parameters. 5. Enter the parameter values, if required, and click [ OK ]. If the statement is successful, results appear in the Report Results pane, and the Status Tab summarizes the execution status. If the statement is unsuccessful, an Errors tab appears under the Report Results pane. See the Parts of Metric Miner (page 220) Run a SQL Statement Using Metric Miner (page 225) Create a Report (page 230) Close a Report (page 233) Modify a Saved Report To modify a saved report: 1. Find the report in the Report Explorer. You might need to expand the report folder and any logical folders so that you can see the icon for the report. 2. Click the icon for the report. Metric Miner opens a new tab, the SQL input area shows the SQL statement, and the Description tab shows detail information for the report. 3. Click the button to save the report configuration ( ). The Report Configuration dialog box appears. 4. Modify the fields in the Report Configuration dialog box. For more information about each field, see Use the Report Configuration Dialog Box (page 231). 5. Click [ Save ]. Use the Report Configuration Dialog Box (page 231) 232 Use Metric Miner

233 Close a Report To close the currently active report, click the button to close a report ( ). To close all report tabs, click the button to close all reports ( ). NOTE: The button to close all reports ( ) is located above the Report Explorer tab. See the Parts of Metric Miner (page 220) Display and Run a Saved Report (page 232) Delete a Report When you delete a report, Metric Miner deletes the.widget file contained in the Reports folder. The file is not recoverable, so use this command with caution. To delete a report: 1. In the Report Explorer, right-click the report icon, and select Delete Report. A confirmation box asks if you want to continue. 2. Click Yes. Delete a Report Folder (page 224) Rename a Report or Report Folder You cannot rename a configured report by changing the file name, but you can save the report configuration as a new report and designate a new name for it. See Copy a Report (page 233). You must not rename a report folder or attempt to move the folder. If you do so, the Report Explorer will not be able to display the folder or the reports contained within it. Instead, create a new folder, and copy reports to the new folder. Copy a Report (page 233) Create a Report Folder (page 224) Copy a Report To copy a configured report: 1. In the Report Explorer, click the report that you want to copy. Clicking the report selects it and causes the SQL statement to be loaded into the SQL input area and the report details to be loaded into the Description tab. 2. On the Metric Miner toolbar, click the button to save the report configuration as a new report ( ). The Report Configuration dialog box appears. NOTE: To avoid duplicate report names, Metric Miner changes the report name to Copy_of_name. 3. Fill in the fields in the Report Configuration dialog box. For more information, see Use the Report Configuration Dialog Box (page 231). 4. Click [ Save ]. Modify a Saved Report (page 232) See the Parts of Metric Miner (page 220) Create and Manage Reports 233

234 Use the Metric Miner Toolbar (page 222) Create a Report (page 230) Share a Report With Another User All reports residing on a workstation are available to all users of the same workstation. To share a report with a user on a different workstation, make a copy of the.widget file for the report, and send it to the other user. The.widget file can be found in the report folder, the location of which is shown in the Report Explorer. The user receiving the.widget file must copy the file to his or her report folder. Metric Miner will display the file as soon as it is copied to a report folder. See the Parts of Metric Miner (page 220) Create a Report Folder (page 224) Use Preconfigured Reports Included With Metric Miner When you install HPDM, a folder of preconfigured reports is loaded on your workstation. Look for the Reports folder in the HPDM installation directory. The installation directory is typically C:\Program Files\Hewlett-Packard\HP Database Manager; however, the installer can optionally place the files in a different location. To view and sample these reports, you can designate the Reports folder as a report folder or copy the files to another designated report folder. When you do so, the files should become visible in the Report Explorer. See Create a Report Folder (page 224). Import Neoview Reports (page 234) Compare Metric Miner, SQL Whiteboard, and Neoview Reports (page 219) Import Neoview Reports You might have Neoview reports to import if you migrated to Release 2.5 from an earlier Neoview release. Neoview Reports are stored on the Neoview platform. With assistance from your HP support representative, you can import Neoview Reports into Metric Miner. HP support must convert the Neoview Reports into one or more text files that contain the SQL text and some tags for additional information. During the import process, HPDM reads each text file, parses it, and creates an XML file for use by Metric Miner. To import a Neoview Reports text file: 1. Arrange to have an HP support representative convert your Neoview Reports into one or more text files that can be copied to the workstation on which you use Metric Miner. 2. In the Report Explorer, right-click the report folder in which you want to store the Neoview Reports, and select Import NV Report. The Select Neoview Report File dialog box appears. 3. Select the text file (or multiple files) provided by HP support, and click [ Open ]. If a single file is selected, Metric Miner displays the Report Configuration dialog box, allowing you to update report information before saving the file. If multiple files are selected, all the files are imported without any user prompt, and you do not need to perform the next step. 4. Make any necessary changes, and click [ Save ] to import a single file. 5. In the Report Explorer, right-click the report folder, and select Refresh to update the contents of the report folder so you can view the imported report(s). Compare Metric Miner, SQL Whiteboard, and Neoview Reports (page 219) Use Preconfigured Reports Included With Metric Miner (page 234) 234 Use Metric Miner

235 Link and Drill Down Link Reports in Metric Miner Suppose you have a series of reports, and some of them require input parameters. And suppose various column values from one report can serve as the input parameters for another report. Using Metric Miner, you can link the reports. Linking makes it possible to double-click a row (or right-click a row and select Drill Down) in one report and pass one or more values from selected columns in that row to another report. Drill-down capability saves you the trouble of having to load and run many SQL statements with different input parameters. It also makes it possible to quickly see the effects of different input values on a report. You can link reports as part of report configuration, or you can link them as part of drill down. To link reports: 1. Display (open the tab for) the calling report. This is the report whose result data will be passed to the called report. For more information about displaying a report, see Display and Run a Saved Report (page 232). 2. Use these steps to display the Link Reports dialog box so that you can create report mappings: a. Click the button to save the report configuration ( ). The Report Configuration dialog box appears. b. Click the Drill Down Attributes tab. c. Click [ Add ]. TIP: Another way to display the Link Reports dialog box is to double-click a row in the Report Results Pane or right-click a row and select Drill Down. The Select Report dialog box appears. Click [ Add ]. 3. In the Link Reports dialog box, select a report in the Drill down to Report list. If the report has input parameters, the input parameters appear in the Map Columns list at the bottom of the dialog box. 4. Under the Column Name column, click the down arrow and select a table column to map to each input parameter. 5. Optional: In the Link Reason box, type a reason for the association between the reports. 6. Click [ OK ] to close the Link Reports dialog box. 7. In the Report Configuration dialog box, click [ Save ]. 8. Test the link by drilling down on a row in the calling report. See Drill Down Through Linked Reports in Metric Miner (page 236). Add Parameters to Statements (page 226) Drill Down Through Linked Reports in Metric Miner (page 236) Use the Link Reports Dialog Box (page 236) Link and Drill Down 235

236 Use the Select Report Dialog Box This table describes the fields in the Select Report dialog box: Field Linked Reports Link Reason (Describes the association between the reports) Passed Values Description Lists the reports that are linked to the calling report. Text entered by the report author to document the mapped columns between reports. Shows the parameter values that will be passed to the called report selected in the Linked Reports list. This table describes the button functions in the Select Report dialog box: Button [ Add ] [ Edit ] [ Delete ] [ OK ] [ Cancel ] Description Displays the Link Reports dialog box allowing you to add a linked report. Allows you to update the list of linked reports. Allows you to remove a report mapping. Saves any changes that you made. Cancels any changes, closing the dialog box. Link Reports in Metric Miner (page 235) Drill Down Through Linked Reports in Metric Miner (page 236) Use the Link Reports Dialog Box This table describes the fields in the Link Reports dialog box: Field Drill from Report: Drill down to Report Link Reason (Describes the association between the reports) Map Columns from calling report to Parameters of called report Description Identifies the calling report. This is the report that will provide column data to the called report. Lists all reports that have been loaded into the Report Explorer. Select a report from this list to establish a column mapping. This is the called report. Text entered by the report author to document the mapped columns between reports. Shows all columns in the called report that can have input parameters. In the Column Name column, select the table columns that you want to map to the input parameters. Link Reports in Metric Miner (page 235) Use the Select Report Dialog Box (page 236) Drill Down Through Linked Reports in Metric Miner (page 236) Drill Down Through Linked Reports in Metric Miner To drill down through linked reports: 236 Use Metric Miner

237 1. Display (open the tab for) the calling report. This is the report whose result data will be passed to the called report. For more information about displaying a report, see Display and Run a Saved Report (page 232). 2. Refresh or execute the report so that results are loaded into the Report Results pane. For more information, see Run a SQL Statement Using Metric Miner (page 225). 3. In the Report Results pane, double-click a result row, or right-click anywhere in the row and select Drill Down. The Select Report dialog box appears. 4. In the Linked Reports list, select a linked report. The Passed Values section of the dialog box shows the information that will be passed to the linked report. If no linked reports are present, you can add one by clicking [ Add ]. See Link Reports in Metric Miner (page 235). The dialog box also allows you to edit an already linked report, or remove a currently linked report. 5. If the Passed Values are okay, click [ OK ]. Metric Miner runs the linked report using the values passed from the selected row of the calling report. If the Passed Values are not okay, you can click the down arrow for each parameter to select from previously passed values or cancel the operation and select a different row in the calling report. NOTE: If the linked report is already loaded, a dialog box asks if you want to create a new instance of the linked report. Click [ Yes ] or [ No ]. 6. To pass different values to the linked report, repeat the steps in this procedure, drilling down on other rows in the original report. Link Reports in Metric Miner (page 235) Use the Select Report Dialog Box (page 236) Link and Drill Down 237

238 238

239 21 Launch the Neoview Command Interface (NCI) Learn About NCI The Neoview platform supports a client-based utility, Neoview Command Interface (NCI), which enables you to enter SQL statements interactively or from script files in its command-line interface. You can also pass an SQL statement to NCI from a Perl or Python command line or from a Perl or Python program. For more information about using NCI, see the Neoview Command Interface (NCI) Guide located on the customer documentation Web site. See Resources on the Web (page 17). Or use the command-line help within NCI. The help describes the commands supported in the current operating mode of NCI. Locate the NCI Program (page 239) Launch NCI (page 239) Set Auto Logon Options (page 240) Locate the NCI Program Launch NCI The HPDM application locates the NCI program in the NCI default install location. If the NCI program is not found in the default install location, a window appears and allows you to browse for the NCI installation location. Once the NCI program is located, the location persists. If NCI becomes uninstalled for any reason, you must use the same process to locate the NCI program again. You can change the location of the NCI program at any time by using the Tools > Options window. Launch NCI (page 239) Set Auto Logon Options (page 240) To launch NCI, use one of these methods: Click the Neoview Command Interface button ( ) on the HPDM toolbar. For more information about the HPDM toolbar, see Use the HPDM Toolbar (page 44). From the HPDM main menu, select Tools > Neoview Command Interface. The NCI interface launches in a separate window. User credentials from the HPDM session are used to log on to NCI. The data source and schema name also are taken into consideration. NCI sets these values (if specified) during the auto logon process. To set auto logon properties, see Set Auto Logon Options (page 240). Log on to the Neoview system and select Tools > Neoview Command Interface, the NCI window appears with a prompt ready to execute NCI commands. If NCI is launched and you are not logged on to a system, NCI does not use auto logon. Instead, NCI launches and prompts for an IP address (which is the default behavior in NCI). Under the Tools menu, select Options. The Options window is available only from the HPDM main window. The Option window is not available for cloned windows. You can set the path for the NCI.exe and the auto logon options Learn About NCI (page 239) Locate the NCI Program (page 239) Set Auto Logon Options (page 240) Learn About NCI 239

240 Set Auto Logon Options To set the NCI auto logon features, click the Options button ( ) on the HPDM toolbar, or select Tools > Options from the HPDM menu. Select Neoview Command Interface in the left pane of the Options window. The Options window displays a dialog box where auto logon features can be set for NCI. Auto logon can be disabled or enabled. The NCI prompt can be set to prompt specific options. The NCI prompt can be customized: Option Auto Logon Prompt Options Custom Prompt Description Click the check box to enable NCI auto logon. Click User, Server, or Schema to include these items in the NCI prompt when auto logon is also checked. When this item is checked, you may enter a custom prompt into the text field. Learn About NCI (page 239) Locate the NCI Program (page 239) Launch NCI (page 239) 240 Launch the Neoview Command Interface (NCI)

241 22 Manage Disk Space About Space Management Space Management is a new area within HPDM that enables the monitoring and display of SQL space-related data for the Neoview platform. The displayed space data includes six panes of detailed SQL-space usage statistics. Space Management allows you to display SQL space by user, by schema, by table, and by partition. It also helps you identify and react to fast-growing tables by looking at historical trends. NOTE: For this release, the Space Management area includes only SQL space reporting and does not provide a space-management solution for an entire Neoview system. Terms area Display the Space Management Area To display the Space Management area: 1. In the navigation tree pane, select a connected system for which you want to obtain SQL space usage information. If no system is configured, see Add a System (page 29). 2. Select the Space Management area. For more information about areas, see Select an Area (page 35). 3. Fill in the Connect / Edit System dialog box, and click Connect. For more information, see Use the Connect / Edit System Dialog Box (page 26). About Space Management 241

242 4. In the right pane, click the Monitoring tab. After successful logon to a Neoview system: Space references are verified. Last inventory information is retrieved. The Over Threshold Summary is fetched. The System Overall and System Detail panes are automatically populated. The SQL Objects and SQL Objects Detail panes are populated when you double-click an area of the pie chart or select a row in the System Detail pane. The Partition Distribution Across Disks and Table Growth panes are populated by using either of these methods: Select and double-click a bar in the graph of the SQL Objects pane. Select and double-click a row in the SQL Objects Detail pane. NOTE: At any time, you can refresh other panes, change values in the drop-down box, or select a bar graph in the SQL Objects pane or select a row in the SQL Objects Detail pane. See the Parts of Space Management (page 243) Understand Space Usage Statistics (page 245) 242 Manage Disk Space

243 See the Parts of Space Management Space Management shows SQL space usage statistics for a Neoview system, including SQL objects, partition distribution across disks, and table growth. You can monitor and display space usage as a pie chart, bar graph, data grid, timeline, or a combination. Space Management presents information in a graphic and row format. Space Management reports on a Neoview system and plots multiple metrics on different graphs. You choose which metrics are reported on, and then selectively view each in the graph. Space Management employs a color scheme to display each metric and its performance. Each pane in the Monitoring tab can be enlarged by clicking the box icon on the right of the heading. When the display is focused on one pane, you can no longer view information from the other panes. To return to the full system view, click the box icon again. At the top of the Monitoring tab, connection information and last inventory status are displayed. This figure shows the parts of the Space Management interface. For easier viewing, the display is divided into two vertical parts (left side and right side): See the Parts of Space Management 243

244 244 Manage Disk Space

245 About the Monitoring Tab (page 246) Understand Space Usage Statistics Space Management shows six panes of detailed SQL space usage statistics: Pane System Overall System Detail SQL Objects Description Pie chart view of the amount of space used on the Neoview by Category, Schema, Table, or by User. Detailed grid view of the total SQL space size per schema. Bar graph view of the SQL objects within the schema (including base tables, materialized views, and indexes). Understand Space Usage Statistics 245

246 Pane SQL Objects Detail Partition Distribution Across Disks Table Growth Description Detailed grid view of the SQL objects within the schema. Bar graph view of the partition distribution across all disks in the system in megabytes (MB). Timeline view of the object sizes by table and the top fastest growing tables in the system. About the Monitoring Tab (page 246) About the Monitoring Tab The Monitoring tab provides an SQL space snapshot of a selected Neoview system. A graphical view visually depicts the system overall, including SQL objects, partition distribution across disks, and table growth. The Monitoring tab is the first point of reference for displaying SQL space management information. The Monitoring tab shows multiple bar graphs, data grids, and a timeline that represents a total view of the SQL space usage information for a selected system: View the Over Threshold Summary The Over Threshold Summary bar instantly allows you to identify if any disks, tables, or partitions are reaching a specified threshold level. Only entries that meet threshold criteria are displayed. 246 Manage Disk Space

247 To display the Over Threshold Summary, display the Monitoring tab, and click the double arrows at the top of the Logical Space tab: The Over Threshold Summary bar allows you to configure these fields: Field or Option %Full Max Rows for Each Type Disk Category Description You can enter a percentage value and only those disks, tables, and partitions exceeding the value are displayed. Shows the maximum number of rows for disks, table, and partitions. The default value is 10 (displays a maximum of 30 rows). By default, data disks and $SYSTEM are considered. Selecting the Audit check box includes all audit disks ($MAT* and $AUD*). In the Over Threshold Summary, these fields are displayed for disks, tables, and partitions: Field Type Date Time Segment Object Name %Full %User Full Description Specifies type as: DISK, PARTITION, or TABLE. A snapshot of the time when the space data was last collected. Displays the segment name. Displays the disk name, table name, or partition name. Fetches details from a Neoview Repository view: NEO.HP_METRICS.DISK_STATS_V1.FULL_PCT. Displays the percentage of user full. Percent values are computed according to the total user space, which is always less than the total platform space. HP uses some space for swap files, scratch space, and other support functions. In the pie chart, % values are calculated using total user space as the 100% reference. This figure shows the Over Threshold Summary where you can view disks, tables, or partitions that have exceeded a specified threshold of 50%: View the Over Threshold Summary 247

248 Use [ Refresh ] to refresh the Over Threshold Summary data grid. To change the sort order of a displayed column: Click the title of the column that you want to sort in ascending or descending order. See Sort and Move Data Columns (page 47). For more information about customizing the data grid, see Customize the Data Grid (page 52). The buttons across the bottom of the notification window allow you to export data: Button [ Data to Clipboard ] [ Data to Browser ] [ Data to Spreadsheet ] [ Data to File ] Function Copies the table data to the Windows clipboard. See Export Data (page 53). Opens a browser to display the data in a tabular format. See Export Data (page 53). Opens the Excel application and displays the data. See Export Data (page 53). Exports the data to a file in CSV format. See Export Data (page 53). View the System Overall The System Overall pane is a pie chart that is automatically populated and displays the amount of SQL space used on the Neoview by Category, by Schema, by Table, or by User. From the Space Management area: 1. Select a system you want to view details about. 2. Click the Monitoring tab. 3. View the System Overall pane. Click the box icon on the right of the heading to enlarge the view of the System Overall pane. When the display is focused on one pane, you can no longer view information from the other panes. To return to the full system view, click the box icon again. 248 Manage Disk Space

249 This figure shows a snapshot of the System Overall pane and the free space available: In the System Overall pane, you can: 1. Select a value for Type in the drop-down box. 2. Select a value for Count in the drop-down box. 3. Optionally, select the check boxes Others or Free. 4. Click [ Refresh ] to refresh the pane by re-fetching the space information for the specified type. In the System Overall pane, these fields can be selected in the drop-down box: Field or Option Type Count Others Free Description Select the type of information to be retrieved. The type values are: CATEGORY, SCHEMA, TABLE, or USER. (User is a role and is not associated with an LDAP user). Select the maximum number of areas to be displayed. The maximum count value is Captures the categories that do not make the top 10 (if the count is set to 10). You can select or deselect this check box. This field is optional. Captures the overall free space on the system. Objects less than 1% are listed on the top left-side. You can select or deselect this check box. This field is optional. NOTE: Percent values are computed according to the total user space. When Neoview is sold, a customer is sold x% of total physical disk space; HP needs the remaining SQL infrastructure to work well (for example, scratch space, swap space, etc.). On a Neoview C model, total user space is 66% of total physical disk space. On a Neoview E model, total user space is 64%. In the pie chart, % values are calculated using total user space as the 100% reference View the System Detail The System Detail pane is a data grid that is automatically populated and summarizes the total SQL space used for each schema. If the schema contains both partitioned and non-partitioned tables, then two rows are found in the data grid. In the System Detail pane each schema occupies a separate row in the data grid. View the System Detail 249

250 From the Space Management area: 1. Select a system you wish to view details about. 2. Click the Monitoring tab. 3. View the System Detail pane. Click the box icon on the right of the heading to enlarge the view of the System Detail pane. When the display is focused on one area, you can no longer view information from the other areas. To return to the full system view, click on the box icon again. This figure shows a snapshot of the System Detail pane: To activate the System Detail pane, you can either: 1. Select a row in the data grid and click [ Refresh ] to refresh the pane by re-fetching the space information for the specified schema. 2. Double-click a row in the data grid. If you click the Filter Settings bar, you can: Select the columns to be displayed in the data grid. Select the partition types to be displayed (partition and non-partitioned). Enter the maximum number of rows to be viewed. NOTE: In the filter options, the schema setting is required. This figure shows the filter settings that you can select (by clicking on the check boxes) to be displayed in the data grid: 250 Manage Disk Space

251 To change the sort order of a displayed column: Click the title of the column that you want to sort in ascending or descending order. See Sort and Move Data Columns (page 47). For more information on customizing the data grid, see Customize the Data Grid (page 52). In the System Detail pane, these fields are displayed: Field or Option Date Time Catalog Schema Space Type Number of Objects Schema Size %Used Description The last time space data was captured. Displays the catalog name of the schema. Displays the SQL schema name. Specifies the space type as partitoned or non-partitioned. Specifies the number of objects in the schema (objects can be base tables, materialized views, or indexes). Specifies the total size of the individual objects in the schema in megabytes (MB). Indicates the percentage of schema size versus total user space. The buttons across the bottom of the System Detail pane allow you to export data: Button [ Data to Clipboard ] [ Data to Browser ] Function Copies the table data to the Windows clipboard. See Export Data (page 53). Opens a browser to display the data in a tabular format. See Export Data (page 53). View the System Detail 251

252 Button [ Data to Spreadsheet ] [ Data to File ] Function Opens the Excel application and displays the data. See Export Data (page 53). Exports the data to a file in CSV format. See Export Data (page 53). View SQL Objects The SQL Objects pane is a bar graph view of the SQL objects in the schema. The SQL objects are viewed largest to smallest. Objects limited in size are not represented in the bar graph. The title of the bar graph represents the name of the schema. From the Space Management area: 1. Select a system you wish to view details about. 2. Click the Monitoring tab. 3. To activate the SQL Objects pane, you can either: Double-click an area of the pie chart. Double-click a row in the System Detail pane or select a row and click [ Refresh ] to refresh the pane by re-fetching the SQL objects within the schema. 4. To enlarge the view of the SQL Objects pane, click the box icon on the right of the heading. When the display is focused on one area, you can no longer view information from the other areas. To return to the full system view, click on the box icon again. 5. In the SQL Objects pane, you can: Select a value for Type in the drop-down box. Select a value for Count in the drop-down box. Click [ Refresh ] to refresh the pane by re-fetching the SQL objects in the schema. This figure shows the SQL Objects pane which displays the objects/sizes within the schema named TPCDS1000: 252 Manage Disk Space

253 NOTE: The name and size of the object appears whenever you place your cursor on a bar in the graph. In the SQL Objects pane, these fields can be selected in the drop-down box: Field or Option Type Count Description Specifies type as: base table (BT), materialized view (MV), index (IX), or ALL. The ALL option displays all objects. Specifies the number of objects to be displayed. View the SQL Objects Detail The SQL Objects Detail pane is a data grid of the SQL objects within a schema. In the SQL Objects Detail pane each schema occupies a separate row in the data grid. From the Space Management area: 1. Select a system you wish to view details about. 2. Click the Monitoring tab. 3. To activate the SQL Objects Detail pane, you can either: Double-click an area of the pie chart. Double-click a row in the System Detail pane or select a row and click [ Refresh ] to refresh the pane by re-fetching the SQL objects within the schema. 4. To enlarge the view of the SQL Objects Detail pane. Click the box icon on the right of the heading to enlarge the view of the SQL Objects Detail pane. When the display is focused on one pane, you can no longer view information from the other panes. To return to the full system view, click on the box icon again. View the SQL Objects Detail 253

254 This figure shows a view of the SQL Objects Detail pane: If you click the Filter Settings bar, you can: Select the columns to be displayed in the data grid. Enter the maximum number of rows to be viewed, default is NOTE: In the filter options, the object name is required. This figure shows the filter settings that you can select (by clicking on the check boxes) to be displayed in the data grid: 254 Manage Disk Space

255 To change the sort order of a displayed column: Click the title of the column that you want to sort in ascending or descending order. See Sort and Move Data Columns (page 47). For more information on customizing the data grid, see Customize the Data Grid (page 52). In the SQL Objects Detail pane, these fields are displayed: Field or Option Date Time Catalog Schema Object Type Object Name Object Name Space Row Count Object Size Number of Partitions Last Update Stats: Description The last time space data was captured. Specifies the SQL catalog name. Displays the SQL schema name. Specifies the type of SQL object. The object type values are: base table (BT), materialized view (MV), or index (IX). Specifies the SQL object name. Specifies the object name space as: CN Constraint IX Index LK Lock TA Table value object (table, view, stored procedure, SQL/MP alias) TR Trigger TT Trigger temp table The actual number of rows. This value may not be collected by the Inventory process if the option is turned OFF. Obtaining this value increases total inventory time. Specifies the object size in megabytes (MB). Specifies the number of partitions for the SQL object. No partition is 0. Displays the time and date when statistics were last updated. View the SQL Objects Detail 255

256 Field or Option Stats Row Count: %Full Description Number of rows from the histogram (accuracy depends on when statistics was last updated). Indicates the full size of the object. The buttons across the bottom of the SQL Objects Detail pane allow you to export data. Button [ Data to Clipboard ] [ Data to Browser ] [ Data to Spreadsheet ] [ Data to File ] Function Copies the table data to the Windows clipboard. See Export Data (page 53). Opens a browser to display the data in a tabular format. See Export Data (page 53). Opens the Excel application and displays the data. See Export Data (page 53). Exports the data to a file in CSV format. See Export Data (page 53). View Partition Distribution Across Disks The Partition Distribution Across Disks pane is a bar graph view of the partition distribution across all disks in megabytes (MB). The title of the bar graph represents the name of the table. Partition distribution across disks identifies skew (partitions of different sizes) which may indicate a problem with table partitioning and slow down performance. From the Space Management area: 1. Select a system you wish to view details about. 2. Click the Monitoring tab. 3. To activate the Partition Distribution Across Disks pane, you can either: Double-click a bar in the graph of the SQL Objects pane Double-click a row in the SQL Objects Detail pane or select a row and click [ Refresh ] to refresh the pane by re-fetching the SQL objects within the schema. 4. To enlarge the view of the View Partition Distribution Across Disks pane, click the box icon on the right of the heading. When the display is focused on one pane, you can no longer view information from the other panes. To return to the full system view, click on the box icon again. NOTE: At any time, you can refresh other panes, change values in the drop-down box, or select a bar graph in the SQL Objects pane or select a row in the SQL Objects Detail pane. This figure shows the View Partition Distribution Across Disks pane and displays the partition sizes for the disks in the table named STORE_SALES: 256 Manage Disk Space

257 In the Partition Distribution Across Disks pane, you can: 1. Select a value for Count in the drop-down box. 2. Select a value for Delta from AVG in the drop-down box. 3. Click [ Refresh ] to refresh the pane by re-fetching the partition distribution. In the Partition Distribution Across Disks pane, these fields can be selected in the drop-down box: Field or Option Count Delta from AVG Description Specifies the maximum number of partitions displayed. Specifies the percent (%) difference compared to the average partitions size (delta can represent above or below the average size). The bar graph color communicates an acceptable range for partition size: Color Red Green Description Indicates the partition size is higher or lower than the average partition size (for more than the Delta % specified). Indicates the partition size is within an acceptable range (for the Delta % specified). View Table Growth The Table Growth pane shows a graphical view of the object sizes by table and the top fastest growing tables. The title of the bar graph represents the name of the table. You can select a date range for the graph. Data is retrieved from the space historical view. From the Space Management area: 1. Select a system you wish to view details about. 2. Click the Monitoring tab. View Table Growth 257

258 3. To activate the Table Growth pane, you can either: Double-click a bar in the graph of the SQL Objects pane Double-click a row in the SQL Objects Detail pane 4. To enlarge the view of the Table Growth pane, click the box icon on the right of the heading. When the display is focused on one pane, you can no longer view information from the other panes. To return to the full system view, click on the box icon again. NOTE: At any time, you can refresh other panes, change values in the drop-down box, or select a row in the SQL Objects Detail pane. This figure shows a snapshot of the Table Growth pane which displays the object sizes for the table named QUERY_STATS, during the last quarter: By Table Tab In the Table Growth pane, you can view growth by table or show the top fastest growing tables in the schema: By Table Tab (page 258) Top Fastest Growing Tables Tab (page 260) The By Table tab allows you to view the object sizes by table and specify the interval for which data is fetched. This figure shows a snapshot of the By Table tab which displays the object sizes for the table named T100K, during the last quarter: 258 Manage Disk Space

259 1. Select a date range for the graph using the drop-down boxes. By default, the By Table data grid fetches table details for the last quarter. You can also select other time range options: Custom Range Last day Last week Last month Last quarter Last year 2. Click [ Refresh ] to refresh the pane by re-fetching table growth information. The bar graph color communicates table growth: Color Red Yellow Blue Description Indicates the minimum and maximum table growth. Indicates average table growth. Indicates current table growth. The buttons across the bottom of the By Table tab allow you to export data. Button [ Data to Clipboard ] [ Data to Browser ] [ Data to Spreadsheet ] [ Data to File ] Function Copies the table data to the Windows clipboard. See Export Data (page 53). Opens a browser to display the data in a tabular format. See Export Data (page 53). Opens the Excel application and displays the data. See Export Data (page 53). Exports the data to a file in CSV format. See Export Data (page 53). View Table Growth 259

260 Top Fastest Growing Tables Tab The Top Fastest Growing Tables tab allows you to view the top fastest growing tables (in bytes per second) and specify a date interval for which data is fetched. This figure shows a snapshot of the Top Fastest Growing Tables tab which displays the object sizes for a table named T100K during a custom selected time range: 1. Select a date range for the graph using the drop-down boxes. By default, the Top Fastest Growing Tables data grid fetches table details for the last quarter. You can also select other time range options: Custom Range Last day Last week Last month Last quarter Last year 2. Click [ Refresh ] to refresh the pane by re-fetching table growth information. In the Top Fastest Growing Tables tab, these fields are displayed: Field or Option Catalog Schema Description Specifies the SQL catalog. Specifies the SQL schema. 260 Manage Disk Space

261 Field or Option Object Name Space Object Name Start Size End Size Description Specifies the object name space as: CN Constraint IX Index LK Lock TA Table value object (table, view, stored procedure, SQL/MP alias) TR Trigger TT Trigger temp table Specifies the SQL object name. The object size corresponds to the start time (or close to the start time), in megabytes (MB). The object size corresponds to the endme (or close to the end time), in megabytes (MB). The buttons across the bottom of the Top Fastest Growing Tables tab allow you to export data. Button [ Data to Clipboard ] [ Data to Browser ] [ Data to Spreadsheet ] [ Data to File ] Function Copies the table data to the Windows clipboard. See Export Data (page 53). Opens a browser to display the data in a tabular format. See Export Data (page 53). Opens the Excel application and displays the data. See Export Data (page 53). Exports the data to a file in CSV format. See Export Data (page 53). Understand Historical Space Data Historical tables contain aggregated rows. Historical space data is based on an In-Place Data Aging algorithm: History grows over time, but remains in the same table. Displays more granularity when the selected period is closer to present time and displays less granularity when the selected period is further away from present time. Displays less granularity for older tables. Aggregated records retain the average, maximum, minimum, and current. You can specify the period of time as follows: Hourly records are aggregated into a daily record Daily records are aggregated into a weekly record Month daily records are aggregated into a monthly record Month records are aggregated into a quarterly record Quarterly records are aggregated into a yearly record Yearly records are retained indefinitely About the Configuration Tab The Configuration tab allows you to select specific configuration criteria for a system. The Configuration tab is displayed only if you log on as a user in the role of ROLE.DBA or SUPER.SERVICES. The Configuration tab includes the: General tab Advanced tab This figure shows the Configuration tab: Understand Historical Space Data 261

262 About the General Tab The General tab includes these groups: Inventory Control (page 262) Inventory Process Detail Status (page 264) Inventory Control The Inventory Control group allows you to define the inventory criteria to be displayed: Field or Option EXCLUDE percent sign (%) Description Use the EXCLUDE check box to exclude full inventory of a catalog, schema, or object in the inventory criteria. Deselecting the EXCLUDE check box allows full inventory of that object to be displayed. If you specifiy a catalog name, schema name, or object name the inventory is limited to those objects. Specifies all objects are displayed. In the Inventory Commands group, these buttons can be selected: Field or Option [ Start ] [ Pause ] Description Starts an inventory. Pauses the inventory. 262 Manage Disk Space

263 Field or Option [ Resume ] [ Stop ] [ Status ] Description Resumes the inventory. Stops the inventory. Obtains status and displays the progress at the bottom of the screen. In the Others area, you can configure these settings: Field or Option Space Reference Settings Inventory Stats Refresh If objects are reaching the specified threshold, automatically show the notification window Description Displays a window that specifies the locations of the space references. These references are verified at startup after log on. If any reference settings are not valid, a dialog box displays a warning message, but the Space client continues to execute. If any reference is incorrect, multiple SQL errors could be generated upon refresh. See Space Reference Settings (page 263). NOTE: Space reference settings can change the location for space tables or views, but these settings should not be changed by customers. Controls the refresh interval for the Last Inventory information displayed at the top of the screen. You can select or deselect this option. Displays the Over Threshold dialog automatically if thresholds are reached. You can select or deselect this option. See View the Over Threshold Summary (page 246). Space Reference Settings Space reference settings specifies the location of the space references and allows you to point to alternate space table and views. This figure shows the Space Reference Settings dialog box: About the Configuration Tab 263

264 The references are verified upon startup after initial logon and also verified each time you switch to another already connected system. If any of the references specified cannot be found, a dialog box displays a warning, but the Space Management client continues to run. If tables are missing, you run into multiple SQL errors upon refresh of the schema. In the Space Reference Settings dialog box, these fields are displayed: Category Table View SPJ Field or Option SQL System Registry SQL Snapshot Period SQL Class Rule SQL Status SQL Space SQL Space History Disk Status SPJ Name Description Defines space parameters in terms of user space and disk capacity. Controls data aging and aggregation (historical data). Defines categories of space data. Contains inventory status. Last inventory space data. Historical space data. Repository Disk View (used for %full). SPJ controls inventory (Start, Status, and so on). Inventory Process Detail Status The Inventory Process Detail Status area displays detailed status of the inventory process. About the Advanced Tab The Advanced tab includes these groups: Inventory Options (page 265) Update Space Reference Tables (page 265) This figure shows the Advanced tab: 264 Manage Disk Space

265 Inventory Options In the Inventory Options group, these options can be selected in the drop-down box: Field or Option Process Count Config Rate Description Number of parallel processes used for inventory. An internal pacing value keeping inventory from using too many system resources. Update Space Reference Tables In the Update Space Reference Tables group, these tabs can be selected: Tab Snapshot Periods Table Classification Rule Description Exposes the table that controls space data aging and aggregation. If you change the values, you need to restart the space aging component on a Neoview platform for the changes to be in effect. NOTE: Unless specifically recommended by HP support, these values should not be changed. Exposes the table that controls categorization of space information. If you change the values, you need to restart the space provider component on a Neoview platform for the changes to be in effect. Snapshot Periods Table Tab This figure displays the Snapshot Periods Table tab: Classification Rule Table Tab This figure displays the Classification Rule Table tab: About the Configuration Tab 265

266 System Registry Table Tab This figure displays the System Registry Table tab: About Space Management Tracing Options The Space Management Options dialog box shows tracing controls for Space Management. These tracing controls are for HP support use only. 266 Manage Disk Space