This topic describes the Procedure Builder error messages. The errors are listed in order by their error code number.
Note: For help on other error messages, see Finding error message help.
Cause:
The trigger body contains an invalid PL/SQL construct.
Action:
Correct the error in the PL/SQL construct before closing the editor.
Cause:
You invoked DEBUGSUSPEND within the body of a debug trigger, which is not allowed.
Action:
Remove the call to DEBUGSUSPEND from the body of the debug trigger.
Cause:
You attempted to advance PL/SQL execution with the STEP command, but there was no PL/SQL program unit whose execution was suspended at the time.
Action:
If you wish to use the STEP command, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
The trigger body contains an invalid PL/SQL construct.
Action:
Correct the error in the PL/SQL construct before closing the editor.
Cause:
You entered the ATTACH command to attach a library, but did not specify a library name.
Action:
Check the syntax of the ATTACH command.
Cause:
You entered the ATTACH command to attach a library residing in the file system, but the specified file name could not be found.
Action:
Check the spelling of the specified file name and re-enter the command.
Cause:
You entered the ATTACH command with the NAMESPACE keyword to attach a library to a namespace, but did not specify an existing namespace.
Action:
Re-enter the ATTACH command, specifying an existing namespace.
Cause:
You entered the ATTACH command with too many location options (BEFORE, AFTER, START, END).
Action:
Re-enter the ATTACH command, specifying a single location option.
Cause:
You entered the ATTACH command to attach a library residing in the database, but the specified name could not be found or there is no current database connection.
Action:
Check the spelling of the specified library name, verify the database connection, and re-enter the command.
Cause:
You entered the ATTACH command to attach a library without specifying a location, but the specified name could not be found in either the file system or the database.
Action:
Check the spelling of the specified library name, and re-enter the command.
Cause:
You entered the ATTACH command with the NAMESPACE keyword to attach a library to a namespace, but the specified namespace could not be found.
Action:
Check the spelling of the specified namespace. Re-enter the ATTACH command, specifying an existing namespace.
Cause:
You entered an invalid PL/SQL construct in the trigger body.
Action:
Fix the PL/SQL construct before closing the editor.
Cause:
You entered the CLOSE command to close a library, but did not specify a library name.
Action:
Check the syntax of the CLOSE command.
Cause:
You entered the CLOSE command to close a library, but did not specify a library that is currently open.
Action:
Re-enter the CLOSE command, specifying a library that is currently open.
Cause:
You entered the COMPILE command to compile one or more program units, or to compile all of the program units in one or more libraries. However, you did not provide any keywords and/or values in the command string.
Action:
Re-enter the COMPILE command, specifying the appropriate keywords and values.
Cause:
You entered the COMPILE command to compile a library that is not currently open. You cannot compile libraries that are not open.
Action:
If you wish to compile a library that is not open, open the library using OPEN, then re-enter the COMPILE command to compile the open library. Otherwise, re-enter COMPILE, specifying a library that is already open.
Cause:
You entered the CONNECT command to connect to a database, but specified an invalid connect string.
Action:
Check the spelling of the connect string or specify another one and re-enter the command.
Cause:
You entered the CREATE command to create a new library, but you did not provide any keywords and/or values in the command string.
Action:
Re-enter the CREATE command, specifying the appropriate keywords and values.
Cause:
You entered the CREATE command to create a new library, but a library by that name is currently open or attached.
Action:
Close or detach the library or check the spelling of the library name and re-enter the CREATE command.
Cause:
You attempted to open a library in a nonexistent namespace.
Action:
Create the namespace, or specify a different namespace.
Cause:
You entered the CREATE command with the namespace keyword, but did not supply a namespace.
Action:
Check the syntax of the CREATE command. Re-enter the command, supplying a name for the namespace.
Cause:
You entered the CREATE LIBRARY command with the SOURCE keyword to create a library using the specified file, but did not supply a file name.
Action:
Check the syntax of the CREATE LIBRARY command. Re-enter the command, specifying a file name.
Cause:
You aborted a library CREATE or SAVE operation because an external location was already in use.
Action:
Select a new name for the library using the CREATE or SAVE operation or opt to replace the existing object.
Cause:
You entered the CREATE LIBRARY command with the SOURCE keyword to create a library from the specified file, but the file is not a valid PL/SQL source file.
Action:
Re-enter the command, supplying a valid source file.
Cause:
You entered the DESCRIBE command to display information about a library that is not currently attached. You cannot display information about libraries that are not attached.
Action:
If you wish to display information about a library that is not attached, attach the library using ATTACH, then re-enter the previous DESCRIBE command to view the information. Otherwise, re-enter DESCRIBE, specifying a library that is already attached.
Cause:
You entered the DESCRIBE command to display information about a breakpoint or debug trigger, but did not specify the ID of an existing debug action.
Action:
Re-enter DESCRIBE, specifying an existing debug action ID.
Cause:
You entered the DESCRIBE command to display detailed information about a program unit, debug action, library, local variable or parameter, or the load path. However, you did not provide any keywords and/or values in the command string.
Action:
Re-enter the DESCRIBE command, specifying the keywords and values appropriate to the type of information you wish to display.
Cause:
You entered the DESCRIBE command to display information about a local variable or parameter, but the local you specified does not exist in the current scope location.
Action:
Re-enter the DESCRIBE command, specifying a local variable or parameter that exists in the current scope location.
Cause:
You entered the DESCRIBE command to display information about a program unit, but the program unit you specified is not defined in the current environment.
Action:
Re-enter the DESCRIBE command, specifying a program unit that is defined in the current environment.
Cause:
You entered the DESCRIBE command to display information about a table, but the table you specified does not exist in the database.
Action:
Re-enter the DESCRIBE command, specifying a table that exists in the database.
Cause:
You entered the DESCRIBE command to display information about a view, but the view you specified does not exist in the database.
Action:
Re-enter the DESCRIBE command, specifying a view exists in the database.
Cause:
You entered the DELETE command to remove a breakpoint or debug trigger, but did not specify a valid debug action ID.
Action:
Re-enter DELETE, specifying a valid debug action ID.
Cause:
You entered the DELETE command to delete a bind variable, but did not specify a valid bind variable name.
Action:
Re-enter DELETE, specifying a valid bind variable name.
Cause:
You attempted to delete one or more program units from a library that is not currently open. You cannot delete program units from libraries that are not open.
Action:
If you wish to delete one or more program units from a library that is not open, open the library using OPEN, then re-enter the previous DELETE command to delete the program unit(s) from the library Otherwise, re-enter DELETE, specifying a library that is already open.
Cause:
You entered the DELETE command to delete a program unit, but the program unit you specified is a Built-in. Built-ins cannot be deleted from Procedure Builder.
Action:
You can only delete program units that are created within or loaded into Procedure Builder.
Cause:
You entered the DELETE command to delete a namespace, but the specified namespace is the current namespace.
Action:
You cannot delete a namespace that is the current namespace, a parent of the current namespace, or the global namespace. Use the CHANGE command to select another namespace as the current namespace and re-enter the DELETE command.
Cause:
You entered the DELETE command to delete a namespace, but the specified namespace is the global namespace.
Action:
You cannot delete a namespace that is the current namespace, a parent of the current namespace, or the global namespace.
Cause:
You entered the DELETE command to delete a namespace, but the specified namespace does not exist.
Action:
Check the spelling of the namespace and retry the command..
Cause:
You entered the DELETE command to delete one or more libraries, but did not specify a library name.
Action:
Check the syntax of the DELETE command. Re-enter the command, specifying the name(s) of the library or libraries you wish to delete.
Cause:
You entered the DELETE command to delete one or more program units, but did not specify a program unit name.
Action:
Check the syntax of the DELETE command. Re-enter the command, specifying the name(s) of the program unit(s) you wish to delete.
Cause:
You entered the DELETE command to delete one or more program units from an open library, but did not specify a library name.
Action:
Check the syntax of the DELETE command. Re-enter the command, specifying the name of the library from which you wish to delete one or more program units.
Cause:
You entered the DELETE command to delete one or more bind variables, but did not specify a bind variable name.
Action:
Check the syntax of the DELETE command. Re-enter the command, specifying the name(s) of the bind variable(s) you wish to delete.
Cause:
You entered the DELETE command to delete a namespace, but the specified namespace contains the current namespace.
Action:
You cannot delete a namespace that is the current namespace, a parent of the current namespace, or the global namespace. Use the CHANGE command to select another namespace as the current namespace and re-enter the DELETE command.
Cause:
You entered the DISABLE command to disable a breakpoint or debug trigger, but did not specify a valid debug action ID.
Action:
Re-enter DISABLE, specifying a valid debug action ID.
Cause:
You entered the DISABLE command to temporarily remove one or more debug actions, or suspend logging to the current log file. However, you did not provide any keywords and/or values in the command string.
Action:
Re-enter the DISABLE command, specifying the keywords and values appropriate to the item(s) you wish to disable.
Cause:
You entered the DETACH command to detach a library, but did not specify a library name.
Action:
Check the syntax of the DETACH command. Re-enter the command, specifying the name of the library you wish to detach.
Cause:
You entered the DETACH command to detach a library, but the library you specified is not currently attached. You cannot detach libraries that are not attached.
Action:
Check the spelling of the library name you specified and re-enter the DETACH command.
Cause:
You entered the ENABLE command to enable a breakpoint or debug trigger, but did not specify a valid debug action ID.
Action:
Re-enter ENABLE, specifying a valid debug action ID.
Cause:
You entered the ENABLE command to reactivate one or more disabled debug actions, or resume logging to the current log file. However, you did not provide any keywords and/or values in the command string.
Action:
Re-enter the ENABLE command, specifying the keywords and values appropriate to the item(s) you wish to enable.
Cause:
You entered the SET command to set the current namespace or change the current scope location, but you did not specify any keywords and/or values in the command string.
Action:
Re-enter the SET command, specifying the appropriate keywords and values.
Cause:
You entered the SET NAMESPACE command to change the current namespace, but did not specify an existing namespace.
Action:
Re-enter the SET NAMESPACE command, specifying an existing namespace.
Cause:
You attempted to change the current scope location with the SET SCOPE command, but the scope location could not be set because there was no PL/SQL program unit whose execution was suspended at the time.
Action:
If you wish to use the SET SCOPE command, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
You attempted to change the current scope location with the SET SCOPE command, but the scope location could not be set because you did not specify a PL/SQL program unit.
Action:
Re-enter the SET SCOPE command, specifying a program unit.
Cause:
You entered the EXPORT command to write the source of one or more program units to a file, but did not specify a file name.
Action:
Check the syntax of the EXPORT command. Re-enter the command, specifying the name of the file in which to write the program unit source.
Cause:
You entered the EXPORT command to write the source of one or more program units to a file, but did not specify any program unit names.
Action:
Check the syntax of the EXPORT command. Re-enter the command, specifying the program unit(s) whose source you wish to export.
Cause:
You entered the EXPORT command to write the source of one or more program units to a file, but do not have the necessary privileges to write to the specified file.
Action:
Change your privileges so you can write to the file, or specify another file to which you can write.
Cause:
You entered the EXPORT command to export the contents of a library that is not currently attached. You cannot export libraries that are not attached.
Action:
If you wish to export a library that is not attached, attach the library using the ATTACH command, the re-enter the previous EXPORT command. Otherwise, re-enter EXPORT, specifying a library that is already attached.
Cause:
You entered the EXPORT command to export the contents of a library, but did not specify a library name.
Action:
Check the syntax of the EXPORT command. Re-enter the command, specifying the name of the library whose source you wish to export.
Cause:
You entered the EXPORT command with the STORED keyword to export stored program units, but you are not currently connected to a database.
Action:
Connect to a database and re-enter the EXPORT command.
Cause:
You entered the EXPORT command to export one or more stored program units, but the specified stored program units do not exsit in the database.
Action:
Re-enter the EXPORT command, specifying the correct names for the stored program units.
Cause:
You entered a type keyword that does not match the language keyword.
Action:
Re-enter the EXPORT command, specifying the correct type and language.
Cause:
You entered the GENERATE command to produce a ".c" file from a program unit, without specifying the name of the file to generate.
Action:
Re-enter the GENERATE command, using the FILE keyword and argument.
Cause:
You entered the GENERATE command to produce a ".c" file from a program unit without compiling program unit first.
Action:
Compile the program unit and re-enter the GENERATE command.
Cause:
You entered the GENERATE command to produce a ".c" file from a program unit, specifying both SPEC and BODY.keywords. A ".c" file may contain only the SPEC or the BODY, not both.
Action:
Use two GENERATE commands, specifying SPEC and BODY separately.
Cause:
You entered the GENERATE command to produce a ".c" file from a program unit, without specifying a program unit. If a program unit was specified, its type does not match the SPEC or BODY keyword.
Action:
Re-enter the GENERATE command, specifying a valid program unit keyword and argument.
Cause:
An operating system error occurred while attempting to open the ".c" file in a GENERATE command.
Action:
Re-enter the GENERATE command, specifying a valid FILE keyword and argument.
Cause:
A GENERATE command was issued without the LIBRARY keyword.
Action:
Re-enter the GENERATE command, specifying the LIBRARY keyword. For more information, see GENERATE.
Cause:
You entered the GENERATE command to produce a ".c" file from a program unit without specifying a symbol name.
Action:
Re-enter the GENERATE command, specifying the symbol name.
Cause:
You attempted to generate a runtime library for a library that is not currently open. You cannot perform this operation for libraries that are not open.
Action:
Make sure the library you wish to generate is open, or check the spelling of the specified library and re-enter the command.
Cause:
You entered the GENERATE command to produce a runtime library without specifying the name of the source library.
Action:
Re-enter the GENERATE command using the LIBRARY keyword and argument.
Cause:
You entered the GRANT command to grant a user access to a library stored in the database, but did not specify a library name.
Action:
Check the syntax of the GRANT command. Re-enter the command, specifying the library to which you wish to grant access.
Cause:
You entered the GRANT command to grant a user access to a library stored in the database, but did not specify a username.
Action:
Check the syntax of the GRANT command. Re-enter the command, specifying the username to which you wish to grant access.
Cause:
You entered the HELP command to display information about a Procedure Builder command, but did not specify a valid command.
Action:
Re-enter the HELP command, specifying Procedure Builder command for which you need help.
Cause:
You entered the INTERPRET command to execute one or more Procedure Builder scripts, but you did not provide any keywords and/or values in the command string.
Action:
Re-enter the INTERPRET command, specifying the appropriate keywords and values.
Cause:
You entered the INTERPRET command to interpret the contents of a file, but the last PL/SQL block in the file was incomplete.
Action:
Check the contents of the file. Fix any errors and retry the operation.
Cause:
You entered the INTERPRET command with the FILE keyword , but the file is not a valid PL/SQL source file.
Action:
Re-enter the command, supplying a valid source file.
Cause:
You entered the INSERT command, but did not provide enough arguments in the command string.
Action:
Check the syntax of the INSERT command.
Cause:
You entered the INSERT command to insert one or more program units into an open library, but did not list any program units in the command string.
Action:
Check the syntax of the INSERT command. Re-enter the command, specifying the program unit(s) you wish to add to the library.
Cause:
You entered the INSERT command to insert one or more program units into a library that is not currently open. You cannot add program units to libraries that are not open.
Action:
If you wish to add one or program units to a library that is not open, open the library using OPEN, then re-enter the previous INSERT command to add the program unit(s) to the library. Otherwise, re-enter INSERT, specifying a library that is already open.
Cause:
You entered the INSERT command to modify the load path, but did not specify any keywords and/or directory path(s) to insert.
Action:
Check the syntax of the INSERT command. Re-enter the command, specifying the keywords and/or directory path(s) you wish to insert into the load path.
Cause:
You entered the INSERT command to insert one or more program units into a namespace that does not exist.
Action:
Check the spelling of the specified namespace, or create a new namespace using the .CREATE command and re-enter the INSERT command.
Cause:
You entered the INSERT command with the namespace keyword to insert one or more program units into a namespace, but did not specify a namespace.
Action:
Re-enter the INSERT command specifying an existing namespace.
Cause:
You entered the LOG command without providing any keywords and/or values in the command string.
Action:
Re-enter the LOG command, specifying the appropriate keywords and values.
Cause:
You entered the LOG command to begin saving a transcript of Interpreter input and output in a log file, but do not have the necessary privileges to write to the specified file.
Action:
Change your privileges so you can write to the file, or specify another file to which you can write.
Cause:
You entered the LOG command with the FILE keyword, but did not specify a file name.
Action:
Re-enter the LOG command, specifying a file name.
Cause:
You entered the LOAD command to load one or more program units stored in a library that is not currently attached. You cannot load program units stored in a library that is not attached.
Action:
If you wish to load program units stored in a library, attach the library using ATTACH, then enter the LOAD command to load the program units.
Cause:
You entered the LOAD command without providing any keywords and/or values in the command string.
Action:
Re-enter the LOAD command, specifying the appropriate keywords and values. You can use LOAD to load one or program units from an attached library, a file, or the database.
Cause:
You entered the LOAD command, but did not specify any program units to load.
Action:
Re-enter the LOAD command, specifying the name(s) of the program unit(s) you wish to load.
Cause:
You entered the LOAD command to load one or more program units stored in the database, but the stored program unit you specified does not exist.
Action:
Re-enter the LOAD command, specifying the name(s) of the stored program unit(s).
Cause:
You entered the LOAD command with the STORED keyword to load one or more program units stored in the database, but you are not currently connected to a database.
Action:
Connect to a database and re-enter the LOAD command.
Cause:
You entered the LOAD command with the NAMESPACE keyword to load a program unit into a namespace, but the specified namespace does not exist.
Action:
Re-enter the LOAD command, specifying an existing namespace.
Cause:
You entered the LOAD command with the NAMESPACE keyword but did not specify any namespace to load into.
Action:
Re-enter the LOAD command , supplying the appropriate keywords and values to specify which stored program units to load.
Cause:
You entered the LOAD command with the FILE keyword, but you did not specify a file from which to load.
Action:
Re-enter the LOAD command, specifying the name of the file from which to load the program unit(s).
Cause:
You entered the LOAD command with the FILE keyword , but the file is not a valid PL/SQL source file.
Action:
Re-enter the command, supplying a valid source file.
Cause:
You entered the OPEN command to open a library, but did not specify a library name.
Action:
Check the syntax of the OPEN command. Re-enter the command, specifying the name of the library you wish to open.
Cause:
You entered the OPEN command to open a library residing in the file system, but the specified file name could not be found.
Action:
Check the spelling of the specified file name and re-enter the command.
Cause:
You attempted to open a library in a nonexistent namespace.
Action:
Create the namespace, or specify a different namespace.
Cause:
You entered the OPEN command to open a library under a namespace, but did not specify a namespace.
Action:
Check the syntax of the OPEN command. Re-enter the command, specifying a namespace.
Cause:
You attempted to issue a SQL DDL statement but you are not currently connected to a database.
Action:
Connect to a database and re-try the SQL DDL statement.
Cause:
You entered the REVOKE command to revoke a user's access to a library stored in the database, but did not specify the library name.
Action:
Check the syntax of the REVOKE command. Re-enter the command, specifying the library to which you wish to revoke access.
Cause:
You entered the REVOKE command to revoke a user's access to a library stored in the database, but did not specify a username.
Action:
Check the syntax of the REVOKE command. Re-enter the command, specifying the username whose access you wish to revoke.
Cause:
You entered the RENAME command to change the name of a library that resides in the current database, but did not specify the old name of the library.
Action:
Check the syntax of the RENAME command. Re-enter the command, specifying the old name.
Cause:
You entered the RENAME command to change the name of a library that resides in the current database, but did not specify a new name for the library.
Action:
Check the syntax of the RENAME command. Re-enter the command, specifying a new name.
Cause:
You entered the RENAME command to change the name of a library, but the command failed for one of the following reasons:
A: The specified library does not exist in the current database.
B: You do not have permission to rename the specified library.
Action: You can take the following actions to correct this error:
If A: Re-enter the RENAME command, specifying the correct library name.
If B: Acquire the privileges necessary to rename the library and re-enter the RENAME command.
Cause:
You entered the RENAME command to change the name of a library, but were not connected to a database.
Action:
Connect to the database where the library is stored, and rename the library.
Cause:
You entered the RENAME command to change the name of a library stored in the current database, but the library specified by the new name is currently attached. You cannot rename a library to the name of a library that is currently attached.
Action:
Use the DETACH command to detach the library specified by the new name or use a different new name, then re-enter the RENAME command.
Cause:
You entered the RENAME command to change the name of a library stored in the current database, but the library specified by the new name is currently open. You cannot rename a library to the name of a library that is currently open.
Action:
Use the CLOSE command to close the library specified by the new name or use a different new name, then re-enter the RENAME command.
Cause:
You entered the RESET command to reset to an explicitly specified debug level, but no such debug level exists.
Action:
Check the syntax of the LEVEL keyword to the RESET command. For more information, see RESET. Re-enter the command with a valid debug level.
Cause:
You entered the RESET command to abort execution of a PL/SQL program unit, but there was no program unit whose execution was suspended at the time.
Action:
If you wish to use the RESET command, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
You entered the REVERT command to revert a library, but did not specify a library name.
Action:
Check the syntax of the REVERT command. Re-enter the command, specifying the name of the library you wish to revert.
Cause:
You attempted to revert a library that is not currently open. You cannot revert libraries that are not open.
Action:
Make sure you are trying to revert an open library. Check the spelling of the specified library and re-enter the command.
Cause:
You entered the SAVE command to save a library, but did not specify a library name.
Action:
Check the syntax of the SAVE command. Re-enter the command, specifying the name of the library you wish to save.
Cause:
You attempted to save a library that is not currently open. You cannot save a libraries that are not open.
Action:
Make sure you are trying to save an open library. Check the spelling of the specified library and re-enter the command.
Cause:
You entered the SAVE command with the AS option to save a library in a specified file, but you did not specify a file name.
Action:
Check the syntax of the SAVE command. Re-enter the command, specifying the name of the file in which you wish to save the library.
Cause:
You entered a SQL SELECT statement, but you are not currently connected to a database.
Action:
Connect to a database and re-enter the statement. For more information on connecting to a database, see your Oracle product documentation.
Cause:
You attempted to list frames on the call stack with the SHOW command, but there was no call stack because there was no PL/SQL program unit whose execution was suspended at the time.
Action:
If you wish to use the SHOW command to list frames on the call stack, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
You entered a type keyword that does not match the language keyword.
Action:
Re-enter the SHOW command specifying the correct type and language.
Cause:
You entered the STORE command, but did not specify any program units to store.
Action:
Re-enter the STORE command, supplying the appropriate keywords and values to specify which program units to store.
Cause:
You entered the STORE command to store one or more program units in the database, but the program unit you specified does not exist.
Action:
Re-enter the STORE command, specifying the correct name for the program unit.
Cause:
You entered the STORE command to store a program unit in the database, but you are not currently connected to a database.
Action:
Connect to a database and re-enter the STORE command.
Cause:
You entered the STORE command to store a program unit in the database, but the program unit you specified is a Built-in.
Action:
You can only store program units that are created within or loaded into Procedure Builder.
Cause:
You entered the STORE command to store a program unit in the database, but the program unit's source is not a complete PL/SQL construct.
Action:
Enter a complete PL/SQL construct as the source of the program unit, then re-enter the STORE command.
Cause:
You entered the STORE command with the OWNER keyword, but you did not specify an owner name.
Action:
Re-enter the STORE command, supplying the owner name.
Cause:
You entered the STORE command to store a function or procedure specification in the database. Only package specifications can be stored.
Action:
Make sure there is a body for the function or procedure you are attempting to store. Re-enter the STORE command without the SPECIFICATION keyword.
Cause:
You entered the TRIGGER command to create a debug trigger, but did not supply a PL/SQL statement or block as the body of the trigger.
Action:
Check the syntax of the TRIGGER command. Re-enter the command with a valid trigger body.
Cause:
You entered an invalid PL/SQL construct in the trigger body.
Action:
Fix the PL/SQL construct before closing the editor.
Cause:
You entered the EXECUTE command to execute a parameterless procedure, but did not specify a procedure name.
Action:
Check the syntax of the EXECUTE command. Re-enter the command, specifying the name of the parameterless procedure you wish to execute.
Cause:
You entered the EXECUTE command to execute a parameterless procedure, but did not compile the procedure beforehand.
Action:
Compile the procedure (using the COMPILE command), then re-enter the EXECUTE command.
Cause:
You called a DEBUG.GETx function or DEBUG.SETx procedure to access the value of a local parameter or variable, but the specified local is not defined at the current scope location.
Action:
Use the SHOW LOCALS command to list the local parameters and variables at the current scope location. Then change the DEBUG.GETx or DEBUG.SETx call to pass a valid local name.
Cause:
You called a DEBUG.GETx function or DEBUG.SETx procedure to access the value of a local parameter or variable, but the base type of the specified local did not match x. For example, you would get this error if you tried to get the value of a local CHAR variable using the local NUMBER function DEBUG.GETN.
Action:
Check the base type of the specified local and call the DEBUG.GETx or DEBUG.SET x subprogram that is appropriate for that type.
Cause:
You tried to set the value of a variable for which there is no debugging information available.
Action:
Recompile the package or procedure with debugging information.
Cause:
You tried to set the value of a variable to something inappropriate, too long, or out of range.
Action:
Check the definition of the variable and set it to something appropriate.
Cause:
You tried to perform an unimplemented feature (e.g. setting the value of an IN variable in the debugger).
Action:
You cannot use this functionality yet.
Cause:
The ORA_DE_REFLECTION package on the server is out of date.
Action:
Your DBA should reload this package. This can be done by running the DEJAVINS.SQL script supplied with Oracle Procedure Builder.
Cause:
The ORA_DE_REFLECTION package on the server is too advanced for this version of Oracle Procedure Builder.
Action:
This exception should never occur. ORA_DE_REFLECTION is intended to be backward compatible with all previous versions of Oracle Procedure Builder. Report this problem to customer support.
Cause:
See accompanying error messages for more information.
Action:
Your DBA should reload this package. This can be done by running the DEJAVINS.SQL script supplied with Oracle Procedure Builder.
Cause:
You defined a call to a foreign function using one or more datatypes that are not supported by the ORA_FFI package.
Action:
Use datatypes that is supported by the ORA_FFI package. For more information about supported datatypes, see the Oracle product documentation for your operating system.
Cause:
You defined a call to a foreign function using a return value datatype that is not supported by the ORA_FFI package.
Action:
Use a return value datatype that is supported by the ORA_FFI package. For more information about supported datatypes, see the Oracle product documentation for your operating system.
Cause:
You attempted to call a function in a foreign library, but the library you specified does not exist or could not be opened.
Action:
Check to see if the specified foreign library exists, and make sure you have permission to read its contents. Also, check the spelling of the library name in your call.
Cause:
You attempted to call a function in a foreign library, but the function you specified could not be found in the library.
Action:
Make sure the function is contained in the specified library. Also, check the spelling of the function and library names in your call.
Cause:
You attempted to perform an operation on a library handle to a foreign library, but the handle you specified was invalid.
Action:
Make sure the library handle is a valid result of ORA_FFI.LOAD_LIBRARY or ORA_FFI.FIND_LIBRARY.
Cause:
You attempted to perform an operation on a function handle to a foreign function, but the handle you specified was invalid.
Action:
Make sure the function handle is a valid result of ORA_FFI.REGISTER_FUNCTION or ORA_FFI.FIND_FUNCTION.
Cause:
The total size of all arguments registered so far is too large.
Action:
Redefine this function or procedure to take fewer arguments.
Cause:
You called the TEXT_IO.FOPEN function to open a text file, but passed an invalid file mode specification argument.
Action:
Check the syntax of the TEXT_IO.FOPEN function. For more information, see The TEXT_IO Package. Change the TEXT_IO.FOPEN call to pass a valid file mode specification argument.
Cause:
You called a subprogram in the TEXT_IO package to read from or write to a text file, but you passed a file handle argument that is not associated with an open file.
Action:
Use the TEXT_IO.FOPEN function to open the file and return a valid file handle. Then call the TEXT_IO subprogram again, passing the valid file handle as an argument.
Cause:
The position you supplied was invalid.
Action:
Supply a new position that is greater than or equal to 0 and less than the length of the list.
Cause:
You called a stored (server-side) subprogram from a client-side program unit, but it failed because the stored subprogram requires more arguments than are currently supported by Procedure Builder (100).
Action:
Redefine the stored subprogram to require fewer arguments, or define a new stored subprogram with fewer arguments that calls the old subprogram on the database side.
Cause:
Records have been left in the SYS.PSTUBTBL table in the database by the previous execution of a program.
Action:
Delete all entries in the SYS.PSTUBTBL table and retry your operation.
Cause:
A call to a stored program unit creates a stub program unit of the same name on the client side. This stub could not be created because there is already an existing program unit with the same name.
Action:
Rename the existing program unit.
Cause:
An operation involving the kernal or PL/SQL subsystem encountered an error.
Action:
Take the appropriate action for the subsystem error.
Cause:
You entered a command and specified an invalid keyword in the command string.
Action:
Check the syntax of the command you just entered. For more information, see Using Interpreter commands. Re-enter the command, specifying the appropriate keywords, values, and options for that command.
Cause:
You entered a Procedure Builder command which has been disabled by another product.
Action:
Check the syntax of the command you just entered within the context of the product you are running. Re-enter the command correctly, specifying the appropriate keywords, values, and options for that command.
Cause:
You entered the INTERPRET command to execute a Procedure Builder script stored in a file, but either the file you specified does not exist, or you do not have permission to read the file.
Action:
Re-enter the INTERPRET command, specifying a file containing a Procedure Builder script you have permission to read.
Cause:
You performed an operation that attempted to access the PL/SQL execution state, but there was no PL/SQL program unit whose execution was suspended at the time.
Action:
If you wish to perform this operation, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
You attempted to execute a program unit, but the execution was aborted because its execution state was invalidated by the actions of a debug trigger. For example, you would receive this error if you called a program unit for which a debug trigger was defined that invoked the RESET command.
Action:
Restart execution of the original program unit and avoid the operation that caused the invalidation.
Cause:
You issued a command that does not exist.
Action: Type .HELP COMMAND on the Interpreter command line to display a list of valid commands.
Cause:
You issued a null command (e.g., DEBUG.INTERPRET('');).
Action:
Change the command string to a valid command.
Cause:
You entered a command, but supplied too many keywords or supplied extra keywords that were inappropriate for the context in which the command was executed. For example, you would receive this error if you entered the command .SHOW PROCEDURES BREAKPOINTS because you cannot list both procedures and breakpoints in the same command.
Action:
Check the syntax of the command you just entered.
Cause:
You entered the CONNECT command to connect to a database, but did not specify a connect string.
Action:
Check the syntax of the CONNECT command. Re-enter the command correctly, specifying the appropriate keyword and connect string.
Cause:
You entered a command that accesses the database, but there was no current connection.
Action:
Connect to a database and re-enter the command.
Cause:
You entered a command in which you specified one or more program units (e.g., LIST, DESCRIBE, BREAK, etc.), but at least one of the program units you specified was not defined in the environment.
Action:
Re-enter the command, specifying only program units that are defined in the environment.
Cause:
You entered a command in which you specified a source location in terms of a debug action ID (e.g., LIST, BREAK, etc.), but the ID you supplied did not identify an existing debug action.
Action:
Re-enter the command, specifying a valid debug action ID.
Cause:
You entered a Procedure Builder command in which you either failed to specify a location (for example, LIST, STEP, BREAK, etc.), or specified the current location when there is none.
Action:
Re-enter the command, specifying a valid location.
Cause:
You entered a command in which you specified a source location in terms of a debug action ID (e.g., LIST, BREAK, etc.), but the ID you supplied identified a trigger attached to multiple source lines (e.g., a DEBUG or * trigger).
Action:
Re-enter the command, specifying an ID that identifies a debug action associated with a single source line, or specify the source location in some other manner.
Cause:
You entered a Procedure Builder command (e.g., CONNECT) and supplied a keyword (e.g., DB) that required an argument consisting of a string of whitespace delimited characters, but you did not supply the argument.
Action:
Re-enter the command, supplying the appropriate argument for the keyword.
Cause:
You entered a command (e.g., LOAD) and supplied a keyword (e.g., FILE) that required one or more file name arguments, but did not supply any file names.
Action:
Check the syntax of the command you just entered. Re-enter the command, specifying the appropriate keywords, values, and options for that command.
Cause:
You entered a command (e.g., DELETE) and supplied a keyword (e.g., PROCEDURE) that required one or more object name arguments, but did not supply any object names.
Action:
Check the syntax of the command you just entered. Re-enter the command, specifying the appropriate keywords, values, and options for that command.
Cause:
You entered a Procedure Builder command (e.g., BREAK) and supplied the USER keyword. USER requires an argument (user name), but none was supplied.
Action:
Check the syntax of the command you just entered. Re-enter the command, specifying the appropriate keywords, values, and options for that command.
Cause:
You entered a Procedure Builder command (e.g., BREAK) and supplied the USER keyword. You also entered a Program Unit name in the form USER.PU. You must choose one method by which to supply the user name. The syntax PACKAGE.PU is not currently supported.
Action:
Check the syntax of the command you just entered. Re-enter the command, specifying the appropriate keywords, values, and options for that command.
Cause:
You entered a Procedure Builder command (e.g., BREAK) and supplied the USER keyword or used the USER.PU notation. However, you are not connected to an Oracle database. The syntax PACKAGE.PU is not supported.
Action:
Connect to an Oracle database and try the command again.
Cause:
You entered a Procedure Builder command (e.g., LIST, BREAK) and specified one or more program units. However, at least one of the program units is a Built-in, and this operation is not allowed on Built-ins.
Action:
Re-enter the command, specifying program units that are not Built-ins.
Cause:
You entered a command with a keyword that expects an integer value (e.g., LINE, COUNT), but did not specify a valid integer.
Action:
Check the syntax of the command you just entered. Re-enter the command, specifying the appropriate keywords, values, and options for that command.
Cause:
You entered a command with a keyword that expects one or more file name arguments (e.g., FILE), but a file name you supplied exceeded the maximum supported length of 128 bytes.
Action:
Rename or move the file such that its name can be specified using fewer than the maximum number of bytes, then re-enter the command with the shorter file name.
Cause:
You entered a command with a keyword that expects one or more valid SQL or PL/SQL name arguments (e.g., PROCEDURE), but a name you supplied does not begin with a letter.
Action:
Re-enter the command, specifying the correct SQL or PL/SQL object name(s) beginning with a letter.
Cause:
You entered a command and supplied a keyword argument that started with a double quote, but you did not supply a matching close quote.
Action:
Re-enter the command, supplying a matching close quote for the quoted argument.
Cause:
You entered a command with a keyword that expects one or more valid SQL or PL/SQL name arguments (e.g., PROCEDURE), but a name you supplied exceeds the maximum allowable identifier length of 30 bytes.
Action:
Re-enter the command, specifying SQL or PL/SQL object name(s) that do not exceed the maximum allowable length.
Cause:
You entered a command (e.g., TRIGGER) with a keyword (e.g., IS) that expected a PL/SQL statement or block to follow, but you supplied only a PL/SQL comment instead.
Action:
Re-enter the command, specifying PL/SQL statement or block in place of the originally supplied comment. If you wish to associate a comment with the PL/SQL construct, enter a block and place the comment within the BEGIN and END keywords.
Cause:
You entered a command (e.g., CONNECT) and supplied a keyword (e.g., DB) that required a whitespace delimited argument, but the argument you supplied exceeded the maximum allowable length of 128 bytes.
Action:
Re-enter the command with a smaller argument value.
Cause:
You entered a command (e.g., CONNECT) and supplied a string that should follow the SQL naming conventions, but the string you entered was not valid.
Action:
Re-enter the command with a valid SQL name.
Cause:
Failed to start the JVM controller or connect to an existing JVM controller.
Action:
Notify your administrator.
Cause:
You specified the same argument more than once on the command line.
Action:
Specify the argument only once. If you want to specify multiple values, specify them as a list value.
Cause:
You specified an invalid keyword argument on the command line.
Action:
Specify the correct keyword argument.
Cause:
You specified a positional argument after a keyword argument.
Action:
All positional arguments must be specified before any keyword arguments. Once a keyword argument has been specified, all subsequent arguments must also be keyword arguments on the command line.
Cause:
You specified an invalid value for a keyword argument on the command line.
Action:
Specify the correct keyword value.
Cause:
You specified an improperly formatted list value for a keyword argument on the command line.
Action:
Specify the correct list format.
Cause:
You specified a list value for a keyword which does not accept list values.
Action:
Specify a single value for the keyword.
Cause:
In the Object Navigator, you tried to paste or drop an object of an inappropriate type.
Action:
Drag or paste the object to a different node of the appropriate type.
Cause:
In the Object Navigator, you tried to perform an operation which requires all selected objects to be of the same type.
Action:
Select objects of the same type and try the operation again.
Cause:
Procedure Builder cannot obtain enough memory from the system to complete an attached library operation.
Action:
Make more memory available, if you can, or ask your system administrator for assistance.
Cause:
You tried to attach a library that is already attached.
Action:
Since the library is already attached, there is no need to try to reattach it.
Cause:
You entered the DELETE command to delete a library from the database, but the specified library is currently attached or open.
Action:
Detach the library using the DETACH command or close the library using the CLOSE command, then re-enter the previous DELETE command to delete the library from the database.
Cause:
You entered the DELETE command to delete a library stored in the database, but this operation failed because of one of the following reasons:
A: You specified an incorrect library name.
B: You specified a library that is currently attached.
Action: You can take the following actions to correct this error:
If A: Re-enter the DELETE command, specifying the correct library name.
If B: Detach the specified library using the DETACH command and re-enter the
DELETE command.
Cause:
You attempted to reference a library that is not currently attached.
Action:
Retry the operation, specifying the name of an attached library.
Cause:
You attempted to attach a generated, runtime only library (.PLX extension). This is not supported.
Action:
Attach the source library (.PLL extension) instead.
Cause:
You attempted to attach a library to itself. This is not supported.
Action:
The library and its contents are already accessible. There is no need to attempt to attach it again.
Cause:
You attempted to declare a new Procedure Builder bind variable using the CREATE command, but a bind variable with the specified name already exists.
Action:
Re-enter the CREATE command specifying a different, unique name for the bind variable.
Cause:
You attempted to reference a bind variable in a PL/SQL program unit, but the specified bind variable is not defined.
Action:
Edit the program unit, change the bind variable reference to a valid bind variable name, and recompile.
Cause:
You attempted to advance PL/SQL execution with the GO or STEP commands, but there was no PL/SQL program unit whose execution was suspended at the time.
Action:
If you wish to use the GO or STEP commands, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
Records have been left in the SYS.PSTUBTBL table in the database by the previous execution of a program.
Action:
Delete all entries in the SYS.PSTUBTBL table and retry your operation.
Cause:
You executed a remote (server-side) program unit, which is suspended at a breakpoint. If you were allowed to disconnect now, all dependent program units would be invalidated. You cannot disconnect until the execution is reset or finished.
Action:
Reset or finish the program unit execution, then disconnect.
Cause:
Procedure Builder attempted to decode a program unit that was created on a different machine architecture. This process requires recompiling the program unit, but no source code was found.
Action:
Supply a program unit that was created on the current machine architecture, or provide a copy from the foreign machine that was saved with source code.
Cause:
Procedure Builder attempted to decode a program unit that was encoded by an unsupported version of the library management code.
Action:
This is an internal error.
Cause:
You tried to store a program unit in a library, but its stored representation exceeds the maximum allowable size on this operating system.
Action:
Split the offending program unit into smaller program units and retry the operation.
Cause:
In Version 1, Procedure Builder allowed you to create a program unit with the same name as a Built-in package. This is not allowed in Version 2. When you load a program unit with the same name as a Built-in package, Procedure Builder renames the program unit by appending two dollar signs. For example, the procedure DEBUG becomes DEBUG$$.
Action:
Change the program unit name before loading, if desired, making sure that you update all references to the program unit name as well.
Cause:
You attempted an operation that caused an internal error, also known as an abnormal condition. The error code (in parentheses) specifies the internal routine associated with the error.
Action:
For information on how to proceed, see Abnormal Conditions in the Procedure Builder documentation.
Cause:
An error occurred. The error is documented in the release notes file.
Action:
See the Procedure Builder release notes file.
Cause:
You attempted to edit a library that is attached read-only.
Action:
Detach the library you wish to edit, then reattach the library read-write.
Cause:
You attempted to create a new library in the current database, but a library by the same name already exists.
Action:
Specify a different, unique name for the library and retry the create operation.
Cause:
You attempted to edit a library that was created by Version 1.0.5 or earlier of Procedure Builder, but such libraries may only be accessed read-only from newer versions.
Action:
Copy the contents of the old library into a new library for which read-write access is supported. Copying a library is most easily accomplished using File>Save As in the Library editor.
Cause:
You attempted to rename or delete a library residing in the file system using the RENAME or DELETE command, respectively, but this operation is only supported on libraries residing in the database.
Action:
Use the appropriate facilities of the native operating system to rename or delete libraries residing in the file system.
Cause:
You attempted to create or access a library stored in the database, but the operation failed because a table was missing from the Oracle Tools Common Schema.
Action:
Contact your DBA and insure that the Oracle Tools Common Schema is installed properly.
Cause:
You attempted a library operation, but the specified library does not exist in the database.
Action:
Check the spelling of the library name and retry the operation, specifying an existing database library.
Cause:
You entered a command and specified a library that could not be found or did not exist in either the file system or the current database.
Action:
Re-enter the previous command, specifying the correct location and name of the library you wish to use.
Cause:
You attempted a library operation, but the specified library could not be opened.
Action:
This error is issued in conjunction with other errors. Investigate the additional errors for suggestions on how to handle this error.
Cause:
You entered the RENAME command to rename a library stored in the current database, but the new name you specified is the same as that of an existing library.
Action:
Re-enter the RENAME command, specifying a different name as the new name. Otherwise, rename the library that is currently using the new name you specified in the failed command, then re-enter the failed command.
Cause:
You attempted to create a library, but the specified file could not be opened, most likely for one of the following reasons:
A: You specified an invalid library name.
B: You specified the name of a library that already exists in a file, but you
do not have the necessary permissions to modify the file.
Action: You can take the following actions to correct this error:
If A: Retry the operation, specifying a valid library name.
If B: Retry the operation, specifying a different library name. If you wish to use the same library name (effectively overwriting the existing library), make sure you have the necessary permissions to do so.
Cause:
A library operation attempted to fetch a record and failed.
Action:
Make sure that all of your Procedure Builder-related tables are correctly installed. If all of the tables appear to be correct, contact Oracle Customer Support.
Cause:
You attempted to open a file containing a PL/SQL library, but either the file permissions are incorrect, the specified file does not contain a valid library, or the file is in use by another application.
Action:
Check the spelling of the specified file name, the permissions of the file, and the contents of the file to ensure you are opening a valid PL/SQL library file. If these seem correct, check for other applications or users using the file. Then retry the operation.
Cause:
You attempted to load a program unit from a library, but the stored representation of the program unit is too large to be read into memory on this operating system.
Action:
Return to the operating system in which this library was originally generated and split the offending program unit into smaller program units.
Cause:
You attempted to attach a library from a database READ/WRITE, but the library could not be locked. The most likely cause is that another user has attached the library READ/WRITE.
Action:
Attach the library READONLY, if possible. Otherwise, locate the user who has attached the library READ/WRITE and retry the operation after the user has detached the library.
Cause:
A library operation attempted to update an old version of the library.
Action:
If the library being saved or closed is stored in the database, the DE_ATTACHED_LIBS table must be updated. Refer to your platform's installation notes for information about upgrading this table. If the library is stored in a file, use the SAVE AS command to save the library to a different file then rename the file to replace the original, old version.
Cause:
A library operation attempted to rename a temporary file to the actual filename, but could not get a write lock on the file.
Action:
Check that you have write permission on the file you are saving, and that no other use has it locked. Or save the data to another file using the SAVE AS command.
Cause:
A library operation attempted to rename a temporary file to the actual filename, but could not. A race condition ensued, and the data had to be left in a temporary file.
Action:
Reopen the library from the temporary file, and save it using the SAVE AS command.
Cause:
A library has been modified too many times.
Action:
Recreate the library and recompile all.
Cause:
You attempted an operation on a program unit that requires it to be compiled, but it isn't.
Action:
Compile the program unit and retry the operation.
Cause:
You attempted an operation on a program unit that depends on an external program unit, which is required to be loaded into Procedure Builder. The operation failed because the external program unit could not be located.
Action:
Allow Procedure Builder to resolve the reference by doing one of the following:
Cause:
You attempted an operation on a program unit that requires an externally referenced program unit to have debugging symbols, but the referenced program unit has no debugging symbols.
Action:
Recompile the referenced program unit in Procedure Builder, then retry the operation.
Cause:
You attempted an operation on a program unit that requires it to have debugging symbols, but the program unit has no debugging symbols.
Action:
Recompile the program unit in Procedure Builder, then retry the operation.
Cause:
You attempted to compile a program unit that has no source code.
Action:
Provide source code for the program unit, then recompile.
Cause:
You tried to access a stored program unit to which you do not have access. Most likely, the program unit is in another schema.
Action:
Gain access to the program unit.
Cause:
You attempted an operation that inspects or changes the value of a local, but there was no PL/SQL program unit whose execution was suspended at the time.
Action:
If you wish to inspect or change the value of a local within Procedure Builder, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
You attempted an operation that inspects or changes the value of a local, but this program unit does not have sufficient debugging information to perform the operation.
Action:
Recompile the program unit and retry the operation.
Cause:
You attempted to move to a frame on the call stack using the SET SCOPE command, but the specified frame does not exist.
Action:
Re-enter the command, specifying a valid frame on the call stack.
Cause:
You attempted to set the current scope using the SET SCOPE command, but there is no PL/SQL executing and, therefore, no call stack.
Action:
The SET SCOPE command can be used only when there is a PL/SQL call stack.
Cause:
You attempted to move up the call stack to a specific program unit frame using the SET SCOPE UP PROGRAMUNIT command, but no frame associated with the specified program unit exists above the current frame.
Action:
Re-enter the command, specifying the name of a program unit that is above the current frame in the call stack.
Cause:
You attempted to move down the call stack to a specific program unit frame using the SET SCOPE DOWN PROGRAMUNIT command, but no frame associated with the specified program unit exists below the current frame.
Action:
Re-enter the command, specifying the name of a program unit that is below the current frame in the call stack.
Cause:
You attempted to move up the call stack using the SET SCOPE UP command, but the specified frame is beyond the top of the stack.
Action:
Re-enter the command, specifying a valid frame on the call stack.
Cause:
You attempted to move down the call stack using the SET SCOPE DOWN command, but the specified frame is below the bottom of the stack.
Action:
Re-enter the command, specifying a valid frame on the call stack.
Cause:
You attempted a Procedure Builder operation that inspects the call stack or accesses the value of a local, but there was no PL/SQL program unit whose execution was active or interrupted at the time.
Action:
If you wish to inspect the call stack or access the value of a local from Procedure Builder, you must execute a PL/SQL program unit and interrupt its execution using a debug action.
Cause:
You attempted to create a new namespace that has the same name as another namespace under the same parent namespace.
Action:
Choose another name and retry the command.
Cause:
You entered the name of an attached library that could not be located.
Action:
Check the spelling of the library name and re-enter the command.
Cause:
You tried to create a namespace that has a non-existing parent.
Action:
Create the parent namespace first, then the child.
Cause:
You did not supply data for the bind operation.
Action:
Check input data for the bind operation.
Cause:
The SELECT statement does not return data.
Action:
Revise the SELECT statement.
Cause:
See the error message above for details.
Action:
See the error message above for details.
Cause:
The CONNECT string is incorrect.
Action:
Revise the CONNECT string.
Cause:
Internal problem.
Action:
Contact customer support.
Cause:
Internal problem.
Action:
Contact customer support.
Cause:
See the error message above for details.
Action:
See the error message above for details.
Cause:
Internal problem.
Action:
Contact customer support.
Cause:
Procedure Builder cannot obtain enough memory from the system to complete an open library operation.
Action:
Make more memory available, or ask your system administrator for assistance.
Cause:
You tried to open a library that is already open.
Action:
Since the library is already opened, there is no need to try to reopen it.
Cause:
While saving or closing a library, Procedure Builder temporarily unlocks all currently open libraries in accordance with the Oracle transaction model. When the save or close operation is completed, all remaining open libraries are relocked. This error is raised if another user manages to lock a library between the completion of the save or close operation and the reacquisition of the lock.
Action:
If the library has been changed, use the SAVE command to create a new library with your changes. If the library has not been changed, close the library as soon as possible and discard the changes to prevent overwriting any changes made by another user.
Cause:
You entered a SAVE or CLOSE command to save or close a new library that has no external location.
Action:
If you want to save the contents of the library, use the SAVE command with the AS option to save your changes, or the CLOSE command with the DISCARD option to discard your changes. If this error occurred during a QUIT operation, retry the QUIT after the library has been saved or discarded.
Cause:
You entered the SAVE command to save attached library information, but you specified a directory path and filename that exceeds the maximum number of characters allowed.
Action:
Retry the operation using a shorter name. To do this, use the INSERT LOADPATH command to insert the directory path into the load path. Then re-enter the SAVE command, specifying only the base name of the library.
Cause:
You attempted to open a generated, runtime only library (.PLX extension). This is not supported.
Action:
Open the source library (.PLL extension) instead.
Cause:
You attempted to revert a library that has not been saved.
Action:
Save the library, then revert it.
Cause:
You entered a Procedure Builder command that accesses the database, but there is no current connection.
Action:
Connect to a database and re-enter the command.
Cause:
Databases before Version 7.3.3 do not support server-side debugging.
Action:
See your Oracle customer service representative about upgrading your database to a version that supports server-side debugging.
Cause:
You attempted an operation on a program unit source line, but specified a line number that is out of range.
Action:
Retry the operation, specifying a valid line number for this program unit.
Cause:
You attempted an operation (most likely from a debug trigger) that invalidates the compiled state of a program unit, but it was disallowed because the program unit is currently executing.
Action:
Defer the operation until after execution of the program unit has completed.
Cause:
You attempted to define a breakpoint or a debug trigger for a program unit, but the specified source line does not correspond to executable code.
Action:
Try defining the debug action again, specifying an executable source line.
Cause:
You attempted an operation on a program unit that requires it to be compiled, but it isn't.
Action:
Compile the program unit and retry the operation.
Cause:
You attempted to modify or edit a Built-in program unit, but destructive operations on Built-ins are not allowed.
Action:
You can only edit or modify program units that are created within or loaded into Procedure Builder.
Cause:
You attempted an operation that requires the PL/SQL compiler, but you were in a runtime-only environment.
Action:
Retry the operation in a compile-time version of the product.
Cause:
You attempted to modify the source of a program unit, but it is a read-only program unit.
Action:
You cannot modify the source of read-only program units.
Cause:
You attempted to create or modify the source of a program unit, but the source you supplied does not define a program unit of the required type.
Action:
Edit the source of the program unit to define a program unit of the specified type.
Cause:
The compiled size of this program unit exceeds the maximum possible on the current platform.
Action:
Try reducing the size of the program unit by breaking it up into a number of smaller program units.
Cause:
You tried to access a stored program unit to which you do not have access. Most likely, the program unit is in another schema.
Action:
Gain access to the program unit.
Cause:
Procedure Builder attempted to load a resource from its resource file, but the file could not be opened.
Action:
Reinstall Procedure Builder and try again.
Cause:
You attempted to load a program unit, but a program unit or database object that it references could not be resolved.
Action:
The unresolved object may reside in a library to which are not attached, or in a database to which you are not connected. Retry the operation after attaching the necessary library or connecting to a different database, as appropriate.
Cause:
You attempted to load a program unit from a source file, but the file could not be opened.
Action:
Retry the load operation, specifying the name of a file that exists and that you have permission to read.
Cause:
You specified a PL/SQL identifier (e.g., the name of a program unit) that is too long. Identifiers can be no more than 30 characters.
Action:
Retry the operation, specifying an identifier of no more than 30 characters.
Cause:
You cannot change the value of variables in this frame.
Action:
Choose another frame.
Cause:
The program unit has no debugging information.
Action:
Recompile the program unit in debug mode.
Cause:
You are attempting to access and/or modify a variable which does not exist in the current frame.
Action:
Choose another frame or another variable.
Cause:
You tried to set a variable to a value which is not legal for its type.
Action:
Set the variable to a legal value.
Cause:
You cannot assign a null value to an object whose type is NOT NULL.
Action:
Declare the object as a different type, or assign a value other than NULL.
Cause:
The version of the PBRUN package installed on the server is incompatible.
Action:
Install the current version of the PBRUN package on the server.
Cause:
You tried to set a breakpoint on an illegal line.
Action:
Set the breakpoint on a valid line.
Cause:
You tried to perform an operation on a breakpoint which does not exist.
Action:
Set the breakpoint before trying the operation.
Cause:
This breakpoint is not in use.
Action:
Delete the breakpoint.
Cause:
You modified the program unit after the breakpoint was set.
Action:
Reset the breakpoint.
Cause:
You tried to make use of functionality which has not yet been implemented in Procedure Builder.
Action:
Find an alternate method of accomplishing your task.
Cause:
The PL/SQL server-side debugging packages are not correctly installed on the server.
Action:
Reinstall the PL/SQL server-side debugging packages on the server.
Cause:
The PL/SQL server-side debugging package installed on the server is incompatible with the current version of Procedure Builder.
Action:
Install compatible PL/SQL server-side debugging packages on the server.
Cause:
The attempt to access the database timed out.
Action:
Try again to access the database. If you continue to be unable to access the database, check with your administrator to see if the database is down.
Cause:
The breakpoint could not be set because the program unit was not correctly compiled.
Action:
Correct the errors in your program unit source, recompile, and reset the breakpoint.
Cause:
Databases preceding Version 7.3.3 do not support server-side debugging.
Action:
See your Oracle customer service representative about upgrading your database to a version which does support server-side debugging.
Cause:
You attempted an operation in Procedure Builder, but it failed due to this Oracle Server error.
Action:
For more information the error, see your Oracle Server manual on error messages.
Cause:
You attempted an operation in Procedure Builder, but it failed because the database connection is no longer valid.
Action:
Reconnect to the database and retry the operation.
Cause:
You attempted to connect to a database but failed, most likely for one of the following reasons: you mistyped the connection string; you cannot access the machine on which the database resides; or the database does not exist.
Action:
Retry the operation, ensuring that you enter the correct connection string. Also, check your server and network to ensure that the database exists and can be accessed.
Cause:
You executed a program unit, but it aborted because an exception was raised but never handled.
Action:
Redefine the program unit to handle the exception, or address the cause of the exception.
Cause:
You attempted to move to a frame on the call stack using the SET SCOPE command, but the specified frame does not exist.
Action:
Re-enter the command, specifying a valid frame on the call stack.
Cause:
You attempted to resume execution with the GO or STEP commands, but the suspended PL/SQL execution state was invalidated by a previous operation in Procedure Builder. For example, you might receive this error if you removed a program unit on the current call stack while at a breakpoint, then tried to resume execution with the GO command.
Action:
Restart execution of the original program unit and avoid the operation that caused the invalidation.
Cause:
You attempted to execute a PL/SQL program unit, but PL/SQL execution is disabled in this context. For example, you might receive this error if you are not in the runtime simulation mode of the Oracle product you are using.
Action:
Re-execute the PL/SQL program unit while in runtime simulation mode of the Oracle product.
Cause:
You attempted suspend execution of a program unit using a debug trigger or breakpoint trigger (possibly by calling DEBUG.SUSPEND), but suspension is prohibited in this context.
Action:
Redefine the offending debug trigger or breakpoint, removing the call(s) in the trigger body that suspend execution, then retry the operation.
Cause:
You executed a program unit, but it aborted because an application error was raised.
Action:
Refer to your application's documentation for further information about the cause of the error and appropriate corrections.
Cause:
You tried to run an anonymous program unit (e.g., one entered at the command prompt) with arguments. This is currently unsupported.
Action:
Rewrite the command as a self-contained program unit and run that from the command line.
Cause:
You attempted an operation that requires an in-progress or stopped debug context (in other words, a program unit stopped at a break point) when there wasn't one.
Action:
Only use the command when execution is interrupted.
Cause:
The Quick Tour executable file was not found.
Action:
Reinstall the Quick Tour and try again.
Cause:
The tab size preference contains a value that is outside the valid range of 2 to 100 characters.
Action:
Please provide a tab size value in the range of 2 to 100 characters.
Cause:
You selected the Add or Remove buttons in the Grant Access List dialog box, but you did not select or enter a user first.
Action:
Select or enter a user name and try again.
Cause:
You attempted to add a user name in the Grant Access List dialog box that already exists in the access list.
Action:
Select or enter a new user name and try again.
Cause:
You selected the Attach button in the Attach Library dialog box, but you did not specify a library to be attached.
Action:
Specify a library to be attached in the Library field before selecting the Attach button.
Cause:
You selected the OK button in the Breakpoint dialog box, but you did not specify a program unit.
Action:
Specify a program unit for the breakpoint in the Program Unit field before selecting the OK button.
Cause:
You selected the OK button in the Breakpoint dialog box, but you did not specify a line number.
Action:
Specify a line number for the breakpoint in the Line field before selecting the OK button.
Cause:
You selected the OK button in the Breakpoint dialog box, but you did not specify a complete PL/SQL construct in the Trigger field.
Action:
Specify a complete PL/SQL construct in the Trigger field before selecting the OK button.
Cause:
You attempted to move up to and select the previous message in the Error Summary window, but you are already at the first message.
Action:
Only select the up key when you are not at the first message.
Cause:
You attempted to move down to and select the next message in the Error Summary window, but you are already at the last message.
Action:
Only select the down key when you are not at the last message.
Cause:
You selected the Connect button in the Connect dialog box, but you did not specify a username.
Action:
Enter a valid username in the Username field before selecting the Connect button.
Cause:
Procedure Builder attempted to create a window but failed, most likely for one of the following reasons: you have used up all of your window resources; you have encountered an internal error.
Action:
If you have a large number of windows open (that is, more than 30), close as many windows as necessary to free up window resources, then retry the previous operation. If the problem persists, contact Oracle Customer Support.
Cause:
You selected a button to perform an operation on a database object, but you did not select or enter the name of a database object to be operated on.
Action:
Select or enter the name of a database object and try again.
Cause:
You selected the Rename button in the Rename Library dialog box, but you did not enter the new name for the library.
Action:
Enter the new name for the library in the New Name field and try again.
Cause:
You selected the OK button in the Goto Line dialog box, but you did not specify a line number in the GoTo Line Field.
Action:
Enter the line number in the field, and try again.
Cause:
You specified a line number that is either zero, negative, or is not a number (such as containing letters or other non-numeric symbols).
Action:
Enter a valid positive line number in the field, and try again.
Cause:
You tried to perform a Replace or Edit operation on a selected program unit in the Results box of the Find and Replace in Program Units dialog box, but the system failed to locate the selected program unit.
Action:
The list of program units in the Results box may not be current. Try to perform a search operation again to refresh the list in the Results box.
Cause:
You selected the Interpret button in the Interpret Debug Script dialog box, but you did not specify a file to interpret.
Action:
Enter the name of the desired file in the File field and try again.
Cause:
You selected the Load button in the Load Program Unit dialog box, but you did not specify a file to load.
Action:
Enter the name of the desired file in the File field and try again.
Cause:
You loaded a program unit stored in a file using the Load Program Unit dialog box, but the program unit contains one or more compilation errors.
Action:
Edit and compile the loaded program unit using the Program Unit editor.
Cause:
You used the Load Program Unit dialog box to load the contents of a file, but the file you specified does not contain valid PL/SQL source.
Action:
Retry the operation, entering the name of the file containing the PL/SQL source you wish to load.
Cause:
You selected the Log button in the Log dialog box, but you did not specify a log file.
Action:
Enter the name of the desired file in the File field and try again.
Cause:
You attempted to move up to and select the previous message in the message pane, but you are already at the first message.
Action:
Only select the up key when you are not at the first message.
Cause:
You attempted to move down to and select the next message in the message pane, but you are already at the last message.
Action:
Only select the down key when you are not at the last message.
Cause:
You attempted to move up to and select the previous message in the message pane, but you are already at the first message.
Action:
Only select the up key when you are not at the first message.
Cause:
You attempted to move down to and select the next message in the message pane, but you are already at the last message.
Action:
Only select the down key when you are not at the last message.
Cause:
You selected the OK button in the New Program Unit dialog box, but you did not specify a program unit name.
Action:
Specify a program unit name in the Name field before selecting the OK button.
Cause:
You attempted to create a new stored program unit with the same name as an existing stored program unit.
Action:
Specify a different stored program unit name in the Name field and try again.
Cause:
You attempted to create a new stored program unit with an invalid name.
Action:
Specify a valid stored program unit name in the Name field and try again.
Cause:
You selected the Open button in the Open Library dialog box, but you did not specify a library name.
Action:
Specify a library name in the Library field before selecting the Open button.
Cause:
You attempted to import from or export to a file while in a PL/SQL field, but the file could not be opened.
Action:
If importing, specify a file that exists. If exporting, specify a file for which you have write permission. Then try again.
Cause:
You attempted to edit a program unit that is already being edited in another editor window.
Action:
Move to the open editor window to edit the program unit.
Cause:
The Quick Tour file was not installed properly.
Action:
Reinstall the Quick Tour file.
Cause:
You selected a button in the Find and Replace dialog box to perform a search or replace operation, but you did not enter a search string in the Find What field.
Action:
Enter a search string in the Find What field and retry the operation.
Cause:
You attempted to search for a regular expression using the Find and Replace dialog box, but the string you entered in the Find What field could not be parsed.
Action:
Check the Find What field for any special wildcard characters (e.g., (, ), ~) that you attempted to use as literal characters, but did not precede with an escape character (\).
Cause:
You tried to compile a stored program unit in the database, but the program unit's source is not a complete PL/SQL construct.
Action:
Enter a complete PL/SQL construct as the source of the stored program unit, then recompile.
Cause:
You selected the OK button in the Attribute dialog box without specifying an atribute name.
Action:
Specify a name for the attribute in the Attribute Name text box and try again.
Cause:
You attempted to import from or export to a file while in a text edit field, but the file could not be opened.
Action:
If importing, specify a file that exists. If exporting, specify a file for which you have write permission.
Cause:
You selected the Save button in the Database Trigger dialog box, but you did not specify a trigger name.
Action:
Specify a name for the trigger in the Trigger Name field before selecting the Save button.
Cause:
You selected the Save button in the Database Trigger dialog box, but you did not specify a base table.
Action:
Specify a base table for the trigger in the Table Name field before selecting the Save button.
Cause:
You selected the Save button in the Database Trigger dialog box, but you did not specify a complete PL/SQL construct for the trigger body.
Action:
Specify a complete PL/SQL construct for the trigger body before selecting the Save button.
Cause:
You selected the Save button in the Database Trigger dialog box, but you did not specify a SQL statement that causes the trigger to fire.
Action:
Specify at least one SQL statement that causes the trigger to fire. You can specify as many as three.
Cause:
You attempted to edit a trigger, but none were selected.
Action:
Select the New button to create a new trigger.
Cause:
The error in the trigger may be a syntax error, or an unresolved reference.
Action:
Edit the trigger.
Cause:
You selected the OK button in the Method dialog box without specifying a method name.
Action:
Specify a name for the method in the Method Name text box and try again.
Cause:
You selected the button to add a parameter in the Method dialog box but you did not specify a parameter name.
Action:
Specify a name for the parameter in the Parameter Name text box and try again.
Cause:
You selected the OK button in the Trigger dialog box, but you did not specify a program unit.
Action:
Specify a program unit for the trigger in the Program Unit field before selecting the OK button.
Cause:
You selected the OK button in the Trigger dialog box, but you did not specify a line number.
Action:
Specify a line number for the trigger in the Line field before selecting the OK button.
Cause:
You selected the OK button in the Trigger dialog box, but you did not specify a complete PL/SQL construct in the Trigger Body field.
Action:
Specify a complete PL/SQL construct in the Trigger Body field before selecting the OK button.
Cause:
You did not enter a valid type name.
Action:
Specify a name for the type in the Type Name text box before going to the next step.
Cause:
You tried to create a user-defined type via the Type Wizard, but the operation failed due to some unknown reason.
Action:
Examine the generated SQL command in the last page of the Type Wizard. Fix any error you can find and try again.
Cause:
You attempted a date operation in Procedure Builder, but it failed.
Action:
For more information, see your Oracle Server manual on error messages.
Cause:
You selected a button in the Find and Replace dialog box to perform a search or replace operation, but you did not enter a search string in the Find What field.
Action:
Enter a search string in the Find What field and re-try the operation.
Cause:
You attempted to search for a regular expression using the Find and Replace dialog box, but the string you entered in the Find What field could not be parsed.
Action:
Check the Find What field for any special wildcard characters (e.g., (, ), ~) that you attempted to use as literal characters, but did not precede with an escape character (\).