PLS-01505: ALTER is non-ANSI
Cause: ALTER is non-ANSI.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
Category Archives: Database
PLS-01504: Use of AS phase in CREATE TABLE statement is non_ANSI
PLS-01504: Use of AS phase in CREATE TABLE statement is non_ANSI
Cause: CREATE TABLE allows only the definition of the structure of a table. Use of AS phase in CREATE TABLE statement is non-ANSI.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01503: The expression in a SET clause must not include a set function
PLS-01503: The expression in a SET clause must not include a set function
Cause: The expression in a SET clause must not include a set function.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01502: Constraint name and constraint status are non-ANSI
PLS-01502: Constraint name and constraint status are non-ANSI
Cause: Constraint name and constraint status are non-ANSI.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01501: Options in CREATE TABLE statement is non-ANSI
PLS-01501: Options in CREATE TABLE statement is non-ANSI
Cause: CREATE TABLE allows only the definition of the structure of a table. None of the .SPACE__name. .PCTFREE__numeric_literal. .cluster. is ANSI.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01500: Unions are not allowed in the definition of a view
PLS-01500: Unions are not allowed in the definition of a view
Cause: Unions are not allowed in the definition of a view.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01474: Use of ANY is non_ANSI
PLS-01474: Use of ANY is non_ANSI
Cause: Due to the combining of comparison_predicate and quantified_predicate, we may have something like sim_expr = ANY_ sim_expr, which is nonetheless accepted by kernel.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01473: Use <> instead of != or ~=
PLS-01473: Use <> instead of != or ~=
Cause: Use <> instead of != or ~=.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01472: In a set_function_specification, if DISTINCT is present, the expression must be a column_specification
PLS-01472: In a set_function_specification, if DISTINCT is present, the expression must be a column_specification
Cause: In a set_function_specification, if DISTINCT is present, the expression must be a column_specification.
Action: Refer to ANSI document ANSI X3.135-1992 for details.
PLS-01471: The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr)
PLS-01471: The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr)
Cause: The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr).
Action: Refer to ANSI document ANSI X3.135-1992 for details.