This chapter is a reference to VERSANT error codes for all interfaces.
Virtual System 0001-0899
System Level 0900-0999
VERSANT Server 1000-2999
VERSANT Network 3000-3999
VERSANT Manager 4000-4999
Locking 5000-5199
Archive 5200-5399
Query 5400-5599
Version 5600-5799
Checkout/checkin 5800-5999
Schema 6000-6199
Container 6200-6399
Nested Transaction 6400-6999
System Utility 7000-7999
C++ Specific 8000-8999
The format of the error code documentation is:
number handle message
0001 VSL_KEY_INVAL Invalid Key
0002 VSL_BLKSZ_INVAL Invalid block size
0003 VSL_BLKNO_INVAL Invalid block number
0004 VSL_SHM_ALLOC Cannot allocate shared memory
If there are multiple databases running on this machine, shut one or more down (if possible), which will free the shared memory used by these databases. Otherwise you need to reconfigure your kernel so that it can allocate more shared memory resources on demand.
0005 VSL_SHM_ACCESS Cannot access shared memory
0006 VSL_SHM_ELOCAT Cannot locate shared memory
For example, suppose that a database named db1 is visible on both machine host1 and machine host2. Next, suppose that db1 has been started by a connection from host1, which has created a server process, cleanup process, and a page cache in shared memory on host1. Now, if you try to connect to it from host2, you will get this error, because host2 will try to start db1 on host2, even though it is already running on host1.
If a database is in a directory visible to two machines, you can start it on either machine, as long as it has not already been started on the other machine. In the case of the above example where db1 is already running on host1 when you try to make a connection from host2, you could successfully make a connection if you used the syntax db1@host1, but your connection would fail if you used the syntax db1 or db1@host2.
In general, you should always assign ownership of a database to a particular machine, typically configured as a server. Then, from client machines, always access the database with the syntax database@server. This will ensure that the database is started only on the server machine and that server processes and shared memory segments are present only on the server machine.
Ensuring that a database directory is visible only to the server machine will prevent this problem altogether, because it would make it necessary that all client machines access the database with database@server syntax.
0007 VSL_SHM_BUSY Shared memory is in use
0008 VSL_SHM_ERM Unable to remove shared memory
0009 VSL_CLK_ESTART Timer already started
0010 VSL_CLK_NSTART Timer not started
0011 VSL_CLK_ESYNC Timer out of synchronization
0012 VSL_CLK_NBUF No buffer specified
0013 VSL_CLK_ETIMDAT Unable to obtain time of day
0014 VSL_PR_EPTBL Process table invalid
0015 VSL_PR_NSLOT Process table full
0016 VSL_PR_ECREAT Cannot create process
0017 VSL_PR_NARGS Too many arguments
0018 VSL_PR_EXEC Process execution failed
0019 VSL_PR_NEXIST Process does not exist
0020 VSL_PR_EKILL Error killing process
0021 VSL_PR_EWAIT Error waiting for process
0022 VSL_PR_TBLBUSY Process control block is in use
0023 VSL_SEM_EINIT Latch not initialized
0024 VSL_SEM_EFREE Latch already freed
0025 VSL_SEM_EGNCNT Unable to get wait count
0026 VSL_SEM_ETIMEO Latch wait timed out
0027 VSL_SEM_EWAIT Wait error occurred
0028 VSL_SEM_ERETRY Retry count exceeded
0029 VSL_SEM_BUSY Latch is in use
0030 VSL_SEM_EPOST Error posting latch
0031 VSL_SEM_ECREATE Error creating latch
transaction parameter in the database server profile file, profile.be, is set to a higher value than can be supported by your UNIX kernel. The solution is to increase the number of semaphores configured into your kernel.
For example, on Sun machines running SunOS, the kernel parameter of interest is SEMMNS, and the kernel configuration file should be in the file /usr/kvm/sys/sun4c/conf. See the documentation for your machine to determine how to increase the number of sempahores. Your VERSANT platform notes (which are part of your Release Package) will contain default values which are appropriate for most purposes.
For example, the recommended kernel values for SunOs are:
options SHMMNI=200
options SEMMNI=100
options SEMMNS=500
The parameter SEMMNI indicates the maximum number of databases that can be active concurrently. The parameter SEMMNS specifies approximately the total number of database processes allowed for that system.
0032 VSL_SEM_ESETVAL Error setting latch value
0033 VSL_SEM_EGETINFO Error getting latch info
0034 VSL_SEM_ENTRIES No more latch entries
transaction parameter for that database. The solution is to stop the database and increase the value of its transaction parameter in the server process profile file profile.be. See your Database Administration Manual for information about the transaction parameter and how to change its value.
0035 VSL_SEM_UPGRADE Attempt to upgrade latch
0036 VSL_SEM_NOLATCHES No.of latches per execution unit exceeded
0041 VSL_VOL_ECLOSE Unable to close volume
0042 VSL_VOL_EXISTS Volume already exists
0043 VSL_VOL_EREAD Volume read error
0044 VSL_VOL_EWRITE Volume write error
0045 VSL_VOL_ESEEK Seek error on volume
0046 VSL_VOL_EOPEN Unable to open volume
0047 VSL_VOL_ESTAT Unable to get volume status
0048 VSL_VOL_EDESTROY Unable to destroy volume
0049 VSL_VOL_INVALID Invalid volume specified
0050 VSL_EINPTR Pointer is invalid
0051 VSL_EBUFSIZ Buffer size is wrong
0052 VSL_EUSERNAM Unable to get user name
/etc are different on the two machines. The solution is to run ypmake on the NIS server to propagate the /etc/passwd file to your client machine. On SGI machines that run NIS, your application has to be linked with the option -lsun.
0053 VSL_MEM_NOMEM Out of process memory
swap_threshold in your application process profile file. When you use VERSANT, the recommended swap space-to-RAM ratio is 3:1. See your Database Administration Manual for information about the swap_threshold parameter.
0054 VSL_SHM_EEXIST Shared memory exists
stopdb utility, which will remove the shared memory segments. See your Database Administration Manual for information about the stopdb utility.
0055 VSL_PR_NPERM No permission to kill
0061 VSL_FIXED_DEV_ZERO Cannot open "/dev/zero"
0062 VSL_FIXED_MAP Cannot map memory
0063 VSL_FIXED_ADDRESS Mapped at wrong address
0064 VSL_FIXED_UNMAP Cannot unmap memory
0065 VSL_FIXED_CREATE Cannot create segment
0066 VSL_FIXED_ATTACH Cannot attach segment
0067 VSL_FIXED_DETACH Cannot detach segment
0068 VSL_FIXED_REMOVE Cannot remove segment
0071 VSL_EOSCPATH Error while resolving configuration
0072 VSL_EDBPATH No database path
0073 VSL_EDBIDPATH No osc-dbid path
0074 VSL_EDBIDNODE No osc-dbid node name
0075 VSL_ECONFIGFILE Error in configuration file specified
0076 VSL_ELIBSYSINFO Error in versant_root/lib/sysinfo
0077 VSL_EUNKNOWNKEYWORD Unknown keyword
0078 VSL_ENOLOCALHOSTINFO No Versant root found for local info
0079 VSL_ENOVERSANTROOT No Versant root
0080 VSL_ESTRINGTOOLONG Keyword or string too long
0081 VSL_EINVALIDVERS Version number is invalid or non-numeric
0082 VSL_STAT_NBUF No buffer specified
0083 VSL_STAT_EOSSTATS Unable to obtain operating system statistics
0084 VSL_EAUTHPATH No user authentication program path
0101 VSL_EXEC_ASYNC Async EXEC of: %s failed, errno: %d
0102 VSL_EXEC_SYNC Sync EXEC of: %s failed, errno: %d
0111 VSL_MSG_CANT_GET_QUEUE Cannot get message queue
0112 VSL_MSG_CANT_SEND Cannot send the message
0113 VSL_MSG_CANT_RECEIVE Cannot receive the message
0114 VSL_MSG_CANT_CONTROL Cannot manipulate the queue
0115 VSL_MSG_EXIST Message queue exists
0121 VSL_MUT_EINIT Error while initializing a mutex
0122 VSL_MUT_ELOCK Error while locking a mutex
0123 VSL_MUT_EUNLOCK Error while unlocking a mutex
0124 VSL_MUT_EDESTROY Error while destroying a mutex
0125 VSL_TLS_ECREATE Could not create tls key
0126 VSL_TLS_EGET Could not get tls key
0127 VSL_TLS_ESET Could not set tls key
0128 VSL_THR_ECREATE Error in create new thread
0129 VSL_CV_EINIT Error while initializing a condition variable
0130 VSL_CV_ELOCK Error while locking a condition variable
0131 VSL_CV_EUNLOCK Error while unlocking a condition variable
0132 VSL_CV_EDESTROY Error while destroying a condition variable
0133 VSL_FILE_OPEN Error while opening file $(file)
0134 VSL_FILE_WRITE Error while writing to file $(file)
0135 VSL_FILE_MMAP Error while mapping a file to memory
0136 VSL_TLS_EDELETE Could not delete tls key
0137 VSL_FILE_SEEK Error during a seek on file $(file)
0138 VSL_FILE_READ Error while reading file $(file)
0139 VSL_FILE_FSYNC Error while syncing file $(file) to disk
0140 VSL_FILE_TRUNCATE Error while truncating file $(file)
0141 VSL_FILE_EEXIST File $(file) does not exist
0142 VSL_FILE_EACCES Error while acessing the file $(file)
0143 VSL_FILE_EXISTS File $(file) already exists
0144 VSL_FILE_EOF End of file detected while reading file
0145 VSL_FILE_UNABLE_TO_LOCK Unable to lock file
0146 VSL_FILE_STAT Error during stat on file $(file)
0147 VSL_THR_JOIN Error while waiting to join a thread
0148 VSL_TRACE_WRONG_VERSION incompatible trace file version
0900 SL_MEM_INVAL_SIZE Invalid size specified
0902 SL_MEM_NOELEMENT Out of elements
0903 SL_MEM_NOMEM Out of heap memory
0911 SL_BAD_LIST Bad list
0912 SL_BAD_ITEM Bad list element
0914 SL_BAD_VSTR Bad vstr (variable length string)
0915 SL_BAD_BUFFER Bad buffer
0931 SL_MSG_WOULDBLOCK Message would have blocked
0932 SL_MSG_ALONE No frontend shared memory
0941 SL_PATH_NOHOME No home environment
0942 SL_DBNAME_TOOLONG Database name too long
0943 SL_USERNAME_TOOLONG User name too long
0944 SL_NODENAME_TOOLONG Node name too long
0950 SL_CANT_CREATE_LOCAL Cannot create local heap
0951 SL_CANT_CREATE_SHARED Cannot create shared memory
0952 SL_CANT_EXTEND_LOCAL Cannot extend local heap
ps aux | grep cleanbe
You can reduce the memory requirements of your application by committing more often and/or using pin regions to hold only necessary objects in memory. See your interface manual for information about commits and pin regions.
0953 SL_CANT_EXTEND_SHARED Cannot extend shared memory
0955 SL_CANT_ATTACH_CONTIGUOUS Cannot attach shared memory contiguously
0956 SL_HEAP_SHOULD_EXTEND Heap should extend
0957 SL_CANT_ATTACH_RIGHT Cannot attach shared memory at the right
address
0958 SL_SEGMENT_TABLE_FULL Shared memory segment table is full
0960 SL_BAD_SHARED_MAGIC Bad shared memory format
0961 SL_WRONG_SDA_VERSION Incompatible version of SDA
0962 SL_WRONG_ODA_VERSION Incompatible version of ODA
0963 SL_CANT_CREATE_KEY Cannot create session key file
0964 SL_ATTACH_EXTEND_SEG Cannot attach extension segments
0965 SL_CANT_RELEASE_LATCH Cannot release latch
0966 SL_CANT_GET_LATCH Cannot get latch
0967 SL_CANT_ALLOC_PAGE Cannot alloc page space
0968 SL_INVALID_HEAP_ADDRESS Invalid heap address pointer
0969 SL_AREA_ALREADY_FREE Area is marked as already free
0970 SL_BAD_PAGE_STATUS Page status is bad
0971 SL_PANIC_MESSAGE [E%d: %s] Versant process terminated in file
%s at line %d
0972 SL_DB_PANIC_MESSAGE [E%d: %s] Versant panicking; SDA has crashed;
database shutting down.
0973 SL_CANT_GET_LATCH_TWICE Cannot get the same latch twice
0974 SL_BUFFER_READ Buffer Read
0975 SL_VERSION_MISMATCH Database is $(db_version). Versant is
$(versant_version). Use different version of
versant or run convertdb
0976 SL_CRASH_NOTALLOWED Backend crash test not allowed
0977 SL_MESSAGE_TEST Test message functionality
0978 SL_MESSAGE_TRACE Trace along error path
1000 SM_E_UNKNOWN Unknown error
1001 SM_E_INTERNAL Internal SM error
1002 SM_E_BAD_NODE_OPER Invalid evaluation operator
1003 SM_E_BAD_PARAM Invalid internal function parameter
1004 SM_E_TOO_MANY_BOOLEANS Too many boolean terms
1005 SM_E_BAD_KEY_LENGTH Invalid key value length
1006 SM_E_BAD_COMPARATOR Invalid comparison operator
1007 SM_E_BAD_USER_PARAM Invalid user input parameter
1008 SM_E_BAD_ACCESS_MODE Invalid access mode
1009 SM_E_KEY_NOT_FOUND Key cannot be found
1010 SM_E_BAD_CSR_POSITION Invalid cursor position
1011 SM_E_BAD_DOMAIN_TYPE Invalid domain specified for attribute
1013 SM_E_TOO_MANY_INDEXES Too many indexes
1014 SM_E_INDEX_NOT_FOUND Index cannot be found
1015 SM_E_BAD_CURSOR_TYPE Invalid cursor type
1017 SM_E_BAD_ATT_TYPE Invalid attribute type
1018 SM_E_BAD_NAME_LENGTH Invalid attribute type
1019 SM_E_VOL_NOT_FOUND Volume not found
1020 SM_E_NDX_NOT_FOUND Index not found
1021 SM_E_CLS_NOT_FOUND Class not found
1027 SM_E_CSR_NOT_OPENED Cursor is not open
1028 SM_E_ID_NOT_FOUND Id not found in the catalog
1030 SM_E_NO_SUCH_OBJECT No such object
1031 SM_E_BAD_NDX_ID Bad index id
1032 SM_E_BAD_CSR_ID Invalid cursor id
1033 SM_E_OUT_OF_CSR_SPACE Out of cursor space
1034 SM_E_BAD_OPER Invalid evaluation operator
1035 SM_E_BAD_READ_OFFSET Invalid read offset
1036 SM_E_BAD_READ_LEN Invalid read length
1037 SM_E_NO_SPACE No space
1038 SM_E_NO_SYS_SEGMENTS System segments not found
1039 SM_E_REMOVE_AT_SEG Error removing AT segment
1040 SM_E_ID_EXISTS Id already exists
1041 SM_E_OBJID_NOT_FOUND Object id not found
1042 SM_E_SEG_EXISTS Segment already exists
1043 SM_E_SEG_NOT_FOUND Segment not found
1044 SM_E_SEG_NOT_EMPTY Segment not empty
1045 SM_E_CLS_EXISTS Class already exists
1046 SM_E_CLS_NOT_EMPTY Class not empty
1047 SM_E_BAD_BUFFER_SIZE Buffer size too small
1048 SM_E_BAD_SYS_SEG_ID Invalid system segment id
1049 SM_E_NAME_EXISTS Name already exists
1050 SM_E_BAD_SEG_ID Invalid segment id
1051 SM_E_BAD_CLS_ID Invalid class id
1053 SM_E_BAD_CLS_NAME Invalid class name
1054 SM_E_REMOVE_SYS_CLS Error removing system class
1055 SM_E_REMOVE_SYS_SEG Error removing system segment
1056 SM_E_BAD_SEG_NAME Invalid segment name
1057 SM_E_BAD_SYS_CLS_ID Invalid sys class id
1064 SM_E_BAD_CLS_TYPE Invalid class type
1068 SM_E_ATT_NOT_FOUND No entry in attribute-segment
1071 SM_E_IDS_NOT_FOUND No entry in id segment
1072 SM_E_SEGMENT_REFCNT Invalidate segment reference count (0)
1073 SM_E_SEGMENT_NOT_FOUND No entry in segment-segment
1074 SM_E_SEGMENT_OWNERCNT Segment owner count error
1075 SM_E_SEGMENT_OPEN_ERROR Segment open error
1076 SM_E_NDXSEG_NOT_FOUND Index segment not found
1077 SM_E_MAX_OPENFILES Number of open files already maximum
1078 SM_E_CLS_SEG_NOT_FOUND Class segment not found
1079 SM_E_NDX_SEG_NOT_FOUND Index segment not found
1080 SM_E_BAD_NDX_TYPE Wrong index type
1081 SM_E_BAD_MO_TAILINFO Inconsistent medium object tail information
1083 SM_E_OUT_OF_VOL_SPACE all volumes exhausted
addvol utility to add data volumes. See your Database Administration Manual for information about the addvol utility.
The database configuration parameter sysvol in the server process profile file determines the initial size of the database when it is created, and changing it after a database has been created will have no effect. See your Database Administration Manual for information about creating databases.
1099 SM_E_SDA_CRASHED SDA has crashed
1100 SM_E_NOMEM Out of backend heap memory
1102 SM_E_FATAL Storage manager encountered fatal error %d in
module %d location id %d
1103 SM_E_SDA_INIT Error in Storage manage shared memory
initialization
1104 SM_E_CNVT_UNDERFLOW Key conversion underflow
1105 SM_E_CNVT_OVERFLOW Key conversion overflow
1106 SM_E_CNVT_WRONG_TYPE Invalid type for key conversion
1107 SM_E_INCOMPAT_KEY_TYPE Incompatible key type
2500 SM_LOG_INVALID_PARM Invalid parameter to logging interface
2501 SM_LOG_NO_ACTIVE_TR No active transaction
2502 SM_LOG_FATAL Fatal unrecoverable error
2503 SM_LOG_CANNOT_EXTEND raw device, can not extend
2504 SM_LOG_NO_LOG_ADR Invalid log record address
2505 SM_LOG_NO_PLOG_SPACE Out of physical log file space
2506 SM_LOG_NO_LLOG_SPACE Out of logical log file space
2507 SM_LOG_NO_PLOG_FILE No/invalid physical log volume
2508 SM_LOG_NO_LLOG_FILE No/invalid logical log volume
2509 SM_LOG_NOPACKSPACE Unable to re-organize/pack file
2510 SM_LOG_INVALID_PLOG Invalid physical log version, physical
recovery disabled
2511 SM_LOG_INVALID_LLOG Invalid logical log version, logical
recovery disabled
2512 SM_LOG_INCOMPAT_VERSION Log file and utility versions are
incompatible
2513 SM_LOG_BAD_BGN_REC Deferred begin record is wrong
2514 SM_LOG_BAD_LOGPTR Log Pointer corrupted
2515 SM_LOG_NO_PARENT_TR No parent log pointer
2516 SM_LOG_OVERFLOW Number overflow
2517 SM_LOG_MEM_CORRUPTED Log memory corrupted
2518 SM_LOG_FILE_CORRUPTED Log file corrupted
2519 SM_LOG_UIDTOOSMALL Invalid uid
2520 SM_LOG_DISABLE_CP Error in disable log CP
2521 SM_LOG_PLOG_NOT_EMPTY Plog file not empty
2522 SM_LOG_LLOG_NOT_EMPTY Llog file not empty
2523 SM_LOG_CANNOT_EXTEND_PLOG Plog on raw device cannot extend
2524 SM_LOG_CANNOT_EXTEND_LLOG Llog on raw device cannot extend
2525 SM_LOG_WRONG_DB_VERSION DB version not right, need to run convertb
2526 SM_LOG_NOT_EMPTY Log files have to emptied by stopdb and
startdb in order to run convertdb
2527 SM_LOG_END_OF_UNIT End of log unit reached
2701 SM_E_BADCURSOR Bad scan cursor
2702 SM_E_BADSCANTYPE Scan type incompatible with operation
2703 SM_E_BADRELOCATION Incorrect relocation
2704 SM_E_NOFILENO File number not found
2705 SM_E_BADFILENO Invalid file number
2706 SM_E_BADSCANID Invalid scan id
2707 SM_E_SCANFILENOTMATCH Scan id does not match file number
2708 SM_E_NOMOREMEMORY3 No more memory space for scan table
2709 SM_E_ACCESSVIOLATION Attempt to update a read file
2710 SM_E_NONEXTOID3 No next object id
2711 SM_E_NOPREVOID3 No previous object id
2712 SM_E_PAGENOTFOUND Page not found in buffer pool
2713 SM_E_NOFREEBUFFERS No more free buffers
2714 SM_E_WRONGBUFFER Accessing the wrong buffer
2715 SM_E_NULLFIDPARM Null file id parameter
2716 SM_E_NULLPIDPARM Null page id parameter
2717 SM_E_BADMODEPARM Bad file mode parameter
2718 SM_E_INVTIMESTAMP Timestamp is invalid
2719 SM_E_NONEXTKEY No next key in index
2720 SM_E_NOPREVKEY No previous key in index
2721 SM_E_NOFIRSTINDEX No first key in index
2722 SM_E_NOLASTINDEX No last key in index
2723 SM_E_NONEXTOID2 Current object id is the last for this key
2724 SM_E_NOPREVOID2 Current object id is the first for this key
2725 SM_E_DUPLICATEKEY Duplicate key found
2726 SM_E_DUPLICATEKEYPTR Duplicate key found in B-tree nodes
2727 SM_E_KEYNOTFOUND Cannot find the key
2728 SM_E_INDEXNUMTOOLARGE Index number too large (create index)
2729 SM_E_KEYLENGTHTOOLONG Key too long (create index)
2730 SM_E_BADSLOTCOUNT Negative slot count
2731 SM_E_KEYALREADYEXISTS Key already exists
2732 SM_E_FILENAMETOOLONG File name too long
2733 SM_E_NOOIDMATCH The index to be deleted is not found
2734 SM_E_ILLEGALCURSOR Bad cursor for index scan
2735 SM_E_VOLNOTOPEN Volume not open
2736 SM_E_NOSUCHFILE No file by that name
2737 SM_E_VOLALREADYOPEN Volume already open
2738 SM_E_FILEALREADYEXISTS File already exists
2739 SM_E_NOMOREMEMORY2 Failed to allocate memory
2740 SM_E_TOOMANYVOLUMES Too many volumes currently in use
2741 SM_E_FILESTILLOPEN Attempt to remove a currently opened file
2742 SM_E_BADOPENFILENUM Open file id is out of range
2743 SM_E_WRONGUSER This open file belongs to another user
2744 SM_E_TOOMANYOPENFILES Too many open files
2745 SM_E_UNKNOWNMODE Unknown access mode
2746 SM_E_MODECONFLICT Access modes conflict
2747 SM_E_UNKNOWNPROT Unknown protection mode
2748 SM_E_PERMISSIONDENIED File permission denied
2749 SM_E_NOPERMISSION No file permission
2750 SM_E_DEVSEEKERROR Device seek error
2751 SM_E_DEVREADERROR Device read error
2752 SM_E_DEVWRITEERROR Device write error
2753 SM_E_MOUNTFAILED Device mount failed
2754 SM_E_DISMOUNTFAILED Device dismount failed
2755 SM_E_VOLNOTMOUNTED Referenced volume not mounted
2756 SM_E_TOOMANYVOLS Too many volumes mounted
2757 SM_E_TOOMANYFILES Too many files created
2758 SM_E_NOSPACEONDISK No space on system disk
2759 SM_E_NOMOREMEMORY0 Insufficient main memory
2760 SM_E_FIDPIDNOTMATCH Volume IDs in the file id and page id are
inconsistent
2761 SM_E_FILENOTINUSE Reference a non-existent file
2762 SM_E_INVALIDPID Invalid page number
2763 SM_E_INVALIDFID Invalid file number
2764 SM_E_BADHEADER Bad volume header
2765 SM_E_NULLPIDPTR0 Null page id pointer
2766 SM_E_NULLFIDPTR0 Null file id pointer
2767 SM_E_NULLBUFPTR Null memory buffer pointer
2768 SM_E_NAMEINUSE File name already in use
2769 SM_E_BADSLOTNUMBER Invalid slot number
2770 SM_E_LISTOFEMPTYSLOTS Empty slots at end of page
2771 SM_E_NOROOMONPAGE No space for expansion on page
2772 SM_E_NULLOIDPTR Null object id pointer
2773 SM_E_NULLPIDPTR2 Null page id pointer
2774 SM_E_NULLFIDPTR2 Null file id pointer
2775 SM_E_NULLPAGEPTR Null page buffer pointer
2776 SM_E_NULLOBJADDR Null object buffer address
2777 SM_E_DELNOEXTOBJ Deleting a non-existing object
2778 SM_E_PAGENOTINFILE Referenced page not in file
2779 SM_E_ENDOFFILE End of file reached
2780 SM_E_OBJWONTFIT No space for object on this page
2781 SM_E_CANTINSERTOBJ Cannot insert object for unknown reason
2782 SM_E_VOLUMESTILLACTIVE Attempt to dismount a volume with open
files
2783 SM_E_NOMORESLICES Attempt to grow a long data item beyond
limit
2784 SM_E_BADDATATYPE Bad data type detected
2785 SM_E_ILLEGALOP Illegal operator found
2786 SM_E_VOLMOUNTED Volume already mounted
2787 SM_E_VOLEXISTS Volume already exists
2788 SM_E_CREATFAILED Volume create failed
2901 SM_LOCK_WOULDBLOCK Lock would have blocked process
2902 SM_LOCK_DEADLOCK Deadlock detected
2903 SM_LOCK_TIMEDOUT Lock wait Timed out
2904 SM_LOCK_DELETED Object deleted
2905 SM_LOCK_NOUPGRADE Lock upgrade not allowed
2906 SM_LOCK_INVALID Invalid lock mode
2907 SM_LOCK_MODLM Lock model modified
2908 SM_LOCK_LMNOTCHANGED Cannot change lock model
2909 SM_LOCK_NOTSUPER Not a superset of Versant Standard Lock
Model
2910 SM_LOCK_NOLKONOBJ Found no lock on obj
2911 SM_LOCK_NO_EXCACC Not holding exclusive access
2912 SM_LOCK_OWN_EXCACC Own exclusive access
2913 SM_LOCK_TS_CHANGED Object may have changed
2921 SM_TR_EXISTS Transaction already exists
2922 SM_TR_FAIL Transaction failed
2923 SM_TR_NOTFOUND Transaction not found
2924 SM_TR_NO_LOG No log => no save point
2925 SM_TR_OBJ_NOTFOUND Object isn't in its hash chain
2926 SM_TR_MULTIPLE_LOCKS Multiple locks on the same transaction and
object
2927 SM_TR_COMPATIBILITY Unknown relation between transactions
2928 SM_TR_LOG_RECORD_TYPE Unknown log record type
2929 SM_TR_CANT_LOCK_OBJECT Cannot lock object
2930 SM_TR_WRONG_COUNT Number of to be recovered transaction changed
2931 SM_TR_RECOVERING Recovery of distributed transactions in
progress
2932 SM_TR_ALREADY_ATTACHED XA transaction already active in backend
2933 SM_TR_NEW_XACTS_BLOCKED Database being stopped; new transactions
are blocked
2934 SM_TR_UPDATES_BLOCKED Database being stopped; new updates are
blocked
2961 SM_SHM_NOT_READY SDA not ready
2962 SM_SHM_SHUTTING_DOWN SDA is shutting down
2981 SM_PS_NOT_FOUND Process not found
2982 SM_CANT_FLUSH_BUFFER Page buffer not flushable
2983 SM_CANT_GET_CONFIG_INFO Unable to obtain configuration info
2984 SM_KILL_FE_CLEANUP Killing the front end cleanup process[%d]
2985 SM_KILL_BE_CLEANUP Killing the back end cleanup process[%d]
2986 SM_KILL_PROCESS Killing process[%d]
2987 SM_DBA_ONLY Only the DBA can access the database currently
2988 SM_DBA_NOT_ALONE Only one process can access the database
2989 SM_DBA_MODE_SET DBA-only mode is already set
2990 SM_DB_IS_UNSTARTABLE Database is unstartable. Use dbinfo to change
mode.
2991 SM_UNSTARTABLE_MODE_SET Unstartable mode is already set
2994 SM_NOT_IN_USER_LIST Not in userlist. Use DBUSER to add.
2995 SM_E_SAMEKEYFOUND Identical key not allowed on unique index
2996 SM_E_OUTOF_CACHE_MEMORY No BufferPool Mem Available
2997 SM_E_INVALIDBUF Buffer not useful for reading
2998 SM_E_BUF_WRONGSIZE Buffer with wrong size
3000 NET_EINPTR Invalid pointer (condef)
3001 NET_ETIMEO Network layer timeout
3002 NET_ENOMEM Unable to allocate memory
3003 NET_ENOPN Connection is not opened
3004 NET_EREAD Network layer read error
This error can occur if the remote inetd daemon is not able to start the ss.d process. In this case, the solution is to update the /etc/inetd.conf file with the correct entry and then restart the inetd daemon. For further information, see the installation instructions in your Release Package.
This error can also occur if the ss.d process is not able to start the server process for the database. This can occur in the following situations:
— if the VERSANT machine configuration file /etc/.oscxxyynn (where xxyynn corresponds to your release number) does not have the right setting for VERSANT_ROOT (which specifies the software root directory,)
— if different releases are running on the client and server and the configuration parameter VERSANT_REL@node has not been properly set on the client machine, or
— if the number of the VERSANT release running on the server is not numerically equal to or greater than the client release number.
This error can also occur if the database server process crashes while the application process was communicating with it, in which case there will be a core dump. This could happen due to resource limitations such as lack of shared memory or semaphores. In this case, the cause is normally written to a file called LOGFILE under the VERSANT database directory. If LOGFILE does not contain the information you need to solve the problem, please call VERSANT Technical Support.
For information on the .oscxxyynn machine configuration file, the VERSANT_ROOT and VERSANT_REL configuration parameters, and the LOGFILE error file, see your Database Administration Manual.
3005 NET_EWRITE Network layer write error
LOGFILE under the VERSANT database directory. If LOGFILE does not contain the information you need to solve the problem, please call VERSANT Technical Support.
3006 NET_ENODNAM Unable to obtain node name
3007 NET_INVREQ Invalid RPC function
3008 NET_INVHOST Invalid host name
3009 NET_ECONNECT Low level connect error
This error can occur if the network inetd process does not know how to start the oscssd (ss.d) server process for a database. In this case, the solution is usually to correct the entry for the oscssd process in the /etc/inetd.conf configuration file and then killing the inetd process with kill -1. For further information, see the installation notes in your Release Package.
This error can also occur if the database server process crashes while the client application process was communicating with it, in which case there will be a core dump. In this case, examine the LOGFILE error file in the database directory to see if you can find the cause of the problem. If you cannot find the problem in LOGFILE, please contact VERSANT Technical Support. For information on LOGFILE, see your Database Administration Manual.
Another cause for this error is that your system has run out of socket descriptors. Socket descriptors and file descriptors are allocated from the same pool. In this case, you need to increase the number of file descriptors configured into your kernel. Since, the number of file descriptors is usually dependent on the number of concurrent users supported by your kernel, it should be sufficient to increase the parameter that sets the maximum number of users. This parameter is usually called MAXUSER. For information on setting the number of users, see your operating system manuals.
3010 NET_TCP_ESOCK Error obtaining socket
3011 NET_INVUSRNM Invalid user name/password string
If this error occurred on a personal computer, it may mean that the configuration parameter VERSANT_USER has not been set to a valid user of the database involved. In this case, set VERSANT_USER to a valid user name or have the dba for the database add the current user name to the list of authorized user.
This error may also mean that your user name is not a valid login name on the remote machine. In this case, have the system administrator for the remote machine to add your user name to the list of valid login names on the machine where the database is located.
3012 NET_INVCONSTR Invalid connection string
3013 NET_ENOSTREAM Expected stream to follow
3014 NET_INVREQ2 Invalid request (lower level)
3015 NET_EPCREAT Unable to start local OBE
3016 NET_ECONLOST Network connection lost
3017 NET_E2MANYOBJ Read/write object count exceeded
3018 NET_ENOOSCGRP OSC_GROUP not on host
3019 NET_NULLDRVR Null driver called
3020 NET_INVSERV Invalid service
oscssd 5019/tcp entry in your /etc/services file does not also exist on the NIS server machine. This solution is to update the /etc/services file on the NIS server with the entry oscssd 5019/tcp. For information, see the installation chapter in your Release Package.If you are not able to get access to the NIS server, you can alternately disable the NIS client software on your machine. One way to disable NIS is by doing the following:
1. Move the ypbind file:
mv /usr/etc/ypbind /usr/etc/ypbind.orig.
Once you disable the NIS client software on your machine, you should be able to run VERSANT successfully.
3021 NET_PURGE_STREAM Unable to purge stream
3022 NET_INVSERV_INFO Invalid server process info
3023 NET_NETWORK_TYPE Invalid network type for server
3024 NET_NETINIT Unable to init server network
3025 NET_INTERNAL Internal error
3026 NET_INITMSG Unable to get initial message
3027 NET_CLIENT_NAME Unable to get peer name of client
3029 NET_ROOTPATH Unable to obtain root path
3030 NET_EXECSERV Unable to exec backend server
3031 NET_NOT_IN_USERLIST Not in userlist. Use DBUSER to add.
adduser utility to add your username to the list of authorized users. For information on the adduser utility, see your Database Administration Manual.
3032 NET_NO_POLLING_YET Polling has not come in yet
3033 NET_OBSOLETE RPC is no longer supported.
3034 NET_UNIMPLEMENTED RPC is not yet implemented
3035 NET_EACCESS User authentication failed
3036 NET_RW_ACCESS_REQUIRED Read/Write access is required
3037 NET_THREADS_REQUIRED You must link with the threads library to use
1p connections
4000 OM_SE_NOT_FOUND Not in the session
4001 OM_SE_ALREADY_IN Already in a session
4002 OM_SE_NAME_EXISTS Session name exists
4003 OM_SE_INVAL Invalid argument
4004 OM_SE_NOT_PARENT Not a parent process
4005 OM_SE_PARENT Parent process
4006 OM_SE_NO_SESSION No session to join
4007 OM_SE_NO_JOIN No dynamic join in
4008 OM_SE_INVAL_USERNAME Invalid username
4009 OM_SE_INVAL_SESSNAME Invalid session name
4010 OM_SE_NOT_IN_THREAD o_beginthread must be called
4011 OM_SE_IN_THREAD o_beginthread already called
4012 OM_SE_NOT_IN_SESSION o_setsession must be called
4013 OM_SE_NOT_IN_TABLE Invalid session specified
4014 OM_SE_INVALID_PID Invalid process id
4015 OM_SE_NOT_THREAD_SAFE O_THREAD option required
4016 OM_SE_SHARE_UNSUPPORTED O_SHARE option unsupported
4017 OM_SE_THREADS_REQUIRED You must link with the threads library to use
shared or threaded sessions
4018 OM_BAD_OPTIONS Invalid options specified by user
4019 OM_SE_SESSION_IN_USE Session is in use by other threads
4020 OM_SE_FE_LOCKFILE_ERR Error opening the FE lock file
4021 OM_TR_NOT_EXISTS No such transaction
4024 OM_TR_EXISTS Transaction already exists
4025 OM_TR_INVAL_ACTION Invalid action
4026 OM_TR_NO_LOGGING Logging not turned on
4027 OM_TR_IS_ABORTABLE Current transaction is abortable
4028 OM_TR_JOIN_IMPLICIT Cannot end transaction implicitly started
by o_joinsession.
4029 OM_TR_BEGIN_IMPLICIT Cannot end transaction implicitly started
by o_beginsession.
4030 OM_TR_IMPLICIT Cannot end implicitly started transaction.
4031 OM_TR_PARENT_PROC Cannot end a transaction in the parent
process.
4032 OM_TR_INVAL_TRNAME Invalid short transaction name.
4033 OM_TR_INVAL_LONG_TRNAME Invalid long transaction name.
4034 OM_TR_BEGIN_FAIL Cannot begin transaction.
4035 OM_TR_DBDOWN Database is down at commit time.
4036 OM_TR_INVALID_TS Failed time stamp validation
4037 OM_TR_INVALID_XID Transaction has either incorrect or no xid
4041 OM_PS_NOT_FOUND No such process
4042 OM_PS_NARGS Too many arguments
4043 OM_PS_WAITING Waiting by someone else
4044 OM_PS_NO_ROOT Process has no root act
4061 OM_SHM_NOT_READY ODA not ready
4062 OM_ODA_STACK_SIZE Stack size mismatch
4063 OM_INVALID_OID_TABLE Invalid object id table
4064 OM_INVALID_CLASS_TABLE Invalid class name table
4081 OM_DB_NOT_FOUND Not connected to this DB
4082 OM_DB_NOT_STARTED Cannot start this DB
4083 OM_DB_NAME_INVALID Invalid DB name
4084 OM_DB_TOO_MANY_CONN too many connections
4085 OM_DB_CANT_DISCONN_PRIM Cannot disconnect primary db
4086 OM_DB_PERSONAL Non-primary connection to personal database
4087 OM_DB_DISCONN_DIRTY Cannot disconnect a database with dirty objects(commit or rollback before disconnecting)
4088 OM_DB_LIST_DB_NOT_FOUND Database cannot be found in this logical
database
4089 OM_DB_LIST_NOT_FOUND Logical database was not initialized
4090 OM_DB_LIST_EXISTS Logical database already exists
4101 OM_LO_FE_IN_USE Long transaction in use
4102 OM_LO_FE_INVAL_OBJECT Unknown object
4103 OM_LO_FE_NO_LONG_TR No long transaction operations
4104 OM_LO_FE_NO_PRIMARY No persistent lock to primary DB
4107 OM_LO_BE_WOULDBLOCK Persistent lock would have blocked process
4108 OM_LO_FE_INVAL Invalid argument for p-lock
4109 OM_LO_BE_LOCK_BROKEN Soft lock was broken
4110 OM_LO_BE_NO_UPGRADE Lock cannot be upgraded
4112 OM_LO_BE_NOTFOUND Lock not found
4113 OM_LO_RESERVED cannot lock comp object
4114 OM_LO_BE_INVAL Invalid argument for p-lock
4115 OM_LO_BE_INCOMPAT incompatible p-locks
4116 OM_LO_PLOCK_NOTFOUND Cannot get persistent lock info
4121 OM_PROF_DONE Processing completed
4122 OM_PROF_SYNTAX Syntax error
4123 OM_PROF_NEGATIVE Negative number
4124 OM_PROF_FILE Cannot open file
4125 OM_PROF_EOF Unexpected EOF
4126 OM_INTERNAL_ERROR Internal OM error
4161 OM_HEAP_NOMEM Out of front-end heap memory
4163 OM_COD_PAGE_INFO Invalid cod page info
4164 OM_COD_ALIGNMENT COD is aligned wrong
4165 OM_COD_ALREADY_FREE COD is already free
4201 OM_LK_MODELEXISTS Lock model object exists
4202 OM_LK_MODELSIZE Lock model size mismatch
4203 OM_LK_MODELTABLESIZE Lock model table size mismatch
4204 OM_LK_NOTALLOWED Operation not allowed
4205 OM_LK_MODELNOTFOUND Lock model object not found
4206 OM_LK_MODELNOTUNIQUE Duplicate lock models
4230 OM_SERIAL_NEG_ADD Negative addend to serial number
4231 OM_SERIAL_OVERFLOW Serial number overflow
4232 OM_REPLICA_MISMATCH Replica db information mismatch
4233 OM_REPLICA_DOUBLE_FAIL Both replica databases in a replica pair
are down
4234 OM_REPLICA_WRONG_LIST Illegal replication deferred list
4235 OM_REPLICA_NET_PARTITION Network partition error
4236 OM_REPLICA_SYN_FAIL Database unavailable for synchronization
4237 OM_REPLICA_SYN_DONE Sync. to replica is done
238 OM_REPLICA_REC_FAIL Recursive failure during polling
4239 OM_FE_DELETE_VERSIONED_OBJS Let front end delete generic or versioned
objects
4240 OM_REPLICA_UNSUPPORTED API does not support replication
4241 OM_SYMT_TABLE_NOT_FOUND Symbol table could not be found
4260 STAT_AUTOCOLLECT_OPEN Could not open statistics automatic collection
file
4261 STAT_AUTOCOLLECT_NOT_STARTED Statistics automatic collection is not turned
on
4262 STAT_AUTOCOLLECT_ALREADY_STARTED
Statistics automatic collection is already
turned on
4263 STAT_ERRORTABLE_NO_MATCH Error or message not found in error table.
4264 STAT_BAD_TIME_ENV Could not parse VERSANT_STAT_TIME environment
variable
4265 STAT_BAD_STATS_ENV Could not parse VERSANT_STAT_STATS environment
variable
4266 STAT_BAD_FUNCS_ENV Could not parse VERSANT_STAT_FUNCS environment
variable
4267 STAT_FILE_WRITE Error writing to statistics automatic
collection file
4268 STAT_INVALID_STATISTIC Invalid statistic
4269 STAT_MISSING_STATISTIC Missing one or more statistic
4280 OM_CM_WRONG_MODE o_beginsession must use O_CONFIG option
4281 OM_CM_INCOMPATIBLE CM does not work with versioned objects or
checkin/checkout
4282 OM_CM_ISSMART Object itself is a smart object. Hence
operations like o_cmsetsmart, o_cmgetsmart are
not allowed on it
4283 OM_CM_ISNOTSMART Cannot apply smart object function on
non-smart objects
4284 OM_CM_HAS_MEMBERS Invalid delete operation attempted on a smart
object which is associated with target objects
4285 OM_CM_HAS_SMART Invalid delete operation. Attempted to delete
a target object which has a smart object
4286 OM_CM_INVALID_MIGRATE
4287 OM_CM_NO_SMART_CLASS Cannot find the class for smart objects
4341 OM_PSR_NOMEM: VQL PARSE ERR Parser unable to allocate memory
4342 OM_PSR_NULLQUERY Null query statement
4343 OM_PSR_SYNTAX_ERROR VQL PARSE ERR: $(errmsg): on/near token
"$(token)".
4344 OM_PSR_MIXED_TYPE: VQL PARSE ERR
Mixed types in set of constants
4345 OM_PSR_TYPE_OVERFLOW: VQL PARSE ERR
Value overflows or underflows
4346 OM_PSR_SET_PREDICATE_NOT_SUPPORTED:VQL PARSE ERR
Multi-value constant in predicate is not
supported in this release.
4347 OM_PSR_ATTR_NOT_FOUND_IN_DOMAIN: VQL PARSE ERR
Attribute $(attr) not in domain
4348 OM_PSR_DOMAIN_NOT_FOUND: VQL PARSE ERR
Domain not found
4349 OM_PSR_NOT_AGG_TO_SCALAR: VQL PARSE ERR
Cannot assign aggregate to scalar
4350 OM_PSR_NOT_AGG_OF_CHAR: VQL PARSE ERR
Aggregates of char not yet supported
4351 OM_PSR_UNSUPPORTED_DBTYPE:VQL PARSE ERR
Encounter Versant Type that is not yet
supported
4352 OM_PSR_OBJCLASS_NOT_FOUND: VQL PARSE ERR
Class for object $(object) not found
4353 OM_PSR_ATTRCLASS_NOT_FOUND: VQL PARSE ERR
Domain for attribute $(attr) not found
4354 OM_PSR_CLASS_NOT_FOUND: VQL PARSE ERR
Class not found.
4355 OM_PSR_TYPE_MISMATCH: VQL PARSE ERR
Type mismatch on attribute $(attr).
4356 OM_PSR_FIND_ATTR_FAIL: VQL PARSE ERR
Failed to find all attribute objects for class
$(class)
4357 OM_PSR_ATTR_NOT_FOUND: VQL PARSE ERR
Attribute $(attr) not found
4358 OM_PSR_NO_VALUE_INSERT: VQL PARSE ERR
No value to insert for Attr
4359 OM_PSR_NULL_RESULT: VQL PARSE ERR
NULL parseresult pointer is passed in
4360 OM_PSR_ATTRS_OUTBOUND: VQL PARSE ERR
Number of Attributes in SELECT, UPDATE, INSERT
list can not be bigger than $(limit)
4361 OM_PSR_PATHATTRS_OUTBOUND: VQL PARSE ERR
Number of Attributes in path expresion can not
be bigger than $(limit)
4362 OM_PSR_BCD_NOT_SUPPORT: VQL PARSE ERR
BCD type input value is not supported yet.
4363 OM_PSR_PARAMETER_TWICE: VQL PARSE ERR
$(index) the parameter can not be used twice
in the query
5000 OB_BADLOCK Illegal lock mode
5001 OB_WLOCK WLOCK is required if an object is modified
5002 OB_NULL NULL object is not allowed
5003 OB_NOPIN Object must be pinned
Pointers are no longer valid after a short transaction ends. The solution is to use a link to maintain references to a persistent object across short transaction boundaries.
This error can also occur if you use a routine that unpins an object and then try to reference it with a pointer, or if you use a routine or parameter that clears that cached object descriptor table, which will invalidate both links and pointers.
For example, consider the following fragment of code in C++.
::dom->beginsession( dbname, NULL ) ;
{
A *pa = new Persistent A(10);
pa->unpinobj();
pa->dirty();
::dom->commit();
}
::dom->endsession();
The exception 5003 is going to be thrown when dirty() is called on the object referenced by the transient pointer pa after the object is unpinned from the object cache. When the dirty() method tries to reference the cached object descriptor table to change the status of the object, VERSANT finds that the object has been released from memory by the use of unpinobj(). In general, you will get this error only when you do something that causes a reference to the cached object descriptor table. See the VERSANT Database Fundamentals Manual for further information about pointers and the VERSANT memory model.
5004 OB_RESIDENT Object cannot be deleted
5005 OB_WRONG_DB Wrong destination db
5006 OB_NO_SUCH_OBJECT Cannot find the object
The link you are using could be dangling because another user has deleted the object pointed to by the link.
This error will also occur if you try to use a link after clearing the cached object descriptor table with a method such as zapcods(). Clearing the cached object descriptor table invalidates all links.
5008 OB_CANT_DEL_CHKOUT_OBJ Cannot delete checked out object which is not a versioned object nor a snapshot object
5009 OB_COMP_OBJ Operation not supported on comp object
5010 OB_ANON_NOT_IN_CONT Anonymous object not in container
5011 OB_NULL_LOID_PTR NULL pointer to logical object id
5012 OB_INVALID_ANON Invalid anonymous object
5013 OB_NULL_CLS_OBJ Object has no class
5014 OB_NOT_ARCHIVED Object was not archived from the list of
input or connected databases
5015 OB_INVALID_OBJ_TYPE Invalid object type
5016 OB_NO_REGION_NUMBERS Ran out of region numbers
5017 OB_ROOT_PIN_REGION Cannot end activity root pin region
5018 OB_BAD_PRINTABLE_LOID Printable LOID is in bad format
5019 OB_LOCK_COUNTER_ZERO Lock counter is zero
5020 OB_LOCK_COUNTER_MAXIMUM Lock counter is at maximum value
5021 OB_NULL_OBJECTS The input objects parameter is NULL
5022 OB_OBJ_NOT_REGULAR Object is not regular
5023 OB_NO_LOCK_TO_DOWNGRADE No locks to downgrade because of no database
connection
5024 OB_DOWNGRADE_TO_NOLOCK_ONLY Can only downgrade to no locks
5025 OB_CANT_DEL_SCHEMA_OBJ Cannot delete class objects, attribute
objects, and method objects
5026 OB_NEWOBJ New object must be dirty
5027 OB_SINGLE_GRW_MRSW Only one process can do group write at any
time in MRSW session
5028 OB_OBJS_FROM_DIFF_DBS All objects need to be from the same database
5200 ARC_BASE
5202 ARC_ARCNAME_TOOLONG The input archive database name is too
long
5203 ARC_NULL_ARCNAME The input archive database name is null
5204 ARC_SAME_DBS The input archive and source databases are
the same
5205 ARC_NULL_OBJECTS The input objects parameter is null
5206 ARC_BAD_ARCNAME The input archive database is invalid:
error when trying to connect to it
5207 ARC_NO_VALID_OBJS No valid objects to archive
5208 ARC_INCOMPLETE The archive was incomplete
5209 ARC_SYSOBJ Trying to archive a system object
5210 ARC_CHKOUT_OBJ Trying to archive a checked out object
5211 ARC_OBJ_NOT_REGULAR Trying to archive an object that is not
regular
5212 ARC_VSNOBJ Trying to archive a versioned object
5213 ARC_CLSOBJ Trying to archive a class object
5214 ARC_CLS_NOT_IN_DB The object's class is not in the source
database
5215 ARC_INCOMPAT_SCHEMA Incompatible class schema between the
source and archive databases
5216 ARC_NO_DBA There is no dba associated with the source
database
5217 RST_ARCNAME_TOOLONG The input archive database name is too long
5218 RST_NULL_ARCNAME The input archive database name is null
5219 RST_BAD_ARCNAME The input archive database is invalid:
error when trying to connect to it
5220 RST_INVALID_OBJ Invalid object
5221 RST_NO_VALID_OBJS No valid objects to restore
5222 RST_INCOMPLETE The restore was incomplete
5223 RST_OBJ_NOT_IN_ARCHIVE The object to restore was not in the
archive database
5224 ARCHIVED_OBJ The object has been archived
5225 OP_NOT_ALLOWED_ON_ARCDB This operation is not allowed on an archive
database
5226 RST_NO_TOMBSTONE_ENTRY There's no tombstone entry for the object
5227 ARC_MORE_THAN_ONE_PDB Cannot archive from more than one personal
database to the same archive
5400 QRY_BASE For query processor
5401 QRY_BAD_OP Bad comparison operator in query
5402 QRY_BAD_ATTRIBUTE Bad attribute in query
5403 QRY_LOID_EXPECTED Attribute type of loid expected
5404 QRY_BAD_DOMAIN Bad attribute to query
5405 QRY_FIRST_PATH_NOT_LOID First attribute in path query is not a link
5406 QRY_TYPETYPE_NOT_SPECIFIED Keytype must be specified for path query
5407 QRY_TYPETYPE_UNKNOWN Invalid keytype in o_predterm
5408 QRY_NOTREACHED Internal error
5409 QRY_ZERO_TERM_BLOCK Predblock with no terms not supported
5410 QRY_OR_BLOCK_NOT_SINGLE O_OR Predblock must have exaclot one member
5411 QRY_NO_CLASS Class name specified in O_(NOT_)ISA_EXACT
operation does not exist
5412 QRY_CLS_WITH_VSTR Cannot have classname with O_SELECT_WITH_VSTR
5413 QRY_OBJ_WITHOUT_VSTR Cannot have vstr_holder without
O_SELECT_WITH_VSTR
5414 QRY_ATTR_WITHOUT_VSTR Cannot have vstr_attr without
O_SELECT_WITH_VSTR
5415 QRY_NO_CLS_WITHOUT_VSTR Must have classname without O_SELECT_WITH_VSTR
5416 QRY_NO_OBJ_WITH_VSTR Must have vstr_holder with O_SELECT_WITH_VSTR
5417 QRY_NO_ATTR_WITH_VSTR Cannot have vstr_attr with O_SELECT_WITH_VSTR
5418 QRY_TYPETYPE_BAD Key typetype cannot be used with this relop
5419 QRY_BAD_KEYLEN Predicate keylen incompatible with typetype
5420 QRY_STPTR_NOT_IMP Typetype O_STPTR_TYPE not implemented
5421 QRY_BAD_OPTIONS Invalid query options
5500 CSR_BASE For cursor processor
5501 CSR_NOEXIST The specified cursor is not currently open
5502 CSR_BAD_FLAGS Reserved values not zero or invalid options
5503 CSR_POS_UNDEF Severe error occurred on previous cursor
operation
5504 CSR_RELS_CURSOR Cannot release cursor
5505 CSR_BAD_OPTIONS O_CSR_DROP_RLOCK bit is not allowed to be set
in the options parameter
5600 VSN_NON_VERSION Must be a versioned object
5601 VSN_CANT_DELE_RELEASE Cannot delete released version
5602 VSN_NO_CLASSOBJ Class object is not allowed
5603 VSN_BAD_STATUS Bad version status
5604 VSN_NO_SUCH_VERSION Version does not exist
5605 VSN_CLASS_NOT_COMP Class of version object not compatible
5606 VSN_BAD_CLASSNAME Bad class name
5607 VSN_CANT_UPD Cannot update working or released version
5608 VSN_NON_LEAF Non-leaf version cannot be transient
5609 VSN_COUT_NON_VSN Cannot version checked out non-versioned
object
5610 VSN_NO_CYCLIC_VDG Cyclic VDG is not allowed
5611 VSN_CANT_VSN_COMPOBJ Cannot version comp object
5612 VSN_BAD_INDEX Bad index into pinned objects
5613 VSN_BAD_DEFAULT No default version
5614 VSN_BAD_VSNNO No version number
5615 VSN_BAD_NODE No node in VDG for version
5616 VSN_BAD_INPUT Bad input arguments
5617 VSN_DELETED Version has been deleted
5800 CHK_BASE For checkin/checkout
5801 CHK_CLS_IN_RW Cannot checkout class object in read-write
mode
5802 CHK_NULL_DBNAME Null database name
5803 CHK_BAD_DBNAME Bad database name
5806 CHK_INTO_WRONG_DB Checkin into wrong DB
5807 CHK_FROM_WRONG_DB Checkout from wrong DB
5808 CHK_CANT_CHK_INTO_PDB Cannot check into personal DB
5809 CHK_CANT_CHK_FROM_PDB Cannot check from personal DB
5810 CHK_CANT_CHKIN_GLOBOBJ Cannot check in global object
5811 CHK_CANT_CHK_SAME_DB Cannot checkin/out from the same DB
5812 CHK_BAD_PLOCK_MODE Bad lock mode
5813 CHK_NULL_CLSNAME Null class name
5814 CHK_CANT_CHECK_SYSOBJ Cannot check system object
5815 CHK_CANT_CHECK_COMPOBJ Cannot check composite object
5816 CHK_NO_PERSONAL_DB Personal db is not allowed
5817 CHK_NULLDB_FOR_NEWOBJ Null database name for checking in new objects
5818 CHK_CANT_CHECKOUT_VSN_FROM_PDB
Cannot checkout a versioned object from
a personal database.
6000 SCH_BASE For schema manager
6001 SCH_CLASS_DEFINED Class already defined
6002 SCH_CLASS_UNDEFINED Class undefined
6003 SCH_NULL_CLSNAME Null class name
6004 SCH_BAD_SUPERCLASS Bad superclass
6005 SCH_BAD_ATTRNAME Bad attribute name
6006 SCH_BAD_METHNAME Bad method name
6007 SCH_BAD_DOMAIN Bad domain
6008 SCH_BAD_BUFFER Bad return buffer
6009 SCH_NOMEM Out of schema memory
6010 SCH_NON_LEAF_CLASS Update to non-leaf class
6011 SCH_BAD_CACHE Bad object cache
6012 SCH_BAD_CLSOBJ Bad class object on disk
6013 SCH_CREATE_CLSOBJ Cannot create class object
6014 SCH_NULL_DBNAME Null database name
6015 SCH_NULL_ATTRNAME Null attribute name
6016 SCH_NULL_METHNAME Null method name
6017 SCH_BAD_ATTROBJ Bad attribute object
6018 SCH_BAD_METHOBJ Bad method object
6019 SCH_CANT_CACHE_GDBCLS Cannot cache global class
6020 SCH_CANT_UPD_CLS Cannot update class
6021 SCH_NO_SUCH_INDEX Non-existing index
6022 SCH_NON_INDEXABLE Attribute can't be indexed
6023 SCH_NULL_OBJECT A NULL object
6024 SCH_DBNAME_NOTMATCH Database name does not match
6025 SCH_CANT_MOVE_VSNOBJ Cannot migrate version
6026 SCH_CANT_MOVE_CLSOBJ Cannot migrate class
6028 SCH_CANT_DROP_INHR_ATTR Cannot drop inherited attribute
6029 SCH_CANT_DROP_INHR_METH Cannot drop inherited method
6030 SCH_BAD_CLS_STRUCT Bad class structure
6031 SCH_CLSNAME_TOOLONG Class name too long
6032 SCH_ATTRNAME_TOOLONG Attribute name too long
6033 SCH_METHNAME_TOOLONG Method name too long
6035 SCH_CANT_UPD_SYSCLS Cannot update system class
6036 SCH_CANT_INDEX_SYSCLS Cannot index on system class
6037 SCH_CANT_UPD_SYSOBJ Cannot update system object
6038 SCH_CANT_CREATE_SYSOBJ Cannot create system object
6039 SCH_CANT_MOVE_SYSOBJ Cannot move system object
6040 SCH_CANT_UPD_INHRDOMAIN Cannot update inherited domain
6041 SCH_CANT_UPD_DOMAIN Cannot update non-null domain
6042 SCH_BAD_CLS_TBL Bad front-end class cache
6043 SCH_BAD_SCH_CACHE Bad back-end schema cache
6044 SCH_CANT_INHERIT_SELF Cannot inherit from itself
6045 SCH_OBJ_NOT_FOUND Cannot find object
6046 SCH_CLSDEF_CONFLICT Conflicting class definitions in databases
6047 SCH_CANT_EXPAND_MEM Cannot expand memory - internal only
6048 SCH_CANT_MOVE_CHKOUT_OBJ Cannot migrate checked out object which is
not a versioned object nor a snapshot
object
6049 SCH_BAD_ATTR_OFF Bad attribute offset
6050 SCH_BAD_ATTR_POS Bad attribute position
6051 SCH_CANT_MOVE_COMP Cannot migrate composite
6052 SCH_REF_TO_ANON Ref to anonymous object
6053 SCH_DUP_ATTRNAME Duplicate attribute name
6054 SCH_DUP_METHNAME Duplicate method name
6055 SCH_BAD_INDEXTYPE Index type must be O_IT_BTREE or O_IT_HASH
6056 SCH_OBJ_SIZE_MISMATCH Mismatch between bufdesc length and object
size in the database
6057 SCH_NO_CLASS_CLASS Cannot find storage of class class
6058 SCH_GENERATE_RESOBJ_FAILED Failed to generate resident schema objects
6059 SCH_CLS_INIT_FAILED Failed to init schema class variables
6060 SCH_RELEASE_RESOBJ_FAILED Failed to release resident objects or class
table
6061 SCH_CRT_RESOBJ_FAILED Failed to create resident schema objects
6062 SCH_NULL_OBJECTS The input objects parameter is NULL
6063 SCH_MIGR_NO_VALID_OBJS No valid objects to migrate
6064 SCH_CLASS_NOT_IN_SOURCE_DB The class of the object to migrate is not
in the source database
6065 SCH_OBJ_NOT_REGULAR Object is not regular.
6066 SCH_CANT_RENAME_INHR_ATTR Cannot rename an inherited attribute.
6067 SCH_OBJ_HAS_NO_ATTR Class instance has no attributes
6068 SCH_CLSDEF_CHANGED Class definition has changed
6069 SCH_CANT_EVOLVE_IF_DBDOWN Schema evolution is not allowed if any
connected replica database is down.
6070 SCH_WRONG_SIZE_VSTR The input vstr size is incorrect
6071 SCH_LAYOUT_ATTR_NAME Bad attribute name in o_attrlayout
6072 SCH_LAYOUT_ATTR_TYPE Bad attribute type in o_attrlayout
6073 SCH_INDEX_CONFLICT A similar index exists on attribute
6074 SCH_CLS_MUST_BE_EMPTY Class must be empty to be clustered
6075 SCH_CANT_DROP_SYSTEM_CLASS_ATTR
Cannot drop attribute belonging to a system
class
6076 SCH_CANT_DROP_SYSTEM_CLASS Cannot drop system class
6077 SCH_CANT_MODIFY_SYSTEM_CLASS Cannot modify system class
6078 SCH_CANT_RENAME_SYSTEM_CLASS_ATTR
Cannot rename system class attribute
6079 SCH_CANT_RENAME_SYSTEM_CLASS Cannot rename system class
6200 FS_BASE For fasload/fasdump
6203 FSD_BAD_ATTROBJ Bad attribute object detected in fasdump
6204 FSL_BAD_ATTROBJ Bad attribute object detected in fasload
6205 FSD_CANT_DUMP_REMOTEOBJ Cannot dump remote object
6206 FSL_CANT_LOAD_REMOTEOBJ Cannot load remote object
6207 FSD_CANT_DUMP_LOGGED Cannot dump with logging on
6208 FSL_OBJ_NOT_FOUND Cannot find object to load
6209 FSL_TOO_MANY_DBIDS Too many different dbids in LOIDs
6300 CONT_BASE
6301 CONT_DBNAME_TOOLONG Db name is too long
6302 CONT_NULL_DBNAME Db name is null
6303 CONT_OBJ_NOT_CONTAINER Not a container object
6304 CONT_NULL_CLS_OBJECT Null class object
6305 CONT_CANT_CREATE_SYSOBJ Class object is resident class
6306 CONT_NULL_OBJECT Null object
6307 CONT_NOT_ANON_OBJ Cannot be an anonymous object
6308 CONT_CANNOT_INSERT_AT Cannot insert container object into
associative table
6309 CONT_BE_NO_OBJ_TO_DELETE No object to delete
6310 CONT_MEM_NO_MEM Out of mem writing cont
6311 CONT_OBJ_INVALID_OBJ Bad object type passed
6312 CONT_CANNOT_EMBED_CONTAINERS Container in container not allowed
6313 CONT_READ_NO_MEM Out of mem reading container
6314 CONT_ROOT_NO_MEM Out of mem read container object
6315 CONT_ROOT_BAD_TYPE Bad object type in container
6316 CONT_SCH_OBJ_NOT_PINNED Object not pinned
6317 CONT_SCH_NOT_ANON_OBJ Trying to upgrade non-anonymous object
6318 CONT_VAR_NO_MEM Out of memory in variable size attribute
6319 CONT_CANNOT_REF_OWN_CONTAINER Ref to own container object
6320 CONT_WRITE_NO_DISK_SPACE Out of disk space
6322 CONT_MEM_NULL_DB Bad db
6323 CONT_VAR_REF_TO_ANON Ref to anonymous object
6324 CONT_SCH_NULL_ANON Ref to ext anon
6325 CONT_VAR_REF_DEL_OBJ Ref to deleted object
6326 CONT_WRITE_REF_DEL_OBJ Ref to deleted object
6327 CONT_WRITE_BAD_TYPE Unexpected object type
6328 CONT_NULL_PARAM Null pointer was passed in
6329 CONT_SE_TOO_MANY_CONTAINERS Too many container in session
6330 CONT_OBJ_SCH_OBJ Cannot put schema object in container
6331 CONT_MOVE_VERSIONED_OBJ Cannot add version object to container
6332 CONT_MOVE_PLOCK_OBJ Cannot add persistent lock object to
container
6333 CONT_MEM_ROOT_IS_PINNED Root is still pinned
6400 ACT_BASE
6401 ACT_WRONG_MODE Wrong session options
6402 ACT_NO_SESSION Session has not been created
6403 ACT_NO_PROCESS Proc has not been created
6404 ACT_NO_ACTIVITY Act has not been created
6405 ACT_NO_MEM Out of memory
6406 ACT_PROCROOT_ACT Proc root act not allowed
6407 ACT_OUTSTANDING_ACT There are active act's
6408 ACT_NOT_IMPLEMENTED Not implemented yet
6409 ACT_NOT_FOUND Activity not found
6410 ACT_NO_NESTED_PROC Missing nested process(es)
6411 ACT_NESTED_PROC_ERR Nested proc exited in err
6412 ACT_SHOULD_ROLLBACK Not a unanimous commit
6413 ACT_ROOT_ACT_EXISTS Cannot have multiple roots
6414 ACT_NULL_TRID NULL transaction id
6500 EV_BASE
6501 EV_BAD_USER_DATA Invalid user input data
6502 EV_NULL_OID NULL object logic id
6503 EV_BUFFER_TOO_SMALL Buffer too small
6504 EV_BAD_BUFFER_PTR Bad buffer pointer
6505 EV_AUX_INFO_MISMATCH Aux info length mismatch
6506 EV_WRONG_EVENT_ORDER Invalid event
6507 EV_INVALID_KEY Invalid databas path name
6508 EV_IPC_NOT_EXIST
6509 EV_IPC_REMOVED IPC queue removed
6510 EV_BAD_IPC_ID Invalid IPC id
6511 EV_CANT_START_DD Cannot start event daemon
6512 EV_EVENT_LOST An event not delivered
6513 EV_OP_NOT_ALLOWED Not a front-end operation
6514 EV_PROCESS_INIT Cannot initialize daemon
6515 EV_BAD_HANDLE Bad event queue handle
6516 EV_NOT_ACTIVATED Event notifcation disabled
6517 EV_INVALID_REG_ID Invalid registration id
6518 EV_NOT_REG_OWNER Not owner of registration
6519 EV_BAD_EVENT_PAIR Lower event greater than higher event
6520 EV_BAD_DEF_FLAGS
6521 EV_BAD_EVENT_TYPE Not a proper event type
6522 EV_BAD_OPTION Invalid option
6523 EV_BAD_FLAGS Invalid flags
6524 EV_DAEMON_NOT_RUN Event daemon not running
6525 EV_NULL_EVENT NULL events
6526 EV_OBJ_NOT_EXIST Object does not exist
6527 EV_IPC_VIOLATED Permission denied to access message queue
6528 EV_NO_MSG No message
6529 EV_NO_REG No event registrations
6530 EV_STILL_ACTIVATED Event notification activated
6531 EV_NOT_INITIALIZED ev in memory structure has not been
initialized. (try calling
o_initen(O_EV_ENABLE),and o_xact if in
persistent registration mode)
6532 EV_PTR_CAN_NOT_NULL User input pointer should not be null
7000 UT_OK No error
7001 UT_DB_NOT_FOUND DB directory not found
VERSANT_DB configuration parameter does not point to a database root directory that has a subdirectory with the same name as the database you want to use. Check to make sure that there is a directory with the same name as the database under the directory returned by invoking the environment utility as oscp -d.. See the Database Administration Manual for information about database directories, VERSANT_DB, and oscp.
7002 UT_DB_NOT_PERSONAL Not a personal DB
7003 UT_DB_NO_ACCESS No access rights to DB dir
7004 UT_BE_PROFILE_ERROR Error parsing back-end profile
7005 UT_FE_PROFILE_ERROR Reserve for error parsing frontend profile
7006 UT_ER_NOFILE Cannot find error message file error.msg
7007 UT_ER_NO_MSG Cannot find error message
This problem can occur if the server process is on a different machine and is running a different VERSANT release than the application process. The solution is to assert the release number on the server using the VERSANT_REL@server configuration parameter on the client machine. In any case, the server machine must be running a release of VERSANT that is numerically equal or higher to the release running on the client machine.
This problem can also occur on a UNIX machine if the file /etc/.oscxxyyzz on the server machine does not have the correct entry for VERSANT_ROOT. In this case, you can either correct the VERSANT_ROOT entry in the .oscxxyyzz file on the server machine or set the environment parameter VERSANT_ROOT@server on the client machine to point to the VERSANT software root directory.
Another possible reason for this error is that the error messages file error.msg has not been installed on the server machine, which could occur if a vendor has supplied you with a run-time version of VERSANT.
For information about the VERSANT_REL@server and VERSANT_ROOT@server configuration parameters, see the Database Administration Manual.
7008 UT_DB_ALREADY_STARTED Database already started in another machine
7009 UT_WRONG_OBE_VERS OBE version doesn't match client's
7010 UT_UNKNOWN_UTILITY Unknown database utility
7011 UT_DB_EXISTS Database already exists
7012 UT_INVALID_PARAMETER Invalid parameter
7013 UT_ER_CREATE_DBDIR Failed to create database directory
7014 UT_ER_CHGOWNER_DBDIR Failed to change owner of database
directory
7015 UT_ER_CHGGROUP_DBDIR Failed to change group of database
directory
7016 UT_ER_CREATE_BEPROFILE Failed to create server process profile. Check
disk space, permissions etc.
7017 UT_ER_CHGOWNER_BEPROFILE Failed to create default database profiles
7018 UT_ER_CREATE_FEDIR Failed to create FE profile directory
7019 UT_ER_CHGOWNER_FEPROFILE Failed to change owner of FE profile
7020 UT_ER_CHGGROUP_BEPROFILE Failed to change group of database BE
profile
7021 UT_ER_DBDIR_NOACCESS Database directory not found or no access
permission
createdb utility without first creating the database directory and database support files. In this case, the solution is to run the makedb utility before running createdb. See the Database Administration Manual for information on how to create databases.Alternately, your login name may have a space in it: although NT allows spaces in login names, VERSANT does not.
7022 UT_ER_SYSTEMVOL_NOACCESS No access to system volume
7023 UT_ER_SYSTEMVOL_EXISTS System volume already exists
7024 UT_ER_SYSTEMVOL_CREATE Unable to create system volume
7025 UT_ER_PHYSICALLOG_NOACCESS No access to physical log volume
7026 UT_ER_PHYSICALLOG_EXISTS Physical log volume already exists
7027 UT_ER_PHYSICALLOG_CREATE Unable to create physical log volume
7028 UT_ER_LOGICALLOG_NOACCESS No access to logical log volume
7029 UT_UR_LOGICALLOG_FILE_TYPE Logical log volume already exists
7030 UT_ER_LOGICALLOG_CREATE Unable to create logical log volume
7031 UT_ER_DBID_NOACCESS Failed to access database ID file
7032 UT_ER_FORMAT_LOGFILES Failed to format log files
7033 UT_ER_FORMAT_DATABASE Failed to format database
7034 UT_ER_SDA_INIT Failed to initialize shared memory
The solution is to configure shared memory on the system according to the instructions in the installation notes.
For example, on Sun machines, the system configuration file is in /usr/kvm/sys/sun4/conf. The name of the file depends on the system administrator who has configured your system. The following two lines need to be present in this file for shared memory to be available in your system:
options IPCSHMEM
options SHMMNI=nnn
In the above, nnn represents the maximum number of shared memory segments that can be made available in your system.
Please set SHMMNI to the value suggested by VERSANT in the "Platform Notes" chapter of your Release Package.
7035 UT_ER_VOLUME_SIZE Invalid volume size
7036 UT_ER_STARTDB Failed to start database
7037 UT_ER_VOLUME_OFFSET Invalid volume offset
7038 UT_ER_VOLUME_NOACCESS No access to volume
7039 UT_ER_VOLUME_EXISTS Volume already exists
7040 UT_ER_VOLUME_CREATE Unable to create volume
7041 UT_ER_VOLUME_FORMAT Failed to format volume
7042 UT_ER_VOLUME_DELETE Failed to delete volume
7043 UT_ER_BEGIN_SESSION Failed to begin session
7044 UT_ER_UNAUTHORIZED_ACCESS Unauthorized access
7045 UT_ER_DB_INUSE Database is in use
7046 UT_ER_DB_INCONSISTENT Database may be inconsistent
7047 UT_ER_USER_NOTFOUND Database user not found
7048 UT_ER_USER_FOUND Database user found
7049 UT_ER_USER_IS_DBA User is DBA
7050 UT_ER_ROLLBACK Failed to rollback database
7051 UT_ER_SDA_CRASHED Shared memory crashed
If this occurs, check the file LOGFILE in your database directory, look at error messages reported there, and decide whether the error messages make any sense to you and whether you can do anything about the problem reported.
For example, in LOGFILE you might see the following error message:
0964, SL_ATTACH_EXTEND_SEG Cannot attach extension segments in the LOGFILE.
In this case, error 0964 is an error for which you have a solution (presented above), and you can execute the solution as per the recommendation.
If the error message does not make any sense to you, please call Versant Technical Support for help.
7052 UT_ER_SDA_GRPSHARE Unable to share SDA for group
7053 UT_ER_PROCESS_INIT Process initialization failed
7054 UT_ER_RECOVERY Database recovery failed
7055 UT_ER_CLEANBE Failed to start cleanbe process
7056 UT_ER_HEAP_NOMEM No more heap space
7057 UT_ER_MOUNT_TAPE Tape not mounted
7058 UT_ER_FE_CLEANUP Failed to clean up front resources
7059 UT_ER_UNKNOWN_DB Unknown database
7060 UT_ER_LOCKMODEL_FILE Cannot get new lock model from file
7061 UT_ER_DB_LOCKED Database already started
7062 UT_ER_DETACH_ODA Failed to detach from ODA
7063 UT_ER_PARSE_BEPROFILE Error %d: parsing back-end profile at %s
7064 UT_ER_NOT_DB_OWNER Not Database owner
7065 UT_ER_NOT_GROUP_MEMBER Not a group member
7066 UT_ER_DBID_CREATE Cannot create database ID file at %s
7067 UT_ER_DBID_LOCK Error %d: obtaining lock on DBID file
7068 UT_ER_MAKE_DB_DIRECTORY Failed to make db directory
7069 UT_ER_REMOTE_ACCESS Failed to invoke utility remotely
If the problem is a login error and the error occurred on a personal computer, it may mean that the configuration parameter VERSANT_USER has not been set to a valid user of the database involved. In this case, set VERSANT_USER to a valid user name or have the dba for the database add the current user name to the list of authorized user.
This error may also mean that your user name is not a valid login name on the remote machine. In this case, have the system administrator for the remote machine to add your user name to the list of valid login names on the machine where the database is located.
This error can occur if the remote inetd daemon is not able to start the ss.d process. In this case, the solution is to update the /etc/inetd.conf file with the correct entry and then restart the inetd daemon. For further information, see the installation instructions in your Release Package.
This error can also occur if the ss.d process is not able to start the server process for the database. This can occur in the following situations:
— if the VERSANT machine configuration file /etc/.oscxxyynn (where xxyynn corresponds to your release number) does not have the right setting for VERSANT_ROOT (which specifies the software root directory,)
— if different releasese are running on the client and server and the configuration parameter VERSANT_REL@node has not been properly set on the client machine, or
— if the number of the VERSANT release running on the server is not numerically equal to or greater than the client release number.
This error can also occur if the database server process crashes while the application process was communicating with it, in which case there will be a core dump. This could happen due to resource limitations such as lack of shared memory or semaphores. In this case, the cause is normally written to a file called LOGFILE under the VERSANT database directory. If LOGFILE does not contain the information you need to solve the problem, please call VERSANT Technical Support.
For information on the .oscxxyynn machine configuration file, the VERSANT_ROOT and VERSANT_REL configuration parameters, and the LOGFILE error file, see your Database Administration Manual.
7070 UT_ER_INTERNAL Internal error
7071 UT_ER_READ_BE_PROFILE Cannot read back-end profile
7072 UT_ER_WRITE_BE_PROFILE Cannot write back-end profile
7073 UT_ER_READ_FE_PROFILE Cannot read front-end profile
7074 UT_ER_WRITE_FE_PROFILE Cannot write front-end profile
7075 UT_ER_EXCEED_MAXVOLUMES Exceed maximum number of volumes
7076 UT_ER_DBID_EXISTS osc-dbid already exists
7077 UT_ER_BAD_GEN_OP Invalid operation for ut_genericRPC
7078 UT_ER_BAD_GEN_REP_MODEL Invalid replicaModel for rep_genericRPC
7080 UT_SS_UNKNOWN_CLIENT Unable to get peer name of client. %m
7081 UT_SS_LOGIN_ERROR Error receiving login message from %s. %m
7082 UT_SS_SEND_ERROR Unable to send response to %s. errno: %m
7083 UT_SS_UNAUTHORIZED_ACCESS Unauthorized remote login: %d
ROOT. The solution is to not use VERSANT as a superuser. VERSANT checks for superuser status and raises this error for security reasons.
7084 UT_SS_UNKNOWN_PATH Unable to obtain oscpath to %s. errno: %m
085 UT_SS_CONNECTION_TIMEOUT Connection from %s has been timed out.
7086 UT_SS_CONNECTION_DROPPED Connection from %s has been dropped.
7087 UT_SS_INCOMPATIBLE_RELEASE Fail to find a compatible release
7088 UT_ER_WRONG_OSC_PATH Wrong osc path %s
7089 UT_ER_OSC_PATH_NOT_FOUND osc path %s not found
If the remote machine is a UNIX machine running the same VERSANT release as your machine, confirm that the VERSANT_ROOT configuration parameter in the file /etc/.oscxxyyzz on the remote machine points to the correct VERSANT software root directory.
If the remote machine is running a different VERSANT release than your machine, confirm that the release number on the remote machine is numerically higher than the release number on your machine. If the server release number is higher than the application release number, set the VERSANT_ROOT@server configuration parameter as an environment variable on the application machine to point to the VERSANT software root directory on the remote machine.
For information about the /etc/.oscxxyyzz file and the VERSANT_ROOT@server configuration parameter, see your Database Administration Manual.
7090 UT_SS_BAD_BUFSIZE Network buffer size is too large
7091 UT_INCOMPATIBLE_LOCKFILE Incompatible .lock file
7092 UT_DB_IS_UNSTARTABLE Database is unstartable
7093 UT_LOCKFILE_NOT_FOUND Lock file not found
7094 UT_ER_ADD_USR_TO_PDB Cannot add users to personal databases
7095 UT_ALIGN_NOT_POWER_OF_2 O_ALIGN not on a power of 2
7096 UT_ER_DBDIR_EXISTS Database directory already exists
7097 UT_ER_BEPROF_EXISTS Back end profile file already exists
7098 UT_ER_FEPROF_EXISTS WARNING: Using an existing front end profile
7099 UT_ER_CLEANFE cleanfe terminated abruptly
7100 UT_ER_UNKNOWN_LEVEL Unknown level
7101 UT_ER_NEED_LEVEL_0 Restore level 0 first
7102 UT_ER_NEED_LEVEL_1 Restore level 1 first
7103 UT_ER_WRONG_DBID Wrong dbid
7104 UT_ER_NO_DBID Cannot create dbid
7105 UT_ER_NO_DIRECTORY A database directory is required. Create
one with makedb or vutil.
7106 UT_ER_BACKING_UP Another process is backing up already
7107 UT_UNCONVERTED_AND_STARTED Convertdb requires that the database be
stopped
7108 UT_DIFFERENT_HOSTS Both databases must be on the same machine and
are not.
7109 UT_LOCAL_ONLY Remote databases are unsupported. Try running
on "$(host)".
7110 UT_TRIAL_EXPIRED Trial period expired on evaluation copy
7111 UT_DBID_EXCEED_LIMIT dbid can not exceed UT_DBID_USER_MAX (0xFF7F)
7112 UT_ER_VOLUME_DUPENTRY Database profile.be has duplicate entry for
data volume
7113 UT_ER_VOLUME_NEEDADD Need run 'addvol' for the data volume entry in
profile.be
7114 UT_ER_RESTORE_PREV_VER Restore from backup of previous version not
allowed
7200 UT_W_NOT_LATEST There is a more recent backup of this level
7203 UT_W_NEWER_LEVEL_2 Level 2 more recent than level 1, restore
level 2 again afterward
7204 UT_W_DB_MODIFIED Db modified since last restore
7205 UT_W_END_OF_BACKUP End of backup
7206 UT_DB_NOT_IN_DBID Database not in osc-dbid file
7220 UT_NO_REPLICA_ENTRY No entry for database in
VERSANT_ROOT/replica
7221 UT_IS_ALREADY_A_REPLICA_DB Database is already replicated
7222 UT_MULTIPLE_REPLICA_INFOS Multiple instances of replica_info were
detected
7223 UT_FAILED_TO_CLONE_OBJECTS Could not replicate all the objects
7224 UT_OBJECT_NOT_IN_DB1 Object `%s' is in `%s' but not `%s'
7225 UT_OBJECT_NOT_IN_DB2 Object `%s' is in `%s' but not `%s'
7226 UT_OBJECT_VALUES_DIFFERENT Object `%s' has different values in `%s'
and `%s'
7227 UT_LOGGING_REQUIRED CREATEREPLICA requires that logging be ON.
7228 UT_GROUP_REQUIRED CREATEREPLICA does not support personal
databases
7229 UT_USE_REMOVEREPLICA Use REMOVEREPLICA to remove a replicated
database
7230 UT_ER_DBID_IN_USE Attempt to assign a dbid that is already
in use.
7231 UT_ER_NOT_SUPER_USER Must be super user for the operation
7232 UT_OPEN_REPLICA_FILE_FAIL Attempt to open replica file failed
7233 UT_ER_ALREADYON Roll forward already on
7234 UT_ER_ALREADYOFF Roll forward already off
7235 UT_ER_INVALIDARG Invalid argument to RF
7236 UT_ER_ARCHIVING_OFF Archiving not turned on
7237 UT_ER_BACKUP_OFF Backup not started
7238 UT_ER_BACKUP_NOCONFIRM Prev backup not confirmed
7239 UT_ER_WRONGID Confirmation for wrong ID
7240 UT_ER_ARCHIVING_PENDING Archiving not turned on
7241 UT_ER_RECOVERY_OFF RF recovery not started
7242 UT_ER_RFREC_TOO_LARGE RF Record > 256K len
7243 UT_ER_RF_INVALIDREC Rec-aligned RF rec needed
7244 UT_CANT_CONNECT_PDB Cannot connect to personal database
7245 UT_DBA_PRIVILEGE You need dba privilege to do this operation
7246 UT_ER_TERM_LOGGER Logging process terminated
7247 UT_ER_ARCHIVE_REP Cannot archive a replicated database
7248 UT_ER_INVALID_SEQNO Out-of-order record seqno
7249 UT_ER_PTN_EXIST Partition exists
7250 UT_FTS_INVALID_PDELAY Invalid polling delay. Must be either 0 or -1
251 UT_ER_BACKUP_NO_LEVEL_0 No level 0 backup
7252 UT_DB_NOT_EMPTY Destination database must be empty
7253 UT_DB_WRONG_STATE Database is in the wrong state
7254 UT_DB_ALREADY_SUSPENDED ftstool -stopsync has already been applied on
the database
7255 MSG_VERSANT_UTILITY VERSANT Utility %s Version %s
7256 MSG_VERSANT_COPYRIGHT Copyright (c) %s-%s VERSANT Object
Technology
7257 MSG_PANIC Versant panicking in file '%s' at line %d
7258 MSG_YES Yes
7259 MSG_NO No
7260 MSG_ERROR Error
7261 MSG_WARNING Warning
7262 MSG_ABORT_ACTION Do you want to abort?
7263 MSG_ANSWER_YES Y
7264 MSG_ANSWER_NO N
7275 MSG_UDLTOOL_USAGE %% %s [-d ddbname] [-l sdbname] [-n] [-p]
[-s [lm]] [filename]
7276 MSG_UDLTOOL_1 -d ddbname db name where the lock model
will be set
7277 MSG_UDLTOOL_USAGE_2 -l sdbname db name where the lock model
object is/will be located
7278 MSG_UDLTOOL_USAGE_3 -n store the new lock model object into
sdbname
7279 MSG_UDLTOOL_USAGE_4 -p print info of the lock model currently
used in ddbname
7280 MSG_UDLTOOL_USAGE_5 -s [lm] set the lock model lm in sdbname
to be used in ddbname
7281 MSG_UDLTOOL_USAGE_6 filename name of the input file that
describes the lock model
7282 MSG_UDLTOOL_USAGE_7 if -n is specified, both filename and
sdbname are required
7283 MSG_UDLTOOL_USAGE_8 if -s or -p is specified, ddbname is
required
7284 MSG_UDLTOOL_USAGE_9 if -s is specified and if sdbname is not
provided, ddbname will be used
7285 MSG_UDLTOOL_USAGE_10 to retrieve the lock model object
7286 MSG_UDLTOOL_USAGE_11 if -s is specified, the lock model name
can be obtained either from the
7287 MSG_UDLTOOL_USAGE_12 command line or from the input file
7288 MSG_UDLTOOL_USAGE_13 if -s is specified and the lock model name
is not provided, the Versant
7289 MSG_UDLTOOL_USAGE_14 Standard Lock Model will be used
7290 MSG_UDLTOOL_USAGE_15 ddbname can be specified in the
environment variable O_DBNAME
7291 MSG_UDLTOOL_USAGE_END End of UDL help
7292 MSG_UDL_PARSE_ERROR UDL Parser [line %d column %d]
7293 MSG_UDL_COMMENT_ERROR UDL Parser: at line %d: no comment
delimiter
7295 MSG_ADDVOL_USAGE Usage: addvol parameters [options] <dbname>
7296 MSG_ADDVOL_USAGE_1 parameters:
7297 MSG_ADDVOL_USAGE_2 -n volName logical volume name
7298 MSG_ADDVOL_USAGE_3 -p volPath full path name of volume
device/file
7299 MSG_ADDVOL_USAGE_4 options:
7300 MSG_ADDVOL_USAGE_5 -s volSize volume size, default to 4M
7301 MSG_ADDVOL_USAGE_6 -e extSize extent size, default to use
backend profile
7302 MSG_ADDVOL_USAGE_7 -i pre-allocate and initialize volume
7303 MSG_ADDVOL_USAGE_8 -noprint suppress display messages
7304 MSG_ADDVOL_USAGE_9 dbname: database name
7305 MSG_ADDVOL_USAGE_END Usage: Addvol
7315 MSG_CREATEDB_USAGE Usage: createdb [options] <dbname>
7316 MSG_CREATEDB_USAGE_1 options:
7317 MSG_CREATEDB_USAGE_2 -i pre-allocate and initialize the database
7318 MSG_CREATEDB_USAGE_3 -noprint suppress display messages
7319 MSG_CREATEDB_USAGE_4 dbname: database name
7320 MSG_CREATEDB_USAGE_END Usage: createdb
7325 MSG_DBUSER_USAGE Usage: dbuser <command> [options]
<dbname>
7326 MSG_DBUSER_USAGE_1 command:
7327 MSG_DBUSER_USAGE_2 -list list database user access list
(default)
7328 MSG_DBUSER_USAGE_3 -add add user to database access list
7329 MSG_DBUSER_USAGE_4 '-n' or '-P' options required
7330 MSG_DBUSER_USAGE_5 -delete delete user from access list
7331 MSG_DBUSER_USAGE_6 '-n' or '-P' options required
7332 MSG_DBUSER_USAGE_7 options:
7333 MSG_DBUSER_USAGE_8 -n name user name
7334 MSG_DBUSER_USAGE_9 -P public access
7335 MSG_DBUSER_USAGE_10 -mode r/ rw access mode
7336 MSG_DBUSER_USAGE_11 -noprint suppress display messages
7337 MSG_DBUSER_USAGE_12 dbname: database name
7338 MSG_DBUSER_USAGE_END Usage:dbuser
7345 MSG_MAKEDB_USAGE Usage: makedb [options] <dbname>
7346 MSG_MAKEDB_USAGE_1 options:
7347 MSG_MAKEDB_USAGE_2 -g group database
7348 MSG_MAKEDB_USAGE_3 -p personal database, the default
7349 MSG_MAKEDB_USAGE_4 -owner user make user as owner of database
directory
7350 MSG_MAKEDB_USAGE_5 -cpprofile db copy profiles from the specified
db
7351 MSG_MAKEDB_USAGE_6 directory
7352 MSG_MAKEDB_USAGE_7 -nofeprofile do not create front-end
profile
7353 MSG_MAKEDB_USAGE_8 -logging turn logging on
7354 MSG_MAKEDB_USAGE_9 -locking turn locking on
7355 MSG_MAKEDB_USAGE_10 -mlatch turn single_latch off
7356 MSG_MAKEDB_USAGE_11 -noprint suppress display messages
7357 MSG_MAKEDB_USAGE_12 dbname: database name
7358 MSG_MAKEDB_USAGE_END Usage: makedb
7365 MSG_DBLIST_USAGE Usage: dblist [options]
7366 MSG_DBLIST_USAGE_1 options:
7367 MSG_DBLIST_USAGE_2 -all list all db in the system (default)
7368 MSG_DBLIST_USAGE_3 -owner owner list db owned by owner
7369 MSG_DBLIST_USAGE_4 -d dbName list only the named database
7370 MSG_DBLIST_USAGE_5 -dir list all databases and empty
7371 MSG_DBLIST_USAGE_6 Database directories
7372 MSG_DBLIST_USAGE_7 -noprint suppress display messages
7373 MSG_DBLIST_USAGE_END Usage: dblist
7375 MSG_DBINFO_USAGE: Usage: dbinfo [options] <dbname>
7376 MSG_DBINFO_USAGE_1 options:
7377 MSG_DBINFO_USAGE_2 -m set multi-user mode
7378 MSG_DBINFO_USAGE_3 -0 set unstartable mode
7379 MSG_DBINFO_USAGE_4 -1 set DBA-only single-connection mode
7380 MSG_DBINFO_USAGE_5 -d set DBA-only multi-connection mode
7381 MSG_DBINFO_USAGE_6 -p print existing database mode
7382 MSG_DBINFO_USAGE_7 -c create a new .lock file
7383 MSG_DBINFO_USAGE_8 dbname: database name
7384 MSG_DBINFO_USAGE_END Usage: dbinfo
7385 MSG_REMOVEDB_USAGE Usage: removedb [options] <dbname>
7386 MSG_REMOVEDB_USAGE_1 options:
7387 MSG_REMOVEDB_USAGE_2 -f force removing database
7388 MSG_REMOVEDB_USAGE_3 -rmdir remove database directory
7389 MSG_REMOVEDB_USAGE_4 -noprint suppress display messages
7390 MSG_REMOVEDB_USAGE_5 dbname: database name
7391 MSG_REMOVEDB_USAGE_END Usage: removedb
7395 MSG_STARTDB_USAGE Usage: startdb <dbname>
7396 MSG_STARTDB_USAGE_END Usage: startdb
7403 MSG_STOPDB_USAGE Usage: stopdb [options] <dbname>
7404 MSG_STOPDB_USAGE_1 options:
7405 MSG_STOPDB_USAGE_2 -f force killing all active transactions
7406 MSG_STOPDB_USAGE_3 -s wait for update RPCs to be done
7407 MSG_STOPDB_USAGE_4 -st wait for all active transactions to be
done
7408 MSG_STOPDB_USAGE_5 -nonprint supress display messages
7409 MSG_STOPDB_USAGE_6 dbname: database name
7410 MSG_STOPDB_USAGE_END Usage: stopdb
7411 MSG_DBID_USAGE Usage: dbid -N
7412 MSG_DBID_USAGE_END Usage: dbid
7415 MSG_MAKEPROFILE_USAGE Usage: makeprofile[options] <dbname>
7416 MSG_MAKEPROFILE_USAGE_1 options:
7417 MSG_MAKEPROFILE_USAGE_2 -cpprofile db copy profiles from the
specified db
7418 MSG_MAKEPROFILE_USAGE_3 Directory
7419 MSG_MAKEPROFILE_USAGE_4 -nofeprofile do not create front-end profile
7420 MSG_MAKEPROFILE_USAGE_5 -logging turn logging on
7421 MSG_MAKEPROFILE_USAGE_6 -locking turn locking on
7422 MSG_MAKEPROFILE_USAGE_7 -mtlatch turn single_latch off
7423 MSG_MAKEPROFILE_USAGE_8 -noprint suppress display messages
7424 MSG_MAKEPROFILE_USAGE_9 dbname database name
7425 MSG_MAKEPROFILE_USAGE_END Usage makeprofile
7445 MSG_REORGDB_USAGE Usage reorgdb parameters <dbname>
7446 MSG_REORGDB_USAGE_1 parameters:
7447 MSG_REORGDB_USAGE_2 options:
7448 MSG_REORGDB_USAGE_3 -noprint suppress display messages
7449 MSG_REORGDB_USAGE_4 dbname: database name
7450 MSG_REORGDB_USAGE_END Usage: reorgdb
7455 MSG_RESTOREDB_USAGE Usage: restoredb parameters <dbname>
7456 MSG_RESTOREDB_USAGE_1 parameters:
7457 MSG_RESTOREDB_USAGE_2 -if device input device name
7458 MSG_RESTOREDB_USAGE_3 options:
7459 MSG_RESTOREDB_USAGE_4 -nowait don't wait for operator
assistance
7460 MSG_RESTOREDB_USAGE_5 -noprint suppress display messages
7461 MSG_RESTOREDB_USAGE_6 dbname: database name
7462 MSG_RESTOREDB_USAGE_END Usage: restoredb
7465 MSG_OSCP_USAGE Usage: oscp [options]
7466 MSG_OSCP_USAGE_1 options:
7467 MSG_OSCP_USAGE_2 -d database path
7468 MSG_OSCP_USAGE_3 -i environment information
7469 MSG_OSCP_USAGE_4 -l product version number with path
7470 MSG_OSCP_USAGE_5 -n dbid node name
7471 MSG_OSCP_USAGE_6 -0 osc-dbid path
7472 MSG_OSCP_USAGE_7 -p Versant runtime path
7473 MSG_OSCP_USAGE_8 -r Versant root path
7474 MSG_OSCP_USAGE_9 -v product version number
7475 MSG_OSCP_USAGE_END Usage: oscp
7495 MSG_CONVERTDB_USAGE Usage: convertdb <dbname>
7496 MSG_CONVERTDB_USAGE_END Usage: convertdb
7505 MSG_DBUSER_NAME User Name
7506 MSG_DBUSER_READ_ACCESS R
7507 MSG_DBUSER_WRITE_ACCESS W
7508 MSG_DBUSER_DBA DBA
7509 MSG_DBUSER_CREATION_DATE Creation Date
7515 MSG_DBID_HEADER_INFO DBID file header
7516 MSG_DBID_MAX_ID max ID = %d
7517 MSG_DBID_VERSION version = %d
7518 MSG_DBID_VERSION2 version2 = %d
7519 MSG_DBID_ENTRIES entries = %d
7520 MSG_DBID_VALID_ENTRIES valid entries = %d
7521 MSG_DBID_PATH path = %s
7525 MSG_DBLIST_ENTRY ID = %d
7526 MSG_DBLIST_ENTRY_EMPTY ID = EMPTY DB DIRECTORY
7527 MSG_DBLIST_DBNAME DB name = %s
7528 MSG_DBLIST_CREATOR creator = %s
7529 MSG_DBLIST_DATE_CREATED date created = %s
7530 MSG_DBLIST_TYPE_PERSONAL db type = PERSONAL DATABASE
7531 MSG_DBLIST_TYPE_GROUP db type = GROUP DATABASE
7532 MSG_DBLIST_TYPE_UNIVERSAL db type = PUBLIC DATABASE
7533 MSG_DBLIST_TYPE_UNKNOWN db type = UNKNOWN
7534 MSG_DBLIST_VERSION db version = %s
7535 MSG_DBLIST_GROUPID db group id = %d
7545 MSG_DBID_ENTRY DBID entry %d
7546 MSG_DBID_ENTRY_EMPTY ID = EMPTY DB DIRECTORY
7547 MSG_DBID_ID ID = %d
7548 MSG_DBID_DBNAME DB name = %s
7549 MSG_DBID_CREATOR creator = %s
7550 MSG_DBID_DATE_CREATED date created = %d:%d:%d %d/%d/%d
7551 MSG_DBID_DBVERSION version = %s
7555 MSG_VERSION Versant Product Version: %s
7556 MSG_ROOT_PATH Versant Root Path: %s
7557 MSG_ROOT_NOACCESS WARNING: no access to root path
7558 MSG_TOO_MANY_LINK_LEVELS WARNING: too many level of links
7559 MSG_RUNTIME_PATH Versant Runtime Path: %s
7560 MSG_DB_DIRECTORY Versant DB Directory: %s
7561 MSG_DB_NOACCESS WARNING: no access to db directory
7562 MSG_VERSANT_CFG VERSANT_CFG: %s
7563 MSG_ROOT_ENV VERSANT_ROOT: %s
7564 MSG_DB_ENV VERSANT_DB: %s
7565 MSG_DBID_ENV VERSANT_DBID: %s
7566 MSG_REL_ENV VERSANT_REL: %s
7567 MSG_SSD_NOACCESS WARNING: CANNOT LOCATE ss.d
7568 MSG_SSD Versant ss.d Location: %s
7569 MSG_DBID_NODE Versant osc-dbid node name:%s
7570 MSG_DBID_PATH_IS Versant osc-dbid path %s
7575 MSG_ADD_USER Adding User Name = %s
7576 MSG_ADD_USER_INFO User Inserted
7577 MSG_DELETE_USER Deleting User Name = %s
7578 MSG_DELETE_USER_INFO User Deleted
7585 MSG_WRONG_VOLUME_MOUNTED WRONG VOLUME SEQUENCE NUMBER
7586 MSG_CHECK_VOLUME_NUMBER ATTENTION: Is new tape #%d mounted and
ready?
7587 MSG_VOLUME_INFO volume %s at %s, size=%d
7595 MSG_BACKUPDB_INFO Backing up database
7596 MSG_BACKUPDB_DEVICE device path = %s
7605 MSG_RESTOREDB_INFO Restoring database
7606 MSG_RESTOREDB_NAME database name = %s
7607 MSG_RESTOREDB_VOLUMES total volumes = %d
7615 MSG_COMPRESSDB_INFO Compress Database
7616 MSG_COMPRESSDB_FAILED ERROR: Compress Database Failed
7617 MSG_COMPRESSDB_RESTORE Restoring database
7625 MSG_REMOVEDB_WARNING Attempt to force removal of database
7626 MSG_REMOVEDB_SYSVOL Warning: system volume may be corrupted
7627 MSG_REMOVEDB_DATAVOL user volumes created by addvol utility are
not removed
7628 MSG_REMOVEDB_RETRY Retrying (this may take up to 2 minutes)
7629 MSG_REMOVEDB_DBID Database entry %d removed from ID file
7630 MSG_REMOVEDB_VOLNAME deleting volume at %s
7631 MSG_REMOVEDB_DBDIR Removing database directory %s
7635 MSG_ADDVOL_INFO Add Volume
7636 MSG_ADDVOL_NAME volume name = %s
7637 MSG_ADDVOL_SIZE volume size = %dK
7638 MSG_ADDVOL_PATH volume path = %s
7639 MSG_ADDVOL_OFFSET volume offset = %d
7640 MSG_ADDVOL_EXTSIZE extent size = %d
7641 MSG_ADDVOL_NUMOFEXT number extents = %d
7642 MSG_ADDVOL_INSERT_ENTRY Inserting volume entry
7645 MSG_CREATEDB_DBID database ID is %d
7646 MSG_CREATEDB_PLOG Physical log volume created at %s
7647 MSG_CREATEDB_PLOG_INFO size=%dK
7648 MSG_CREATEDB_LLOG Logical log volume created at %s
7649 MSG_CREATEDB_LLOG_INFO size=%dK
7650 MSG_CREATEDB_SYSVOL System volume created at %s
7651 MSG_CREATEDB_SYSVOL_INFO size=%dK, page size=%d, extent size=%d,
number of extents=%d
7652 MSG_CREATEDB_FORMAT Formatting system volume
7653 MSG_CREATEDB_SYSCLASS Creating system classes
7655 MSG_STOPDB_WARNING Database may be inconsistent while
attempting to remove shared memory
7656 MSG_STOPDB_RETRY Retrying (this may take up to 3 minutes)
7657 MSG_MAKE_DIRECTORY Making directory at %s
7665 MSG_BEPROFILE Back end profile created at %s
7666 MSG_FEPROFILE Front end profile created at %s
7675 MSG_LOCK_MODES %s Lock Model has %d lock modes
7676 MSG_LOCK_RS_TABLE Relative Strength Table
7677 MSG_LOCK_COMP_TABLE Compatibility Table
7678 MSG_LOCK_IPEL_TABLE Implicit Promotion of Explicit Locks Table
7679 MSG_LOCK_PROMO_TABLE Other Promotions Table
7685 MSG_MSG_NOTFOUND Non-existent error message
7686 MSG_MSG_FILE_NOTFOUND Cannot find error message file error.msg
7687 MSG_MSG_CREATE_INDEX Cannot create error message index file
error.msi
7688 MSG_MSG_WRITE_INDEX Error while writing error message index
file error.msi
7689 MSG_MSG_REMOVE_INDEX Error while removing faulty error message
index file error.msi
7690 MSG_MSG_SEEK_ERROR Error while seeking on error message index
file error.msi
7691 MSG_MSG_LINE_ERROR Error: A line in error message file
error.msg does not begin with a number
7695 MSG_DBMODE Database is in %s mode
7696 MSG_CREATE_DBLOCK Database lock file is created
7705 MSG_STARTDB_BEGIN_PHY_REC Beginning physical recovery phase
7706 MSG_STARTDB_END_PHY_REC Ending physical recovery phase
7707 MSG_STARTDB_BEGIN_LOG_REC Beginning logical recovery phase
7708 MSG_STARTDB_END_LOG_REC Ending logical recovery phase
7715 MSG_CREATEREPLICA_USAGE Usage: createreplica [options] <dbname>
<replica-dbname>
7716 MSG_CREATEREPLICA_USAGE_1 options:
7717 MSG_CREATEREPLICA_USAGE_2 -i pre-allocate and initialize the database
7718 MSG_CREATEREPLICA_USAGE_3 -noprint suppress display messages
7719 MSG_CREATEREPLICA_USAGE_4 -nocreate copy to existing database
7720 MSG_CREATEREPLICA_USAGE_5 dbname: name of database to replicate
7721 MSG_CREATEREPLICA_USAGE_6 replica-dbname: database name for replica
7722 MSG_CREATEREPLICA_USAGE_7 -nocreate and -i cannot be used together
7723 MSG_CREATEREPLICA_USAGE_END Usage: createreplica
7725 MSG_REMOVEREPLICA_USAGE Usage: removereplica [options]
<replica-dbname>
7726 MSG_REMOVEREPLICA_USAGE_1 options:
7727 MSG_REMOVEREPLICA_USAGE_2 -f force removing of database
7728 MSG_REMOVEREPLICA_USAGE_3 -rmdir remove database directory
7729 MSG_REMOVEREPLICA_USAGE_4 -noprint suppress display messages
7730 MSG_REMOVEREPLICA_USAGE_5 replica-dbname: name of replica database
7731 MSG_REMOVEREPLICA_USAGE_END Usage: removereplica
7735 MSG_COMPAREDB_USAGE Usage comparedb [options] <db1> <db2>
7736 MSG_COMPAREDB_USAGE_1 options:
7737 MSG_COMPAREDB_USAGE_2 -value compare object values
7738 MSG_COMPAREDB_USAGE_3 -noprint suppress display messages
7739 MSG_COMPAREDB_USAGE_4 db1: name of first database
7740 MSG_COMPAREDB_USAGE_5 db2: name of second database
7741 MSG_COMPAREDB_USAGE_END Usage: comparedb
7745 MSG_SETDBID_USAGE Usage setdbid [options] <dbid> <dbname>
7746 MSG_SETDBID_USAGE_1 options:
7747 MSG_SETDBID_USAGE_2 -noprint suppress display messages
7748 MSG_SETDBID_USAGE_3 dbid: new dbid number
7749 MSG_SETDBID_USAGE_4 dbname: name of the database
7750 MSG_SETDBID_USAGE_END Usage: setdbid
7755 MSG_SETMINDBID_USAGE Usage: setmindbid [options] <dbid>
7756 MSG_SETMINDBID_USAGE_1 options:
7757 MSG_SETMINDBID_USAGE_2 -noprint suppress display messages
7758 MSG_SETMINDBID_USAGE_3 dbid: new minimum dbid number
7759 MSG_SETMINDBID_USAGE_END Usage: setdbid
7765 MSG_CREATEREPLICA_DONE The replica has been successfully created.
7766 MSG_REMOVEREPLICA_DONE The replica has been successfully removed.
7767 MSG_REPLICA_FILE_REMINDER **REMEMBER TO UPDATE THE REPLICA FILE**
7768 MSG_COMPAREDB_VALUE_SUCCESS Success! Object LOIDs and values are the same
in both databases.
7769 MSG_COMPAREDB_LOID_SUCCESS Success! Object LOIDs are the same in both
databases.
7775 MSG_ADDUSER_USAGE Usage: adduser [options] <dbname>
7776 MSG_ADDUSER_USAGE_1 options (either -n or -P is required):
7777 MSG_ADDUSER_USAGE_2 -n name user name
7778 MSG_ADDUSER_USAGE_3 -P public access
7779 MSG_ADDUSER_USAGE_4 -noprint suppress display messages
7780 MSG_ADDUSER_USAGE_5 dbname: database name
7781 MSG_ADDUSER_USAGE_END Usage: adduser
7785 MSG_DELUSER_USAGE Usage: deluser [options] <dbname>
7786 MSG_DELUSER_USAGE_1 options (either -n or -P is required):
7787 MSG_DELUSER_USAGE_2 -n name user name
8001 CXX_CANT_CAST Can not cast object of type %s to type %s
This error can occur when you use the AS() or L_AS() macros and make an incorrect cast. It can also happen if a parameterized collection class contains an object of the wrong class, although this problem should have been caught at compile-time.
This error can also occur if you are trying to cast a pointer to a transient instance of a class and the constructor for the class does not contain the line VPP_CLASS_CONSTRUCTOR1(ClassName), which is needed for runtime type identification.
8002 CXX_NO_CONTAINER No containers named %s were found on database %s
8003 CXX_DUP_CONTAINER Multiple containers named %s were found in
database %s
8004 CXX_BAD_DATE The date %s %d, %d is illegal
8005 CXX_BAD_DAY %s is not the name of a day of the week
8006 CXX_NOT_PERSISTENT_VEC Cannot convert % object to pHandle_vec as
it contains transient elements
8007 CXX_NOT_VERSION %s method invoked on non-version %s object
8008 CXX_BAD_ALLOC_SIZE Allocated %s size must be positive
8009 CXX_BAD_INDEX Index of %d applied to %s object is out of
bounds %d
8010 CXX_NOT_FOUND %s object was not found in %s for
operation %s
8011 CXX_REMOVE_ERR %s object to be removed was not found in %s
8012 CXX_BAD_PRED Illegal predicate %s was applied to class
%s
8013 CXX_BAD_ATTR %s is not an attribute of class %s
8014 CXX_SUBSTRING_ERR Illegal substring from position %d length
%d on %s of length %d
8015 CXX_BAD_CLASS Got object of class %s when class %s was
expected
8016 CXX_BAD_SPECIES Got object of species %s when species %s
was expected
8017 CXX_BAD_ARG_CLASS Got argument of class %s when class %s was
expected by method %s
8018 CXX_BAD_ARG_SPECIES Got argument of species %s when species %s
was expected by method %s
8019 CXX_BAD_RANGE Range from %d of length %d in %s method %s
is invalid
8020 CXX_BAD_DATE_RANGE The date %s %d, %d is outside the legal
range
8021 CXX_EMPTY The %s is empty for operation %s
8022 CXX_BAD_TIME %d:%d:%d %s %s %d,%d is an invalid time
8023 CXX_BAD_DBLLINK Bad double linked node in %s for
operation %s
8024 CXX_BAD_MONTH No such month as %s
8025 CXX_BAD_MONTH_NUM %d is a bad month number
8026 CXX_BAD_DAY_NUM %d is a bad day number
8027 CXX_DUPLICATE_KEY Attempt to use duplicate %s key with %s
value in %s
8028 CXX_KEY_NOT_FOUND %s key not found in %s
8029 CXX_UNKNOWN Unknown error number %d was thrown
8030 CXX_ZERO_DENOM Zero denominator in %s
8031 CXX_NO_MEM Local memory is exhausted
8032 CXX_FUNC_OVER Double %g conversion to %s yielded large
exponent %d
8033 CXX_FUNC_UNDEFINED Double %g conversions is undefined for
exponent %d
8034 CXX_BAD_LINK %s next should be zero
8035 CXX_DERIVED Virtual method %s should have been
implemented by derived class %s
8036 CXX_SHOULD_NOT %s should not implement method %s
8037 CXX_NOT_IMPLEMENTED Method %s is not implemented in this
release
8038 CXX_INVALID_ITERATOR Iterator is invalid in %s
8039 CXX_NO_CLSOBJ database does not know about class %s
8040 CXX_NO_CXXCLS C++ interface does not know about class %s
VERSANT provides class definition information at build-time by embedding within an application the C++ class object for each class used by the application. For example, for class X, the class object PClassObject<X> will be embedded within the executable.
To embed a class object during the compiling and linking process, the application source code must include the header file for the class.
A quick patch for this problem is to put into your main program the following dummy function:
dummyFunction() {
new (PClassObject<X>::Pointer()) X;
// all classes whose objects may be referenced
}
This dummy function need not be called by the application.
8041 CXX_CORRUPT_CLSOBJ Database contains corrupt class %s object
8042 CXX_NO_SUCH_ATTR No such attribute %s in class %s
8043 CXX_BAD_DOMAIN Cannot select on domain of attribute %s in
class %s
8044 CXX_COMPARE_UNDEFINED Comparison method undefined
8045 CXX_HASH_UNDEFINED Hashing method undefined
8046 CXX_INTERNAL_ASSERT C++ interface internal assertion failed
8047 CXX_THIS_NULL Got NULL for this in method %s
8048 CXX_BAD_F_ARG Bad argument for %s in function %s
8049 CXX_BAD_M_ARG Bad argument for %s in method %s
8050 CXX_ZERO_F_ARG Bad zero argument for %s in function %s
8051 CXX_ZERO_M_ARG Bad zero argument for %s in method %s
8052 CXX_OM_PANIC Internal object manager panic: %s (line %d
file %s)
8054 CXX_CLASS_SIGNATURE For class %s, compiled class signature %x
does not match schema signature %x in
database %s
8055 CXX_NOT_MUNCHED Problem in munch -- static objects did not
construct
8056 CXX_ASSERTT An assert macro failed (see "cxxcls/paux.h")
cxxcls/paux.h contains two macros, assertt() and assertts(), which throw this error when they fail. assertt() puts the source file name and line number in the error, and assertts() puts a second argument, a string, in the error. VERSANT uses assertts() inside its class libraries at positions that should never fail. These will print the extra argument beginning with the word "bomb_" if they do fail. Contact Versant if one of our assertions fails.
8057 CXX_OM_VSTR_OUTSIDE_SESSION A vstr that was created during a session was released or resized after endsession
Instances of VERSANT helper classes (such as links, vstrs, and link vstrs) that are created during a session can only be used during that session. In this case a vstr that was created during a session was changed or released after the session. Often this happens when a transient object (perhaps a spurious temporary object) is created during a session, and then is deleted after the session ends. Often you can avoid this by putting braces { } around the work within a session, and closing them before calling endsession.
For example:
::dom->beginsession()
{ ..... your work ..... }
dom->endsession()
This is a problem because C++ compilers often do not delete temporary objects as soon as they should. Please refer to the C++/VERSANT Reference Manual for further information.
8058 CXX_BOMB Internal assertion failed: %s
This error can indicate that there is an inconsistency in the build process, in which case you should check your makefiles and make sure that the build is done correctly.
During the template instantiation process for cfront 3.0 based compilers, VERSANT generates intermediate files of the general form __PClass_something.cc. This error can mean that the generation of a file of this form is not controlled by your makefiles, which means that if a class definition changes, these files are not automatically rebuilt. If this is the case, you need to clean out all the intermediate files, the .o files, and rebuild from scratch.
8059 CHL_NCOMP NCOMP not` yet supported by checking
NCOMP. NCOMP is a VERSANT kernel object type which is not supported by the Check Facility yet. (Bad Links can also produce this error.)
8060 CH_INTERNAL Internal failure within checking
8061 CHL_NO_SESSION A link was used while no session exists
PHandle, PCOD* or o_object outside of a session, because the object cache does not exist except during a session. Likewise, a link from one session is invalid in another seesion.
8062 CHL_XCOD A COD is referenced outside of COD-space
8063 CHL_NO_COD_TYPE Problem in COD
8064 CHL_DELETED A link to a deleted object was used
8065 CHL_TOP_XHEAP Persistent object located outside object space
8066 CHL_BAD_LOOP Problem in COD
8067 CHH_NULL null object header pointer
8068 CHH_NO_CLASS Problem in object header
8069 CHH_CLASS_XCOD Problem in object header
8070 CHH2_XHEAP Problem in extended object header
8071 CHH2_XCOD Problem in extended object header
8072 CHH_XHEAP Object header not in heap
8073 CHP_WHAT Object has bad PObject::__what slot
8074 CH_ADDR Pointer has illegal value
8075 CHV_S_FREED vstr has already been freed
8076 CHV_S_TFREED Transient vstr has already been freed
8077 CHV_S_BOGUS vstr pointer does not point to a vstr
8078 CHP_PERSIST Use of persistent object located outside
of heap
8079 CHL_MUST_PERSIST Link to transient object where persistent
object is required
8080 CHV_MUST_PERSIST Transient vstr where persistent vstr is
required
8081 CH_FAILURE The Check Facility found an inconsistency:
%s
CheckL(), CheckP(), CheckV(), etc. Or it could have been built into the VERSANT library libcxxchk.a or libcxxvnch.a. If you use libcxxchk.a, the entire front end cache is checked before dom methods that will use the entire cache, such as dom->commit(), dom->abort(), dom->endsession(), dom->savepoint(), dom->exit(), etc.If you cannot figure out why this error occurs, you might try turning on all checking and tracking facilities, and look in that output for the address given in this error. This may help you figure out what object or vstr pointer is wrong.
You may have a bad pointer, or something may have trashed the memory at a valid pointer, which confused the Check Facility.
8082 CH_FAIL_L Problem while checking a link at address
{=" in the description, along with a clue as to which operation requested the check. See comments at error "CH_FAILURE"
The check facility could have been invoked directly by you, because you use CheckL() or CheckCache(), or it could have been built into the VERSANT library libcxxchk.a or libcxxvnch.a.
If you use libcxxchk.a, CheckCache() is called automatically before transaction-oriented methods such as dom->commit(), dom->abort(), dom->endsession(), dom->savepoint(), etc. The phrase <cache> appears in the output if CheckCache() is called.
Another message will be presented, which might give you a better hint about what is wrong. The exact problem could have occurred within some other object, which is linked to by an attribute of this object. If that is the case, you will be told which attribute points to it, and the index if the attribute is a linkvstr.
8083 CH_FAIL_H Problem while checking a header at address
{=" in the description, along with a clue as to which operation requested the check. See comments at error "CH_FAILURE"
8084 CH_FAIL_T Problem while checking a persistent object at address
{=" in the description, along with a clue as to which operation requested the check. See comments at error "CH_FAILURE"
8085 CH_FAIL_P Problem while checking a pointer to PObject at address
PObject* address of the object is printed after the "{=" in the description, along with a clue as to which operation requested the check. See comments at error "CH_FAILURE"
8086 CH_FAIL_V Problem while checking a vstr at address
{=" in the description, along with a clue as to which operation requested the check. See comments at error "CH_FAILURE"
8087 CH_FAIL_LV Problem while checking a link vstr at address
{=" in the description, along with a clue as to which operation requested the check. See comments at error "CH_FAILURE"
8088 CH_FAIL_ATTR Failure occurred within attribute
8089 CH_FAIL_INDEX Failure occurred at linkvstr index
8502 SCAP_WORD_FATAL Error
8504 SCAP_WORD_WARN Warning
8505 SCAP_WORD_NOTE Note
8511 SCAP_CANNOT_CREAT_EMPTY Cannot create file with EMPTY name
8512 SCAP_CANNOT_CREAT Cannot create file %s
8513 SCAP_CANNOT_OPEN Cannot open file %s
8514 SCAP_CANNOT_OPEN_EMPTY cannot open file with EMPTY name
8518 SCAP_NEED_DB_ARG You must specify a database name after the
%d option.
8519 SCAP_MALLOC Out of memory: cannot malloc
malloc(). You need more swap space. You might terminate some processes to free up some swap space. Also check that you do not have "limit"s set low.
8520 SCAP_BOMB Internal assertion failed: %s
8521 SCAP_CHECKING Internal checking failed: %s
8522 SCAP_VERSION Incompatible .sch-version number: program=%d/%s .sch=%d/%s
sch2db or sch2z utility that you are using. The solution is to recompile or rerun schema capture to generate new .sch schema files.
You can look at the top line of a .sch schema file to see the schema version number and the architecture name. The information you want follows the letter "v". For example: v 113 sparc. Then, to determine the version number of your utility, run it with the -v option, which will emit a timestamp ending in /s plus its schema version number. For example: .../s113sparc.
See the C++/VERSANT Reference Manual for information about schema capture and the Database Administration Manual for information about the sch2db utility.
8523 SCAP_CORRUPT_SCH Corrupt .sch file: unexpected object type %d
.sch file. Perhaps you gave the utility the wrong filename, or perhaps your .sch files have been corrupted.
8524 SCAP_SEL_CLS_CLS Cannot find classes in database %s
class". This might be due to locking or deadlock, but it could indicate a corrupt database.
8525 SCAP_SETDOMAIN Unable to fixup forward reference domain: %s class: %s attribute: %s
sch2db we try to fix up all of these attributes, but the domain still is not defined, or for some other reason the object manager cannot fix up this attribute.
8526 SCAP_FIXUP Problem during forward reference fixup -- some classes may not be fixed up.
SCAP_SETDOMAIN.
8527 SCAP_FIXUP_DOMAIN Cannot locate domain class %s object during fixup of class %s, attribute %s
.sch files, or your database could be corrupt. See SCAP_SETDOMAIN.
8528 SCAP_VSTR Vstr operation failed within schema utility
8529 SCAP_PREP_CLS Cannot add signature to class object, for class %s
8530 SCAP_LOC_CLSOBJ Cannot locate class object: class %s
8531 SCAP_LOC_ATTR Cannot locate attribute object: class %s attribute %s
8532 SCAP_LOC_DOMAIN Cannot locate domain object: class %s attribute %s
8533 SCAP_ATTR_MATCH Database attribute names do not match .sch file: database %s class %s database-attribute %s .sch-attribute %s
8534 SCAP_ATTR_OFFSET Database attribute offsets do not match .sch file: database %s class %s attribute %s database-offset %d .sch-offset %d
8535 SCAP_LOC_SUPERCLS Cannot locate the class object for the superclass of %s
8536 SCAP_DEFCLASS Could not define class %d
8537 SCAP_DEFCLASS_LOC Could not locate class object after
defining class %s
8538 SCAP_LOC_ATTR_CLASSID Cannot locate o_attrobj::classid of class
%s attr %s
8539 SCAP_LOC_ATTR_ATTRID Cannot locate o_attrobj::attrid of class
%s attr %s
8540 SCAP_CORRUPT_LOCATE Database corruption detected: cannot use
class %s (internal id %s)
8541 SCAP_DROPCLASS Cannot drop class %s from the database
8542 SCAP_DROPINSTS Cannot drop instances of class %s from the
database
8543 SCAP_DROPATTR Cannot drop attribute %s from class %s
8544 SCAP_NEWATTRAT Cannot add new attribute %s to class %d
8545 SCAP_ADD_CLS_SIG Cannot attach signature %x to database
class object %x
8546 SCAP_DIRTY Cannot mark an object dirty
o_preptochange() was unsuccessful. Perhaps we were unable to get a write lock on the object, or were connected to a read-only database.
8547 SCAP_NO_OP_STAR operator * undefined in Link-like class %s
PLink, you must provide a monadic operator*() (the indirection operator). Schema capture uses this operator to determine what kind of a link it is.
8548 SCAP_NO_OP_BRACKET operator * undefined in Link-like class %s
PVstr, you must provide an operator*[] (the subscript operator). Schema capture uses this operator to determine what kind of a vstr it is.
8549 SCAP_BITFIELD Sorry, bitfields not supported in database class %s
PObject cannot contain bitfields. Try defining them as o_u1b or o_u2b or o_u4b, as appropriate.
8550 SCAP_VSTR_NOTSIMPLE Vstr of nonsimple type %s used in definition of class %s
PObject are going to have persistent instances, they cannot have vstrs of non-simple data types. The sch2db utility will complain if you try to install this class in a database.
8551 SCAP_BEGINSESSION Cannot begin database session on database %s
8552 SCAP_ENDSESSION Error during endsession on database %s
8553 SCAP_NO_DB_NAME No database name was provided -- use "-D" option
-D option, or you can set the O_DBNAME environment variable to the name of the database.
8554 SCAP_SCH_CONFLICT Two declarations of class %s conflict with each other
.sch files, there are two different definitions of the given class. This error can happen if two different modules use two different classes of the same name, or if you recompile one module after making changes, but do not recompile the other module.
8555 SCAP_CLASS_DIFFERS Class %s already exists in the database in a different form
.sch file contained the class in a different form.
If you did not specify -e, you may try again with -e if you want to evolve the classes (and instances), or you may use -f if you want to drop the old classes (and instances) and define them again.
If you specified -e, no supported methods of evolution could be used to evolve the class. You will have to either make the new class definitions differ in ways we support evolution, or use the -f option to drop the old classes (and instances) and define them again.
8556 SCAP_CMDNAME This Versant command does not understand its name
sch2db or dropclass.
8557 SCAP_OPTION Unknown dash option
8701 EVPP_BOMB Internal error in vpp
+D option, and send us the _cpp file, so we can reproduce the problem. Also write down the bomb_ code that gets printed with the error.
8703 EVPP_EXPSUP_NOTCLASS Cannot VPP_EXPAND_SUPER on nonclass
VPP_EXPAND_SUPER is special, and its argument must be a class name. You may be using a non-class name as if it were a class, or the VERSANT preprocessor could be confused and not realize that something is a class. You should not be using the VPP_EXPAND_SUPER statement directly.
8704 EVPP_EXPSUP_OUTSIDE Cannot use VPP_EXPAND_SUPER outside Template
VPP_EXPAND_SUPER statement can only be used inside a template definition. You should not be using the VPP_EXPAND_SUPER statement directly.
8705 EVPP_PCO_UNDEF Template PClassObj undefined
PClassObj is not defined. Perhaps you forgot to include the standard headers, or perhaps they are corrupt.
8706 EVPP_TPL_UNDEF Unknown Template
8707 EVPP_AFTER_NOT_TPL After clause is not a Template
After in a clause in a template definition. For example, you can say After Link<X>, but you cannot say After Employee.
8708 EVPP_NEST_TPL Cannot nest Templates definition
8709 EVPP_TPL_REDEF Template redefined
8710 EVPP_OPTION Undefined option flag
8711 EVPP_ARGV No arguments needed
-'.
8712 EVPP_STDOUT Error writing standard output
8713 EVPP_NO_IMP There is no Implementation for this Template
8714 EVPP_CLAUSE Undefined Template clause
After clause, or it could be a clause that is special to C++/VERSANT. The latter should not happen if you include <cxxcls/pobject.h>.
8715 EVPP_NEST_EXPSUP Cannot nest VPP_EXPAND_SUPER
VPP_EXPAND_SUPER statement. VERSANT's own code should never have nested VPP_EXPAND_SUPER statements. So this error should not happen.
8716 EVPP_OUT_OF_MEMORY Out of memory in parser
stopdb on a VERSANT database can also help a lot.
8717 EVPP_SYNTAX_ERROR General syntax error
8718 EVPP_MULTIPLE_IMPLEMENT Multiple implement clauses in template definition
Implement clause in a template definition.
8719 EVPP_PRIMITIVE_UNDEFINED Primitive template undefined
<cxxcls/pobject.h>.
8720 EVPP_BAD_LINE_MARKER Bad line marker
For example: # "filename" 88 or #line "filename" 88
Something must have created a marker line that the VERSANT preprocessor cannot understand.
8721 EVPP_BAD_PARAMETER Parameter is not a word
8722 EVPP_TPL_RECURSION Recursive template name
ClassOne<ClassTwo> which uses ClassOne<ClassOne<ClassTwo> > which uses ClassOne<ClassOne<ClassOne<ClassTwo> > > etc. would create this error.
8723 EVPP_INFINITE_TDEF Infinite typedef recursion
8960 E_VGC2_EXTERNAL_REF External reference to loid
This online documentation is confidential and proprietary to Versant Corporation and is licensed to you, or to your organization, pursuant to the terms of an agreement between you and Versant that restricts the use of this documentation. Please refer to the agreement for more information or call Versant at 510-789-1500 with any questions.