Versant Error Codes Reference

Versant Error Codes Reference
Versant Error Codes Reference
Release 9
Versant Error Codes Reference: Release 9
Versant Server 9.3
Copyright © 2001–2017 Versant Software LLC and Copyright © 2013–2017 Actian Corporation. All rights reserved.
The software described in this document is subject to change without notice. This document does not represent a commitment
on the part of Versant or Actian. The software is furnished under a license agreement or nondisclosure agreement and may be
used or copied only in accordance with the terms of the agreement. No part of this manual may be reproduced or transmitted in
any form or by any means, electronic or mechanical, including photocopying and recording, or for any purpose without the express
written permission of Actian.
Versant uses functionality provided in libraries supplied by third parties. License agreements for these third party libraries are
provided along with the libraries in the lib directory in the Versant installation.
Versant, Versant Server, Versant Object Database and FastObjects are either registered trademarks or trademarks of Versant
Software LLC in the United States and/or other countries.
Java and all Java-based marks are trademarks or registered trademarks of Oracle Corporation in the United States and other
countries.
Eclipse and Built on Eclipse are trademarks of Eclipse Foundation, Inc.
Microsoft, Windows, Visual C#, Visual Basic, Visual J#, and ActiveX are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
All other products are a registered trademark or trademark of their respective company in the United States and/or other countries.
9.3.0.4_1943—2017.04.12
Table of Contents
Contact Information for Actian .................................................................................................... vii
1. Introduction ............................................................................................................................. 1
2. Error Codes by Category ............................................................................................................ 3
2.1. Virtual System Errors, Series — 0001 ............................................................................... 4
2.2. System Level Errors, Series — 0700 ................................................................................ 10
2.3. Versant Server Errors, Series — 1000, 2000 ..................................................................... 14
2.4. Versant Network Errors, Series — 3000 .......................................................................... 24
2.5. Versant Manager Errors, Series — 4000 .......................................................................... 28
2.6. Locking Errors, Series — 5000 ....................................................................................... 34
2.7. Archive Errors, Series — 5200 ........................................................................................ 36
2.8. Query Errors, Series — 5400 .......................................................................................... 37
2.9. Version Errors, Series — 5600 ........................................................................................ 41
2.10. Schema Errors, Series — 6000 ...................................................................................... 42
2.11. Container Errors, Series — 6200 ................................................................................... 46
2.12. Event Notification Errors, Series — 6500 ...................................................................... 48
2.13. Virtual Attribute Errors, Series — 6600 ......................................................................... 50
2.14. System Utility Errors, Series – 7000, 9000, 11000, 12300 .............................................. 52
2.15. Versant C++ Errors, Series — 8000, 40000 ................................................................... 115
2.16. GUI Tool Errors, Series — 10000 ................................................................................. 138
Versant Error Codes Reference
iii
iv
Versant Error Codes Reference
List of Tables
1.1. Error Categories and Code Number Series ................................................................................ 1
Versant Error Codes Reference
v
vi
Versant Error Codes Reference
Contact Information for Actian
You can obtain the latest information about Actian products by contacting either of our main office
locations, visiting our web sites, or sending us an email.
Actian Office Locations
Actian Corporation is headquartered in Palo Alto, California. Actian Versant products are developed in
Hamburg, Germany.
Actian Corporate Headquarters
Actian
2300 Geng Rd., Suite 150
Palo Alto, CA 94303
USA
+1.888.446.4737 [TEL—Toll Free US]
+1.650.587.5500 [TEL]
+1.650.587.5550 [FAX]
Actian Versant Development Center
Versant GmbH
Halenreie 42
D-22359 Hamburg
Germany
+49 (0)40 609 90 0 [TEL]
+49 (0)40 609 90 113 [FAX]
Actian Web Site
For the latest corporate and product news, visit the Actian web site at:
http://www.actian.com/
Versant Error Codes Reference
vii
Actian Versant Products
For inquiries about Actian Versant products and services, contact:
info@actian.com
For help in using Actian Versant products, contact Technical Support at:
versant_support@actian.com
The Actian Customer Portal provides all the essential information and valuable resources needed by
developers using Versant Object Database. Visit the Actian Customer Portal at:
http://support.actian.com/
(You will need an Actian ID to login. If you do not have an Actian ID, follow the Register link on that page
to create one.)
Trial Evaluation Support
If you are using the Versant Trial Evaluation and have questions or need help, you can get quick answers.
Contact Trial Evaluation Support at:
trial_support@actian.com
Please send feedback regarding this guide to:
documentation@actian.com
viii
Versant Error Codes Reference
Chapter 1. Introduction
This document lists and briefly explains the error codes generated by Versant.
The error codes are grouped into categories based on the general type of error. The following table shows
the error categories and corresponding numerical series of the error codes.
Table 1.1. Error Categories and Code Number Series
Category
Number Series
Virtual System
0001-0699
System Level
0700-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
Schema
6000-6199
Container
6200-6399
Event Notification
6500-6540
Virtual Attribute
6600-6627
System Utility
7000-7999
9000-9999
11000-11999
12300-12999
The format of the error code documentation is: number handle message
Versant Error Codes Reference
1
Incomplete Error Messages
If error numbers are displayed without an accompanying error message, then either your Versant
installation is incomplete or the necessary environment variables have not been correctly set up. For
more information on setting up the environment variables, refer to the Versant Installation and Deployment
Guide.
2
Versant Error Codes Reference
Chapter 2. Error Codes by Category
Sections
• Virtual System Errors, Series — 0001
• System Level Errors, Series — 0700
• Versant Server Errors, Series — 1000, 2000
• Versant Network Errors, Series — 3000
• Versant Manager Errors, Series — 4000
• Locking Errors, Series — 5000
• Archive Errors, Series — 5200
• Query Errors, Series — 5400
• Version Errors, Series — 5600
• Schema Errors, Series — 6000
• Container Errors, Series — 6200
• Event Notification Errors, Series — 6500
• Virtual Attribute Errors, Series — 6600
• System Utility Errors, Series – 7000, 9000, 11000, 12300
• Versant C++ Errors, Series — 8000, 40000
• GUI Tool Errors, Series — 10000
Versant Error Codes Reference
3
Virtual System Errors, Series — 0001
2.1. Virtual System Errors, Series — 0001
0001
VSL_KEY_INVAL
Invalid Key with OS err #$(oserr)
0002
VSL_BLKSZ_INVAL
Invalid block size
0003
VSL_BLKNO_INVAL
Invalid block number $(block)
0004
VSL_SHM_ALLOC
Cannot allocate shared memory OS err #$(oserr)
Versant cannot find enough shared memory for the server page cache.
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 with OS err
#$(oserr)
0006
VSL_SHM_ELOCAT
Cannot locate shared memory with OS err
#$(oserr)
You can get this error while trying to connect to a database which is located on an NFS mounted
directory visible to two different machines. If the database has been started by one machine
and then you try to connect to it using another machine, you will get this error.
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.
4
Versant Error Codes Reference
Virtual System Errors, Series — 0001
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.
Versant does not support storing database files on a Network File System (NFS).
0007
VSL_SHM_BUSY
Shared memory is in use with OS err #$(oserr)
0008
VSL_SHM_ERM
Unable to remove shared memory with OS err
#$(oserr)
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
The process table mentioned here is a Versant internal structure. If you receive this message,
you need to increase the transactions parameter in the profile.be file, stopping and restarting
the database afterwards, until you no longer receive this message whilst running your application.
0016
VSL_PR_ECREAT
Cannot create process with OS err #$(oserr)
0017
VSL_PR_NARGS
Too many arguments
0018
VSL_PR_EXEC
Process execution failed with OS err #$(oserr)
0019
VSL_PR_NEXIST
Process #$(pid) does not exist
0020
VSL_PR_EKILL
OS error #$(oserr) in killing process #$(pid)
0021
VSL_PR_EWAIT
OS error #$(oserr) while waiting for process #$(pid)
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
Versant Error Codes Reference
5
Virtual System Errors, Series — 0001
0026
VSL_SEM_ETIMEO
OS wait timeout err #$(oserr) after waiting $(timeout)
seconds for latch hold by process #$(pid)
0027
VSL_SEM_EWAIT
OS err #$(oserr) with timeout set to $(timeout) seconds
while waiting for latch hold by process #$(pid)
0028
VSL_SEM_ERETRY
Retry count #$(count) exceeded while waiting for latch
hold by process #$(pid)
0029
VSL_SEM_BUSY
Latch is in use
0030
VSL_SEM_EPOST
OS err #$(oserr) while posting latch
0031
VSL_SEM_ECREATE
OS err #$(oserr) while creating latch
The 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.
0032
VSL_SEM_ESETVAL
OS err #$(oserr) while setting latch value
0033
VSL_SEM_EGETINFO
Error getting latch info
0034
VSL_SEM_ENTRIES
No more latch entries
More transactions are trying to access a database than the limit set by the 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.
0035
VSL_SEM_UPGRADE
0036
VSL_SEM_NOLATCHES
No.of latches per execution unit exceeded
0037
VSL_SEM_DOWNGRADE
Attempt to downgrade latch failed
0041
VSL_VOL_ECLOSE
Unable to close volume with OS err #$(oserr)
0042
VSL_VOL_EXISTS
Volume already exists OS err #$(oserr)
0043
VSL_VOL_EREAD
Volume read OS error #$(oserr)
0044
VSL_VOL_EWRITE
Volume write error OS err #$(oserr)
0045
VSL_VOL_ESEEK
Seek OS error #$(oserr) on volume
0046
VSL_VOL_EOPEN
Unable to open volume OS err #$(oserr)
0047
VSL_VOL_ESTAT
OS err #$(oserr) while trying to get volume status from
dbpath '$(file)'
0048
VSL_VOL_EDESTROY
Unable to destroy volume ($(file)), OS error = #$(oserr)
0049
VSL_VOL_INVALID
Invalid volume specified OS err #$(oserr)
0050
VSL_EINPTR
Pointer is invalid
6
Attempt to upgrade latch
Versant Error Codes Reference
Virtual System Errors, Series — 0001
0051
VSL_EBUFSIZ
Buffer size is wrong
0052
VSL_EUSERNAM
Unable to get user name ($(string))
You are running NIS ("Yellow Pages") at your site, and the password files in /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.
0053
VSL_MEM_NOMEM
Out of process memory OS err #$(oserr)
You need more swap space on your machine, at least as much swap space as the value you set
for the parameter swap_threshold in your application process profile file. When you use Versant,
the recommended swap space-to-RAM ratio is 3,1.
0054
VSL_SHM_EEXIST
Shared memory exists OS err #$(oserr)
Versant needs to allocate shared memory for a database, but shared memory has already been
allocated for that database or some earlier incarnation of that database. The solution is to stop
the database with the stopdb utility, which will remove the shared memory segments.
0055
VSL_PR_NPERM
0061
VSL_FIXED_DEV_ZERO
Can't open "/dev/zero" with OS err #$(oserr)
0062
VSL_FIXED_MAP
Can't map memory with OS err #$(oserr)
0063
VSL_FIXED_ADDRESS
Mapped at wrong address
0064
VSL_FIXED_UNMAP
Cannot unmap memory with OS err #$(oserr)
0065
VSL_FIXED_CREATE
Cannot create segment with OS err #$(oserr)
0066
VSL_FIXED_ATTACH
Cannot attach segment with OS err #$(oserr)
0067
VSL_FIXED_DETACH
Cannot detach segment with OS err #$(oserr)
0068
VSL_FIXED_REMOVE
Cannot remove segment with OS err #$(oserr)
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
Versant Error Codes Reference
No permission to kill process #$(pid)
7
Virtual System Errors, Series — 0001
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
OS err #$(oserr) while initializing a mutex
0122
VSL_MUT_ELOCK
OS err #$(oserr) while locking a mutex
0123
VSL_MUT_EUNLOCK
OS err #$(oserr) while unlocking a mutex
0124
VSL_MUT_EDESTROY
OS err #$(oserr) 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
OS err #$(oserr) while initializing a condition variable
0130
VSL_CV_ELOCK
OS err #$(oserr) while locking a condition variable
0131
VSL_CV_EUNLOCK
OS err #$(oserr) while unlocking a condition variable
0132
VSL_CV_EDESTROY
OS err #$(oserr) while destroying a condition variable
0133
VSL_FILE_OPEN
OS err #$(oserr) while opening file $(file)
0134
VSL_FILE_WRITE
OS err #$(oserr) while writing to file $(file)
0135
VSL_FILE_MMAP
OS err #$(oserr) while mapping a file to memory
0136
VSL_TLS_EDELETE
Could not delete tls key
0137
VSL_FILE_SEEK
OS err #$(oserr) during a seek on file $(file)
8
Versant Error Codes Reference
Virtual System Errors, Series — 0001
0138
VSL_FILE_READ
OS err #$(oserr) while reading file $(file)
0139
VSL_FILE_FSYNC
OS err #$(oserr) while syncing file $(file) to disk
0140
VSL_FILE_TRUNCATE
OS err #$(oserr) while truncating file $(file)
0141
VSL_FILE_EEXIST
File $(file) does not exist
0142
VSL_FILE_EACCES
OS err #$(oserr) while accessing the file $(file)
0143
VSL_FILE_EXISTS
File $(file) already exists OS err #$(oserr)
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
OS err #$(oserr) during stat on file $(file)
0147
VSL_THR_JOIN
OS err #$(oserr) while waiting to join a thread
0148
VSL_TRACE_WRONG_VERSION
Incompatible trace file version.
You may want to rename/remove the old trace file (typically .systrace file in database directory
or entry against trace_file parameter in profile.be).
0149
VSL_OSERR
OS function '$(osfunc)' failed with err '$(oserr)'
0150
VSL_DL_OPENFAILED
Cannot open Library for loading
0151
VSL_DL_CLOSEFAILED
Cannot close Library for loading
0152
VSL_DL_INVALIDHANDLE
Invalid Handle
0153
VSL_DL_INVALIDSYM
Invalid Symbol
0154
VSL_PASSWD_EXCEEDSSIZE
Password size exceeds 256
0155
VSL_CANNOT_GET_PASSWD
Cannot get password from terminal with OS err
#$(oserr)
0156
VSL_RAWDEV_DISK_DESC_TYPE
Device description error
You may want to rename/remove the old trace file (typically .systrace file in database directory
or entry against trace_file parameter in profile.be).
0157
VSL_DIR_DELETE_FAILED
OS err #$(oserr) while deleting directory
0158
VSL_DIR_NOT_A_DIRECTORY
The specified path is not a directory
0159
VSL_DIR_NOACCESS
Database directory not found or no access
permission
Versant Error Codes Reference
9
System Level Errors, Series — 0700
2.2. System Level Errors, Series — 0700
0700
SL_EXPR_UNSUPPORTED_UNARY_OP
This unary operator is not supported
0701
SL_EXPR_UNSUPPORTED_BINARY_OP
This binary operator is not supported
0702
SL_EXPR_UNSUPPORTED_COND_OP
This conditional operator is not supported
0710
SL_EXPR_UNSUPPORTED_CONST_TYPE
This constant type is not supported in expressions
0711
SL_EXPR_UNSUPPORTED_ATTR_TYPE
This attribute type is not supported in expressions
0715
SL_EXPR_BAD_OPERAND_TYPE
Data type of operand is not compatible with the
operator
0730
SL_EXPR_WOULD_OVERFLOW
The evaluation of the expression would cause a
numeric overflow
0731
SL_EXPR_WOULD_UNDERFLOW
The evaluation of the expression would cause a
numeric underflow
0732
SL_EXPR_DIVIDE_BY_ZERO
The evaluation of the expression would cause a divide
by zero
0792
SL_BAD_SDA_BASE_ENV
Could not parse VERSANT_SDA_BASE environment
variable
0800
SL_DATABUF_BAD_START_SIZE
Invalid start size
0801
SL_DATABUF_NOMEM
Memory not available
0802
SL_DATABUF_NOT_INITIALIZED
Data buffer is not initialized
0803
SL_DATABUF_BAD_DATA_LENGTH
Invalid data length
0804
SL_DATABUF_MAX_SIZE_REACHED
Data buffer has already reached its maximum size
0805
SL_DATABUF_NULL_DATA_POINTER
Null data pointer
0806
SL_DATABUF_FIXED_SIZE_MISMATCH
Data did not fit in fixed size data buffer
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
0913
SL_ITEM_NOT_FOUND
Item not found in the list
10
Versant Error Codes Reference
System Level Errors, Series — 0700
0914
SL_BAD_VSTR
Bad vstr (variable length string)
0915
SL_BAD_BUFFER
Bad buffer
0916
SL_BUFFER_TOOSMALL
Buffer is too small
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 heap in local memory
0951
SL_CANT_CREATE_SHARED
Cannot create heap in shared memory
0952
SL_CANT_EXTEND_LOCAL
Cannot extend heap in local memory
You are running out of application memory, which can occur if there are too many processes
running on your machine or if your application is manipulating too many objects in a transaction.
First try reducing the number of processes. One thing you can do is stop any databases that are
running but not being used.
On UNIX, you can check for unused databases with the following:
ps aux | grep vserver
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.
0953
SL_CANT_EXTEND_SHARED
Cannot extend heap in shared memory
0954
SL_HEAP_MAXIMUM_SIZE
Heap hit specified maximum size
0955
SL_CANT_ATTACH_CONTIGUOUS
Cannot attach shared memory contiguously
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
Versant Error Codes Reference
11
System Level Errors, Series — 0700
0964
SL_ATTACH_EXTEND_SEG
Cannot attach extension segments
The machine containing a database has run out of shared memory segments. The solution is
to reconfigure the operating system on the machine containing the database so that it can
support a larger number of shared memory 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 pointer in heap function
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 $(loid) $(filename)
$(4byte) $(u4byte) $(oserr)
0978
SL_MESSAGE_TRACE
Trace along error path
0979
SL_BAD_INPUT
Input parameter is bad
0980
SL_DIV_ZERO
Trying to divide by zero
0981
SL_CPI_KEYNOTFOUND
Can't find an entry with this plugin-typename
0982
SL_CPI_CANNOTLOAD
Can't load the plugin
0983
SL_CPI_INVALIDID
This plugin not supported
0984
SL_VCP_ERROR
Error in the Plugin Module
0985
SL_CPI_PATHEXCEEDSSIZE
Plugin path exceeds max-size
0986
SL_CPI_INVALIDDLLNAME
Not a valid plugin name
0987
SL_CPI_NAMEEXCEEDSSIZE
Plugin_typename exceeds limit (max, 32 chars)
12
Versant Error Codes Reference
System Level Errors, Series — 0700
0988
SL_CPI_NULLPTR
NULL pointer
0989
SL_CPI_PROFILEEXCEEDSLIMIT
Only 8 Entries allowed
0990
SL_ER_DOUBLEBUFFER_INVALIDSIZE
Invalid Buffer Size
0991
SL_ER_DOUBLEBUFFER_EMPTY
Buffer Empty
0992
SL_CHARACTER_SET_UNSUPPORTED
Specified character set not supported
Versant Error Codes Reference
13
Versant Server Errors, Series — 1000, 2000
2.3. Versant Server Errors, Series — 1000, 2000
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
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 $(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 $(class) $(attr)
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, loid = $(loid)
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
14
Versant Error Codes Reference
Versant Server Errors, Series — 1000, 2000
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
Versant Error Codes Reference
15
Versant Server Errors, Series — 1000, 2000
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
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
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 at file
%s: line %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
1108
SM_E_MULTIVALUED_PATH
Multi-valued path attrs are not allowed here
1109
SM_E_INCOMPLETE_PATH
Multi-valued path attrs are not allowed here
1131
SM_OBJECT_TOO_LARGE
An object exceeds the maximum size
O_MAX_OBJECT_SIZE. The error message contains the
loid and the size of that object.
1132
SM_E_LOOP_DETECTED
Loop detected during segment structure analysis.
1133
SM_E_PREVLINK_BAD
Prev link in segment structure is incorrect.
1134
SM_E_INDEX_INCONSISTENT
Index is inconsistent with data page record
This indicates that the index contains an entry for an object that is not at the database location
given by the index entry. The index should be rebuilt.
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 log file
16
Versant Error Codes Reference
Versant Server Errors, Series — 1000, 2000
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 cannot be extended. Either there is insufficient
space in the filesystem/device, or, PLOG has already
reached its maximum size
2524
SM_LOG_CANNOT_EXTEND_LLOG
LLOG cannot be extended. Either there is insufficient
space in the filesystem /device, or LLOG has already
reached its maximum size.
2525
SM_LOG_WRONG_DB_VERSION
DB version not right, need to run convertdb
2526
SM_LOG_NOT_EMPTY
Log files have to be emptied by stopdb and startdb
in order to run convertdb
2527
SM_LOG_END_OF_UNIT
End of log unit reached
2530
SM_LOG_REC_LEN_OVERFLOW
Internal error
2531
SM_LOG_ILLEGAL_RECORD_TYPE
Found illegal record type $(recordType) in logical log
Versant Error Codes Reference
17
Versant Server Errors, Series — 1000, 2000
Indicates that the startdb process has come across an unknown record type in the transactional
recovery log (logical.log). This can happen either due to a version mismatch between the installed
Versant version and the database files or a corruption. If you encounter this error, contact
Versant support for further assistance.
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 $(key) found
2726
SM_E_DUPLICATEKEYPTR
Duplicate key found in B-tree nodes
2727
SM_E_KEYNOTFOUND
Cannot find the key
18
Versant Error Codes Reference
Versant Server Errors, Series — 1000, 2000
2728
SM_E_INDEXNUMTOOLARGE
Index number too large (create index)
2729
SM_E_KEYLENGTHTOOLONG
Index key length is too long
2730
SM_E_BADSLOTCOUNT
Negative slot count
2731
SM_E_KEYALREADYEXISTS
Key $(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
This means that a disk write has failed, probably because the disk is full.
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
Versant Error Codes Reference
19
Versant Server Errors, Series — 1000, 2000
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, pid = $(pid)
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
20
Versant Error Codes Reference
Versant Server Errors, Series — 1000, 2000
2787
SM_E_VOLEXISTS
Volume already exists
2788
SM_E_CREATFAILED
Volume create failed
2790
SM_E_VAERROR
VA internal error
2800
SM_E_INVALID_PASSWORD
Invalid Password specified
2801
SM_E_CANNOT_CHANGE_PASSWORD
Cannot Change Password
2802
SM_E_NULL_PASSWORD
No Password
2803
SM_E_INVALID_USER
The user has no password and is not logged into the
OS as that user
2901
SM_LOCK_WOULDBLOCK
Lock on $(loid) would have blocked process
2902
SM_LOCK_DEADLOCK
Deadlock detected on attempt to lock $(loid)
2903
SM_LOCK_TIMEDOUT
Lock wait Timed out on $(loid)
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
Versant Error Codes Reference
21
Versant Server Errors, Series — 1000, 2000
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
2935
SM_TR_ADDVOL_BLOCKED
Another addvol is active; addvols is blocked
2936
SM_TR_NOT_ZOMBIE
Transaction is not a dead/zombie transaction
2937
SM_TR_INVALID_STATE
Transaction is in the wrong state
2961
SM_SHM_NOT_READY
SDA not ready
2962
SM_SHM_SHUTTING_DOWN
SDA is shutting down
2971
SM_DB_IS_READONLY
Database is read-only mode
2972
SM_DB_IS_ACTIVE
Active transaction in database
2973
SM_DB_IS_REPLICATED
Replicated database
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, key =
$(key)
2996
SM_E_OUTOF_CACHE_MEMORY
No BufferPool Mem Available
This error symbolises that the backend page cache has run out of memory. This can be fixed by
increasing the max_page_buffs parameter in the server process profile and restarting the
22
Versant Error Codes Reference
Versant Server Errors, Series — 1000, 2000
operation. Alternatively, you can reduce the number of pages in the cache by not taking read
locks by default. This will reduce the number of objects which are locked in the memory.
2997
SM_E_INVALIDBUF
Buffer not useful for reading
2998
SM_E_BUF_WRONGSIZE
Buffer with wrong size
Versant Error Codes Reference
23
Versant Network Errors, Series — 3000
2.4. Versant Network Errors, Series — 3000
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
There has been a network 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.
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/.osc090300 does not have the correct 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
• 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.
3005
NET_EWRITE
Network layer write error
The database server process has crashed 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. The cause is normally written to the file LOGFILE under
the Versant database directory. If LOGFILE does not contain the information you need to solve
the problem, please call Versant Technical Support.
24
Versant Error Codes Reference
Versant Network Errors, Series — 3000
3006
NET_ENODNAM
Unable to obtain node name
3007
NET_INVREQ
Invalid RPC function
3008
NET_INVHOST
Invalid host name ($(string)), OS error = #$(oserr)
3009
NET_ECONNECT
Low level connect error.
A network error has occurred.
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 the Release Notes.
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.
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.
3010
NET_TCP_ESOCK
Error obtaining socket
3011
NET_INVUSRNM
Invalid user name/password string ($(string)).
A login error has occurred.
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)
3016
NET_ECONLOST
Network connection lost
Versant Error Codes Reference
25
Versant Network Errors, Series — 3000
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 ($(string)), OS err #$(oserr)
There is a Yellow Pages configuration error. This error happens if your site is running NIS
"Yellow Pages" and the Versant 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 the
Release Notes.
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.
2. Reboot.
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.
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
26
Versant Error Codes Reference
Versant Network Errors, Series — 3000
3038
NET_NO_UNUSED_PORT
Cannot find an unused port, all ports specified in
VERSANT_SERVER_PORTS are in use
3039
NET_XID_CONVERTION_ERR
Convert xid from 32/64 bit to 64/32 bit failed
3040
NET_RETRY
Local server did not receive a response from an
authoritative server. Try again later, OS err #$(oserr)
3041
NET_NO_RECOVERY
An unrecoverable error occured, OS err #$(oserr)
3042
NET_NO_ADDRESS
The hostname ($(string)) is valid but does not have
an Internet address at the name server, OS err
#$(oserr)
3043
NET_SERVICE_UNAVAILABLE
None of the name services configured are running
or available, OS err #$(oserr)
3044
NET_NO_NAME
The requested address parameter ($(string)) is valid
but does not have a name at the name server, OS
err #$(oserr)
3045
NET_EINVALIDPORTS
VERSANT_SERVER_PORTS contains invalid value.
3047
NET_SIGNAL_RECEIVED
A network related system call received a signal.
Versant Error Codes Reference
27
Versant Manager Errors, Series — 4000
2.5. Versant Manager Errors, Series — 4000
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.
You are using an invalid session name in your begin
session routine. Session names cannot exceed 31
characters.
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
4017
OM_SE_THREADS_REQUIRED
You must link with the threads library to use 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
28
Versant Error Codes Reference
Versant Manager Errors, Series — 4000
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 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
4038
OM_TR_PRIMDBDOWN
Primary database $(dbname) is down at commit time
4039
OM_TR_REPDBDOWN
Replica database $(dbname) is down at commit time
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 $(name) or not connected.
You are not using a valid database name. Database names cannot exceed 31 characters.
For more information, on other rules related to session names, please refer to the chapter
“Sessions” in VODFundamentals.
Versant Error Codes Reference
29
Versant Manager Errors, Series — 4000
4084
OM_DB_TOO_MANY_CONN
Too many connections
4085
OM_DB_CANT_DISCONN_PRIM
Cannot disconnect primary db
You have tried to disconnect from your session database. To use Versant, you must be in a
database session. The database you use as a session workspace is the database specified in the
begin session routine. The only way to disconnect from your session database, is to end your
database session.
4086
OM_DB_PERSONAL
Non-primary connection to personal database
You have tried to connect to a personal database after a session has started. You can start a
session using a personal database as the session database, but after this, you can connect only
to a group database and not to another personal database. The solution is to make sure that
when you use a connect database routine the database that you specify as an argument is a
group database and not a 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
4091
OM_DB_OUT_OF_SPACE
Database out of DataVolume Space
4102
OM_LO_FE_INVAL_OBJECT
Unknown object
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
4121
OM_PROF_DONE
Processing completed
4122
OM_PROF_SYNTAX
Syntax error
There is a syntax error in the application process profile
that you are using for this database.
You probably need to find the application process profile file and change its name. On UNIX
machines, the application process file must have the same name as your database.
If problems persist, call Versant Technical Support.
4123
OM_PROF_NEGATIVE
Negative number
4124
OM_PROF_FILE
Cannot open file
30
Versant Error Codes Reference
Versant Manager Errors, Series — 4000
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
4208
UT_API_UNSUPPORTED
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
4238
OM_REPLICA_REC_FAIL
Recursive failure during polling
4240
OM_REPLICA_UNSUPPORTED
API does not support replication
4241
OM_SYMT_table_NOT_FOUND
Symbol table could not be found
4242
OM_REP_ACTICE_XA_XACT
Active external transactions present.
4243
OM_REP_TR_CANT_COMMIT
Could not commit the transaction because concerned
fts database $(dbname) is down.
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.
Versant Error Codes Reference
31
Versant Manager Errors, Series — 4000
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 parseVERSANT_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
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 $(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 $(attr).
32
Versant Error Codes Reference
Versant Manager Errors, Series — 4000
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 cannot be bigger than $(limit)
4361
OM_PSR_PATHATTRS_OUTBOUND
VQL PARSE ERR Number of Attributes in path
expression cannot 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
Versant Error Codes Reference
33
Locking Errors, Series — 5000
2.6. Locking Errors, Series — 5000
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.
You have tried to use an invalid pointer.
Pointers are no longer valid after a transaction ends. The solution is to use a link to maintain
references to a persistent object across 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 error OB_NOPIN 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.
5004
OB_RESIDENT
Object cannot be deleted
5005
OB_WRONG_DB
Wrong destination db
5006
OB_NO_SUCH_OBJECT
Cannot find the object, loid = $(loid)
You have tried to de refer a dangling or invalid link in your database.
34
Versant Error Codes Reference
Locking Errors, Series — 5000
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.
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
5029
OB_BAD_COD
Invalid COD entry
Versant Error Codes Reference
35
Archive Errors, Series — 5200
2.7. Archive Errors, Series — 5200
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
5211
ARC_OBJ_NOT_REGULAR
Trying to archive an object that is not regular
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
36
Versant Error Codes Reference
Query Errors, Series — 5400
2.8. Query Errors, Series — 5400
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 in a
(not_)isa_exact operation
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 exact 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
Versant Error Codes Reference
37
Query Errors, Series — 5400
5421
QRY_BAD_OPTIONS
Invalid query options
5422
QRY_VA_NOT_SUPPORTED
Usage of Virtual Attribute is not supported
with this option
5423
QRY_OP_NOT_ALLOWED
Illegal operator-key combination
5425
QRY_CLAUSE_NOT_SUPPORTED
Unknown or Unsupported Query Clause
5440
QRY_REWRT_CANNOT_INVERT_ OP
The inversion of this operator is not defined
5441
QRY_REWRT_SIGNOF_NONNUMERIC_TYPE
An attempt was made to get sign of a
non-numeric value
5442
QRY_UNEXPECTED_FORMAT
Received invalid query rpc format from front
end
5443
QRY_OPERAND_NOT_COLLECTION _TYPE
Operand is not of collection type
5444
QRY_UNEXPECTED_COLLECTION_TYPE
Unexpected collection type.
5445
QRY_INCOMPATIBLE_OPERANDS_TYPE
Incompatible operands type. For an operation
to be evalualted successfully, its operands
must be of compatible types
5446
QRY_SET_OPERATORS_NOT_SUPPORTED_ON_STRINGS Set operators are not supported on string type
operands
5447
QRY_ATTRIBUTE_NOT_FOUND
Attribute not present in class version
5448
QRY_SORT_MEMORY_EXCEEDED_QUERY_MAX
The maximum amount of sorting memory
allocated to this query was exceeded
5449
QRY_SORT_MEMORY_EXCEEDED_TOTAL_MAX
The maximum amount of sorting memory
allocated for all queries was exceeded
5450
QRY_PSR_SYNTAX_ERROR
VQL parser error, $(errmsg) at $(token).
5451
QRY_UNSUPPORTED_QUERY_TYPE
Unsupported query type
5442
QRY_UNSUPPORTED_QUERY_PROJECTION
Unsupported projection type
5453
QRY_UNSUPPORTED_QUERY_
Unsupported query class.
5454
QRY_INPUT_INVALID_LOID
Invalid loid value.
5455
QRY_VAR_ALREADY_DEFINED
Variable redefined.
5456
QRY_VARIABLE_EXPECTED
Variable expected.
5457
QRY_UNSUPPORTED_ORDERBY_EXPRESSION
Unsupported order by expression.
5458
QRY_BAD_COLLECTION
Invalid or bad collection.
5459
QRY_BAD_CLASS_NAME
Invalid or bad class name.
38
Versant Error Codes Reference
Query Errors, Series — 5400
5460
QRY_ATTR_TYPE_LOID
Attribute type loid expected.
5461
QRY_INVALID_TYPE
Not a valid data type.
5462
QRY_INVALID_COLLECTION_ TYPE
Not a valid collection type.
5463
QRY_COLLECTION_TYPE_UNSUPPORTED
Unsupported collection type.
5464
QRY_ATTR_NOT_FOUND
Attribute does not exist for class.
5465
QRY_INVALID_PARSE_BLOCK
Invalid parse block.
5466
QRY_PREDICATE_UNEXPECTED_TYPE
Unexpected query predicate type
5467
QRY_PREDTERM_UNEXPECTED_TYPE
Unexpected query predterm type
5468
QRY_UNSUPPORTED_COND_OP
Unsupported conditional operator in query
5469
QRY_PARAM_NOT_SUBSTITUTED
Query parameter $(paramName) not
substituted
5470
QRY_CAN_NOT_TAKE_CANDIDATE_COLLECTION
Candidate collection can not be set for select
with vstr or candidate collection queries
5471
QRY_UNSUPPORTED_DATA_TYPE
This data type is not supported in queries
5472
QRY_INVALID_DATA_TYPE
This data type is invalid
5473
QRY_PARAM_SIZE_MISMATCH
Given param size does not match with size of
parameter's data type
5474
QRY_PARAM_STRING_NOT_NULL_TERMINATED
Given param string is not null terminated
5475
QRY_PARAM_STRING_SIZE_MISMATCH
Given param string length does not match
with specified param Size
5476
QRY_PARAM_NOT_FOUND
Param $(paramName) not found
5477
QRY_CANDIDATE_NOT_FOUND
Candidate $(candidateName) not found
5478
QRY_API_NULL_ARGUMENT
Api argument $(argnum) is NULL
5479
QRY_API_INVALID_START_POS
Invalid start position
5480
QRY_UNSUPPORTED_COND_OP_IN_COMPLEXEXPR
Conditional operator $(condop) in complex
expression not yet supported
5481
QRY_FETCH_SIZE_EXCEEDED_ MAX
Fetch size exceeded allowed maximum value
5482
QRY_MAX_RESULT_COUNT_EXCEEDED_MAX
Max result count exceeded allowed maximum
value
5483
QRY_INVALID_HANDLE
Query handle is invalid
5484
QRY_INCORRECT_SESSION
This query does not belong to this session
Versant Error Codes Reference
39
Query Errors, Series — 5400
5485
QRY_RESULT_UNUSABLE
Query result is unusable and should be
destroyed
5486
QRY_RESULT_INVALID_HANDLE
Query result handle is invalid
5487
QRY_RESULT_INCORRECT_SESSION
This query result does not belong to this
session
5488
QRY_RESULT_BACKWARD_SEEK_NOT_SUPPORTED
Moving backward in query result is not
supported
5489
QRY_RESULT_RECORDNUM_EXCEEDED_MAX
Recordnum exceeded allowed maximum value
5490
QRY_RESULT_CURRENT_POSITION_AT_BEFORE_FIRST Current cursor position is at before the first
record
5491
QRY_RESULT_ENCOUNTERD_END
Encountered end of query result
5492
QRY_RESULT_INVALID_ PROJNUM
Invalid projnum
5493
QRY_RESULT_INVALID_RECORDNUM
Invalid record number
5494
QRY_NULL_DOMAIN_ATTRIBUTE
Null domain attribute in path expression
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
40
Versant Error Codes Reference
Version Errors, Series — 5600
2.9. Version Errors, Series — 5600
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
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
Versant Error Codes Reference
41
Schema Errors, Series — 6000
2.10. Schema Errors, Series — 6000
6000
SCH_BASE
For schema manager
6001
SCH_CLASS_DEFINED
Class already defined
6002
SCH_CLASS_UNDEFINED
Class $(class) undefined
6003
SCH_NULL_CLSNAME
Null class name
6004
SCH_BAD_SUPERCLASS
Bad superclass $(class)
6005
SCH_BAD_ATTRNAME
Bad attribute name $(attribute)
6006
SCH_BAD_METHNAME
Bad method name
6007
SCH_BAD_DOMAIN
Bad domain $(class)
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
Specified index cannot be defined on the given
attribute
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
42
Versant Error Codes Reference
Schema Errors, Series — 6000
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
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
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
Versant Error Codes Reference
43
Schema Errors, Series — 6000
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
6080
SCH_DUP_PARTITIONS
Duplicate partition sequence
6081
SCH_NO_ATTR_CLASS
Cannot find storage of class attribute
6082
SCH_NULL_METHDESC
Null method description
6083
SCH_CANT_MODIFY_CLASS
Cannot modify schema for class $(class) because there
are other active clients that may be using it
6084
SCH_CANT_BEGIN_TR
Cannot begin transaction because there is at least one
active transaction modifying the database schema
6085
SCH_CANT_READ_CLASS
Could not read the schema for class $(class) (timeout
occurred). Another transaction is probably evolving
the schema.
44
Versant Error Codes Reference
Schema Errors, Series — 6000
6086
SCH_CANT_UPD_INHERITANCE
Can't update inheritance for non empty class
$(classname) because of index ${indexname}
6087
SCH_E_CONVERT_OBJ
Could not convert schema for class into/from canonical
format
Versant Error Codes Reference
45
Container Errors, Series — 6200
2.11. Container Errors, Series — 6200
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
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
46
Versant Error Codes Reference
Container Errors, Series — 6200
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
6333
CONT_MEM_ROOT_IS_PINNED
Root is still pinned
Versant Error Codes Reference
47
Event Notification Errors, Series — 6500
2.12. Event Notification Errors, Series — 6500
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 database 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 notification 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 $(loid) does not exist
48
Versant Error Codes Reference
Event Notification Errors, Series — 6500
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
6533
EV_CLASS_INVALID_NUM_ OBJ
class %s has %d num instances, it should only have %d
6534
EV_BAD_DB
Inconsistent pewcrsistent ev schema (possibly caused
by user changing its schema)
6535
EV_ASSERT_FAIL
Internal assertion failure
6536
EV_REG_ALL_OBJ_DEL
ev registration $(loid) is invalidated, all of its registered
objects have been deleted
6537
EV_ERR_INCOMPATIBLE
Pre 5.0 app using event with new event mode is not
supported
6538
EV_FE_DIED
Frontend has died
6539
EV_ERR_DB_SHUTDOWN
Db is shutting down. (possible by stopdb -st
6540
EV_ERR_DAEMON_EXIST
A event daemon exists. Mutliple event daemon is not
supported in current release
Versant Error Codes Reference
49
Virtual Attribute Errors, Series — 6600
2.13. Virtual Attribute Errors, Series — 6600
6600
VA_BASE
6601
VA_PARSE_FAILED
Invalid syntax of VA
6602
VA_NOT_INITIALIZED
VA is not initialized
6603
VA_VAT_NOT_FOUND
VAT is not defined
6604
VA_VA_INIT_ERR
VA initialization error
6605
VA_KEY_NOT_MATCH
Key items doesn't match attribute items
6606
VA_KEY_PARSE_FAILED
Key has wrong format
6607
VA_TYPE_UNSUPPORTED
Wrong Type Or Type Is Not Supported Yet
6608
VA_KEY_OVERFLOW
Key Value Overflowed
6609
VA_NOT_VALID_CMP_FLAG
Invalid Compare Method
6610
VA_INTERNAL_ERROR
Va Internal Error
6611
VA_EMPTY_KEY
Key Is An Empty String
6612
VA_HASH_INDEX_NOT_SUPPORTED
Hash Index On VA Not Supported
6613
VA_INDEX_ALREADYEXISTS
duplicate index not allowed
6614
VA_NO_SUCH_INDEX
Non-existing index
6615
VA_INDEX_NOT_SUPPORTED_IN_FTS
Index operations on replica databases not supported
yet
6616
VA_EXISTED_IN_HASHtable
Entry Is In Hashtable Already
6617
VA_NO_CLASS_VERSION_FOUND
Class Doesn't Have Any Instance
6618
VA_NOT_INDEXABLE
Indexing Not Supported On This Virtual Attribute
6619
VA_INSUF_ARGS
Insufficient No. Of Arguments
6620
VA_MEMALLOC_ERROR
Memory Allocation Error
6621
VA_INCORRECT_TYPE
Received Incorrect Type Of Argument
6622
VA_NULL_SPECIFIC
Va_Getspecific Returned NULL
6623
VAT_CONSTRUCTOR_ERROR
Error $(Err) In Vat_Constructor
6624
VAT_DESTRUCTOR_ERROR
Error $(Err) In Vat_Destructor
6625
VAT_VALUES_ERROR
Error $(Err) In Vat_Values
6626
VAT_COMPARE_ERROR
Error $(Err) In Vat_Compare
50
Versant Error Codes Reference
Virtual Attribute Errors, Series — 6600
6627
VA_QUERY_OPERATOR_NOT_SUPPORTED
Versant Error Codes Reference
Operator Not Supported
51
System Utility Errors, Series – 7000, 9000, 11000,
12300
2.14. System Utility Errors, Series – 7000, 9000, 11000, 12300
7000
UT_OK
No error
7001
UT_DB_NOT_FOUND
DB directory not found
The database directory or one of the required database files was not found or could not be
opened. In order to successfully start up a Versant database, all of the necessary files need to
be present in the database directory. It is also important that all of these files are accessible to
the DBA user. Refer to Section 10.19, “startdb” in the Versant Server Guide for a description
of the startdb utility including a list of the required files.
7002
UT_DB_NOT_PERSONAL
Not a personal DB
7003
UT_DB_NO_ACCESS
No access rights to DB dir
You do not have appropriate permissions on the directory containing the database you are
trying to access. The solution is to check permissions on the database directory and change
them as appropriate.
7004
UT_BE_PROFILE_ERROR
Error parsing back-end profile
7005
UT_FE_PROFILE_ERROR
Error parsing front-end profile
7006
UT_ER_NOFILE
Cannot find error message file error.msg
7007
UT_ER_NO_MSG
Cannot find error message
The database server process needs to report an error, but it cannot find the error message file.
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/.osc090300 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 .osc090300 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.
7008
52
UT_DB_IS_RUNNING_ON_ANOTHER_HOST
Database is running on another machine
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
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
Could not create application process profile. Check
disk space, permissions, etc.
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
You may have tried to create a database with the 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.
Alternately, your login name may have a space in it, although Windows allows spaces in login
names, Versant does not.
7022
UT_ER_SYSTEMVOL_NOACCESS
No access to system volume
7023
UT_ER_SYSTEMVOL_FILE_TYPE
System volume already exists and is not a raw device
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 and is not a raw
device
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 and is not a raw
device
7030
UT_ER_LOGICALLOG_CREATE
Unable to create logical log volume
7031
UT_ER_DBID_NOACCESS
Failed to access database ID file
Versant Error Codes Reference
53
System Utility Errors, Series – 7000, 9000, 11000,
12300
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
Shared memory is not configured on this system.
The solution is to configure shared memory on the system according to the instructions in the
installation notes.
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
The database server process has died due to lack of system resources and/or due to an
inconsistency seen by the Versant database.
If this occurs, check the file LOGFILE in your database directory, look at error messages reported
there, and execute the solution as per the recommendation Or call Versant Technical Support.
For example, in LOGFILE you might see the following error message, 0964, SL_ATTACH_EXTEND_SEG
Cannot attach extension segments in the LOGFILE.
54
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
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.
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
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
There has been a network error or a login error.
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
Versant Error Codes Reference
55
System Utility Errors, Series – 7000, 9000, 11000,
12300
the inetd daemon. For further information, see the installation instructions in the Release
Notes.
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/.osc090300 does not have the correct 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.
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_OSC_DBID_EXISTS
Osc-Dbid File 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
7079
UT_SS_INVALID_PORTRANGE
Invalid Port specified, valid range is 2 thru 65534
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
56
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
This error probably means that you are logged on as 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
7085
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
A remote machine cannot find the location of the server process executable.
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/.osc090300 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.
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
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
Versant Error Codes Reference
57
System Utility Errors, Series – 7000, 9000, 11000,
12300
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 -- "$(db1)"
and "$(db2)" 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
7115
UT_ER_PASSWDS_DONOTMATCH
The passwords do not match!!!
7116
UT_ER_2PROCESS
Must be a two process connection.
7117
UT_ER_SOME_OBJECTS_DIFFERENT
Some objects are different in two databases
7118
UT_DB_IS_UNRESTORED_HABACKUP
The database device is an unrestored habackup
7119
UT_ER_DBALOGGING_LEVEL_IS_ZERO
The DBA logging level is zero, so DBA logging is disallowed
7120
UT_ER_DBID_EXISTS
Database id already exists in osc-dbid file
7121
UT_ER_DB_ENTRY_EXISTS
Database entry already exists in osc-dbid file
7122
TARGET_DB_NOT_CREATED
vmovedb requires that target database be
created
7123
UT_FAILED_TO_MOVE_ALL_OBJECTS
Could not move all objects
7124
UT_NO_OBJECTS_TO_MOVE
No objects to move
7125
UT_NO_REPLICA_MOVE
vmovedb is not allowed on a replica pair of
databases
7126
UT_VMOVEDB_INVALID_TARGET
The specified database is invalid for vmovedb
7127
UT_VBACKUP_INCOMPLETE
vbackup did not backup all pages
7128
UT_ER_MAKEDB_PROFILE_NOTFOUND
makedb did not find the profile file at the
Specified location
58
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
7129
UT_ER_ADDVOL_PROFILE_UPDATION_FAILED
7130
UT_ER_ADDVOL_DATAVOL_ENTRY_ALREADY_EXISTS datavol entry already exists in server profile file
7131
UT_ER_DATAVOL_ALREADY_EXISTS
data volume at the specified location already
exists
7132
UT_ER_VBACKUP_RESTORE_REMOVE_DATABASE
vbackup restore process is unable to remove
creation time database files of renamed
database
7133
UT_ER_VBACKUP_DUPLICATE_RESTORE
Another process is doing restore already
7134
UT_ER_USER_ABORT_REQUEST
Aborted at user's request.
7135
UT_ER_ALREADY_CONVERTED
Database version is same as current release version.
No need to convert
7136
UT_ER_STARTUP_ABSOLUTE_PATH
Error launching startup executable. Absolute path is
not allowed.
7137
UT_ER_STARTUP_IS_DIR
Error launching startup executable. $(file) is a
directory.
7138
UT_ER_STARTUP_NOT_FOUND
OS err #$(oserr) while launching startup executable.
$(file) could not be found.
7139
UT_ER_STARTUP_INCORRECT_PERMISSIONS Error launching startup executable. $(file) has write
permission for users other than DBA.
7140
UT_ER_STARTUP_IS_LINK
Error launching startup executable. $(file) is a
symbolic link.
7141
UT_ER_STARTUP_WRITE_LOG
OS err #$(oserr) while writing to log file. Launching
startup executable failed.
7142
UT_ER_STARTUP_LAUNCH
Launching startup executable $(file) failed.
7143
UT_ER_STARTUP_SET_PROCID
Error while trying to save the startup executable
process-id
7144
UT_ER_STARTUP_ALREADY_RUNNING
Cannot start database. A previous instance of the
startup script is already running with process-id
$(pid)
7145
UT_ER_STARTUP_GET_DBDIR
Error retrieving database directory.
7146
UT_ER_STARTUP_OPEN_LOG
Error while opening $(file) for writing.
7147
UT_ER_STARTUP_NOT_EXECUtable
Error launching startup executable. $(file) does not
have execute permission for DBA.
Versant Error Codes Reference
addvol failed to update server profile file with
datavol entry
59
System Utility Errors, Series – 7000, 9000, 11000,
12300
7159
UT_ER_ARCHIVER_ALREADY_RUNNING
Archiver process is already running.
7160
UT_CONFIG_PARAM_UNKNOWN
Unknown configuration parameter ($(parameter)) at
line $(line) in the database configuration file at
&(path).
7161
UT_CONFIG_PARAM_SYNTAX
Syntax error while parsing argument for parameter
($(parameter)) at line $(line) in the database
configuration file at &(path).
7162
UT_CONFIG_PARAM_LIST_UNKNOWN
Unknown configuration parameter ($(parameter)) in
nvlist.
7163
UT_CONFIG_PARAM_LIST_SYNTAX
Syntax error while parsing value ($(value)) for
parameter ($(parameter))
7164
UT_ER_DBID_ZERO
Database has dbid zero, use setdbid to set a valid
value
Your database has an invalid dbid. Before you can start the database you need to set the dbid
to a new valid value. A valid value is one that has not been used for the current or any other
databases in the database network to which the current database belongs. The following steps
can be used to determine the list if previously used dbids in the database network.
Get the list of all databases in the database network that contains the current database. Dblist
(It is safe to call this command on a productive system.)
For each of the databases listed, you need to get the dbid history list. dbtool -AT -info -rootpages
<db> (It is safe to call this command on a running database.)
You will find the dbids used for each DB in the first column of the output. For instance, the
output below shows that dbid 1 and dbid 43 are or have been in use.
c:\>dbtool -AT -info -rootpages tutorialdb
VERSANT Utility DBTOOL Version 9.3.0
Copyright (c) 1988-2017 VERSANT Corporation
The original dbid is 1
The current dbid is 43
The current file version is 5
AT RootPage information per dbid:
dbid
Globaldepth
Cardinality
RootPID
Max Object ID
60
Num. of RootPages
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
====
1
0:55
43
0:886
===========
===========
9
1.0.246802
8
43.0.201544
200640
200448
=================
=======
===========
1
1
You will need to determine the lowest non-zero integer that is not in use and has not been in
used so far by all the databases belonging to the database network.
Set the dbid for the currently non-startable database to the value you determined.
1. dbinfo -1 <db>
2. stopdb -s <db>
3. setdbid <new DBID> <db>
4. dbinfo -m <db>
7165
UT_SS_PID_FILE_CANNOT_WRITE
ss.d cannot write the pid file under /tmp.
7166
UT_SS_PID_FILE_NOT_FOUND
When ss.d is called with -stop the correct pid file for
the daemon to be killed is not found under /tmp.
7167
UT_SS_KILL_DAEMON_FAILED
ss.d was called with -stop but failed to stop the
desired daemon process.
7168
UT_CONFIG_PARAM_ILLEGAL
Illegal/unknown parameter name "$(parameter)"
7169
UT_CONFIG_PARAM_NON_TUNABLE
Parameter "$(parameter)" cannot be tuned at
run-time
7170
UT_CONFIG_VALUE_ILLEGAL
Value "$(value)" is not a valid value or outside the
allowed range
7171
UT_ER_LEVEL2FILE_INCONSISTENT
Recreating AT is not possible while a level 2 file is
inconsistent.
7172
UT_CONFIG_PARAM_NOT_SUPPORTED
Parameter "$(parameter)" is currently not supported
for tunability. You need to manually edit the
configuration file
7173
UT_ER_BLACKBOX_WRONG_VERSION
Incompatible black box versions. Current version is
$(current_version). Version of this file is
$(file_version).
Versant Error Codes Reference
61
System Utility Errors, Series – 7000, 9000, 11000,
12300
7174
UT_SS_IMPLICIT_STARTDB
Starting database implicitly is prohibited by
profile.be.
7175
UT_ER_PROC_SUSPENDED
process is suspended by a crash anchor
7176
UT_VSERVER_RUNNING
can not connect to vserver but appears to be already
running
This code is returned to the client if the requested database is apparently running, i.e., started,
but no connection to the server process is possible.
Refer occurrences of this error to the database administrator (DBA).
7177
UT_SHUTDOWN_NOT_COMPLETED
Shutdown not completed yet. vserver process $(pid)
still alive.
This error code is returned by the stopdb utility if the database shutdown is not completed
within a specified amount of time, currently set at 300 seconds. This does not apply to a forced
shutdown, stopdb -f.
The database shutdown proceeds and may still complete after receipt of this code. You have
the following options.
• Monitor the system processes for termination of the vserver process
• Send the same stopdb command again to verify the shutdown (calling stopdb with the same
stop mode does not interfere with a previous call)
• Send the stopdb command again but with a stricter stop mode (calling stopdb -f will force
a shutdown)
Refer to Section 10.20, “stopdb” in the Versant Server Guide
utility and the available stop modes.
7178
UT_STARTDB_ABORTED
for descriptions of the stopdb
Starting database aborted.
While waiting for internal service threads to become ready, either stopdb was requested via a
signal or an internal timeout was reached.
7179
UT_LEGACY_CONNECTOR_DISABLED
Legacy connector disabled in profile.be
A legacy client (a client based on a Versant release prior to 9.2) receives this error when
attempting to connect to a Versant Server with legacy client connections disabled. Refer to
legacy_connector in the Versant Server Guide .
Error codes 7180 to 7188 are licensing errors. If you encounter any of these errors, rerun vlicvrfy utility
to get further details about the cause of the error. If required, contact Versant for new license key for
the component.
62
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
7180
LIC_ERR_ARGS
Error in arguments passed
7181
LIC_ERR_NODE
Component not licensed
7182
LIC_ERR_DATE
License expired
7183
LIC_ERR_ENVVARIABLE
Environment variable not set
7184
LIC_ERR_FILENOTFOUND
License file not found
7185
LIC_ERR_FILESYNTAX
Error in license file
7186
LIC_ERR_TEXTIGNORE
Ignoring text in license file
7187
LIC_ERR_VMDETECT
Component not licensed under virtualization
7188
LIC_ERR_VMCORES
The number of licensed cores is less than the actual
cores.
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
7207
UT_ABNORMAL_EXIT
Utility process was killed or crashed. Command was
$(command)'.
7208
UT_ER_VBACKUP_FILE_READ
Cannot read vbackup status file for specified database
7209
UT_ER_VBACKUP_FILE_WRITE
Cannot write to vbackup status file for specified database
7210
UT_ER_VBACKUP_FILE_NO_ACCESS
Cannot access vbackup status file for specified database
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
Replication does not support personal databases
Versant Error Codes Reference
63
System Utility Errors, Series – 7000, 9000, 11000,
12300
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
7250
UT_FTS_INVALID_PDELAY
Invalid polling delay. Must be either 0 or -1
7251
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 $(utility) Version $(version) $(comment)
7256
MSG_VERSANT_COPYRIGHT
Copyright (c) $(from_year)-$(current_year) Versant
Corporation
7257
MSG_PANIC
Versant panicking in file '%s' at line %d
64
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
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
7276
MSG_UDLTOOL_USAGE_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
Versant Error Codes Reference
%% %s [-d ddbname] [-l sdbname] [-n] [-p] [-s
[lm]] [filename]
65
System Utility Errors, Series – 7000, 9000, 11000,
12300
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 name for volume
7298
MSG_ADDVOL_USAGE_3
-p volpath path of volume device/file
7299
MSG_ADDVOL_USAGE_4
Options
7300
MSG_ADDVOL_USAGE_5
-s volsize volume size, default to 128M
7301
MSG_ADDVOL_USAGE_6
-e extsize extent size
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
-il pre-initialize the physical and logical logs to
logvolmaxsize
7319
MSG_CREATEDB_USAGE_4
-noprint suppress display messages
7320
MSG_CREATEDB_USAGE_5
Dbname: database name
7321
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 , '-passwd' option maybe
specified
7330
MSG_DBUSER_USAGE_5
-delete delete user from access list
66
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
7331
MSG_DBUSER_USAGE_6
'-n' or '-P' options required
7332
MSG_DBUSER_USAGE_7
-chpasswd change the password for an existing user
7333
MSG_DBUSER_USAGE_8
'-n' options required '-opasswd' and '-passwd' options
may be specified
7334
MSG_DBUSER_USAGE_9
Options:
7335
MSG_DBUSER_USAGE_10
-n name user name
7336
MSG_DBUSER_USAGE_11
-passwd password password
7337
MSG_DBUSER_USAGE_12
-opasswd old-password old password
7338
MSG_DBUSER_USAGE_13
-P public access
7339
MSG_DBUSER_USAGE_14
-m r | rw access mode
7340
MSG_DBUSER_USAGE_15
-noprint suppress display messages
7341
MSG_DBUSER_USAGE_16
Dbname: database name
7342
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 | -p ]
7348
MSG_MAKEDB_USAGE_3
-g group database
7349
MSG_MAKEDB_USAGE_4
-p personal database
7350
MSG_MAKEDB_USAGE_5
-owner user make user as owner of database
directory
7351
MSG_MAKEDB_USAGE_6
-cpprofile db copy profiles from the specified db
7352
MSG_MAKEDB_USAGE_7
Directory
7353
MSG_MAKEDB_USAGE_8
-nofeprofile do not create front-end profile
7354
MSG_MAKEDB_USAGE_9
-logging turn logging on
7355
MSG_MAKEDB_USAGE_10
-locking turn locking on
7356
MSG_MAKEDB_USAGE_11
-noprint suppress display messages
7358
MSG_MAKEDB_USAGE_13
-promptpasswd prompt for DBA's password
7359
MSG_MAKEDB_USAGE_14
-beprofile filepath — copy server profile file from
specified location
Versant Error Codes Reference
67
System Utility Errors, Series – 7000, 9000, 11000,
12300
7360
MSG_MAKEDB_USAGE_15
-feprofile filepath — copy application profile file from
specified location
7361
MSG_MAKEDB_USAGE_16
-feprofile and -nofeprofile — cannot be specified
together
7362
MSG_MAKEDB_USAGE_17
-feprofile and -beprofile — cannot be used with
-cpprofile
7363
MSG_MAKEDB_USAGE_18
Dbname: database name
7364
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 | -0 | -1 | -d ]
7378
MSG_DBINFO_USAGE_3
-m set multi-user mode
7379
MSG_DBINFO_USAGE_4
-0 set unstartable mode
7380
MSG_DBINFO_USAGE_5
-1 set DBA-only single-connection
7381
MSG_DBINFO_USAGE_6
-d set DBA-only multi-connection
7382
MSG_DBINFO_USAGE_7
-p print existing database mode
7383
MSG_DBINFO_USAGE_8
-c create a new .lock file
7384
MSG_DBINFO_USAGE_9
Dbname: database name
7385
MSG_DBINFO_USAGE_END
Usage: dbinfo
7387
MSG_REMOVEDB_USAGE
Usage: removedb [options] <dbname>
7388
MSG_REMOVEDB_USAGE_1
Options :
68
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
7389
MSG_REMOVEDB_USAGE_2
7390
MSG_REMOVEDB_USAGE_3
-rmdir remove database directory
7391
MSG_REMOVEDB_USAGE_4
-noprint suppress display messages
7392
MSG_REMOVEDB_USAGE_5
Dbname: database name
7393
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 | -s | -st ]
7406
MSG_STOPDB_USAGE_3
-f force killing all active transactions
7407
MSG_STOPDB_USAGE_4
-s wait for update rpcs to be done
7408
MSG_STOPDB_USAGE_5
-st wait for all active transactions to be done
7409
MSG_STOPDB_USAGE_6
-noprint suppress display messages
7410
MSG_STOPDB_USAGE_7
Dbname: database name
7411
MSG_STOPDB_USAGE_END
Usage: stopdb
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
-noprint suppress display messages
7423
MSG_MAKEPROFILE_USAGE_8
Dbname: database name
7424
MSG_MAKEPROFILE_USAGE_END
Usage: makeprofile
7426
MSG_DBID_USAGE
Usage: dbid [options] <dbname>
7427
MSG_DBID_USAGE_1
Options :
7428
MSG_DBID_USAGE_2
-N Create an osc-dbid file. <dbname> is not specified
Versant Error Codes Reference
-f force removing database
69
System Utility Errors, Series – 7000, 9000, 11000,
12300
7429
MSG_DBID_USAGE_3
7430
MSG_DBID_USAGE_4
-C <dbid> Create an entry in osc-dbid file for database
<dbname>
7431
MSG_DBID_USAGE_5
And database id as <dbid>.
7432
MSG_DBID_USAGE_6
-t <type> Specify the type of database (group or
personal )
7433
MSG_DBID_USAGE_7
Must be used with -c or -C options.
7434
MSG_DBID_USAGE_8
Default database type is group.
7435
MSG_DBID_USAGE_9
-d Remove the database <dbname> entry from the
osc-dbid file
7436
MSG_DBID_USAGE_10
-r Print the database id of the database <dbname>
7437
MSG_DBID_USAGE_11
-noprint Suppress display messages
7438
MSG_DBID_USAGE_12
Dbname: database name
7439
MSG_DBID_USAGE_13
Type: database type
7440
MSG_DBID_USAGE_14
1: Personal database
7441
MSG_DBID_USAGE_15
2: Group database
7442
MSG_DBID_USAGE_END
Usage: dbid
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
70
-c Create an entry in osc-dbid file for database
<dbname>
-i environment information
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
7469
MSG_OSCP_USAGE_4
-l product version number with patch
7470
MSG_OSCP_USAGE_5
-n dbid node name
7471
MSG_OSCP_USAGE_6
-o 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_10
-b patch information
7476
MSG_OSCP_USAGE_END
Usage: oscp
7477
MSG_SSD_USAGE
Usage: ss.d <command> [options]
7478
MSG_SSD_USAGE_1
Command:
7479
MSG_SSD_USAGE_2
-start start the system services daemon, requires '-port'
option
7480
MSG_SSD_USAGE_3
Options:
7481
MSG_SSD_USAGE_4
-port port-number port number where ss.d has to accept
new Versant connection
7482
MSG_SSD_USAGE_5
-log log-file-name logs additional information to
specified log file
7483
MSG_SSD_USAGE_END
Usage: ss.d
7495
MSG_CONVERTDB_USAGE
Usage: convertdb <dbname>
7496
MSG_CONVERTDB_USAGE_1
Options:
7497
MSG_CONVERTDB_USAGE_2
-noprint suppress display messages
7498
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
Versant Error Codes Reference
71
System Utility Errors, Series – 7000, 9000, 11000,
12300
7518
MSG_DBID_VERSION2
ersion2 = %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 = %s
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
7564
MSG_DB_ENV
VERSANT_DB: %s
7565
MSG_DBID_ENV
VERSANT_DBID: %s
7566
MSG_REL_ENV
VERSANT_REL: %s
72
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
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
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 = %u pages (page size = %d bytes)
7638
MSG_ADDVOL_PATH
Volume path = %s
Versant Error Codes Reference
73
System Utility Errors, Series – 7000, 9000, 11000,
12300
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=%u pages ( page size = %d bytes )
7648
MSG_CREATEDB_LLOG
Logical log volume created at %s
7649
MSG_CREATEDB_LLOG_INFO
Size=%u pages ( page size = %d bytes )
7650
MSG_CREATEDB_SYSVOL
System volume created at %s
7651
MSG_CREATEDB_SYSVOL_INFO
Size=%u pages ( page size=%d bytes ), 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
Can't find error message file error.msg
7687
MSG_MSG_CREATE_INDEX
Can't create error message index file error.msi
7688
MSG_MSG_WRITE_INDEX
Error while writing error message index file error.msi
74
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
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
7709
MSG_STARTDB_BEGIN_PREINIT_PLOG
Beginning physical log pre-initialization phase
7710
MSG_STARTDB_BEGIN_PREINIT_LLOG
Beginning logical log pre-initialization phase
7711
MSG_STARTDB_END_PREINIT_PLOG
Ending physical log pre-initialization phase
7712
MSG_STARTDB_END_PREINIT_LLOG
Ending logical log pre-initialization 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
-threads N fork N threads for copying
7721
MSG_CREATEREPLICA_USAGE_6
-batchsize M copy M objects per transaction default
= 1000)
7722
MSG_CREATEREPLICA_USAGE_7
Dbname: name of database to replicate
7723
MSG_CREATEREPLICA_USAGE_8
Replica-dbname: database name for replica
7724
MSG_CREATEREPLICA_USAGE_9
-nocreate and -i cannot be used together
7725
MSG_CREATEREPLICA_USAGE_END
Usage: createreplica
7726
MSG_REMOVEREPLICA_USAGE
Usage: removereplica [options] <replica-dbname>
7727
MSG_REMOVEREPLICA_USAGE_1
Options:
Versant Error Codes Reference
75
System Utility Errors, Series – 7000, 9000, 11000,
12300
7728
MSG_REMOVEREPLICA_USAGE_2
-f force removing of database
7729
MSG_REMOVEREPLICA_USAGE_3
-rmdir remove database directory
7730
MSG_REMOVEREPLICA_USAGE_4
-noprint suppress display messages
7731
MSG_REMOVEREPLICA_USAGE_5
Replica-dbname: name of replica database
7732
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
-advanced -classes <class1> <class2> ... Compare
only the listed classes
7740
MSG_COMPAREDB_USAGE_5
-classes <class1> <class2> ... Compare only the listed
classes
7741
MSG_COMPAREDB_USAGE_6
-fullcompare list all the differences (option
incompatible with -noprint)
7742
MSG_COMPAREDB_USAGE_7
Db1: name of first database
7743
MSG_COMPAREDB_USAGE_8
Db2: name of second database
7744
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
sage: setdbid
7765
MSG_CREATEREPLICA_DONE
76
The replica has been successfully created.
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
7766
MSG_REMOVEREPLICA_DONE
The replica has been successfully removed.
7767
MSG_REPLICA_FILE_REMINDER
**REMEMBER TO CHECK 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.
7770
MSG_COMPAREDB_DIFFERENCES
Some of the objects are different in two 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
7788
MSG_DELUSER_USAGE_3
-P public access
7789
MSG_DELUSER_USAGE_4
-noprint suppress display messages
7790
MSG_DELUSER_USAGE_5
Dbname: database name
7791
MSG_DELUSER_USAGE_END
Usage: deluser
7792
MSG_POLLING_BEGIN
Polling process %d begins
7793
MSG_POLLING_BEGINSESSION
Polling begin session on %s
7794
MSG_POLLING_ENDSESSION
Polling end session
7795
MSG_POLLING_CONNECTDB
Polling connectdb to %s
7796
MSG_POLLING_DISCONNECTDB
Polling disconnect from %s
7797
MSG_POLLING_SETDBUP
Polling set %s to UP
7798
MSG_POLLING_SETDBSYNC
Polling set %s to SYNC
7799
MSG_POLLING_RECURSIVE_FAIL
Polling gets recursive failure on %s
7800
MSG_POLLING_FAIL
Polling process fails on %s with err %d
7801
MSG_POLLING_EXIT_OK
Polling exits successfully
Versant Error Codes Reference
77
System Utility Errors, Series – 7000, 9000, 11000,
12300
7802
MSG_POLLING_EXIT_FAIL
Polling exits with err %d
7803
MSG_POLLING_SETDB_FAIL
Polling set db status on %s fails with err %d
7804
MSG_POLLING_BEGINSESSION_FAIL
Polling begin session on %s fails with err %d
7805
MSG_POLLING_ENDSESSION_FAIL
Polling end session fails with err %d
7806
MSG_POLLING_CONNECTDB_FAIL
Polling connectdb fails with err %d
7807
MSG_POLLING_BEGIN_SYNC
Polling begins to do the sync from %s to %s
7808
MSG_POLLING_SYNC_FAIL
Polling sync fails with err %d
7809
MSG_POLLING_DISCONNECTDB_FAIL
Polling disconnectdb fails with err %d
7810
MSG_POLLING_SET_UNSTARtable
Polling has set %s to unstartable mode automatically
7811
MSG_POLLING_SET_MULTIUSER
Polling has set %s back to multi-user mode
7812
MSG_POLLING_USAGE
Usage: polling <fromdb> <todb>
7813
MSG_POLLING_COMMIT
Polling does a commit
7814
MSG_POLLING_COMMIT_FAIL
Polling commit fails with err %d
7815
MSG_POLLING_SYNC_OK
Polling finishes the sync successfully
7816
MSG_POLLING_RUNNING
Polling already running
7817
MSG_POLLING_VANISH
Polling disappeared
7818
MSG_VCOPYDB_USAGE
Usage: vcopydb [options] <dbname> <replica-dbname>
7819
MSG_VCOPYDB_USAGE_1
Options:
7820
MSG_VCOPYDB_USAGE_2
-nolock ignore locks in source db
7821
MSG_VCOPYDB_USAGE_3
-i pre-allocate and initialize the database
7822
MSG_VCOPYDB_USAGE_4
-noprint suppress display messages
7823
MSG_VCOPYDB_USAGE_5
-nocreate copy to existing database
7824
MSG_VCOPYDB_USAGE_6
-threads N fork N threads for copying
7825
MSG_VCOPYDB_USAGE_7
-batchsize M copy M objects per transaction (default =
1000)
7826
MSG_VCOPYDB_USAGE_8
Dbname: name of database to replicate
7827
MSG_VCOPYDB_USAGE_9
Replica-dbname: database name for replica
7828
MSG_VCOPYDB_USAGE_10
nocreate and -i cannot be used together
7829
MSG_VCOPYDB_USAGE_END
Usage: vcopydb
7832
MSG_POLLING_SETTING_MULTIUSER
Polling is setting %s back to multi-user mode
78
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
7833
MSG_VCOPYDB_DONE
7835
MSG_FTSTOOL_USAGE
Usage: ftstool [options] <dbname>
7836
MSG_FTSTOOL_USAGE_1
Options:
7837
MSG_FTSTOOL_USAGE_2
-p T fork a polling process after T seconds
7838
MSG_FTSTOOL_USAGE_3
T can be either:
7839
MSG_FTSTOOL_USAGE_4
: no delay, or
7840
MSG_FTSTOOL_USAGE_5
-1: disable automatic forking
7841
MSG_FTSTOOL_USAGE_6
-disable/-forcedisable
7842
MSG_FTSTOOL_USAGE_7
-enable
7843
MSG_FTSTOOL_USAGE_8
-stopsync [-batchsize N] change database to
SUSPEND state
7844
MSG_FTSTOOL_USAGE_9
Polling records are discarded in batches: default N
= 1000
7845
MSG_FTSTOOL_USAGE_10
-status
7846
MSG_FTSTOOL_USAGE_11
Dbname: database name
7847
MSG_FTSTOOL_USAGE_END
Usage: ftstool
7848
MSG_FTSTOOL_CURRENTPD
Current polling delay: %d
7849
MSG_FTSTOOL_SETPD
Setting polling delay to %d
7850
MSG_FTSTOOL_SUSPEND
Database state changed to SUSPEND
7855
MSG_VERSANT_RELEASE
Versant Release Version: %s
7856
MSG_PLATFORM
Platform: %s
7857
MSG_OS
Operating System: %s
7858
MSG_OS_PATCH
OS Patch Info: %s
7859
MSG_C
C Version: %s
7860
MSG_CPLUSPLUS
C++ Version: %s
7861
MSG_CPLUSPLUS_PATCH
C++ Patch Info: %s
7865
MSG_VARCOMPARE_USAGE
Usage: varcompare -classes <class1> <class2> ... <db1>
<db2>
7866
MSG_VARCOMPARE_USAGE_1
Db1: name of first database
Versant Error Codes Reference
The database has been successfully copied.
79
System Utility Errors, Series – 7000, 9000, 11000,
12300
7867
MSG_VARCOMPARE_USAGE_2
Db2: name of second database
7868
MSG_VARCOMPARE_USAGE_END
Usage: varcompare
7869
MSG_VMOVEDB_USAGE
Usage: vmovedb [options] [-C c1 c2 c3 ...] <source>
<target>
7870
MSG_VMOVEDB_USAGE_1
Options:
7871
MSG_VMOVEDB_USAGE_2
-subclasses select all subclasses for the specified
classes
7872
MSG_VMOVEDB_USAGE_3
-closure L move objects in closure set for L levels
7874
MSG_VMOVEDB_USAGE_5
batchsize S move S objects per transaction (default =
1000)
7875
MSG_VMOVEDB_USAGE_6
-C <c1> <c2> <c3> .... Select objects from classes c1,
c2, c3 only (default = all user defined classes)
7876
MSG_VMOVEDB_USAGE_7
Source: name of source database
7877
MSG_VMOVEDB_USAGE_8
Target: name of the target database
7878
MSG_VMOVEDB_USAGE_END
Usage: vmovedb
7879
MSG_VMOVEDB_DONE
Vmovedb completed successfully
7880
MSG_GETVBACKUPSTATUS_USAGE
Usage: getvbackupstatus <dbname>
7881
MSG_GETVBACKUPSTATUS_USAGE_END
Usage: getvbackupstatus
7882
MSG_GETVBACKUPSTATUS_DONE
Getvbackupstatus executed successfully
7885
MSG_VLICVRFY_USAGE
Usage: vlicvrfy [ <license-file> ]
7886
MSG_VLICVRFY_USAGE_END
Usage: vlicvrfy
7887
MSG_VLICCHK_USAGE
Usage: vlicchk -c <component> -v <version>
[<license-server>]
7888
MSG_VLICCHK_USAGE_END
Usage: vlicchk
9601
EVJ_BAD_SESSION
Bad session, or session not begun, or session ended
9602
EVJ_JAVA_CTOR
Constructor failed for a java class
9603
EVJ_BAD_LOID_STRING
String not valid for conversion to Handle
9604
EVJ_THREW_ERROR
Internal error
9605
EVJ_BOMB
Internal error
9606
EVJ_OUT_OF_MEMORY
Out of Memory
9607
EVJ_BAD_UNICODE_UTF
Cannot convert UTF characters to unicode
80
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
9608
EVJ_NO_SUCH_ATTR
Attribute does not exist
9609
EVJ_BAD_ATTR_TYPE
Attribute is wrong type
9610
EVJ_NOT_IMPLEMENTED
Feature not implemented
9611
EVJ_NOT_CLASS_OBJ
Operation requires a class object
9612
EVJ_BAD_CAPABILITY
Valid newsessioncapability required
9613
EVJ_ALREADY_CAPABILITY
Only one newsessioncapability can be created
9614
EVJ_NOT_HANDLE_OBJ
Handlevector contains a non-handle object
9615
EVJ_CANNOT_GETPUT_PATH_ATTR
Cannot get/put on an attribute object for path query
only
9616
EVJ_CANNOT_GETPUT_EMPTY_HANDLE
Cannot get/put on an empty handle which does not
correspond to any database objects
9617
EVJ_CANNOT_END_SESSION_INUSE
Cannot end a session which is in use
9618
EVJ_CANNOT_END_UNATTACHED_SESSION Cannot end a session which is not attached by this
thread
9619
EVJ_QUERY_PARAMETER_COUNT_INVALID
Any parameters specified in VQL query string are
not set by a call to bind
9620
EVJ_HANDLE_OPERATION_INVALID
The operation on the handle is invalid because it
contains a Smalltalk constant
9621
EVJ_SESSION_MISMATCH
The session of the current thread is different from
the session of the persistent object
9622
EVJ_CURSOR_VQLQUERY_INVALID
This type of vqlquery String is not supported for
cursor based queries
9800
EVJ_METHOD_NOT_SUPPORTED
The method is not implemented in this class
9801
EVJ_NOT_A_PERSISTENT_CLASS
The class of the object does not belong to a
persistent category
9802
EVJ_PARAMETER_INVALID
The specified parameter is invalid
9803
EVJ_SCHEMA_JAVA_DB_TYPE_MISMATCH
The database schema differs from the Java class
definition with repsect to the type of an attribute
9804
EVJ_SCHEMA_JAVA_ATTR_MISSING
The database schema differs from the Java class
definition because attribute present in the database
schema is missing from the Java class definition
9805
EVJ_SCHEMA_DB_ATTR_MISSING
The database schema differs from the Java class
definition because an attribute present in the Java
Versant Error Codes Reference
81
System Utility Errors, Series – 7000, 9000, 11000,
12300
class definition does not exist in the database
schema
9806
EVJ_SERIALIZATION_EXCEPTION
Serialization of an object failed.
9807
EVJ_DESERIALIZATION_EXCEPTION
Deserialization of an object failed
9808
EVJ_ROOTNAME_ALREADY_DEFINED
A root object with the given name already exists in
the database
9809
EVJ_ROOTNAME_DOES_NOT_EXIST
A root object with the given name does not exist
in the database
9810
EVJ_NOT_A_VALID_KEY_TYPE
The type of given key for VQL query is not
supported.
9811
EVJ_NOT_A_PERSISTENT_INSTANCE
The instance object has not been made persistent
yet
9812
EVJ_OBJECT_WAS_CLEARED_FROM_JAVA_CACHE The object was cleared from the Java cache and is
no longer valid
9813
EVJ_EXCEPTIONS_ACCESSING_ARRAY
There were exceptions when accessing an array of
persistent objects. The exceptions are stored in the
vexception arguments
9814
EVJ_NOT_IN_SESSION
The current thread is not in a session
9815
EVJ_TOO_MANY_SESSIONS
The session pool has exceeded its limit on number
of sessions
9816
EVJ_NOT_A_TRANSIENT_INSTANCE
The instance object has been made
persistent
9817
EVJ_OBJECT_IS_ACTIVE
The persistent object is still active within its
transaction
9818
EVJ_SESSION_CLASSLOADER_USED_WITH_LAUNCHER
Cannot call setsessionclassloader method
while using the Launcher
9819
EVJ_OBJECT_DOES_NOT_HAVE_OID
Cannot call setpersistentstate on a transient
object that does not have an oid associated
with it
9820
EVJ_OBJECT_HAS_OID
Cannot call makepersistent on a transient
object that has an oid associated with it
9821
EVJ_OBJECT_ALWAYS_PERSISTENT
Attempted to make an always persistent
object transient.
82
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
9822
EVJ_INVALID_OID_SPECIFIED
The oid specified for the transient object
already exists. Cannot call setpersistentstate
with the option NEW_STATE for this
transient object
9823
EVJ_INVALID_USERNAME
The user name is limited to 35 characters
9824
EVJ_INVALID_PASSWORD
The user password is limited to 256
characters
9825
EVJ_INTERNAL_ERROR
Number format Exception.
9826
EVJ_INVALID_CACHED_OBJECTS_STATE
The state specified for cached objects is
invalid
9827
EVJ_INVALID_SESSION
The session of the current thread and the
session in which the query was executed are
different
9828
EVJ_CANNOT_GET_CLASS_OBJECT_FOR_EMPTY_HANDLE Cannot get a class object for an empty
handle which does not correspond to any
database object
11001 VUTIL_BACKEND_PROFILE_CLASSNAME
Server Process Parameters — The name of
the backendprofile class
11002 VUTIL_BACKEND_PROFILE_READ_FAILED
Error reading Server Process parameter file
— Error when read fails
11003 VUTIL_BACKEND_PROFILE_WRITEFAILED
Error writing Server Process parameter file
— Error when write fails
11051 VUTIL_PROFILE_CLASSNAME
Parameters — The name of the Profile class
11052 VUTIL_PROFILE_UNSPECIFIED
Default — The word to use for unspecified
parameters
11053 VUTIL_PROFILE_WAIT_FOREVER
Wait Forever — The word to use for
wait-forever parameters
11054 VUTIL_PROFILE_UNSPECIFY_OP
Set to `Default' — The name of the
Profile_unspecify opoeration
11055 VUTIL_PROFILE_WAIT_FOREVER_OP
Set to `Wait Forever' — The name of the
Profile_waitforever operation
11076 VUTIL_COMMANDS_INVALID_MODE
Invalid Mode — Bad value for mode argument
11077 VUTIL_COMMANDS_POPEN_FAILED
Could not open pipe — Popen failed
11078 VUTIL_COMMANDS_OS_ERROR
Operating System Error %s
Versant Error Codes Reference
83
System Utility Errors, Series – 7000, 9000, 11000,
12300
11101 VUTIL_DATABASE_CLASSNAME
Database — The name of the Database class
11102 VUTIL_DATABASE_START
Start — The name of the Database_startdb operation
11103 VUTIL_DATABASE_STOP
Stop — The name of the Database_stopdb operation
11104 VUTIL_DATABASE_STOP_OPTIONS
Force to stop : Arg 1 — options for stopdb: force or don't
force
11105 VUTIL_DATABASE_STOP_FORCE
Force : Arg 1, option 1 — force
11106 VUTIL_DATABASE_STOP_DONT_FORCE
Don't Force : Arg 1, option 2 — dont't force
11107 VUTIL_DATABASE_STOP_MESSAGE
Force killing of all active transactions? — The message
displayed in the operation dialog box
11108 VUTIL_DATABASE_DESTROY
Remove — The name of the Database_destroydatabases
operation
11109 VUTIL_DATABASE_DESTROY_OPTIONS
Force to remove : Arg 1 — options for removedb: force
or don't force
11110 VUTIL_DATABASE_DESTROY_FORCE
Force : Arg 1 option 1 — force
11111 VUTIL_DATABASE_DESTROY_DON’T_FORCE Don't Force : Arg 1 option 2 — don't force
11112 VUTIL_DATABASE_DESTROY_MESSAGE
Are you sure you want to destroy all objects in %s? —
The message displayed in the operation dialog box
11113 VUTIL_DATABASE_ADDVOL
Add Volume — The name of the Database_addvolume
operation
11114 VUTIL_DATABASE_ADDVOL_PATH
Path of device/file : Arg 1 — the path of the device/file
11115 VUTIL_DATABASE_ADDVOL_SIZE
Volume size : Arg 2 — the size of the new volume
11116 VUTIL_DATABASE_ADDVOL_EXTENT_SIZE Pages per extent : Arg 3 — the extent size of the new
volume
11117 VUTIL_DATABASE_ADDUSER
Add The name of the Database_adduser operation
11118 VUTIL_DATABASE_REMOVEUSER
Remove Selection The name of the
Database_removeuser operation
11119 VUTIL_DATABASE_SCH2DB
Load Schema File The name of the
Database_sch2db operation
11120 VUTIL_DATABASE_SCH2DB_FILE
Schema file(s) : Arg 1 — the schema file or files
11121 VUTIL_DATABASE_SCH2DB_ON_CONFLICT
On Conflict : Arg 2 — how to handle a conflict
11122 VUTIL_DATABASE_SCH2DB_ABORT
Abort : Arg 2,option 1 — abort the operation
11123 VUTIL_DATABASE_SCH2DB_DROP
Drop : Arg 2, option 1 — drop the classes
84
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11124 VUTIL_DATABASE_SCH2DB_EVOLVE
Evolve : Arg 2, option 1 — evolve the classes
11125 VUTIL_DATABASE_SCH2DB_MESSAGE
Are sure you want to make these changes? —The
message displayed in the dialog box
11126 VUTIL_DATABASE_SCH2DB_UNNECESSARY
No changes are necessary — The message
displayed when no changes are necessary
11127 VUTIL_DATABASE_DROPCLASS
Remove Selection — The name of the
Database_removeclasses operation
11128 VUTIL_DATABASE_DROPCLASS_MESSAGE
Drop the following classes? — The message to
show in the dialog box
11129 VUTIL_DATABASE_DROPINST
Drop Instances of Selection — The name of the
Database_removeinstances operation
11130 VUTIL_DATABASE_DROPINST_MESSAGE
Remove instance of the following classes? — The
message to show in the dialog box
11131 VUTIL_DATABASE_SYNC_CLASS
Copy Class — The name of the
Database_syncclass operation
11132 VUTIL_DATABASE_SYNC_CLASS_CLASS
Source Class : Arg 1 — The class to sync to
11133 VUTIL_DATABASE_SYNC_CLASS_QUERY
Copy Class — The name of the
Database_syncclassquery operation
11134 VUTIL_DATABASE_SYNC_CLASSQUERY_CLASS
Source Class : Arg 1 — The class to sync to
11135 VUTIL_DATABASE_SYNC_CLASS_QUERY_CONFLICT On conflict : Arg 2 — how to deal with a conflict
11136 VUTIL_DATABASE_SYNC_CLASS_QUERY_DROP
Drop arg 2 — option 1 — drop instances
11137 VUTIL_DATABASE_SYNC_CLASS_QUERY_PRESERVE
Evolve arg 2 — option 2 — evolve instances
11138 VUTIL_DATABASE_SYNC_CLASS_QUERY_MESSAGE
A conflict exists — The message in the
dialog box
11139 VUTIL_DATABASE_SHOW_ALL_CLASSES
Show All Classes — The name of the
Database_showallclasses operation
11140 VUTIL_DATABASE_SHOW_SUBCLASSES
Show Immediate Subclasses Of : — The
name of the Database_showsubclassesof
operation
11141 VUTIL_DATABASE_SHOW_SUBCLASSES_CLASS
Subclasses Of : arg 1 — the class
11142 VUTIL_DATABASE_SHOW_ALL_SUBCLASSES
Show All Subclasses Of — The name of the
Database_showallsubclassesof operation
11143 VUTIL_DATABASE_SHOW_ALL_SUBCLASSES_CLASS
Subclasses Of : Arg 1 — the class
Versant Error Codes Reference
85
System Utility Errors, Series – 7000, 9000, 11000,
12300
11144 VUTIL_DATABASE_BAD_INTERPERSONAL_SYNC
Copying classes between personal
databases is not supported. Can't synclass
between personals since you can't have two
personals in the same session.
11145 VUTIL_DATABASE_COULD_NOT_REFRESH_CLASSES
Error refreshing database's classes list.
Error given when Database refreshclasses
fails
11146 VUTIL_DATABASE_USER_NOT_IN_GROUP
User %s is not in group %s — Error for
attempt to add a user to a group database
that is not in the appropriate group.
11147 VUTIL_DATABASE_BEGIN_SESSION_ERROR
Error while beginning session with personal
database %s — error for failed begin
session.
11148 VUTIL_DATABASE_CONNECTDB_ERROR
Error while connecting to database %s.error
for failed connectdb.
11149 VUTIL_DATABASE_END_SESSION_ERROR
Error while ending session with personal
database %s. Error for failed end session.
11150 VUTIL_DATABASE_DISCONNECT_ERROR
Error while beginning session with database
%s. Error for failed disconnectdb.
11151 VUTIL_DATABASE_BACKUPINFO_FORMAT_SANS_COMMENT Level %d made on %s. The format for
listing a backup info entry w/o comment
11152 VUTIL_DATABASE_BACKUPINFO_FORMAT_WITH_COMMENT Level %d made on %s. %s The format for
listing a backup info entry + comment
11153 VUTIL_DATABASE_COULD_NOT_REFRESH_BACKUP_INFO Error refreshing database's backup
information. Error for when
refreshBackupInfo fails
11154 VUTIL_DATABASE_BACKUP
Online Incremental Backup — name of
database_backup operation.
11155 VUTIL_DATABASE_ADD_GROUP
Add Group — name of database_addgroup
operation
11156 VUTIL_DATABASE_ADD_GROUP_GROUP
Group to add — group arg for
database_addgroup operation
11157 VUTIL_DATABASE_REMOVE_GROUP
86
Remove Group — name of database_removegroup
operation
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11158 VUTIL_DATABASE_REMOVE_GROUP_GROUP
Group to remove — group arg for
database_removegroup operation
11159 VUTIL_DATABASE_ADD_USER_USER
User to add — user arg for database_adduser
operation
11160 VUTIL_DATABASE_COULD_NOT_ADD
Could not add user %s — error when adduser() fails.
11161 VUTIL_DATABASE_COULD_NOT_REMOVE
Could not remove user %s — error when
removeuser() fails.
11162 VUTIL_DATABASE_MODE_UNSTARtable
Unstartable — name of the unstartable mode.
11163 VUTIL_DATABASE_MODE_SINGLE_CONNECT
DBA Only; Single Connection — name of the single
process mode.
11164 VUTIL_DATABASE_MODE_DBA_ONLY
DBA Only; Multiple Connections — name of the
dba only mode.
11165 VUTIL_DATABASE_MODE_MULTI_USER
Multi-User — name of the started mode.
11166 VUTIL_DATABASE_FORCE_MESSAGE
Database %s is in use. Is it ok\nto kill the processes
using it? — Question asked before "forcing" a
change in mode.
11167 VUTIL_DATABASE_COULD_NOT_REFRESH_SIZE Error refreshing database's size — When
Database::refreshsize fails
11168 VUTIL_DATABASE_COULD_NOT_REFRESH_MODE Error refreshing database's mode — When
Database::refreshmode fails
11169 VUTIL_DATABASE_COULD_NOT_REFRESH_USERS Error refreshing database's user list — When
Database::refreshusers fails
11170 VUTIL_DATABASE_UNSTARtable_SKIP
Database in Unstartable mode — skipping refresh
of users classes, and size. Message for when
refreshes are skipped due to unstartable mode
11171 VUTIL_DATABASE_SCH2DB_DESCRIPTION
Enter the .sch file name(s) and pick one of the
three\nstrategies for resolving conflicts with
existing\nclasses : Abort the operation, Drop the
existing\nclasses, or Evolve the existing classes. —
The message displayed in the dialog box
11172 VUTIL_DATABASE_ROLL_FORWARD_ON
Turn On Log Archiving — name of
database_rollforwardon operation
11173 VUTIL_DATABASE_ROLL_FORWARD_OFF
Turn Off Log Archiving — name of
database_rollforwardon operation
Versant Error Codes Reference
87
System Utility Errors, Series – 7000, 9000, 11000,
12300
11174 VUTIL_DATABASE_ROLL_FORWARD_LOG
Archive Logs — name of database_rollforwardon
operation
11176 VUTIL_DATABASE_VIEW_CLASSNAME
Database View — The name of the Database View
class
11177 VUTIL_DATABASE_VIEW_VERSION_NAME
Version — The name of the Version field
11178 VUTIL_DATABASE_VIEW_CREATIONDATE_NAME Creation Date — The name of the Creation Date
field
11179 VUTIL_DATABASE_VIEW_ISPUBLIC_NAME
Disregard User List — The name of the Public
Access field
11180 VUTIL_DATABASE_VIEW_USERS_NAME
Users — The name of the Users field
11181 VUTIL_DATABASE_VIEW_CLASSES_NAME
Classes — The name of the Classes field
11182 VUTIL_DATABASE_VIEW_VERSION_LABEL
Version — The label of the Version field
11183 VUTIL_DATABASE_VIEW_CREATIONDATE_LABEL Created — The label of the Creation Date field
11184 VUTIL_DATABASE_VIEW_ISPUBLIC_LABEL
Disregard User List — The label of the Public Access
field
11185 VUTIL_DATABASE_VIEW_USERS_LABEL
Users — The label of the Users field
11186 VUTIL_DATABASE_VIEW_CLASSES_LABEL
Classes — The label of the Classes field
11187 VUTIL_DATABASE_VIEW_WINDOW_TITLE
Versant Utilities; Database %s — The title of the
Database Window
11188 VUTIL_DATABASE_VIEW_BACKUPINO_NAME
Backups — The name of the backupinfo field
11189 VUTIL_DATABASE_VIEW_BACKUPINFO_LABEL
Current Incremental Backups — The label for the
backupinfo field
11190 VUTIL_DATABASE_VIEW_MODE_NAME
Mode — The name of the mode field
11191 VUTIL_DATABASE_VIEW_MODE_LABEL
Mode — The label for the mode field
11192 VUTIL_DATABASE_VIEW_SIZE_NAME
Size — The name of the size field
11193 VUTIL_DATABASE_VIEW_SIZE_LABEL
Size — The label for the size field
11194 VUTIL_DATABASE_VIEW_FREE_NAME
Free — The name of the free field
11195 VUTIL_DATABASE_VIEW_FREE_LABEL
Free — The label for the free field
11201 VUTIL_DATABASE_DIRECTORY_CLASSNAME
Database Directory — The name of the Database
Directory class
88
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11202 VUTIL_DATABASE_DIRECTORY_PERSONAL
Personal — The database type name of
personal databases
11203 VUTIL_DATABASE_DIRECTORY_GROUP
Group — The database type name of group
databases
11204 VUTIL_DATABASE_DIRECTORY_UNIVERSAL
Universal — The database type name of
universal databases
11205 VUTIL_DATABASE_DIRECTORY_NEW_DB_NOT_FOUND
Could not find newly created database
directory - error for when create succeeds but
refresh fails
11206 VUTIL_DATABASE_DIRECTORY_DESTROY
Remove — name of the
databasedirectory_destroy operation
11207 VUTIL_DATABASE_DIRECTORY_CREATEDB
Create Database — name of the
databasedirectory_createdatabase operation
11208 VUTIL_DATABASE_DIRECTORY_CREATEDB_OPTIONS
Initialize the database : Arg 1 — options for
createdb init or don't init
11209 VUTIL_DATABASE_DIRECTORY_CREATEDB_INIT
Reserve : Arg 1; option 1 — init
11210 VUTIL_DATABASE_DIRECTORY_CREATEDB_DONT_INIT Grow : Arg 1; option 2 — dont't init
11211 VUTIL_DATABASE_DIRECTORY_CREATEDB_MESSAGE
Should disk space be reserved for the full size
of the system volume , or should it
be\ncreated at a minimal size and allowed to
dynamically grow up to its maximum size? —
The message displayed in the operation dialog
box
11212 VUTIL_DATABASE_DIRECTORY_REFRESH
Refresh — The name of the
databasedirectory_refresh operation
11213 VUTIL_DATABASE_DIRECTORY_PARAMETERS
View Parameters — The name of the
databasedirectory_parameters operation
11214 VUTIL_DATABASE_DIRECTORY_NOT_ROOT
Only the superuser can change the owner —
Error for when the owner is changed by other
than root
11215 VUTIL_DATABASE_DIRECTORY_VIEW
View — The name of the
databasedirectory_view operation
11216 VUTIL_DATABASE_DIRECTORY_NO_LONGER_EXISTS
%s no longer exists. — The message given
when a database or database directory is
destroyed.
Versant Error Codes Reference
89
System Utility Errors, Series – 7000, 9000, 11000,
12300
11217 VUTIL_DATABASE_DIRECTORY_NAME_IN_USE
The name %s is already in use — Given when
makedb is called with an already used name.
11218 VUTIL_DATABASE_DIRECTORY_RESTORE
Restore from Backup — name of
database_restore operation.
11251 VUTIL_DATABASE_DIRECTORY_VIEW_CLASSNAME
Database Directory View — The name of the
Database Directory View class
11252 VUTIL_DATABASE_DIRECTORY_VIEW_NAME_NAME
Name — The name of the Name field
11253 VUTIL_DATABASE_DIRECTORY_VIEW_OWNER_NAME
DBA — The name of the Owner field
11254 VUTIL_DATABASE_DIRECTORY_VIEW_GROUP_NAME
Group — The name of the Group field
11255 VUTIL_DATABASE_DIRECTORY_VIEW_DBTYPE_NAME
Database Type — The name of the
Database Type field
11256 VUTIL_DATABASE_DIRECTORY_VIEW_LOGGING_NAME
Logging — The name of the Logging field
11258 VUTIL_DATABASE_DIRECTORY_VIEW_LOCKING_NAME
Locking — The name of the Locking field
11260 VUTIL_DATABASE_DIRECTORY_VIEW_NAME_LABEL
Name — The label of the Name field
11261 VUTIL_DATABASE_DIRECTORY_VIEW_OWNER_LABEL
DBA — The label of the Owner field
11262 VUTIL_DATABASE_DIRECTORY_VIEW_GROUP_LABEL
Group — The label of the Group field
11263 VUTIL_DATABASE_DIRECTORY_VIEW_DBTYPE_LABEL
Type — The label of the Database Type
field
11264 VUTIL_DATABASE_DIRECTORY_VIEW_LOGGING_LABEL
Logging — The label of the Logging field
11266 VUTIL_DATABASE_DIRECTORY_VIEW_LOCKING_LABEL
Locking — The label of the Locking field
11268 VUTIL_DATABASE_DIRECTORY_VIEW_WINDOW_TITLE
Versant Utilities; Database Directory %s
— The title of the Database Directory
Window
11301 VUTIL_FRONTEND_PROFILE_CLASSNAME
Application Process Parameters — The
name of the frontendprofile class
11302 VUTIL_ALIAS_CLASSNAME
Alias — The name of the Alias class
11303 VUTIL_FRONTEND_PROFILE_ADD_CONNECTION
Add — The name of the
frontendprofile_addconnection operation
11304 VUTIL_FRONTEND_PROFILE_ADD_CONNECTION_DATABASE Database — The first arg — the name of
the database to connect to
11305 VUTIL_FRONTEND_PROFILE_REMOVE_CONNECTION
90
Remove Selection — The name of the
frontendprofile_removeconnection
operation
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11306 VUTIL_FRONTEND_PROFILE_ADD_ALIAS
Add — The name of the
frontendprofile_addalias operation
11307 VUTIL_FRONTEND_PROFILE_ADD_ALIAS_ALIAS
Alias — The first arg — the alias
11308 VUTIL_FRONTEND_PROFILE_ADD_ALIAS_DATABASE
Database — The second arg — the
expansion
11309 VUTIL_FRONTEND_PROFILE_REMOVE_ALIAS
Remove Selection — The name of the
frontendprofile_removealias operation
11310 VUTIL_FRONTEND_PROFILE_BAD_DATABASE_NAME Bad database name %s — A database name in the
connects or aliases list was bad
11311 VUTIL_FRONTEND_PROFILE_BAD_CONNECT
Bad entries removed from connect list — There
were bad database names in the connects list
11312 VUTIL_FRONTEND_PROFILE_BAD_ALIAS
Bad entries removed from alias list — There were
bad database names in the aliases list
11313 VUTIL_FRONTEND_PROFILE_PERSONAL_CONNECT You cannot have an automatic connection to a
personal database — user trys to add a personal
database to the connects list
11314 VUTIL_FRONTEND_PROFILE_UNCREATED_CONNECT Be careful it is impossible to connect to an
uncreated database directory — The user added
a connection to an uncreated database
11315 VUTIL_FRONTEND_PROFILE_READ_FAILED
Error reading Client Process parameter file —
error when read fails
11316 VUTIL_FRONTEND_PROFILE_WRITE_FAILED
Error writing Client Process parameter file —
error when write fails
11351 VUTIL_GROUP_CLASSNAME
Group — The name of the Group class
11401 VUTIL_MACHINE_CLASSNAME
Host — The name of the Machine class
11402 VUTIL_MACHINE_REFRESH
Refresh — The name of the Machine_refresh
operation
11403 VUTIL_MACHINE_OPEN_MACHINE
New Host Window — The name of the
Machine_newmachine operation
11404 VUTIL_MACHINE_OPEN_MACHINE_MACHINE_NAME Name of Host : Arg 1 — The name of the machine
to open
11405 VUTIL_MACHINE_VIEW
View Selection — The name of the Machine_view
operation
Versant Error Codes Reference
91
System Utility Errors, Series – 7000, 9000, 11000,
12300
11406 VUTIL_MACHINE_NEW_DIRECTORY
New Database Directory — The name of the
Machine_createdirectory operation
11407 VUTIL_MACHINE_NEW_DIRECTORY_DIR_NAME
Name of the new directory : Arg 1 — the name
of the new directory
11408 VUTIL_MACHINE_NEW_DIRECTORY_INVALID_NAME Invalid host name — Error generated when the
machine name is invalid.
11409 VUTIL_MACHINE_CREATE_DATABASES
Create Database(s) from Selection — The name
of the Machine_createdatabases operation
11410 VUTIL_MACHINE_CREATE_DATABASES_OPTIONS
Initialize the database : Arg 1 — options for
createdb: init or don't init
11411 VUTIL_MACHINE_CREATE_DATABASES_INIT
Reserve : Arg 1, option 1 — init
11412 VUTIL_MACHINE_CREATE_DATABASES_DONT_INIT Grow : Arg 1, option 2 — don't init
11413 VUTIL_MACHINE_CREATE_DATABASES_MESSAGE
Should disk space be reserved for the full size
of the system volume , or should it be\ncreated
at a minimal size and allowed to dynamically
grow up to its maximum size?
11414 VUTIL_MACHINE_DESTROY_DIRECTORIES
Remove Selection — The name of the
Machine_destroydirectories operation
11415 VUTIL_MACHINE_DESTORY_DIRECTORIES_MESSAGE Remove the following database directories? —
The message displayed in the operation dialog
box
11416 VUTIL_MACHINE_START
Start Selection — The nameo of the
Machine_startdbs operation
11417 VUTIL_MACHINE_STOP
Stop Selection — The name of the
Machine_stopdbs operation
11418 VUTIL_MACHINE_STOP_OPTIONS
Force to stop : Arg 1 — options for stopdb:
force or don't force
11419 VUTIL_MACHINE_STOP_FORCE
Force : Arg 1: option 1 — force
11420 VUTIL_MACHINE_STOP_DONT_FORCE
Don't Force : Arg 1: option 2 — dont't force
11421 VUTIL_MACHINE_STOP_MESSAGE
Force killing of all active transactions? — The
message displayed in the operation dialog box
11422 VUTIL_MACHINE_DESTROY_DATABASES
Remove Selection — The name of the
Machine_destroydatabases operation
92
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11423 VUTIL_MACHINE_DESTROY_DATABASES_OPTIONS
Force to remove : Arg 1 : options for removedb;
force or don't force
11424 VUTIL_MACHINE_DESTROY_DATABASES_FORCE
Force : Arg 1 : option 1 — force
11425 VUTIL_MACHINE_DESTROY_DATABASES_DONT_FORCE Don't Force : Arg 1 : option 2 — dont't force
11426 VUTIL_MACHINE_DESTROY_DATABASES_MESSAGE
Destroy all objects in the following databases?
— The message displayed in the operation
dialog box
11427 VUTIL_MACHINE_WRONG_PERSONAL
This personal database is only accessible by
its owner: %s — The message displayed when
a user tries to access someone else's personal
database.
11428 VUTIL_MACHINE_NOT_IN_GROUP
To access this group database you must be in
the %s group — The message displayed when
a user tries to access a group database for
another group.
11429 VUTIL_MACHINE_NOT_IN_USER_LIST
To access this database you must be in its user
list — The message displayed when a user is
not in a database's user list.
11430 VUTIL_MACHINE_BACKUPDBS
Online Incremental Backup of Selection — The
name of the machine_backupdbs operation.
11431 VUTIL_MACHINE_RESTOREDBS
Restore Selection from Backup — The name of
the machine_restoredbs operation.
11432 VUTIL_MACHINE_CREATE_DEVICE
New Backup Device Window — name of
database_createdevice operation.
11433 VUTIL_MACHINE_VIEW_PARAMETERS
View Parameters of Selection — name of
machine_viewparameters operation
11434 VUTIL_MACHINE_ROLL_FORWARD_ON
Turn On Log Archiving for Selection — name of
machine_rollforwardon operation
11435 VUTIL_MACHINE_ROLL_FORWAR_OFFD
Turn Off Log Archiving for Selection — name
of machine_rollforwardon operation
11436 VUTIL_MACHINE_ROLL_FORWARD_LOG
Archive Logs for Selection — name of
machine_rollforwardon operation
11451 VUTIL_MACHINE_VIEW_CLASSNAME
Host View — The name of the Machine View
class
Versant Error Codes Reference
93
System Utility Errors, Series – 7000, 9000, 11000,
12300
11452 VUTIL_MACHINE_VIEW_WINDOW_TITLE
Versant Utilities: Host %s — the title of the
Machine Window
11453 VUTIL_MACHINE_VIEW_DATABASE_LIST_NAME
Databases — the name of the database list
11454 VUTIL_MACHINE_VIEW_DIRECTORIES_LIST_NAME Database Directories — the name of the
database directories list
11455 VUTIL_MACHINE_VIEW_ROOT_PATH_NAME
Root Path — the name of the root path field
11456 VUTIL_MACHINE_VIEW_DB_PATH_NAME
Database Path — the name of the db path field
11457 VUTIL_MACHINE_VIEW_VERSION_NAME
Product Version — the name of the product
version field
11458 VUTIL_MACHINE_VIEW_DATABASE_LIST_LABEL
Fully Created Databases — the label of the
database list
11459 VUTIL_MACHINE_VIEW_DIRECTORIES_LIST_LABEL Empty Database Directories — the label of the
database directories list
11460 VUTIL_MACHINE_VIEW_ROOT_PATH_LABEL
Root Path — the label of the root path field
11461 VUTIL_MACHINE_VIEW_DB_PATH_LABEL
Database Path — the label of the db path field
11462 VUTIL_MACHINE_VIEW_VERSION_LABEL
Product Version — the label of the product
version field
11463 VUTIL_MACHINE_VIEW_CLOSE
Close — The name of the machineview_close
window
11464 VUTIL_MACHINE_VIEW_ARE_YOU_SURE
Are you sure you want to exit Versant Utilities?
— The question to ask the user before exiting
11465 VUTIL_MACHINE_VIEW_DBID_NODE_NAME
DBID Node — the name of the dbid node field
11466 VUTIL_MACHINE_VIEW_DBID_PATH_NAME
DBID Path — the name of the dbid path field
11467 VUTIL_MACHINE_VIEW_DBID_NODE_LABEL
DBID Node — the label of the dbid node field
11468 VUTIL_MACHINE_VIEW_DBID_PATH_LABEL
DBID Path — the name of the dbid path field
11501 VUTIL_MAIN_PERSONAL_DB_FLAG_ALIAS
-D — A localized alias for -D
11502 VUTIL_MAIN_NO_ARG_ERROR
-D requires an argument — printed when no
arg is supplied to -D
11503 VUTIL_MAIN_IGNORING_FLAG
Ignoring unknown %s flag — printed when
an unknown flag is found
11504 VUTIL_MAIN_NOT_FOUND
Ignoring non-existant %s — printed when a
non-existent database or database directory
is passed.
94
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11505 VUTIL_MAIN_APP_NAME
Versant Utilities — The name of the
application: Versant Utilities
11506 VUTIL_MAIN_VIEWS_UNAVAILABLE
The DISPLAY environment variable must be
set — The error message to give when no X
display is specified
11507 VUTIL_MAIN_COULD_NOT_REFRESH_LOCAL_HOST
Error refreshing information on the local host
— Error given if refresh fails for the local host
11508 VUTIL_MACHINE_COULD_NOT_REFRESH_OSCP_INFO
Error refreshing host's configuration
information — error given of
Machine::refreshinfo fails
11509 VUTIL_MACHINE_COULD_NOT_REFRESH_DBLIST_INFO Error refreshing host's database list and
related information — error given of
Machine:: refreshdatabases fails
11601 VUTIL_PROFILE_VIEW_CLASSNAME
Parameters View — The name of the
profileview class
11602 VUTIL_PROFILE_VIEW_SYSVOL_LABEL
System Volume — The label of the system
volume profile parameter
11603 VUTIL_PROFILE_VIEW_PLOGVOL_LABEL
Physical Log Volume — the label of the
Physical Log Volume profile parameter
11604 VUTIL_PROFILE_VIEW_LLOGVOL_LABEL
Logical Log Volume — the label of the Logical
Log Volume profile parameter
11605 VUTIL_PROFILE_VIEW_VOL_PATH_LABEL
Path — the label of the Path profile parameter
11606 VUTIL_PROFILE_VIEW_VOL_SIZE_LABEL
Size — the label of the Size profile parameter
11607 VUTIL_PROFILE_VIEW_EXTENT_SIZE_LABEL
Pages per Extent — the label of the Pages per
Extent profile parameter
11608 VUTIL_PROFILE_VIEW_LLOG_BUF_SIZE_LABEL
Logical Log Buffer Size — the label of the
Logical Log Buffer Size profile parameter
11609 VUTIL_PROFILE_VIEW_PLOG_BUF_SIZE_LABEL
Physical Log Buffer Size — the label of the
Physical Log Buffer Size profile parameter
11610 VUTIL_PROFILE_VIEW_HEAP_SIZE_LABEL
Initial Heap Size — the label of the Initial
Heap Size profile parameter
11611 VUTIL_PROFILE_VIEW_MAX_PAGE_BUFFS_LABEL
Maximum Page Buffers — the label of the
Maximum Page Buffers profile parameter
Versant Error Codes Reference
95
System Utility Errors, Series – 7000, 9000, 11000,
12300
11612 VUTIL_PROFILE_VIEW_LOCK_WAIT_TIMEOUT_LABEL Lock Wait Timeout — the label of the Lock
Wait Timeout profile parameter
11613 VUTIL_PROFILE_VIEW_DATABASE_TIMEOUT_LABEL Database Timeout — the label of the Database
Timeout profile parameter
11614 VUTIL_PROFILE_VIEW_CREATION_LABEL
Creation Parameters — the label of the
Creation Parameters group label
11615 VUTIL_PROFILE_VIEW_BACKEND_LABEL
Server Process Tuning Parameters — the label
of the Server Process Parameters group label
11616 VUTIL_PROFILE_VIEW_FRONTEND_LABEL
Application Process Parameters for %s — the
label of the Application Process Parameters
group label
11617 VUTIL_PROFILE_VIEW_CACHE_SIZE_LABEL
Swap Threshold — the label of the Swap
Threshold profile parameter
11618 VUTIL_PROFILE_VIEW_FE_HEAP_SIZE_LABEL
Initial Heap Size — the label of the Initial Heap
Size profile parameter
11619 VUTIL_PROFILE_VIEW_ALIASES_LABEL
Aliases — the label of the Aliases profile
parameter
11620 VUTIL_PROFILE_VIEW_CONNECTS_LABEL
Automatic Connections — the label of the
Automatic Connections profile parameter
11621 VUTIL_PROFILE_VIEW_WINDOW_TITLE
Versant Utilities: Parameters for %s — the title
of the Parameters Window
11623 VUTIL_PROFILE_VIEW_SYSVOL_PATH_NAME
System Volume Path — the name of the System
Volume Path profile parameter
11624 VUTIL_PROFILE_VIEW_PLOGVOL_PATH_NAME
Physical Log Volume Path — the name of the
Physical Log Volume Path profile parameter
11625 VUTIL_PROFILE_VIEW_LLOGVOL_PATH_NAME
Logical Log Volume Path — the name of the
Logical Log Volume Path profile parameter
11626 VUTIL_PROFILE_VIEW_EXTENT_SIZE_NAME
Pages per Extent — the name of the Pages per
Extent profile parameter
11627 VUTIL_PROFILE_VIEW_SYSVOL_SIZE_NAME
System Size — the name of the System Size
profile parameter
11628 VUTIL_PROFILE_VIEW_LLOGVOL_SIZE_NAME
Logical Log Size — the name of the Logical Log
Size profile parameter
11629 VUTIL_PROFILE_VIEW_PLOGVOL_SIZE_NAME
Physical Log Size — the name of the Physical
Log Size profile parameter
96
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11630 VUTIL_PROFILE_VIEW_LLOG_BUF_SIZE_NAME
Logical Log Buffer Size — the name of the
Logical Log Buffer Size profile parameter
11631 VUTIL_PROFILE_VIEW_PLOG_BUF_SIZE_NAME
Physical Log Buffer Size — the name of the
Physical Log Buffer Size profile parameter
11632 VUTIL_PROFILE_VIEW_HEAP_SIZE_NAME
Server Process Initial Heap Size — the name
of the Server Process Initial Heap Size profile
parameter
11633 VUTIL_PROFILE_VIEW_MAX_PAGE_BUFFS_NAME
Maximum Page Buffers — the name of the
Maximum Page Buffers profile parameter
11634 VUTIL_PROFILE_VIEW_LOCK_WAIT_TIMEOUT_NAME Lock Wait Timeout — the name of the Lock
Wait Timeout profile parameter
11635 VUTIL_PROFILE_VIEW_DATABASE_TIMEOUT_NAME Database Timeout — the name of the Database
Timeout profile parameter
11636 VUTIL_PROFILE_VIEW_CACHE_SIZE_NAME
Swap Threshold — the name of the Swap
Threshold profile parameter
11637 VUTIL_PROFILE_VIEW_FE_HEAP_SIZE_NAME
Application Process Initial Heap Size — the name
of the Application Process Initial Heap Size
profile parameter
11638 VUTIL_PROFILE_VIEW_ALIASES_NAME
Aliases — the name of the Aliases profile
parameter
11639 VUTIL_PROFILE_VIEW_CONNECTS_NAME
Automatic Connections — the name of the
Automatic Connections profile parameter
11640 VUTIL_PROFILE_VIEW_TRANSACTIONS_LABEL
Transaction Count — the label of the transactions
profile parameter
11641 VUTIL_PROFILE_VIEW_TRANSACTIONS_NAME
Transaction Count — the name of the
transactions profile parameter
11642 VUTIL_PROFILE_VIEW_MAX_PROCESSES_LABEL
Maximum Processes — the label of the
max_processes profile parameter
11643 VUTIL_PROFILE_VIEW_MAX_PROCESSES_NAME
Maximum Processes — the name of the
max_processes profile parameter
11644 VUTIL_PROFILE_VIEW_COMMIT_FLUSH_LABEL
Commit Flush — the label of the commit_flush
profile parameter
11645 VUTIL_PROFILE_VIEW_COMMIT_FLUSH_NAME
Commit Flush — the name of the commit_flush
profile parameter
Versant Error Codes Reference
97
System Utility Errors, Series – 7000, 9000, 11000,
12300
11646 VUTIL_PROFILE_VIEW_SIGNAL_BLOCK_LABEL
Signal Block — the label of the signal_block
profile parameter
11647 VUTIL_PROFILE_VIEW_SIGNAL_BLOCK_NAME
Signal Block — the name of the signal_block
profile parameter
11651 VUTIL_USER_CLASSNAME
User — The name of the User class
11701 VUTIL_CLASS_CLASSNAME
Class — The name of the Class class
11751 VUTIL_DEVICE_CLASSNAME
Backup Device — The name of the Device class
11752 VUTIL_DEVICE_LEVEL_ARG
Level — The label for the level argument
11753 VUTIL_DEVICE_POSITION_ARG
Tape Position — The label for the level argument
11754 VUTIL_DEVICE_COMMENT_ARG
Comment — The label for the level argument
11755 VUTIL_DEVICE_DEVICE_ARG
Device — The label for the device argument
11756 VUTIL_DEVICE_BLOCKING_ARG
Blocking — The label for the blocking argument
11757 VUTIL_DEVICE_CAPACITY_ARG
Capacity — The label for the capacity argument
11758 VUTIL_DEVICE_DATABASE_ARG
Database — The label for the database argument
11759 VUTIL_DEVICE_BACKUP
Online Incremental Backup — The name of device_backup
11760 VUTIL_DEVICE_REFRESH
Refresh — The name of device_refresh
11761 VUTIL_DEVICE_MOUNT_THE_NEXT_TAPE Mount the appropriate tape... — printed between restores
11762 VUTIL_DEVICE_ANOTHER_LEVEL_QUERY Would you like to do another level of restore\non database
%s? — asks the user if they would like to do another level
of restore
11763 VUTIL_DEVICE_MODAL_QUERY
Modal Query — The name of device_recoverableerror
11764 VUTIL_DEVICE_BACKUP_MESSAGE
Would you like to turn on log archiving\nwith this backup?
Prepare the backup device\nand press 'Yes' or 'No' to start
the backup. — The message in the backup dialog
11765 VUTIL_DEVICE_RESTORE_MESSAE
Prepare the backup device and\npress 'OK' to start the
restore. — The message in the restore dialog
11766 VUTIL_DEVICE_LOG_MESSAGE
Prepare the backup device and press\n'ok' to start
archiving log records. — The message in the backup dialog
11767 VUTIL_DEVICE_ROLL_FORWARD_LOG
Archive Logs — name of machine_rollforwardlog operation
11768 VUTIL_DEVICE_AGGRESSION_ARG
Aggression — The label for the database argument
11769 VUTIL_DEVICE_LOG_RESTORE_MESSAGE Reappling log records... — Message displayed during log
roll forward restore
98
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
11770 VUTIL_DEVICE__COPY_QUERY
During roll forward would you like to apply records\nfrom
the database's current log file in addition to any\narchived
records ? If so, then this log file must be\ncopied to a safe
location so it is not overwritten\nduring the restore.
11771 VUTIL_DEVICE_OLD_LOG_ARG
Path of log file
11772 VUTIL_DEVICE_COPY_LOG_ARG
Path for copy of log file
11773 VUTIL_DEVICE_RF_ON
Yes
11774 VUTIL_DEVICE_RF_UNCHANGED
No
11775 VUTIL_DEVICE_RF_ARG
Turn on roll forward
11786 VUTIL_DEVICE_VIEW_CLASSNAME
Backup Device View — The name of the deviceview class
11787 VUTIL_DEVICE_VIEW_WINDOW_TITLE
Versant Utilities; Backup Device %s — the title of the
Device window
11788 VUTIL_DEVICE_VIEW_FILES_LABEL
Backup files on device — The text of the backup files
label
11789 VUTIL_DEVICE_VIEW_FILES_NAME
Files — The name of the backup files list
11790 VUTIL_DEVICE_VIEW_CAPACITY_LABEL
Capacity — The text of the capacity label
11791 VUTIL_DEVICE_VIEW_CAPACITY_NAME
Capacity — The name of capacity field
11792 VUTIL_DEVICE_VIEW_BLOCKING_LABEL
Blocking — The text of the blocking label
11793 VUTIL_DEVICE_VIEW_BLOCKING_NAME
Blocking — The name of blocking field
11794 VUTIL_DEVICE_VIEW_DEVICE_LABEL
Device — The text of the device label
11795 VUTIL_DEVICE_VIEW_DEVICE_NAME
Device — The name of device field
11801 VUTIL_FILE_CLASSNAME
Backup Device View — The name of the deviceview
class
11802 VUTIL_FILE_NAME_FORMAT_WITH_COMMENT Position %d: %s volume %d. %s — The format of a file's
name
11803 VUTIL_FILE_NAME_FORMAT_SANS_COMMENT Position %d: %s volume %d — The format of a file's
name
11804 VUTIL_FILE_RESTORE
Restore Database from Selection — The name of
file_restore
11805 VUTIL_FILE_RESTORE_DATABASE_ARG
Database — The database arg for file_restore
11806 VUTIL_FILE_RESTORE_SINGLE_FILE_ONLY Multiple file restores are not yet supported.\nselect a
single file and try again. — Error given when multi-file
select is attempted.
Versant Error Codes Reference
99
System Utility Errors, Series – 7000, 9000, 11000,
12300
12301 VBACKUP_ALGO_NEXT_TAPE
End of tape encountered. Please mount a blank tape.
VBACKUP_TAPE_END_OF_VOLUME during restore
12302 VBACKUP_ALGO_COULD_NOT_OPEN
Could not open device %s at position %s.\nos error
#%d. Please check the device. — verbose version of
VBACKUP_TAPE_COULD_NOT_OPEN
12303 VBACKUP_ALGO_WRONG_FORMAT
The file on device %s at position %s is not\nof the
proper format. Please mount the proper tape. —
verbose version of VBACKUP_TAPE_WRONG_FORMAT
12304 VBACKUP_ALGO_WRONG_VOLUME
The file on device %s at position %s\nis volume %d.
Please mount volume %d. — verbose version of
VBACKUP_TAPE_WRONG_VOLUME
12305 VBACKUP_ALGO_WRONG_LABEL
The file on device %s at position %s is labeled :\n
%s\nplease retry with the proper file:\n %s — verbose
version of VBACKUP_TAPE_WRONG_LABEL
12322 VBACKUP_TAPE_END_OF_VOLUME
Please mount the next tape — End of volume reached.
12323 VBACKUP_TAPE_COULD_NOT_OPEN
Error while opening the file — An error was encountered
opening the file
12324 VBACKUP_TAPE_WRONG_FORMAT
Wrong file format — The file format was different from
the one specified in open()
12325 VBACKUP_TAPE_WRONG_LABEL
Wrong file label — The label was different from the one
specified in open()
12326 VBACKUP_TAPE_WRONG_VOLUME
Wrong volume number — The tapes were inserted in the
wrong order for a multi volume file.
12327 VBACKUP_TAPE_WRONG_BLOCK
Block check failure. File is corrupted — The internal block
field was wrong indicating file corruption.
12328 VBACKUP_TAPE_ABORTED
Aborted at user's request — the backup was aborted.
12329 VBACKUP_TAPE_ERROR
Error reading or writing the tape — error from read(),
write(), or rmt connection.
12330 VBACKUP_TAPE_GET_STATUS_FAILED
Failed ioctl call while getting status of device.
12331 VBACKUP_TAPE_EOM_FAILED
Failed ioctl call while positioning tape after last file.
12332 VBACKUP_TAPE_BSF_FAILED
Failed ioctl call while adjusting the tape position
backward.
12333 VBACKUP_TAPE_FSF_FAILED
Failed ioctl call while adjusting the tape position forward.
12334 VBACKUP_TAPE_INVALID_POSITION
Can not go to a negative tape position.
100
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
12335 VBACKUP_TAPE_EOF_FAILED
Failed ioctl call while writing end-of-file marker.
12336 VBACKUP_TAPE_CLOSE_FAILED
Could not close the device. OS error #%d.
12337 VBACKUP_TAPE_BROKEN_PIPE
The pipe connecting to the remote device was broken.
12338 VBACKUP_TAPE_NO_ACCESS_TO_HOST
Permission denied while trying to access remote host via
rsh.
12339 VBACKUP_TAPE_PIPE_CREATION_FAILED Error creating a pipe.
12340 VBACKUP_TAPE_FORK_FAILED
Could not fork the rsh process probably due to lack of
swap space.
12341 VBACKUP_TAPE_COULD_NOT_CLOSE_PIPE Error while closing pipe to remote tape device.
12342 VBACKUP_TAPE_SEND_COMMAND_FAILED
Error while sending a command to the remote device.
12343 VBACKUP_TAPE_POSITION_0_ONLY
Files only support position 0.
12344 VBACKUP_TAPE_REWIND_FAILED
Failed ioctl call while rewinding the tape.
12345 VBACKUP_TAPE_FLUSH_FAILED
Error while syncing backup device.
12346 VBACKUP_TAPE_WRONG_VERSION
The backup was made with an old incompatible version
of Versant.
12347 VBACKUP_TAPE_WRONG_BYTE_ORDERING
The backup was made on a machine with incompatible
byte ordering.
12348 VBACKUP_TAPE_REWINDING
Warning: %s is a rewinding tape device.\nonly
non-rewinding tape devices are supported.
12349 VBACKUP_TAPE_DBUFFER_FULL
Double buffer used for backup and restore is currently
full cannot copy into full buffers
12350 VBACKUP_TAPE_DBUFFER_EMPTY
Double buffer used for backup and restore is currently
empty cannot "get" from empty buffers
12351 VBACKUP_OLIB_UNKNOWN_TIMESTAMP
??? Given as timestamp when backupdbinfo fails
12352 VBACKUP_OLIB_NEXT_BACKUP_TAPE
End of tape encountered. Please mount a blank\ntape
on device %s. VBACKUP_TAPE_END_OF_VOLUME
during backup
12353 VBACKUP_OLIB_NEXT_RESTORE_TAPE
End of tape encountered. Please mount volume %d\non
device %s. VBACKUP_TAPE_END_OF_VOLUME during
restore
12354 VBACKUP_OLIB_WRONG_DBNAME
The file on device %s at position %s is a backup
of\ndatabase %s. Please try again using a backup of %s.
Versant Error Codes Reference
101
System Utility Errors, Series – 7000, 9000, 11000,
12300
— verbose version of
VBACKUP_TAPE_WRONG_DBNAME
12355 VBACKUP_OLIB_INCONSISTENT_RESTORE The database %s @ %s should be restored with
the\nnew name %s @ %s. Please try again. — verbose
version of VBACKUP_TAPE_INCONSISTENT_RESTORE
12359 VBACKUP_OLIB_NEED_PREVIOUS_LEVEL
Before you can restore this level %d backup,\nyou must
first restore the level %d backup\nmade on %s —
verbose version of UT_ER_NEED_LEVEL_XXX errors.
12360 VBACKUP_OLIB_NOT_LATEST
Warning: A more recent level %d backup of %s was
made\non %s — verbose version of UT_W_NOT_LATEST
12361 VBACKUP_OLIB_NEWER_LEVEL_2
Warning: After this restore is complete, you
will\nprobably want to restore the level 2 backup
made\non %s — verbose version of
UT_W_NEWER_LEVEL_2
12362 VBACKUP_OLIB_DB_MODIFIED
Warning: The database has been modified since you
did\nthe previous level of restore. You should
consider\nrestarting from level 0. — verbose version of
UT_W_MODIFIED_SINCE_RESTORE
12363 VBACKUP_OLIB_REMOTE_DB_UNSUPPORTED Backup and restore of remote databases is currently
unsupported — given when an attempt is made to
backup or restore a remote database
12364 VBACKUP_OLIB_BEGIN
<done with pre-restore> gets passed to callback, but
shouldn't be printed
12375 VBACKUP_ARGS_INVALID_UPDATE
Valid settings are: device, position, capacity, and blocking.
12376 VBACKUP_ARGS_USAGE
Usage: vbackup full usage\n This is never printed by
Versant.\n — The usage message displayed when arguments
aren't entered properly.
12377 VBACKUP_ARGS_MINUS_DEVICE
-device — internationalized synonym for -device
12378 VBACKUP_ARGS_MINUS_LEVEL
-level — internationalized synonym for –level
12379 VBACKUP_ARGS_MINUS_POSITION
-position — internationalized synonym for -position
12380 VBACKUP_ARGS_MINUS_CAPACITY
-capacity — internationalized synonym for -capacity
12381 VBACKUP_ARGS_MINUS_BLOCKING
-blocking — internationalized synonym for -blocking
12382 VBACKUP_ARGS_MINUS_BUFFER
-buffer — internationalized synonym for -buffer
12383 VBACKUP_ARGS_MINUS_COMMENT
-comment — internationalized synonym for -comment
102
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
12384 VBACKUP_ARGS_MINUS_LIST
-list — internationalized synonym for -list
12385 VBACKUP_ARGS_MINUS_BACKUP
-backup — internationalized synonym for -backup
12386 VBACKUP_ARGS_MINUS_RESTORE
-restore — internationalized synonym for -restore
12387 VBACKUP_ARGS_MINUS_INFO
-info — internationalized synonym for -info
12395 VBACKUP_ARGS_BAD_ARG
Unrecognized option %s. — Error message for bad args
12396 VBACKUP_ARGS_NO_COMMAND
A command is required. — Error message for no command
12397 VBACKUP_ARGS_ONE_ARG
The %s option requires an argument. — Error message for
when no argument is given and a single argument is required
12398 VBACKUP_ARGS_ONE_OR_MORE_DBS
The %s command requires a list of one more databases —
Error message for when no argument is given and one or
more arguments are required
12399 VBACKUP_ARGS_NO_ARGS
The %s command does not take any arguments — Error
message for when an argument is given when it should not
be.
12400 VBACKUP_ARGS_LEVEL_USAGE
<level> must be one of: 0, 1 or 2 — Error message for when
the level argument doesn't parse
12401 VBACKUP_ARGS_POSITION_USAGE
<position> must be one of append; current; or a non-negative
number — Error message for when the position argument
doesn't parse
12402 VBACKUP_ARGS_CAPACITY_USAGE
<capacity> must be a one of dynamic or a positive number
of bytes — Error message for when the capacity argument
doesn't parse
12403 VBACKUP_ARGS_BLOCKING_USAGE
<blocking> must be a one of optimal or a positive number
of bytes. — Error message for when the blocking argument
doesn't parse
12404 VBACKUP_ARGS_BUFFER_SIZE_USAGE <buffer size> must be a positive number of bytes — Error
message for when the capacity argument doesn't parse
12410 VBACKUP_ARGS_APPEND
Append — The symbol for setting position to
LOW_LEVEL_TAPE_POSITION_APPEND
12411 VBACKUP_ARGS_CURRENT
Current — The symbol for setting position to
LOW_LEVEL_TAPE_POSITION_CURRENT
12412 VBACKUP_ARGS_OPTIMAL
Optimal — The symbol for setting blocking to 0 so it defaults
to optimal
Versant Error Codes Reference
103
System Utility Errors, Series – 7000, 9000, 11000,
12300
12413 VBACKUP_ARGS_DYNAMIC
Dynamic — The symbol for setting capacity to 0 so the
hardware is trusted to detected the end of the tape.
12415 VBACKUP_ARGS_BYTES
Bytes — The units for parsing and unparsing bytes
12416 VBACKUP_ARGS_BLOCKS
Blocks — The units for parsing and unparsing 512 byte blocks
12417 VBACKUP_ARGS_KILOBYTES
Kilobytes — The units for parsing and unparsing kilobytes
12418 VBACKUP_ARGS_MEGABYTES
Megabytes — The units for parsing and unparsing megabytes
12419 VBACKUP_ARGS_GIGABYTES
Gigabytes — The units for parsing and unparsing gigabytes
12420 VBACKUP_ARGS_MINUS_ROLLFORWARD -rollforward — internationalized synonym for -rollforward
12421 VBACKUP_ARGS_MINUS_OFF
-off — internationalized synonym for -off
12422 VBACKUP_ARGS_MINUS_LOG
-log — internationalized synonym for -log
12423 VBACKUP_ARGS_MINUS_SCRIPT
-script — internationalized synonym for -log
12424 VBACKUP_ARGS_MINU_AGGRESSIONS -aggression — internationalized synonym for -aggression
12425 VBACKUP_ARGS_AGGRESSION_USAGE <aggression> must be a number of seconds >= 0 — usage for
-aggression
12426 VBACKUP_ARGS_MINUS_RENAME
-rename — internationalized synonym for -rename
12427 VBACKUP_ARGS_USAGE_1
(The usage message displayed when arguments aren't
entered properly.)
Usage: vbackup [options] command
where options are one or more of:
-level <level>
-device <filename>
-position <position>
-capacity <capacity>
-blocking <blocking>
-comment <comment>
-rollforward
-startsync
-aggression <aggression>
-script <script>
12428 VBACKUP_ARGS_USAGE_2
104
(The usage message displayed when arguments aren't
entered properly.)
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
and command is one of:
-backup <database-names>
-restore {<database-name> [-rename
<new-database-name>] [-overwrite]} ...
-off <database-names>
-log <database-names>
-info <database-names>
-list [-getbeprofile [-odir <path-to-save-profile>]]
12429 VBACKUP_ARGS_MINUS_STARTSYNC
-startsync — internationalized synonym for –startsy
12430 VBACKUP_ARGS_HABACKUP_USAGE1
(The usage message displayed when arguments aren't
entered properly.)
usage: habackup [options] command
where options are one or more of:
-cmd <command>
-level <level>
-device <filename>
-rollforward
-startsync
12432 VBACKUP_ARGS_HABACKUP_USAGE2
(The usage message displayed when arguments aren't
entered properly.)
And command is one or more of
-split <database-names>
-backup <database-names>
-restore <new-database-names> [-syncwith
<database-name>]
-off <database-names>
-log <database-names>
12433 VBACKUP_ARGS_MISSING_SPLIT_CMD
Versant Error Codes Reference
-cmd <command> option must be specified — usage
for -split
105
System Utility Errors, Series – 7000, 9000, 11000,
12300
12434 HABACKUP_ARGS_LEVEL_ZERO_DISABLED
Level 0 backup should be performed using –split —
usage for -split
12435 HABACKUP_ARGS_NO_COMMAND
A command is required — Error message for no
command
12436 VBACKUP_ARGS_MINUS_NOPROMPT
-noprompt — internationalized synonym for
-noprompt
12437 VBACKUP_ARGS_MINUS_BACKGROUND
-background — internationalized synonym for
-background
12438 HABACKUP_ARGS_MINUS_SYNCWITH
-syncwith <dbname to syncwith after restore> usage
for -syncwith
12439 HABACKUP_OLIB_INCONSISTENT_RESTORE
The database %s should be restored with the\nnew
name %s. Please try again — verbose version of
HABACKUP_TAPE_INCONSISTENT_RESTORE
12440 VBACKUP_ARGS_MINUS_OVERWRITE
-overwrite — internationalized synonym for
–overwrite
12441 VBACKUP_ARGS_MINUS_GETBEPROFILE
-getbeprofile — internationalized synonym for
-getbeprofile
12442 VBACKUP_ARGS_MINUS_ODIR
-odir — internationalized synonym for -odir
12450 VBACKUP_CLI_COPYRIGHT
Versant Utility VBACKUP Version \%s.\%s
\%s\ncopyright (c) \%s-\%s Versant Corporationtion
— The copyright and version message
12451 VBACKUP_CLI_LIST_HEADER
Listing Versant files on device %s: The header printed
before starting the list
12452 VBACKUP_CLI_LIST_FORMAT_WITH_COMMENT Position %d: %s volume %d blocking %s. %s The
format for listing a file which has a comment.
12453 VBACKUP_CLI_LIST_FORMAT_SANS_COMMENT Position %d: %s volume %d blocking %s. The format
for listing a file which does not have a comment.
12454 VBACKUP_CLI_LIST_TRAILER
Done — The trailer printed after a listing is complete.
12460 VBACKUP_CLI_BACKUP_HEADER
Backing up database %s to device %s — Message
displayed before backup
12461 VBACKUP_CLI_BACKUP_TRAILER
Backup has completed successfully — Message
displayed after backup.
12462 VBACKUP_CLI_RESTORE_HEADER
Restoring database %s from device %s — Message
displayed before restore
106
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
12463 VBACKUP_CLI_RESTORE_TRAILER
Restore has completed successfully — Message
displayed after backup.
12464 VBACKUP_CLI_PERCENT_GAUGE
0\% 50\% 100\%\n | | | | |\n The percentage gauge
printed above the percent markers.
12465 VBACKUP_CLI_PERCENT_GAUGE_MARKER
. — The string used to mark off an increment on the
percent gauge.
12466 VBACKUP_CLI_PERCENT_GAUGE_LENGTH
40 — The number of times the gauge string must be
printed to reach 100%
12467 VBACKUP_CLI_INFO_HEADER
Backup information for database %s — The message
displayed before the backupinfo is listed
12468 VBACKUP_CLI_INFO_FORMAT_WITH_COMMENT Level %d backup made on %s. %s — The format for
providing info on a database with a comment
12469 VBACKUP_CLI_INFO_FORMAT_SANS_COMMENT Level %d backup made on %s. — The format for
providing info on a database which does not have a
comment.
12470 VBACKUP_CLI_INFO_TRAILER
Done — The message displayed after the backupinfo
is listed
12471 VBACKUP_CLI_PRESS_RETURN
Press <return> when you are ready to continue... —
The message displayed while vbackup is waiting for
a <return>
12472 VBACKUP_CLI_ANOTHER_LEVEL_QUERY
Would you like to do another level of restore\non
database %s? [ default = no ] — asks the user if they
would like to do another level of restore
12473 VBACKUP_CLI_MUST_ANSWER_YES_OR_NO
Answer either `yes' or `no' : If the user enters
something other than yes or no
12474 VBACKUP_CLI_YES
Yes %s — yes
12475 VBACKUP_CLI_NO
No — no
12476 VBACKUP_CLI_MOUNT_THE_NEXT_TAPE
Mount the appropriate tape and press return to
begin... Printed between restores
12477 VBACKUP_CLI_DUBIOUS_DATABASE_NAME
Warning: Dubious database name %s. — printed for
database names beginning with '-'
12478 VBACKUP_CLI_ROLL_FORWARD_QUERY
Would you like to roll forward archived logs
for\ndatabase %s? (yes or no) — asks the user if they
would like to do roll forward restore
Versant Error Codes Reference
107
System Utility Errors, Series – 7000, 9000, 11000,
12300
12479 VBACKUP_CLI_SETTINGS
Current settings are : \n\n device = %s\n position =
%s\n capacity = %s\n blocking = %s
12480 VBACKUP_CLI_SETTINGS_PROMPT
[?=help]
12481 VBACKUP_CLI_SETTINGS_HELP
Change a setting by typing a name and new value (e.g.
"position 2"),\ntype "quit" to quit, or type <return> to proceed.
It is only necessary\nto type enough of a command to make
it unique, so you can type "q"\ninstead of "quit" or "p 2"
instead of "position 2".
12482 VBACKUP_CLI_QUIT
Quit — quit
12483 VBACKUP_CLI_SCRIPT
User input required. Running the following script and exiting
:\n %s
12484 VBACKUP_CLI_LOG_HEADER
Archiving log records to device %s — Message displayed before
backup
12485 VBACKUP_CLI_RETURN_TO_EXIT
Press <return> when you are ready to exit — Return to exit
12486 VBACKUP_CLI_SETTINGS_MESSAGE Change additional settings or type <return> to proceed.
12487 VBACKUP_CLI_RF_ON_INFO
Log archiving is on; but no archiver process is running.\n The
next file number will be #%d.
12488 VBACKUP_CLI_RF_OFF_INFO
Log archiving currently off.
12489 VBACKUP_CLI_REMOVE_COPY
After you have verified that the database was\nsuccessfully
restored; remember to remove\n%s
12490 VBACKUP_CLI_RF_RUNNING_INFO
Currently archiving logs to file #%d via connection %d
12491 HABACKUP_CLI_COPYRIGHT
Versant Utility HABACKUP Version \%s.\%s \%s\ncopyright
(c) \%s-\%s Versant Corporation — The copyright and version
message
12500 VBACKUP_RF_CANT_CONNECT
Error while connecting to database %s :\n %s.— error from
o_beginsession or o_connectdb
12501 VBACKUP_RF_CANT_TURN_ON
Error while turning on log roll forward for database %s:\n %s
— error from ut_rollforwardset(db, UT_LRF_ON)
12502 VBACKUP_RF_CANT_TURN_OFF
Error while turning off log roll forward for database %s:\n %s
— error from ut_rollforwardset(db, UT_LRF_OFF)
12503 VBACKUP_RF_CANT_END_SESSION
Error while ending session:\n %s — error from o_endsession
12504 VBACKUP_RF_WRONG_FILE_NUM
Requested log archive file #%d, received #%d — error from
o_endsession
108
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
12505 VBACKUP_RF_WRONG_DBNAME
This is not a log archive for database %d. Error from
o_endsession
12506 VBACKUP_RF_PROMPT
Insert log archive #%d of database %s. Prompt for tape
12507 VBACKUP_RF_ABORT
Aborted at user's request.
12508 VBACKUP_RF_LOGGING_TERMINATED Log archiving terminated for database %d:\n %s
12509 VBACKUP_RF_BACKUP_PENDING
Database %s is pending backup.
12510 VBACKUP_RF_BACKUP_STARTED
Database %s is now being archived.
12511 VBACKUP_RF_COPY_QUERY
During roll forward would you like to apply
records\nfrom the database's current log file in
addition to any\narchived records ? [default = yes ]
12512 VBACKUP_RF_COPY_QUERY_OLD
This logical log file must then be copied to a
safe\nlocation so it is not overwritten during the
restore.\n\nenter the path of the logical log
[default=%s ]
12513 VBACKUP_RF_COPY_QUERY_NEW
Enter the path for storing the copy [ default = %s ]
12514 VBACKUP_RF_COPY_OLD_NOT_FOUND
Could not find the old logical log %s.\n
12515 VBACKUP_RF_COPY_COPY_EXISTS
A file already exists at %s.\n
12516 VBACKUP_RF_COPY_COPYING
Preserving %s as %s.
12517 VBACKUP_RF_VOL_REPLACING
Additional volumes exist in the path.Do u want to
overwrite them
12518 VBACKUP_RF_LOGGING_CANT_TERMINATE
Error while turning off log archiving for database %s:\n
%s — error from ut_rollforwardset (db,
UT_LRF_NOLOG)
12519 HABACKUP_RF_LLOG_QUERY
Do you have a copy of logical.log file that you\nwould
like to apply at this point ? [default = yes ]
12520 HABACKUP_RF_LLOG_PATH
Enter the path of logical.log:
12521 HABACKUP_RF_LLOG_NOT_FOUND
Could not read logical.log at %s.\n
12522 VBACKUP_RF_SUSPEND
Suspended at user's request.
12523 VBACKUP_RF_IS_NOT_SUSPENDED
The database is not in restore suspended mode and
therefore denies to resume the database.\n In
emergency case, please call Versant support
immediately.
Versant Error Codes Reference
109
System Utility Errors, Series – 7000, 9000, 11000,
12300
12550 VBACKUP_SPLIT_CANT_CONNECT
Error while connecting to database: %s\n — error from
o_beginsession or o_connectdb
12551 VBACKUP_SPLIT_CANT_DO_CONDEF
Error while connecting to database: %s\n — error from
db_namecondef
12552 VBACKUP_SPLIT_CANT_RF_FILENUMBERGET Error while connecting to database: %s\n — error from
ut_rollforwardfilenumget
12553 VBACKUP_SPLIT_CANT_BEGINSPLIT
Error trying to start a split on database: %s\n — error
from net_beginsplit
12554 VBACKUP_SPLIT_CANT_ENDSPLIT
Error trying to end a split on database: %s\n — error
from net_endsplit
12555 VBACKUP_SPLIT_CANT_RECOVERSPLIT Error trying to recover from split failure on database: %s\n
— error from net_recoversplit
12556 VBACKUP_SPLIT_EXEC_FAILURE
Error executing command: %s\n — error from executecmd
12600 VSTATS_CLI_USAGE
(The usage message displayed when arguments aren't
entered properly.)
Usage: vstats [options] command
where options are one or more of:
-filename <filename>
-stdin
-database <dbname>
-username <user>
-password <passwd>
-id <connection-id>
-period <seconds>
-iterations <iterations>
-noinfo
and command is one of:
-stats <stats>
-on <stats>
-off <stats>
-connections
-transactions
-locks
-summary
110
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
12601 VSTATS_CLI_COPYRIGHT
Versant Utility VSTATS Version \%s.\%s \%s\ncopyright
(c) \%s-\%s Versant Corporation — The copyright and
version message
12602 VSTATS_CLI_FE_SUMMARY
Frontend per process statistics — header for fe stats
summary
12603 VSTATS_CLI_SE_SUMMARY
Frontend per session statistics — header for se stats
summary
12604 VSTATS_CLI_BE_SUMMARY
Backend per connection statistics — header for be stats
summary
12605 VSTATS_CLI_DB_SUMMARY
Backend per database statistics — header for db stats
summary
12606 VSTATS_CLI_UNIMPLEMENTED
This feature is not implemented yet — for unimplemented
features
12607 VSTATS_CLI_STAT_UNDEFINED
The statistic %s is not defined — for undefined statistics
12608 VSTATS_CLI_NO_DBNAME
You must specify a database name for this command —
given when a dbname is required but not given
12609 VSTATS_CLI_CONNECTIONS_HEADING
Connection ID to database %s:\n — Heading for list of
connections
12610 VSTATS_CLI_CONNECTIONS_ENTRY
Connection ID = %d\n User Name = %s\n Session Name =
%s\n Long Transaction = %s\n Server Process = %s:%d\n
Client Process = %s:%d — Format for connections list entry
12611 VSTATS_CLI_CONFIG_OPEN
Could not open configuration file %s — could not open
config file
12612 VSTATS_CLI_CONFIG_ERROR
Error on line %d of %s — error in config file
12613 VSTATS_CLI_DERIVED_STATS_SUMMARY Derived statistics from %s: — header for printing derived
stats
12614 VSTATS_CLI_NO_DERIVED_STATS
<none defined> — for when no derived stats are defined
12615 VSTATS_CLI_COMPOUND_CONFIG_ERROR Error on line %d of %s:\n\n%s — error in config file
12616 VSTATS_CLI_STATS_REQUIRED
The `-stats' command requires that you specify at least
one statistic — error in config file
12617 VSTATS_CLI_NO_CONNECTIONS
<no connections> — printed when there are no
connections
12618 VSTATS_CLI_INVALID_CONNECTION_ID
Versant Error Codes Reference
%d is not currently a valid connection ID — printed
when there are no connections
111
System Utility Errors, Series – 7000, 9000, 11000,
12300
12619 VSTATS_CLI_CONNECTIONS_ENTRY_TCP
Protocol = TCP/IP\n Server Port = %d.%d.%d.%d:%d\n
Client Port = %d.%d.%d.%d:%d — Format for TCP/IP
specific protocol info
12621 VSTATS_CLI_LOCKS_ENTRY
Object = %s\n External Mode = %s\n Internal Mode =
%s\n Transaction ID = %s\n Flags = %s — Format for
locks list entry
12622 VSTATS_CLI_NO_LOCKS
<no locks> — printed when there are no locks
12623 VSTATS_CLI_LOCK_NOLOCK
None
12624 VSTATS_CLI_LOCK_WLOCK
Write
12625 VSTATS_CLI_LOCK_ULOCK
Update
12626 VSTATS_CLI_LOCK_RLOCK
Read
12627 VSTATS_CLI_LOCK_IWLOCK
Intention to Write
12628 VSTATS_CLI_LOCK_IRLOCK
Intention to Read
12629 VSTATS_CLI_LOCK_RIWLOCK
Read with Intention to Write
12630 VSTATS_CLI_LOCK_RIRLOCK
Read with Intention to Read
12631 VSTATS_CLI_LOCK_RUNNING
Running
12632 VSTATS_CLI_LOCK_WAITING
Waiting
12633 VSTATS_CLI_LOCK_TRANSIENT
Transient
12634 VSTATS_CLI_LOCK_PERSISTENT
Persistent
12635 VSTATS_CLI_LOCKS_HEADING
Locks in database %s:\n — Heading for list of locks
12636 VSTATS_CLI_TRANSACTIONS_ENTRY
Transaction ID = %s\n Name = %s\n Lock Count =
%d\n Connection ID = %d\n Flags = %s — Format for
locks list entry
12637 VSTATS_CLI_NO_TRANSACTIONS
<no transactions> — printed when there are no
transactions
12638 VSTATS_CLI_TRANSACTIONS_HEADING
Transactions in database %s :\n — Heading for list
of transactions
12639 VSTATS_CLI_TRANSACTIONS_SHORT
Short
12641 VSTATS_CLI_CONNECTIONS_ENTRY_INTERNAL Protocol = INTERNAL
Format for INTERNAL protocol info
12646 VSTATS_SYMBOL_UNDEFINED
112
Symbol %s is not defined — symbol not defined
Versant Error Codes Reference
System Utility Errors, Series – 7000, 9000, 11000,
12300
12647 VSTATS_FUNC_NO_DELTA_ENTRY
No delta entry yet... — delta entry not found
12648 VSTATS_FUNC_SYMBOL_TYPE_MISMATCH
Argument %s of function %s must be called with a
symbol value — symbol arg type mismatch
12649 VSTATS_FUNC_DOUBLE_TYPE_MISMATCH
Argument %s of function %s must be called with a
numeric value — double arg type mismatch
12650 VSTATS_FUNC_ARG_NOT_FOUND
Attempt to get value of non-existent argument: Arg
not found
12651 VSTATS_INPUT_FILE_OPEN
OS error %d while opening file %s — fopen failed.
12652 VSTATS_INPUT_VERSION
VSTATS %d.%d.%d cannot read %d.%d.%d files
—incompatible versions
12653 VSTATS_INPUT_SYNTAX_ERROR
Bad file format — Bad format
12654 VSTATS_INPUT_EOF
Unexpected end of file while reading %s — read error
12655 VSTATS_INPUT_ALREADY_OPEN
Attempt to open an open file — double open()
12656 VSTATS_INPUT_ALREADY_CLOSED
Attempt to close a closed file — double close()
12657 VSTATS_INPUT_END_OF_INPUT
End of file reached — expected end of file
12676 VSTATS_PARSER_SYNTAX_ERROR
Syntax Error in position %d of %s — for syntax errors
evaluating expressions
12677 VSTATS_PARSER_INTERNAL_ERROR
Internal error while parsing — This should never
happen
12678 VSTATS_PARSER_UNDEFINED_SYMBOL
The symbol %s is not defined — for undefined
symbols
12679 VSTATS_PARSER_BAD_DECLARATION
Error at position %d of declaration %s — for bad
declarations
12680 VSTATS_PARSER_NEEDS_DBNAME
In the expression:\n\n %s\n\nthe statistic %s must
be followed by a database name. \nall backend and
database statistics must do this. (For example,
\n'db_net_bytes_read db1@foo') — for when db or be
stats are missing a dbname
12681 VSTATS_PARSER_NO_BE
In the expression :\n\n %s\n\nyou used a BE statistic
(%s) without specifying\na connection with the -id
option — for when db or be stats are missing a
dbname
12682 VSTATS_PARSER_NEEDS_DBNAME_OR_ESCAPE In the expression:\n\n %s\n\nthe statistic %s must
be followed by a database name. \nall backend and
Versant Error Codes Reference
113
System Utility Errors, Series – 7000, 9000, 11000,
12300
database statistics must do this. (For example,
\n'db_net_bytes_read db1@foo'). If your database
name begins with\nanything other than a letter, you
must escape it by inserting a\nleading '\\' — for when
db or be stats are missing a dbname
114
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
2.15. Versant C++ Errors, Series — 8000, 40000
8001
CXX_CANT_CAST
Can not cast object of type %s to type %s.
You attempted to cast a pointer or a link to some other type of pointer that it is not compatible
with. This often occurs when using the AS() or L_AS() macros. It can also happen if a parametrized
collection class contains an object of the wrong class, although C++ compile-time type-safety
should prevent this. [ used by 'pclass::offsetof(pclass *type)'] [ used by 'the AS macro, the L_AS
macro, pobject::as()']
This error can 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 [
used by 'class Container']
8003
CXX_DUP_CONTAINER
Multiple containers named %s were found in database
%s [ used by ` class Container']
8004
CXX_BAD_DATE
The date %s %d, %d is illegal [ used by 'class Date
(vnih)']
8005
CXX_BAD_DAY
%s is not the name of a day of the week [ used by 'class
Date (vnih)']
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
[ used by ` Vstr<>'] [ used by 'varray<>, vlist<> '] [ used
by ` linkedlist (vnih)']
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 [ used by
'class Set (vnih)']
8012
CXX_BAD_PRED
Illegal predicate %s was applied to class %s [ used by
'old pclass::select()']
8013
CXX_BAD_ATTR
%s is not an attribute of class %s [ used by 'old
pclass::select()']
Versant Error Codes Reference
115
Versant C++ Errors, Series — 8000, 40000
8014
CXX_SUBSTRING_ERR
Illegal substring from position %d length %d on %s of
length %d
[ used by 'class substring (vnih)']
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
[ used by 'class String, substring (vnih)']
8020
CXX_BAD_DATE_RANGE
The date %s %d, %d is outside the legal range [ used
by 'class Time (vnih)']
8021
CXX_EMPTY
The %s is empty for operation %s [ used by 'class
linkedlist (vnih)']
[ used by 'class orderedcltn (vnih)']
[ used by 'class velist<>']
8022
CXX_BAD_TIME
%d,%d,%d %s %s %d,%d is an invalid time
[ used by 'class Time (vnih)']
8024
CXX_BAD_MONTH
No such month as %s
[ used by 'class Date (vnih)']
8025
CXX_BAD_MONTH_NUM
%d is a bad month number
[ used by 'class Date (vnih)']
8026
CXX_BAD_DAY_NUM
%d is a bad day number
[ used by `class Date (vnih)']
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. A key could not be found in a
dictionary. [ used by 'class Dictionary (vnih)']
[ used by 'class V??Dictionary<>']
116
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
8029
CXX_UNKNOWN
Unknown error number %d was thrown
8030
CXX_ZERO_DENOM
Zero denominator in %s
[ used by 'class Fraction (vnih)']
8031
CXX_NO_MEM
Local memory is exhausted
8032
CXX_FUNC_OVER
Double %g conversion to %s yielded large exponent
%d [ used by 'class Fraction (vnih)']
8033
CXX_FUNC_UNDEFINED
Double %g conversions is undefined for exponent %d
[ used by 'class Fraction (vnih)']
8034
CXX_BAD_LINK
%s next should be zero
[ used by 'class Link (vnih)']
8035
CXX_DERIVED
Virtual method %s should have been implemented by
derived class %s. It is the responsibility of subclasses
of lookupkey to redefine virtual methods value() and
value(const Object&). [ used by 'class lookupkey (vnih)']
8036
CXX_SHOULD_NOT
%s should not implement method %s. The operation
cannot be done on an instance of this class.
[ used by 'vnih classes']
8037
CXX_NOT_IMPLEMENTED
Method %s is not implemented in this release
8038
CXX_INVALID_ITERATOR
Iterator is invalid in %s
[ used by 'Versant Collection classes']
8039
CXX_NO_CLSOBJ
Database does not know about class %s. The schema
for this class has not been installed into the database.
Use sch2db to put the schema from the .sch file into
the database.
8040
CXX_NO_CXXCLS
C++ interface does not know about class %s.
There is no pclassobj<> for the class compiled into your application, and yet your running
application has encountered an instance of that class, or for some other reason needs to find
the pclassobj<> for that class.
Your application does not know the definition of a class.
Versant Error Codes Reference
117
Versant C++ Errors, Series — 8000, 40000
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.
This is a problem because C++ compilers often do not delete temporary objects as soon as they
should.
Please refer the Versant C++ Reference for further information.
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. It is the responsibility
of a subclass of pvirtual to define a compare method.
This error is thrown by the default pvirtual::compare()
8045
CXX_HASH_UNDEFINED
Hashing method undefined. It is the responsibility of
a subclass of pvirtual to define a hash method. This
error is thrown by the default pvirtual::hash().
8046
CXX_INTERNAL_ASSERT
C++ interface internal assertion failed. This error
should never happen. Report it to Versant.
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
118
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
8052
CXX_OM_PANIC
Internal object manager panic: %s (line %d file %s).
This is a serious error. No other database object
manager operations will be possible for this process
after this error. This is cause for terminating your
program and trying again. It may indicate database
corruption.
8054
CXX_CLASS_SIGNATURE
For class %s, compiled class signature %x does not
match schema signature %x in database %s.
A 32-bit signature is calculated for each class during schema capture using a CRC function
across the class and its attributes. This 32-bit signature is compiled into your application and
is also deposited in the .sch file.
Sch2db will read it from the .sch file, and put it into the database. When your application runs,
the signatures in your program are compared against the signatures in the database whenever
database classes are used.
If the signatures do not match, this exception is throw. This can happen when you have a
different defintion of the classes in your application than there are in the database, because
you installed the wrong .sch files into the database. To correct the problem, use sch2db to install
the correct .sch files into the databases.
8055
CXX_NOT_MUNCHED
Problem in munch — static objects did not construct.
The binary you are executing did not "munch" correctly
when it was compiled. It will have to be recompiled
properly before it can be used.
8056
CXX_ASSERTT
An assert macro failed (see "paux.h")
The header paux.h contains two macros, assertt() and assertts(), which throw this error when
they fail. "assertt()" puts the source filename and linenumber in the error, and assertts() puts
a second argument, a string, in the error.
Versant uses assertts() inside their class library 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.
Links and Vstrs 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 endsession.
Versant Error Codes Reference
119
Versant C++ Errors, Series — 8000, 40000
Often you can avoid this by putting braces { } around the work within a session, and closing
them before calling ensession:
Dom->beginsession()
{ ..... Your work ..... }
Dom->endsession()
This is a problem because C++ compilers often do not delete. These temporary objects as soon
as they could.
8058
CXX_BOMB
Internal assertion failed, %s. This error should never
occur. Report it to Versant.
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.
8061
CHL_NO_SESSION
A link was used while no session exists.
You cannot use links (or phandle or 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.
You seem to have a bad link (or phandle or PCOD* or o_object), because it points to an address
which cannot possibly be a COD, because it is outside of the range of addresses in which a COD
could be formed.
8063
CHL_NO_COD_TYPE
Problem in COD. You seem to have a bad link (or
phandle or PCOD* or o_object).
8064
CHL_DELETED
A link to a deleted object was used.
This error is not actually enforced; it seems to be too useful to have links to deleted objects.
(You are still using a link to an object which has been deleted.)
8065
120
CHL_TOP_XHEAP
Persistent object located outside object space.
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
You seem to have a bad link (or phandle or PCOD* or o_object). We intuit that because the
object associated with this non-link would be located outside of the range of permissible
addresses for persistent objects.
8066
CHL_BAD_LOOP
Problem in COD. You seem to have a bad link (or
phandle or PCOD* or o_object).
8067
CHH_NULL
Null object header pointer.
Something is wrong which lead us to beleive that an object has a null header pointer, which
cannot happen. You probably have trashed your object or link.
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
8090
CXX_BAD_VIRTUAL_EVENT
Virtual event %d not understood by object
Experimental.
8091
CXX_DOM_IS_NULL
Global variable dom is NULL
8092
CXX_REL_MISMATCH
Release %s calls %s of release %s.
Two different releases are being mixed together. This will probably cause trouble. The thing
that was called is complaining that the caller is of a different release.
8094
CXX_IS_TRANSIENT
Transient object used in persistent object operation.
Some operations can only be done on persistent objects. One of these operations was attempted
on a transient object. [ used by 'vpp scap']
Versant Error Codes Reference
121
Versant C++ Errors, Series — 8000, 40000
8095
CXX_BILINK_NOTFOUND
A bilink of bilinkvstr relation is missing in the bilink
table. Some bilink or bilinkvstr relation is not inserted
into the bilink relation table.
8096
CXX_ERROR_HEAD_FMT
<Error %ld the output format of an error number.
8097
CXX_FNAME_LNUM_FMT
In %s line %ld the output format of a file name and
line number.
8098
CXX_UNIX_ERRNO_FMT
%s (unix errno %d)the output format of a unix error
number and its name
8099
CXX_UNKNOW_ERRNO_FMT
[unknown unix error %d] the output format of an
unknown unix error number
8100
CXX_NO_MEMORY
No memory (cannot malloc), no more memory is
available
8101
CXX_UNEXPECTED
Unexpected exception, an unexpected exception is
caught
8102
CXX_TERMINATING
Terminating, Process is terminating
8103
CXX_TRY_DEPTH
Too many nested try blocks
8104
CXX_DOUBLE_FAULT
Perror thrown while throwing Perror. Perror thrown
while throwing perror, an internal error
8115
CXX_WORD_IN
In, the English word "in"
8120
CXX_EMPTY_ARRAY
Viarray(vvarray) is empty at %d for %s please use
is_null() to test whether this cell is empty or not before
using the operator[]
8121
CXX_EMPTY_LIST
Vilist(vvlist) is empty at %d for %s please use is_null()
to test whether this cell is empty or not before using
the operator[]
8122
CXX_VDICTION_BASE_CLASS
Vdictionary base class wrong.
8123
CXX_INVALID_METHOD_IN_MULTISESSION Method is not a valid method in multi-session
application
8124
CXX_SELECT_NOT_PERSISTENT
Cannot select from a non-persistent collection object
8125
CXX_TYPE_MISMATCH
Object size of type %s is different from the size in
schema object check whether you have re-built the
schema file after modifying class definition
8126
CXX_PARSE_FAILED
Failed to parse query in d_VQL_Query.
8127
CXX_INVALID_QUERYCOMMAND
D_OQL_execute does not support commands other
than O_QRY_SELECT.
122
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
8128
CXX_INVALID_PROJECTION
Invalid number of projections in
d_OQL_Query::parsedresult.
8129
CXX_ATTRIBUTEOBJ_NOT_FOUND
Attribute object for %s can not be not found.
8130
CXX_ATTRIBUTES_NOT_MATCH
Type of the %d th attribute in projections does not
match the type of the %d th element in the result
variable.
8131
CXX_OLIST_NOT_SUPPORTED
Type O_LIST is not supported.
8132
CXX_CONVERSION_NOT_ALLOWED
Conversion from %s to %s is not allowed in
Pbuffer::converttype().
8133
CXX_NO_MORE_SUBSTITUTES
No more parameter substitute are allowed.
8134
CXX_SUBSTITUTES_NEEDED
Need parameter substitutes for query.
8135
CXX_PROJECTION_NEEDED
No projection is found in the query.
8136
CXX_NOT_MATCH_PROJECTION_TYPE
Result type does not match the type of %d the
projection in the query.
8137
CXX_FAIL_TO_MAP_INT_TYPE
Failed to map type INT or UNSIGNED INT to a Versant
Type.
8138
CXX_NEED_PARSEQUERY
Need to parse query in d_VQL_Query.
8139
CXX_OQL_CLASS_NOT_FOUND
D_oql_execute() Class Object of Input Type is not
found.
8140
CXX_THREAD_NOT_IN_SESSION
There is no session attached to the current vthread
object.
8141
CXX_SESSION_NOT_ATTACHED
Session %s is not attached to the current vthread.
8142
CXX_CONTAINER_IS_EMPTY
STL method %s cannot be applied on an empty
container.
8143
CXX_ITERATOR_OUT_OF_RANGE
Iterator or pointer points to memory which is out of
current allocated space
8144
CXX_ITERATOR_NOT_IN_ORDER
The iterator pair(first last) has the wrong order.
8145
CXX_NO_VTHREAD_OBJECT
There is no vthread object attached to current session
8146
CXX_SESSION_ATTACHED_ALREADY
Session init fails because current thread has already
attached to another session
8147
CXX_TLS_KEY_INIT_ERROR
Kernel call vs_tlsgetptr() returns NULL. Cannot
initialize thread specific data key
8148
CXX_TLS_ALLOCATION_ERROR
Cannot allocate thread local storage. Vs_tlsgetptr()
failed.
Versant Error Codes Reference
123
Versant C++ Errors, Series — 8000, 40000
8149
CXX_KERNEL_CLSOBJ_NOT_INITIALIZED
Cannot access kernel class object; session may not start
yet
8150
CXX_PUSH_EMPTY_ITEM_TO_LIST
Try to push an empty item to a list
8151
CXX_TOO_MANY_SESSIONS
Try to open more than maxinum number of sessions
8152
CXX_LOCAL_TIME_EXCEEDS_LIMITATION
Cannot convert local time earlier than Jan 1st 1970
8153
CXX_NULL_PROFILE_POINTER
Cannot accept NULL pointer in readprofile
8154
CXX_QUERY_HANDLE_NULL
Query handle is NULL. Query may not be compiled
8155
CXX_RESULT_HANDLE_NULL
Result handle is NULL
8156
CXX_NOT_ALL_PROJECTION_SUPPORTED
Only O_OBJECT_TYPE projections are supported
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.
A command-line argument naming a database was missing for a Schema Utility.
8519
SCAP_MALLOC
Out of memory, cannot malloc.
The process ran out of memory while trying to malloc(). You need more swap space. You might
terminate some processes to free up some swap space. Also check that you do not have limits
set low.
8520
SCAP_BOMB
Internal assertion failed, %s. This error should never
occur. Report it to Versant.
8522
SCAP_VERSION
Incompatible .sch-version number: program=%d/%s
.sch=%d/%s.
The version number built into a schema file is not compatible with the version number of the
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 116 Intelx86.
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, .../s116Intelx86.
124
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
8523
SCAP_CORRUPT_SCH
Corrupt .sch file, unexpected object type %d.
The input to a schema utility was not a correct .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.
The utility was unable to do a select on instances of class "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.
The domain of some attribute was not defined at the time that the class containing it was
defined. At the end of 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.
Could be a sign of database corruption. See SCAP_SETDOMAIN.
8527
SCAP_FIXUP_DOMAIN
Cannot locate domain class %s object during fixup of
class %s, attribute %s.
A class was defined with forward references to the domain class. On the second pass, when we
wanted to fixup the forward reference, the domain class still was not defined. You may be
missing some .sch files, or your database could be corrupt. See SCAP_SETDOMAIN.
8528
SCAP_VSTR
Vstr operation failed within schema utility. Check the
kernel error code. You may need a bigger front end
cache size.
8529
SCAP_PREP_CLS
Cannot add signature to class object, for class %s.
We were unable to mark the class object as dirty, so we could not add the class signature to it.
This will prevent the schema signature assertion at runtime.
8530
SCAP_LOC_CLSOBJ
Cannot locate class object, class %s.
This probably indicates a corrupt database, but maybe you were just locked out.
8531
SCAP_LOC_ATTR
Cannot locate attribute object, class %s attribute %s.
This probably indicates a corrupt database, but maybe you were just locked out.
8532
SCAP_LOC_DOMAIN
Cannot locate domain object, class %s attribute %s.
This probably indicates a corrupt database, but maybe you were just locked out.
8533
SCAP_ATTR_MATCH
Versant Error Codes Reference
Database attribute names do not match .sch file,
database %s class %s database-attribute %s
.sch-attribute %s.
125
Versant C++ Errors, Series — 8000, 40000
This probably indicates a corrupt database.
8534
SCAP_ATTR_OFFSET
Database attribute offsets do not match .sch file,
database %s class %s attribute %s database-offset %d
.sch-offset %d.
This represents an inconsistency between the way cfront aligns attributes and they way the
database thinks they should be aligned. Let Versant know about this error.
8535
SCAP_LOC_SUPERCLS
Cannot locate the class object for the superclass of %s.
The class is probably not usable in the database until
the classes are redefined.
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_attrob::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.
For some reason we were unable to locate the class object or to change it. Therefore we could
not add the signature to this object. This may be a problem if it already had a signature and is
now wrong. If you can figure out why the class was unavailble, and fix it, you should try the
schema operation again.
8546
SCAP_DIRTY
Cannot mark an object dirty.
A call to the object manager o_preptochange() was unsucessful. 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.
If you derive classes from 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
126
SCAP_NO_OP_BRACKET
Operator * undefined in Link-like class %s.
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
If you derive classes from 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.
Classes derived from 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.
If classes derive from pobject ard are going to have persistent instances, they cannot have Vstr's
of non-simple data types. "sch2db" will complain if you try to install this class in a database.
8551
SCAP_BEGINSESSION
Cannot begin database session on database %s.
The begin session method failed for the given reason. You might try other applications to see
if they can access the database. You might have misspelled the database name, or you might
not have permission to use it.
8552
SCAP_ENDSESSION
Error during endsession on database %s.
An error was returned during the endsession methods on the database. If you made changes to
the database and have not enabled logging, you may have lost data.
8553
SCAP_NO_DB_NAME
No database name was provided -- use "-D" option.
You need to name which database the command is to act upon. You may do this with the "-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.
Within a group of .sch files, there are two different definitions of the given class. This error can
occur 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.
The named class already exists in the database when a .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
Versant Error Codes Reference
This Versant command does not understand its name.
127
Versant C++ Errors, Series — 8000, 40000
Some Versant commands use their name to determine what to do. Perhaps you renamed the
binary, or have a link to it by a different name than the one used by Versant. The name could
be "sch2db" or "dropclass" or "sch2z".
8557
SCAP_OPTION
Unknown dash option
8558
SCAP_OBJECT_FILE_MAGIC
Object file format error, wrong magic number.
8559
SCAP_OBJECT_COMPILE_DEBUG
Cannot read the .debug section.
You might have forgotten to compile with '-schema' option? Did you compile the file with '-g'
option? Versant schema capture utility does the schema capture based on the debugging
information embedded in the object code. To enable the schema capture, the object code needs
to be compiled with '-g' option.
8560
SCAP_DEBUG_MAP
Cannot map the .debug section to memory, please
contact to Versant Support.
8561
SCAP_SYMBOL_MAP
Cannot map the symbol table section to memory,
please contact to Versant Support.
8562
SCAP_STAB_FORMA
Stab format error, please contact to Versant Support.
8563
SCAP_OBJECT_FILE_OPEN
Cannot open the object file %s
8564
SCAP_STAB_ALIGNMENT_ERROR
Stab format error, alignment error
8565
SCAP_CANT_OPEN_FILE
Cannot open file %s for write
8566
SCAP_ABORT_IN_S
ABORT in %s ,
8567
SCAP_S_INTERRRUPTED
%s Interrupted
8568
SCAP_NO_PLUS_F
Missing +fsourcefilename option
8569
SCAP_ERROR_IN_S
Error in %s
8570
SCAP_NO_PLUS_T
Plus T option not required
8571
SCAP_NO_CXXSUN_SUPPORT
Not supported by cxxsun
8572
SCAP_CXXSUN_NO_SINGLE_QUOTE
Cxxsun does not support single quotes in arguments
8573
SCAP_MISSING_IN_PATHFILE
%s path for %s missing from file %s
8574
SCAP_XLC_INTERNAL_ERROR
Internal error, cannot recover, please contact to
Versant Support.
8575
SCAP_XLC_HEAP_STORAGE
Fatal error in operator new(), heap storage exhausted
8576
SCAP_XLC_SCAP_USAGE
Usage:scapxlc [+v] [+z] [+C] +ffilename
8577
SCAP_XLC_INPUT_FILE_MISSING
Input file name missing, Usage:scapxlc [+v] [+z] [+C]
+ffilename
128
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
8578
SCAP_XLC_HEAP_STORAGE_C
Fatal error in Classdef::operator new(), heap storage
exhausted
8579
SCAP_XLC_HEAP_STORAGE_S
Fatal error in Sym::operator new(), heap storage
exhausted
8580
SCAP_POINTER_TO_CLASS_MEMBER
Warning, pointer to class data member inside
persistent class
8581
SCAP_NO_SCHEMA_FILE_CREATED
No .sch file emitted (missing or bad +f option)
8582
SCAP_CANT_DETERMINE_VTBL
Cannot determine the vtbl name for class %s
8583
SCAP_FATAL_ERROR_IN_BSLOT
Versant Internal error, please contact to Versant
Support.
8584
SCAP_NO_USER_NAME
No user name was provided — use the "-U" option
8585
SCAP_NO_PASSWORD
No password was provided — use the "-P" option
8601
PERR_CANNOT_WRITE
Cannot write to file, An attempt to write a file failed.
Checking the operating system error code (errno) may
be helpful
8602
PERR_CANNOT_MAKE_TOOLCODE
Cannot convert error to toolcode string.
A toolcode string is an internal format for Versant tools to use. Some error occurred while trying
to make this string.
8701
EVPP_BOMB
Internal error in vpp. An internal error that should
never happen has occurred.
Please contact Versant. It would help if you compile with the +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.
[ used by 'vpp']
8703
EVPP_EXPSUP_NOTCLASS
Cannot VPP_EXPAND_SUPER on nonclass.
The statement 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 vpp could be confused and not realize
that something is a class. Customers should not be using the VPP_EXPAND_SUPER statement
directly.
[ used by 'vpp']
8704
EVPP_EXPSUP_OUTSIDE
Cannot use VPP_EXPAND_SUPER outside Template.
The special VPP_EXPAND_SUPER statement can only be used inside a Template definition.
Customers should not be using the VPP_EXPAND_SUPER statement directly.
[ used by 'vpp']
8705
EVPP_PCO_UNDEF
Versant Error Codes Reference
Template pclassobj undefined.
129
Versant C++ Errors, Series — 8000, 40000
The template pclassobj is not defined. Perhaps you forgot to include the standard headers, or
perhaps they are corrupt.
[ used by 'vpp']
8706
EVPP_TPL_UNDEF
Unknown Template.
The template has not been defined yet. The ability to use forward reference templates is very
limited; all templates should be fully defined before they are used.
[ used by 'vpp']
8707
EVPP_AFTER_NOT_TPL
After clause is not a Template.
Only template occurances may follow the keyword `After' in a clause in a template definition.
For example, you could say After Link<X> but you could not say After Employee
[ used by 'vpp']
8708
EVPP_NEST_TPL
Cannot nest Templates definition.
Template definitions may not occur inside a template definition.
[ used by 'vpp']
8709
EVPP_TPL_REDEF
Template redefined.
A template can only be defined once.
[ used by 'vpp']
8710
EVPP_OPTION
Undefined option flag.
A command line option to vpp (starting with a dash) was not understood.
[ used by 'vpp']
8711
EVPP_ARGV
No arguments needed.
The vpp command line does not take any arguments except for those beginning with a dash `-'.
[ used by 'vpp']
8712
EVPP_STDOUT
Error writing standard output.
The vpp command sends its output to standard output. A write failed. This could be because
the disk filled, or due to a hardware error.
[ used by 'vpp']
8713
EVPP_NO_IMP
There is no Implementation for this Template.
You have said to Implement a template that does not have an Implement clause.
[ used by 'vpp']
8714
EVPP_CLAUSE
Undefined Template clause.
A clause of a Template is undefined. This could be a clause named in another After clause, or
it could be a clause that is special to the Versant C++ interface. The latter should not happen
if you include pobject.h.
130
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
[ used by 'vpp']
8715
EVPP_NEST_EXPSUP
Cannot nest VPP_EXPAND_SUPER.
Customers should not be using the special VPP_EXPAND_SUPER statement. The Versant code
should never have nested VPP_EXPAND_SUPER statements. So this error should not happen.
[ used by 'vpp']
8716
EVPP_OUT_OF_MEMORY
Out of memory in parser.
The vpp program ran out of memory. Adding more swap space could help, as could removing
some processes from the machine. Using "stopdb" on a Versant database can also help a lot.
[ used by 'vpp']
8717
EVPP_SYNTAX_ERROR
General syntax error.
The lexer or parser of vpp has detected a syntax error. These are very often mismatched
parentheses or curly braces. Some nonstandard C++ constructs can also confuse vpp.
[ used by 'vpp parser']
8718
EVPP_MULTIPLE_IMPLEMENT
Multiple implement clauses in template definition.
There can only be one Implement clause in a template definition.
[ used by 'vpp']
8719
EVPP_PRIMITIVE_UNDEFINED
Primitive template undefined.
Some templates are special to the Versant interface, and must be there if you are using the
primitive Versant classes. These templates should all be defined if you included pobject.h.
[ used by 'vpp']
8720
EVPP_BAD_LINE_MARKER
Bad line marker.
The vpp program reads and writes filename-and-linenumber marker lines in the format that
the standard C preprocessor understands.
Examples: # "filename" 88 or #line "filename" 88
Something must have created a marker line that vpp cannot understand.
[ used by 'vpp']
8721
EVPP_BAD_PARAMETER
Parameter is not a word.
Vpp template occurrences only accept simple C++ identifiers and other template occurrences
as parameters.
[ used by 'vpp']
8722
EVPP_TPL_RECURSION
Recursive template name.
Vpp has seen a template (or a group of templates) that invoke themselves to get longer and
longer template names. This can happen if you have recursive templates. For instance, template
Versant Error Codes Reference
131
Versant C++ Errors, Series — 8000, 40000
Foo<bar> which uses Foo<Foo<bar>> which uses Foo<Foo<Foo<bar>>> etc. Would create this
error.
[ used by 'vpp']
8723
EVPP_INFINITE_TDEF
Infinite typedef recursion.
The vpp program attempts to understand simple typedef statements so that it will not generate
redundant template definitions. This error occurs if the typedefs create an infinite loop.
[ used by 'vpp']
8750
EVPP_TOO_MANY_NESTED_CLASSES
VPP abort —- more than %d nested class levels!
The vpp parser has a limit of the nesting class level. It is unusual to reach this limit in a normal
program.
[ used by 'vpp']
8751
EVPP_NO_MEMORY_SCANNER
VPP abort —- out of memory.
No memory is available. Either the input file is too huge or there is not enough virtual memory.
[used by 'vpp']
8753
EVPP_SYN_ERROR
VPP finds syntax errors in the following files, VPP finds
some syntax errors.
If these errors are not reported by your C++ compiler, there might be a bug in VPP.
[ used by 'vpp']
8754
EVPP_ACTION_UNKNOWN
VPP abort —- internal error, unknown action.
This is an internal error. Please contact to Versant Support.
[ used by 'vpp']
8755
EVPP_TOO_MANY_TMPL_ARGUMENT
VPP abort —— too many template arguments.
This is an internal ARGUMENT error. Please contact to Versant Support. [ used by 'vpp']
8801
CIH_OFFSET_NO_MEMORY_ATTR
8802
CIH_INTERNAL_NAME_COMPOSTION_ERROR Offset calculation function is not able to compose the
attribute name, please contact to Versant Support.
8803
CIH_OFFSET_FUNCTION_NULL
The pointer for offset calculation in the pclass object
is NULL
8804
CIH_OFFSET_NO_MEMORY_OBJECT
Offset calculation function is not able to allocate
enough memory for the object
8805
CIH_NO_CXX_ACTIVATOR
The pointer for class activator is NULL. The virtual
table pointer and virtual base pointer value cannot be
set
132
Offset calculation function is not able to allocate
enough memory for offset table
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
8806
CIH_OFFSET_CALCULATION_ERROR
The offset calculation function internal error, cannot
allocate enough memory
8807
CXX_TRANSIENT_NO_WHAT
The transient object doesn't have RTTI information.
You need to call O_ACTIVATE_RTTI on the transient
object.
8808
CXX_ATTRIBUTE_NOT_FOUND
Versant internal error. Attribute %s can not be found
in the pclassobject of %s
8900
VRT_BUFFER_SIZE_MISMATCH
Can not interpret an object of size %d as type %s.
The vrtbuffer class is used to access heterogeneous attribute values. There is a mismatch between
the size of the attribute data type and the size of the data type that application interprets that
attribute to be.
8925
VSO_MAGIC_NUMBER_MISMATCH
The shared object arena is corrupted.
A magic number is stored in the shared object arena. When an application connects to shared
object arena the magic number is checked. The exception is thrown if the magic number is
incorrect.
8926
VSO_VERSION_MISMATCH
The format of the shared object arena does not match
the application.
A format version stored in the shared object arena does not match the number compiled into
the application.
8927
VSO_CLASS_SIGNATURE_MISMATCH
For class %s, compiled class signature does not match
schema signature in the shared object arena
A 32-bit signature is calculated for each class during schema capture using a CRC function
across the class and its attributes. This 32-bit signature is compiled into your application. The
exception is thrown if the class signature for the same class is not the same in all applications
which share the same object arena.
40101 T_SCAP_DEFINE_CLASS
Define class %s
40102 T_SCAP_DROP_CLASS
Drop class %s and all its instances
40103 T_SCAP_DROP_INSTANCES
Drop instances of class %s
40104 T_SCAP_GET_NEW_ATTR
Class %s gets new attribute %s
40105 T_SCAP_GET_DROP_ATTR
Class %s drop attribute %s
40106 T_SCAP_PRINT_VERSION
This is version %s
40107 T_SCAP_SCHEMA_CHANGES_NEEDED
Schema changes needed:
40108 T_SCAP_NO_CHANGES_APPLIED
NO CHANGES APPLIED
40109 T_SCAP_APPLYING_SCHEMA_CHANGES
APPLYING SCHEMA CHANGES
Versant Error Codes Reference
133
Versant C++ Errors, Series — 8000, 40000
40110 T_SCAP_WILL_DROP_INST
Will drop instances of,
40111 T_SCAP_OK_TO_APPLY_Q
OK to apply changes?
40112 T_SCAP_NOT_A_TTY
Standard input is not a tty, so '-y' option is required
for changes
40113 T_SCAP_DROPPING_INSTANCES
DROPPING INSTANCES
40114 T_SCAP_NO_SCHEMA_CH_REQ
No schema changes required.
40115 T_SCAP_NO_CLASSES_TO_DROP_INST
There are no classes of which to drop the instances
40116 T_SCAP_GET_RENAME_ATTR
Class %s renames attribute %s as %s
40117 T_SCAP_GROUP_ADD_ATTR
Group add %d attributes
40118 T_SCAP_CLASS_NEEDS_REARRANGE
Class %s needs rearrange
40119 T_SCAP_CHANGE_CLASS_SIGNATURE
Change class signature for class %s from %x to %x
40150 T_SCAP_USAGE_DROPCLASS_1
Usage, dropclass [-options....] Class1 class2 ...
40151 T_SCAP_USAGE_DROPINST_1
Usage, dropinst [-options....] Class1 class2 ...
40152 T_SCAP_USAGE_SCH2DB_1
Usage, sch2db [-options....] File1.sch file2.sch ...
40153 T_SCAP_USAGE_DASH_D
\t-D db\tdatabase, use database db (or use O_DBNAME
environment)
40154 T_SCAP_USAGE_DASH_N
\t-n\tno, make no changes
40155 T_SCAP_USAGE_DASH_Y
\t-y\tyes, make any changes
40156 T_SCAP_USAGE_DASH_I
\t-i\tinteractive (default), ask yes or no (stdin must be
tty)
40157 T_SCAP_USAGE_DASH_E
\t-e\tevolution, schema evolution is a potential
strategy
40158 T_SCAP_USAGE_DASH_R
\t-r\trename, rename attribute is a potential strategy
40159 T_SCAP_USAGE_DASH_F
\t-f\tforce, dropping classes is a potential strategy
40160 T_SCAP_UNKNOWN_OPTION
Unknown Option
40161 T_SCAP_USAGE_DASH_U
\t-u\tuser, run as this DB user
40162 T_SCAP_USAGE_DASH_P
\t-p\tpassword, enter password for the DB user entered
in -u
40171 T_SCAP_DB2TTY_USAGE
\n\tusage 1: db2tty -D databasename [options] [
classnames ... ]\n\tusage 2: db2tty -D databasename
[-l] -o loids\n\t-i\tshow instances\n\t-a\tshow all
classes (including system)\n\t-s\tshow schema
infomation only\n\t-t LX\toperate in long transaction
134
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
LX\n\t-l\tuse read locks (default is NOLOCK)\n\t-n
<num>\tnumber of objects per cursor fetch (default is
200,valid only with -i option)\n\t-o loids\tdisplay
objects with specified loids
40301 REBILINK_WARNING
\ndo you really want to change all\nold bilink objects
in the database?\n\nthe new bilink objects are NOT
compatible with old\napplications.
You will need to recompile your old\napplications to access new bilink objects.\n\npress the
ENTER key twice to continue, or press\ncontrol-C to abort this program.\n
40302 REBILINK_USAGE
%s [-Q] -D database_name\n
40303 REBILINK_LOCATE_SUPER
Problem locating superclass object [%ld] of class %s,
40304 REBILINK_LOCATE_ATTR
Problem locating attribute object [%ld] of class %s,
40401 D_Error_None
40402 D_Error_databaseclassmismatch
For class %s, compiled class signature %x does not
match schema signature %x in database %s
40404 D_Error_databaseclosed
Database %s is either already closed or has not yet been
opened
40405 D_Error_databaseopen
Database %s is already opened
40406 D_Error_dateinvalid
%d/%d/%d is an invalid date
40407 D_Error_iteratorexhausted
Iterator is invalid in %s
40408 D_Error_namenotunique
An object with name %s already exists in the database
40409 D_Error_positionoutofrange
Index of %d applied to %s object is out of bounds %d
40410 D_Error_queryparameter
Countinvalid
40411 D_Error_queryparameter
Typeinvalid
40412 D_Error_refinvalid
40413 D_Error_refnull
D_Ref is NULL
40414 D_Error_timeinvalid
%d,%d,%d is an invalid time
40415 D_Error_timestampinvalid
Invalid timestamp
40416 D_Error_transactionopen
A transaction has already opened
40418 D_Error_databasenull
The database pointer is NULL
40419 D_Error_Iteratoruninitialized
The iterator has not been initialized with a collection
40420 D_Error_tzinvalid
%d,%d is an invalid time zone time
Versant Error Codes Reference
135
Versant C++ Errors, Series — 8000, 40000
40421 D_Error_Double_Fault
D_Error thrown while throwing d_Error
D_Error thrown while throwing d_Error, an internal
error
40422 D_Error_badinterval
The d_Interval spcified is bad, check the hour, min and
sec
40423 D_Error_Already_Connected
This group database has been connected already
40424 D_Error_sessiondatabaseopened
A session database has already been opened
40425 D_Error_nametransientobject
Cannot create name for a transient object
40426 D_Error_Duplicaterelsetinsertion
Try to insert an duplicated element to a d_Rel_Set
40427 D_Error_elementnotincollection
Cannot find the element in a collection
40428 D_Error_invalideventtype
Invalid event type for function get_notified
40429 D_Error_illegaldatabasename
A null database name is not allowed
40430 D_Error_transactionstillactive
Cannot close a database with active transactions
40431 D_Error_transactionalreadydetached The transaction had already detached from the
database
40432 D_Error_Transactionalreadyattached The transaction had already attached to the database
40433 D_Error_transactionclosed
A transaction is either closed or not yet opened
40434 D_Error_Notransactiondatabase
There is no database opened for current transaction
40435 D_Error_transactionnotconnected
Current transaction is not connected to database %s
40436 D_Error_databaseinvalid
Cannot open database %s. Check if the dbname is valid.
40437 D_Error_deleteunknowntransientobj
Cannot delete a transient object of unknown type
40600 D_Error_XA_OK
40602 D_Error_XAER_ASYNC
Async. Operation already outstanding
40603 D_Error_XAER_RMERR
An RM error occurred in the transaction branch
40604 D_Error_XAER_NOTA
The XID is not valid
40605 D_Error_XAER_INVAL
Invalid arguments were given
40606 D_Error_XAER_PROTO
XA routine invoked in improper context
40607 D_Error_XAER_RMFAIL
The Resource Manager is unavailable
40608 D_Error_XAER_DUPID
XID already exists
40609 D_Error_XAER_OUTSIDE
RM doing work outside global transaction
40610 CXX_NO_SESSIONPOOL
The SessionPool is unavailable
136
Versant Error Codes Reference
Versant C++ Errors, Series — 8000, 40000
50000 USER_DEFINED_ERROR
Versant Error Codes Reference
User defined error is $(userdefined)
137
GUI Tool Errors, Series — 10000
2.16. GUI Tool Errors, Series — 10000
10000 GUI_TEST_ERROR_MESSAGES
During initialization, this test message is read in.
If it does not match the string GUI_TEST_ERROR_MESSAGES, the program is aborted with a
message that the error message file could not be found.
10026 GUI_BOOLEAN_CLASSNAME
Boolean — The name of the gui_boolean type
10027 GUI_BOOLEAN_TURN_ON
Turn On — The name of the guiboolean_turnon
operation.
10028 GUI_BOOLEAN_TURN_OFF
Turn Off — The name of the guiboolean_turnoff
operation.
10029 GUI_BOOLEAN_TOGGLE
Toggle — The name of the guiboolean_toggle
operation.
10051 GUI_BUTTON_CLASSNAME
Button — The name of the gui_button type
10061 GUI_CALLBACK_CLASSNAME
Callback — The name of the gui_callback type
10076 GUI_DIALOG_CLASSNAME
Dialog — The name of the gui_dialog type
10101 GUI_DICTIONARY_CLASSNAME
Dictionary — The name of the gui_dictionary type
10126 GUI_EDIT_FIELD_CLASSNAME
Edit Field —The name of the gui_editfield type
10151 GUI_ELEMENT_CLASSNAME
Element — The name of the gui_element type
10176 GUI_ERROR_CLASSNAME
Error — The name of the gui_error type
10177 GUI_ERROR_WARNING
Warning — Format for warnings printed to stdout
10178 GUI_ERROR_ERROR
Error — Format for errors printed to stdout
10179 GUI_ERROR_FATAL_ERROR
Fatal Error — Format for fatal errors printed to stdout
10201 GUI_FIELD_CLASSNAME
Field — The name of the gui_field type
10202 GUI_FIELD_CUT
Cut — The name of the guifield_cut operation
10203 GUI_FIELD_PASTE
Paste — The name of the guifield_paste operation
10204 GUI_FIELD_CLEAR
Clear — The name of the guifield_clear operation
10226 GUI_FILE_CLASSNAME
File — The name of the gui_file type
10251 GUI_FONT_CLASSNAME
Font — The name of the gui_font type
10252 GUI_FONT_HELVETICA
Helvetica — The name of the Helvetica font
10253 GUI_FONT_TIMES
Times — The name of the Times font
138
Versant Error Codes Reference
GUI Tool Errors, Series — 10000
10254 GUI_FONT_COURIER
Courier — The name of the Courier font
10255 GUI_FONT_SYMBOL
Symbol — The name of the Symbol font
10256 GUI_FONT_BOLD
Bold — The name of the Bold style
10257 GUI_FONT_ITALIC
Italic — The name of the Italic style
10258 GUI_FONT_UNDERLINE
Underline — The name of the Underline style
10276 GUI_IPC_CLASSNAME
GUI IPC — The name of the gui_ipc type
10277 GUI_IPC_CLEANUP
Cleaning up... — The message shown during cleanup
which happens after ctrl-C
10301 GUI_LABEL_CLASSNAME
Label — The name of the gui_label type
10302 GUI_LABEL_COPY
Copy — The name of the guilabel_copy operation
10326 GUI_LIST_CLASSNAME
List — The name of the gui_button type
10351 GUI_LIST_VIEW_CLASSNAME
List View — The name of the gui_listview type
10371 GUI_MESSAGING_LOCALIZED_WB_FLAG
-workbench — A localized alias for -workbench /
-softbench
10372 GUI_MESSAGING_WB_NOT_AVAILABLE
This application was not compiled to support
Worbench/Softbench. Error given when -workbench
is used but the application was not Compiled with
workbench support.
10376 GUI_MESSAGE_DIALOG_CLASSNAME
Message Dialog — The name of the gui_messagedialog
type
10401 GUI_MENU_CLASSNAME
Menu — The name of the gui_menu type
10402 GUI_MENU_HELP_MENU_NAME
Help — The name of the help menu
10426 GUI_NUMBER_CLASSNAME
Number — The name of the gui_number type
10427 GUI_NUMBER_SECOND
Second — The word to use for 1 second
10428 GUI_NUMBER_SECONDS
Seconds — The word to use for n seconds
10429 GUI_NUMBER_MINUTE
Minute — The word to use for 1 minute
10430 GUI_NUMBER_MINUTES
Minutes — The word to use for n minutes
10431 GUI_NUMBER_HOUR
Hour — The word to use for 1 hour
10432 GUI_NUMBER_HOURS
Hours — The word to use for n hours
10433 GUI_NUMBER_DAY
Day — The word to use for 1 day
10434 GUI_NUMBER_DAYS
Days — The word to use for n days
10435 GUI_NUMBER_BYTE
Byte — The word to use for 1 byte
Versant Error Codes Reference
139
GUI Tool Errors, Series — 10000
10436 GUI_NUMBER_BYTES
Bytes — The word to use for n bytes
10437 GUI_NUMBER_KILOBYTE
Kilobyte — The word to use for 1 kilobytes
10438 GUI_NUMBER_KILOBYTES
Kilobytes — The word to use for n kilobytes
10439 GUI_NUMBER_MEGABYTE
Megabyte — The word to use for 1 megabytes
10440 GUI_NUMBER_MEGABYTES
Megabytes — The word to use for n megabytes
10441 GUI_NUMBER_GIGABYTE
Gigabyte — The word to use for 1 gigabytes
10442 GUI_NUMBER_GIGABYTES
Gigabytes — The word to use for n gigabytes
10451 GUI_OBJECT_CLASSNAME
Object — The name of the gui_object type
10476 GUI_OPERATION_DIALOG_CLASSNAME
Operation Dialog — The name of the
gui_operationdialog type
10477 GUI_OPERATION_DIALOG_OK
OK — The name of the guioperationdialog_ok operation
used to implement the "OK" button in the operation
dialog box.
10478 GUI_OPERATION_DIALOG_OK_EMPTY_FIELD All the fields must be filled in. — The message
presented to the user when a field is left empty
10479 GUI_OPERATION_DIALOG_CANCEL
Cancel The name of the guioperationdialog_cancel
operation used to implement the "Cancel" button in
the operation dialog box.
10480 GUI_OPERATION_DIALOG_WARNING
Warning — The name of the
guioperationdialog_warning operation used to
implement the warning dialog box for operations with
warnings.
10481 GUI_OPERATION_DIALOG_HELP
Help — The name of the guioperationdialog_help
operation used to implement the "Help" button on the
dialog box
10482 GUI_OPERATION_DIALOG_YES
Yes — Alternate label for "OK" button
10483 GUI_OPERATION_DIALOG_NO
No — Alternate label for "Cancel" button
10501 GUI_OPERATION_CLASSNAME
Operation — The name of the gui_operation type
10526 GUI_OPERATION_TYPE_CLASSNAME
Operation Type — The name of the gui_operationtype
type
10551 GUI_OPTION_CLASSNAME
Option — The name of the gui_option type
10576 GUI_PULLDOWN_CLASSNAME
Pulldown Menu — The name of the gui_pulldown type
10601 GUI_RECTANGLE_CLASSNAME
Rectangle — The name of the gui_rectangle type
140
Versant Error Codes Reference
GUI Tool Errors, Series — 10000
10626 GUI_REFERENCE_FIELD_CLASSNAME
Reference Field — The name of the gui_referencefield
type
10627 GUI_REFERENCE_FIELD_WRONG_TYPE
This field can only hold objects that are of type %s.
The message given when an object of the wrong type
is dropped in the field
10628 GUI_REFERENCE_FIELD_FIND_FAILED
Could not find an instance of %s which matches the
string %s. The message given when the findinstance
method returns NULL.
10651 GUI_SCROLLER_CLASSNAME
Scroller — The name of the gui_scroller type
10676 GUI_SUBSET_CLASSNAME
Subset — The name of the gui_subset type
10677 GUI_SUBSET_SELECT_ALL
Select All — The name of the guisubset_selectall
operation for setting the subset equal to the set
10678 GUI_SUBSET_UNSELECT_ALL
Unselect All — The name of the guisubset_unselectall
operation for clearing the subset.
10701 GUI_TEXT_CLASSNAME
Text — The name of the gui_text type
10726 GUI_TEXT_VIEW_CLASSNAME
Option — The name of the gui_option type
10751 GUI_TOGGLE_CLASSNAME
Toggle — The name of the gui_toggle type
10776 GUI_TYPE_CLASSNAME
Type — The name of the gui_type type
10801 GUI_VIEW_CLASSNAME
View — The name of the gui_view type
10802 GUI_VIEW_UNDEFINED_DROP
Dropping an instance of %s on an instance of %s is
undefined. By default, this message will be presented
for drag and drop
10803 GUI_VIEW_CLOSE
Close — The name of the guiview_close operation used
for closing windows
10816 GUI_VMESSAGE_APPNAME
Versant Message — The name of the application
10817 GUI_VMESSAGE_USAGE
Usage vmessage <target> <message> — The usage
message
10818 GUI_VMESSAGE_INVALID_TARGET
Invalid target. — Error printed when sendmessage fails.
10819 GUI_VMESSAGE_MESSAGE_FAILED
Failed to send message — Error printed when
sendmessage fails.
10820 GUI_VMESSAGE_VIEWS_UNAVAILABLE
The DISPLAY environment variable must be set. The
error message to give when no X display is specified
10821 GUI_VMESSAGE_MINUS_INFO
-info — Localized alias for -info
10822 GUI_VMESSAGE_MINUS_RESET
-reset — Localized alias for -reset
Versant Error Codes Reference
141
GUI Tool Errors, Series — 10000
10826 GUI_WINDOW_CLASSNAME
Window — The name of the gui_window type
10831 GUI_PERCENT_VIEW_CLASSNAME
Percent Bar — The name of the gui_percentview type
10836 GUI_PERCENT_DIALOG_CLASSNAME
Percent Dialog — The name of the gui_percentdialog
type
10837 GUI_PERCENT_DIALOG_ABORT
Cancel — The name of the percentdialog_abort option
10841 GUI_TEXT_DIALOG_CLASSNAME
Text Dialog — The name of the gui_textdialog type
10842 GUI_TEXT_DIALOG_ABORT
Cancel — The name of the textdialog_abort option
142
Versant Error Codes Reference
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising