Oracle Error Messages: 11/20/11

AMD-00134: measure #string: RDBMS measure column name not specified

AMD-00134: measure #string: RDBMS measure column name not specified

Cause: RDBMS measure column name for this measure was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing RDBMS measure column name.

AMD-00133: measure #string: analytic workspace measure name not specified

AMD-00133: measure #string: analytic workspace measure name not specified

Cause: Analytic workspace measure name for this measure was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing analytic workspace measure name.

AMD-00132: dimension #string: RDBMS GID column data type not specified

AMD-00132: dimension #string: RDBMS GID column data type not specified

Cause: RDBMS dimension column data type for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing RDBMS dimension column data type.

AMD-00131: dimension #string: RDBMS parent column data type not specified

AMD-00131: dimension #string: RDBMS parent column data type not specified

Cause: RDBMS dimension column data type for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing RDBMS dimension column data type.

AMD-00130: dimension #string: RDBMS dimension column data type not specified

AMD-00130: dimension #string: RDBMS dimension column data type not specified

Cause: RDBMS dimension column data type for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing RDBMS dimension column data type.

AMD-00129: dimension #string: RDBMS GID column not specified

AMD-00129: dimension #string: RDBMS GID column not specified

Cause: RDBMS GID column for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing RDBMS GID column.

AMD-00128: dimension #string: RDBMS parent column not specified

AMD-00128: dimension #string: RDBMS parent column not specified

Cause: RDBMS parent column for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing RDBMS parent column.

AMD-00127: dimension #string: RDBMS dimension column not specified

AMD-00127: dimension #string: RDBMS dimension column not specified

Cause: RDBMS dimension column for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing RDBMS dimension column.

AMD-00126: dimension #string: analytic workspace column level relation not specified

AMD-00126: dimension #string: analytic workspace column level relation not specified

Cause: Analytic workspace column level relation for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing analytic workspace column level dimension.

AMD-00125: dimension #string: analytic workspace column level dimension not specified

AMD-00125: dimension #string: analytic workspace column level dimension not specified

Cause: Analytic workspace column level dimension for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing analytic workspace column level dimension.

AMD-00124: dimension #string: analytic workspace GID variable not specified

AMD-00124: dimension #string: analytic workspace GID variable not specified

Cause: Analytic workspace GID variable for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing Analytic Workspace GID variable.

AMD-00123: dimension #string: analytic workspace hierarchy dimension value not specified

AMD-00123: dimension #string: analytic workspace hierarchy dimension value not specified

Cause: Hierarchy dimension value for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing hierarchy dimension value.

AMD-00122: dimension #string: analytic workspace hierarchy dimension not specified

AMD-00122: dimension #string: analytic workspace hierarchy dimension not specified

Cause: Hierarchy dimension for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing hierarchy dimension.

AMD-00121: dimension #string: analytic workspace hierarchy not specified

AMD-00121: dimension #string: analytic workspace hierarchy not specified

Cause: Hierarchy for this dimension was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing hierarchy.

AMD-00120: dimension #string: analytic workspace dimension name not specified

AMD-00120: dimension #string: analytic workspace dimension name not specified

Cause: Dimension name was not specified in either the input text file or the input string.

Action: Modify the input text file or the input string to include the missing dimension name.

AMD-00119: analytic workspace dimensions not specified in input

AMD-00119: analytic workspace dimensions not specified in input

Cause: Either the input text file or the input string did not specify an analytic workspace dimension.

Action: Add one or more dimensions to the input text file or the input string. At least one dimension is required.

AMD-00118: output file string already exists

AMD-00118: output file string already exists

Cause: The output file already exists in the specified location.

Action: Delete or rename the file, then retry.

PLS-00706: Exception string cannot be used as prefix of a selected component

PLS-00706: Exception string cannot be used as prefix of a selected component

Cause: An exception name was mistakenly used to qualify a reference to a component. For example, when dot notation was used to specify fields within a record, an exception name might have been coded instead of the record name.

Action: Rewrite the component reference using a valid prefix (for example, the name of a package, record, or schema).

PLS-00705: exception string used in expression requiring return type

PLS-00705: exception string used in expression requiring return type

