Oracle Database Errors or Warnings from Error ORA-06571 to ORA-06580

SQLServerF1

 

ORA-06571: Function string does not guarantee not to update database
Cause: There are two possible causes for this message:
* A SQL statement references a packaged, PL/SQL function that does not contain a pragma that prevents the database from being updated.
* A SQL statement references a stand-alone, PL/SQL function that contains an instruction to update the database.
Action: If the referenced function is a packaged, PL/SQL function: Recreate the PL/SQL function with the required pragma; be certain to include the ‘Write No Database State’ (WNDS) argument in the argument list of the pragma. If the referenced function is a stand-alone, PL/SQL function: Do not use the function.
ORA-06572: Function string has out arguments
Cause: A SQL statement references either a packaged, or a stand-alone, PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter.
Action: Recreate the PL/SQL function without the OUT parameter in the argument list.
ORA-06573: Function string modifies package state, cannot be used here
Cause: There are two possible causes for this message:
* A SQL statement references a packaged, PL/SQL function that does not contain a pragma containing the ‘Write no Package State’ (WNPS).
* A SQL statement references a stand-alone, PL/SQL function that modifies a package state. A stand-alone, PL/SQL function referenced by a SQL statement cannot modify a package state.
Action: If the function is a packaged, PL/SQL function: Recreate the function and include a pragma containing the ‘Write no Package State’ (WNPS). If the function is a stand-alone, PL/SQL function: Delete the function from the SQL statement.

ORA-06574: Function string references package state, cannot execute remotely
Cause: There are two possible causes for this message:
* A remote, packaged function or a remote-mapped, local, packaged function that does not contain a pragma with the ‘Write no Package State’ (WNPS) and ‘Read no Package State’ (RNPS) arguments references a package state.
* A remote, stand-alone function or a remote-mapped, local, stand-alone function contains a reference to a package state (reads or writes a package variable). Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state.
Action: If the function is a packaged function: Recreate the function and include a pragma containing the ‘Write no Package State’ (WNPS) and ‘Read no Package State’ (RNPS) arguments. If the function is a stand-alone function: Do not call the function.
ORA-06575: Package or function string is in an invalid state
Cause: A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors.
Action: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object.
ORA-06576: not a valid function or procedure name
Cause: Could not find a function (if an INTO clause was present) or a procedure (if the statement did not have an INTO clause) to call.
Action: Change the statement to invoke a function or procedure

ORA-06577: output parameter not a bind variable
Cause: The argument corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement must be a bind variable.
Action: Change the argument to a bind variable
ORA-06578: output parameter cannot be a duplicate bind
Cause: The bind variable corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement cannot be a duplicate bind variable.
Action: Change the bind variable to be unique
ORA-06579: Bind variable not big enough to hold the output value
Cause: The bind variable specified by the user is not large enough to hold the output returned by the function or a procedure.
Action: Specify a bind variable of larger size.
ORA-06580: Hash Join ran out of memory while keeping large rows in memory
Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.
Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increaed.

Above are list of Oracle Database Errors or Warnings from Error ORA-06571 to ORA-06580 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *