Oracle Error Messages: 12/07/11

PLS-00512: Implementation Restriction: string : Cannot directly access remote package variable or cursor

PLS-00512: Implementation Restriction: string : Cannot directly access remote package variable or cursor

Cause: An attempt was made to reference a remote packaged variable or cursor. This is not allowed. Instead, add to the remote package a function that returns the value of the variable or cursor.

Action: Remove the illegal reference.

PLS-00511: a record may not contain a PL or SQL table of records

PLS-00511: a record may not contain a PL or SQL table of records

Cause: n a RECORD definition, one of the fields was declared as a PL or SQL table of records. This is not allowed. A record can be the component of another record (that is, records can be nested), but a PL or SQL table of records cannot be the component of a record.

Action: Remove the field declaration, or revise it to specify a simple record type.

PLS-00510: Float cannot have scale

PLS-00510: Float cannot have scale

Cause: When a FLOAT variable was declared, its precision and scale were specified, as shown in the following example: DECLARE Salary FLOAT(7,2); However, a scale for FLOAT variables cannot be specified; only a precision can be specified, as in salary FLOAT(7);

Action: Remove the scale specifier from the declaration, or declare a NUMBER variable instead.

PLS-00509: Implementation Restriction : Pass a returned record to a temporary identifier before selecting a field

PLS-00509: Implementation Restriction : Pass a returned record to a temporary identifier before selecting a field

Cause: Illegal syntax was used to call a parameter-less function that returns a record or a PL or SQL table of records. When calling a function that takes parameters and returns a record, you use the following syntax to reference fields in the record: function_name(parameters).field_name However, you cannot use the syntax above to call a parameter-less function because PL or SQL does not allow empty parameter lists. That is, the following syntax is illegal: function_name().field_name -- illegal; empty parameter list You cannot just drop the empty parameter list because the following syntax is also illegal: function_name.field_name --illegal; no parameter list.

Action: Declare a local record or PL or SQL table of records to which you can assign the function result, then reference its fields directly.

PLS-00508: The expression in a RETURN statement cannot be a type

PLS-00508: The expression in a RETURN statement cannot be a type

Cause: A datatype specifier was used instead of an expression in the RETURN statement of a user-defined function, as shown in the example below. Do not confuse the RETURN statement, which sets the function identifier to the result value, with the RETURN clause, which specifies the datatype of the result value. FUNCTION credit-rating (acct_no NUMBER) RETURN BOOLEAN IS BEGIN ... RETURN NUMBER; -- should be an expression END;

Action: Replace the datatype specifier in the RETURN statement with an appropriate expression.

PLS-00507: a PLSQL Table may not contain a table or a record with composite fields

PLS-00507: a PLSQL Table may not contain a table or a record with composite fields

Cause: In a TABLE type definition, a nested record type was specified as the element type. This is not allowed. All fields in the record must be scalars.

Action: Remove the TABLE type definition, or replace the nested record type with a simple record type.

PLS-00506: User Defined Constrained Subtypes are disallowed

PLS-00506: User Defined Constrained Subtypes are disallowed

Cause: An attempt was made to define a constrained subtype, but only unconstrained subtypes are allowed in this release of PL or SQL. For example, the following type definition is illegal: SUBTYPE Acronym IS VARCHAR2(5); --illegal

Action: Remove the illegal type constraint.

PLS-00505: User Defined Types may only be defined as PLSQL Tables or Records

PLS-00505: User Defined Types may only be defined as PLSQL Tables or Records

Cause: An attempt was made to define a type other than TABLE or RECORD, but these are the only user- defined types allowed in this release of PL or SQL. For example, the following type definition is illegal: TYPE Byte IS INTEGER(2); -- illegal

Action: Remove the type definition, or revise it to specify a TABLE or RECORD type.

PLS-00504: type string_BASE may not be used outside of package STANDARD

PLS-00504: type string_BASE may not be used outside of package STANDARD

Cause: In a declaration, the datatype NUMBER_BASE (for example) was mistakenly specified. The datatypes CHAR_BASE, DATE_BASE, MLSLABEL_ BASE, and NUMBER_BASE are for internal use only.

Action: Specify (for example) the datatype NUMBER instead of NUMBER_BASE.

PLS-00503: RETURN lamp;lt;lamp;nbsp;valuelamp;gt; statement required for this return from function

PLS-00503: RETURN lamp;lt;lamp;nbsp;valuelamp;gt; statement required for this return from function

Cause: In a function body, a RETURN statement was used that contains no expression. In procedures, a RETURN statement contains no expression because the statement simply returns control to the caller. However, in functions, a RETURN statement must contain an expression because its value is assigned to the function identifier.

Action: Add an expression to the RETURN statement.

TNS-00218: Current Bytes or Sec. : number

TNS-00218: Current Bytes or Sec. : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00217: Total Bytes of Data : number

TNS-00217: Total Bytes of Data : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00216: Total Failed Connections : number

TNS-00216: Total Failed Connections : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00215: Total Successful Connections : number

TNS-00215: Total Successful Connections : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00214: Total Connections in Use : number

TNS-00214: Total Connections in Use : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00213: Available Connections : number

TNS-00213: Available Connections : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00212: Total Pumps Started : number

TNS-00212: Total Pumps Started : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00211: Total Active Pumps : number

TNS-00211: Total Active Pumps : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00210: Total Pumps Available : number

TNS-00210: Total Pumps Available : number

Cause: Part of status request for Connection Manager.

Action: None

TNS-00209: Tracing : string

TNS-00209: Tracing : string

Cause: Part of status request Interchange.

Action: None

TNS-00208: Logging : string

TNS-00208: Logging : string

Cause: Part of status request.

Action: None

TNS-00207: Uptime : number days number hr. number min. number sec

TNS-00207: Uptime : number days number hr. number min. number sec

Cause: Part of status request.

Action: None

TNS-00206: Status Information for Interchange string:

TNS-00206: Status Information for Interchange string:

Cause: Message sent back by Interchange as header for status request.

Action: None

TNS-00205: Turning off tracing in intlsnr

TNS-00205: Turning off tracing in intlsnr

Cause: Internal message - Turned off tracing in the Interchange listener.

Action: None

TNS-00204: Started tracing in intlsnr

TNS-00204: Started tracing in intlsnr

Cause: Internal message- Successfully started tracing information.

Action: None.

TNS-00203: Unable to start tracing in intlsnr

TNS-00203: Unable to start tracing in intlsnr

Cause: Failure in setting up tracing for Interchange listener.

Action: Check file permissions in Network trace directory also check to make sure that if trace file names and directories are specified in INTCHG.ORA, they are correct.

TNS-00202: Failure in redirecting call : Original to string Redirect to string

TNS-00202: Failure in redirecting call : Original to string Redirect to string

Cause: Internal - error could not redirect call to a pump or other Interchange listener. The cause may be insufficient network or machine resources.

Action: Add resources or close some running applications in order to free up resources. If error persists, call Oracle Customer Support.

TNS-00201: Unable to read answer connection data :string:

TNS-00201: Unable to read answer connection data :string:

Cause: Improperly formed connect data sent to the Interchange listener.

Action: If problem persists, check the application using the Interchange (it may be closing down or crashing). Call Oracle Customer Support if the problem cannot be located.

TNS-00200: Unable to do nsanswer on context result=string

TNS-00200: Unable to do nsanswer on context result=string

Cause: Requester of service may have aborted or options negotiation failed.

Action: Try making the connection again. If the problem persists call Oracle Customer Support.

TNS-00147: Failed to start a pre-spawned pump.

TNS-00147: Failed to start a pre-spawned pump.

Cause: The Connection Manager was unable to start a pump during startup.

Action: Check all configuration parameters and assure that they are correct. Turn on tracing to determine the area that the failure ocurred in.

TNS-00146: Internal-- Retry data request withing pump.

TNS-00146: Internal-- Retry data request withing pump.

Cause: The data space provided in order to receive data from the pump is to small.

Action: Operation must be retried with a larger buffer.

TNS-00145: PUMPS value in INTCHG.ORA is too large.

TNS-00145: PUMPS value in INTCHG.ORA is too large.

Cause: The number of PUMPS specified in INTCHG.ORA is too large to be supported on this platform.

Action: Consult the Oracle operating system specific manual for the maximum value for the number of PUMPS.

TNS-00144: PUMP_CONNECTIONS value in INTCHG.ORA is too large.

TNS-00144: PUMP_CONNECTIONS value in INTCHG.ORA is too large.

Cause: The number of PUMP_CONNECTIONS specified in INTCHG.ORA is too large to be supported on this platform.

Action: Consult the Oracle operating system specific manual for the maximum value for the number of PUMP_CONNECTIONS.

TNS-00143: Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA

TNS-00143: Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA

Cause: PREFERRED_CMANAGERS entry in the TNSNAV.ORA used by the Connection Manager. There should only be a PREFERRED_NAVIGATORS entry in the TNSNAV.ORA on an Interchange.

Action: Remove the PREFERRED_CMANAGERS entry from TNSNAV.ORA and assure that either no PREFERRED_NAVIGATORS entry is present or that it is correct.

TNS-00142: Community mismatch in TNSNAV.ORA

TNS-00142: Community mismatch in TNSNAV.ORA

Cause: The communities in the LOCAL_COMMUNITIES entry in TNSNAV.ORA do not correspond with all the communities in the NAVIGATOR_ADDRESSES entry.

Action: Assure that all communities in the NAVIGATOR_ADDRESSES correspond to those in the LOCAL_COMMUNITIES component.

TNS-00141: Failed to get file stream information

TNS-00141: Failed to get file stream information

Cause: Error in the file stream package.

Action: None.

TNS-00140: Interchange specified was not found in network tables

TNS-00140: Interchange specified was not found in network tables

Cause: Could not find the Interchange specified in a control request.

Action: Check that the Interchange specified is indeed in TNSNET.ORA.

TNS-00139: Internal - Data passed from the Interchange listener is poorly formed

TNS-00139: Internal - Data passed from the Interchange listener is poorly formed

Cause: Internal error in Interchange.

Action: Check that you are using compatible components of the Interchange product, using the INTCTL VERSION command. If problem persists call Oracle Customer Support.

TNS-00138: Failed to find ORACLE executable directory

TNS-00138: Failed to find ORACLE executable directory

Cause: The ORACLE environment is not correctly set.

Action: Ensure that the ORACLE environment is correctly set and the error messages file is in the correct place.

TNS-00137: Failed to get TNS error message file entry

TNS-00137: Failed to get TNS error message file entry

Cause: No TNS error message file present.

Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.

TNS-00136: Did not register product or facility for TNS error message

TNS-00136: Did not register product or facility for TNS error message

Cause: Error message file error.

Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.

TNS-00135: Missing TNS error message file

TNS-00135: Missing TNS error message file

Cause: No error message file present.

Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.

TNS-00134: Missing COMMUNITY component in addresses for the Navigator in TNSNAV.ORA

TNS-00134: Missing COMMUNITY component in addresses for the Navigator in TNSNAV.ORA

Cause: The addresses specified for the Navigator have no COMMUNITY name.

Action: Ensure that all addresses in the NAVIGATOR_ADDRESSES field have a COMMUNITY entry in the TNSNAV.ORA file.