Cause: An exception was referred to in an expression. Exceptions have names but not values and therefore cannot contribute values to an expression. For example, the following RETURN statement is illegal: FUNCTION credit_limit (cust_no INTEGER) RETURN NUMBER IS limit NUMBER; over_limit EXCEPTION; ... BEGIN ... RETURN over_limit; -- illegal END;

Action: Check the spelling of the identifiers in the expression, then rewrite the expression so that it does not refer to an exception.

PLS-00704: string must be declared as an exception

PLS-00704: string must be declared as an exception

Cause: The exception_name parameter passed to an EXCEPTION_INIT pragma is misspelled or does not refer to a legally declared exception. Or, the pragma is misplaced; it must appear in the same declarative section, somewhere after the exception declaration.

Action: Check the spelling of the exception_name parameter. Then, check the exception declaration, making sure the exception name and the keyword EXCEPTION are spelled correctly. Also make sure the pragma appears in the same declarative section somewhere after the exception declaration.

PLS-00703: multiple instances of named argument in list

PLS-00703: multiple instances of named argument in list

Cause: Two or more actual parameters in a subprogram call refer to the same formal parameter.

Action: Remove the duplicate actual parameter.

PLS-00702: second argument to PRAGMA EXCEPTION_INIT must be a numeric literal

PLS-00702: second argument to PRAGMA EXCEPTION_INIT must be a numeric literal

Cause: The second argument passed to an EXCEPTION_INIT pragma was something other than a numeric literal (a variable, for example). The second argument must be a numeric literal in the range -9999 .. -1 (excluding -100) for Oracle errors or in the range -20000 .. -20999 for user-defined errors.

Action: Replace the second argument with a valid error number.

PLS-00701: illegal ORACLE error number string for PRAGMA EXCEPTION_INIT

PLS-00701: illegal ORACLE error number string for PRAGMA EXCEPTION_INIT

Cause: The error number passed to an EXCEPTION_INIT pragma was out of range. The error number must be in the range -9999 .. -1 (excluding -100) for Oracle errors or in the range -20000 .. -20999 for user-defined errors.

Action: Use a valid error number.

PLS-00700: PRAGMA EXCEPTION_INIT of string must follow declaration of its exception in the same declarative part

PLS-00700: PRAGMA EXCEPTION_INIT of string must follow declaration of its exception in the same declarative part

Cause: An EXCEPTION_INIT pragma was not declared in the same block as its exception. They must be declared in the proper order in the same block, with the pragma declaration following the exception declaration.

Action: Place the EXCEPTION_INIT pragma directly after the exception declaration referenced by the pragma.

PLS-00670: sort columns must be simple column names

PLS-00670: sort columns must be simple column names

Cause: An attempt was made to specify an expression as a sort column in a PARTITION BY, CLUSTER BY or ORDER BY clause. Only simple column names are permitted.

Action: Specify a simple column name.

PLS-00669: Type of expression should be a valid collection variable

PLS-00669: Type of expression should be a valid collection variable

Cause: An attempt was made to specify expression after INDICES OF or VALUES OF clause that is not a collection variable.

Action: Change the index collection expression type to a valid collection variable.

PLS-00668: Type of expression should be a collection type

PLS-00668: Type of expression should be a collection type

Cause: An attempt was made to specify expression after INDICES OF or VALUES OF clause whose type is not a collection type.

Action: Change the index collection expression type to a valid collection type.

PLS-00667: Element type of associative array should be pls_integer or binary_ integer

PLS-00667: Element type of associative array should be pls_integer or binary_ integer

Cause: An attempt was made to specify index collection whos element type was not one of pls_integer or binary_integer.

Action: Change the index collection variable type to associative array whose element type is pls_integer or binary_integer.

PLS-00666: Only index by binary_integer or pls_integer associative arrays allowed here

PLS-00666: Only index by binary_integer or pls_integer associative arrays allowed here

Cause: An attempt was made to specify index collection that was not indexed by binary_integer or pls_integer.

Action: Change the index collection variable type to associative array that is indexed by binary_integer or pls_integer.

PLS-00665: ORDER BY and CLUSTER BY clauses require a PARTITION BY clause

PLS-00665: ORDER BY and CLUSTER BY clauses require a PARTITION BY clause

Cause: An attempt was made to specify an ORDER BY or CLUSTER BY clause without also specifying a PARTITION BY clause.

Action: Add a PARTITION BY clause, or remove the ORDER BY or CLUSTER BY clause.

PLS-00664: Both ORDER BY and CLUSTER BY can not be specified for the same table function

PLS-00664: Both ORDER BY and CLUSTER BY can not be specified for the same table function

Cause: An attempt was made to specify both ORDER BY and CLUSTER BY for the same table function.

Action: specify either ORDER BY or CLUSTER BY for a table function, but not both.

PLS-00663: the NEW keyword is not allowed in this context

PLS-00663: the NEW keyword is not allowed in this context

Cause: The NEW keyword is not followed by an call to a constructor method.

Action: Remove the NEW keyword, or make sure the expression following it is a constructor call.

PLS-00662: Non-external object types containing external mapped attributes are not allowed

PLS-00662: Non-external object types containing external mapped attributes are not allowed

Cause: An attempt was made to create a non-external object, whoose attributes are mapped externally.

Action: Create the object as an external object.

PLS-00661: RETURN statement in a CONSTRUCTOR cannot include an expression

PLS-00661: RETURN statement in a CONSTRUCTOR cannot include an expression

Cause: An attempt was made to include an expression in the RETURN statement of a CONSTRUCTOR body.

Action: Remove the expression from the RETURN statement.

PLS-00660: SELF parameter of constructor method must be IN OUT

PLS-00660: SELF parameter of constructor method must be IN OUT

Cause: The mode of the SELF parameter of the constructor was not IN OUT.

Action: Change the mode of the SELF parameter to be IN OUT.

PLS-00659: constructor method must return SELF AS RESULT

PLS-00659: constructor method must return SELF AS RESULT

Cause: The return clause of the constructor method did not specify SELF AS RESULT.

Action: Change the return clause to include RETURN SELF AS RESULT.

O2I-00101: Invalid value for the USERID parameter

O2I-00101: Invalid value for the USERID parameter

