DOCSLIB.ORG

Administering JDBC Data Sources for Oracle Weblogic Server

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Administering JDBC Data Sources for Oracle Weblogic Server Oracle® Fusion Middleware Administering JDBC Data Sources for Oracle WebLogic Server 12c (12.2.1.4.0) E90814-06 October 2020 Oracle Fusion Middleware Administering JDBC Data Sources for Oracle WebLogic Server, 12c (12.2.1.4.0) E90814-06 Copyright © 2007, 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle. Contents Preface Documentation Accessibility xvi Conventions xvi 1 Introduction and Roadmap Document Scope and Audience 1-1 Guide to this Document 1-1 Related Documentation 1-2 JDBC Samples and Tutorials 1-3 Avitek Medical Records Application (MedRec) and Tutorials 1-3 JDBC Examples in the WebLogic Server Distribution 1-3 New and Changed JDBC Data Source Features in This Release 1-3 2 Configuring WebLogic JDBC Resources Understanding JDBC Resources in WebLogic Server 2-1 Ownership of Configured JDBC Resources 2-2 Data Source Configuration Files 2-2 JDBC System Modules 2-3 Generic Data Source Modules 2-3 Active GridLink Data Source System Modules 2-4 Multi Data Source System Modules 2-4 JDBC Application Modules 2-5 Standard Java EE Application Modules 2-5 Proprietary JDBC Application Modules 2-5 JDBC Module File Naming Requirements 2-7 JDBC Modules in Versioned Applications 2-7 JDBC Schema 2-8 JDBC Data Source Type 2-9 JMX and WLST Access for JDBC Resources 2-9 JDBC MBeans for System Resources 2-10 iii JDBC Management Objects in the Java EE Management Model (JSR-77 Support) 2-10 Using WLST to Create JDBC System Resources 2-11 How to Modify and Monitor JDBC Resources 2-13 Best Practices when Using WLST to Configure JDBC Resources 2-13 Creating High-Availability JDBC Resources 2-13 3 Configuring JDBC Data Sources Understanding JDBC Data Sources 3-1 Types of WebLogic Server JDBC Data Sources 3-1 Creating a JDBC Data Source 3-2 JDBC Data Source Properties 3-2 Data Source Names 3-3 Data Source Scope 3-3 JNDI Names 3-3 Selecting a Database Type 3-3 Selecting a JDBC Driver 3-3 Configure Transaction Options 3-6 Configure Connection Properties 3-7 Configuring Connection Properties for Oracle BI Server 3-7 Test Connections 3-7 Target the Data Source 3-7 Configuring Generic Connection Pool Features 3-7 Enabling JDBC Driver-Level Features 3-8 Enabling Connection-based System Properties 3-9 Enabling Connection-based Encrypted Properties 3-10 Initializing Database Connections with SQL Code 3-10 Advanced Connection Properties 3-11 Define Fatal Error Codes 3-11 Using Edition-Based Redefinition 3-12 Configuring Oracle Parameters 3-14 Configuring an ONS Client 3-14 Tuning Generic Data Source Connection Pools 3-15 Generic Data Source Handling for Oracle RAC Outages 3-15 Generic Data Source Handling of Driver-Level Failover 3-15 4 Using the Default Data Source What is the Default Data Source 4-1 Defining a Custom Default Data Source 4-2 iv Compatibility Limitations When Using a Default Data Source 4-3 5 Configuring JDBC Multi Data Sources Multi Data Source Features 5-1 Removing a Database Node 5-2 Adding a Database Node 5-2 Creating and Configuring Multi Data Sources 5-3 Choosing the Multi Data Source Algorithm 5-3 Failover 5-3 Load Balancing 5-4 Multi Data Source Fail-Over Limitations and Requirements 5-4 Test Connections on Reserve to Enable Fail-Over 5-4 No Fail-Over for In-Use Connections 5-4 Multi Data Source Failover Enhancements 5-5 Connection Request Routing Enhancements When a Generic Data Source Fails 5-5 Automatic Re-enablement on Recovery of a Failed Generic Data Source within a Multi Data Source 5-5 Enabling Failover for Busy Generic Data Sources in a Multi Data Source 5-6 Controlling Multi Data Source Failover with a Callback 5-6 Callback Handler Requirements 5-6 Callback Handler Configuration 5-7 How It Works—Failover 5-7 Controlling Multi Data Source Failback with a Callback 5-8 How It Works—Failback 5-9 Deploying JDBC Multi Data Sources on Servers and Clusters 5-10 Planned Database Maintenance with a Multi Data Source 5-10 Shutting Down the Data Source 5-11 6 Using Active GridLink Data Sources What is an Active GridLink Data Source 6-1 Fast Connection Failover 6-2 Runtime Connection Load Balancing 6-3 GridLink Affinity 6-4 Session Affinity Policy 6-5 XA Affinity Policy 6-6 SCAN Addresses 6-6 Secure Communication using Oracle Wallet with ONS Listener 6-7 Support for Active Data Guard 6-7 Creating an Active GridLink Data Source 6-7 JDBC Data Source Properties 6-8 v Data Source Names 6-8 Data Source Scope 6-8 JNDI Names 6-8 Select a Driver 6-8 Configure Transaction Options 6-9 Configure Connection Properties 6-9 Enter Connection Properties 6-10 Enter a Complete URL 6-10 Supported AGL Data Source URL Formats 6-11 Test Connections 6-12 ONS Client Configuration 6-12 Enabling FAN Events 6-12 Configure ONS Host and Port 6-12 Secure ONS Client Communication 6-13 Test ONS Client Configuration 6-14 Target the Data Source 6-14 Using Socket Direct Protocol 6-14 Configuring Runtime Load Balancing using SDP 6-14 Configuring Active GridLink Connection Pool Features 6-15 Enabling JDBC Driver-Level Features 6-15 Enabling Connection-based System Properties 6-16 Initializing Database Connections with SQL Code 6-16 Configuring Oracle Parameters 6-16 Configuring an ONS Client Using WLST 6-17 Tuning Active GridLink Data Source Connection Pools 6-17 Monitoring Active GridLink JDBC Resources 6-17 Viewing Run-Time Statistics 6-17 JDBCOracleDataSourceRuntimeMBean 6-17 JDBCOracleDataSourceInstanceRuntimeMBean 6-18 ONSDaemonRuntimeMBean 6-18 Debug Active GridLink Data Sources 6-18 JDBC Debugging Scopes 6-18 UCP JDK Logging 6-19 Enable Debugging Using the Command Line 6-19 Using Active GridLink Data Sources without FAN Notification 6-19 Understanding the ActiveGridlink Attribute 6-20 Best Practices for Active GridLink Data Sources 6-20 Catch and Handle Exceptions 6-20 Connection Creation with Active Gridlink Data Sources 6-21 Comparing Active GridLink
Load more

