DOCSLIB.ORG

Data Warehouse Service

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Data Warehouse Service Data Warehouse Service SQL Error Code Reference Issue 03 Date 2018-08-02 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd. Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: http://www.huawei.com Email: [email protected] Issue 03 (2018-08-02) Huawei Proprietary and Confidential i Copyright © Huawei Technologies Co., Ltd. Data Warehouse Service SQL Error Code Reference Contents Contents 1 Error Code Reference....................................................................................................................1 1.1 Description of SQL-based Error Codes..........................................................................................................................1 1.2 GAUSS-00001 -- GAUSS-00100.................................................................................................................................12 1.2.1 GAUSS-00001 -- GAUSS-00010..............................................................................................................................12 1.2.2 GAUSS-00011 -- GAUSS-00020..............................................................................................................................14 1.2.3 GAUSS-00021 -- GAUSS-00030..............................................................................................................................15 1.2.4 GAUSS-00031 -- GAUSS-00040..............................................................................................................................17 1.2.5 GAUSS-00041 -- GAUSS-00050..............................................................................................................................18 1.2.6 GAUSS-00051 -- GAUSS-00060..............................................................................................................................20 1.2.7 GAUSS-00061 -- GAUSS-00070..............................................................................................................................21 1.2.8 GAUSS-00071 -- GAUSS-00080..............................................................................................................................23 1.2.9 GAUSS-00081 -- GAUSS-00090..............................................................................................................................24 1.2.10 GAUSS-00091 -- GAUSS-00100............................................................................................................................26 1.3 GAUSS-00101 -- GAUSS-00200.................................................................................................................................27 1.3.1 GAUSS-00101 -- GAUSS-00110..............................................................................................................................27 1.3.2 GAUSS-00111 -- GAUSS-00120..............................................................................................................................29 1.3.3 GAUSS-00121 -- GAUSS-00130..............................................................................................................................30 1.3.4 GAUSS-00131 -- GAUSS-00140..............................................................................................................................32 1.3.5 GAUSS-00141 -- GAUSS-00150..............................................................................................................................33 1.3.6 GAUSS-00151 -- GAUSS-00160..............................................................................................................................35 1.3.7 GAUSS-00161 -- GAUSS-00170..............................................................................................................................36 1.3.8 GAUSS-00171 -- GAUSS-00180..............................................................................................................................38 1.3.9 GAUSS-00181 -- GAUSS-00190..............................................................................................................................39 1.3.10 GAUSS-00191 -- GAUSS-00200............................................................................................................................40 1.4 GAUSS-00201 -- GAUSS-00300.................................................................................................................................42 1.4.1 GAUSS-00201 -- GAUSS-00210..............................................................................................................................42 1.4.2 GAUSS-00211 -- GAUSS-00220..............................................................................................................................44 1.4.3 GAUSS-00221 -- GAUSS-00230..............................................................................................................................45 1.4.4 GAUSS-00231 -- GAUSS-00240..............................................................................................................................47 1.4.5 GAUSS-00241 -- GAUSS-00250..............................................................................................................................48 1.4.6 GAUSS-00251 -- GAUSS-00260..............................................................................................................................50 1.4.7 GAUSS-00261 -- GAUSS-00270..............................................................................................................................51 1.4.8 GAUSS-00271 -- GAUSS-00280..............................................................................................................................53 Issue 03 (2018-08-02) Huawei Proprietary and Confidential ii Copyright © Huawei Technologies Co., Ltd. Data Warehouse Service SQL Error Code Reference Contents 1.4.9 GAUSS-00281 -- GAUSS-00290..............................................................................................................................54 1.4.10 GAUSS-00291 -- GAUSS-00300............................................................................................................................56 1.5 GAUSS-00301 -- GAUSS-00400.................................................................................................................................58 1.5.1 GAUSS-00301 -- GAUSS-00310..............................................................................................................................58 1.5.2 GAUSS-00311 -- GAUSS-00320..............................................................................................................................59 1.5.3 GAUSS-00321 -- GAUSS-00330..............................................................................................................................61 1.5.4 GAUSS-00331 -- GAUSS-00340..............................................................................................................................63 1.5.5 GAUSS-00341 -- GAUSS-00350..............................................................................................................................65 1.5.6 GAUSS-00351 -- GAUSS-00360..............................................................................................................................66 1.5.7 GAUSS-00361 -- GAUSS-00370..............................................................................................................................68 1.5.8 GAUSS-00371 -- GAUSS-00380..............................................................................................................................70 1.5.9 GAUSS-00381 -- GAUSS-00390..............................................................................................................................72 1.5.10 GAUSS-00391 -- GAUSS-00400............................................................................................................................73 1.6 GAUSS-00401 -- GAUSS-00500.................................................................................................................................75 1.6.1 GAUSS-00401 -- GAUSS-00410..............................................................................................................................75 1.6.2 GAUSS-00411 -- GAUSS-00420..............................................................................................................................77
Load more

