FastObjects Error Code Reference

Transcription

1

2 FastObjects Release 12.0 Copyright Versant Software LLC and Copyright Actian Corporation. All rights reserved. The software described in this document is subject to change without notice. This document does not represent a commitment on the part of Versant or Actian. The software is furnished under a license agreement or nondisclosure agreement and may be used or copied only in accordance with the terms of the agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or for any purpose without the express written permission of Actian. Versant, Versant Object Database and FastObjects are either registered trademarks or trademarks of Versant Software LLC in the United States and/or other countries. Java and all Java-based marks are trademarks or registered trademarks of Oracle Corporation in the United States and other countries. Eclipse and Built on Eclipse are trademarks of Eclipse Foundation, Inc. Microsoft, Windows, Visual C#, Visual Basic, Visual J#, and ActiveX are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other products are a registered trademark or trademark of their respective company in the United States and/or other countries V9-6

3 Table of Contents Contact Information for Actian... v 1. Overview About this Guide Organization of this Guide Prerequisite Knowledge FastObjects Error Codes Operating System Errors -1 to File System Errors -301 to Internal Errors -501 to Internal Index Management Errors to General Kernel Errors to Client/Server Communication Errors to Database Validity Check Errors to Database Encryption and Communication Encryption Errors to Database Replication and Failover Errors to Sub Schemata Errors to Licensing Errors to Miscellaneous Usage Errors to and to OQL Errors to Transaction Errors to Call Clustering and Access Path Errors to Loadable Module Errors to Index Service Errors to SQL Object Factory Errors to Database and Dictionary Administration Errors to Online Versioning Logging Errors to Online Versioning Callback Errors to FastObjects Internal Errors to FastObjects Warning Codes File I/O Warning 300 to FastObjects Internal Index Management Warnings 1001 to General Kernel Warnings 2000 to OQL Warnings 3001 to Transaction Warnings Call Clustering and Access Path Warnings 4101 to SQL Object Factory Warnings 6093 to Dictionary and Database Warnings 7000 to Database Check Warnings 7101 to Transaction Warnings 9000 to iii

4 iv

5 Contact Information for Actian You can obtain the latest information about Actian products by contacting either of our main office locations, visiting our web sites, or sending us an . Actian Office Locations Actian Corporation is headquartered in Redwood City, California. Versant GmbH is responsible for European operations and has headquarters in Hamburg, Germany. Actian Corporate Headquarters 500 Arguello Street, Suite 200 Redwood City, CA USA [TEL] [FAX] Versant GmbH Halenreie 42 D Hamburg Germany +49 (0) [TEL] +49 (0) [FAX] Actian Web Site For the latest corporate and product news, visit the Actian web site at Actian Versant Products For inquiries about Versant products and services, contact: info@versant.com For help in using Versant products, contact Technical Support at: versant_support@actian.com The Actian Customer Portal provides all the essential information and valuable resources needed by developers using Versant Object Database or Versant FastObjects. Visit the Actian Customer Portal at support.actian.com v

6 Please send feedback regarding this guide to: vi

7 Chapter 1. Overview This chapter describes the purpose and organization of this guide, defines what prerequisite knowledge you need in order to use this book, and presents a list of related FastObjects documents that you may find useful About this Guide This guide provides a list of the error and warning codes that are returned by the FastObjects API methods for the various SDKs. This guide also provides a description of the error and warning codes if they are listed by number and suggestions for correcting them Organization of this Guide This guide contains the following chapters: Chapter 2, FastObjects Error Codes pg. 3, provides listings of the FastObjects error codes Chapter 3, FastObjects Warning Codes pg. 69, provides listings of the FastObjects warning codes. A comprehensive index is also provided at the end of this document Prerequisite Knowledge This guide assumes that you are familiar with object-oriented concepts. 1

8 2

9 Chapter 2. FastObjects Error Codes This chapter provides listings of the FastObjects error codes. In the sections listing the errors by number, there are also descriptions of the error and suggestions for correcting them. The error codes are returned directly by many of the API calls in the FastObjects C++ binding. Error codes are represented by negative code values. The return value zero (0) indicates no error or warning. The FastObjects SDK for the Java Platform binding uses exceptions and the error is reported as a descriptive error message that is a part of any thrown exceptions. However, when using FastObjects SDK for the Java Platform, some exceptions simply use the error code rather than a descriptive exception message Operating System Errors -1 to -300 Unknown operating system error; not handled by FastObjects. Refer to your OS Description. For further information, contact FastObjects Technical Support File System Errors -301 to -399 This range of error codes is reserved for file-i/o modules. Refer to your File System Description. For further information, contact FastObjects Technical Support Internal Errors -501 to -508 This range of error codes is normally not exposed to the API. For further information, contact FastObjects Technical Support Internal Index Management Errors to This range of error codes is reserved for FastObjects-internal index management. For further information, contact FastObjects Technical Support. 3

