Oracle Internet File System Developer's Guide Release 1.1 A75172-04 |
|  |  | Index

# A
Error Messages

This appendix presents typical error messages you may encounter while developing your application. For each message, the cause of the error as well as actions you may take to correct the error condition are provided.

#####

IFS-10170 | Invalid name/credential.
Cause: | Incorrect Oracle iFS login and password were entered.
Possible Actions: | 1. Re-enter the correct login and password. 2. Confirm that a user exists in Oracle iFS with the specified name.
IFS-10200 | Unable to access object (insufficient privileges)
Cause: | User tried to access a PublicObject (such as a Document, Folder, etc.) that the user did not have permission to access.
Possible Actions: | 1. Have the owner change the permissions (ACL) to allow user to access the object. 2. If the permissions are set correctly so as to prohibit the user from accessing the object, no other action is applicable.
IFS-10406 | Invalid AttributeValue conversion ({0} to Java {1})
Cause: | This error generally occurs when writing directly against the Java API. The error is coercing an attribute value to an incorrect datatype. An example of an invalid conversion is coercing a DATE to a BOOLEAN. An example of a valid conversion is coercing an INTEGER to a STRING. One case worthy of a special mention is in converting from PUBLICOBJECT to PUBLICOBJECT. This will fail if the user does not have permission to access the PublicObject referenced in the AttributeValue. The parameters {0} and {1} will have the actual values that caused the error.
Possible Actions: | 1. Check the datatypes, and modify them to be compatible datatypes. 2. In the case of coercing to a PublicObject, check whether the user can access the PublicObject referenced in the AttributeValue.
IFS-10600 | Unable to construct library connection
Cause: | This error occurs when the Oracle iFS repository cannot connect to the database. Generally, this is caused by an invalid database username specified in the service properties file, or an invalid database password. It can also occur if the DatabaseUrl setting in the service properties file is invalid.
Possible Actions: | 1. Verify that the database username, password, and TNS names entry are set correctly, by using SQL*Plus or a similar tool to connect to the database. 2. Check to see if this exception encapsulates another exception that describes the cause more clearly.
IFS-10620 | Unable to construct connection pool
Cause: | This error generally occurs when database connections cannot be made. Typically, error 10633 causes this error to be thrown.
Possible Actions: | If error 10633 has caused this exception, verify that the database username, password, and TNS names entry are set correctly, by using SQL*Plus or similar tool to connect to the database.
IFS-10633 | Unable to create library connection
Cause: | This error generally occurs when database connections cannot be made. Typically, error 10600 causes this error to be thrown.
Possible Actions: | If error 10600 has caused this exception, verify that the database username, password, and TNS names entry are set correctly, by using SQL*Plus or a similar tool to connect to the database.
IFS-12200 | Invalid item name specified (<item name>).
Cause: | An attempt was made to look up an object by name in one of the Oracle iFS Collections, and no object by that name exists. This can occur when directly invoking the getItems() method on the Collection class, or indirectly by performing an operation that will access one of the Collections. An example of the latter case is when a ClassObject name is specified in an operation such as creating a new Document, and there is no ClassObject with the specified name.
Possible Actions: | Check the name specified, and re-enter a valid name.
IFS-12620 | Parser: syntax error (parameter)
Cause: | A syntactical error was detected by a parser while parsing a document stream being introduced into the Oracle iFS repository. The parameter identifies the token responsible for the syntax error. For example, the SimpleXmlParser will throw this exception when an unknown tag is encountered while parsing an XML file; the parameter is the unknown tag value.
Possible Actions: | Fix the document body, correcting the syntax error, and re-submit to Oracle iFS.
IFS-20000 | Unable to get repository parameter (parameter)
Cause: | This error typically occurs when trying to run Oracle iFS against a partially installed Oracle iFS instance or a very old Oracle iFS instance (e.g., older than 1.0.8.0.0). This is particularly true if the parameter listed is the string "SCHEMAVERSION".
Possible Actions: | Verify that the Oracle iFS instance on which this error occurs has been installed properly, and is version 1.0.8.0.0 or higher.
IFS-20001 | Unable to get schema version.
Cause: | This error is typically caused by error 20000, the inability to get the repository parameter named "SCHEMAVERSION". This generally occurs when trying to run Oracle iFS against a partially installed Oracle iFS instance or a very old Oracle iFS instance (e.g., older than 1.0.8.0.0).
Possible Actions: | Verify that the Oracle iFS instance on which this error occurs has been installed properly, and is version 1.0.8.0.0 or higher.
IFS-20010 | Failed to get PropertiesResourceBundler <parameter>
Cause: | This error occurs when attempting to start an Oracle iFS process by specifying a service properties file name that cannot be located by the Oracle iFS repository. The parameter specified in the error is the name of the specified service properties file. The specified service properties file must exist in the oracle.ifs.server.properties package descending from one of the directories included in the CLASSPATH setting for the process.
Possible Actions: | Check for the existence of a service properties file with the specified name reachable from the current CLASSPATH.
IFS-21008 | Login failure (2)
Cause: | An attempt to establish an Oracle iFS session has failed, usually because the specified credential (name/password combination) is invalid. In this case, this error encapsulates the error 10170; for all other (rare) authentication failures, error 10150 is encapsulated.
Possible Actions: | If the login failure is caused by invalid credential, re-enter the valid credential to establish an Oracle iFS session.
IFS-30002 | Unable to create new LibraryObject
Cause: | The creation of a new Oracle iFS object has failed. The actual cause of the failure is described in an exception encapsulated by this exception. For example, if a uniqueness constraint is violated when attempting to create a new object, the top-most exception will be 30002, and it will encapsulate exception 30010: "Attribute would not be unique (<attribute>)".
Possible Actions: | Investigate the cause of the object creation failure, take corrective action, and retry.
IFS-34611 | Error reserving version series
Cause: | An error has occurred in "checking out" a versioned PublicObject, e.g., reserving the VersionSeries object associated with a versioned PublicObject. The failure can be caused by number of conditions, listed below, and described in most cases by inspecting the encapsulated exception. For example, another user already has the VersionSeries reserved, the encapsulated exception will be 34602: "Operation not permitted, version series is reserved."
Possible Actions: | 1. Make sure the VersionSeries is not reserved or locked by another user. 2. Make sure that the Family is not locked by another user. 3. Make sure that the last version in the VersionSeries is not locked by another user. 4. Verify the current user has the permission "AddVersion" on the target VersionSeries.
IFS-46113 | No such Server (name)
Cause: | An attempt was made to look up an Oracle iFS Server by name, using one of the ServerManager interfaces, when no such server exists. This can occur if the name is improperly specified, or when a server that matches this name is no longer running.
Possible Actions: | 1. Re-check the active server list, using the ServerManager interfaces; e.g. by using the "list servers" command in the ServerManager commandline interface. 2. Check the ServerManager and/or protocol server logs to see if a server by the specified name has stopped unexpectantly.
IFS-46114 | Server name IfsProtocols is ambiguous; specify the server identifier:(<id>, <id>, ...)
Cause: | An attempt was made to look up an Oracle iFS Server by name in the ServerManager comandline interface, and more than one server exists with this name. The identifiers listed in the exception text are the unique server identifiers of the servers that have the specified name. These identifiers can be used in place of the server name to perform an operation on a server.
Possible Actions: | List the servers using the -i option in the ServerManager commandline interface. Then, re-submit the original server request by using the identifier instead of the server name.

| Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|  |  | Index