Breadcrumb(); > Message Index (by Number) (by Subsystem) > Store Subsystem Messages
Store Subsystem Messages
The Store1.0 catalog contains messages in the range BEA280000 - BEA280999. Messages in this catalog are part of the
weblogic.store Internationalization package and the
weblogic.store Localization package.
Debug:
msg
Description
A generic debug message Cause
Debug message. Action
No action required. Info: A new store log extent was created in the file "fileName"
Description
The specified file was created to serve as a location to hold updates to the persistent store. Cause
The number of objects held in the persistent store has increased and it is necessary to allocate more disk space for their storage. Action
No action required. Error: An error was encountered when creating a new log extent: msg
Description
When attempting to create a new file to store persistent objects, an error occurred. Cause
The disk may be full or there may be a hardware problem. Action
Check that there is enough disk space available in the store directory. Warning: An error occurred when cleaning up the persistent store log: msg
Description
An attempt was made to reduce the size of the persistent store's log, but an error occurred. Cause
Internal error. Action
Contact product support. Warning: An error occurred while attempting to move a persistent store record: msg
Description
The persistent store periodically attempts to save space by moving older records within the log or to the heap file. This error is produced when this process fails. Cause
There may be a problem with the disk hardware, or the disk(s) where the store keeps its log and data files may be full. Action
Check that the hardware is functioning and that there is sufficient disk space. The server should continue to function in the meantime. Warning: An error occurred while deleting records from the heap file: msg
Description
The persistent store keeps long-lived records, as well as large records, in a separate file. This error is produced when the file must be cleaned out of deleted records. Cause
The disk may be full, or there may be another problem with the heap file itself. Action
Check that there is sufficient disk space and that all the files that make up the persistent store are available on-line. The server should continue to function in the meantime. Error: The persistent store was unable to complete the recovery process: msg
Description
There was a problem with the contents of the existing persistent store files, or the store was unable to perform additional updates to the persistent data as part of the boot-time recovery process. Cause
See the detail message. Action
Ensure that all the store files are available on line and that the disk is not full, then restart the server. Error: A record with an invalid log type of type was found in the persistent store's log files
Description
A bad log record was found in the persistent store's log. Cause
There could have been a hardware or operating system problem that caused the log to be corrupted, or there may be a version mismatch of the server running against the log. Action
Ensure that the hardware is functioning properly, that all the environment variables are set correctly, and that no other process is running that could be accessing the log. Restart the server. Info: Opening an instance of the persistent file store for recovery
Description
The persistent store is scanning its log and data files in order to reconstruct its state at the last time it was running. Cause
Informational message. Action
No action required. Info: The persistent file store has been opened and contains numRecs records
Description
The persistent store has scanned its files and recovered its state at the last time that it was running. Cause
Informational message. Action
No action required. Error: The specified flags argument is invalid
Description
A method was called that has a "flags" parameter, and the value of this parameter was incorrect. Cause
Programming error. Action
Check the code and try again. Error: The specified log record has an invalid type
Description
When a zero-length log record is logged, the "type" parameter must not be zero. Cause
Programming error. Action
Check the code and try again. Error: 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. Action
Check the code and try again. Error: The specified file store record is longer than the maximum length of maxLength bytes
Description
The record is too large. Cause
Programming error. Action
Either change the code or increase the size of the record. Error: The unreserve method is not supported with manual log space management
Description
The "unreserve" method must only be used when the log is opened with automatic space management. Cause
Programming error. Action
Fix the code and try again. Error: The log record lsn was not found
Description
The specified log record has not yet been written and flushed to the log. Cause
Either "flush" has not yet been called, or the caller specified an invalid LSN. Action
Check the code and try again. Error: There was an error while checking the directory for log files
Description
The store directory containing log files could not be read Cause
Either the directory is not available, or there is a hardware failure. Check the detail message for more information. Action
Check that the persistent store directory is available and that the hardware is working. Error: There was a gap in the collection of log files available. File num is missing.
Description
Not all the expected log files could be found, so the log cannot be safely recovered. Cause
Either a file was accidentially deleted or moved, or there is an I/O problem in the hardware or software. Action
Check the detail message, and double-check that the persistent store directory was correctly specified. Error: An invalid number of extents was specified
Description
The "initialExtents" and/or "maxExtents" parameter were specified incorrectly. Both must be greater than or equal to one, and "maxExtents" must be equal to or greater than "initialExtents" Cause
Programming error. Action
Fix the code and try again. Error: There was an error while writing to a file store file
Description
There was an error while writing to a file. See the detail message for more information. Cause
See the detail message for the cause. Action
Ensure that the hardware and O/S are functioning properly and that there is enough disk space available for the file store''s files. Error: There was an error while reading from the log file
Description
There was an error while reading from the log file. See the detail message for more information. Cause
See the detail message for the cause. Action
Ensure that the hardware and O/S are functioning properly and that all the persistent store''s files are available on line. Error: There was an error while opening the file store file "name"
Description
A file could not be opened. The persistent store may not be able to recover. Cause
The specified file does not exist, or the server does not have permissions to open the file, or there is a hardware or O/S problem. Action
Ensure that the file exists and that the directory name was specified correctly. Error: The log file "name" is not a valid log file
Description
The specified file is not a valid log file because it was not created by a compatible version of WebLogic Server. Cause
The file was created by another program, or it was corrupted. Action
Ensure that the file's directory name is correctly specified, and that the O/S and hardware are functioning properly. Remove the file and restart the server. Warning: There was an error while closing a log file
Description
A file that was previously open could not be properly closed. Cause
There may be a hardware or O/S problem. Action
No action required. The server will recover from this error. Error: 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. Action
Ensure that there is enough disk space and that the hardware and O/S are working properly. Error: 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. Action
Fix the code and try again. Error: The file "name" is not both readable and writeable
Description
The specified file store file file or raw disk partition cannot be both read and written. Cause
The file permissions are incorrect, or the server is running under the wrong user ID. Action
Fix the file permissions or run the server under the correct user ID. Error: The persistent store's log properties file is missing the required property "propName"
Description
The specified property is missing from the properties file. Cause
The file was created incorrectly, or the specified file is not the correct file. Action
Fix the file and re-start the server. Error: The header on a persistent store record is longer than the maximum of max bytes
Description
The persistent store only allows the header to be a certain length. Cause
Programming error. Action
Fix the code and try again. Error: The persistent store record id could not be found
Description
The specified record does not exist, or the transaction has not yet been committed. Cause
Programming error. Action
Ensure that the correct record ID was specified. Error: The persistent store record could not be updated because the original header was goodLength bytes long and the new header is badLength bytes long
Description
The persistent store requires that once a record is created with a header, any "update" operations must replace the header with a header of the same length. Cause
Programming error. Action
Fix the code and try again. Error: The persistent store named "storeName" has not yet been opened
Description
It is an error to call any methods on the persistent store before it has been opened. Cause
Programming error. Action
Fix the code and try again. Error: The persistent store suffered a fatal error and it must be re-opened
Description
Once certain kinds of errors occur, the persistent store must be closed and re-opened in order to ensure that the data remains consistent. Cause
A fatal error occurred previously. Action
Restart the server. Info: The persistent store found records from an older version of WebLogic. It is upgrading this data to a newer version.
Description
When a file store from an older version of WebLogic Server is found, each record in that file store must be converted into a new format before the file store may be used. Cause
Normal operation. Action
No action required. Info: The persistent store converted count records from an older version
Description
When a file store from an older version of WebLogic Server is found, each record in that file store must be converted into a new format before the file store may be used. This message indicates that conversion is complete. Cause
Normal operation. Action
No action required. Error: Unable to access the file store directory "name"
Description
The specified directory cannot be accessed. See the detail message for more information. Cause
See the detail message. Action
Check that the specified path name is correct, that it exists, and that the directory is readable and writeable by the server's user ID. Error: Missing the file store file "fileName" in the directory "dirName"
Description
The file store was expecting to find the specified file, but it is not available. Cause
The file has been accidentially deleted or moved, or the wrong directory name was specified, or the server process does not have permissions to read and write the file. Action
Ensure that the directory name is correct and that the server process has permissions to read and write the files. If necessary, create an empty file with the same name. Error: 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. Action
Delete data from the store and try again. Error: An error occurred while flushing the contents of a file store file
Description
The flush operation on a file store file ensures that the data in the file is persistently written to disk. This operation failed. See the detail message for more information. Cause
See the detail message. Action
See the detail message. Error: The persistent store handle id is not valid
Description
The specified persistent store handle is not a valid handle because it was not actually generated by the persistent store. Cause
Programming error. Action
Fix the code and try again. Error: An invalid record was found in the file store. Code=code
Description
A record in the file store was invalid, either becuse its header was not intact or because its checksum was invalid. The "code" may be used by BEA Support to understand the exact problem. Cause
The store file has been corrupted, possibly by a hardware or O/S error. Action
Restore from backup. Error: An record was found in the file store with an invalid version of version
Description
A record in the file store was invalid because it contains an incorrect version number. Cause
The store file may have been used with an incompatible version of WebLogic Server. Action
Restore from backup. Error: The file store file "name" cannot be opened because it is actually a directory
Description
The file store is attempting to open files in its directory, but one of those files actually is a directory itself. Cause
A directory was accidentially created in the file store's own directory, or the path specified is incorrect. Action
Check that the file store's path is correct. Error: The file store file "name" cannot be opened because it is already open
Description
The specified file has already been opened and may not be re-opened. Cause
Internal programming error. Action
Contact product support. Error: The file store directory "name" does not exist
Description
The persistent store cannot be opened because its directory does not exist. Cause
The directory has not yet been created, or its filesystem is not available. Action
Check that the directory path has been correctly specified, and create the directory if necessary. Error: The file store directory "name" is not a directory
Description
The persistent store cannot be opened because its directory is not actually a directory. Cause
The directory has not yet been created, or its filesystem is not available. Action
Check that the directory path has been correctly specified, remove any file or directory that already exists in its place, and create the directory if necessary. Error: The directory "name" is not both readable and writeable
Description
The specified file store directory cannot be both read and written. Cause
The file permissions are incorrect, or the server is running under the wrong user ID. Action
Fix the file permissions or run the server under the correct user ID. Error: 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. Action
Contact product support. Error: 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. Action
Ensure hard-drive is not failing. Also ensure only one open JMS store has access to the file. Ensure no other process is writing to the file. Note that corrupted blocks are zeroed out and re-used by the JMS store after this log message is printed. Error: The maximum size of a log extent was exceeded. The maximum size is maxSize bytes.
Description
The persistent file store only supports log extent up to the specified maximum size. Cause
Configuration error. Action
Reduce the maximum extent size and try again. Info: Persistent store "storeName" opened: directory="dirName" writePolicy="writePolicy" blockSize=blockSize directIO=directIO driver="driverInfo"
Description
This is an informational message that describes the status of the persistent store's data files. This information is useful when performing performance tuning. Cause
Normal operation. Action
No action required. Error: The persistent store was not able to create a new record.
Description
There may have been an error serializing the record. Cause
Internal Error. Action
Contact product support. Error: The persistent store was not able to read a record.
Description
There may have been an error deserializing the record. Cause
Internal Error. Action
Contact product support. Error: An attempt was made to use a closed store.
Description
The store may not be used after close is called. Cause
Internal Error. Action
Contact product support. Error: Cannot close store because there are currently n active connections: s
Description
All connections created from a store must be closed before the store is closed. Cause
Internal Error. Action
Contact product support. Error: Invalid name for store write policy: "s"
Description
The legal write policy names are "Cache-Flush", " Direct-Write", and "Disabled" Cause
Internal Error. Action
Contact product support. Error: A persistent store error occurred: s
Description
This message wraps a store exception that occurred elsewhere. See the description of the underlying exception, documented in this file, for more information. Cause
See the description of the underlying exception. Action
See the description of the underlying exception Error: The persistent store named "storeName" is already open
Description
It is an error to attempt to open a store twice. Cause
Programming error. Action
Fix the code and try again. Error: 'name' is not a valid store name.
Description
Valid store names are restricted to valid java identifier characters or the '.' character. Cause
Programming error. Action
Fix the code and try again. Error: '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. Action
Fix the code and try again. Emergency: 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. Action
Restart the server. Error: The persistent store "name" could not be deployed: msg
Description
The persistent store could not be deployed. See the detail message for information about the cause of the failure. Cause
See detail message. Action
See detail message. Warning: The persistent store "name" could not be shut down: msg
Description
The persistent store could not be shut down. See the detail message for information about the cause of the failure. Cause
See detail message. Action
See detail message. Error: The "type" field value "val" in table reference "tableRef" (format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "maxLength" for this field.
Description
Databases have limits on the length of identifiers. Cause
Configuration error. Action
When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name. Error: exceptionText (server="serverName" store="storeName" table="tableRef")
Description
An error occurred and an exception was thrown from the named JDBC store. Cause
See exception text, and linked exception (if one exists). Action
See exception text, and linked exception (if one exists). Error: exceptionText (server="serverName" store="storeName" table="tableRef"):(Linked Cause, "rootCauseText")
Description
An error occurred and an exception was thrown from the named JDBC store. Cause
See exception text, and linked exception text. Action
See exception text, and linked exception text. Error: Empty field value in table reference "tableRef" (format [[[catalog.]schema.]table).
Description
The location of the JDBC table has been configured incorrectly. Cause
Configuration error. Action
Make sure the entire table reference is blank, or that the table field is not blank. If there is no schema, make sure there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references. Notice: JDBC store "storeName" did not find a database table at "tableRef", so it created one using the commands in file "fileName".
Description
The first time a JDBC store boots, it creates a table in the database for data storage. The commands it uses to create this table are database specific, and are stored in the indicated file. If the indicated file was administratively configured, the JDBC store first searches for it in the file path, then in the java classpath. If the indicated file was not administratively configured then the JDBC store generated the file name based on the database vendor name, and located the default version of the file in the java class path (default files are stored in the weblogic.jar under weblogic/store/io/jdbc/ddl/). Cause
The JDBC store did not find its backing table, so it created one. Action
None. Error: JDBC store failed to initialize. It did not find its database table and failed trying to create a new empty table using the commands in file "fileName".
Description
The first time a JDBC store boots, it creates a table in the database for data storage. The commands it uses to create this table are database specific, and are stored in the indicated file. If the indicated file was administratively configured, the JDBC store first searches for it in the file path, then in the java classpath. If the indicated file was not administratively configured then the JDBC store generated the file name based on the database vendor name, and located the default version of the file in the java class path (default files are stored in the weblogic.jar under weblogic/store/io/jdbc/ddl/). Cause
See linked exception text and linked exception stack trace. Action
See linked exception text and linked exception stack trace. Error: JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because the JDBC driver is unknown and/or unsupported. To force table creation with an unknown and/or unsupported driver, see the JDBC store "CreateTableDDLFile" configuration attribute. Driver information: database product name = "databaseProduct", driver name = "databaseDriver".
Description
The first time a JDBC store boots, it creates a table in the database for data storage. The commands it uses to create this table are database specific, and are stored in a text file (termed a DDL file). If the DDL file locatiion was administratively configured, the JDBC store first searches for it in the file path, then in the java classpath. If the DDL file location was not administratively configured then the JDBC store generated the file name based on the database vendor name, and searches for the default version of the file in the java class path (default files are stored in the weblogic.jar under weblogic/store/io/jdbc/ddl/). Cause
See exception text and exception stack trace. Action
See exception text and exception stack trace. Error: JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because it could not locate the configured DDL file "filename".
Description
The first time a JDBC store boots, it creates a table in the database for data storage. The commands it uses to create this table are database specific, and are stored in a text file (termed a DDL file). If the DDL file locatiion was administratively configured, the JDBC store first searches for it in the file path, then in the java classpath. If the DDL file location was not administratively configured then the JDBC store generated the file name based on the database vendor name, and searches for the default version of the file in the java class path (default files are stored in the weblogic.jar under weblogic/store/io/jdbc/ddl/). Cause
The configured file is located in the server file path. Action
For supported databases consider the option of not configuring a custom DDL file, there is usually no need to configure a custom DDL file unless custom database specific tuning commands have been added to the file. If a DDL file must be configured (perhaps because it is for an unsupported database), ensure that the configured file is located either in the server file path or server class path. Info: JDBC store "storeName" opened table "tableRef" and loaded recordCount. For additional JDBC store information, use the diagnostics framework while the JDBC store is open.
Description
For additional JDBC store information, use the diagnostics framework while the JDBC store is open. Cause
A JDBC store booted. Action
None. Error: JDBC store "storeName" failed to open table "tableRef".
Description
A JDBC store failed to open, any resources that depend on this store will also fail to open. Cause
See linked exception. Action
See linked exception. Error: 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. Action
Ensure that the file store was upgraded using the weblogic.Upgrade tool. Error: The persistent store "name" encountered an unresolvable failure while processing transaction "xid". Shutdown and restart to resolve this transaction. t
Description
This message is logged when the store encounters an error that it cannot recover from while processing a transaction. In most cases, this happens in the case of certain I/O errors, when the store must be restarted so that it can determine the status of transaction"s persistent data. Cause
There was a serious I/O error, either with file I/O or the JDBC connection to the database, or an unexpected exception was thrown while processing a transaction. Action
Restart the server. Error: JDBC store "storeName" failed to retain ownership of database table "tableRef", either due to database access problems or due to concurrent accessors of the table. See the linked exception for more information.
Description
A JDBC store failed to retain ownership of the database table. The JDBC store will be closed. Cause
Some other WebLogic server process or JDBC store has taken over ownership of the database table, or some database access error prevented this JDBC store from renewing ownership of the database table. Action
The error message has information to identify potential owners in conflict. Warning: Database table "tableRef" for store "storeName" is currently owned by "currentOwner". Trying to wait for ownership.
Description
A JDBC store failed to get ownership of the database table. Cause
Some other WebLogic server process or JDBC store has ownership of the database table. Action
The warning message has information to identify the current owner of the database table. If the current owner does not yield ownership within some time, this server will not be able to open the JDBC store and will log an error. Error: JDBC store "storeName" in this server is not the owner of database table "tableRef". Unexpected current owner is "currOwner", expected current owner is "me".
Description
A JDBC store in a server encountered an unexpected owner of the database table. Cause
Some other WebLogic server process or JDBC store has ownership of the database table. Action
The error message has information to identify and resolve the owners in conflict. Error: The handle passed was created from a different store connection
Description
Only the store connection that creates a PersistentHandle is capable of performing further operations on the handle Cause
Programming error. Action
Ensure that the correct connection was used Info: An instance of the mSA PersistentStore
Info: Number of create requests issued by this store.
Info: Number of read requests issued by this store.
Info: Number of update requests issued by this store.
Info: Number of delete requests issued by this store.
Info: Number of objects contained in the store.
Info: Number of times the store flushed its data to durable storage.
Info: An instance of an mSA PersistentStoreConnection.
Info: Number of create requests issued by this store connection.
Info: Number of read requests issued by this store connection.
Info: Number of update requests issued by this store connection.
Info: Number of delete requests issued by this store connection.
Info: Number of objects contained in the store connection.