10 General Kernel Errors to General Kernel Errors to ERR_PT_BREAK Your function was interrupted because a progress callback function returned the value PtEXC_ABORT. It is also possible that your callback function does not have a return value and is returning whatever happened to be on the stack ERR_PT_CLASSDESC_NOT_READY FastObjects cannot use a specific class description from the class dictionary because the class description has not been verified or is incomplete. This means that your class dictionary has not been fully loaded, and there may be a problem with this class description ERR_PT_ILLEGAL_PARAMETER One of the parameters you passed to this function is not valid. See the description for the function that you called ERR_PT_NO_CLASSDESC FastObjects cannot find a specific class description in the class dictionary. This most commonly occurs when you explicitly delete a class from the class dictionary but the database contains objects or references to objects of this class ERR_PT_FACTORY_NOT_FOUND The class factory table for the schema could not be found. The name of the class factory table is stored as a string both in the database itself and in the PtAssoc structure of the dictionary's class factory files. This error is returned if the two strings do not match. Case sensitive comparison is used. This error can occur if (1) the name you used to create the dictionary does not match the one stored in the database, or (2) you are not linking in your class factory files. If you store class factory files in a library, they may not be linked in because there are no explicit references to them in your program. You can solve this problem by (1) including the class factory files into another program file that is referenced, e.g., the one that implements the class, or (2) linking the class factory object files into your project directly, not via a library. Another common cause is the usefactory parameter of the InitPOET() method being set incorrectly. 4

11 General Kernel Errors to ERR_PT_RANGE You attempted to do a Get() or a Seek() at the beginning or end of a set. This is not usually an error; it merely means that you have reached the end of the set ERR_PT_CLASSDESC_NOT_LINKED Your class description has not been linked. This means that the class dictionary has not been fully loaded, and there may be a problem with this class description ERR_PT_IS_OPENED This error code is used for two different scenarios: (1) You are attempting to open a database using PtBase::Open(), but the PtBase already has an open database. Use PtBase::Close() to close the database before opening another one. (2) You are trying to perform an administrative function such as Reorg or Recover that requires exclusive access to the database, but there is another PtBase that has the database open ERR_PT_NOT_OPENED You are attempting to use a PtBase that does not have an open database. Either you forgot to open it, or your open failed ERR_PT_IS_CONNECTED You are attempting to connect to a server using PtBase:: Connect(), but the PtBase is already connected to a server. Use PtBase:: DisConnect() to disconnect from the server before attempting to connect to another one ERR_PT_NOT_CONNECTED You are trying to use a PtBase that is not connected to a server ERR_PT_NOT_CLOSED The database has not been closed ERR_PT_NOT_ASSIGNED A persistent object or allset has not been assigned to the database. Objects must be assigned to a database before they can be stored or placed in an ondemand, and allsets must be assigned to a database before they can be used to retrieve objects. 5

12 General Kernel Errors to ERR_PT_ALREADY_ASSIGNED You are attempting to assign an object or an allset that has already been assigned. The object or allset still has its original object identity, and the assign failed. If you want to keep the old identity, you can ignore this error. Otherwise, create a new object, or use UnAssign() to remove the existing identity ERR_PT_CANNOT_CREATE_OBJECT The dictionary was unable to create an object. This can happen if you are trying to read an object from the database and you do not have enough RAM for the object, or if the class factory file for a particular class has not been linked into the application ERR_PT_NO_DICTIONARY There is no dictionary for this database ERR_PT_OVERFLOW Your set has just overflowed, i.e., it has exceeded its RAM limitations. This is most likely to occur if you are using a cset and the size of the set exceeds 64K. Change the cset to an lset and run PTXX again ERR_PT_ALREADY_DELETED You are attempting to access an object that has been deleted or has not been stored. This can happen if you delete an object but do not delete references to the object. Another possible reason is that you are unaware of other threads in multi-threaded environments ERR_PT_DIFFERENT_SURR You are using a pointer or reference to an object that has been deleted and whose space has been recycled, so there is a new object in that space. FastObjects does not read the old object or the new one, so your reference has been set to zero ERR_PT_INVALID_PATH You used an invalid path when accessing or creating a database. 6

13 General Kernel Errors to ERR_PT_NO_INDEX You are using PtAllSet::SortByIndex() or PtAllSet::SortBy(), but the index you are specifying does not exist ERR_PT_CONVERSION_FAILED FastObjects was unable to convert this object to the current version. You cannot read this object ERR_PT_SYSTEM_CLASS You attempted to delete a system class from the class dictionary. Because this would corrupt the database, FastObjects will not let you do this ERR_PT_NO_REFERENCE You are trying to use an ondemand that does not contain a valid reference to an object ERR_PT_TOO_MANY_USERS You cannot connect because there are too many connected applications on the server for your current site license. Each computer with an opened PtBase object that is connected to the server counts as a user ERR_PT_BUFFER_CORRUPTED The object buffer for this object seems to be corrupted. There may be a problem with the database or with communications. This problem often goes away if you reorganize the database. Remember to make a backup first! ERR_PT_KEY_NOT_FOUND The index value could not be found ERR_PT_DIFFERENT_CLID The object buffer contains a different class ID than expected ERR_PT_DUPLICATE_KEY You have declared a unique index, and adding this object would result in a duplicate value for the unique index. The Store() has failed, and the indexes are unchanged. 7

14 General Kernel Errors to ERR_PT_CANNOT_CONVERT_OBJECT The requested object could not be converted ERR_PT_MEMORY You have run out of RAM ERR_PT_NO_DATABASE FastObjects was unable to find the database files to open the database. Check the database name. Single backslashes can cause this error (they are escape characters in C++ and C). If the string is a constant in your program, use double backslashes as shown: c:\\admin\\test Do not use single backslashes as shown: c:\admin\test ERR_PT_NO_ACCESS You do not have the required file permissions to access your database files. If you are using a server, make sure that it has the file permissions to open the database. If you are in local mode, make sure that your process has these permissions and that no other application has opened the database files ERR_PT_NO_SHARE FastObjects could not open your database because you are not running SHARE.EXE in a Windows environment ERR_PT_DISK_FULL Your hard disk is full ERR_PT_DATABASE_EXISTS The database already exists ERR_PT_INDEX_EXISTS You are trying to index a member that is already indexed ERR_PT_TYPE_MISMATCH You are trying to add an object to a set, but the object does not belong to the class that the set contains, and nor does it belong to a class derived from this class. This error occurs when you 8

15 General Kernel Errors to are adding objects to a pointer set or an ondemand set and you have set type safety on using the betypesafe keyword in POET.CFG ERR_PT_DATABASE_VERSION This database was created by an older version of FastObjects. Convert it to the current version by running Convert in the Administrator's Workbench ERR_PT_DATABASE_DIRTY An index could not be opened. Run Reorg in the Administrator's Workbench. This error can occur if the database was not closed correctly ERR_PT_ACCESS_DENIED An attempt was made to access an object or a class in a mode that is not valid. Possible reasons: The object is locked or the database is open in read-only mode ERR_PT_OBJECT_LOCKED You tried to lock an object or a class that is locked by another user ERR_PT_CLASS_LOCKED You are trying to lock an allset, but at least one object is locked by another user ERR_PT_OBJECT_MODIFIED An object could not be modified or deleted because another process has changed the object in the meantime ERR_PT_ILLEGAL_LOCKMODE The specified lock mode is not allowed ERR_PT_NOT_LOCKED You are trying to unlock an object that is not locked ERR_PT_NOT_WATCHED You are trying to remove a watch from an object that is not watched. 9

16 General Kernel Errors to ERR_PT_ILLEGAL_WATCHMODE The specified watch mode is not allowed ERR_PT_OBJECT_ALREADY_LOCKED You are trying to lock a set that you have already locked with the same lock mode and depth. Although locks stack for objects, they do not stack for sets, which means that you may set the same lock several times for an object, but a lock on a set must always be different from existing locks ERR_PT_OBJECT_ALREADY_WATCHED You are trying to watch a set that you have already watched with the same watch mode and depth. Although watches stack for objects, they do not stack for sets, which means that you may set the same watch several times for an object, but a watch on a set must always be different from existing watches ERR_PT_NO_OBJDESC There is no entry for this object ERR_PT_NO_CLIENT There is no entry for this client ERR_PT_DUPLICATE_ENTRY The entry already exists ERR_PT_NO_PERS_LOCKDESC The object does not have a persistent lock ERR_PT_DELETE_PERSPROPS The persistent property could not be deleted in the database ERR_PT_RESTORE_PERSLOCK The persistent lock could not be restored. 10

17 General Kernel Errors to ERR_PT_CS_TIMEOUT Timeout occurred while trying to enter a critical section ERR_PT_WATCH_LOCK_COUNT_OVERFLOW The number of watches or locks reaches the limit (0xffff) ERR_PT_NO_DEFAULT This error code is no longer used. The value 0 is now returned ERR_PT_NO_TARGET The watch could not be set because you forgot to specify the target ERR_PT_SIGNIFICANCE You are trying to define an index that is too long. An index definition cannot contain more than 254 characters. In compound index definitions, the sum of all fields cannot exceed 254 characters. This error is reported by PTXX ERR_PT_NOT_INITIALIZED As of the POET 3.0 product, you need to call InitPOET() before you create a PtBase object ERR_PT_BACKUP_ERROR This error occurs only under insufficient memory conditions ERR_PT_BACKUP_RUNNING An online backup is already running on the database ERR_PT_NO_BACKUP_RUNNING You tried to finish an online backup that has not been started ERR_PT_CANNOT_REMOVE_DIRECTORY A directory could not be removed from the disk. 11

18 General Kernel Errors to ERR_PT_MAJOR_VERSION The database contains objects whose format has changed the inheritance hierarchy or other major changes that cannot be versioned on the fly. The database needs to be reversioned using the Versall program or the Administrator's Workbench ERR_PT_INDEX_VERSION The current version of a class has different indexes than the older version. On-the-fly versioning does not work if the indexes have changed. You must regenerate the index using Reindex() or Reorg() ERR_PT_FACTORY_ENTRY_NOT_FOUND The factory for a class could not be found ERR_PT_NO_DICTIONARY_FOUND The dictionary could not be found. This can happen if somebody moved the database or the dictionary. If you specified a relative dictionary path when you created the dictionary, the dictionary must always be reachable via this path. If it contains an absolute path for the dictionary, the dictionary cannot be moved unless you use configuration files to specify a name for the dictionary with an entry in your POET.CFG. To see the physical name for the dictionary, try to open the database in the Workbench and look at the physical name entry for the dictionary. Keep in mind that the server uses a config file too ERR_PT_NO_DICTIONARY_ACCESS You do not have the required file permissions to access your dictionary files. If you are using a server, make sure that it has the file permissions to open the dictionary. If you are in local mode, make sure that your process has these permissions and no other application opened it exclusively ERR_PT_FACTORYTAB_MISMATCH Your application is trying to open a database whose dictionary does not match your class factory. At least one class contained in your class factory is not registered in the dictionary, or contains a version timestamp that does not match any version in the dictionary. This may simply mean that you are trying to open the wrong database. If you have one database for inventory and another for your stamp collection, you will get this error if you try to open the inventory database with your stamp collection management program. When the dictionary was created, PTXX 12

