Oracle® Email Administrator's Guide Release 2 (9.0.4) Part Number B10720-01 |
|
|
View PDF |
This chapter explains how to interpret error messages and correct errors. It lists the error codes in numerical order, divided into the following groups:
Error messages may appear in any part of Oracle Email. Users may see them in the end-user interface. Administrators may see them in the administrative tools and process logs.
When a list of error messages, called an error stack, is displayed, 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. |
This section describes the IMAP and POP error messages. The notations 1 and 2, which appear in many cells in the "Action to Handle the Error," mean the following:
ES_FOLDER_API
has been loaded. "
Error Number and Message |
Cause of the Error |
Action to Handle the Error |
---|---|---|
101, 0, Login failed |
Invalid user name or password used for |
Check the user nameand password. Try again. |
102, 0, No of auth/login tries exceeded. Exiting |
Used all your allowed login attempts |
Check the user name and password; then retry in a new session. |
103, 0, User logged out |
IMAP/POP session ended either by |
Session end by |
104, 0, Authorization succeeded |
Successful login using authenticate command |
None |
105, 0, Authorization failed |
Unsuccessful login attempt using authenticate command |
Check the user credentials and try again. |
106, 0, Could not retrieve folder id for folder={sarg0}. Error#{narg0} |
Possibly a nonexistent folder name was used. |
Correct the folder name and try again. If the folder name is correct, check and resolve any other database errors in this error chain. |
107, 0, Failed to get header info for folder={sarg0} with fid={narg1}. Error#{narg0} |
Could be due to an OCI error |
Foot 1 (1). (2). Check and resolve any other database errors in this error chain. |
108, 0, Failed to update folder={sarg0} with fid={narg1}. Error#{narg0} |
Could be due to an OCI error |
(1). (2). Check and resolve any other database errors in this error chain. |
109, 0, Failed to connect to database {sarg1}. Error#{narg0} |
Server unable to create OCI connection pool. |
Make sure thedatabase is up and configured correctly in Oracle Internet Directory. |
110, 0, Connected to database {sarg1} |
Successful connections to the database |
None |
111, 0, Failed to get statement handle {narg1} with Error#{narg0}. |
Database related error |
Check for anOCI error in this error chain. |
112, 0, Autologout: idle {narg0} minutes. |
Your session was idle for too long |
Send noop or any other command before timeout. |
113, 0, Out of free Memory. Requested {narg0} bytes. |
No more free memory is available to the server. |
Reduce the load on the server by reducing any of following: threads, max. clients, OCI sessions, or Oracle Internet Directory connections. Make sure enough free memory is available for the server on your system. |
114,0, Module {sarg0}: nesting level too deep, no stats |
Internal error |
Contact customer support. |
117, 0, Failed to get body parts for messageID={narg0} |
Could be due to an OCI error |
(1). (2). Check and resolve any other database errors in this error chain. |
118, 0, Failed to get database session for db={sarg0}. Error#{narg0} |
No more free sessions are available in the OCI connection pool. |
This error may be temporary, 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. |
119, 0, Failed to insert subscribed folder={sarg0}. Error #{narg0} |
Database error. |
Check the OCI errors in this error chain. |
120, 0, Failed to rename folder={sarg0})to {sarg1}. Error#{narg0} |
Make sure that a folder with the old name exists and that the new name is not already in use or contains restricted characters. Check for any other database errors in this error chain. | |
121, 0, Failed to set SEEN flag for msgid={narg0} in fid={narg1}. Error#{narg2} |
Could be due to an OCI error |
(1). (2). Check and resolve any other database errors in this error chain. |
122, 0, Failed to get shell for msgid={narg0}. Error#{narg1} |
Could be due to an OCI error |
(1). (2). Check and resolve any other database errors in this error chain. |
123, 0, Failed to create hierarchical folders {sarg0}. Error#{narg0} |
Check the folder name you are trying to create. Also check for any OCI errors in this error chain. | |
124, 0, Failed to expunge {narg0} msgs from folder with fid={narg1}. Error#{narg2} |
Could be due to an OCI error |
(1). (2). Check and resolve any other database errors in this error chain. |
125, 0, Bad flags list |
Syntax error in the flag list for the Store command. |
Correct the syntax for theflag list. |
126, 0, Failed to get folder Id for folder={sarg0}. Error#{narg0} |
Make sure you are looking for the right folder and its name 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. | |
117, 0, Failed to create shared folder={sarg0}. Error#{narg0},{sarg1} |
Database error |
Check and resolve database errors in this chain. |
128, 0, Failed to delete shared folder={sarg0}. Error#{narg0},{sarg1} |
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. | |
129, 0, Failed to rename shared folder={sarg0} to {sarg1}. Error#{narg0},{sarg2} |
Make sure you are the owner of the shared folder, or retry with a different name. | |
130, 0, Failed to change ACI on shared folder={sarg0}. Error#{narg0},{sarg1} |
Database error |
Check the error logs for the database and Oracle Internet Directory. |
131, 0, Failed to determine if this folder or any child is shared.{sarg0}.Error#{narg0} |
Could be due to an OCI error |
(1). (2). Check and resolve any other database errors in this error chain. |
132, 0, Failed to determine Folder space usage for user={sarg0}. Error#{narg0} |
Could be due to an OCI error |
(1). (2). Check and resolve any other database errors in this error chain. |
133, 0, Bad message in Folder={narg0},mid={narg1},muid={narg2}. Null value for {sarg0} |
One of the required message attributes is missing in the database. |
(1). |
1 (1) means "Make sure all required packages have been loaded into the database correctly." (2) means "In particular, check whether ES_FOLDER_API has been loaded." |
This section describes the SMTP error messages.
This section describes the housekeeping error messages.
This section describes the list server error messages.
This section presents the NNTP error messages.
This section describes the WebMail error messages.
This section describes the virus scrubber error messages.