Recommended publications
  • Perl DBI API Reference
    H Perl DBI API Reference This appendix describes the Perl DBI application programming interface. The API consists of a set of methods and attributes for communicating with database servers and accessing databases from Perl scripts. The appendix also describes MySQL-specific extensions to DBI provided by DBD::mysql, the MySQL database driver. I assume here a minimum version of DBI 1.50, although most of the material applies to earlier versions as well. DBI 1.50 requires at least Perl 5.6.0 (with 5.6.1 preferred). As of DBI 1.611, the minimum Perl version is 5.8.1. I also assume a minimum version of DBD::mysql 4.00. To determine your versions of DBI and DBD::mysql (assuming that they are installed), run this program: #!/usr/bin/perl # dbi-version.pl - display DBI and DBD::mysql versions use DBI; print "DBI::VERSION: $DBI::VERSION\n"; use DBD::mysql; print "DBD::mysql::VERSION: $DBD::mysql::VERSION\n"; If you need to install the DBI software, see Appendix A , “Software Required to Use This Book.” Some DBI methods and attributes are not discussed here, either because they do not apply to MySQL or because they are experimental methods that may change as they are developed or may even be dropped. Some MySQL-specific DBD methods are not discussed because they are obsolete. For more information about new or obsolete methods, see the DBI or DBD::mysql documentation, available at http://dbi.perl.org or by running the following commands: % perldoc DBI % perldoc DBI::FAQ % perldoc DBD::mysql The examples in this appendix are only brief code fragments.
    [Show full text]
  • Database Schema Migration Tools Open Source
    Database Schema Migration Tools Open Source Validating Darian sometimes tranquillize his barony afterwards and cast so stubbornly! Vilhelm rocket his flirt bludge round-arm or best after Worthy smuts and formulise conspiratorially, quinoidal and declaratory. Implied Ernest rinsings: he built his Kathy lexically and amorally. Does this coupon code that is ideal state can replicate for speaking with their database tools and handled it ensures data, a granular control Review the tool for migrating to? If necessary continue browsing the site, will agree specify the rush of cookies on this website. Iteratively make both necessary changes to applications. 1 Database Version Control DBMS Tools. It moves to schema migration database tools source database migration is a few clicks configuration as well as someone to. GDPR: floating video: is from consent? Openmysql rootwelcometcp1270013306migrationtest if err nil fmt. Database health Suite itself and Schema Sync across. The Top 33 Database Migrations Open Source Projects. The community edition of PDI is useful enough they perform our mystery here. Migration Supports schema migration for MySQL SQLite and PostgreSQL Reverse Engineering For existing database structures we to reverse enginering. Most schema migration tools aim to minimize the footprint of schema changes on any existing data in tally database. Contains errors, warnings, and informational messages relating to migration operations. To schema and tools with a tool allows you take years of the tooling uses the type of. But migrating data services ownership, and integrity checks will be able to other objects to use open source tools now part of. Making database schema while capturing any databases, open source endpoint to migrate to get started with constraints between data sources in an altered outside the.
    [Show full text]
  • Dbartisan Reviewers Guide
    DBArtisan® XE Product Review Guide May 2010 Americas Headquarters EMEA Headquarters Asia-Pacific Headquarters 100 California Street, 12th Floor York House L7. 313 La Trobe Street San Francisco, California 94111 18 York Road Melbourne VIC 3000 Maidenhead, Berkshire Australia SL6 1SF, United Kingdom The High Performance DBA CONTENTS Contents ..................................................................................................................................................................... - 1 - Overview ......................................................................................................................................................................... - 2 - Introduction ............................................................................................................................................................... - 2 - Product Description .................................................................................................................................................. - 2 - Contact Information .................................................................................................................................................. - 2 - DBArtisan XE Highlights ................................................................................................................................................ - 3 - New and Interesting Features of DBArtisan XE ..................................................................................................... - 3 - Key Benefits
    [Show full text]
  • DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice
    DATABASE INTEGRATION GUIDE PIPELINE PILOT INTEGRATION COLLECTION 2016 Copyright Notice ©2015 Dassault Systèmes. All rights reserved. 3DEXPERIENCE, the Compass icon and the 3DS logo, CATIA, SOLIDWORKS, ENOVIA, DELMIA, SIMULIA, GEOVIA, EXALEAD, 3D VIA, BIOVIA and NETVIBES are commercial trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the U.S. and/or other countries. All other trademarks are owned by their respective owners. Use of any Dassault Systèmes or its subsidiaries trademarks is subject to their express written approval. Acknowledgments and References To print photographs or files of computational results (figures and/or data) obtained using BIOVIA software, acknowledge the source in an appropriate format. For example: "Computational results obtained using software programs from Dassault Systèmes BIOVIA. The ab initio calculations were performed with the DMol3 program, and graphical displays generated with Pipeline Pilot." BIOVIA may grant permission to republish or reprint its copyrighted materials. Requests should be submitted to BIOVIA Support, either through electronic mail to [email protected], or in writing to: BIOVIA Support 5005 Wateridge Vista Drive, San Diego, CA 92121 USA Contents Chapter 1: Introduction 1 Testing SQL Statements 22 Who Should Read this Guide 1 Error Handling 23 Requirements 1 Chapter 5: Customizing SQL Components 24 Supplied Database Drivers 1 Dynamic SQL Using String Replacement 24 Additional Information 2 Chapter 6: Building Protocols with Multiple Chapter 2: Configuring
    [Show full text]
  • Using Proc SQL and ODBC to Manage Data Outside of SAS® Jeff Magouirk, National Jewish Medical and Research Center, Denver, Colorado
    Using Proc SQL and ODBC to Manage Data outside of SAS® Jeff Magouirk, National Jewish Medical and Research Center, Denver, Colorado ABSTRACT The ability to use Proc SQL and ODBC to manage data outside of SAS is another feature in SAS’s toolbox that programmers use to accomplish many different tasks. The idea of pulling data from sources outside of SAS is behind both of these tools. A key benefit of using ODBC and to a certain amount Proc SQL is the reduction in coding that is written. Another positive aspect of using Proc SQL and ODBC is the ability to manage data across a network. At National Jewish Medical & Research Center ODBC and Proc SQL are used to manage and pull end users data across networks so users can examine their data quickly and efficiently. Since end users can have almost real time access to the collected data it is especially useful for checking the accuracy of the data from patient health studies and clinical trials. Error checks and data handling are done first as the data is collected and put into data tables with SAS and then outputted either with an ODBC connection or Proc SQL. The purpose of this paper is to show users how to set up an ODBC connection, compare the reduction in code when an ODBC is set up and how to use Proc SQL to manage data outside of SAS. INTRODUCTION Open Database Connectivity (ODBC) is an Application Programming Interface (API) that allows a programmer to access data from database management system with a non-native application.
    [Show full text]
  • Opengis Catalog Services Specification
    OGC 02-087r3 Open GIS Consortium Inc. Date: 2002-12-13 Reference number of this OpenGIS® project document: OGC 02-087r3 Version: 1.1.1 Category: OpenGIS® Implementation Specification Editor: Douglas Nebert OpenGIS® Catalog Services Specification Copyright notice This OGC document is copyright-protected by OGC. While the reproduction of drafts in any form for use by participants in the OGC standards development process is permitted without prior permission from OGC, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from OGC. Document type: OpenGIS® Publicly Available Standard Document subtype: Implementation Specification Document stage: Adopted Document language: English OGC 02-087r3 Contents 1 Scope........................................................................................................................1 2 Conformance ..........................................................................................................1 3 Normative references.............................................................................................1 4 Terms and definitions............................................................................................1 5 Conventions ............................................................................................................3 5.1 Symbols (and abbreviated terms).........................................................................3 5.2 UML notation.........................................................................................................4
    [Show full text]
  • Odbc — Load, Write, Or View Data from ODBC Sources
    Title stata.com odbc — Load, write, or view data from ODBC sources Syntax Menu Description Options Remarks and examples Also see Syntax List ODBC sources to which Stata can connect odbc list Retrieve available names from specified data source odbc query "DataSourceName", verbose schema connect options List column names and types associated with specified table odbc describe "TableName", connect options Import data from an ODBC data source odbc load extvarlist if in , table("TableName") j exec("SqlStmt") load options connect options Export data to an ODBC data source odbc insert varlist if in , table("TableName") fdsn("DataSourceName") j connectionstring("ConnectionStr")g insert options connect options Allow SQL statements to be issued directly to ODBC data source odbc exec("SqlStmt") , fdsn("DataSourceName") j connectionstring("ConnectionStr")g connect options Batch job alternative to odbc exec odbc sqlfile("filename") , fdsn("DataSourceName") j connectionstring("ConnectionStr")g loud connect options Specify ODBC driver manager (Unix only) set odbcmgr iodbc j unixodbc , permanently 1 2 odbc — Load, write, or view data from ODBC sources where DataSourceName is the name of the ODBC source (database, spreadsheet, etc.) ConnectionStr is a valid ODBC connection string TableName is the name of a table within the ODBC data source SqlStmt is an SQL SELECT statement filename is pure SQL commands separated by semicolons and where extvarlist contains sqlvarname varname = sqlvarname connect options Description user(UserID) user
    [Show full text]
  • Step by Step Guide: Connecting to Mysql with SAP Crystal Reports 2016 © 2019 SAP AG Or an SAP SAP Allag Or Rightsaffiliate© Company
    SAP Crystal Solutions SAP Crystal Reports and SAP Crystal Server Step by Step guide: Connecting to MySQL With SAP Crystal Reports 2016 © 2019 SAP AG or an SAP SAP AllAG or affiliate rights© company. reserved. SAP an 2019 Because of its open source roots, the MySQL database platform is used in many types of applications. Now provided under the umbrella of Oracle corporation as both paid and free products, MySQL can be the source for many types of SAP Crystal Reports projects. Reporting from a MySQL database requires two general preparation steps: * Download and install the MySQL ODBC database driver. * Create an ODBC Data Source. DOWNLOADING A MySQL DRIVER SAP Crystal Reports won’t recognize a MySQL database “out of the box.” You must first download and install a MySQL driver to connect Crystal Reports to the database. While there are many sources for MySQL drivers found in an Internet search, you’ll typically find current drivers at Oracle’s MySQL.com site. You may find options to download individual drivers one at a time, or an all-encompassing installation program that permits you to choose a combination of drivers from a single installation process. Unless you are planning on using multiple components of MySQL products (perhaps installing your own database server, in addition to a driver for Crystal Reports), you’ll probably only need to download the desired ODBC driver. IMPORTANT: Remember that, despite the strong possibility that you are running a 64-bit version of Microsoft Windows, SAP Crystal Reports is a 32-bit application and will only recognize 32-bit database drivers.
    [Show full text]
  • Essbase SQL Interface Guide, 9.3.1 Copyright © 1998, 2007, Oracle And/Or Its Affiliates
    HYPERION® ESSBASE® – SYSTEM 9 RELEASE 9.3.1 SQL INTERFACE GUIDE Essbase SQL Interface Guide, 9.3.1 Copyright © 1998, 2007, Oracle and/or its affiliates. All rights reserved. Authors: Rosemary Peters The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987).
    [Show full text]
  • Developing Database Applications
    Developing Database Applications JBuilder® 2005 Borland Software Corporation 100 Enterprise Way Scotts Valley, California 95066-3249 www.borland.com Refer to the file deploy.html located in the redist directory of your JBuilder product for a complete list of files that you can distribute in accordance with the JBuilder License Statement and Limited Warranty. Borland Software Corporation may have patents and/or pending patent applications covering subject matter in this document. Please refer to the product CD or the About dialog box for the list of applicable patents. The furnishing of this document does not give you any license to these patents. COPYRIGHT © 1997–2004 Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners. For third-party conditions and disclaimers, see the Release Notes on your JBuilder product CD. Printed in the U.S.A. JB2005database 10E13R0804 0405060708-987654321 PDF Contents Chapter 1 Chapter 4 Introduction 1 Connecting to a database 27 Chapter summaries . 2 Connecting to databases . 28 Database tutorials. 3 Adding a Database component to your Database samples . 3 application . 28 Related documentation . 4 Setting Database connection properties . 29 Documentation conventions . 6 Setting up JDataStore . 31 Developer support and resources. 7 Setting up InterBase and InterClient. 31 Contacting Borland Developer Support . 7 Using InterBase and InterClient with JBuilder . 32 Online resources. 7 Tips on using sample InterBase tables . 32 World Wide Web . 8 Adding a JDBC driver to JBuilder .
    [Show full text]
  • JDBC Driver for SQL/MP
    Contents HP JDBC/MP Driver for NonStop SQL/MP Programmer's Reference for H10 Abstract This document describes how to use the JDBC/MP Driver for NonStop SQL/MP on HP Integrity NonStop™ NS-series servers. JDBC/MP provides NonStop Server for Java applications with JDBC access to HP NonStop SQL/MP. JDBC/MP driver conforms where applicable to the standard JDBC 3.0 API from Sun Microsystems, Inc. Product Version HP JDBC/MP Driver for NonStop SQL/MP H10 Supported Hardware All HP Integrity NonStop NS-series servers Supported Release Version Updates (RVUs) This publication supports H06.04 and all subsequent H-series RVUs until otherwise indicated by its replacement publication. Part Number Published 529851-001 January 2006 Document History Part Number Product Version Published JDBC Driver for SQL/MP September 526349-002 (JDBC/MP) V21 2003 JDBC Driver for SQL/MP 527401-001 October 2003 (JDBC/MP) V30 JDBC Driver for SQL/MP 527401-002 July 2004 (JDBC/MP) V30 JDBC Driver for SQL/MP 527401-003 May 2005 (JDBC/MP) V30 and H10 JDBC/MP Driver for NonStop 529851-001 January 2006 SQL/MP H10 Legal Notices © Copyright 2006 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, 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.
    [Show full text]
  • Teradata SQL Assistant/Web Edition User Guide
    Teradata SQL Assistant/Web Edition User Guide Release 12.00.00 B035-2505-067A July 2007 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, DB2, MVS, RACF, Tivoli, and VM are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademarks of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.
    [Show full text]