My Oracle Support Banner

TOP ARTICLES Errors PLS-907 ORA-6508 ORA-4068 ORA-4063 ORA-4065 (Doc ID 738034.1)

Last updated on JANUARY 29, 2022

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


The purpose of this article is to explain the reason of list of related errors and pointer to the top articles that address those errors, different reasons for the errors and how to solve it.

Most of those errors are solved by recompiling the objects referenced in the error. Start by running utlrp.sql, if the error still exist then manually recompile the objects in sequence based on their dependencies.

Note that while the notes below do not specifically reference PLS-907, the same information applies.


The errors that are covered here are:

Error: PLS-907
Text: cannot load library unit %s (referenced by %s)
Cause: PL/SQL is unable to find and load a library unit that was
previously available. This typically happens when you try to
load a unit which references another library unit that is
non-existent or invalid.
Action: Provide the needed library unit.

Error: ORA 4065
Text: not executed, altered or dropped %s
Cause: Attempt to execute a stored procedure that has
been altered or dropped thus making it not callable from the
calling procedure.
Action: Recompile its dependents.

Error: ORA 6508
Text: PL/SQL: could not find program unit being called
Cause: There should be more errors. See the other errors higher up the stack.
Action: Solve the errors higher up the stack.

Error: ORA 4068
Text: existing state of packages%s%s%s has been discarded
Cause: One of errors 4060 - 4067 when attempt to execute a stored
Action: Try again after proper re-initialization of any application's

Error: ORA 4063
Text: <name> has errors
Cause: An attempt was made to execute a stored procedure that has errors.
For stored procedures, the problem could be syntax or references to
other, non-existent procedures.
For views, the problem could be a reference in the view's defining
query to a non-existent table.
Action: Fix the errors and create referenced objects as necessary


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.