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