Cause: The value supplied for the USERID parameter is not a legal lamp;lt;lamp;nbsp;usernamelamp;gt; or lamp;lt;lamp;nbsp;passwordlamp;gt;(lamp;lt;lamp;nbsp;databasenamelamp;gt;( string.

Action: Set the USERID option to the correct lamp;lt;lamp;nbsp;usernamelamp;gt; or lamp;lt;lamp;nbsp;passwordlamp;gt; or lamp;lt;lamp;nbsp;usernamelamp;gt; or lamp;lt;lamp;nbsp;passwordlamp;gt;lamp;lt;lamp;nbsp;database namelamp;gt; combination to use when connecting to the database. If you have an OPS$ account, you may instead omit the USERID option, in which case OTT will attempt to connect to the database using the userid OPS$lamp;lt;lamp;nbsp;usernamelamp;gt;. The USERID option may be specified on the command line or in a CONFIG file.

O2F-00341: An error occurred for which no message is available

O2F-00341: An error occurred for which no message is available

Cause: The cause of this error was not reported.

Action: Contact ORACLE customer support.

O2F-00340: Name was null

O2F-00340: Name was null

Cause: A name had a length of 0 characters.

Action: This error should never be reported to the user. Contact ORACLE customer support.

O2F-00339: CODE option has an illegal value

O2F-00339: CODE option has an illegal value

Cause: The value given for the CODE option in the INTYPE file is not legal.

Action: Change the value given for the CODE option to one of the following legal values: C, ANSI_C, KR_C, JAVA, NATIVE_JAVA, ORACLE_JAVA.

O2F-00338: Illegal or missing package name

O2F-00338: Illegal or missing package name

Cause: A legal Java package name was expected following IN or PACKAGE or IN PACKAGE, but was not seen.

Action: Use a legal Java package name.

O2F-00337: Schema not found, or no types found in schema

O2F-00337: Schema not found, or no types found in schema

Cause: A request was made to generate declarations for all the types in a database schema. Either the schema was not found, no user-declared types were found in the schema, or unable to connect to Oracle.

Action: Ensure that a login or password string was specified for OTT and that the Oracle database can be accessed with it. Ensure that the USER_TYPES table contains at least one row.

O2F-00336: Error reported by subsystem:

O2F-00336: Error reported by subsystem:

Cause: A request was made to generate declarations for all the types in a database schema. An error occurred in a subsystem when accessing the database.

Action: Examine the error message reported by the sybsystem to determine its cause. List the types to be processed in an INTYPE file.

O2F-00335: Internal error in O2F component of OTT

O2F-00335: Internal error in O2F component of OTT

Cause: A request was made that all types in the database schema are to database.

Action: List the types to be processed in an INTYPE file. Contact ORACLE customer support.

O2F-00334: A user-defined type is listed more than once in the INTYPE file

O2F-00334: A user-defined type is listed more than once in the INTYPE file

Cause: The same name of a user-defined type appears in more than one type specification. The duplicate specifications of the type name will be ignored.

Action: Put all of the information about the type, including all type name and attribute name translations, in a single TYPE specification, and eliminate the duplicate TYPE specifications.

O2F-00333: An unexpected token appeared where a keyword was expected in the INTYPE file

O2F-00333: An unexpected token appeared where a keyword was expected in the INTYPE file

Cause: A keyword such as TYPE was expected in the INTYPE file, but an incorrect or misspelled keyword was seen.

Action: Verify that your TYPE specification obeys the syntax described in your documentation. Verify that your keyword is spelled correctly.

O2F-00332: A database link may not appear in the name of a user-defined type

O2F-00332: A database link may not appear in the name of a user-defined type

Cause: A database link was seen in the name of a user-defined type. This feature is not yet supported.

Action: Declare the user-defined type in the database to which OTT connects.

O2F-00331: A syntactically illegal name was seen in the INTYPE file

O2F-00331: A syntactically illegal name was seen in the INTYPE file

Cause: A syntax error occurred in a name used in the INTYPE file.

Action: If the name is quoted, make sure that the quotes are at the beginning and at the end of the name. If a period (which separates a schema name from a type name) appears, make sure that the schema name and the type name are both present.

O2F-00330: Name exceeds 265 bytes in length

O2F-00330: Name exceeds 265 bytes in length

Cause: A name seen in the INTYPE file exceeds 265 bytes in length.

Action: Choose a shorter name.

O2F-00329: Type or option specification expected

O2F-00329: Type or option specification expected

Cause: A type or option specification was expected in the INTYPE file, but was not seen.

Action: Check the INTYPE file for syntax errors. Supply a type or option specification. A type specification begins with the word TYPE. An option specification begins with the word CASE, INITFILE, or INITFUNC.

O2F-00328: Illegal INITFUNC name

O2F-00328: Illegal INITFUNC name

Cause: The function name given for the INITFUNC option in the INTYPE file is not a legal C or C++ identifier.

Action: Specify the name of the INITFUNC function as a legal C or C++ identifier. This name can be given in the INTYPE file, given on the command line, or derived from the INITFILE name.

O2F-00327: CASE option has an illegal value

O2F-00327: CASE option has an illegal value

Cause: The value given for the CASE option in the INTYPE file is not legal.

Action: Change the value given for the CASE option to one of the following legal values: SAME, LOWER, UPPER, or OPPOSITE.

O2F-00326: Some characters in this name were not legal identifier characters

O2F-00326: Some characters in this name were not legal identifier characters

Cause: One or more characters in the name of a database entity could not be translated to a character that may appear in a C or C++ identifier, such as a letter, an underscore, or a digit. The characters that could not be translated were replaced with underscores.

Action: Make sure that the name is spelled correctly, and that it is terminated by a blank, the end of a line, or an equals sign ( = ). You may use the translated name with added underscores, or you may specify an explicit translation for the name in the INTYPE file.

O2F-00325: None of the characters in a name were legal identifier characters

O2F-00325: None of the characters in a name were legal identifier characters

Cause: None of the characters in the name of a database entity could be translated to a character that may begin a C or C++ identifier, such as a letter or an underscore.

Action: Specify an explicit translation for the name in the INTYPE file.

O2F-00324: Unable to convert from the database character set to the compiler character set

O2F-00324: Unable to convert from the database character set to the compiler character set

Cause: The name of a type, attribute, or method cannot be converted from the client character set in effect when OTT was invoked to the compiler character set (typically ASCII or EBCDIC).

Action: A name is translated first from the database character set to the client character set, and then from the client character set to the compiler character set. The client character set is specified in a platform-dependent manner (On UNIX platforms, the client character set is specified by setting the NLS_LANG environment variable). Use a client character set that can be translated to the compiler character set. The compiler character set itself is one such character set. Specify synonyms in the INTYPE file for any names of database objects that cannot be successfully translated to the client character set.