7.19 DB0x Errors

NOTE:This guide does not include a comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved.

DB01 Operation cancelled

Source: GroupWise engine; administration engine.
Explanation: Operation cancelled.
Possible Cause: Operation cancelled by user.
Action: None.

DB02 Database access error

Source: GroupWise engine; administration engine.
Explanation: Database access error.
Possible Cause: Cannot complete the requested operation because the database is being updated.
Action: Retry the operation later. If you still cannot access the database, check file activity using your network administration utilities.

DB03 Operation pending; cannot modify

Source: GroupWise engine; administration engine.
Explanation: Unsafe record modification.
Possible Cause: This record has a pending operation and cannot be modified. A remote operation has been requested for this record.
Action: Wait for the MTA or POA to complete the pending operation, or undo the operation. See Pending Operations in System in the GroupWise 2012 Administration Guide.

DB04 Owner not valid user

Source: GroupWise engine; administration engine.
Explanation: Invalid owner.
Possible Cause: The owner you specified is not a valid user in the same post office as the resource.
Action: Select an owner for the resource from among the users in the same post office as the resource. See Changing a Resource’s Owner in Resources in the GroupWise 2012 Administration Guide.
Action: Create a new user in the post office to function as the owner of the resource. See Creating GroupWise Accounts in Users in the GroupWise 2012 Administration Guide.

DB05 Invalid path

Source: GroupWise engine; administration engine.
Explanation: Invalid path specified.
Possible Cause: The specified path exists; however, it is not a directory.
Action: Enter a new path, or remove the invalid path.

DB08 Non-unique name

Source: GroupWise engine; administration engine.
Explanation: Non-unique name.
Possible Cause: The specified name (object.po.domain) conflicts with an existing user, resource, group, or nickname.
Action: Specify a new, unique name.

DB09 User owns resource

Source: GroupWise engine; administration engine.
Explanation: User owns a resource.
Possible Cause: The specified user cannot be deleted or moved because he or she owns a resource.
Action: Remove the resource. See Deleting a Resource in Resources in the GroupWise 2012 Administration Guide.
Action: Reassign the resource to another owner. See Changing a Resource’s Owner in Resources in the GroupWise 2012 Administration Guide.
Possible Cause: If this error occurs after removing resources from a user to be deleted or moved, the change might not yet have replicated through the system.
Action: Wait for replication to occur or manually synchronize the resource(s) and user. See Synchronizing Database Information in Databases in the GroupWise 2012 Administration Guide.
Action: Rebuild the post office database (wphost.db). See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

DB0A Record not found

Source: GroupWise engine; administration engine.
Explanation: Record not found.
Possible Cause: Cannot find a record that was previously in the database. The record might have been deleted.
Action: Check Pending Operations to see if the command is still awaiting execution. See Pending Operations in System in the GroupWise 2012 Administration Guide.
Action: Retry the command.
Action: Make sure the record was replicated throughout the system. See Synchronizing Database Information in Databases in the GroupWise 2012 Administration Guide.

DB0B Required field empty

Source: GroupWise engine; administration engine.
Explanation: Required field empty.
Possible Cause: A required field has no value.
Action: Supply a value for all required fields.

DB0C Cannot close database

Source: GroupWise engine; administration engine.
Explanation: Error closing database.
Possible Cause: An error was encountered while attempting to close the database.
Action: Check the network connection to the database location.

DB0E Insufficient memory to initialize database

Source: GroupWise engine; administration engine.
Explanation: Database initialization failure.
Possible Cause: The database failed to initialize because of insufficient memory. ConsoleOne requires at least 500 KB of available RAM.
Action: Check the amount of available memory and reconfigure your system if necessary.

DB0F Domain not found

Source: GroupWise engine; administration engine.
Explanation: Domain not found.
Possible Cause: Cannot find the specified domain.
Action: Make sure that the domain exists and that the domain name is correct. In ConsoleOne, browse to and right-click the Domain object, then click Properties.
Possible Cause: If this error occurs from the POA, the post office database (wphost.db) might be damaged so that valid domain information is not available.
Action: Check and, if necessary, repair the database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide.