⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 messages_en.properties

📁 derby database source code.good for you.
💻 PROPERTIES
📖 第 1 页 / 共 5 页
字号:
# database errors.# sqlstate range: XSLA0 to XSLAZXSLAT.D=The log directory ''{0}'' exists. The directory might belong to another database. Check that the location specified for the logDevice attribute is correct.XSLAS.D=Log directory {0} not found in backup during restore. Please make sure that backup copy is the correct one and it is not corrupted.XSLAR.D=Unable to copy log file ''{0}'' to ''{1}'' during restore. Please make sure that there is enough space and permissions are correct. XSLAQ.D=cannot create log file at directory {0}.XSLAP.D=Database at {0} is at version {1}. Beta databases cannot be upgraded,XSLAO.D=Recovery failed unexpected problem {0}.XSLAN.D=Database at {0} has an incompatible format with the current version of the software.  The database was created by or upgraded by version {1}.XSLAM.D=Cannot verify database format at {1} due to IOException.XSLAL.D=log record size {2} exceeded the maximum allowable log file size {3}. Error encounted in log file {0}, position {1}XSLAK.D=Database has exceeded largest log file number {0}.XSLAJ.D=The logging system has been marked to shut down due to an earlier problem and will not allow any more operations until the system shuts down and restarts.XSLAI.D=Cannot log the checkpoint log recordXSLAH.D=A Read Only database is being updated.XSLAF.D=A Read Only database was created with dirty data buffers.XSLAE.D=Control file at {0} cannot be written or updated.XSLAD.D=log Record at instant {2} in log file {3} corrupted. Expected log record length {0}, real length {1}.XSLAC.D=Database at {0} have incompatible format with the current version of software, it may have been created by or upgraded by a later version.XSLAB.D=Cannot find log file {0}, please make sure your logDevice property is properly set with the correct path separator for your platform.XSLAA.D=The store has been marked for shutdown by an earlier exception.XSLA8.D=Cannot rollback transaction {0}, trying to compensate {1} operation with {2}XSLA7.D=Cannot redo operation {0} in the log.XSLA6.D=Cannot recover the database.XSLA5.D=Cannot read log stream for some reason to rollback transaction {0}.XSLA4.D=Cannot write to the log, most likely the log is full.  Please delete unnecessary files.  It is also possible that the file system is read only, or the disk has failed, or some other problems with the media.XSLA3.D=Log Corrupted, has invalid data in the log stream.XSLA2.D=System will shutdown, got I/O Exception while accessing log file.XSLA1.D=Log Record has been sent to the stream, but it cannot be applied to the store (Object {0}).  This may cause recovery problems also.XSLA0.D=Cannot flush the log file to disk {0}.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Transactions/Basic# statement errors.# sqlstate range: XSTA0 to XSTAZ# changed XSTA0 and XSTA1 to match DB2 sqlstates - bug 44663B501.S=A SAVEPOINT with the passed name already exists in the current transaction.3B502.S=A RELEASE or ROLLBACK TO SAVEPOINT was specified, but the savepoint does not exist.3B001.S=SAVEPOINT, {0} does not  exist or is not active in the current transaction.3B002.S=The maximum number of savepoints has been reached. XSTA2.S=A transaction was already active, when attempt was made to make another transaction active.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Transactions/Basic# transaction errors.# sqlstate range: 40XT0 to 40XTZ40XT0=An internal error was identified by RawStore module.40XT1=An exception was thrown during transaction commit.40XT2=An exception was thrown during rollback of a SAVEPOINT.40XT4=An attempt was made to close a transaction that was still active. The transaction has been aborted.40XT5=Exception thrown during an internal transaction.40XT6=Database is in quiescent state, cannot activate transaction.  Please wait for a moment till it exits the quiescent state.40XT7=Operation is not supported in an internal transaction.##java/com/ibm/db2j/internalUtil#	Id Parse Errors       			XCXA0-XCXAZ#  	Db Class Path Parse Errors 	 	XCXB0-XCXBZ# 	Id List Parse Errors			XCXC0-XCXCZ#  	IO Errors						XCXD0-XCXDZ#	LocaleFinder Errors				XCXE0-XCXEZXCXA0.S=Invalid identifier.XCXB0.S=Invalid database classpath: ''{0}''.XCXC0.S=Invalid id list.XCXE0.S=You are trying to do an operation that uses the territory of the database, but the database does not have a territory.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Transactions/Basic# system errors.# sqlstate range: XSTB0 to XSTBZXSTB0.M=An exception was thrown during transaction abort.XSTB2.M=Cannot log transaction changes, maybe trying to write to a read only database.XSTB3.M=Cannot abort transaction because the log manager is null, probably due to an earlier error.XSTB5.M=Creating database with logging disabled encountered unexpected problem.XSTB6.M=Cannot substitue a transaction table with another while one is already in use.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Data/Generic# transaction errors.# sqlstate range: 40XD0 to 40XDZ40XD0=Container has been closed40XD1=Container was opened in read-only mode.   40XD2=Container {0} cannot be opened; it either has been dropped or does not exist.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Data/Generic# statement errors.# sqlstate range: XSDA0 to XSDAZXSDA1.S=An attempt was made to access an out of range slot on a pageXSDA2.S=An attempt was made to update a deleted recordXSDA3.S=Limitation: Record cannot be updated or inserted due to lack of space on the page. Use the parameters derby.storage.pageSize and/or derby.storage.pageReservedSpace to work around this limitation.XSDA4.S=An unexpected exception was thrownXSDA5.S=An attempt was made to undelete a record that is not deletedXSDA6.S=Column {0} of row is null, it needs to be set to point to an object.XSDA7.S=Restore of a serializable or SQLData object of class {0}, attempted to read more data than was originally storedXSDA8.S=Exception during restore of a serializable or SQLData object of class {0}XSDA9.S=Class not found during restore of a serializable or SQLData object of class {0}XSDAA.S=Illegal time stamp {0}, either time stamp is from a different page or of incompatible implementationXSDAB.S=cannot set a null time stampXSDAC.S=Attempt to move either rows or pages from one container to another.XSDAD.S=Attempt to move zero rows from one page to another.XSDAE.S=Can only make a record handle for special record handle id.XSDAF.S=Using special record handle as if it were a normal record handle.XSDAG.S=The allocation nested top transaction cannot open the container.XSDAI.S=Page {0} being removed is already locked for deallocation.XSDAJ.S=Exception during write of a serializable or SQLData objectXSDAK.S=Wrong page is gotten for record handle {0}.XSDAL.S=Record handle {0} unexpectedly points to overflow page.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Data/Generic# database errors.# sqlstate range: XSDB0 to XSDBZXSDB0.D=Unexpected exception on in-memory page {0}XSDB1.D=Unknown page format at page {0}XSDB2.D=Unknown container format at container {0} : {1}XSDB3.D=Container information cannot change once written: was {0}, now {1}XSDB4.D=Page {0} is at version {1}, the log file contains change version {2}, either there are log records of this page missing, or this page did not get written out to disk properly.XSDB5.D=Log has change record on page {0}, which is beyond the end of the container.XSDB6.D=Another instance of Derby may have already booted the database {0}.XSDB7.D=WARNING: Derby (instance {0}) is attempting to boot the database {1} even though Derby (instance {2}) may still be active.  Only one instance of Derby should boot a database at a time. Severe and non-recoverable corruption can result and may have already occurred.XSDB8.D=WARNING: Derby (instance {0}) is attempting to boot the database {1} even though Derby (instance {2}) may still be active.  Only one instance of Derby should boot a database at a time. Severe and non-recoverable corruption can result if 2 instances of Derby boot on the same database at the same time.  The db2j.database.forceDatabaseLock=true property has been set, so the database will not boot until the db.lck is no longer present.  Normally this file is removed when the first instance of Derby to boot on the database exits, but it may be left behind in some shutdowns.  It will be necessary to remove the file by hand in that case.  It is important to verify that no other VM is accessing the database before deleting the db.lck file by hand.XSDB9.D=Stream container {0} is corrupt.XSDBA.D=Attempt to allocate object {0} failed.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Data/FileSystem# statment errors.# sqlstate range: XSDF0 to XSDFZXSDF0.S=Could not create file {0} as it already exists.XSDF1.S=Exception during creation of file {0} for containerXSDF2.S=Exception during creation of file {0} for container, file could not be removed.  The exeception was: {1}.XSDF3.S=Cannot create segment {0}.XSDF4.S=Exception during remove of file {0} for dropped container, file could not be removed {1}.XSDF6.S=Cannot find the allocation page {0}.XSDF7.S=Newly created page failed to be latched {0}XSDF8.S=Cannot find page {0} to reuse.XSDFB.S=Operation not supported by a read only databaseXSDFD.S=Different page image read on 2 I/Os on Page {0}, first image has incorrect checksum, second image has correct checksum. Page images follows: {1} {2}XSDFF.S=The requested operation failed due to an unexpected exception.# java/com/ibm/db2j/impl/Database/Storage/RawStore/Data/FileSystem# database errors.# sqlstate range: XSDG0 to XSDGZXSDG0.D=Page {0} could not be read from disk.XSDG1.D=Page {0} could not be written to disk, please check if disk is full.XSDG2.D=Invalid checksum on Page {0}, expected={1}, on-disk version={2}, page dump follows: {3}XSDG3.D=Meta-data for Container {0} could not be accessedXSDG5.D=Database is not in create mode when createFinished is called.XSDG6.D=Data segment directory not found in {0} backup during restore. Please make sure that backup copy is the right one and it is not corrupted.XSDG7.D=Directory {0} could not be removed during restore. Please make sure that permissions are correct.XSDG8.D=Unable to copy directory ''{0}'' to ''{1}'' during restore. Please make sure that there is enough space and permissions are correct. # language01500=The constraint {0} on table {1} has been dropped.01501=The view {0} has been dropped.01502=The trigger {0} on table {1} has been dropped.01503=The column {0} on table {1} has been modified by adding a not null constraint.01504=The new index is a duplicate of an existing index: {0}.01505=The value {0} may be truncated.01522=The newly defined synonym ''{0}'' resolved to the object ''{1}'' which is currently undefined.01003=Null values were eliminated from the argument of a column function.0100E=XX Attempt to return too many result sets. 02000=No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table.21000=Scalar subquery is only allowed to return a single row.22001=A truncation error was encountered trying to shrink {0} ''{1}'' to length {2}.54006=The length resulting from {0} operation is greater than {1}.22003=The resulting value is outside the range for the data type {0}.22005=An attempt was made to get a data value of type ''{0}'' from a data value of type ''{1}''.22007.S.180=The string representation of a datetime value is out of range.22007.S.181=The syntax of the string representation of a datetime value is incorrect.22008.S=''{0}'' is an invalid argument to the {1} function.22011=The second or third argument of the SUBSTR function is out of range.22012=Attempt to divide by zero.22013=Attempt to take the square root of a negative number, ''{0}''.22014=The start position for LOCATE is invalid; it must be a positive integer. The index  to start the search from is ''{2}''.  The string to search for is ''{0}''.  The string to search from is ''{1}''. 22015=The ''{0}'' function is not allowed on the following set of types.  First operand is of type ''{1}''.  Second operand is of type ''{2}''.  Third operand (start position) is of type ''{3}''.22018=Invalid character string format for type {0}.22019=Invalid escape sequence, ''{0}''. The escape string must be exactly one character. It cannot be a null or more than one character.22025=Escape character must be followed by escape character, '_', or '%'. It cannot be followed by any other character or be at the end of the pattern.22027=The built-in TRIM() function only supports a single trim character.  The LTRIM() and RTRIM() built-in functions support multiple trim characters.22501=An ESCAPE clause of NULL returns undefined results and is not allowed.2200L=XMLPARSE operand is not an XML document; see next exception for details.23502=Column ''{0}''  cannot accept a NULL value.23505=The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by ''{0}'' defined on ''{1}''.23503={2} on table ''{1}'' caused a violation of foreign key constraint ''{0}'' for key {3}.  The statement has been rolled back.23513=The check constraint ''{1}'' was violated while performing an INSERT or UPDATE on table ''{0}''.38000=The exception ''{0}'' was thrown while evaluating an expression.38001=The external routine is not allowed to execute SQL statements.38002=The routine attempted to modify data, but the routine was not defined as MODIFIES SQL DATA.38004=The routine attempted to read data, but the routine was not defined as READS SQL DATA.39004=A NULL value cannot be passed to a method which takes a parameter of primitive type ''{0}''.40XC0=Dead statement. This may be caused by catching a transaction severity error inside this statement.# this error is retired in 1.342000=Syntax error or access rule violation; see additional errors for details.# DB2 error for max length violation by char, varchar and long varchar. In future, this error message will be used for other purposes too42601=In an ALTER TABLE statement, the column ''{0}'' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.42601.S.372=ALTER TABLE statement cannot add an IDENTITY column to a table.42606=An invalid hexadecimal constant starting with ''{0}'' has been detected.54002=A string constant starting with ''{0}'' is too long.42611=The length, precision, or scale attribute for column, or type mapping ''{0}'' is not valid. 42605=The number of arguments for function ''{0}'' is incorrect.42610=All the arguments to the COALESCE/VALUE function cannot be parameters. The function needs at least one argument that is not a parameter.42613=Multiple or conflicting keywords involving the ''{0}'' clause are present.

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -