Informatica Data Archive (Version 6.

1)

File Archive Service Message Reference

Informatica Data Archive File Archive Service Message Reference

Version 6.1
September 2012

Copyright (c) 1996-2012 Informatica. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form,
by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international
Patents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in
DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in
writing.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,
PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On
Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica
Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company
and product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights
reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights
[Link] © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta
Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. All
rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved.
Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright ©
Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © Information
Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights
reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All rights reserved. Copyright © Jaspersoft
Corporation. All rights reserved. Copyright © is International Business Machines Corporation. All rights reserved. Copyright © yWorks GmbH. All rights reserved. Copyright ©
Lucent Technologies 1997. All rights reserved. Copyright (c) 1986 by University of Toronto. All rights reserved. Copyright © 1998-2003 Daniel Veillard. All rights reserved.
Copyright © 2001-2004 Unicode, Inc. Copyright 1994-1999 IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved. Copyright ©
PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved. Copyright © Red
Hat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC Corporation. All rights reserved.

This product includes software developed by the Apache Software Foundation ([Link] and other software which is licensed under the Apache License,
Version 2.0 (the "License"). You may obtain a copy of the License at [Link] Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under the License.

This product includes software which was developed by Mozilla ([Link] software copyright The JBoss Group, LLC, all rights reserved; software copyright ©
1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://
[Link]/licenses/[Link]. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not
limited to the implied warranties of merchantability and fitness for a particular purpose.

The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine,
and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of
this software is subject to terms available at [Link] and [Link]

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <daniel@[Link]>. All Rights Reserved. Permissions and limitations regarding this
software are subject to terms available at [Link] Permission to use, copy, modify, and distribute this software for any purpose with or without
fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available
at [Link] [Link].

The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at [Link]

This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this
software are subject to terms available at [Link]
This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://
[Link]/software/ kawa/[Link].

This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless
Deutschland. Permissions and limitations regarding this software are subject to terms available at [Link]

This product includes software developed by Boost ([Link] or under the Boost software license. Permissions and limitations regarding this software are subject
to terms available at http:/ /[Link]/LICENSE_1_0.txt.

This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http://
[Link]/[Link].

This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms
available at http:// [Link]/org/documents/[Link].

This product includes software licensed under the terms at [Link] [Link] [Link]
doc/ [Link], [Link] [Link] [Link] [Link]
[Link], [Link] , [Link] [Link] [Link]
[Link] [Link] [Link] license-
agreement; [Link] [Link] [Link] [Link] http://
[Link]/jsch/[Link]. [Link] . [Link] [Link]
[Link]; [Link] [Link] http://
[Link]/[Link]; [Link] [Link] [Link] [Link]
software/tcltk/[Link], [Link] [Link] [Link] [Link]
iODBC/License; [Link] [Link] [Link] [Link]
[Link]/about/[Link]; [Link] [Link] [Link] [Link]
[Link] and [Link]

This product includes software licensed under the Academic Free License ([Link] the Common Development and Distribution
License ([Link] the Common Public License ([Link] the Sun Binary Code License
Agreement Supplemental License Terms, the BSD License (http:// [Link]/licenses/[Link]) the MIT License ([Link]
[Link]) and the Artistic License ([Link]

This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software
are subject to terms available at [Link] This product includes software developed by the Indiana University Extreme! Lab. For further
information please visit [Link]

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;
6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;
7676516; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending.

DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied
warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The
information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is
subject to change at any time without notice.

NOTICES

This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software
Corporation (“DataDirect”) which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF
THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH
OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: IDA-FMR-61000-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Chapter 1: Data Definition Language Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Data Definition Language Errors Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
08 Connection Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
0B Invalid Transaction Initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
0H Invalid SQLSTATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
21 Cardinality Violation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
22 Data Exception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
23 Integrity Constraint Violation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
25 Invalid Transaction State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
28 Invalid Authorization Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2B Dependent Privilege. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3F Invalid Schema Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
40 Transaction Rollback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
42 Syntax Error or Access Rule Violation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
50 Feature Not Implemented. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
54 Privilege Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
70 Schema Exception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
80 Domain Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
90 Table and View Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
J0 Invalid Integrity Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
K0 Column Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
M0 INSERT Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
N0 Expression Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
O0 Invalid Database Reference and Limit Exceeded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
P0 Subsystem Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Q0 Database Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
S0 Execution Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
T0 Execution Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table of Contents i
 Chapter 2: File Archive Repository Service Exit Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
File Archive Repository Service Exit Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3: Load Balancer and Administration Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Load Balancer and File Archive Administration Utility errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Other ssaserver Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
File Archive Repository Administration Exit Code Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Load Balancer and File Archive Repository Administration Errors. . . . . . . . . . . . . . . . . . . . . . . . . . 39
Rule Engine Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 4: ssamdtool Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Ssamdtool Exit Code Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Metadata Service Errors (Ssaserver, Ssamdtool, and the MDAdmin GUI) . . . . . . . . . . . . . . . . . . . . . 50
Rule Engine Errors (Column Rules, Filter Rules, and File Scopes). . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 5: File Archive SQL Tool Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

File Archive SQL Tool Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Appendix A: File Archive Loader Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

File Archive Loader Messages Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Messages and Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Load Operation Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
File Parsing Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

ii Table of Contents
Preface
The File Archive Service Message Reference provides information about the messages generated by the File
Archive Service. The Message Reference is written for system administrators who are responsible for
administering, monitoring, and troubleshooting optimized file archive tasks in Data Archive.

This guide assumes that you have knowledge of relational database concepts, and the database, flat file, or
mainframe systems in your environment. It also assumes that you are familiar with the operating systems and
network protocols in your environment.

Informatica Resources

Informatica Customer Portal

As an Informatica customer, you can access the Informatica Customer Portal site at
[Link] The site contains product information, user group information, newsletters,
access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library,
the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product
Documentation, and access to the Informatica user community.

Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have
questions, comments, or ideas about this documentation, contact the Informatica Documentation team through
email at infa_documentation@[Link]. We will use your feedback to improve our documentation. Let us
know if we can contact you regarding your comments.

The Documentation team updates documentation as needed. To get the latest documentation for your product,
navigate to Product Documentation from [Link]

Informatica Web Site

You can access the Informatica corporate web site at [Link] The site contains information
about Informatica, its background, upcoming events, and sales offices. You will also find product and partner
information. The services area of the site includes important information about technical support, training and
education, and implementation services.

iii
 Informatica How-To Library
As an Informatica customer, you can access the Informatica How-To Library at [Link]
The How-To Library is a collection of resources to help you learn more about Informatica products and features. It
includes articles and interactive demonstrations that provide solutions to common problems, compare features and
behaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at [Link]
Use the Knowledge Base to search for documented solutions to known technical issues about Informatica
products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If
you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base
team through email at KB_Feedback@[Link].

Informatica Multimedia Knowledge Base

As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at
[Link] The Multimedia Knowledge Base is a collection of instructional multimedia files
that help you learn about common concepts and guide you through performing specific tasks. If you have
questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base
team through email at KB_Feedback@[Link].

Informatica Global Customer Support

You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires
a user name and password. You can request a user name and password at [Link]

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Toll Free Toll Free Toll Free

Brazil: 0800 891 0202 France: 0805 804632 Australia: 1 800 151 830
Mexico: 001 888 209 8853 Germany: 0800 5891281 New Zealand: 09 9 128 901
North America: +1 877 463 2435 Italy: 800 915 985
Netherlands: 0800 2300001
Portugal: 800 208 360 Standard Rate
Spain: 900 813 166 India: +91 80 4112 5738
Switzerland: 0800 463 200
United Kingdom: 0800 023 4632

Standard Rate
Belgium: +31 30 6022 797
France: +33 1 4138 9226
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511445

iv Preface
CHAPTER 1

Data Definition Language Errors

This chapter includes the following topics:

¨ Data Definition Language Errors Overview, 2

¨ 08 Connection Error, 2

¨ 0B Invalid Transaction Initiation, 3

¨ 0H Invalid SQLSTATE, 3

¨ 21 Cardinality Violation, 5

¨ 22 Data Exception, 6

¨ 23 Integrity Constraint Violation, 7

¨ 25 Invalid Transaction State, 7

¨ 28 Invalid Authorization Specification, 8

¨ 2B Dependent Privilege, 8

¨ 3F Invalid Schema Name, 8

¨ 40 Transaction Rollback, 8

¨ 42 Syntax Error or Access Rule Violation, 9

¨ 50 Feature Not Implemented, 11

¨ 54 Privilege Error, 13

¨ 70 Schema Exception, 14

¨ 80 Domain Error, 14

¨ 90 Table and View Error, 15

¨ J0 Invalid Integrity Constraints, 18

¨ K0 Column Error, 19

¨ M0 INSERT Failure, 22

¨ N0 Expression Error, 22

¨ O0 Invalid Database Reference and Limit Exceeded, 22

¨ P0 Subsystem Failure, 23

¨ Q0 Database Error, 23

1
 ¨ S0 Execution Failure, 24

¨ T0 Execution Failure, 24

Data Definition Language Errors Overview

This chapter lists the diagnostic messages that may be returned when executing SQL commands. Generally, there
are three types of diagnostic messages:

¨ Success - the SQL statement has executed successfully and without warnings

Warning: s - conditions that are not serious enough to prevent an SQL statement from executing successfully,
but which require user notification, as the statement might not produce the expected results

¨ Errors - conditions that prevent an SQL statement from executing successfully

The File Archive Service uses SQL92-compliant SQLSTATE status codes to categorize the diagnostic messages.
Each SQLSTATE code consists of a 2-character class, followed by a 3-character subclass. The class specifies
general information about the error type; the subclass specifies more specific information. For example,
SQLSTATE code 54503 indicates the class 54 (Privilege Errors) and the subclass 503 (“Cannot grant privileges -
non-existent object”). Each of the five characters in an SQLSTATE value is a digit (0...9) or an uppercase letter
(A...Z). Class codes that begin with a digit in the range 0...4, or a letter in the range A...H, are reserved for SQL92
predefined conditions. All other class codes are reserved for implementation-defined conditions.

Most of the diagnostic messages in this document are accompanied by a description of the error and warning, and
some recommended course of action.

08 Connection Error
08004 Server refused connection - Maximum number of sessions reached
Explanation: The maximum number of concurrent database sessions have been reached and another
connection is attempted. The maximum number of sessions is set through the MaxUsers
parameter in the [Link] file.

User Response: If required, the MaxUsers value can be increased up to a maximum of 127.

2 Chapter 1: Data Definition Language Errors

0B Invalid Transaction Initiation
0001B Exclusive use not possible while other transactions are active
Explanation: A user issues the SET TRANSACTION...ISOLATION LEVEL EXCLUSIVE command while
there are other concurrent user connections to the same database instance. In order to “lock”
the database using the SET TRANSACTION...ISOLATION LEVEL EXCLUSIVE command,
the user executing the command must have the only connection to the database.

Two or more users are connected to a database instance, and one of the users attempts to
execute an ALTER TABLE...ADD CONSTRAINT command. For concurrency control reasons,
you cannot add constraints to a table while other user sessions are active.

A File Archive Loader operation is attempted on a database while one or more users are
connected to the database instance. The File Archive Loader requires exclusive access to
the database in order to function.

0002B Transaction statement failure - duplicate clauses

Explanation: A SET TRANSACTION statement includes more than one ISOLATION LEVEL clause or
access mode (READ ONLY, READ WRITE). The access mode and ISOLATION LEVEL
clause can appear at most once in a SET TRANSACTION statement.

0003B Transaction statement failure - invalid diagnostic size

Explanation: The DIAGNOSTIC SIZE clause in a SET TRANSACTION or START TRANSACTION
statement specifies a value that is zero or less, or greater than 32. The value specified by the
DIAGNOSTIC SIZE clause must be between 1 and 32 inclusive.

0H Invalid SQLSTATE
0H000 Invalid SQLSTATE. can't compare or combine host variables

Explanation: Host variables or parameter markers can neither be combined in arithmetic expressions nor
appear on both sides of a comparison operator. Note that embedded SQL is a deprecated
feature.

0H000 Invalid SQLSTATE. can't use host variables in NULL or LIKE predicates

Explanation: Host variables or parameter markers cannot be used in NULL or LIKE predicates in a
Boolean value expression (search condition). Note that embedded SQL is a deprecated
feature.

0H000 Invalid SQLSTATE. Cannot load into a table that has constraints other than not null

Explanation: The File Archive Loader cannot load data into a table that has PRIMARY KEY or UNIQUE
constraints defined on the table or its columns.

User Response: Execute one or more ALTER TABLE...DROP CONSTRAINT statements to remove the key
constraints before attempting the data load again. When the load is complete, the constraints
can be redefined using ALTER TABLE...ADD CONSTRAINT statements.

0B Invalid Transaction Initiation 3

 0H000 Invalid SQLSTATE. CASCADE not yet supported

Explanation: The DROP command cannot include the CASCADE keyword in the current version of the File
Archive Service.

User Response: The DROP object command requires that all dependent objects be explicitly dropped prior to
attempting to drop the object.

0H000 Invalid SQLSTATE. constant op constant not folded

Explanation: A derived view column evaluates to a numeric constant, and this view column is selected as
part of an arithmetic expression involving another numeric constant. For example:

CREATE VIEW view1 (col1) AS SELECT 1 FROM table1;

SELECT col1 * 10 FROM view1;

The error is also generated if a host variable is arithmetically combined with a numeric
constant. Note that embedded SQL is a deprecated feature.

0H000 Invalid SQLSTATE. escape symbol should be one character only

Explanation: This message is returned when the LIKE predicate is used in a Boolean value expression
(search condition), and the ESCAPE clause specifies more than one escape character. The
ESCAPE clause, if included, must specify a single character.

0H000 Invalid SQLSTATE. Execution failed - Not enough input parameters

Explanation: This message is returned when a value expression or search condition contains a “?” (without
the quotation marks).

If this character is intended as a parameter marker, it should be noted that the File Archive
Service does not support embedded SQL.

This message is also generated when an INSERT statement contains a “?” (without the
quotation marks) in the value list. A “?” can be inserted only into a character column, and it
must be enclosed by quotation marks, otherwise this error will be returned.

0H000 Invalid SQLSTATE. expression evaluation error

Explanation: A problem occurred while evaluating an expression in the SQL statement. This can occur
when attempting to store a numeric value greater than the maximum size or less than the
minimum size of the datatype and domain intended to store the value.

0H000 Invalid SQLSTATE. host variables not allowed in this command

Explanation: This message is generated when a host variable or parameter marker appears in an SQL
statement that does not permit its use. Note that embedded SQL is a deprecated feature.

0H000 Invalid SQLSTATE. inappropriate specification of variable

Explanation: This message is generated when a host variable or parameter marker appears in an SQL
statement that does not permit its use. Note that embedded SQL is a deprecated feature.

0H000 Invalid SQLSTATE. Load API calling sequence error

4 Chapter 1: Data Definition Language Errors

 Explanation: This error can be returned when a successive data load is attempted after the previous load
did not terminate “cleanly”.

User Response: Restart the engine and loader, and attempt to load the data again. If the problem persists,
make note of the diagnostic message and circumstances, and contact Informatica Global
Customer Support.

0H000 Invalid SQLSTATE. Load API heap allocation failure

Explanation: A sufficient amount of memory could not be allocated for a File Archive Loader operation.

User Response: Free up some memory by terminating other running processes, and then attempt the data
load again. Also note that the cache size (Cache) parameter in the [Database instance-name]
section of the engine-side [Link] file should be set to 1/40 of the database size as a rule
of thumb. If the error occurred on a UNIX platform, try increasing the maximum data segment
or virtual memory size for the current execution environment using the system ulimit
command.

0H000 Invalid SQLSTATE. rel_create_rel (Selector TMPSELECT)

Explanation: An internal error occurred.

User Response: Make note of the diagnostic message and circumstances, and contact Informatica Global
Customer Support.

0H000 Invalid SQLSTATE. tried to add/subtract/multiply/divide inappropriate types

Explanation: This message is returned when arithmetic operations are attempted on datatypes or column
domains that do not support these operations.

For example, the following SQL statement will generate this error:

SELECT date1/date2 FROM table1;

21 Cardinality Violation
21000 Cardinality violation - scalar subquery returned more than one row
Explanation: This message appears when a scalar subquery returns more than one record. A scalar
subquery must return either a single record or no records.

User Response: If necessary, rewrite the scalar subquery to ensure that it will return at most one record.

21 Cardinality Violation 5
22 Data Exception
22002 Data exception - null value not allowed
Explanation: This message appears when an INSERT statement attempts to insert a null value into a
column that participates in a PRIMARY KEY constraint, or on which a NOT NULL constraint
is defined. None of the columns that are part of a primary key can have null values; while a
NOT NULL constraint ensures that the column contains no null values.

Note: that when loading into a table through the File Archive Loader, omitting a NOT NULL
column from the mapping section of the load specification script will always cause the
operation to fail with this error. Since the column is omitted, the File Archive Loader will
attempt to load the column with default null values, which are disallowed because of the NOT
NULL constraint.

22003 Data exception - numeric value out of range

Explanation: This message appears when an SQL operation results in a numeric overflow or underflow.
That is, an evaluated numeric expression is either too large or too small to be contained in a
suitable datatype without loss of precision or scale.

22012 Data exception - division by zero

Explanation: This message appears when a division-by-zero operation is attempted. Dividing by zero is
not permitted.

User Response: ALTER SESSION ALTER DIVISION command may be used to instruct the File Archive
Service to intercept divide-by-zero errors and return a null value instead.

22014 Data exception - field not found

Explanation: This message appears when a nonexistent column name is referenced in a SELECT,
INSERT, UPDATE, DELETE, or view definition statement.

User Response: If necessary, query the [Link] table or the [Link] view to
determine the correct spelling of the column name.

22500 Data exception - type mismatch

Explanation: This message appears whenever an SQL operation involving incompatible datatypes is
attempted.

For example, the following operations are not permitted:

¨ multiplying a number by a character string in a value expression

¨ inserting a numeric value into a date field

¨ specifying a UNION between two tables whose corresponding columns have incompatible
datatypes.

6 Chapter 1: Data Definition Language Errors

 22501 Data exception - string truncation
Explanation: This message appears when an INSERT or UPDATE statement specifies a character string
value that is longer than the maximum that can be stored in the target column. The length of
the character string must be less than or equal to the maximum length permitted by the
column.

This message is also returned if the concatenation operator ( || ) or the CONCAT( ) function
produces a string that is 4057 or more characters in length. The maximum length of a
concatenated string is 4056 characters.

23 Integrity Constraint Violation

23500 Unique constraint violation - duplicate value
Explanation: This message appears when an attempt is made to insert or update a duplicate value into a
column -- or a duplicate combination of values into columns -- on which there is a UNIQUE or
PRIMARY KEY constraint. The UNIQUE constraint prohibits duplicate column values; the
PRIMARY KEY is implicitly UNIQUE.

23606 Update failed - attempted to assign values to a row multiple times

Explanation: This message is returned when multiple values satisfy the conditions of the WHERE clause in
an UPDATE...FROM statement, such that the same row in the target table is slated to be
updated multiple times.

User Response: As the same row cannot be updated more than once in a single operation, this condition is
illegal. It is up to the user to ensure that a unique set of records is produced by the WHERE
clause.

25 Invalid Transaction State

25006 Execution failure - the transaction is read only
Explanation: This message appears when a statement which updates information in the database is
executed in a transaction that was specified as read-only (using the SET TRANSACTION
statement).

User Response: To make changes to the database, a new transaction - set to read-write - will have to be
started. End the current read-only transaction with a ROLLBACK; and then begin issuing the
database-altering SQL statements (since a new transaction is read-write by default).
Alternatively, use the SET TRANSACTION READ WRITE command to end the current
transaction with an implicit ROLLBACK and start a new transaction in read-write mode.

23 Integrity Constraint Violation 7

28 Invalid Authorization Specification
28500 Duplicate authorization name
Explanation: This message appears when a CREATE AUTHORIZATION statement specifies an
authorization name that already exists in the current database. All authorization names must
be unique within the database.

2B Dependent Privilege
2000B Dependent privilege descriptors still exist
Explanation: This message appears when a REVOKE statement attempts to remove a privilege from an
authorization that was granted WITH GRANT OPTION. The authorization has granted the
privilege to one or more other authorizations.

User Response: REVOKE the privilege from these other authorizations before attempting the original
REVOKE statement again.

3F Invalid Schema Name

3500F Duplicate schema name
Explanation: This message appears when a CREATE SCHEMA statement references a schema name that
already exists in the current database. All schema names must be unique within the database.

40 Transaction Rollback
40001 Transaction error - a possible conflict forced a rollback
Explanation: This message appears when a user attempts to commit database changes that conflict with
changes committed by one or more other concurrent user connections to the same database.
There will be an implicit ROLLBACK of any transactional changes made by the user receiving
this error.

For example, say that User 1 and User 2 connect to a database at the same time. If User 1
inserts data into Table A, and then User 2 drops Table A and commits the change, User 1 will
receive this transaction error when committing the data insert because Table A no longer
exists. Any changes made by User 1 in the transaction will be rolled back.

8 Chapter 1: Data Definition Language Errors

42 Syntax Error or Access Rule Violation
42000 Syntax error
Explanation: This message appears when a syntactically incorrect SQL statement is entered. The
message may also appear if the SQL statement references a non-delimited database object
name that contains an ASCII character not found in the following list:

¨ All uppercase and lowercase letters (A - Z, a - z)

¨ Digits (0 - 9)

¨ The symbols #, $, %, &, { (opening brace), } (closing brace), and _ (underscore)

In this case, the database object name must be delimited by double quotation marks ("...").

42100 Too many unions in statement

Explanation: This message is returned when the number of unions in a single SQL statement exceeds 32.
That is, the UNION keyword can appear at most 32 times in the combined query expression.

42400 No dba privileges

Explanation: This message appears when a user without DBA privileges attempts to execute the
SHUTDOWN command, or issues the SET TRANSACTION command with the ISOLATION
LEVEL EXCLUSIVE clause.

User Response: Only a user with DBA privileges may issue SHUTDOWN or SET
TRANSACTION...ISOLATION LEVEL EXCLUSIVE statements.

42500 Create authorization failed - insufficient privileges

Explanation: This message appears when a user without DBA privileges attempts a CREATE
AUTHORIZATION statement.

User Response: The user must be granted DBA privileges to create an authorization.

42502 Insufficient privileges on schema

Explanation: This message appears when a user attempts an ALTER TABLE, DROP TABLE, or DROP
VIEW statement in the user's default schema, and the user does not own the schema,
possess the OWNER privilege on it, or possess DBA privileges. This message also appears if
a DROP DOMAIN or RENAME DOMAIN statement specifies a domain on which the user
issuing the statement has no privileges.

User Response: In order to ALTER, DROP, or RENAME these database objects, the OWNER privilege on the
schema containing the object must be granted by the schema owner or the DBA.

42505 Alter authorization failed - insufficient privileges

Explanation: This message appears when a non-DBA user attempts to execute an ALTER
AUTHORIZATION statement that references another authorization. A user without DBA
privileges can alter only their own authorization settings.

User Response: In order to alter another authorization, the user must be granted DBA privileges.

42510 Drop authorization failed - insufficient privileges

Explanation: This message appears when a non-DBA user attempts a DROP AUTHORIZATION statement.

User Response: The user must be granted DBA privileges to drop an authorization.

42 Syntax Error or Access Rule Violation 9

 42511 Drop authorization failed - cannot drop DBA or PUBLIC
Explanation: This message appears when a user attempts to drop either the DBA or PUBLIC user. These
are special authorizations that cannot be dropped from the database.

42512 Drop authorization failed - authorization still owns objects

Explanation: This message appears when a user with DBA privileges attempts to drop an authorization
that still owns database objects.

User Response: Drop all of the database objects owned by the authorization before dropping the authorization.

42530 Drop schema failed - insufficient privileges

Explanation: This message appears when a non-DBA user attempts to drop a schema that they do not
own. The user executing the DROP SCHEMA command must own the specified schema, or
possess DBA privileges. The message also appears if a user with DBA privileges attempts to
drop the PUBLIC, SYSTEM, or DBA schema. These special schemas cannot be dropped.

42531 Drop schema failed - dependent objects

Explanation: This message appears when a user attempts to drop a schema that contains one or more
database objects.

User Response: Drop all database objects belonging to the schema before attempting to drop the schema.

42535 Create domain failed - insufficient privileges

Explanation: This message appears when a non-DBA user attempts to create a domain on a schema that
the user does not own or possess the OWNER privilege on.

User Response: In order to create a domain in that schema, the user must be granted the OWNER privilege
on the schema from the schema owner or DBA, or be granted DBA privileges.

42545 Create table failed - insufficient privileges

Explanation: This message appears when a non-DBA user attempts one of the following:

¨ a CREATE TABLE statement on a schema on which the user possesses no privileges

¨ an ALTER TABLE statement that references a table on which the user possesses no
privileges
¨ a CREATE TABLE statement that references a domain on which the user possesses no
privileges
¨ an ALTER TABLE...ADD COLUMN statement that references a domain on which the user
possesses no privileges

User Response: In order to create a table in a particular schema, the user must be granted the OWNER
privilege on the schema or DBA privileges on the database.

In order to alter a table, the user must be granted the OWNER privilege on the schema to
which the table belongs or DBA privileges on the database.

In order to specify a domain in a CREATE or ALTER TABLE statement, the user must be
granted USAGE on the domain, the OWNER privilege on the schema that contains the
domain, or DBA privileges on the database.

10 Chapter 1: Data Definition Language Errors

 42556 Set schema failed - insufficient privileges
Explanation: This message appears when a non-DBA user attempts a SET SCHEMA statement that
references a schema on which the user has no privileges.

User Response: The user must be granted the OWNER privilege on the schema or DBA privileges on the
database to set the schema.

50 Feature Not Implemented

50000 Feature not implemented
Explanation: This message appears when an unsupported SQL command or clause is attempted.

50111 Unable to insert into table

Explanation: This message appears when an INSERT...SELECT statement is attempted, specifying the
same table as both a source and destination for table data.

User Response: The data entered into a table through an INSERT...SELECT statement must come from other
tables.

50400 Non-existent authorization

Explanation: This message appears when an ALTER AUTHORIZATION, DROP AUTHORIZATION,
GRANT, REVOKE, or CREATE SCHEMA statement references an authorization name that
does not exist in the database.

User Response: If necessary, query the [Link] table or the

[Link] view to determine the correct spelling of the authorization name.

50500 Unable to proceed with Group By clause - incorrect argument list

Explanation: This message appears when a SELECT statement contains inappropriate arguments in the
GROUP BY, HAVING, WITH SAMPLE OF, and ORDER BY clauses.

User Response: Every value expression in the projection list that does not contain an aggregate function must
also appear in the GROUP BY clause (note that derived columns can only be referenced by
their numeric position in the projection list). Aggregate functions cannot appear in the
GROUP BY clause. The HAVING clause must include either an aggregate function or a
grouped column (that is, a column listed in the GROUP BY clause). The ORDER BY clause
must include a grouped column.

The optional SELECT clauses, if included, must appear in the following order:

¨ WHERE

¨ GROUP BY
¨ HAVING

¨ WITH SAMPLE OF

¨ ORDER BY

¨ FETCH FIRST...ONLY

50 Feature Not Implemented 11

 50501 Incorrect Order By clause
Explanation: This message appears when one or more SELECT statements are connected by the UNION
keyword, and a SELECT statement other than the final one contains an ORDER BY clause.
Only the last SELECT statement in a UNION may contain an ORDER BY clause, which is
used to order the UNION output table. Also note that the ORDER BY clause must reference
an output column by number.

This message may also appear when an internal error prevents the successful execution of a
SELECT statement with an ORDER BY clause. Retry the SQL command. If this error
message appears again, the DBA should shut down the database instance, and then restart
the instance and reestablish a connection. If this error message still appears in response to
the original SQL command, contact Informatica Global Customer Support.

50502 Mismatched union fields

Explanation: This message appears when a UNION is attempted between two tables with a different
number of columns. The two tables must have the same number of columns, and the
corresponding columns must have compatible datatypes or File Archive Service domains.

50503 Invalid expression - Having without Group By

Explanation: This message appears when a SELECT statement includes a column in the projection list
and a HAVING clause, but does not include a GROUP BY clause. The SELECT statement
cannot include a HAVING clause without a GROUP BY clause, unless the projection list and
the HAVING clause contain only aggregate functions.

50600 Sample incorrect argument list

Explanation: This message appears when the SELECT...WITH SAMPLE OF clause specifies a number
less than or equal to zero (0), or the number argument is greater than the factor argument.

User Response: Ensure that the WITH SAMPLE OF number is a positive integer, and that number divided by
factor does not produce a value greater than 1.0 (that is, 100%).

50601 Incorrect With Sample Of clause

Explanation: This message appears when one or more SELECT statements are connected by the UNION
keyword, and a SELECT statement other than the final one contains a WITH SAMPLE OF
clause. Only the last SELECT statement in a UNION may contain a WITH SAMPLE OF
clause, which is used to return a subset of the UNION output table.

50700 Fetch First incorrect argument list

Explanation: This message appears when the FETCH FIRST...ONLY clause specifies zero or a negative
number of rows, or specifies a ratio greater than 1.0.

User Response: At least one row must be specified when fetching an absolute number of rows. When fetching
a percentage of the result set, at most 100% of the results (a ratio of 1.0) can be returned.

50701 Incorrect Fetch First Only clause

Explanation: This message is returned when the FETCH FIRST...ONLY clause is not the last clause in the
SELECT statement.

User Response: Syntactically, the FETCH FIRST...ONLY clause must appear after all other SELECT clauses.
In the case of a series of UNIONed SELECT statements, the FETCH FIRST...ONLY clause
can be included only at the end of the final query.

12 Chapter 1: Data Definition Language Errors

54 Privilege Error
54500 Insufficient privileges
Explanation: This message appears when an SQL statement references a database object on which the
user issuing the SQL statement has no privileges.

User Response: The user must be granted the required privilege on the database object by the owner of the
object or a user with DBA privileges.

54501 Cannot modify privileges for DBA authorization

Explanation: This message appears when a GRANT or REVOKE statement attempts to modify the DBA's
privileges. DBA privileges cannot be modified.

54502 Cannot modify own privileges

Explanation: This message appears when an authorization attempts to modify their own privileges through
a GRANT or REVOKE statement. Users cannot modify their own privileges.

54503 Cannot grant privileges - non-existent object

Explanation: This message appears when a user attempts to grant privileges on a database object that
does not exist in the current schema or database.

User Response: If the object belongs to a different schema, qualify the object name with the schema name in
the GRANT statement (that is, [Link]-name). If necessary, query the
appropriate system table or PUBLIC view to determine the correct spelling of the database
object name.

54504 Cannot revoke privileges - non-existent object

Explanation: This message appears when a user attempts to revoke privileges on a database object that
does not exist in the current schema or database.

User Response: If the object belongs to a schema other than the current one, qualify the object name with the
schema name in the REVOKE statement (that is, [Link]-name). If necessary,
query the appropriate PUBLIC view to determine the correct spelling of the database object
name.

54505 Invalid privilege

Explanation: This message appears when a user attempts to grant or revoke an invalid privilege type.

54508 Non-existent routine

Explanation: This message appears when an SQL statement contains a string that ends with the substring
'()' or '(x)', where x is a numeric value, a string enclosed by single quotation marks, or the
name of a column from a table referenced in the statement.

User Response: The File Archive Repository Service interprets this string as a routine call. Routines are not
supported in the current release.

54509 Non-existent privilege

Explanation: This message appears when a REVOKE statement references a privilege that is not
possessed by the specified authorization.

54 Privilege Error 13
70 Schema Exception
70400 Non-existent schema
Explanation: This message appears when a SET SCHEMA or DROP SCHEMA statement references a
schema name that does not exist in the current database, or when a database object name is
qualified with a schema name that does not exist in the current database.

User Response: If necessary, query the [Link] table or the [Link] view to
determine the correct spelling of the schema name.

80 Domain Error
80110 Create domain failed - invalid datatype
Explanation: This message appears when a CREATE DOMAIN statement specifies a nonexistent datatype.

80111 Create domain failed - invalid precision

Explanation: This message appears when a CREATE DOMAIN statement specifies a DEC, DECIMAL, or
NUMERIC datatype with a precision of 32 or greater, or less than 1. The maximum precision
allowed for these datatypes is 31; the minimum is 1.

80112 Create domain failed - invalid scale

Explanation: This message appears when a CREATE DOMAIN statement specifies a DEC, DECIMAL, or
NUMERIC datatype with a scale greater than the precision, or less than zero (0). The scale
must be less than or equal to the precision, and cannot be a negative number.

80113 Create domain failed - invalid length

Explanation: This message appears when a CREATE DOMAIN statement specifies a CHAR,
CHARACTER, VARCHAR, CHARACTER VARYING, or CHAR VARYING datatype with a
length less than 1 or greater than 4056.

User Response: If a length argument is included with the character datatypes, it must be a value between 1
and 4056.

80140 Create domain failed - duplicate domain name

Explanation: This message appears when a CREATE DOMAIN statement specifies a domain name that
already exists in the database for the specified schema.

User Response: Domain names must be unique within a schema.

80141 Create domain failed - reserved domain name

Explanation: This message appears when a CREATE DOMAIN statement specifies a domain name that
begins with an underscore character (“_”).

User Response: Only system-generated domains are permitted to begin with the underscore character.

14 Chapter 1: Data Definition Language Errors

 80310 Drop domain failed - dependent objects exist
Explanation: This message appears when one or more columns reference the domain specified in a DROP
DOMAIN statement.

User Response: Drop the columns that store values in the domain, or the tables containing those columns,
before attempting to drop the domain.

80311 Drop domain failed - system domain

Explanation: This message appears when a DROP DOMAIN statement references a system domain (that
is, any of the default domains belonging to the SYSTEM schema). System domains cannot
be dropped.

80400 Non-existent domain

Explanation: This message appears when a DROP DOMAIN or RENAME DOMAIN statement references a
domain name that does not exist in the database.

User Response: If necessary, query the [Link] table or the [Link] view to
determine the correct spelling of the domain name.

80500 Rename domain failed - system domain

Explanation: This message appears when a RENAME DOMAIN statement references a system domain
(that is, any of the default domains belonging to the SYSTEM schema). System domains
cannot be renamed.

80501 Rename domain failed - new domain name already in use

Explanation: This message appears when a RENAME DOMAIN statement attempts to change a domain
name to one that already exists in the same schema. Domain names must be unique within a
schema.

90 Table and View Error

90100 Create table failed - duplicate table name
Explanation: This message appears when a CREATE TABLE or CREATE VIEW statement attempts to
create a new table or view using a table and view name that already exists for the current
schema. All table and view names must be unique within a schema.

90201 Create view failed - a column is a projected expression that is not named
Explanation: This message appears when a CREATE VIEW statement includes an unnamed value
expression (that is not a direct column reference) in the projection list of the defining SELECT
statement.

User Response: The value expression must be given a correlation name, which will be the name of the output
column when the view is queried.

90 Table and View Error 15

 90205 Create table failed - too many columns in table definition
Explanation: This message appears when a CREATE TABLE statement specifies 4097 or more columns.
A maximum of 4096 columns are permitted in each table.

This error is also returned when the number of arguments in the view column list of a
CREATE VIEW statement is more or less than the number of output columns returned by the
defining query expression. The number of view column names must match precisely the
number of columns in the query expression result table.

90206 Create table failed - too many keys in constraint definition

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement includes 65 or
more columns in a UNIQUE or PRIMARY KEY table constraint definition. UNIQUE and
PRIMARY KEY constraints can have at most 64 participating columns.

90207 Create table failed - no column name provided in key definition

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement includes a
PRIMARY KEY or UNIQUE table constraint definition with an empty column list.

User Response: The column list of a PRIMARY KEY or UNIQUE table constraint must reference at least one
column in the designated table.

90220 Create table failed - duplicate unique constraint

Explanation: This message appears when a CREATE TABLE or ALTER TABLE...ADD COLUMN
statement repeats the UNIQUE keyword for a column constraint.

For example,

CREATE TABLE t (c1 INT UNIQUE UNIQUE);

A UNIQUE constraint can be defined only once for a particular column.

90310 Drop table failed - dependent objects exists

Explanation: This message appears when a DROP TABLE statement specifies a table that is referenced
by one or more view definitions.

User Response: Drop the dependent views before attempting to drop the table.

90311 Drop table failed - cannot drop system level table

Explanation: This message appears when a DROP TABLE statement specifies a system table (that is, any
of the default tables in the SYSTEM schema). These system tables are essential to the
functioning of the File Archive Service database and cannot be dropped.

90312 Drop table failed - table is a view

Explanation: This message appears when a DROP TABLE statement references a view.

User Response: Use a DROP VIEW statement to remove a view from the database.

90313 Drop view failed - base table

Explanation: This message appears when a DROP VIEW statement specifies a table.

User Response: Use a DROP TABLE statement to remove a table from the database.

16 Chapter 1: Data Definition Language Errors

90314 Drop view failed - dependent objects exists
Explanation: This message appears when a DROP VIEW statement specifies a view on which one or more
other views are based.

User Response: The view cannot be dropped until the dependent views are dropped.

90320 Alter table failed - non-existent constraint

Explanation: This message appears when an ALTER TABLE...DROP CONSTRAINT statement references
a nonexistent constraint. Constraints can only be dropped by specifying the constraint name.
If a constraint was created without a user-defined name, one was routinely generated by
SAND CDBMS Nearline.

User Response: The easiest way to determine the constraint name is to violate the constraint intentionally.
This will produce an error message that lists the name of the violated constraint.

90321 Alter table failed - system table

Explanation: This message appears when an ALTER TABLE statement attempts to modify the structure of
a system table (that is, any of the default tables in the SYSTEM schema).

User Response: These system tables are essential to the functioning of the SAND CDBMS Nearline database
and cannot be altered directly.

90322 Alter table failed - cannot alter a view

Explanation: This message appears when an ALTER TABLE statement attempts to modify a view.

User Response: If you wish to change a view definition, drop the view, then recreate the view with the desired
attributes.

90323 Alter table failed - too many columns in table definition

Explanation: This message appears when an ALTER TABLE statement attempts to add a column to a
table that already has 4096 columns. The maximum number of columns in one table is 4096.

90330 Rename table failed - system table

Explanation: This message appears when a RENAME TABLE statement references a system table (that
is, any table in the SYSTEM schema).

User Response: System tables cannot be renamed.

90331 Rename table failed - dependent objects exists

Explanation: This message appears when RENAME TABLE statement attempts to rename a table that is
referenced by a view definition.

User Response: Drop the dependent view before attempting the RENAME TABLE command, then redefine
the view with the new table name.

90332 Rename table failed - table already exists

Explanation: This message appears when a RENAME TABLE statement attempts to change the name of a
table to one that already exists in the same schema.

User Response: All table names must be unique within a schema.

90 Table and View Error 17

 90400 Non-existent table
Explanation: This message is returned when an ALTER TABLE, CREATE VIEW, DELETE, DROP TABLE,
DROP VIEW, INSERT, SELECT, or UPDATE statement references a table or view name that
does not exist in the current schema.

User Response: If the table or view belongs to a schema other than the current one, the table and view name
must be qualified with the schema name (that is, schema- [Link]-name or schema-
[Link]-name). If necessary, query the [Link] table or the [Link]
view to determine the correct spelling of the table and view name.

J0 Invalid Integrity Constraints

J0200 Invalid unique constraint - non-existent columns in definition
Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement attempts to set
a UNIQUE constraint on a column that does not exist in the table.

User Response: For an ALTER TABLE statement, if necessary, query the [Link] table or the
[Link] view to determine the correct spelling.

J0201 Invalid unique constraint - column repeated in definition

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement attempts to
include the same column in more than one UNIQUE constraint, or in one PRIMARY KEY
constraint and one or more UNIQUE constraints, within the same statement. A column may
participate in at most one UNIQUE constraint; if a column participates in a UNIQUE
constraint, it cannot subsequently participate in a primary key.

This message is also generated when the same column name is repeated in a UNIQUE
constraint definition in a CREATE TABLE or ALTER TABLE statement. A particular column
name can be included only once in a table constraint definition.

J0203 Invalid unique constraint - existing rows would violate the proposed constraint
Explanation: This message appears when an ALTER TABLE statement attempts to add a UNIQUE or
PRIMARY KEY constraint to a table that has duplicate values in the proposed key columns.

User Response: The UNIQUE and PRIMARY KEY constraints ensure that each value or set of values in the
participating columns is unique, and therefore cannot be added to a table whose existing
values would immediately violate the constraint.

J0204 Invalid unique or primary key constraint - a key is a subset of another key
Explanation: This message appears when an ALTER TABLE statement attempts to add a UNIQUE or
PRIMARY KEY constraint that includes a column already participating in a UNIQUE
constraint.

A column can participate in at most one UNIQUE constraint, and a column that is part of a
UNIQUE constraint cannot also be part of a primary key.

18 Chapter 1: Data Definition Language Errors

 J0300 Invalid primary key constraint - only one primary key allowed
Explanation: This message appears when a CREATE TABLE statement attempts to set more than one
primary key column constraint, or an ALTER TABLE statement attempts to add a primary key
constraint to a table that already has one. A table can have at most one primary key
constraint.

User Response: If you wish to change the primary key constraint on a table, drop the existing primary key
constraint through the ALTER TABLE...DROP CONSTRAINT command, then use the ALTER
TABLE...ADD CONSTRAINT command to set the desired primary key constraint.

J0301 Invalid primary key constraint - non-existent columns in definition

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement attempts to set
a primary key constraint on a column that does not exist in the table.

J0302 Invalid primary key constraint - column repeated in definition

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement attempts to set
a primary key constraint on the same column more than once in the same statement.

J0303 Invalid primary key constraint - duplicate constraint

Explanation: This message appears when a CREATE TABLE statement attempts to include the same set
of columns in a PRIMARY KEY constraint more than once. A PRIMARY KEY constraint can
be defined only once in a table.

J0304 Invalid primary key constraint - null value in constraint definition

Explanation: This message appears when an ALTER TABLE statement attempts to include a column that
contains a null value as part of a primary key constraint. No individual column participating in
a primary key constraint may contain a null value.

J0400 Invalid constraint definition - duplicate constraint name

Explanation: This message appears when a CREATE TABLE statement includes two constraint definitions
with the same constraint name, or when an ALTER TABLE statement attempts to add a
constraint whose name matches one already defined for the table. Each constraint defined on
the same table must have a unique constraint name.

K0 Column Error
K0100 Invalid column definition - invalid datatype
Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement defines a
column with an unrecognized datatype or SAND CDBMS Nearline domain.

User Response: If necessary, query the [Link] table or the [Link] view to
determine the correct spelling of the SAND CDBMS Nearline domain name. Note that if a
referenced domain belongs to another schema, the domain name must be qualified by the
schema name; that is, [Link]-name.

K0 Column Error 19
 K0101 Invalid column definition - invalid precision
Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement specifies a
DEC, DECIMAL, or NUMERIC datatype with a precision less than 1 or greater than 31. The
minimum precision permitted for these datatypes is 1; the maximum is 31.

K0102 Invalid column definition - invalid scale

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement specifies a
DEC, DECIMAL, or NUMERIC datatype with a scale greater than the precision. The scale
must be less than or equal to the precision.

K0103 Invalid column definition - invalid length

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement specifies a
column of type CHAR or VARCHAR with a length greater than the maximum size (4056) or
less than the minimum (1).

K0106 Invalid column definition - duplicate not null constraint

Explanation: This message appears when a CREATE TABLE or ALTER TABLE statement defines two or
more NOT NULL constraints on the same column. A column can have at most one NOT
NULL constraint.

K0200 Invalid column definition - duplicate column name

Explanation: This message appears when a CREATE TABLE or CREATE VIEW statement defines two or
more columns with the same name. This message is also generated when the new column
name specified in an ALTER TABLE...ADD COLUMN or ALTER TABLE...RENAME COLUMN
statement duplicates a column name that already exists in the table. Each column in the
same table or view must have a unique name.

K0300 Drop column failed - column is part of a constraint key

Explanation: This message appears when an ALTER TABLE...DROP COLUMN statement attempts to
drop a column that is part of a multi-column table constraint.

User Response: Drop the table constraint before attempting to drop the column, and then redefine the table
constraint without the dropped column.

K0302 Drop column failed - dependent views

Explanation: This message appears when an ALTER TABLE...DROP COLUMN statement attempts to
drop a column that is referenced by a view.

User Response: Drop the view before attempting to drop the column, and then recreate the view without
referencing the dropped column.

K0310 Drop column failed - too few columns in table definition

Explanation: The message appears if an ALTER TABLE...DROP COLUMN statement attempts to drop the
only column in the specified table. A table must have at least one column.

20 Chapter 1: Data Definition Language Errors

K0400 Non-existent column
Explanation: This message appears when a CREATE TABLE, ALTER TABLE, INSERT, UPDATE,
GRANT, or REVOKE statement references a column name that does not exist in the
specified table. The message is also returned if a SELECT statement using the JOIN syntax
neglects to reference any columns from one of the joined tables. At least one column from
each table in the join must be referenced in the join condition.

K0500 Ambiguous column reference

Explanation: This message appears when a SELECT or CREATE VIEW statement, or the query
expression clause of an INSERT statement, does not qualify duplicate column names
selected from multiple tables or views.

User Response: To avoid this error, prefix the column names with the respective table, view, or correlation
names, followed by a period (that is, [Link]-name, [Link]-name, or
[Link]-name).

K0600 Mismatch between column list and columns in table

Explanation: This message appears when an INSERT statement contains a column list with duplicate
column names, or when an UPDATE statement attempts to update the same column more
than once.

User Response: The same column name may not be specified more than once in an INSERT column list or in
the SET clause of an UPDATE statement.

K0700 Table name appears more than once

Explanation: This message appears when a SELECT or CREATE VIEW statement, or the query
expression clause of an INSERT statement, specifies the same table or view name more than
once in the FROM clause, without correlation or schema qualification. The table, view, or
correlation names appearing in the FROM clause must be unique. The following statement,
for instance, produces this error message:

SELECT column1, column3

FROM table_name, table_name ;

If the duplicate table and view names use correlation names, the statement becomes legal,
as there are now two separate instances of table table_name in the FROM list:

SELECT t1.column1, t2.column3

FROM table_name t1, table_name t2 ;

Tables or views sharing the same name but belonging to different schemas may also appear
in the FROM clause, provided they are prefixed with their respective schema name, for
example:

SELECT *

FROM schema1.table_name, schema2.table_name ;

K0 Column Error 21
M0 INSERT Failure
M0100 Insert failed - incorrect number of values
Explanation: This message appears when an INSERT statement attempts to insert more or less values
than there are columns in the target table. The number of values inserted into a table must
correspond exactly to the number of data fields in the table.

N0 Expression Error
N0001 Expression evaluation error
Explanation: This message appears when an SQL statement contains an arithmetic expression that
produces a value greater than or less than the numeric datatype or domain intended to store
the value.

O0 Invalid Database Reference and Limit Exceeded

O0100 Invalid database reference
Explanation: This message appears when a database object is qualified with a database name, for
instance, [Link]-name. Database objects may not be qualified
with the database name in the current release of SAND CDBMS Nearline.

O0200 Table reference limit exceeded

Explanation: This message appears when the number of tables referenced in a single query expression
exceeds 128. The maximum number of table references permitted in a query, including the
tables referenced in subqueries and in the definitions of all views in the query, is 128.

User Response: If possible, reformulate the query with fewer table references.

O0201 Column reference limit exceeded

Explanation: This message appears when the number of columns referenced in a single query expression
exceeds 8192. The maximum number of column references permitted in a query, including
the tables referenced in subqueries and in the definitions of all views in the query, is 8192.

User Response: If possible, reformulate the query with fewer column references.

22 Chapter 1: Data Definition Language Errors

P0 Subsystem Failure
P0200 Vector subsystem failure - EID out of range
Explanation: An internal error has occurred. Report this error and the circumstances to Informatica Global
Customer Support.

P0300 Execution failure - Join intermediate exceeds limit

Explanation: This message appears when a query expression join produces an intermediate result table
with more than five hundred billion (500,000,000,000) rows. The maximum number of rows
that can appear in an intermediate joined table is five hundred billion.

User Response: If possible, rewrite the query expression to reduce the complexity of the join, or utilize views
that deal with a subset of the data in the original join tables.

P0400 Execution failure - Statement execution has been terminated

Explanation: This message appears when a user’s running query has been cancelled, either by the user or
another user with DBA privileges.

Q0 Database Error
Q0100 Open database failure
Explanation: This message appears when SAND CDBMS Nearline fails to read a database. This can be
caused by hardware or operating system issues.

User Response: Consult your system administrator for help with resolving this problem.

Q0101 Open database failure - another database instance is already running

Explanation: This message appears if an attempt is made to start a database instance while another
database instance is already running. The same File Archive Repository Service can run only
one database instance at a time.

Q0102 Open database failure - non-existent database

Explanation: This message appears when a client application attempts to connect to a database that does
not have a section header in the engine-side [Link] file and is not located in the SAND
CDBMS Nearline support directory.

User Response: Make sure that a corresponding entry for the database exists in the engine-side [Link]
file before attempting to connect to the database.

Q0103 Open database failure - no read permission

Explanation: This message appears when a user attempts to connect to a database instance on which the
File Archive Repository Service does not have read permission.

User Response: Ask the system administrator to change the permissions on the appropriate database files, so
as to allow engine read access to the database.

P0 Subsystem Failure 23
S0 Execution Failure
S0101 Execution failure - function not implemented
Explanation: If the secondary message is "Load initialization failure due to active applications", this error
was likely caused by an attempt to load into a database that has one or more non-loader
clients connected.

User Response: Before reattempting the load operation, the non-loader users should be instructed to
disconnect, or the -u flag should be included in the File Archive Loader invocation to
disconnect other users routinely.

If the secondary message is anything else, then an internal error has occurred. Report this
error and the circumstances to Informatica Global Customer Support.

T0 Execution Failure
T0803 Execution failure - time limit exceeded
Explanation: This message appears when the execution time of an individual SQL command within a
transaction exceeds the time limit specified in the SET TRANSACTION..TIMEOUT statement
that began the transaction. The message is also returned when the execution time exceeds
the time limit established with the nisqlm .SESS DURATION command. Note that SET
TRANSACTION...TIMEOUT sets its limit in seconds, while the .SESS DURATION limit is in
minutes.

24 Chapter 1: Data Definition Language Errors

CHAPTER 2

File Archive Repository Service

Exit Codes
This chapter includes the following topic:

¨ File Archive Repository Service Exit Codes, 25

File Archive Repository Service Exit Codes

The following exit code messages might appear when you run the File Archive Repository Service.

Exit code 1
Explanation: This exit code is returned when incorrect syntax is entered to start the File Archive
Repository Service. The proper syntax is displayed.

Exitcode2 Could not find the NUCLEUS environment variable

Explanation: The NUCLEUS environment variable has not been set. This variable contains information
required by the SAND CDBMS Nearline Server and client applications. The only non-optional
NUCLEUS parameter is the SUPPORT path; this parameter tells the SAND CDBMS Nearline
Server and client applications where to find the [Link] file. All other parameters can be
set either in the NUCLEUS environment variable or the [Link] file. If a parameter
appears in neither the NUCLEUS variable or the [Link] file, the default parameter value
is used.

Exitcode3 The parameter SUPPORT was not found in the NUCLEUS environment variable
Explanation: This message is returned when the NUCLEUS environment variable does not contain the
SUPPORT path, which tells SAND CDBMS Nearline Server and client applications where to
find the [Link] file.

Exitcode4 The [Link] file was not found at 'file-path'. Check the parameter SUPPORT in the
NUCLEUS environment variable
Explanation: The SUPPORT parameter in the NUCLEUS environment variable does not contain the
correct SAND CDBMS Nearline support path, or the [Link] file has been removed from
the support directory.

User Response: Ensure that the SUPPORT path corresponds to the exact location of the [Link] file.

25
 Exitcode5 The size of the initialization file should be less than 65536
Explanation: SAND CDBMS Nearline Server and client applications cannot read a [Link] file greater
than 64 KB in size.

User Response: Reduce the size of the [Link] file by removing unnecessary entries and comments.

Exitcode10 Could not find a section 'Connection connection-name' in the initialization file
Explanation: The connection name specified to start the File Archive Repository Service does not have a
corresponding [CONNECTION connection-name] section in the [Link] file.

User Response: Ensure that the connection name supplied in the File Archive Repository Service invocation
matches the spelling of the connection name in the [Link] file.

Exitcode11 Could not find a section 'Database db-name' in the initialization file
Explanation: The Nucleus and File Archive repository database name specified to start the File Archive
Repository Service does not have a corresponding [DATABASE database-name ] section
in the [Link] file.

User Response: Ensure that the database name supplied in the File Archive Repository Service command
matches the spelling of the name in the database section header.

Exitcode12 Database creation failed - cannot open error message file

Explanation: The file [Link] could not be found in the SAND CDBMS Nearline support directory. This
file is required to create a Nucleus database.

Exitcode13 Could not find a database path in the initialization file

Explanation: The [DATABASE database-name ] section in the [Link] file, where database-name
corresponds to the database name specified to start the File Archive Repository Service,
does not contain a DatabasePath parameter. This parameter tells the File Archive Repository
Service where to find the primary database file (database-name.n00), which is required to
start the database.

User Response: Add the following line to the relevant DATABASE section in the [Link] file:

DatabasePath=<database location>

For example:

DatabasePath=/usr/sand/db

Exitcode14 The database path in the initialization file is too long

Explanation: The [DATABASE database-name ] section in the [Link] file (where database-name
corresponds to the database instance name specified to start the File Archive Repository
Service) contains a DatabasePath value that is 129 characters or more in length. The
maximum database path length is 128 characters.

User Response: Create a new database in, or move the existing database file to, a directory whose full path is
128 characters or fewer, and update the DatabasePath value in the [Link] file.

Exitcode20 The server was unable to bind to port 'x'. The port may be in use.
Explanation: The indicated port cannot be used by the File Archive Repository Service, most likely
because it is being used by another process.

26 Chapter 2: File Archive Repository Service Exit Codes

User Response: Simply change the Port value in the [Link] file, in the [CONNECTION connection-
name ] section that corresponds to the connection name used to start the File Archive
Repository Service. The port value can be any number between 1,024 and 65,535 inclusive.

Exitcode30 Cannot build a database in run-mode

Explanation: A Nucleus database could not be created. Ensure that the [DATABASE database-name ]
section in the [Link] file (where database-name corresponds to the Nucleus or File
Archive repository database name specified to start the File Archive Repository Service) has
its RUNMODE parameter set to “Real”.

User Response: Removing the RUNMODE parameter altogether will have the same effect, since Real is the
default mode.

Exitcode40 Database creation failed - cannot create directory 'file-path'

Explanation: This message is returned when the [DATABASE database-name ] section in the [Link]
file (where database-name corresponds to the database name specified to start the File
Archive Repository Service) contains an invalid DatabasePath value.

User Response: Ensure that the database path actually exists on the host computer. If the database directory
(that is, the last directory in the path) does not exist, the File Archive Repository Service will
create it, provided the rest of the path is valid.

For example:

DatabasePath=/usr/sand/db

If the directory “db” does not exist already, it will be created by the File Archive Repository
Service, as long as the path “/usr/sand” exists on the host computer.

On the other hand:

DatabasePath=/usr/sand/nonexistentdir/db

If the directory “nonexistentdir” does not exist, “db” will not be created, and this Exit Code will
be returned.

Exitcode41 Database creation failed - cannot read the seed database 'expected-seed-path'
Explanation: The seed database file (ndb.n00) does not exist in the SAND CDBMS Nearline support
directory, or you do not have the appropriate access permissions on the seed database file.
The seed database is required to create a Nucleus database.

User Response: If the seed database file has been removed, extract the required file from the Nucleus
installation files to the support directory. If you do not have read permission on the seed
database file, have the system administrator grant you this permission.

Exit code 42: Database creation failed - cannot create file 'database-file-name' in directory 'database-path'

Explanation: This message is returned when attempting to create a Nucleus database in a directory on
which you do not have the appropriate access permissions.

User Response: Have the system administrator grant you write permission on the directory specified in the
error message.

Exitcode50 Could not access the file 'database-path'

Explanation: This error may be caused when the primary database file could not be read. This would occur
if you do not have read permission on the primary database file.

File Archive Repository Service Exit Codes 27

 User Response: In this case, have the system administrator grant this permission.

Exitcode51 Could not start 'database-path' - incompatible format

Explanation: This message is returned when attempting to start a database instance from primary and
secondary database files that either use a different page size from the SAND CDBMS
Nearline Server software (1 MB vs. 64 KB), or that were created under another, incompatible
operating system (big endian vs. little endian). For example, this would occur when
attempting to start a database in HP Tru64 UNIX from database files created under Solaris,
or when attempting to start a Solaris database with the Windows the File Archive Repository
Service program.

Exitcode54 Could not access secondary database file

Explanation: This message is returned when a secondary database file or the database temporary file is
not accessible.

User Response: Ensure that none of the secondary files have been moved from the “database drives”
locations specified in the database configuration record. Also make sure that the “tempfile”
directory path specified in the configuration record points to a valid location.

28 Chapter 2: File Archive Repository Service Exit Codes

CHAPTER 3

Load Balancer and Administration

Errors
This chapter includes the following topics:

¨ Load Balancer and File Archive Administration Utility errors, 29

¨ Other ssaserver Messages, 36

¨ File Archive Repository Administration Exit Code Errors, 38

¨ Load Balancer and File Archive Repository Administration Errors, 39

¨ Rule Engine Messages, 45

Load Balancer and File Archive Administration Utility

errors
The following errors might appear when you run Load Balancer and the File Archive Administration utility.

Column-name : unknown column or invalid type definition

Explanation: In File Archive Administration utility interactive SQL mode, a query specified an invalid
column, or the optimized file archive data file being queried contains invalid header
information. In the latter case, the data file might have to be re-created.

Cannot create file: x

Explanation: The specified SCT file could not be created. This might occur if the current user does not
possess the required permissions on the target directory or file. If the SCT file already exists,
it might have been locked by another process.

Cannot mask SIGINT signal. Ctrl^C handler will not be installed.

Explanation: An internal error occurred: pressing <Ctrl+C> will not shut down the program.

User Response: It might be necessary to kill the Archive Administration utility process through the operating
system, if you wish to cancel program execution.

Cannot run Ctrl^C handling thread. Ctrl^C handler will not be installed.

Explanation: An internal error occurred: pressing <Ctrl+C> will not shut down the program.

29
 User Response: It might be necessary to kill the Archive Administration utility process through the operating
system, if you wish to cancel program execution.

Connection Error: n

Explanation: A connection error occurred while attempting to load file archive data into a SAND database.

User Response: Ensure that the database is currently running and is accessible through the network, and then
attempt the operation again.

Authorization not granted

Explanation: This message is returned when a user without DBA privileges on the File Archive repository
database attempts to execute the SHUTDOWN IMMEDIATE command from a client
connection. Only a user with DBA privileges can shut down ssaserver.

Can't compare column column1 with column2 from different domains

Explanation: The query contains an illegal comparison between columns belonging to incompatible
domains.

Can't compare column x of type type1 with constant of type type2

Explanation: The query contains an illegal comparison between a column and a literal with incompatible
datatypes.

Can't compare column with itself

Explanation: Queries cannot contain expressions that compare a column with itself, for example, "c1 >=
c1".

User Response: The query will have to be reformulated.

Cannot execute IN <file> clause against non-archived table

Explanation: The IN-file syntax can be used only with archived tables. Attempting to include it in a query
against standard tables will generate this error message.

Cannot open INI file.

Cannot open INI file <path>\[Link].
Explanation: The ssaserver and Agent configuration file ([Link]) was not found in the path specified by the
SSA_INI_DIR environment variable.

User Response: Ensure that the [Link] file is located in the correct directory. If necessary, move the file or
change the value of the SSA_INI_DIR environment variable.

Column names too long

Explanation: An internal error occurred: The fetched column names collectively exceed the size of the
buffer created to hold them.

User Response: Attempt the operation again, possibly after restarting ssaserver and File Archive repository
database. If the problem persists, contact Informatica Global Customer Support.

30 Chapter 3: Load Balancer and Administration Errors

CVDB::Open( VDB-name, 0, cache-size ) : error opening file

Explanation: A temporary file could not be created in the directory specified by the TEMPDIR parameter in
the [Link] file.

¨ Write permission on the target directory is denied

¨ A component of the TEMPDIR path is not a directory

¨ The length of the path and file name exceed the operating system limit

¨ There is not enough system memory available to create the temporary file

¨ There are no more system file descriptors available

User Response: Ensure that the appropriate permissions on the target directory have been granted. As well,
make sure that the correct directory path is specified by the TEMPDIR parameter in the
[Link] file.

Error #n starting up COM.

Explanation: An internal error occurred while attempting to start ssaserver. If the problem persists, contact
Informatica Global Customer Support for help.

Error #n starting up EXE.

Explanation: An internal error occurred while attempting to start ssaserver. If the problem persists, contact
Informatica Global Customer Support for help.

Error #n starting up META.

Explanation: This message is returned if the wrong connection name is specified when starting up the File
Archiv Service.

User Response: Ensure that the supplied connection name is the one used to start the File Archive repository
database with the File Archive Repository Service.

Error accessing file 'file-name'

Explanation: The IN-file clause specified a file that could not be accessed.

User Response: Ensure that the file is accessible on the network before re-attempting the query.

Error creating temporary repository

Explanation: A virtual file system (VFS) could not be created. This can occur if one of the following
conditions is true:

¨ Write permission on the target directory is denied

¨ A component of the VFS path is not a directory

¨ The length of the path and file name exceed the operating system limit

¨ There is not enough system memory available to create the VFS

¨ There are no more system file descriptors available

Load Balancer and File Archive Administration Utility errors 31

 User Response: Ensure that the appropriate permissions on the target directory have been granted. As well,
make sure that the correct directory path is specified by the VFS parameter in the [QUERY]
section of the [Link] file.

If the problem still occurs, use the standard file system instead. Remove the VFS parameter
from the [Link] file; the Archive Administration utility will create a temporary repository in the
location specified by the [Link] TEMPDIR parameter, using standard files.

Error executing query

Explanation: The query could not be executed for an indeterminate reason.

User Response: Attempt the operation again, possibly after restarting ssaserver and File Archive repository
database. If the problem persists, contact Informatica Global Customer Support for
assistance.

Error opening file 'file-name'

Explanation: The IN-file clause specified a file that could not be opened.

User Response: Ensure that the file exists in the given location before re-attempting the query.

Error reading file 'file-name'

Explanation: The IN-file clause specified a file that cannot be read.

User Response: Ensure that the file has not been locked by another process, and that the appropriate
permissions have been granted on the file, before re-attempting the query.

Error running ssau program

Explanation: The Archive Administration utility could not be started. The Archive Administration utility is
used by the load balancer to manipulate optimized file archive data files. If the Archive
Administration utility executable is deleted, renamed, or removed from the File Archvie
Service support directory, the load balancer cannot handle client requests involving archived
tables.

User Response: Ensure that the Archive Administration utility is in the appropriate directory path and has not
been renamed.

Error starting up LOG

Explanation: The ssaserver log file could not be created. This can occur if one of the following conditions
is true:

¨ The directory path specified by the LOGDIR parameter in the [SERVER] section of the
[Link] file is invalid
¨ Write permission on the target directory is denied

¨ The directory path length exceeds the operating system limit

¨ There is not enough system memory available to create the log file

¨ There are no more system file descriptors available

32 Chapter 3: Load Balancer and Administration Errors

User Response: Ensure that the correct directory path has been specified by the LOGDIR parameter in the
[SERVER] section of the [Link] file, and that the appropriate permissions on the target
directory have been granted. In some cases, the problem can be resolved by simply starting
ssaserver again.

Error starting up
Explanation: An error occurred while starting ssaserver. Consult the description for the secondary error
message in this Appendix for more information.

Error transferring file 'file name'. Unknown error

Explanation: An ODBC-level error occurred during execution of a archived table query with an IN-file
clause. Refer to the secondary message for further information about the cause of the
problem.

Error transferring file 'file name'. Executor not ready

Explanation: There are currently no ssaagent processes running to handle archived table queries.

User Response: Start at least one ssaagent process, and then execute the query again.

Error transferring file 'file name'. File transfer output queue corrupted

Explanation: An internal error occurred during execution of a archived table query with an IN-file clause.

User Response: Attempt the query again. If the error persists, contact Informatica Global Customer Support.

Error transferring file 'file name'. Invalid BETWEEN clause: different operand types

Explanation: The query contains a BETWEEN clause that either specifies a range between operands of
incompatible datatypes, or the range datatype is incompatible with that of the value under
consideration.

User Response: Ensure that numeric and character values are not being mixed together in the BETWEEN
clause.

Error transferring file 'file name'. Invalid constant: x

Explanation: The query contains an invalid constant, for example, a string literal where a number is
expected.

User Response: Correct and re-submit the query.

Error transferring file 'file name'. Invalid execution route: Files from the client site have not been transferred

Explanation: An internal error occurred during execution of a archived table query with an IN-file clause.

User Response: Attempt the query again. If the error persists, contact Informatica Global Customer Support.

Error transferring file 'file name'. Invalid Expression

Explanation: The query contains an invalid expression. Correct the SQL statement before attempting the
operation again.

Error transferring file 'file name'. invalid IN clause: different operand types

Load Balancer and File Archive Administration Utility errors 33

 Explanation: The query contains an IN clause where a value of one datatype or domain is tested for
membership in data of another, incompatible datatype or domain.

Error transferring file 'file name'. Invalid INI file: Invalid [META] specification.

Explanation: The [META] section in the [Link] file contains invalid entries.

User Response: Ensure that the information in the [Link] file is correct before attempting to restart ssaserver.

Error transferring file 'file name'. Invalid INI file: Invalid [SERVER] specification.

Explanation: The [SERVER] section in the [Link] file contains invalid entries.

User Response: Ensure that the information in the [Link] file is correct before attempting to restart ssaserver.

Error transferring file 'file name'. invalid LIKE clause: different operand types

Explanation: The query contains a LIKE clause where a non-character value is being compared to the
pattern string. The LIKE clause can evaluate only character data.

Error transferring file 'file name'. invalid LIKE clause: not string operand

Explanation: The query contains a LIKE clause where the pattern string argument consists of a non-string
literal. The LIKE clause can evaluate only character data.

Error transferring file 'file name'. Invalid LIKE operator format

Explanation: The query contains an invalid LIKE clause.

User Response: Correct the SQL statement before attempting the operation again.

Error transferring file 'file name'. Operator operator not operable with type1, type2, ...

Explanation: The specified operator cannot be used with the specified datatypes. For example, an
arithmetic operator such as + cannot be used with character data: 'a' + 'b'.

Error transferring file 'file name'. Query was terminated

Explanation: The query was cancelled by a user.

Error transferring file 'file name'. read/write operation failed

Explanation: A read or write operation could not be performed.

User Response: Attempt the operation again, possibly after restarting ssaserver and File Archive repository
database. If the problem persists, contact Informatica Global Customer Support for
assistance.

Error transferring file 'file name'. Row too long

Explanation: A fetched row exceeds the size of the buffer created to hold it. This might occur if an SCT file
was registered with the File Archive repository, then the associated table was redefined such
that a column length is smaller than it was.

User Response: The column will have to be restored to its original definition before it can be queried
successfully.

34 Chapter 3: Load Balancer and Administration Errors

Error transferring file 'file name'. Table table-name : error retrieving number of columns

Explanation: The SCT file being queried contains invalid header information.

User Response: This SCT file might have to be recreated.

Error transferring file 'file name'. Two or more source files with the same name in IN <file> clauses

Explanation: Each file name specified in IN-file clauses in the same query must be unique, even if the files
have different locations.

Error transferring file 'file name'. Unexpected message # transferring file 'file-name'

Explanation: An internal error occurred during execution of a archived table query with an IN-file clause.

User Response: Attempt the query again. If the error persists, contact Informatica Global Customer Support.

Error transferring file 'file name'. Unknown column column-name

Explanation: An internal error occurred: A column specified in the query does not have a domain
associated with it.

Error transferring file 'file name'. Unsupported LIKE form

Explanation: The query contains an unsupported LIKE clause.

User Response: Correct the SQL statement, and then attempt the operation again.

Error transferring file 'file name'. unsupported query form

Explanation: The query is not supported.

User Response: Ensure that the SQL statement is valid and can be executed against a archived table.

Error transferring file 'file name'. Wrong number of arguments for operation x (n is expected)

Explanation: An internal error occurred: A function in the query could not be processed correctly.

User Response: Attempt the operation again, possibly after restarting ssaserver and File Archive repository
database. If the problem persists, contact Informatica Global Customer Support.

Cannot create file: x

Explanation: The specified SCT file could not be created. This might occur if the current user does not
possess the required permissions on the target directory or file. If the SCT file already exists,
it might have been locked by another process.

Cannot mask SIGINT signal. Ctrl^C handler will not be installed.

Explanation: An internal error occurred: pressing <Ctrl+C> will not shut down the program.

User Response: It might be necessary to kill the Archive Administration utility process through the operating
system, if you wish to cancel program execution.

Cannot run Ctrl^C handling thread. Ctrl^C handler will not be installed.

Load Balancer and File Archive Administration Utility errors 35

 Explanation: An internal error occurred: pressing <Ctrl+C> will not shut down the program.

User Response: It might be necessary to kill the Archive Administration utility process through the operating
system, if you wish to cancel program execution.

Connection Error: n

Explanation: A connection error occurred while attempting to load file archive data into a SAND database.

User Response: Ensure that the database is currently running and is accessible through the network, and then
attempt the operation again.

Failed to allocate n bytes.

Explanation: The specified amount of memory required for the operation could not be allocated.

User Response: Try closing other running processes to free up some system memory, and then attempt the
operation again.

Invalid encryption key specified

Explanation: Returned when there is an attempt to open an encrypted SCT file using the wrong decryption
key.

Other ssaserver Messages

Connection error. details

Explanation: A connection could not be established with the File Archive repository database. Further
details about the error are provided by the secondary message (details).

Couldn't get the SCT-file column list. Reason: details

Explanation: An error occurred while attempting to retrieve column information from an SCT file. Further
details about the error are provided by the secondary message (details).

Couldn't get the SCT-file's list. Reason: details

Explanation: An error occurred while attempting to retrieve the list of SCT files registered with the File
Archive repository. Further details about the error are provided by the secondary message
(details).

DB general error. details

Explanation: An unspecified error occurred. Further details about the error are provided by the secondary
message (details).

Metadata structure is corrupted

36 Chapter 3: Load Balancer and Administration Errors

Explanation: Problems were encountered while attempting to access metadata structures in the
SDS_REPOSITORY schema in the File Archive repository database. At least one required
table is missing. Either a table was accidentally removed by a user, or an older version of the
File Archive repository database is being used with a newer release of SAND CDBMS
Nearline.

User Response: In the latter case, execute the ssamdtool -v command against the File Archive repository
database to upgrade the metadata structures. If a table was deleted by accident, the
metadata structures will have to be removed and recreated with ssamdtool, and the file
archive data will have to be registered again.

Metadata Synchronize - FAILED. Reason: details

Explanation: An error occurred while the metadata information in the File Archive repository was being
updated. Further details about the error are provided by the secondary message (details).

The connection to DB 'DB-name' has been lost.

Explanation: The client can no longer access the File Archive repository database. The potential cause of
this problem can be a client program error, a network problem, or the abnormal termination of
the Archive Administration utility running the File Archive repository database.

User Response: If necessary, close and restart the client program and the File Archive repository database.

Wasn't able to create Metadata. details

Explanation: The metadata structures could not be created in the database. Further details about the error
are provided by the secondary message (details).

Wasn't able to get next chunk of data. Reason: details

Explanation: An error occurred while retrieving data from the File Archive repository. Further details about
the error are provided by the secondary message (details).

Wasn't able to load Metadata or Metadata is incorrect. details

Explanation: The metadata information in the File Archive repository either could not be read into memory,
or is invalid. View the secondary message (details) for further details.

Wasn't able to open connection to 'connection:DB-name' for user 'user'. Reason: details

Explanation: The specified connection to the File Archive repository database could not be established.
View the secondary message (details) for further details.

Wasn't able to perform 'Execute' for next query x. Reason: details

Explanation: An internal error occurred. View the secondary message (details) for further details.

Wasn't able to perform 'SQL Execute Direct' for next query 'x'. Reason: details

Explanation: An internal error occurred. View the secondary message (details) for further details.

Wasn't able to perform 'SQL Prepare' for next query 'x'. Reason: details

Other ssaserver Messages 37

 Explanation: An internal error occurred. View the secondary message (details) for further details.

File Archive Repository Administration Exit Code Errors

The following exit codes might appear when you run ssadmtool.

ExitCode:-1 (General error)

Explanation: The current operation could not complete successfully.

User Response: Shut down the database, restart it, then attempt the operation again.

ExitCode:-2 (Command line error)

Explanation: An error occurred while parsing the command line parameters.

User Response: Please verify your parameters before re-attempting the command.

ExitCode:-10 (Create metadata error)

Explanation: The Create Metadata operation could not complete successfully. The metadata structures
may already exist in the target database.

User Response: Before attempting the operation again, ensure that the specified database is running, that the
maximum number of client sessions has not been reached, and that the access permissions
on the database have not been altered.

ExitCode:-11 (Remove metadata error)

Explanation: The Remove Metadata operation could not complete successfully.

User Response: Make sure that the database is running, that the maximum number of client sessions has not
been reached, and that the access permissions on the database have not been altered, then
attempt the operation again.

ExitCode:-12 (Clear metadata error)

Explanation: The Clear Metadata operation could not complete successfully. This message will be
returned if the specified database does not contain any metadata structures.

User Response: If there are metadata structures in the database, ensure that the database is running, that the
maximum number of client sessions has not been reached, and that the access permissions
on the database have not been altered, then attempt the operation again.

ExitCode:-18 (Wrong file data format)

Explanation: This message is returned if ssamdtool reaches the end of a file unexpectedly. If this error
occurs, re-attempt the operation.

38 Chapter 3: Load Balancer and Administration Errors

Load Balancer and File Archive Repository
Administration Errors
The following errors related to metadata might appear when you run the load balancer or File Archive repository
administration tool.

Couldn't find Metadata schema.

Explanation: There is no SDS_REPOSITORY schema in the File Archive repository database. This special
schema contains data structures that describe Archives registered with the database.

User Response: If the SDS_REPOSITORY schema and its objects have been dropped from the system, it will
be necessary to use ssamdtool or ssaserver to recreate the schema and metadata structures,
and then re-register the file archive data.

Metadata tables were not found or wrong version of Metadata.

Explanation: The SDS_REPOSITORY schema in the File Archive repository database does not contain
the required tables. These metadata tables store information about SCT files and archived
tables registered with the database, and must never be dropped manually from the system.

User Response: If an older version of the File Archive repository database is being used with a newer release
of SAND CDBMS Nearline, execute the ssamdtool -v command against the File Archive
repository database to upgrade the metadata structures. If this does not rectify the problem, it
might be necessary to use ssamdtool to remove the metadata structures, recreate them, and
then repopulate them with the previous SCT information.

Not all metadata tables were found or wrong version of Metadata.

Explanation: The SDS_REPOSITORY schema in the File Archive repository database does not contain all
of the required tables. These metadata tables store information about the archived tables
registered with the database, and must never be dropped manually from the system.

User Response: If an older version of the File Archive repository database is being used with a newer release
of SAND CDBMS Nearline, execute the ssamdtool -v command against the File Archive
repository database to upgrade the metadata structures. If this does not rectify the problem, it
might be necessary to use ssamdtool to remove the metadata structures, recreate them, and
then repopulate them with the previous SCT information.

The column 'column-name' has the invalid domain ID 'domain-ID'.

This domain ID is not present in the domain list associated with the file 'file-name'.
Explanation: An internal error occurred: an SCT file registered with the File Archive repository contains a
column with an invalid internal domain ID. This problem might have been caused when the
SCT file was created or registered with the File Archive repository.

User Response: In these situations, it might be necessary to recreate the SCT file and re-register the file with
the File Archive repository.

This problem might also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The column 'column-name' has the invalid file ID 'file-ID'. This file ID is not present in the file list.

Load Balancer and File Archive Repository Administration Errors 39

 Explanation: An internal error occurred: a archived table column registered with the File Archive repository
is associated with an invalid internal SCT file ID. This problem might have been caused when
the SCT file was created, registered with the File Archive repository, or when the archived
table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The columns 'column1' and 'column2' associated with the file 'file-name' have the same ID 'column-ID'.

Explanation: An internal error occurred: a pair of columns in a archived table registered with the File
Archive repository have the same internal column ID. This problem might have been caused
when the SCT file was created, registered with the File Archive repository, or when the
archived table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The domain 'domain-name' associated with the file 'file-name' should have at least one associated column.

Explanation: An internal error occurred: a domain associated with an SCT file registered with the system is
not used by any of the columns in the archived table. This problem might have been caused
when the SCT file was created, registered with the File Archive repository, or when the
archived table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The domain 'domain-name' has the invalid file ID 'file-ID'. This file ID is not present in the file list.

Explanation: An internal error occurred: a domain registered with the File Archive repository is associated
with an invalid SCT file ID. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the archived table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The domains “domain1” and 'domain2' associated with the file 'file-name' have the same ID 'domain-ID'.

40 Chapter 3: Load Balancer and Administration Errors

Explanation: An internal error occurred: a pair of domains associated with an SCT file registered with the
File Archive repository have the same internal domain ID. This problem might have been
caused when the SCT file was created, registered with the File Archive repository, or when
the archived table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The file 'file-name' has x associated domains and y associated columns.

The number of associated domains should be less than or equal to the number of referenced
columns.
Explanation: There are more domains than columns associated with an SCT file registered with the File
Archive repository. Since each domain must be associated with at least one column, this is
an internal error condition. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the archived table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The file 'file-name' has the invalid table ID 'table-ID'. This table ID is not present in the table list.

Explanation: An internal error occurred: an invalid internal table ID is associated with an SCT file
registered with the File Archive repository. This problem might have been caused when the
SCT file was created, registered with the File Archive repository, or when the archived table’s
metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The file 'file-name' should have at least one associated column.

Explanation: An internal error occurred: an SCT file registered with the File Archive repository does not
have any associated columns. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the archived table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Load Balancer and File Archive Repository Administration Errors 41

 The file 'file-name' should have at least one associated domain.

Explanation: An internal error occurred: an SCT file registered with the File Archive repository does not
have any associated domains. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the archived table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The files 'file1' and 'file2' have the same ID 'file-ID'.

Explanation: An internal error occurred: two SCT files registered with the File Archive repository have the
same internal file ID. This problem might have been caused when the SCT file was created,
registered with the File Archive repository, or when the archived table’s metadata was
exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The tables 'table1' and 'table2' have the same ID 'table-ID'.

Explanation: An internal error occurred: a pair of archived tables registered with the File Archive repository
have the same internal table ID. This problem might have been caused when the SCT file
was created, registered with the File Archive repository, or when the archived table’s
metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The value 'value' has the invalid column ID 'col-ID'.

This column ID is not present in the column list associated with the file 'file-name'.
Explanation: An internal error occurred: a minimum and maximum value in an SCT file registered with the
File Archive repository is associated with an invalid internal column ID. This problem might
have been caused when the SCT file was created, registered with the File Archive repository,
or when the archived table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

42 Chapter 3: Load Balancer and Administration Errors

The value 'value' has the invalid file ID 'file-ID'. This file ID is not present in the file list.

Explanation: An internal error occurred: a minimum and maximum value in a column registered with the
File Archive repository is associated with an invalid SCT file ID. This problem might have
been caused when the SCT file was created, registered with the File Archive repository, or
when the archived table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The values 'value1' and 'value2' associated with the file 'file-name' and column 'column-name' are the same.

Explanation: An internal error occurred: a pair of minimum and maximum values for an SCT file registered
with the File Archive repository have the same metadata information. This problem might
have been caused when the SCT file was created, registered with the File Archive repository,
or when the archived table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Columns (ID1='col-ID1', ID2='col-ID2') associated with file 'file-name' and 'domain-name' have the different type
descriptions.

Explanation: An internal error occurred: a pair of columns from the same SCT file registered with the File
Archive repository, and associated with the same domain, have different datatypes. This
problem might have been caused when the SCT file was created, registered with the File
Archive repository, or when the archived table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Two columns (ID1='col-ID1', ID2='col-ID2') associated with the file 'file-name' have the same name 'column-name'.

Explanation: An internal error occurred: a pair of columns from the same SCT file registered with the File
Archive repository have the same column name. This problem might have been caused when
the SCT file was created, registered with the File Archive repository, or when the archived
table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Load Balancer and File Archive Repository Administration Errors 43

 Two domains (ID1='domain-ID1', ID2='domain-ID2') associated with the file 'file-name' have the same name 'domain-
name'.

Explanation: An internal error occurred: two domains from the same SCT file registered with the File
Archive repository have the same domain name. This problem might have been caused when
the SCT file was created, registered with the File Archive repository, or when the archived
table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Two tables (ID1='table-ID1', ID2='table-ID2') have the same name 'table-name'.

Explanation: An internal error occurred: a pair of archived tables registered with the File Archive repository
have the same table name. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the archived table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and re-register the file with the File Archive repository.

Explanation: This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

One or more items in the sequence are missing.

The next value after the missing ones is described below. The value 'value-name' associated
with the file 'file-name' and column 'column-name'.
Explanation: An internal error occurred.

User Response: This problem can be safely ignored, as it does not affect normal functioning of SAND CDBMS
Nearline.

WARNING: Two files (ID1='file-ID1', ID2='file-ID2') have the same name 'file-name'.

Explanation: A pair of SCT files registered with the File Archive repository have the same file name. One
of the file entries will be ignored.

This problem could have been caused when an SCT file was registered with the File Archive
repository. The problem could also have occurred if the metadata information in the
SDS_REPOSITORY schema was manually changed. The tables in the SDS_REPOSITORY
schema must never be altered by users, as this can corrupt the metadata and render
archived tables inaccessible.

44 Chapter 3: Load Balancer and Administration Errors

Rule Engine Messages
The following messages might appear when you run Column Rules, Filter Rules, or File Scopes.

Applying column rules to the user query - FAILED. message

Explanation: An error occurred while executing a Column Rule.

User Response: View the secondary message that accompanies this error for more details.

Collision encountered.
FileID(n): According to the column rules the column 'column-name' was replaced with 'NULL',
but this column has 'NOT NULL' constraint.
Explanation: This error is returned when a Column Rule attempts to set a column with a NOT NULL
constraint to null. The Column Rule must be deleted, or else the NOT NULL constraint should
be removed from the archived table column.

Collision encountered. FileID(n).

Found missing column 'column-name', this column has 'NOT NULL' constraint, no column
rules found for this instance. It is impossible to replace this column with 'NULL'.
Explanation: This error is returned when a column missing from an SCT file has a NOT NULL constraint
defined on it. By default, a missing column is set to null, but if the column is defined as NOT
NULL, this error will be generated instead.

User Response: To avoid this error, create a Column Rule that will set this column to a value other than null.

Couldn't build the column rules query.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't build the file scope query.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't build the SCT-file column query.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't build the SCT-file preference's query.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't build the SCT-file query.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Rule Engine Messages 45

 Couldn't build the SCT-file value query.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't get the MD column rules list.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't get the MD column's list.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't get the MD file priority's list.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't get the MD file scope list.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't get the MD file's list.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

Couldn't get the MD value's list.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

FileID(n): Column 'column-name' from Column Rule was not found in the column list of current file.

Explanation: The Column Rule being applied specifies a column that does not exist in the archived table.
The error message includes the internal ID of the affected SCT file.

FileID(n): Cannot sort the list of 'Column Rules' based on their dependencies.
In most cases it means interdependencies between 2 or more columns.
Explanation: A pair of Column Rules are mutually dependent, and cannot be reconciled. For example,
Column Rule #1 sets column A based on column B, while Column Rule #2 sets column B
based on column A. One of the conflicting Column Rules will have to be removed in order to
allow the query to execute. Note that the error message includes the internal ID of the
affected SCT file.

46 Chapter 3: Load Balancer and Administration Errors

Parsing of the column rule expressions - FAILED <message>

Explanation: The Column Rule expression contains invalid syntax.

User Response: View the secondary message that accompanies this error for more details.

Parsing of WHERE clause in user query - FAILED. <message>

Explanation: An internal error occurred. View the error code and secondary message that accompanies
this error for more details.

User Response: Contact Informatica Global Customer Support if the problem persists.

Preparing WHERE expression for evaluation - FAILED. <message>

Explanation: An internal error occurred. View the secondary message that accompanies this error for more
details.

User Response: Contact Informatica Global Customer Support if the problem persists.

query.BuildSCTFileQuery_WhereClause - FAILED.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

ruleEngine.Check_File() - FAILED. <message>

Explanation: An internal error occurred.

User Response: View the secondary message that accompanies this error for more details. Contact
Informatica Global Customer Support if the problem persists.

The column rule expression type is wrong. (expression)

Explanation: The Column Rule expression returns a Boolean value (TRUE or FALSE). Column Rule
expressions must result in a datatype, one that is compatible with the column to which the
Column Rule is applied.

The table 'table-name' wasn't found among the registered tables.

Explanation: An internal error occurred.

User Response: Contact Informatica Global Customer Support if the problem persists.

There are incompatible datatypes between the expression and the column.
The column rule (ID= n, Expression: expression= y). The column 'column-name' has
<datatype> datatype. The expression 'expression' has <datatype> datatype.
Explanation: The Column Rule expression returns a datatype that is incompatible with the column to which
the Column Rule is applied. The error message includes the Column Rule internal ID (n), the
Column Rule column assignment expression (y), the column and its datatype, and the value
expression and its datatype.

Unknown column 'column-name'.

Rule Engine Messages 47

 Explanation: The File Scope used by the Column Rule references an unknown field in its Boolean
expression. The File Scope expression can reference columns only from the SDS_FILE table
in the File Archive repository database.

Wrong expression type.

Explanation: The expression in the File Scope used by the Column Rule is not a Boolean expression. The
File Scope expression must return a TRUE or FALSE value when evaluated against each
registered SCT file; it cannot return a number or a character string.

48 Chapter 3: Load Balancer and Administration Errors

CHAPTER 4

ssamdtool Errors
This chapter includes the following topics:

¨ Ssamdtool Exit Code Errors, 49

¨ Metadata Service Errors (Ssaserver, Ssamdtool, and the MDAdmin GUI) , 50

¨ Rule Engine Errors (Column Rules, Filter Rules, and File Scopes), 55

Ssamdtool Exit Code Errors

ExitCode: -1 (General error)

Explanation: The current operation could not complete successfully.

User Response: Shut down the database, restart it, then attempt the operation again.

ExitCode: -2 (Command line error)

Explanation: An error occurred while parsing the command line parameters.

User Response: Please verify your parameters before re-attempting the command.

ExitCode: -10 (Create metadata error)

Explanation: The Create Metadata operation could not complete successfully. The metadata structures
may already exist in the target database.

User Response: Before attempting the operation again, ensure that the specified database is running, that the
maximum number of client sessions has not been reached, and that the access permissions
on the database have not been altered.

ExitCode: -11 (Remove metadata error)

Explanation: The Remove Metadata operation could not complete successfully.

User Response: Make sure that the database is running, that the maximum number of client sessions has not
been reached, and that the access permissions on the database have not been altered, then
attempt the operation again.

ExitCode: -12 (Clear metadata error)

49
 Explanation: The Clear Metadata operation could not complete successfully. This message will be
returned if the specified database does not contain any metadata structures.

User Response: If there are metadata structures in the database, ensure that the database is running, that the
maximum number of client sessions has not been reached, and that the access permissions
on the database have not been altered, then attempt the operation again.

ExitCode: -18 (Wrong file data format)

Explanation: This message is returned if ssamdtool reaches the end of a file unexpectedly. If this error
occurs, re-attempt the operation.

Metadata Service Errors (Ssaserver, Ssamdtool, and

the MDAdmin GUI)
Couldn't find Metadata schema.

Explanation: There is no SDS_REPOSITORY schema in the File Archive repository database. This special
schema contains data structures that describe Archives registered with the database.

User Response: If the SDS_REPOSITORY schema and its objects have been dropped from the system, it will
be necessary to use ssamdtool or ssaserver to recreate the schema and metadata structures,
and then re-register the file arachive data.

Metadata tables were not found or wrong version of Metadata.

Explanation: The SDS_REPOSITORY schema in the File Archive repository database does not contain
the required tables. These metadata tables store information about SCT files and archived
registered with the database, and must never be dropped manually from the system.

User Response: If an older version of the File Archive repository database is being used with a newer release
of SAND CDBMS Nearline, execute the ssamdtool -v command against the File Archive
repository database to upgrade the metadata structures. If this does not rectify the problem, it
might be necessary to use ssamdtool to remove the metadata structures, recreate them, and
then repopulate them with the previous SCT information.

Not all metadata tables were found or wrong version of Metadata.

Explanation: The SDS_REPOSITORY schema in the File Archive repository database does not contain all
of the required tables. These metadata tables store information about the archived tables
registered with the database, and must never be dropped manually from the system.

User Response: If an older version of the File Archive repository database is being used with a newer release
of SAND CDBMS Nearline, execute the ssamdtool -v command against the File Archive
repository database to upgrade the metadata structures. If this does not rectify the problem, it
might be necessary to use ssamdtool to remove the metadata structures, recreate them, and
then repopulate them with the previous SCT information.

The column 'column-name' has the invalid domain ID 'domain-ID'.

This domain ID is not present in the domain list associated with the file 'file-name'.

50 Chapter 4: ssamdtool Errors

Explanation: An internal error occurred: an SCT file registered with the File Archive repository contains a
column with an invalid internal domain ID. This problem might have been caused when the
SCT file was created or registered with the File Archive repository.

User Response: In these situations, it might be necessary to recreate the SCT file and/or re-register the file
with the File Archive repository.

This problem might also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The column 'column-name' has the invalid file ID 'file-ID'. This file ID is not present in the file list.

Explanation: An internal error occurred: a compacted table column registered with the File Archive
repository is associated with an invalid internal SCT file ID. This problem might have been
caused when the SCT file was created, registered with the File Archive repository, or when
the compacted table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The columns 'column1' and 'column2' associated with the file 'file-name' have the same ID 'column-ID'.

Explanation: An internal error occurred: a pair of columns in a compacted table registered with the File
Archive repository have the same internal column ID. This problem might have been caused
when the SCT file was created, registered with the File Archive repository, or when the
compacted table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The domain 'domain-name' associated with the file 'file-name' should have at least one associated column.

Explanation: An internal error occurred: a domain associated with an SCT file registered with the system is
not used by any of the columns in the compacted table. This problem might have been
caused when the SCT file was created, registered with the File Archive repository, or when
the compacted table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The domain 'domain-name' has the invalid file ID 'file-ID'. This file ID is not present in the file list.

Metadata Service Errors (Ssaserver, Ssamdtool, and the MDAdmin GUI) 51

 Explanation: An internal error occurred: a domain registered with the File Archive repository is associated
with an invalid SCT file ID. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the compacted table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The domains “domain1” and 'domain2' associated with the file 'file-name' have the same ID 'domain-ID'.

Explanation: An internal error occurred: a pair of domains associated with an SCT file registered with the
File Archive repository have the same internal domain ID. This problem might have been
caused when the SCT file was created, registered with the File Archive repository, or when
the compacted table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The file 'file-name' has x associated domain(s) and y associated column(s).

The number of associated domains should be less than or equal to the number of referenced
columns.
Explanation: There are more domains than columns associated with an SCT file registered with the File
Archive repository. Since each domain must be associated with at least one column, this is
an internal error condition. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the compacted table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The file 'file-name' has the invalid table ID 'table-ID'. This table ID is not present in the table list.

Explanation: An internal error occurred: an invalid internal table ID is associated with an SCT file
registered with the File Archive repository. This problem might have been caused when the
SCT file was created, registered with the File Archive repository, or when the compacted
table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

52 Chapter 4: ssamdtool Errors

The file 'file-name' should have at least one associated column.

Explanation: An internal error occurred: an SCT file registered with the File Archive repository does not
have any associated columns. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the compacted table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The file 'file-name' should have at least one associated domain.

Explanation: An internal error occurred: an SCT file registered with the File Archive repository does not
have any associated domains. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the compacted table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The files 'file1' and 'file2' have the same ID 'file-ID'.

Explanation: An internal error occurred: two SCT files registered with the File Archive repository have the
same internal file ID. This problem might have been caused when the SCT file was created,
registered with the File Archive repository, or when the compacted table’s metadata was
exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The tables 'table1' and 'table2' have the same ID 'table-ID'.

Explanation: An internal error occurred: a pair of archived tables registered with the File Archive repository
have the same internal table ID. This problem might have been caused when the SCT file
was created, registered with the File Archive repository, or when the compacted table’s
metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The value 'value' has the invalid file ID 'file-ID'. This file ID is not present in the file list.

Metadata Service Errors (Ssaserver, Ssamdtool, and the MDAdmin GUI) 53

 Explanation: An internal error occurred: a minimum/maximum value in a column registered with the File
Archive repository is associated with an invalid SCT file ID. This problem might have been
caused when the SCT file was created, registered with the File Archive repository, or when
the compacted table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

The values 'value1' and 'value2' associated with the file 'file-name' and column 'column-name' are the same.

Explanation: An internal error occurred: a pair of minimum/maximum values for an SCT file registered with
the File Archive repository have the same metadata information. This problem might have
been caused when the SCT file was created, registered with the File Archive repository, or
when the compacted table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Two columns (ID1='col-ID1', ID2='col-ID2') associated with the file 'file-name' have the same name 'column-name'.

Explanation: An internal error occurred: a pair of columns from the same SCT file registered with the File
Archive repository have the same column name. This problem might have been caused when
the SCT file was created, registered with the File Archive repository, or when the compacted
table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Two domains (ID1='domain-ID1', ID2='domain-ID2') associated with the file 'file-name' have the same name 'domain-
name'.

Explanation: An internal error occurred: two domains from the same SCT file registered with the File
Archive repository have the same domain name. This problem might have been caused when
the SCT file was created, registered with the File Archive repository, or when the compacted
table’s metadata was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

Two tables (ID1='table-ID1', ID2='table-ID2') have the same name 'table-name'.

54 Chapter 4: ssamdtool Errors

 Explanation: An internal error occurred: a pair of archived tables registered with the File Archive repository
have the same table name. This problem might have been caused when the SCT file was
created, registered with the File Archive repository, or when the compacted table’s metadata
was exported to an XML file.

User Response: In these situations, it might be necessary to recreate the SCT file, export the metadata to
XML again, and/or re-register the file with the File Archive repository.

This problem can also occur if the metadata information in the SDS_REPOSITORY schema
was manually changed. The tables in the SDS_REPOSITORY schema must never be altered
by users, as this can corrupt the metadata and render archived tables inaccessible.

One or more items in the sequence are missing.

The next value after the missing one(s) is described below. The value 'value-name' associated
with the file 'file-name' and column 'column-name'.
Explanation: An internal error occurred.

User Response: This problem can be safely ignored, as it does not affect normal functioning of SAND CDBMS
Nearline.

WARNING: Two files (ID1='file-ID1', ID2='file-ID2') have the same name 'file-name'.

Explanation: A pair of SCT files registered with the File Archive repository have the same file name. One
of the file entries will be ignored.

This problem could have been caused when an SCT file was registered with the File Archive
repository. The problem could also have occurred if the metadata information in the
SDS_REPOSITORY schema was manually changed. The tables in the SDS_REPOSITORY
schema must never be altered by users, as this can corrupt the metadata and render
archived tables inaccessible.

Rule Engine Errors (Column Rules, Filter Rules, and

File Scopes)
Applying column rules to the user query - FAILED. message

Explanation: An error occurred while executing a Column Rule.

User Response: View the secondary message that accompanies this error for more details. Note that some of
the secondary messages are described below.

Collision encountered.
FileID(n): According to the column rules the column 'column-name' was replaced with 'NULL',
but this column has 'NOT NULL' constraint.
Explanation: This error is returned when a Column Rule attempts to set a column with a NOT NULL
constraint to null. The Column Rule must be deleted, or else the NOT NULL constraint should
be removed from the compacted table column.

Rule Engine Errors (Column Rules, Filter Rules, and File Scopes) 55
 Collision encountered.
FileID(n): Found missing column 'column-name', this column has 'NOT NULL' constraint, no
column rules found for this instance. It is impossible to replace this column with 'NULL'.
Explanation: This error is returned when a column missing from an SCT file has a NOT NULL constraint
defined on it. By default, a missing column is set to null, but if the column is defined as NOT
NULL, this error will be generated instead.

User Response: To avoid this error, create a Column Rule that will set this column to a value other than null.

Couldn't build the column rules query.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't build the file scope query.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't build the SCT-file column query.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't build the SCT-file preference's query.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't build the SCT-file query.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't build the SCT-file value query.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't get the MD column rules list.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't get the MD column's list.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

56 Chapter 4: ssamdtool Errors

Couldn't get the MD file priority's list.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't get the MD file scope list.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't get the MD file's list.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

Couldn't get the MD value's list.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

FileID(n): Column 'column-name' from Column Rule was not found in the column list of current file.

Explanation: The Column Rule being applied specifies a column that does not exist in the compacted
table. The error message includes the internal ID of the affected SCT file.

FileID(n): Cannot sort the list of 'Column Rules' based on their dependencies.
In most cases it means interdependencies between 2 or more columns.
Explanation: A pair of Column Rules are mutually dependent, and cannot be reconciled. For example,
Column Rule #1 sets column A based on column B, while Column Rule #2 sets column B
based on column A. One of the conflicting Column Rules will have to be removed in order to
allow the query to execute. Note that the error message includes the internal ID of the
affected SCT file.

Parsing of the column rule expressions - FAILED <message>

Explanation: The Column Rule expression contains invalid syntax.

User Response: View the secondary message that accompanies this error for more details.

Parsing of the column rule expressions - FAILED message

Explanation: The Column Rule expression contains invalid syntax.

User Response: View the secondary message that accompanies this error for more details.

Parsing of WHERE clause in user query - FAILED. <message>

Explanation: An internal error occurred. View the error code and secondary message that accompanies
this error for more details.

User Response: Contact Informatica Global Customer Support if the problem persists.

Rule Engine Errors (Column Rules, Filter Rules, and File Scopes) 57
 Parsing of WHERE clause in user query - FAILED. error-number message

Explanation: An internal error occurred. View the error code and secondary message that accompanies
this error for more details.

User Response: Contact a SAND support representative if the problem persists.

Preparing WHERE expression for evaluation - FAILED. <message>

Explanation: An internal error occurred. View the secondary message that accompanies this error for more
details.

User Response: Contact Informatica Global Customer Support if the problem persists.

Preparing WHERE expression for evaluation - FAILED. message

Explanation: An internal error occurred. View the secondary message that accompanies this error for more
details.

User Response: Contact a SAND support representative if the problem persists.

query.BuildSCTFileQuery_WhereClause - FAILED.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

ruleEngine.Check_File() - FAILED. <message>

Explanation: An internal error occurred.

User Response: View the secondary message that accompanies this error for more details. Contact
Informatica Global Customer Support if the problem persists.

ruleEngine.Check_File() - FAILED. message

Explanation: An internal error occurred.

User Response: View the secondary message that accompanies this error for more details. Contact a SAND
support representative if the problem persists.

The column rule expression type is wrong. (expression)

Explanation: The Column Rule expression returns a Boolean value (TRUE or FALSE). Column Rule
expressions must result in a datatype, one that is compatible with the column to which the
Column Rule is applied.

The table 'table-name' wasn't found among the registered tables.

Explanation: An internal error occurred.

User Response: Contact a SAND support representative if the problem persists.

There are incompatible datatypes between the expression and the column.
The column rule (ID= n, Expression: expression= y). The column 'column-name' has data-type
datatype. The expression 'expression' has data-type datatype.

58 Chapter 4: ssamdtool Errors

Explanation: The Column Rule expression returns a datatype that is incompatible with the column to which
the Column Rule is applied. The error message includes the Column Rule internal ID (n), the
Column Rule column assignment expression (y), the column and its datatype, and the value
expression and its datatype.

Unknown column 'column-name'.

Explanation: The File Scope used by the Column Rule references an unknown field in its Boolean
expression. The File Scope expression can reference columns only from the SDS_FILE table
in the File Archive repository database.

Wrong expression type.

Explanation: The expression in the File Scope used by the Column Rule is not a Boolean expression. The
File Scope expression must return a TRUE or FALSE value when evaluated against each
registered SCT file; it cannot return a number or a character string.

Rule Engine Errors (Column Rules, Filter Rules, and File Scopes) 59
CHAPTER 5

File Archive SQL Tool Messages

This chapter includes the following topic:

¨ File Archive SQL Tool Messages, 60

File Archive SQL Tool Messages

This section lists the error messages that may be returned by the File Archive SQL tool (ssasql), the File Archive
Loader program (ssadl), ODBC, or any graphical user interface client application. Each message is accompanied
by a description of the circumstances under which the message might be issued, along with some recommended
course of action.

08001 Unable to establish connection. Connection timed out

Explanation: The client could not connect to the File Archive Repository Service host.

User Response: A connection could not be established with the File Archive Repository Service before a user-
defined timeout limit was reached.

08001 Unable to establish connection. Could not find configuration file

Explanation: The client-side [Link] file could not be located. It must reside in the SAND CDBMS
Nearline support directory, as specified in the NUCLEUS environment variable.

08001 Unable to establish connection. Could not find keyword [<keyword>] in configuration settings

Explanation: The Host and Port parameters for the specified CONNECTION could not be found in either
the [Link] file or the NUCLEUS environment variable.

User Response: Ensure that these parameters have been set before attempting to connect again.

08001 Unable to establish connection. Could not find section [<section>] in configuration file

Explanation: The specified CONNECTION does not have a corresponding section in the client-side
[Link] file.

User Response: Make sure the same connection information used to start the File Archive Repository Service
is contained in the client-side [Link] file.

08001 Unable to establish connection. Could not open configuration file

Explanation: The client program could not open the client-side [Link] file for reading.

60
User Response: Ensure that the client user has the required access permissions, and that no other program
has an exclusive lock on the [Link] file.

08001 Unable to establish connection. Could not reach host: “<host-name>”

Explanation: This message is returned if the File Archive Repository Service host cannot be reached.

User Response: Ensure that the server machine is running and is connected to the network, and that its IP
address, as well as the network routes between the server and the client computer, are valid.

08001 Unable to establish connection. Could not reach server at “<host-name>” : <port>

Explanation: The client could not reach the server through the specified port and timed out after the
default 120 seconds.

User Response: Make sure that the correct Port value is specified for the CONNECTION in the client-side
[Link] file, and that the File Archive Repository Service is running and accepting
connections on that port.

08001 Unable to establish connection. Could not resolve host name: “<host-name>”

Explanation: The Host specified by the CONNECTION was not found on the network. Typically, this error
is caused by a misspelled host name in the client-side [Link] file.

User Response: Verify that the appropriate Host parameter value is correct.

08001 Unable to establish connection. Invalid connection information

Explanation: An unexpected error involving the connection information has occurred. Contact Informatica
Global Customer Support for assistance.

08001 Unable to establish connection. Invalid connection information: connection name missing

Explanation: The connection name was not supplied with the connection request.

User Response: Ensure that the ODBC connection string contains “CONNECTION=<connection-name>”,
where connection-name is the CONNECTION used to start ssaeng.

08001 Unable to establish connection. Invalid connection information: database name missing

Explanation: The database name was not supplied with the connection request.

User Response: Ensure that the ODBC connection string contains “DATABASE=<database-name>”, where
database-name is the database started with ssaeng.

08001 Unable to establish connection. Invalid connection information: server host name missing

Explanation: The Host parameter for the specified CONNECTION is either missing from the client-side
[Link] file or empty.

User Response: This parameter must be defined, and must indicate the machine where ssaeng is running.

08001 Unable to establish connection. Invalid connection information: server port missing

Explanation: The Port parameter for the specified CONNECTION is either missing from the client-side
[Link] file or empty.

File Archive SQL Tool Messages 61

 User Response: This parameter must be defined, and must indicate the port number on which ssaeng is
accepting connections.

08001 Unable to establish connection. Invalid connection information: user name missing

Explanation: The client attempted to connect to ssaeng without specifying a user name.

08001 Unable to establish connection. Invalid value in configuration settings: <keyword>

Explanation: The indicated parameter specifies an inappropriate value (for example, a character string
instead of a number) in either the NUCLEUS environment variable or the [Link] file.

08001 Unable to establish connection. Network error

Explanation: A network subsystem problem is preventing the client from establishing a connection with
ssaeng.

User Response: Contact your network administrator for assistance.

08001 Unable to establish connection. Network is down

Explanation: The client computer is not connected to the network, or the client computer network settings
are not configured properly.

08001 Unable to establish connection. Operation was cancelled

Explanation: The user cancelled the connection request.

08001 Unable to establish connection. Syntax error in configuration settings

Explanation: Invalid syntax was found in the [Link] file or NUCLEUS environment variable.

User Response: Verify the correctness of the configuration settings before attempting to connect again. Make
sure that each parameter value contained in quotes has both starting and closing quotation
marks.

08003 Connection is closed

Explanation: This message is displayed if the client sends requests to the File Archive Repository Service
(ssaeng) after the client has been disconnected (see error 08S01 below).

User Response: A new connection will have to be establish with the server.

08004 Server refused connection. Database is locked by <user-name>@<host-name>

Explanation: This message appears when the client attempts to connect to a database that another user
has locked in exclusive mode through the SET TRANSACTION...ISOLATION LEVEL
EXCLUSIVE [IMMEDIATE] command.

08004 Server refused connection. Maximum number of sessions reached

Explanation: This message appears when the client attempts to connect to the File Archive Repository
Service (ssaeng) after the maximum number of client connections has been reached.

62 Chapter 5: File Archive SQL Tool Messages

User Response: Try connecting to the server at a later time or during off-peak hours. The database
administrator can also increase the maximum number of concurrent client connections by
changing the MaxUsers parameter in the CONNECTION section of the server side
[Link] configuration file.

08004 Server refused [Link] user name and password

Explanation: Either the client attempted to connect to the File Archive Repository Service (ssaeng) using
an invalid user authorization name or password or both, or else the connection name
specified in the connection request did not match the one used to start ssaeng. The second
case occurs only when the connection name invoked by the client is defined in the client-side
[Link] file with the same host name and port used by ssaeng. If necessary, edit the
[Link] file so that the connection name corresponds to the one used to start the
database instance.

08007 Connection terminated: database in exclusive mode

Explanation: The client connection was closed after the database was locked in exclusive mode through
another user’s execution of the SET TRANSACTION...ISOLATION LEVEL EXCLUSIVE
[IMMEDIATE] command.

User Response: A connection cannot be reestablished until the database is unlocked.

0800S Communication version mismatch

Explanation: This message is returned when the client program attempts to establish a connection with an
incompatible version of the File Archive Repository Service (ssaeng).

User Response: Ensure that the client program is compatible with ssaeng before re-attempting a connection.
You may be required to upgrade or reinstall SAND CDBMS Nearline.

0801S Communication media error. Link severed

Explanation: This error is returned when the File Archive Repository Service (ssaeng) shuts down while
the client is still connected. Any uncommitted database changes made through the client will
be rolled back.

User Response: You will have to wait until the database server is restarted before attempting to establish a
new connection.

0802S Communication packet too large

Explanation: The amount of data that the File Archive Repository Service (ssaeng) is attempting to send
the client is too large for the ssaeng send buffer. This might occur if the server was sent a
query expression that joins many long-named columns or a number of BLOB columns.

User Response: If possible, simplify the query, or utilize views that deal with a subset of the columns.

File Archive SQL Tool Messages 63

 37000 Escape error
Explanation: The client program has supplied an invalid escape code or escape code value.

Note: that the escape codes supported by the Nucleus ODBC Driver are the following:

¨ d (date)

¨ t (time)

¨ ts (timestamp)

¨ ESCAPE (escape)

¨ FN (scalar function)

¨ OJ (outer join)

37000 Parser error

Explanation: The client program has supplied a character string or identifier that is missing a closing
quotation mark. See related messages for more in the following text.

HY000 General error

Explanation: Many different error conditions can produce this message.

User Response: View the supplemental message for additional information about the source of the error.

HY001 Memory allocation error

Explanation: There is insufficient memory available on the client-side machine.

User Response: Free up some memory by terminating other programs, and then execute the last command
again.

HY018 Server refused cancel

Explanation: This message is returned when the client attempts to cancel a Data Definition Language
(DDL) command. Only non-DDL SQL commands can be cancelled.

Q0200 Shutdown already in progress

Explanation: A second SHUTDOWN command was sent to the File Archive Repository Service (ssaeng),
for example, after a SHUTDOWN DEFERRED statement had already been issued.

User Response: The server will continue to process the original SHUTDOWN instruction, and will return this
error for all subsequent SHUTDOWN commands.

Q0301 Server error: Memory allocation

Explanation: The File Archive Repository Service (ssaeng) has run out of memory and cannot process the
last client request.

User Response: All future client requests will generate this message as well, until sufficient memory is freed
up on the server machine.

Q0302 Server error: Maximum number of queries already allocated for user
Explanation: This message is returned when the current user has reached the maximum number of
concurrent queries allowed by the connection (by default, 128) and then attempts to execute
one more.

64 Chapter 5: File Archive SQL Tool Messages

User Response: If required, increase the maximum number of queries by changing the MaxQueries setting for
the connection in the server-side [Link] file.

File Archive SQL Tool Messages 65

APPENDIX A

File Archive Loader Messages

This appendix includes the following topics:

¨ File Archive Loader Messages Overview, 66

¨ Messages and Prompts, 66

¨ Load Operation Error Messages, 68

¨ File Parsing Messages, 77

File Archive Loader Messages Overview

This document lists and describes the errors that can be returned when using the File Archive Loader (ssadl) to
import or export data to or from a SAND database or SCT file. The error messages are divided into three
categories:

¨ messages and prompts (messages and prompts displayed during or immediately following a load operation)

¨ load-time errors and warnings (errors and warnings returned during a load operation)

¨ load specification script errors (errors related to the parsing of a load specification file).

Most of the entries describe the conditions that might generate the specified error, as well as possible resolutions
to the problem.

Messages and Prompts

The following messages and prompts might appear when you run ssadl.

n rows rejected by PICTURE

Explanation: ssadl displays this message during a load operation to indicate the number of rows that did
not satisfy the filter conditions in the PIC clause. In the case of an import, these rejected
records are saved to a file named [Link] (where input-file-name is the name of
the source data file).

n rows rejected by SKIPIF

66
Explanation: ssadl displays this message during a load operation to indicate the number of rows that
satisfied the filter conditions in the SKIPIF clause. These skipped records are saved to a user-
specified file, or if no file name was provided in the SKIPIF clause, to a file called
[Link] (where specification-file-name is the name of the load
specification file).

A Selected column was not specified in the record spec

Explanation: This message is displayed when an EXPORT operation SELECT statement specifies a
column that is not defined in the RECORD section. Each column referenced in the SELECT
statement must have a corresponding field definition in the record specification area.

EXECSQL error with row n

Explanation: This message is displayed when a specification file executing the EXECSQL command
contains an erroneous SQL statement. This message will also display the error message
returned from the server and the SQL statement with the error.

Insufficient resources - DATA segment size limit is: n

Explanation: This message is displayed because the operating system's data segment maximum size (n)
is too low for ssadl to operate.

User Response: The data segment size must be set to at least 1,048,576 KB. This can be accomplished with
the ulimit -d system command.

Insufficient resources - number of file descriptors limit is: n

Explanation: This message is displayed because the operating system's maximum number of file
descriptors (n) is too low for ssadl to operate.

User Response: The maximum number of file descriptors must be set to at least 256. This can be
accomplished with the ulimit -n system command.

Invalid encryption key format or encryption option specified in the script.

Explanation: Returned by the loader when attempting to create or process an encrypted SCT file using an
invalid encryption and decryption key or level of encryption in the script. The key must be in a
hexadecimal format, containing a mix of numeric digits (0-9) and alphabetic characters A-F
(not case sensitive). The specified encryption level must be 0, 1, 2, or 3.

Inverting all columns at timestamp

Explanation: This message is displayed at the beginning of the second phase (that is, index phase) of an
import operation. It indicates the date and time that ssadl begins to index all of the columns
loaded into the table in the first phase of the load.

Last output row = n

Explanation: ssadl displays this message at the conclusion of an export operation indicating the number of
rows written to the export file.

Multiple reading threads (-j > 1) not permitted when reading from a pipe; reverting to a single reading thread

Messages and Prompts 67

 Explanation: Multi-threaded reading cannot be performed with pipes, so ndlm will switch to single-threaded
reading if the -j parameter is set to a value greater than 1.

Multiple reading threads (-j > 1) not permitted when reading from CSV files; reverting to a single reading thread.

Explanation: Multi-threaded reading cannot be performed with CSV files, so ndlm will switch to single-
threaded reading if the -j parameter is set to a value greater than 1.

Output n rows
Explanation: This message is displayed by ssadl after each “chunk” of data has been written to the export
file. This permits visual feedback of the export progress.

User Response: You can roughly gauge the pace of the export from this display.

Row n doesn't have an impact on the database

Explanation: This message is displayed during an EXECSQL operation, if an UPDATE/DELETE/INSERT

Boolean condition evaluates to false for a value in the specified update file. That is, the target
table is not altered by the SQL statement for the row containing the field value.

Skipping n bytes
Explanation: This message is displayed whenever the -i invocation option or the IGNORE processing
option is specified. The message provides confirmation of the number of bytes skipped
before importing data.

Skipping n rows
Explanation: This message is displayed whenever either the -s invocation option or the SKIP processing
option is specified. The message provides confirmation of the number of rows skipped before
importing data.

Load Operation Error Messages

The following load operation error messages might appear when you run ssadl.

30101 IMPORT file 'file-name' not found

Explanation: This error message is issued by ssadl when it cannot locate the file containing the data to be
imported.

User Response: Make sure that the file name specified on the first line of the import specification file is
preceded by an “at” sign (@). Also, if the file is not located in the current working directory,
make certain that the file name specification contains the correct path specification.

30102 seek error on back scan

Explanation: This error message indicates that an error was returned from the shell, indicating that a file I/
O error occurred when ssadl tried to locate the last complete line in a variable length file.

68 Appendix A: File Archive Loader Messages

30103 SELECT statement exceeds available buffer space
Explanation: This error is returned by ssadl during export when the size of a SELECT statement exceeds
16 KB.

30104 no SELECT statement in the specification file

Explanation: This error message is issued by ssadl when the SELECT statement could not be located in
the export specification file. If the SELECT statement is indeed in the file, this error may be
the result of improperly placed braces ( {} ).

30105 SYNTAX ERROR in the specification file

Explanation: This error message is issued by ssadl when a syntax error is found in the import or export
specification file. Such an error is generally caused by missing or unbalanced syntax such as
a missing keyword, a missing “at” sign ( @ ), or unbalanced braces or square brackets.

30106 'field-name' field description has multiple lengths [line x]

Explanation: This error message is issued by ssadl when multiple field lengths are specified for the
indicated field. This usually occurs when both an asterisk (*) and an integer are specified
within a field-format, or when two separate “unescaped” integers are contained in a single
field-format.

30107 input file not record delimited

Explanation: This error message is issued when ssadl does not detect the expected delimiter (usually, \r\n
on the Windows platform, \n in UNIX) between records in the input file. Note that this returned
if the delimiter character is incorrectly typed in the RECORD section of the load specification
file (for example, if forward-slashes are used instead of back-slashes).

30108 out of memory

Explanation: This error message is returned when the operating system fails to meet a request for
memory. ssadl uses memory for internal buffers and needs approximately 1 MB in addition to
what the program itself occupies.

User Response: If the error occurred on a UNIX platform, increase user limits for the execution environment
with the system ulimit command.

30109 column 'column-name' not mapped to a field [line x]

Explanation: This error message is issued by ssadl when the indicated column is not assigned to a field-
label in the map specification part of an import specification file.

User Response: It must be assigned to a field that is defined in the record specification part of the import
specification file.

30110 cannot create EXPORT file 'file-name'

Explanation: This message is issued by ssadl if it cannot create the specified export data file.

User Response: Make sure that you have sufficient directory access privileges before re-executing ssadl.
Also, ensure that the specified export file does not have a name longer than 255 characters
(including dot and extension), and does not contain illegal characters.

Load Operation Error Messages 69

 30111 early end of file
Explanation: This message is issued by ssadl when it encounters an end-of-file within the number of bytes
specified for the -i or IGNORE processing option.

User Response: An example would be a request to ignore n+1 bytes in an n-byte file.

30112 processing interrupted

Explanation: This message is issued by ssadl when a negative response (that is, “N”) is entered at the
Data Formatted Correctly? prompt that follows the import preview.

30113 disk full!!!

Explanation: This message is issued when the disk on which the database file resides becomes full during
import, or when the disk to which the export file is being written becomes full during export.

User Response: Make the appropriate space adjustments before re-executing the import or export.

30114 field specifier error: x ( or field specifier, length <= zero; or column in select statement not
specified in record spec)
Explanation: One of these messages is issued when an error is encountered while parsing the
specification file. There are four different variations of this message depending upon the
value of x: i) a selected column is not represented in the record specification, ii) a column has
no specified length, iii) a column has too great a length, and iv) no delimiter is specified for a
variable length field (indicated by an asterisk).

User Response: Diagnoses of these problems can be found by looking at explanations of the following
messages respectively: 30109, 30126, 30116, and 30105.

30115 input data mismatch

Explanation: Issued when an input file record format is inconsistent with the record specification
description contained in the import specification file. This frequently occurs when the record
specification indicates that there is an end-of-line terminating each record (that is, \r\n on the
Windows platform, \n in UNIX), and there is no end-of-line found after the last record in the
input file.

30116 input data longer than the field MAXIMUM (4056)

Explanation: Issued when character data in a variable-length field exceeds 4056 characters. This is the
maximum permissible number of characters for a variable-length character column in SAND
CDBMS SQL. The offending record is rejected and written to the [Link] file, where
input-file is the name of the input data file identified in the import specification file.

30117 export record definition not record delimited

Explanation: This error is returned when the export record definition does not include a end-of-line
terminator (that is, \r\n on the Windows platform, \n in UNIX) indicating the end of a record.
Note that the end-of-line terminator is required when transporting data to another instance of
ssadl through a named pipe.

30118 early end of buffer

Explanation: This message is returned when ssadl scans a flat file and exhausts the current buffered
segment before encountering a field terminator. This is most likely to occur when a scan for
the delimiter character in a variable length field does not find the delimiter.

70 Appendix A: File Archive Loader Messages

30119 cannot open file 'file-name'
Explanation: ssadl cannot open the indicated file.

User Response: Make sure that you have sufficient access privileges and that the file is not damaged. Also,
ensure that the timing file or log file (specified with, respectively, the -t or -e ssadl invocation
flags) does not have a name longer than 255 characters (including dot and extension).

30120 IMPORT datafile record length specified as zero

Explanation: Returned when the specification file for an EXPORT operation contains no record definitions
in the RECORD section.

30121 argument is not a valid x option

Explanation: The indicated option is not a valid ssadl invocation option.

30122 flag option must have a filename argument

Explanation: Issued when either of the invocation options -e or -t is specified without a file name argument.

30123 -V option cannot be used with -B option

Explanation: This error message is issued by ssadl when the invocation options -b and -v are specified in
the same invocation (-v instructs ssadl to issue a prompt, and -b instructs ssadl to suppress
prompts).

30126 no length has been specified for <field-label or column-name>

Explanation: Issued when the field-format for the indicated field-label or column in the import or export
specification file fails to specify a field length.

User Response: Either an integer indicating a specific length, or an asterisk (*) indicating variable length, must
be specified.

30127 'flag-value' is not a valid number for option-flag option

Explanation: Issued when an invocation or processing option is encountered which specifies an invalid
numerical argument.

30128 input record n: width is too long

Explanation: Issued when ssadl, in processing a record from the input file, finds that the data contained in
a particular field exceeds the defined length of the target database column. ssadl will truncate
the data rather than rejecting the record.

30129 unexpected error during FETCH

Explanation: This error message is returned by the server during an export operation. It indicates that an
error has occurred in the FETCH command which returns data from the server to ssadl.

User Response: This generally indicates an error at the server; the export operation should be re-executed.

30130 'x' is not a valid field/table/column name

Explanation: This error message is issued by ssadl because the indicated name is an invalid field name,
table name, or column name. This might be caused by an illegal field name, a field name in
the map specification that does not appear in the record specification, a table name that does
not exist in the specified database, or a column name that does not belong to the specified
table.

Load Operation Error Messages 71

 30131 Nothing to import (or export). Too many rows skipped!
Explanation: This message is issued by ssadl prior to an import or export when the -s invocation option (or
SKIP processing option) specifies that more rows be skipped than exist in the input data file
(import), or than are returned by the export SELECT statement.

30132 fatal error in IGNORE bytes option

Explanation: This error message is issued when ssadl attempts to IGNORE the specified number of bytes,
and the operating system returns an error. This usually indicates file damage or file system
corruption.

30136 attempt to load unprintable character

Explanation: Returned when ssadl was invoked with the -z 0 option flag and a specified data file contains
an unprintable character in one of the input fields. The -z 0 option instructs ssadl to reject any
rows in the data load that contain an unprintable character; the rejected rows are written to
the [Link] file.

User Response: Specify the -z 1 option to have ssadl replace each unprintable character with an ASCII space
character. Include -z 2 in the ssadl invocation, or else omit the -z option entirely, if you wish
to load data as is into a SAND database, even if they contain unprintable characters.

30138 IMPORT/EXPORT file name missing from the specification file

Explanation: Issued when the import or export file (as defined by specification file syntax) is not found.

User Response: Make sure that the file name is specified accurately and prefixed by the “at” sign ( @ ).

30139 mapping error between fields specified and columns selected

Explanation: This error message is issued by ndlm during an export operation when there is a problem
mapping fields in the RECORD section with columns in the SELECT statement. One of three
possible secondary messages is included, specifying the exact nature of the problem:

¨ Number of fields specified exceeds number of columns selected

There are more fields in the RECORD section than columns referenced in the SELECT
statement, so one or more fields are not used.
¨ Selected columns contain duplicates

The SELECT statement projection list includes multiple references to the same column.
¨ Field specified doesn't map to selected columns

A field in the RECORD section is not specified as a column in the corresponding ordinal
position in the SELECT statement projection list.

30140 x already defined, duplicate ignored

Explanation: This warning message is issued by ssadl when duplicate invocation options or processing
options are entered in the ssadl invocation or specification file. Only the first instance is used;
duplicates are ignored.

30141 missing parameter for x, option ignored

Explanation: This warning message indicates that an invocation or processing option which requires an
argument was specified without the argument, and will therefore be ignored.

72 Appendix A: File Archive Loader Messages

30142 Found n errors during IMPORT. Keep going? Yes/No
Explanation: This warning message is issued by ssadl when the number of errors incurred reaches the
number specified with the -m invocation option or the MAXERR processing option.

User Response: Respond affirmatively to continue importing, or negatively to abort the import.

30143 User specified zero rows to process. Program Terminating.

Explanation: Issued when the argument specified with the -p invocation option or the PROCESS
processing option is zero (0).

30144 field width of x does not match column width of y

Explanation: This message is issued by ssadl during an export operation when the width of a column and
the width of the corresponding field do not match. Processing continues, but the exported
field may be truncated.

30145 [input record n:] UNIQUE violation

Explanation: Issued when a UNIQUE column or table constraint is violated during import. The offending
record is rejected and written to the [Link] file, where input-file is the name of the
input data file that is identified in the import specification file.

30146 [input record n:] NULL violation

Explanation: This error message is returned by the server when a NOT NULL column constraint is violated
during import. The offending record is rejected and written to the [Link] file, where
input-file is the name of the input data file that is identified in the import specification file.

30147 [input record n:] incompatible datatype

Explanation: This error message is returned by the server when the data value to be imported has a
datatype that cannot be accommodated by the datatype of the target database column. This
usually occurs during inadvertent attempts to import character data into numeric columns.
There are, however, other mismatch possibilities. The offending record is rejected and written
to the [Link] file, where input-file is the name of the input data file that is identified in
the import specification file.

30148 [input record n:] numeric truncation error

Explanation: This error message is returned by the server when a numeric value is assigned to a column
whose datatype is integer, decimal, or float (including real and double precision) and the
declared precision is insufficient to accommodate all of the digits of the assigned value. The
offending record is rejected and written to the [Link] file, where input-file is the name
of the input data file that is identified in the import specification file.

30149 [input record n:] integer outside range

Explanation: This error message is returned by the server when a value outside the range -32,767 <= n <=
32,767 is assigned to a column defined as SMALLINT, or when a value outside the range
-2,147,483,647 <= n <= 2,147,483,647 is assigned to a column defined as INTEGER. The
offending record is rejected and written to the [Link] file, where input-file is the name
of the input data file that is identified in the import specification file.

Load Operation Error Messages 73

 30150 [input record n:] string truncation error
Explanation: This message is returned when an asynchronous load operation inserts a string value that is
wider than the destination column. The inserted value is truncated on the right side to fit the
size of the column.

30151 attempt to load invalid character

Explanation: Returned when the input data contains a character that cannot be loaded by ssadl. For
example, the nul character (ASCII code 00) will generate this error.

User Response: Ensure that the source data do not contain unprintable or invalid characters.

30152 writing to named pipe. Client connection was closed

Explanation: An error occurred while writing to a a named pipe. The client process shut down
unexpectedly, or there was a network error preventing communication with the client.

User Response: Consult the system or network administrator for help with troubleshooting this error.

30153 [input record n:] DATE/TIME value is invalid

Explanation: Returned when attempting to load an invalid value into a DATE or TIME column. Note that a
DATE value must be in one of the following formats:

¨ mm/dd/yyyy

¨ yyyy-mm-dd

¨ [Link]

where mm is month, dd is day, and yyyy is year.

A TIME value must be in one of the following formats:
¨ [Link]
¨ hh:mm AM (or PM)

¨ hh:mm:ss

where hh is hour, mm is the minutes, and ss is the seconds.

30154 maximum # of errors reached, stopping load

Explanation: Returned when the number of errors specified with the -m flag is reached.

30155 defaulting -k option to 32 threads

Explanation: Returned when an invalid number is used for the -k option. A user-specified -k value must be
between 0 and 32.

30156 missing specified flat file "file-name" skipped

Explanation: Returned when multiple flat files are referenced in the specification file, and at least one of
them could not be found.

30157 maximum reading threads exceeded. n specified, only one allowed in standard mode
Explanation: Returned when attempting to execute the standard loader with the -j option enabled. The -j
flag (for setting the number of reading threads) can be used only with the Parallel Loader.

74 Appendix A: File Archive Loader Messages

30158 null violation, row x, column y (col-name)
Explanation: This error message is returned when a NOT NULL column constraint is violated during
import. The offending record is rejected and written to the [Link] file, where input-file
is the name of the input data file that is identified in the import specification file.

30159 bad datatype conversion, row x, column y (col-name)

Explanation: This error message is returned when the data value to be imported has a datatype that
cannot be accommodated by the datatype of the target database column. This usually occurs
during inadvertent attempts to import character data into numeric columns. There are,
however, other mismatch possibilities. The offending record is rejected and written to the
[Link] file, where input-file is the name of the input data file that is identified in the
import specification file.

30160 numeric truncation, row x, column y (col-name)

Explanation: This error message is returned when a numeric value is assigned to a column whose
datatype is INTEGER, DECIMAL, or FLOAT (including REAL and DOUBLE PRECISION) and
the declared precision is insufficient to accommodate all of the digits of the assigned value.
The offending record is rejected and written to the [Link] file, where input-file is the
name of the input data file that is identified in the import specification file.

30161 integer outside range, row x, column y (col-name)

Explanation: This error message is returned when a value outside the range -32,767 <= n <= 32,767 is
assigned to a column defined as SMALLINT, or when a value outside the range
-2,147,483,647 <= n <= 2,147,483,646 is assigned to a column defined as INTEGER. The
offending record is rejected and written to the [Link] file, where input-file is the name
of the input data file that is identified in the import specification file.

30162 character truncation, row x, column y (col-name)

Explanation: This message is returned when an asynchronous load operation inserts a string value that is
wider than the destination column.

User Response: The inserted value is truncated on the right side to fit the size of the column.

30163 SCT file already exists

Explanation: Returned when the load script SCTFILE parameter specifies a file that already exists.

User Response: To prevent accidental loss of metadata, ssadl will not overwrite an existing SCT file; it will
have to be renamed or moved, or the SCTFILE value will have to be changed, before the
IMPORT operation begins.

30164 IMPORT file specifies no columns to load

Explanation: Returned when the IMPORT specification script does not specify any columns to load. The
specification script is considered to be incomplete in this case.

30165 numeric truncation during export, row n, column x

Explanation: Returned when a fixed length output field is defined in the export specification script, and it is
not large enough to store an exported numeric value. The export operation is not interrupted
when this occurs; the value is exported, but is truncated to fit the defined field.

Load Operation Error Messages 75

 30166 Path to SCT file not found
Explanation: Returned when an invalid SCT path is defined in the specification script.

User Response: Ensure that the correct SCT export path is specified. The directories included as part of the
export path must actually exist.

30167 No valid TEMPDRIVE path was found or access denied: path

Explanation: Returned when the TEMPDRIVE parameter in the NUCLEUS environment variable has been
set to paths that do not exist, or the user does not possess the permissions required to
access the directories.

User Response: Ensure that the correct temporary drives are specified by the TEMPDRIVE parameter, and
that clients have been given the necessary permissions on them.

30169 One or more TEMPDRIVE paths do not exist

Explanation: One or more of the paths specified for the TEMPDRIVE parameter in the NUCLEUS
environment variable are invalid. This will not interrupt a load operation, unless all of the
temporary drives are invalid.

User Response: Verify that the correct TEMPDRIVE paths are set.

30170 Too many rows for SCT file

Explanation: The operation attempted to load more rows than the maximum permitted for a single SCT file
(231 or 2,147,483,648). The job will have to be partitioned and multiple SCT files created.

30171 no records selected, stopping SCT file creation

Explanation: The defining SELECT statement in an SCTEXPORT or ODBCIMPORT operation has
produced an empty result set. No SCT file is created in this situation.

30172 input buffer is too small for the number of reading threads specified: -j n
Explanation: The input buffer size (set with the -f option) cannot support the specified number of reading
threads.

User Response: Retry the loader operation either with a lower number of reading threads or with the input
buffer set to a higher value; or else do not set the input buffer manually, but rather allow
ssadl to determine the buffer size.

30173 Too many rows for one load

Explanation: The operation attempted to load more rows than the maximum permitted for a single load
operation (231 or 2,147,483,648).

User Response: The specification script and source data will have to be partitioned, and the load will have to
be performed over multiple sessions.

30175 Unsupported collation for SCT file

Explanation: This error is returned during an SCTEXPORT or ODBCIMPORT operation intended to create
an SCT file, when one or more character columns in the source table are defined with an
unsupported collation. At present, only BINARY collation is permitted for SCT files.

76 Appendix A: File Archive Loader Messages

 30176 General loader error
Explanation: A general error occurred during data processing. A number of different situations can
produce this error.

User Response: Examine the diagnostic message that accompanies this error for information about the
source of the error.

30177 COMMIT failed

Explanation: The database server failed to execute a COMMIT command during the loader operation.

30178 ROLLBACK failed

Explanation: The database server failed to execute a ROLLBACK command during the loader operation.

30179 Invalid encryption key format specified in [Link] file

Explanation: Returned by the loader when attempting to create or process an encrypted SCT file using an
invalid encryption/decryption key in the [Link] file. Note that the key must be in a
hexadecimal format, containing a mix of numeric digits (0-9) and alphabetic characters A-F
(not case sensitive).

30181 numeric value rounding in column col-name from scale x to scale y

Explanation: This warning is returned during a load operation if the DECIMAL scale in the target column is
less than the scale in the source column. The values will be loaded, but the scale of the data
will be rounded to fit the target column.

30180 -k option required to create the SCT file

Explanation: A loader operation to create an SCT file was initiated in standard mode, instead of Parallel
Loader mode (ssadl -k). SCT files can only be generated using the Parallel Loader.

User Response: Retry the operation, invoking ssadl with the -k parameter to activate the Parallel Loahder and
set the number of processing threads.

File Parsing Messages

The following file parsing messages might appear when you run ssadl.

0001 MAXERR statement has been defined more than once.

Explanation: Returned when the MAXERR option is specified two or more times. A MAXERR statement
can appear only once in the specification file.

0002 ERRINC statement has been defined more than once.

Explanation: Returned when the ERRINC option is specified two or more times. An ERRINC statement can
appear only once in the specification file.

0003 PROCESS statement has been defined more than once.

Explanation: Returned when the PROCESS option is specified two or more times. A PROCESS statement
can appear only once in the specification file.

File Parsing Messages 77

 0006 IGNORE statement has been defined more than once.
Explanation: Returned when the IGNORE option is specified two or more times. An IGNORE statement
can appear only once in the specification file.

0007 SKIP statement has been defined more than once.

Explanation: Returned when the SKIP option is specified two or more times. A SKIP statement can appear
only once in the specification file.

0008 NULL statement has been defined more than once.

Explanation: Returned when the NULL option is specified two or more times. A NULL statement can
appear only once in the specification file.

0009 Invalid file name: 'file-name'.

Explanation: Returned when a specified data file name is considered invalid by the operating system. A
data file name must adhere to the naming rules of the operating system where it is saved. On
a Windows platform, the file name must be less than 256 characters in length, and may not
contain any of the following symbols:

\?|><:/*"

On a UNIX system, the file name must be less than 256 characters in length. Almost any
character can be used in a UNIX file name, but it is recommended that names be limited to
alphabetic characters, numbers, periods ( . ), underscores ( _ ), and dashes ( - ).

0010 Field 'field-name' has been defined more then once.

Explanation: There are two or more fields with the same name in the record specification section. Each
field must have a unique name.

0011 Invalid picture specification on field 'field-name'.

Explanation: Returned when a PIC clause contains an invalid formatting string.

0013 Missing field specification: 'field-name'

Explanation: Returned when an undefined field is referenced in a variable definition.

User Response: Ensure that all referenced fields are defined in the record specification section.

0014 Invalid field length specification: 'field-name'.

Explanation: Returned when a field definition contains an invalid field length specification. The field length
specification must be one of the following:

¨ an integer n, where n is the fixed length of the field

¨ an asterisk (*), indicating a variable-length field

¨ a fixed length field mapping in the form ( starting-position : field-length ), where starting-
position marks the beginning of the field, measured in number of characters from the
beginning (or leftmost position) of the record, and field-length is the number of characters
to include in the field, starting from starting-position and counting from left to right.

0015 Field 'field-name' is referencing an undefined field.

Explanation: Occurs when a field specification references (“remaps”) another field that has not been
defined.

78 Appendix A: File Archive Loader Messages

User Response: Ensure that all referenced fields are defined, and that each referenced field is defined before
the field that remaps it in the record specification section.

0016 Illegal remapping of field 'field-name'.

Explanation: Returned when a record definition contains an invalid field remapping. For instance, a field
cannot remap itself:

field1 (field1:1:2)

User Response: Ensure that each field remapping references a valid field before attempting the load operation
again.

0017 Column 'column-name' has been defined more than once.

Explanation: A column in the map specification section is defined more than once. Each column included
in the load operation must have a single definition.

0018 Column 'column-name' is referencing an undefined field 'field-name'.

Explanation: This error is returned when an undefined field appears in the map specification section.
Ensure that all the fields referenced in the map specification section have a corresponding
field definition in the RECORD section. If field-name is in fact a variable name, note that
variables are referenced by prefixing the variable name with “%”; that is, %variable-name.
Omitting the “%” will result in this error message.

0018 Undefined field 'field-name' found in SKIPIF clause.

Explanation: This error is returned when an undefined field appears in a SKIPIF statement. Ensure that all
the fields referenced in the SKIPIF statement have a corresponding field definition in the
RECORD section. If field-name is in fact a variable name, note that variables are referenced
by prefixing the variable name with “%”; that is, %variable-name. Omitting the “%” will result
in this error message.

0019 Invalid file name found in SKIPIF: 'file-name'.

Explanation: Returned when a specified SKIPIF file name is considered invalid by the operating system.
The SKIPIF file name must adhere to the naming rules of the operating system where it is
saved. On a Windows platform, the file name must be less than 256 characters in length, and
may not contain any of the following symbols:

\?|><:/*"

On a UNIX system, the file name must be less than 256 characters in length. Almost any
character can be used in a UNIX file name, but it is recommended that names be limited to
alphabetic characters, numbers, periods ( . ), underscores ( _ ), and dashes ( - ).

0020 Invalid position value in 'field-name' (must be >= 1 and <= 8192).
Explanation: Returned when a RECORD section field mapping (or remapping) specifies a start position
value that does not fall within the acceptable range. A field (re)mapping position value must
be between 1 and 8192 inclusive.

0021 Invalid length value in 'field-name' (must be >= 1 and <= 8192).
Explanation: Returned when a RECORD section field mapping (or remapping) specifies a length value that
does not fall within the acceptable range. A field (re)mapping length value must be between 1
and 8192 inclusive.

File Parsing Messages 79

 0022 Invalid field mapping specification: 'field-name'.
Explanation: Returned when an invalid field remapping appears in the record specification area. Field
remapping, where a field or part of a field is used as the source for another field (thus
creating “sub-fields”), is defined using the following syntax:

( reference-field-name : position : length )

where reference-field-name is the name of the field being remapped, position is the starting
position of the sub-field within the referenced field, and length is the length of the sub-field (in
characters).

0023 Unable to open rejected rows file: 'file-name'.

Explanation: Returned when ssadl could not open, create, or write to a file containing the rows rejected
during the load operation. The rejected rows file is called [Link], where input-file is
the name of the data file containing the rows that were rejected. The rejected rows file is
saved in the same directory as the specification file. This error might occur if the user
executing ssadl does not possess the appropriate access permissions on the rejected rows
file (if it already exists) or the directory where it is stored. The error might also occur if the
rejected rows file has been locked by another process.

User Response: Ensure that write permission is granted on the relevant files and directories, and that no other
process is using the rejected rows file, before attempting the load operation again.

0024 Invalid position reference for field 'field-name'.

Explanation: Returned when a field definition includes a NULLIF or MISSINGIF clause that uses the field
mapping format. For instance:

field1 (1:5) NULLIF (1:2) == 'ab'

The field mapping format cannot be used with the NULLIF and MISSINGIF clauses. If you
wish to use a subset of a field in these clauses, use the LEFT(), RIGHT(), or MID() functions
to return the substring.

0024 Invalid position reference in SKIPIF.

Explanation: Returned when the SKIPIF clause uses the field mapping format. For instance:

SKIPIF (20:4) == 'xxxx' @[Link]

The field mapping format cannot be used in the SKIPIF clause. Reference fields by name. If
you wish to use a subset of a field in this clause, use the LEFT(), RIGHT(), or MID() functions
to return the substring.

0025 Error found in SQL INSERT.

Explanation: There was a syntax error in the EXECSQL INSERT statement.

User Response: Ensure that the INSERT statement is correct, and then re-attempt the load operation.

0026 Error found in SQL DELETE.

Explanation: There was a syntax error in the EXECSQL DELETE statement.

User Response: Ensure that the DELETE statement is correct, and then re-attempt the load operation.

80 Appendix A: File Archive Loader Messages

0027 Error found in SQL UPDATE.
Explanation: There was a syntax error in the EXECSQL UPDATE statement. Ensure that the UPDATE
statement is correct, and then re-attempt the load operation.

0028 Unclosed comment.

Explanation: Returned when a start of comment indicator ( /* ) appears without an end of comment
indicator ( */ ).

User Response: Ensure that all comments are “closed”.

0028 Token is too large.

Explanation: Returned when a script element, such as an SQL command or an ODBC connection string,
exceeds 256 KB (262,144 characters).

User Response: Ensure that each individual NDL script element is not longer than 262,144 characters, as this
is the maximum size that can be processed by ssadl.

0028 Invalid SQL statement 'x'.

Explanation: Returned when an EXPORT or EXECSQL command contains an erroneous SQL statement.
Usually, this means that the SQL statement is missing a terminating semicolon ( ; ).

0028 Invalid token 'x'.

Explanation: An invalid NDL script element appears in the specification file at the indicated line.

User Response: Make the necessary corrections, and then re-attempt the load operation.

0029 Illegal expression type found. Expected <type>.

Explanation: Returned when an expression evaluates to a datatype that is not expected where the
expression is used.

User Response: Ensure that the expression is correct, and that the correct datatype is produced. If necessary,
“cast” values to the expected datatypes. For example, INT(value1) will produce an int value
(provided that value1 is composed entirely of numeric characters).

0030 Unknown program error during the parsing.

Explanation: An unspecified error occurred while ssadl read the specification file.

User Response: Re-attempt the data load. If the problem persists, contact a SAND support representative.

0031 Invalid pipe name: 'pipe-name'.

Explanation: Returned when a specified pipe name is considered invalid by the operating system. A pipe
name must adhere to the naming rules of the operating system where it is used. On a
Windows platform, the pipe name must be less than 256 characters in length, and must not
contain any of the following symbols:

\?|><:/*"

On a UNIX system, the pipe name must be less than 256 characters in length. Almost any
character can be used in a UNIX pipe name, but it is recommended that names be limited to
alphabetic characters, numbers, periods ( . ), underscores ( _ ), and dashes ( - ).

File Parsing Messages 81

 0032 ODBC driver connection error.
Explanation: An ODBCIMPORT operation could not be performed. Proper operation of ODBC depends
upon a number of Microsoft ODBC drivers. Problems sometimes occur if these drivers have
DLL files with mismatched versions or missing DLL files.

User Response: If necessary, reinstall the Microsoft ODBC drivers.

This error may also indicate a problem with shared network connections. In this case, consult
your network administrator for help with troubleshooting this problem.

0033 Field 'field-name' already declared.

Explanation: Occurs when a field is declared more then once in a TYPE clause. Each field must have a
unique name and can be declared only once.

0034 Variable 'variable-name' already defined.

Explanation: Occurs when a variable is defined more than once. Each variable must have a unique name
and can be defined only once.

0035 Wrong number of arguments in 'function-name' function call. Must be at least x.

Explanation: Occurs when a function is called with the incorrect number of arguments. The number of
arguments passed to the function is less than the minimum number of arguments required by
the function.

0035 Wrong number of arguments in 'function-name' function call. Must be maximum x.

Explanation: Occurs when a function is called with the incorrect number of arguments. The number of
arguments passed to the function exceeds the maximum number of arguments permitted by
the function.

0036 Invalid expression.

Explanation: Signals a general expression error.

User Response: Ensure that the expression is correctly formed, and then re-attempt the load operation.

0037 Variable 'variable-name' is recursively referenced.

Explanation: Occurs when a variable references itself in the variable declaration section. For example:

VAR

V1 (%V1)

82 Appendix A: File Archive Loader Messages

0038 Variable 'variable-name' is referenced but not defined.
Explanation: Occurs when a variable is referenced in an expression, but is not defined in the VAR section.
This error may also be returned if a variable references another variable that is not yet
defined in the variable declaration list. For example:

VAR

V1 (%V2 + 'world')

V2 ('hello ')

V2 must be defined prior to V1 in order for the definition of V1 to be valid.

0039 Datatype <data-type1> can't be assigned to column "column-name". Expected <data-type>.

Explanation: Occurs when the datatype of the expression is not compatible with that of the column to
which it is assigned.

0040 Unknown function found: 'function-name'.

Explanation: Occurs when an identifier that is not recognized as a function is used as a function name.
Consult the NDL++ Scripting Functions chapter in this guide for a description of the valid NDL
functions.

0041 Illegal datatype <data-type1> for argument number x in 'function-name' function. 'function-
name' requires <data-type> not <data-type1>.
Explanation: The wrong datatype was passed to a function. Ensure that the correct values are being
passed to the function. If necessary, “cast” the value to the datatype expected by the
function. For example:

TRUNC( FLOAT(field1) )

If the value is numeric and the function expects a string, use the STR() function to convert the
value. For example:

STR(123)

0041 Illegal arguments in call of function 'function-name' found.

Explanation: Returned when there is a general error involving the arguments in a function call.

User Response: Ensure that the correct datatypes and number of parameters are being sent to the function.

0041 Invalid operator for datatypes. <datatype list> not operable by '<function-name or operator-
type>'.
Explanation: Returned when attempting an arithmetic operation involving a string value. Arithmetic
expressions are limited to the int and float datatypes.

File Parsing Messages 83

 0048 Unexpected script-element in file 'file-name' at line x.
Explanation: An NDL script element was found in an inappropriate location in the specification file. A script
element can be one of the following:

¨ identifier x

¨ integer constant x

¨ float constant x

¨ string x

¨ field delimiters x

¨ file name x
¨ picture specification x

¨ NULL string x

¨ SQL command x

¨ “MAXERR” keyword

¨ “ERRINC” keyword

¨ “SELFREF” keyword

¨ “IGNORE” keyword

¨ “PROCESS” keyword

¨ “RECORD” keyword

¨ “IMPORT” keyword

¨ “EXPORT” keyword

¨ “EXECSQL” keyword

¨ “SKIP” keyword

¨ “SKIPIF” keyword

¨ “TABLE” keyword

¨ “PIC” keyword

¨ “NULL” keyword

¨ “NULLIF” keyword

¨ “MISSINGIF” keyword

¨ “SQL” keyword

¨ “UPSERT” keyword

¨ “ALTERNATESQL” keyword

¨ “ELSE” keyword

¨ “INSERT” keyword

¨ “DELETE” keyword

¨ “UPDATE” keyword

¨ “*”

¨ “{“

¨ “}”

¨ “( “

¨ “)”

¨ “:”

¨ “~”
84 Appendix A: File Archive Loader Messages
¨ “!”

¨ “==”
0049 Missing directive in file 'file-name' at line x found script-element.
Explanation: Indicates that an IMPORT, EXPORT, or EXECSQL command keyword was not found at the
required position.

0050 Illegal directive in file 'file-name' at line x found script-element.

Explanation: Indicates that some other character string was found instead of an IMPORT, EXPORT, or
EXECSQL command keyword at the required position.

0051 Missing file specification in file 'file-name' at line x found script-element.

Explanation: Indicates that the file name for the input file was not specified, or the file name was not
preceded by the '@' symbol.

0052 Missing value or command specification in file 'file-name' at line x found script-element.
Explanation: Indicates that a PROCESS or SKIP keyword was not followed by a parameter value.

0053 Illegal command specification in file 'file-name' at line x found script-element.

Explanation: Returned when the record specification section is omitted, or a function is called from an
inappropriate location in the script.

User Response: Ensure that there is a record specification section; this is a required element of the
specification file.

0054 Missing section specifier in file 'file-name' at line x found script-element.

Explanation: Indicates that an opening section delimiter ( { ) was found without a corresponding section
name.

0055 Missing section opening delimiter in file 'file-name' at line x found script-element.
Explanation: Indicates that a section name was found without a corresponding opening delimiter ( { ).

0056 Invalid field specifier in file 'file-name' at line x found script-element.

Explanation: Indicates that no valid field identifier was found after the opening section delimiter.

0057 Missing field specifier in file 'file-name' at line x found script-element.

Explanation: Indicates that a reserved word was found after the opening section delimiter.

0058 Missing field definition in file 'file-name' at line x found script-element.

Explanation: Indicates that a field in the RECORD specification lacks a defined field format.

User Response: Complete the field definition at the cited line number, and then re-attempt the load operation.

0059 Invalid field definition in file 'file-name' at line x found script-element.

Explanation: Indicates an error in a field-length specification. Note that variable length fields require at
least one trailing delimiter.

File Parsing Messages 85

 0061 Illegal clause in file 'file-name' at line x found script-element.
Explanation: Indicates that an unexpected script element appears after a field definition. The following
elements will generate this error message if they follow a complete field definition:

¨ a string (in quotes) or numeric constant

¨ the PIC keyword without a corresponding expression

¨ (x:y) (field mapping format)

¨ * (variable length operator)

¨ ‘(’ (open parenthesis)

¨ ‘{ }’ (a redundant delimiter)

0062 Illegal expression in file 'file-name' at line x found script-element.

Explanation: Indicates that an expression is incorrectly formed, or absent altogether in a location where it
is expected.

User Response: Ensure that the expression exists and is valid, and then re-attempt the ssadl operation.

0063 Missing section closing delimiter in file 'file-name' at line x found script-element.
Explanation: Indicates that a section is missing its closing delimiter ( } ).

0064 Missing table specification in file 'file-name' at line x found script-element.

Explanation: The destination table for the load is not provided, or is not in the expected location.

User Response: Ensure that the table name appears in the script before the delimited map specification area
as follows:

[schema-name.]table-name

<map specification>

0065 Null value too long, must be <= 256.

Explanation: Returned when the NULL option is included in the script with a string value more than 256
characters in length. The null indicator string must be 256 characters or less.

0066 Delimiter string too long, must be <= 256.

Explanation: Returned when a field delimiter string in the record specification section is more than 256
characters in length. Field delimiters must be 256 characters or less.

0067 Field name too long, must be <= 256.

Explanation: Returned when a field name in the record specification section is more than 256 characters in
length. Field names must be 256 characters or less.

0068 Picture specification too long, must be <= 256.

Explanation: Returned when a PIC clause formatting string is more than 256 characters in length. PIC
clause formatting strings must be 256 characters or less.

86 Appendix A: File Archive Loader Messages

0069 File name too long, must be <= 260.
Explanation: Returned when the specification file contains a SKIPIF, DSNFILE, or export file name that is
256 or more characters. Specified file names must be 255 or fewer characters (including the
dot and extension) in length.

0070 Column name too long, must be <= 256.

Explanation: Returned when a referenced column name is more than 256 characters in length. Note that
SAND database column names have a maximum length of 128 characters.

0071 Character constant too long, must be <= 1024.

Explanation: Returned when a character constant longer than 1024 characters in length appears in the
specification file.

User Response: If a string longer than 1024 characters is required, define multiple variables in the VAR
section, each a subset of the full string. Another variable can then be defined using the
concatenation of these substring variables, for example:

VAR

VAR1 'substring1'

VAR2 'substring2'

VAR3 'substring3'

VARSTRING (%VAR1 + %VAR2 + %VAR3)

The “VARSTRING” variable can be referenced wherever the full string is required. For
instance:

table1

col1 %VARSTRING

0072 Table name too long, must be <= 256.

Explanation: Returned when a referenced table name is more than 256 characters in length. Note that
SAND database table names have a maximum length of 128 characters.

0080 Error reading information from the first row in CSV file.
Explanation: Returned when there is a problem with the optional CSV header row. Possible issues include
the following:

¨ The number of fields names does not correspond to the NUMBEROFFIELDS value in the
record specification.
¨ The number of fields names does not correspond to the actual number of data fields in the
CSV file.
¨ The header row does not terminate with the expected record delimiter.

File Parsing Messages 87

 0083 Maximum number of fields/columns exceeded. Current limit is 4096.
Explanation: Returned if the number of fields or columns specified in the load specification script is greater
than the maximum of 4096.

0084 Number of fields specified in NUMBEROFFIELDS does not match number of fields in the first
row in CSV file.
Explanation: Returned if the number of fields specified for the NUMBEROFFIELDS parameter in the
CSVFORMAT section of the load specification script differs from the actual number of fields
in the CSV file. Since the NUMBEROFFIELDS parameter is intended for error-checking, this
discrepancy will halt the load operation.

User Response: Before retrying the load operation, verify that the correct CSV file is being specified. If
necessary, change the value of NUMBEROFFIELDS, or else disable field error-checking by
either setting NUMBEROFFIELDS to 0 or removing that parameter from the script.

0096 Invalid position value in (pos:len). position (must be >= 1).

Explanation: Occurs when a starting position less than 1 is specified in a field mapping declaration. This
error would be returned in response to the following example:

(-10:3)

0097 Invalid length value in (pos:len). length (must be >= 1 && <= 4056).
Explanation: Occurs when an invalid length is specified for a field mapping declaration. The length value
must be between 1 and 4056 inclusive. This error would be returned in response to the
following example:

(10:-3)

0098 A sign is not allowed for a non-numeric operand. Field 'field-name'.

Explanation: Returned when a plus or minus sign prefixes a string value, for example, +S. A sign can only
be used with int and float values.

0099 Unable to locate 'ODBC-driver' file.

Explanation: The ODBC driver required for the ODBCIMPORT operation could not be found.

User Response: If the DSNSTR option is used in the specification file, ensure that the specified ODBC driver
exists and is spelled correctly. If the DSNFILE option is used, ensure that the specified file
DSN contains the correct ODBC driver path location.

0100 Unable to find function function-name() in 'ODBC-driver'.

Explanation: An internal error occurred while attempting an ODBC import.

User Response: If importing from a SAND database, make sure that the latest version of the Nucleus ODBC
Driver is installed. If the problem persists, contact a SAND support representative. If another
ODBC driver is being used, contact the developers of that driver for help with troubleshooting
this error.

0101 Can't open DSN file 'DSN-file-path'.

Explanation: Returned when the file DSN could not be found in the path specified with the DSNFILE
option, or the file DSN is locked by another process.

88 Appendix A: File Archive Loader Messages

User Response: Ensure that the path is correct, and that no other process is using the file DSN. If necessary,
create a new file DSN with the path specified; or else use the DSNSTR option in conjunction
with an appropriate connection string.

0102 DSN file 'DSN-name' doesn't exist on the registry.

Explanation: On the Windows platform, the specified DSN name could not be found in the system registry.

User Response: Ensure that the spelling of the DSN name is correct. If necessary, create the appropriate
DSN using the Nucleus ODBC Data Source Wizard or the Windows Data Source
Administrator control panel applet prior to attempting the load operation.

0103 Unable to locate 'user-library-name' file.

Explanation: Returned when a user-defined library file could not be located in the path specified in the
LIBRARY section of an NDL script.

User Response: Ensure that the user library path is correct before attempting the load operation again.

0104 User library is referencing the built-in function 'function-name'.

Explanation: Returned when a user-defined function declared in a LIBRARY section has the same name
as a built-in NDL++ function. NDL++ does not permit function “overloading”. Each function
name, whether user-defined or built-in, must be unique within an NDL script.

0105 User function 'function-name' already defined.

Explanation: Returned when the same user-defined function name is declared more than once in an NDL
script. NDL++ does not permit function “overloading”. Each user-defined function name must
be unique within an NDL script, even if functions with the same name belong to different
libraries.

0112 Unable to find user function 'function-name'.

Explanation: Returned when a user-defined function is declared in an NDL script, but the function does not
exist in the specified library file.

User Response: Ensure that the library file includes the specified function, and that the correct function name
is provided for its declaration in the NDL script.

0113 Invalid number of arguments in definition of the user function 'function-name' (must be > 0
and <= 10).
Explanation: Returned when a user-defined function requires 11 or more arguments. NDL++ imposes a
limit of 10 arguments for all functions.

User Response: In order to be used in an NDL script, this user function must be redefined with fewer
arguments.

0114 Too many user functions (must be <= 1024).

Explanation: Returned when an NDL script contains more than 1024 user function definitions.

User Response: Before attempting the load operation again, remove any unnecessary function definitions, or
functions that can be easily substituted for by built-in NDL++ functions, so that the number of
function definitions in the script is less than or equal to 1024.

File Parsing Messages 89

 0115 PICTURE has been defined more then once on field 'field-name'.
Explanation: Returned when the PIC keyword appears more than once in relation to the same field. A field
can have at most one PIC clause associated with it.

0116 NULLIF has been defined more then once on field 'field-name'.
Explanation: Returned when the NULLIF keyword appears more than once in relation to the same field. A
field can have at most one NULLIF clause associated with it.

0117 MISSINGIF has been defined more then once on field 'field-name'.
Explanation: Returned when the MISSINGIF keyword appears more than once in relation to the same
field. A field can have at most one MISSINGIF clause associated with it.

0118 User library 'user-library-name' has been already initialized.

Explanation: Returned when a particular user-defined library is referenced in multiple initialization
statements in the INIT section of an NDL script.

User Response: The library may be initialized only once. Remove any redundant initialization statements from
the NDL script before attempting the load operation again.

0119 User library 'user-library-name' is referenced but not defined.

Explanation: Returned when the INIT section of an NDL script contains an initialization statement for a
user library that does not have a corresponding LIBRARY section.

User Response: Ensure that a valid LIBRARY section exists for the user library before attempting the load
operation again.

0120 Duplicate lookup name 'lookup-instance'.

Explanation: Returned when the INIT section of an NDL script contains two or more LOOKUP instances
with the same name. Each LOOKUP instance must have a unique name.

0121 Unknown lookup name 'lookup-instance'.

Explanation: Returned when a LOOKUP call references a lookup instance that was never initialized in the
INIT section.

User Response: Ensure that the referenced lookup name matches one in the INIT section.

0122 Duplicate attribute column 'column-name' for lookup 'lookup-instance'.

Explanation: Returned when the same attribute name appears more than once in a LOOKUP instance
attribute list in the INIT section of an NDL file.

User Response: A specific attribute name may be included only once in a LOOKUP instance attribute list.

0123 Unknown attribute column 'column-name' for lookup 'lookup-instance'.

Explanation: Returned when the second argument in a LOOKUP call is not listed among the attribute fields
in the initialization of the lookup instance.

User Response: Ensure that the attribute argument in the LOOKUP call matches one of the attributes
declared for the lookup instance.

90 Appendix A: File Archive Loader Messages

0124 Duplicate key column 'column-name' for lookup 'lookup-instance'.
Explanation: Returned when the same key name appears more than once in a LOOKUP instance key list
in the INIT section of an NDL file.

User Response: A specific key name may be included only once in a LOOKUP instance key list.

0125 Unknown key column 'column-name' for lookup 'lookup-instance'.

Explanation: Returned when one of the key fields in a LOOKUP call does not match any of the key fields
declared in the initialization of the lookup instance.

User Response: Ensure that there is correspondence among the key fields in the LOOKUP call and the key
field list in the lookup initialization.

0126 Lookup name must be a character constant.

Explanation: Returned when a LOOKUP instance name in the INIT section of an NDL file is not a
character constant value.

User Response: Ensure that the LOOKUP instance name is contained in quotation marks (“lookup-name”).

0127 Lookup attribute must be a character constant.

Explanation: Returned when a LOOKUP attribute name in the INIT section of an NDL file is not a character
constant value.

User Response: Ensure that each name in the LOOKUP attribute list is contained in quotation marks
(“attribute-name”).

0128 Lookup key must be a character constant.

Explanation: Returned when a LOOKUP key name in the INIT section of an NDL file is not a character
constant value.

User Response: Ensure that each name in the LOOKUP key list is contained in quotation marks (“key-name”).

0129 Too many data files found (must be <= 16384).

Explanation: Returned when the number of data files referenced in an NDL script exceeds 16,384. The
File Archive Loader imposes a limit of 16,384 on the number of files it can process in a single
load operation. Note that this error will be returned whether the excessive number of data file
references is explicit (that is, 16,385 or more individual @data-file references) or implicit
(through the use of wildcards, such as, @*.dat).

If there are more than 16,384 data files, combine some of them in order to reduce their
number if possible. Otherwise split the NDL script into multiple scripts, so as to distribute a
smaller number of data file references for each script.

0130 No data files found. Nothing to load.

Explanation: Returned when the specification file references a data file that does not exist.

User Response: Ensure that the correct data file is being referenced, and that it exists in the specified
directory. If no file path is given, the current directory is searched. If wildcards are used,
make certain that at least one file matches the file name mask.

0131 Missing column specification.

Explanation: Returned when a load specification script does not define any columns into which to load. At
least one column must be defined for the load operation.

File Parsing Messages 91

 0132 Lookup name too long.
Explanation: Returned when the length of a LOOKUP instance name is 256 or more characters. The
maximum length of a LOOKUP name is 255 characters.

92 Appendix A: File Archive Loader Messages

INDEX

S
SAND CDBMS Nearline
error messages

93