Error List

Error List for the ‘WL92-Store’ Category

BEA-280012 - Recovery is not yet complete

Description:
The file store may not be used until log and heap recovery is complete. This means that the “recover” method must be called until it returns null.

Cause:
Programming error.

WL92-Store

BEA-280047 - The "force" operation is not supported on files on this system

Description:
The file store must “force” or “sync” files on its filesystem in order to guarantee that they will survive a hardware or power failure. This operation is not supported on this system.

Cause:
The specified operating system or filesystem may not be adequate for the requirements of WebLogic Server.

WL92-Store , ,

BEA-280023 - There was an error while creating a new file named "name" for the file store

Description:
The file store file could not be created and initialized. See the detail message for more information.

Cause:
See the detail message. The disk may be full, or there may be a hardware or O/S problem.

WL92-Store ,

BEA-280059 - 'name' is not a valid store connection name.

Description:
Valid store connection names are restricted to valid java identifier characters or the ‘.’ character.

Cause:
Programming error.

WL92-Store , , ,

BEA-280037 - The file store has reached the maximum number of maxFiles files and no more files may be created

Description:
The file store has a maximum number of files allowed, and once this limit is reached the store cannot hold any more data.

Cause:
There are too many records in the store.

WL92-Store

BEA-280073 - The file store "name" could not be opened because it contained a file with the invalid version versionFound. A file of version versionExpected was expected.

Description:
The file store could not be opened because a file was found that was not the proper version.

Cause:
The file store has not been properly upgraded from a previous version of WebLogic Server, or the file has been corrupted on the disk.

WL92-Store , , ,

BEA-280013 - The specified file store record is longer than the maximum length of maxLength bytes

Description:
The record is too large.

Cause:
Programming error.

WL92-Store

BEA-280048 - Corruption was detected in the heap file "name" at position position. The corresponding file block will be zeroed out on disk, and this corruption will not be reported in the future

Description:
Invalid data was discovered in the heap, which is where the file store keeps long-running records. The corresponding file block will be zeroed out on disk, and this corruption will not be reported in the future.

Cause:
This may happen from time to time when the server is restarted after a catastrophic failure. In that case, the server will recover and its data will remain consistent.

WL92-Store

BEA-280025 - The log file size or offset is invalid

Description:
The size of a raw log partition must be a multiple of the block size, and so must the offset.

Cause:
Programming error.

WL92-Store

BEA-280060 - The persistent store "name" encountered a fatal error, and it must be shut down: message

Description:
This message is logged when the store encounters an error that it cannot recover from. This happens in the case of certain I/O errors, when the store must be restarted so that it can determine the status of all persistent data.

Cause:
There was a serious I/O error, either with file I/O or the JDBC connection to the database.

WL92-Store , , , ,