Oracle Email Administrator's Guide Release 9.0.3 Part Number B10033-01 |
|
| View PDF |
This chapter includes component-specific errors, listed in numerical order. The error codes are divided into the following groups:
Error messages may appear in any part of Oracle Email. Users may see them in the end-user interface, and administrators may see them in the administrative tools and process logs.
Sometimes, more than one error is displayed. A list of error messages is called an error stack. The bottommost error in the stack is typically the cause of the error.
Note: The error stack may contain error messages from other Oracle products that Oracle Email uses. When these additional errors appear, refer to the documentation for the given product. |
The following is a list of IMAP4 and POP3 error messages:
Cause: Invalid user name or password used for LOGIN
command.
Action: Check the user name, password and try again.
Cause: Used all your allowed login attempts
Action: Check the user name and password, then retry in a new session.
Cause: IMAP/POP session ended either by LOGOUT/QUIT
command or because of some other fatal server error like unable to read or write to client connection anymore.
Action: Session end by LOGOUT/QUIT
command is normal. If you suspect an abnormal connection termination, check for other errors in this error chain in server log file.
Cause: Successful login via authenticate command
Action: None
Cause: Unsuccessful login attempt via authenticate command
Action: Check the user credentials and try again.
Cause: Possibly a non-existent folder name was used.
Action: Correct the folder name and try again. If folder name is correct, check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: Server unable to create OCI connection pool.
Action: Make sure database is up and configured correctly in Oracle Internet Directory.
Cause: Successful connections to the database
Action: None
Cause: Database related error
Action: Check for OCI error in this error chain
Cause: Your session was idle for too long
Action: Send noop or any other command before timeout.
Cause: No more free memory is available to server.
Action: Reduce the load on server by reducing any of following: threads, max. clients, OCI sessions or Oracle Internet Directory connections. Make sure enough free memory is available for server on your system.
Cause: Internal error
Action: Contact customer support
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: There are no more free sessions available in OCI connection pool.
Action: This may be a temporary error due to a spike in load. You may need to reevaluate your system to reduce the number of clients connecting to this database, increase the number of sessions in pool or tune the system in general to get faster response.
Cause: Database error.
Action: Check the OCI errors in this error chain
Cause: Trying to rename a non-existent folder, or the new name is already in use or not allowed.
Action: Make sure folder with old name exists and new name is not already in use or contains restricted characters. Check for any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause:
Action: Check the folder name you are trying to create. Also check for any OCI errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API
is loaded. Check and resolve any other database errors in this error chain.
Cause: Syntax error in flag list for Store command.
Action: Correct the syntax for flag list.
Cause: Possible causes are:
Action: Make sure you are looking for the right folder and is spelled correctly. If it is a shared folder, check its configuration and permissions in Oracle Internet Directory. Check and resolve any other database errors in this error chain.
Cause: Database error.
Action: Check and resolve database errors in this chain.
Cause: Possible causes are:
Action: Check the name of the folder and make sure you are the owner of the shared folder you are trying to delete. Check for database errors in this error chain.
Cause: Possible causes are:
Action: Make sure you are the owner of shared folder or retry with a different name.
Cause: Database error.
Action: Check the database and Oracle Internet Directory error logs.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API
is loaded. Check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API
is loaded. Check and resolve any other database errors in this error chain.
Cause: One of the required message attributes is missing in database.
Action: Make sure all required packages are loaded in the database correctly.
The following is a list of SMTP server error messages:
Cause: The process is consuming too much memory.
Action: Reduce the number of threads running and restart the process.
Cause: The process is consuming too much memory.
Action: Reduce the number of threads running and restart the process.
Cause: There are too many threads in the process.
Action: Reduce the number of threads and restart the server. If the problem persists, contact technical support.
Cause: The Oracle Internet Directory server may be down.
Action: Restart the Oracle Internet Directory server. If the problem still exists contact technical support.
Cause: The Oracle Internet Directory server may be down.
Action: Restart the Oracle Internet Directory server. If the problem still exists contact technical support.
Cause: The Oracle Internet Directory server may be down.
Action: Restart the Oracle Internet Directory server. If the problem still exists contact technical support.
Cause: The address resolution for the recipient resulted in a loop.
Action: Make sure the data present in the Oracle Internet Directory server does not introduce any loops for the recipient. Check if auto forward attribute for the recipient introduces a chain ending with original recipient.
Cause: Mandatory attribute orclobjectid
is missing in Oracle Internet Directory.
Action: Populate correct value for the user in Oracle Internet Directory.
Action: Make sure all required packages are loaded in the database correctly. Check if ES_MESSAGE_API
is loaded.
Action: Make sure all required packages are loaded in the database correctly. Check if ES_OT_API
is loaded.
Cause: The user rule resulted in rejection of the message.
Action: None.
Cause: Auto reject is set in Oracle Internet Directory entry for the recipient.
Cause: There may be OCI errors.
Action: Make sure all required packages are loaded in the database correctly. Check if ES_MESSAGE_API
is loaded.
Action: Check the log for exact reason for failure prior to this message, and see any correction for the user's setup is needed.
Cause: Error in recovery processing.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_QUEUE_API is loaded.
Cause: Error in recovery processing.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_QUEUE_API is loaded.
Action: Populate orclmailsmtpexternalfilterprocess
with path for virus scanner executable if virus scanning is enabled.
Cause: Unable to authenticate user in Oracle Internet Directory.
Action: Check user name and password to see if they are correct.
Cause: Unable to get next message ID from database.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert envelope information into database.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert recipient information into database.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert the message into a queue.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert message into database.
Action: Check the OCI error and ORACLE error.
Cause: Message may be in a loop by checking the Received: headers.
Possible causes: Loop in address rewriting rules; Auto-forward between addresses;.forward set up by UNIX mail senders.
Action: Check the rewriting rules and auto-forward setup and notify the sender.
Cause: Unable to read from client.
Action: Check network connections.
Cause: DNS server failed to verify that the IP address of the SMTP client is correct.
Cause: DNS server failed to verify that the host is a valid internet host.
Cause: The sender is either in the list of rejected senders or rejected domains.
Cause: This could be due to either relay is not allowed for the non-local recipient's domain OR the non-local recipient is in the list of rejected recipients.
Cause: This could be due to OCI errors.
Cause: This could be due to OCI errors.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_MESSAGE_API is loaded.
Cause: This could be due to OCI errors.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_MESSAGE_API is loaded.
The following is a list of housekeeping error messages:
Cause: An RDBMS error prevented house keeper from successfully performing expiration.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing pruning.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing pruning.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing collection.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing tertiary storage.
Action: Correct the generic RDBMS error and try running house keeper again.
The following is a list of list server error messages:
Cause: The cause for this error is available in the error message itself.
Action: Look at the oerr error for the error specified in the error message.
Cause: The Oracle Internet Directory server is down or has stopped responding or is listening on a different port.
Action: Restart the Oracle Internet Directory server if it is not running. Otherwise, restart the list server and specify the correct host name and port number of the Oracle Internet Directory server.
Cause: Either the database or the Oracle Internet Directory server is not running or has stopped responding.
Action: Restart the database and Oracle Internet Directory server. If they are running, then restart the list server.
Cause: An Oracle Internet Directory error occurred while trying to process a command for the user.
Action: Check if the user entry on the Oracle Internet Directory server is still valid.
The following is a list of Thin Client error messages:
Cause: WebMail was unable to add the attachments.
Action: Try again.
Cause: The user did not specific a folder name.
Action: Enter a folder name.
Cause: WebMail was unable to create the folder.
Action: Try again.
Cause: The user specified a folder name that is being used by another folder.
Action: Name the folder with a new name or put the folder in a different location.
Cause: WebMail could not create a new message object.
Action: Try creating a message again.
Cause: User did not specify a valid e-mail address in the To field.
Action: Try again and specify a valid e-mail address.
Cause: WebMail could not create a new message object.
Action: Try creating a message again.
Cause: WebMail experienced a problem when removing the attachment.
Action: Contact your system administrator.
Cause: WebMail attachment indices are misaligned.
Action: Recreate the message.
Cause: The user did not select messages for deletion.
Action: Select the message for deletion.
Cause: The message does not exist.
Action: Contact your system administrator.
Cause: This is a problem with the voice mail messages in the folder.
Action: Contact your system administrator.
Cause: The user did not select a message before selecting Forward.
Action: Select a message before selecting Forward.
Cause: Multiple messages were selected for forwarding.
Action: Select one message at a time for forwarding.
Cause: The message selected could not be forwarded.
Action: Try selecting another message, if that does not work, contact your system administrator.
Cause: The selected message could not be processed for forwarding.
Action: Try again or contact your system administrator.
Cause: The destination folder selected does not exist.
Action: Select another destination folder.
Cause: The user did not select a message before selecting Move.
Action: Select a message before selecting Move.
Cause: WebMail could not process the move request.
Action: Try again or contact your system administrator.
Cause: No messages exist before of after the current message.
Action: Try another folder.
Cause: WebMail could not open the next message.
Action: Try again or contact your system administrator.
Cause: No messages exist before of after the current message.
Action: Try another folder.
Cause: WebMail could not open the previous message.
Action: Try again or contact your system administrator.
Cause: The folder is not accessible.
Action: Check the shared permission or contact your system administrator.
Cause: There is no such folder in the account.
Action: Contact your system administrator.
Cause: WebMail experienced problems opening the folder.
Action: Contact your system administrator.
Cause: Possibly a network problem.
Action: Contact your system administrator.
Cause: Internal error.
Action: Contact your system administrator.
Cause: The message may have been deleted, but the browser is looking a cached or old pages.
Action: Refresh the message list and try again.
Cause: The user did not check any messages before selecting Reply.
Action: Select a message before selecting Reply.
Cause: The user selected multiple messages for reply.
Action: Select only one message at a time.
Cause: WebMail could not process the message for reply.
Action: Try again or contact your system administrator.
Cause: Internal error
Action: Contact your system administrator
Cause: Internal error
Action: Contact your system administrator.
Cause: The user did not select a folder in the folder list before selecting Edit.
Action: Select a folder from the folder list.
Cause: The folder selected is not available.
Action: Verify that the folder exists, or contact you system administrator.
Cause: Internal Error
Action: Contact your system administrator.
Cause: The user tried to rename the inbox.
Action: None, the inbox cannot be renamed.
Cause: The user did not specify a name for the folder.
Action: Specify a name for the folder.
Cause: Internal error
Action: Contact your stem administrator.
Cause: Internal error
Action: Contact your stem administrator.
Cause: Internal error
Action: Contact your stem administrator.
Cause: Internal error
Action: Contact your stem administrator.
Cause: The session has timed out.
Action: Contact your stem administrator.