19 General Kernel Errors to generated the correct factory tables for this dictionary. Recompile the application with the appropriate factory files generated by PTXX ERR_PT_DATABASE_MISMATCH The dictionary for this database now has different indexes than those currently found in the database. The database must be updated to the newest version of the dictionary indexes using PtBase::Update() or the FastObjects Administrator's Workbench ERR_PT_NO_DICTIONARY_NAME An attempt is being made to create or open a database that has no dictionary name ERR_PT_DICTIONARY_NAME_TOO_LONG The dictionary name is too long to be used in a database. The total length of the dictionary name plus the name for the dictionary's server must be no longer than 468 characters, which should be sufficient for a logical dictionary name ERR_PT_DICTIONARY_MISMATCH The dictionary does not match the database. You can only open a database with the dictionary that created it. Each dictionary has a unique identifier that is recorded in any database that the dictionary creates. You cannot open a database if this identifier does not match the dictionary ERR_PT_DICTIONARY_VERSION The dictionary has an older version; convert it ERR_PT_DICTIONARY_DIRTY The dictionary is dirty; do a reorg ERR_PT_DESCS_ALREADY_OPENED The descriptions of user classes are already opened ERR_PT_LINK_DESC_DOUBLE A class has multiple descriptions. 13

20 General Kernel Errors to ERR_PT_LINK_DESC_ALREADY_SET A type or member description is already linked to another description ERR_PT_LINK_DESC_LINKNAME A type or member description is linked to another description with a different link name ERR_PT_LINK_DESC_CLASSTYPE A description must be linked to a PtMetaClass description ERR_PT_LINK_DESC_NEWER_FOUND A description will be linked to a description with a newer version ERR_PT_LINK_DESC_ALREADY_DELETED A description is linked to a description which no longer exists ERR_PT_LINK_REFERENT The referenced class description was not found during the dictionary link ERR_PT_LINK_INHERIT The base class description was not found during the dictionary link ERR_PT_LINK_INDEX A problem occurred with an index description during dictionary link. This error occurs if there are index names which do not differ in the first 23 characters. (The significance of index names in the dictionary is 23. That is, they must be unique in the first 23 characters.) Please change your index names accordingly ERR_PT_BUCKET_NOT_FOUND A class description is missing or is not usable. For a schema that uses fulltext indexes, check the installation of the fulltext index. 14

21 General Kernel Errors to ERR_PT_BUCKET_NO_CLASSDESC Cannot find a specific class description in the class dictionary ERR_PT_INTERNAL_TXN_MGR_NULL The pointer to the internal transaction manager for the PtBase is not set. Cause is unknown ERR_PT_ILLEGAL_INHERITANCE Illegal inheritance relationship due to mixed virtual/non-virtual inheritance ERR_PT_IS_DICTIONARY A dictionary was opened with a PtBase or PtMasterDict instance; use a PtClassDict instance instead ERR_PT_LINKCOUNT_TOO_LOW The DeepForget() algorithm detected PtObjects references without proper linkcount ERR_PT_REVLOG The dictionary has no revision log ERR_PT_RESOURCE_LIMIT_REACHED Could not allocate file, thread, mutex, or memory ERR_PT_INTERNAL_ERROR An internal FastObjects error occurred. You can also obtain more information about the error by using the PtBase::getLastBaseError() method. For further information, contact Poet Technical Support ERR_PT_QUEUE Unable to use the query specification; error in reading from or writing to the query queue ERR_PT_QUEUE_EMPTY The query specification is empty. 15

22 General Kernel Errors to ERR_PT_QUEUE_FULL The query specification is full ERR_PT_SYNTAX The query specification is incorrect. Make sure that your braces match, that your SortBy() clauses precede the data member specifications, etc ERR_PT_NO_MEMBER You are trying to query on a member that does not exist, or you are trying to build an index and your index definition includes fields that are not in the class declaration ERR_PT_UNCOMPARABLE No compare function for a type ERR_PT_MEMBER_TYPE_MISMATCH The type of the queried member has changed (object versioning) ERR_PT_MBACC_NO_MEMBER There is no member description available for the member specified ERR_PT_MBACC_NO_OBJECT There was no object specified ERR_PT_MBACC_TYPE_MISMATCH The type specified does not match the type of the member ERR_PT_GENQRY_NO_MEMBER The member specified is not valid ERR_PT_GENQRY_NO_CLASSDESC The class description could not be found. 16

23 General Kernel Errors to ERR_PT_GENQRY_TYPE_MISMATCH The member specified has a wrong type ERR_PT_GENQRY_WRONG_USAGE The operation specified is not allowed in this context ERR_PT_CLASS_DESC_IN_USE Can occur when attempting to delete a dictionary class description while the dictionary is in use ERR_PT_NO_RESULT_COLLECTION There is no result collection specified ERR_PT_NO_TIMEZONE_INFORMATION Timezone information could not be retrieved from the operating system ERR_PT_NO_TIME_INFORMATION Time information could not be retrieved from the operating system ERR_PT_FOREIGN_REFERENCE You are attempting to perform a Delete(), set a lock, or set a watch that involves referenced objects, and at least one of these references is a foreign reference; i.e., it points to an object in a different database ERR_PT_BASE_DIRECTORY_LOCKED Object references to objects in a different database (so-called foreign database references ) use a database identifier for the foreign database. These foreign database identifiers are mapped to the database names in a PtBase directory. This error can occur in rare circumstances if this PtBase directory is locked by another user. For example, if two clients are concurrently attempting to establish a foreign reference in a database not yet listed in the PtBase directory ERR_PT_BASE_DIRECTORY_NO_DATABASE The database files were not found in the PtBase directory. (Refer also to ERR_PT_BASE_DIRECTORY_LOCKED above.) 17

24 General Kernel Errors to ERR_PT_OBJECT_MOVED The object has been moved to another database ERR_PT_SAME_BASE The object cannot be copied to the source database ERR_PT_DEST_OPEN The target database is already open ERR_PT_DATABASE_INCONSISTENT One of the database files does not exist or is corrupt. This can occur if the length of the database file does not match with the actual length of the file. You can usually resolve this problem by performing the following steps: 1. Make a copy of all the database and dictionary files. 2. Check the availability of the database files. 3. Try to run Reorg with force mode. Check/Repair database. This symptom can occur after hard disk problems. You may want to return to using the backup of your database ERR_PT_CANNOT_CREATE_DEST_DIRECTORY The directory for the destination database cannot be created ERR_PT_CANNOT_CREATE_STATUS_FILE The status file inside the destination directory cannot be created ERR_PT_CANNOT_DELETE_STATUS_FILE The status file inside the destination directory cannot be deleted. 18

25 General Kernel Errors to ERR_PT_STATUS_FILE_EXISTS A previous database copy operation failed ERR_PT_RECOVERY_ERROR A recovery attempt was unsuccessful ERR_PT_RECOVERY_NO_ACCESS The recovery file is not accessible or does not exist ERR_PT_RECOVERY_WRONG_FORMAT Recovery file was created with different version or format ERR_PT_RECOVERY_INVALID_FILE Recovery file is not valid for recovery ERR_PT_RECOVERY_DATABASE_NO_ACCESS The database is not accessible for recovery ERR_PT_RECOVERY_NO_FILE The recovery file does not exist or cannot be accessed ERR_PT_RECOVERY_NO_SPACE There is not enough disk space for the recovery file ERR_PT_RECOVERY_NOT_ENABLED Recovery is not enabled ERR_PT_RECOVERY_ALREADY_ENABLED Recovery is already enabled ERR_PT_RECOVERY_EOF The recovery file ends unexpectedly. 19

26 General Kernel Errors to ERR_PT_RECOVERY_FILE_EXISTS A recovery file with the same name already exists ERR_PT_RECOVERY_READ_ONLY Recovery operations are not allowed while the database is opened in read-only mode ERR_PT_RECOVERY_ILLEGAL_USAGE Operation is not allowed while recovery is enabled ERR_PT_WRONG_PASSWORD You entered the wrong password ERR_PT_USERNAME_NOT_UNIQUE You are trying to add a user by specifying a user name that already exists. User names must be unique ERR_PT_ALREADY_IN_GROUP You are trying to add a user to a group, but the user is already in this group. A user cannot be in the same group more than once ERR_PT_AUTHORIZATION_NOT_ENABLED You are trying to perform user authorization tasks on a database that does not have user authorization. Call PtBase:: EnableAuthorization() to enable authorization ERR_PT_AUTHORIZATION_ALREADY_ENABLED You are trying to use PtBase:: EnableAuthorization() for a database that already has authorization enabled ERR_PT_PASSWORD_EMPTY The password field is empty ERR_PT_USERNAME_NOT_FOUND This user does not exist. 20

27 General Kernel Errors to ERR_PT_NOT_LOGGED_IN You cannot perform this operation because user authorization is enabled and you are not logged into the database ERR_PT_LOGIN_FAILED Your login failed ERR_PT_NO_PERMISSION You do not have permission to access this class or object ERR_PT_OBJECT_NOT_COPIED This object cannot be copied ERR_PT_NO_PARENT The workspace has no parent base ERR_PT_WRONG_PARENT The workspace and the parent base specified do not match ERR_PT_WSLIST_LOCKED The workspace list is already locked ERR_PT_WSLIST_NOT_LOCKED WorkspaceList was not locked ERR_PT_WORKSPACE_NOT_UNIQUE The workspace name specified is not unique ERR_PT_WORKSPACE_NOT_FOUND The workspace could not be found. 21

28 Client/Server Communication Errors to ERR_PT_CHECKOUT_RUNNING A checkout is already running ERR_PT_CHECKOUT_NOT_RUNNING There is no checkout running ERR_PT_CHECKIN_RUNNING A checkin is running ERR_PT_NOT_ALLOWED_IN_TRANSACT This operation is not allowed within a transaction ERR_PT_OBJECT_ALREADY_CHECKED_OUT The object is already checked out ERR_PT_WORKSPACE_NOT_OPEN The workspace used is not opened ERR_PT_NO_WORKSPACE The workspace is not valid ERR_PT_NO_USEROBJECT The object is not a user object Client/Server Communication Errors to ERR_PTC_INACTIVE There is no active communication link ERR_PTC_STATUS The communication status is invalid. 22

29 Client/Server Communication Errors to ERR_PTC_PROTOCOL A communication protocol error occurred ERR_PTC_DATA_LOST A data transmission failed to transmit all data, which generally indicates a problem in your network installation ERR_PTC_EMPTY An empty packet was received ERR_PTC_DISCONNECT The physical connection was broken ERR_PTC_PROTOCOL_VERSION The internal FastObjects protocol does not match between client and server; this can happen when you try to connect a newer client to an older server. Clients of versions prior to version 5.0 of the POET product cannot communicate with POET 5.0 servers ERR_PTC_TIMEOUT A communications operation has timed out. If you override PtExcMgr::Error(), it will return this error code when the timeout is exceeded. The default timeout value is 30 seconds; you can change this value by setting the corresponding entry in the FastObjects configuration file ERR_PTC_NOCONNECTION The host you specified is not available or reachable through the underlying network provider ERR_PTC_HOSTNAME The host name specified could not be resolved. To resolve a host name, FastObjects invokes the function gethostbyname() (for TCP/IP addresses). If this function fails, the hostname is not contained in the system hosts file. You can always specify hosts using numerical addresses such as

30 Client/Server Communication Errors to ERR_PTC_SERVICE The service name specified could not be resolved. To resolve a service name, FastObjects invokes the function getservbyname() (for TCP/IP protocol services). If this function fails, the service name is not contained in the system services file. Make sure that you have the same definition of the service as the FastObjects Server has. You can always specify services using numbers such as This is also the default value for the poet service ERR_PTC_SOCKET This usually happens if no more sockets can be created. For Novell LWP users: Run lwpcon, LocalWorkstation Tables TCP Connection Table to see the sockets currently in use ERR_PTC_ILLEGAL_OPCODE Illegal opcode ERR_PTC_NO_SERVICE The client requested a functionality the server does not have ERR_PTC_MAXUSER The maximum number of concurrent users of the FastObjects Server was reached ERR_PTC_NW_NOT_LOGGED_IN NetWare requires a user that is logged in ERR_PTC_NW NetWare error ERR_PTC_NO_MORE_SOCKETS The network layer was not able to create a socket. See ERR_PTC_SOCKET ERR_PTC_SOCK_NOT_VALID Socket handle invalid. 24

31 Client/Server Communication Errors to ERR_PTC_PROTOCOL_UNAVAILABLE The protocol specified is not available by the transport layer or the FastObjects communication module. The default protocol is tcp ERR_PTC_NO_PARTNER FastObjects could connect to the host specified, but there is no server running. Make sure to have the same services on client and server and that the server can use it ERR_PTC_UNKNOWN_ERROR An unexpected network error occurred. Contact the technical support ERR_PTC_WOULD_BLOCK An operation would have been blocked and was therefore aborted ERR_PTC_INTERRUPTED Operation was interrupted ERR_PTC_MODE_UNAVAILABLE The mode specified is not available ERR_PTC_ADDRESS_INVALID The address specified is not valid ERR_PTC_MESSAGE_TOO_LARGE Message is too large ERR_PTC_INVALID_PARAM Invalid parameter ERR_PTC_NO_ADVERTISING No service advertising available. 25

32 Database Validity Check Errors to ERR_PTC_ADDRESS_IN_USE The network address is in use by a running application or an abnormal terminated process (for example, a FastObjects server) ERR_PTC_NO_LICENSE Obsolete error code. Instead for errors regarding licensing the error range to is used. See Licensing Errors ERR_PTC_NO_VALID_LICENSE Obsolete error code. Instead for errors regarding licensing the error range to is used. See Licensing Errors ERR_PTC_CHECKSUM Checksum error on communication level ERR_PTC_SERVER_SHUTDOWN Connection refused because server shutdown was initiated Database Validity Check Errors to ERR_PT_DATABASE_NEWER_VERSION Database requires newer FastObjects version ERR_PT_ROOTBLOCK_CHECKSUM Database header has an invalid checksum ERR_PT_REINDEX_NOT_ALLOWED Reindex is not allowed (e.g., for onefile database) ERR_PT_FILE_NOT_OPEN One of the files of a multi-file database has not yet been opened. 26

33 Database Validity Check Errors to ERR_PT_FILE_INCONSISTENT_FILENAME One of the files of a multi-file database has an inconsistent name ERR_PT_FILE_INCONSISTENT_FILEKIND One of the files of a multi-file database has an inconsistent filekind ERR_PT_FILE_INCONSISTENT_BLOCKZIZE One of the files of a multi-file database has an inconsistent blocksize ERR_PT_FILE_INCONSISTENT_FIRST_CLUSTER_ID One of the files of a multi-file database starts with an inconsistent first cluster id ERR_PT_FILE_TOO_LARGE The database file would grow larger than defined ERR_PT_FILE_SPLITTED The operation is not allowed on a multi-file database ERR_PT_CHECKSUM_ERROR The data record has an incorrect checksum ERR_PT_NEED_RECOVERY Database requires recovery; close and reopen it ERR_PT_NEED_DATABASE_CHECK Database needs to be checked; close it and perform database check or reorg ERR_PT_FILE_INCONSISTENT_TIMESTAMPS One of the database files has an inconsistent timestamp and the database cannot be opened. You can usually resolve this problem by performing the following steps: 1. Forcefully disable recovery. 27

34 Database Validity Check Errors to Try to open the database. 3. If the error still occurs, reindex the database. 4. Re-enable recovery. You may also find the following detailed information useful. The data file (objects.dat), the index file (objects.idx) and the recovery file (data0000.rcy, by default in subfolder "recovery") contain a creation and modification timestamp. These timestamps are used to check whether these files fit together. If one of the timestamps does not match the others, the database cannot be opened, in which case this error code is returned. Generation of this error code prevents the database from being damaged as the result of an outdated recovery file or non-matching index file. A common scenario for a non-matching recovery file is when you open a backup of a database that was created during external backup. If you copy the database files while external backup is running, you have to consider whether the recovery file should be part of the backup. For a snapshot of the database, do not copy the recovery file. If you restore the backup of the database to the same location, the recovery folder of the overwritten database might remain. A subsequent opening of the database will check the timestamps and determine that the modification timestamp of the recovery file is newer than the modification timestamp of both database files. Error will be returned. In this scenario it is safe to forcefully turn off recovery because the database was intended to be a snapshot and, more important, the recovery file does not match the database. You can do this by using forcedisablerecovery with the PtADMIN command line tool, from either the Java binding or C++ binding. For a step-by-step description, refer to the FastObjects Administration Guide. Do not forget to enable recovery afterwards. This error may also result if an index file does not match the data file. This can happen if a copy operation fails that was intended to replace the database files, and only the data file was replaced as a result. Again, you have to forcefully turn off recovery. Even a valid recovery file cannot be recovered to a database that has an invalid index file. If the database still cannot be opened, you have to reindex the database. 28

35 Database Encryption and Communication Encryption Errors to Do not forget to enable recovery afterwards ERR_PT_IS_REPLICATION_LOG The file is a replication log file and cannot be used as an incremental backup file ERR_PT_IS_INCREMENTAL_BACKUP The file is an incremental backup file and cannot be used as a replication log file ERR_PT_FILE_INCONSISTENT_CREATIONSTAMPS One of the database files has an inconsistent creation timestamp. Either the recovery file or the index file does not correctly relate to the database file. If the problem is with the recovery file, disable recovery. If the problem is with the index file, do a database reorganization ERR_PT_DB_DIFFERENT_CREATIONSTAMPS One of the databases has a different creation timestamp ERR_PT_DB_DIFFERENT_TIMESTAMPS One of the databases has a different modification timestamp ERR_PT_DATABASE_CORRUPTED_FSM The database free store management is corrupted. The database should be checked and/or reorganized Database Encryption and Communication Encryption Errors to ERR_PT_INVALID_ENCRYPT_DESC Encryption description is not valid. You set a wrong Module or Type name. 29

36 Database Encryption and Communication Encryption Errors to ERR_PT_ENCRYPTION_DESC_FILE_HAS_WRONG_FORMAT Encryption description file has wrong format. Please make shure the file you set in the FastObjects configuration file is an encryption description file created with the FastObjects API ERR_PT_ENCRYPTION_DESC_IS_ALREADY_SET Encryption description is already set. It is not allowed to set the description twice, Clear the description first ERR_PT_ENCRYPTION_DESC_IS_NOT_SET Encryption/recoding description is not set. You can not call this function without a encryption or recoding description ERR_PT_ENCRYPTION_PARAMSET_HAS_DUPLICATE_ENTRY Parameter set for encryption or recoding has duplicate keys, to avoid you from setting wrong parameters a strict check is done ERR_PT_SECURE_COMMUNICATION_IS_ALREADY_STARTED Secure communication is already started ERR_PT_SSL_CLIENT_CONNECTION Ssl client connection could not be instantiated. The SLL certification session did not succeed, because of Client certificate ERR_PT_SSL_COMMUNICATION Ssl communication instantiating error, wrong synchronisation package ERR_PT_SSL_PORT_PROBLEM Ssl communication instantiating error, no partner on specific port ERR_PT_SSL_SERVER_CONNECTION Ssl client connection could not be instantiated. The SLL certification session did not succeed, because of Server certificate. 30

37 Database Replication and Failover Errors to ERR_PT_SSL_CERTIFICATE Ssl servers certificate not valid ERR_PT_SECURE_KEY Key not valid, please check if the key fits the database encryption ERR_PT_ENCRYPTION_IMPLEMENTATION_IS_NOT_CORRECT Encryption implementation does not return correct values. This error only happens if you have your own encryption implementation ERR_PT_BASE_NOT_ENCRYPTED Database is not encrypted but you entered a key ERR_PT_ENCRYPTION_DESC_FILE_NOT_FOUND Encryption description file is not found. Please make shure the file you set in the FastObjects configuration file is an encryption description file created with the FastObjects API ERR_PT_ENCRYPTION_DESC_FILE_EXISTS Encryption desc file already exists. You can not overwrite the file ERR_PT_ENCRYPTION_IS_DICTIONARY Dictionary encryption is not supported Database Replication and Failover Errors to ERR_PT_REPLICATION_ENABLED The operation is not allowed while replication or incremental backup is enabled. This error happens when using administrative database operations like database reorganization or reindexing while the database still uses replication or incremental backup. 31

38 Database Replication and Failover Errors to ERR_PT_REPLICATION_NOT_ENABLED The operation is not allowed while replication or incremental backup is NOT enabled ERR_PT_REPLICATION_AGENT_NOT_ACCEPTED The agent is not accepted. This error happens when trying to add two replica with the same replication server and replication location or when adding more then one incremental backups ERR_PT_REPLICATION_AGENT_INITIALIZATION The agent could not be initialized. This error happens when incremental backup files that do not exist or can not be accessed ERR_PT_REPLICATION_SEQUENCE The order of replication is not allowed. This error happens when data that should be replicated gets lost due to communication errors and the scenario does not allow loss of data ERR_PT_REPLICATION_RESOURCE The agent could not perform the requested operation because a resource was not available (i.e. hard disk or network connection) ERR_PT_REPLICATION_CASCADED Cascaded replication or incremental backup in replica database is not allowed ERR_PT_REPLICATION_REPLICA_MORE_RECENT The replica database is more recent then the primary database. This error is used by the class PtReplicaDatabaseInfo ERR_PT_REPLICATION_AGENT_WORKLOAD An add replica failed due to high workload. 32

39 This happens during add replica when the load of the primary server is so high, that the replica server can not finish all the work to be in sync with the primary server ERR_PT_REPLICATION_REPLICA_INSTANCE_NOT_EXISTS The replica instance for replication does not exist on the backup server ERR_PT_FAILOVER_REGISTER_OBJECTS Registering client objects on the backup server failed ERR_PT_FAILOVER_DATABASE_MISMATCH The database for failover does not match. This error can happen due to the following conditions: The surrogate of the primary database at open time was greater than the one of the database to reconnect to (backup database). The modification stamp of the primary database at open time was newer than the one of the backup database. The transaction id of the primary database at open time was newer than the one of the backup database. Backup database is older than the time where the primary database was initially opened ERR_PT_FAILOVER_SURROGATE_MISMATCH The highest surrogate does not match. This error can happen whan somebody has fetched surrogates before the last client has been reconnected ERR_PT_FAILOVER_BASE_DICTVERS_MISMATCH Database Replication and Failover Errors to For a base reconnect, the dictionary version on the primary server is higher than on the backup server. 33

40 Sub Schemata Errors to ERR_PT_FAILOVER_BASE_DISK_SURR_MISMATCH For a base reconnect, the disk surrogate on the primary server is higher than on the backup server ERR_PT_FAILOVER_BASE_MOD_STAMP_MISMATCH For a base reconnect, the database open modification time stamp on the primary server is newer than on the backup server ERR_PT_FAILOVER_BASE_TID_MISMATCH For a base reconnect, the transaction ID (TID) on the primary server is higher than on the backup server ERR_PT_FAILOVER_BASE_CREATE_STAMP_MISMATCH For a base reconnect, the database creation time stamp on the primary server is newer than on the backup server ERR_PT_FAILOVER_DICT_DICTVERS_MISMATCH For a dictionary reconnect, the dictionary version on the primary server is higher than on the backup server ERR_PT_FAILOVER_DICT_CREATE_STAMP_MISMATCH For a dictionary reconnect, the dictionary creation time stamp on the primary server is newer than on the backup server Sub Schemata Errors to ERR_PT_UNAVAILABLE_AT_MASTERDICT A dictionary method was called that is not allowed to be called at the master dictionary ERR_PT_IS_MASTERDICT A master dict was opened via a PtClassDict instance; use a PtMasterDict instance instead. 34

41 Sub Schemata Errors to ERR_PT_OUT_OF_CLASS_IDS Unable to handle classes with IDs larger than PtMAX_USER_CLASSID (currently 65300) ERR_PT_UNSPECIFIED_SUBSCHEMA Unable to determine which dictionary is intended. If you are working with multiple schemata, you need to use fully qualified classnames (if class names occur more than once in different schemata). For example, use ERR_PT_MAPPING_TABLE_CORRUPT The master dict was unable to restore the mapping table ERR_PT_NO_EXCLUSIVE_ACCESS Exclusive access is required but was not granted to the database, class dict, or master dict. The database, class dict or master dict might be used by somebody else ERR_PT_UNKNOWN_UNIQUE_ID The master dict was not able to map from the unique to schema local class IDs, because the unique ID was not found in the mapping table ERR_PT_SUBSCHEMA_OPEN A master dictionary was not able to open a required sub schema ERR_PT_NO_SUBSCHEMA A master dictionary requires at least one schema ERR_PT_UNKNOWN_SUBSCHEMA A specified sub schema was not found in the list of sub schemata of a master (e.g., you wanted to work with person@schema1 but you have not added schema1) ERR_PT_QUERY_NOT_ASSOCIATED A query was supposed to run at a set that uses classes from a master dict but the query was not associated with a particular base. 35

42 Licensing Errors to ERR_PT_QUERY_BASE_MISMATCH The query works on a different database than the set is assigned to ERR_PT_CLASSID_NOT_UNIQUE Unable to preserve the class IDs of an added sub schema, because another class with this unique ID is already stored in the mapping table ERR_PT_SCHEMA_FOR_LINK_NOT_OPENED FastObjects was not able to resolve an external reference because the required schema was not opened before linkage ERR_PT_SCHEMA_MODIFIED A sub schema was modified. You need to update the master ERR_PT_IS_BASE A base was opened with a PtClassDict or PtMasterDict instance; use a PtBase instance instead Licensing Errors to ERR_PT_NO_STANDARD_KEY_REGISTERED No standard SDK or Runtime key registered. This error can also happen if your standard license key is expired. You should contact your FastObjects Sales Representative if you have any questions about your licensing needs ERR_PT_WRONG_COMM_LICENSE_KEY_TYPE Client transfered wrong license key type to server. The client transfered a key that is not a communication client key. Please verify the client license configuration ERR_PT_LICENSE_FILE Cannot find or open license file in FastObjects bin directory. 36