Recommended publications
  • Querying Graph Databases: What Do Graph Patterns Mean?
    Querying Graph Databases: What Do Graph Patterns Mean? Stephan Mennicke1( ), Jan-Christoph Kalo2, and Wolf-Tilo Balke2 1 Institut für Programmierung und Reaktive Systeme, TU Braunschweig, Germany [email protected] 2 Institut für Informationssysteme, TU Braunschweig, Germany {kalo,balke}@ifis.cs.tu-bs.de Abstract. Querying graph databases often amounts to some form of graph pattern matching. Finding (sub-)graphs isomorphic to a given graph pattern is common to many graph query languages, even though graph isomorphism often is too strict, since it requires a one-to-one cor- respondence between the nodes of the pattern and that of a match. We investigate the influence of weaker graph pattern matching relations on the respective queries they express. Thereby, these relations abstract from the concrete graph topology to different degrees. An extension of relation sequences, called failures which we borrow from studies on con- current processes, naturally expresses simple presence conditions for rela- tions and properties. This is very useful in application scenarios dealing with databases with a notion of data completeness. Furthermore, fail- ures open up the query modeling for more intricate matching relations directly incorporating concrete data values. Keywords: Graph databases · Query modeling · Pattern matching 1 Introduction Over the last years, graph databases have aroused a vivid interest in the database community. This is partly sparked by intelligent and quite robust developments in information extraction, partly due to successful standardizations for knowl- edge representation in the Semantic Web. Indeed, it is enticing to open up the abundance of unstructured information on the Web through transformation into a structured form that is usable by advanced applications.
    [Show full text]
  • Support Aggregate Analytic Window Function Over Large Data by Spilling
    Support Aggregate Analytic Window Function over Large Data by Spilling Xing Shi and Chao Wang Guangdong University of Technology, Guangzhou, Guangdong 510006, China North China University of Technology, Beijing 100144, China Abstract. ​Analytic function, also called window function, is to query the aggregation of data over a sliding window. For example, a simple query over the online stock platform is to return the average price of a stock of the last three days. These functions are commonly used features in SQL databases. They are supported in most of the commercial databases. With the increasing usage of cloud data infra and machine learning technology, the frequency of queries with analytic window functions rises. Some analytic functions only require const space in memory to store the state, such as SUM, AVG, while others require linear space, such as MIN, MAX. When the window is extremely large, the memory space to store the state may be too large. In this case, we need to spill the state to disk, which is a heavy operation. In this paper, we proposed an algorithm to manipulate the state data in the disk to reduce the disk I/O to make spill available and efficiency. We analyze the complexity of the algorithm with different data distribution. 1. Introducion In this paper, we develop novel spill techniques for analytic window function in SQL databases. And discuss different various types of aggregate queries, e.g., COUNT, AVG, SUM, MAX, MIN, etc., over a relational table. Aggregate ​analytic function, also called aggregate window function, is to query the aggregation of data over a sliding window.
    [Show full text]
  • A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon
    A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon To cite this version: Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon. A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine. DEXA’2014 (Database and Expert System Applications), Sep 2014, Munich, Germany. pp.433-440. hal-00993260 HAL Id: hal-00993260 https://hal.archives-ouvertes.fr/hal-00993260 Submitted on 28 Oct 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Fr´ed´ericDumonceaux, Guillaume Raschia, and Marc Gelgon LINA (UMR CNRS 6241), Universit´ede Nantes, France [email protected] Abstract. Partitions are a very common and useful way of organiz- ing data, in data engineering and data mining. However, partitions cur- rently lack efficient and generic data management functionalities. This paper proposes advances in the understanding of this problem, as well as elements for solving it. We formulate the task as efficient process- ing, evaluating and optimizing queries over set partitions, in the setting of relational databases.
    [Show full text]
  • Alias for Case Statement in Oracle
    Alias For Case Statement In Oracle two-facedly.FonsieVitric Connie shrieved Willdon reconnects his Carlenegrooved jimply discloses her and pyrophosphates mutationally, knavishly, butshe reticularly, diocesan flounces hobnail Kermieher apache and never reddest. write disadvantage person-to-person. so Column alias can be used in GROUP a clause alone is different to promote other database management systems such as Oracle and SQL Server See Practice 6-1. Kotlin performs for example, in for alias case statement. If more want just write greater Less evident or butter you fuck do like this equity Case When ColumnsName 0 then 'value1' When ColumnsName0 Or ColumnsName. Normally we mean column names using the create statement and alias them in shape if. The logic to behold the right records is in out CASE statement. As faceted search string manipulation features and case statement in for alias oracle alias? In the following examples and managing the correct behaviour of putting each for case of a prefix oracle autonomous db driver to select command that updates. The four lines with the concatenated case statement then the alias's will work. The following expression jOOQ. Renaming SQL columns based on valve position Modern SQL. SQLite CASE very Simple CASE & Search CASE. Alias on age line ticket do I pretend it once the same path in the. Sql and case in. Gke app to extend sql does that alias for case statement in oracle apex jobs in cases, its various points throughout your. Oracle Creating Joins with the USING Clause w3resource. Multi technology and oracle alias will look further what we get column alias for case statement in oracle.
    [Show full text]
  • Look out the Window Functions and Free Your SQL
    Concepts Syntax Other Look Out The Window Functions and free your SQL Gianni Ciolli 2ndQuadrant Italia PostgreSQL Conference Europe 2011 October 18-21, Amsterdam Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Outline 1 Concepts Aggregates Different aggregations Partitions Window frames 2 Syntax Frames from 9.0 Frames in 8.4 3 Other A larger example Question time Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Aggregates Aggregates 1 Example of an aggregate Problem 1 How many rows there are in table a? Solution SELECT count(*) FROM a; • Here count is an aggregate function (SQL keyword AGGREGATE). Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Aggregates Aggregates 2 Functions and Aggregates • FUNCTIONs: • input: one row • output: either one row or a set of rows: • AGGREGATEs: • input: a set of rows • output: one row Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Different aggregations Different aggregations 1 Without window functions, and with them GROUP BY col1, . , coln window functions any supported only PostgreSQL PostgreSQL version version 8.4+ compute aggregates compute aggregates via by creating groups partitions and window frames output is one row output is one row for each group for each input row Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Different aggregations Different aggregations 2 Without window functions, and with them GROUP BY col1, . , coln window functions only one way of aggregating different rows in the same for each group
    [Show full text]
  • Lecture 3: Advanced SQL
    Advanced SQL Lecture 3: Advanced SQL 1 / 64 Advanced SQL Relational Language Relational Language • User only needs to specify the answer that they want, not how to compute it. • The DBMS is responsible for efficient evaluation of the query. I Query optimizer: re-orders operations and generates query plan 2 / 64 Advanced SQL Relational Language SQL History • Originally “SEQUEL" from IBM’s System R prototype. I Structured English Query Language I Adopted by Oracle in the 1970s. I IBM releases DB2 in 1983. I ANSI Standard in 1986. ISO in 1987 I Structured Query Language 3 / 64 Advanced SQL Relational Language SQL History • Current standard is SQL:2016 I SQL:2016 −! JSON, Polymorphic tables I SQL:2011 −! Temporal DBs, Pipelined DML I SQL:2008 −! TRUNCATE, Fancy sorting I SQL:2003 −! XML, windows, sequences, auto-gen IDs. I SQL:1999 −! Regex, triggers, OO • Most DBMSs at least support SQL-92 • Comparison of different SQL implementations 4 / 64 Advanced SQL Relational Language Relational Language • Data Manipulation Language (DML) • Data Definition Language (DDL) • Data Control Language (DCL) • Also includes: I View definition I Integrity & Referential Constraints I Transactions • Important: SQL is based on bag semantics (duplicates) not set semantics (no duplicates). 5 / 64 Advanced SQL Relational Language Today’s Agenda • Aggregations + Group By • String / Date / Time Operations • Output Control + Redirection • Nested Queries • Join • Common Table Expressions • Window Functions 6 / 64 Advanced SQL Relational Language Example Database SQL Fiddle: Link sid name login age gpa sid cid grade 1 Maria maria@cs 19 3.8 1 1 B students 2 Rahul rahul@cs 22 3.5 enrolled 1 2 A 3 Shiyi shiyi@cs 26 3.7 2 3 B 4 Peter peter@ece 35 3.8 4 2 C cid name 1 Computer Architecture courses 2 Machine Learning 3 Database Systems 4 Programming Languages 7 / 64 Advanced SQL Aggregates Aggregates • Functions that return a single value from a bag of tuples: I AVG(col)−! Return the average col value.
    [Show full text]
  • Chapter 11 Querying
    Oracle TIGHT / Oracle Database 11g & MySQL 5.6 Developer Handbook / Michael McLaughlin / 885-8 Blind folio: 273 CHAPTER 11 Querying 273 11-ch11.indd 273 9/5/11 4:23:56 PM Oracle TIGHT / Oracle Database 11g & MySQL 5.6 Developer Handbook / Michael McLaughlin / 885-8 Oracle TIGHT / Oracle Database 11g & MySQL 5.6 Developer Handbook / Michael McLaughlin / 885-8 274 Oracle Database 11g & MySQL 5.6 Developer Handbook Chapter 11: Querying 275 he SQL SELECT statement lets you query data from the database. In many of the previous chapters, you’ve seen examples of queries. Queries support several different types of subqueries, such as nested queries that run independently or T correlated nested queries. Correlated nested queries run with a dependency on the outer or containing query. This chapter shows you how to work with column returns from queries and how to join tables into multiple table result sets. Result sets are like tables because they’re two-dimensional data sets. The data sets can be a subset of one table or a set of values from two or more tables. The SELECT list determines what’s returned from a query into a result set. The SELECT list is the set of columns and expressions returned by a SELECT statement. The SELECT list defines the record structure of the result set, which is the result set’s first dimension. The number of rows returned from the query defines the elements of a record structure list, which is the result set’s second dimension. You filter single tables to get subsets of a table, and you join tables into a larger result set to get a superset of any one table by returning a result set of the join between two or more tables.
    [Show full text]
  • Sql Server to Aurora Postgresql Migration Playbook
    Microsoft SQL Server To Amazon Aurora with Post- greSQL Compatibility Migration Playbook 1.0 Preliminary September 2018 © 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offer- ings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without war- ranty of any kind, whether express or implied. This document does not create any warranties, rep- resentations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agree- ments, and this document is not part of, nor does it modify, any agreement between AWS and its cus- tomers. - 2 - Table of Contents Introduction 9 Tables of Feature Compatibility 12 AWS Schema and Data Migration Tools 20 AWS Schema Conversion Tool (SCT) 21 Overview 21 Migrating a Database 21 SCT Action Code Index 31 Creating Tables 32 Data Types 32 Collations 33 PIVOT and UNPIVOT 33 TOP and FETCH 34 Cursors 34 Flow Control 35 Transaction Isolation 35 Stored Procedures 36 Triggers 36 MERGE 37 Query hints and plan guides 37 Full Text Search 38 Indexes 38 Partitioning 39 Backup 40 SQL Server Mail 40 SQL Server Agent 41 Service Broker 41 XML 42 Constraints
    [Show full text]
  • Firebird 3 Windowing Functions
    Firebird 3 Windowing Functions Firebird 3 Windowing Functions Author: Philippe Makowski IBPhoenix Email: pmakowski@ibphoenix Licence: Public Documentation License Date: 2011-11-22 Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions What are Windowing Functions? • Similar to classical aggregates but does more! • Provides access to set of rows from the current row • Introduced SQL:2003 and more detail in SQL:2008 • Supported by PostgreSQL, Oracle, SQL Server, Sybase and DB2 • Used in OLAP mainly but also useful in OLTP • Analysis and reporting by rankings, cumulative aggregates Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions Windowed Table Functions • Windowed table function • operates on a window of a table • returns a value for every row in that window • the value is calculated by taking into consideration values from the set of rows in that window • 8 new windowed table functions • In addition, old aggregate functions can also be used as windowed table functions • Allows calculation of moving and cumulative aggregate values. Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions A Window • Represents set of rows that is used to compute additionnal attributes • Based on three main concepts • partition • specified by PARTITION BY clause in OVER() • Allows to subdivide the table, much like GROUP BY clause • Without a PARTITION BY clause, the whole table is in a single partition • order • defines an order with a partition • may contain multiple order items • Each item includes
    [Show full text]
  • The JOIN Clause
    2.1 The JOIN Clause The Join Clause A JOIN clause allows you to access data from two or more tables in a query. A join links to tables on a common key between the two tables. Usually the primary key on one table is compared to the foreign key on another table using the equals ( = ) sign. This is an equijoin or an inner-join. However, other comparison operators are also valid. If column names from each table in the join have the same name, they must be qualified with the table name or a table alias. Below is a basic example of a SQL statement with an inner join clause using explicit syntax. 1 USE world; 2 SELECT city.name AS "City Name", 3 country.name AS "Country Name" 4 FROM country 6 JOIN city 5 ON city.CountryCode = country. Code; Learning MySQL By Example 1 You could write SQL statements more succinctly with an inner join clause using table aliases. Instead of writing out the whole table name to qualify a column, you can use a table alias. 1 USE world; 2 SELECT ci.name AS "City Name", 3 co.name AS "Country Name" 4 FROM city ci 5 JOIN country co 6 ON ci.CountryCode = co.Code; The results of the join query would yield the same results as shown below whether or not table names are completely written out or are represented with table aliases. The table aliases of co for country and ci for city are defined in the FROM clause and referenced in the SELECT and ON clause: Results: Learning MySQL By Example 2 Let us break the statement line by line: USE world; The USE clause sets the database that we will be querying.
    [Show full text]
  • Using Sqlrender
    Using SqlRender Martijn J. Schuemie 2021-09-15 Contents 1 Introduction 1 2 SQL parameterization 1 2.1 Substituting parameter values . .1 2.2 Default parameter values . .2 2.3 If-then-else . .2 3 Translation to other SQL dialects 3 3.1 Functions and structures supported by translate . .4 3.2 String concatenation . .5 3.3 Table aliases and the AS keyword . .5 3.4 Temp tables . .5 3.5 Implicit casts . .6 3.6 Case sensitivity in string comparisons . .7 3.7 Schemas and databases . .7 3.8 Optimization for massively parallel processing . .8 4 Debugging parameterized SQL 8 5 Developing R packages that contain parameterized SQL 9 1 Introduction This vignette describes how one could use the SqlRender R package. 2 SQL parameterization One of the main functions of the package is to support parameterization of SQL. Often, small variations of SQL need to be generated based on some parameters. SqlRender offers a simple markup syntax inside the SQL code to allow parameterization. Rendering the SQL based on parameter values is done using the render() function. 2.1 Substituting parameter values The @ character can be used to indicate parameter names that need to be exchange for actual parameter values when rendering. In the following example, a variable called a is mentioned in the SQL. In the call to the render function the value of this parameter is defined: sql <- "SELECT * FROM table WHERE id = @a;" render(sql,a= 123) 1 ## [1] "SELECT * FROM table WHERE id = 123;" Note that, unlike the parameterization offered by most database management systems, it is
    [Show full text]
  • Going OVER and Above with SQL
    Going OVER and Above with SQL Tamar E. Granor Tomorrow's Solutions, LLC Voice: 215-635-1958 Email: [email protected] The SQL 2003 standard introduced the OVER keyword that lets you apply a function to a set of records. Introduced in SQL Server 2005, this capability was extended in SQL Server 2012. The functions allow you to rank records, aggregate them in a variety of ways, put data from multiple records into a single result record, and compute and use percentiles. The set of problems they solve range from removing exact duplicates to computing running totals and moving averages to comparing data from different periods to removing outliers. In this session, we'll look at the OVER operator and the many functions you can use with it. We'll look at a variety of problems that can be solved using OVER. Going OVER and Above with SQL Over the last couple of years, I’ve been exploring aspects of SQL Server’s T-SQL implementation that aren’t included in VFP’s SQL sub-language. I first noticed the OVER keyword as an easy way to solve a problem that’s fairly complex with VFP’s SQL, getting the top N records in each of a set of groups with a single query. At the time, I noticed that OVER had other uses, but I didn’t stop to explore them. When I finally returned to see what else OVER could do, I was blown away. In recent versions of SQL Server (2012 and later), OVER provides ways to compute running totals and moving averages, to put data from several records of the same table into a single result record, to divide records into percentile groups and more.
    [Show full text]