Error 6508
Contents |
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle error ora-06508 pl/sql could not find program unit being called PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog ora-06508 forms
ORA-06508: PL/SQL: could not find program could not find program unit being called ora-06512 unit being called tips Oracle Error Tips by Stephanie F. The Oracle docs note this on the ora-06508 error: ORA-06508: PL/SQL: could not find ora-06508 unhandled exception program unit being called. Cause: An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors. Action: Check that all referenced programs, including their package bodies, exist and are compatible. In Oracle warehouse builder (OWB) andOra-06508 Webutil
other PL/SQL operations, you get the ORA-06508 error when one of the program units has not been properly compiled or it cannot be located (a problem with your $PATH environment variable). An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors. Check that all referenced programs, including their package bodies, exist and are compatible. You can use this script to recompile any invalid objects. For full scripts, download the Oracle script collection. You can run this query to find invalid objects, which may cause the ORA-06508 error: select comp_id, comp_name, version, status, namespace, schema from dba_registry; Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum. Verify e
April 2010 12:08 bholeuday Messages: 28Registered: April 2009 Location: Talavali Junior Member Hi, I am getting below error when SP (Packaged Procedure) is called from
Frm-40735 Ora-06508
application... ORA-06508: PL/SQL: could not find program unit being called After checking ora-04063 package body DB, i found package to be valid and call to SP giving same error ORA-06588. If i fire alter when-custom-item-event trigger ora-06508 command to compile the package.. alter package name compile; and then if i try to run the SP in db it runs sucessfully. again after some time ORA-06508 it occurs http://www.dba-oracle.com/t_ora_06508_pl_sql_could_not_find_program_unit_being_called.htm again. after compiling it starts working fine again. Body of the procedure :- begin indexFields.extend; indexFields(indexFields.last) := ATTRIBUTE_REC_TYPE(i_attributeName,i_attributeValue); o_errorcode := '0'; o_errormsg := null; EXCEPTION WHEN OTHERS THEN o_errorcode := to_char(SQLCODE); o_errormsg := SQLERRM; indexFields := ATTRIBUTE_TABLE_TYPE(); end prepBatchIndexField; WHEREAS (Definition of types) :- indexFields ATTRIBUTE_TABLE_TYPE := ATTRIBUTE_TABLE_TYPE(); CREATE OR REPLACE TYPE ATTRIBUTE_TABLE_TYPE IS TABLE OF ATTRIBUTE_REC_TYPE / CREATE OR http://www.orafaq.com/forum/t/156531/ REPLACE TYPE ATTRIBUTE_REC_TYPE IS OBJECT (ATTRIBUTE_NAME VARCHAR2(256),ATTRIBUTE_VALUE VARCHAR2(512) ); / I donno what is wrong here...sometimes it is working fine, sometimes gives error on compiling it works again. Please help me in this regards. Thanks & Regards Report message to a moderator Re: ORA-6508 Error [message #450182 is a reply to message #450181] Mon, 05 April 2010 12:12 BlackSwan Messages: 24930Registered: January 2009 Location: SoCal Senior Member The EXCEPTION handler is 100% totally worthless & should be removed. Procedure will go INVALID when any dependent object is changed. It would be helpful if you followed Posting Guidelines - http://www.orafaq.com/forum/t/88153/0/ Report message to a moderator Re: ORA-6508 Error [message #450183 is a reply to message #450181] Mon, 05 April 2010 12:17 ramoradba Messages: 2454Registered: January 2009 Location: AndhraPradesh,Hyderabad,I... Senior Member ORA-06508: PL/SQL: could not find program unit being called Cause: An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors. Action: Check that all referenced programs, includin
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers http://stackoverflow.com/questions/19376440/ora-06508-pl-sql-could-not-find-program-unit-being-called or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x http://lefterhs.blogspot.com/2009/06/oracle-quoting-error-ora-06508-on.html Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ORA-06508: PL/SQL: could not find program unit being called up vote 7 down vote favorite 1 I am using oracle 10g and toad 11.5. I am trying to call an api from an anonymous could not block. If i recompile the api after adding dbms_output.put_line and then try to execute the anonymous block ,it shows error as "ORA-06508: PL/SQL: could not find program unit being called". However if i end current session and open a new session , then the anonymous block will execute with out the error. Due to this issue, i am made to reconnect the session everytime i make a change to API. Can anyone help if this issue can be resolved by making could not find any configurations in toad or database level. oracle plsql anonymous share|improve this question edited Jan 9 '14 at 6:02 user272735 5,87263464 asked Oct 15 '13 at 8:25 battech 3052312 2 Are you also getting something like 'existing package state had been discarded'? If so running it a second time in the same session ought to work. But that would suggest your package has some state, i.e. a variable declared in the package rather than in a procedure (and nothing to do with the dbms_output). –Alex Poole Oct 15 '13 at 9:45 add a comment| 3 Answers 3 active oldest votes up vote 15 down vote I suspect you're only reporting the last error in a stack like this: ORA-04068: existing state of packages has been discarded ORA-04061: existing state of package body "schema.package" has been invalidated ORA-04065: not executed, altered or dropped package body "schema.package" ORA-06508: PL/SQL: could not find program unit being called: "schema.package" If so, that's because your package is stateful: The values of the variables, constants, and cursors that a package declares (in either its specification or body) comprise its package state. If a PL/SQL package declares at least one variable, constant, or cursor, then the package is stateful; otherwise, it is stateless. When you recompile the state is lost: If the body of an instantiated, stateful package is recompiled (either explicitly, with the "ALTER PACKAGE Statement", or implicitly), the next invocation of a subprogra
find program unit being called in Package OM_TAX_UTIL Procedure Tax_Line This error is persistent and relogin does not allow the user to bypass the error. This framework uses Java Apache processes to connect to the DB, and not the default connection method, seen when a form opens a session and closes it when it is done. These Apache processes stay connected to the DB, until an Apache restart/shutdown occurs. We enable tracing for ORA-06508: ALTER SYSTEM SET EVENTS '6508 trace name errorstack level 3'; The trace files created by the "submit orders" attempts contain the following group of ORA errors: ORA-04061: existing state of package body "APPS.ARP_PROCESS_TAX" has been invalidated ORA-04065: not executed, altered or dropped package body "APPS.ARP_PROCESS_TAX" ORA-06508: PL/SQL: could not find program unit being called In OM_TAX_UTIL.TAX_LINE there are calls to ARP_PROCESS_TAX's procedures. ARP_PROCESS_TAX package gets its body invalidated by a AR purge process, which executes DDL operations on a few AR interface tables. This process recompiles every object it invalidates, before it finishes. So, ARP_PROCESS_TAX spec and body have VALID status, when its procedures are called by TAX_LINE. The key for this problem is the fact that the Apache processes that handle the Quoting requests, stay always connected to the database. For some reason (probably Bug 2747350) the new package state is not picked up. A demonstration is following to simulate the issue. We create a table: CREATE TABLE SYSTEM.TEST_TABLE TABLESPACE TOOLS LOGGING NOCOMPRESS NOCACHE NOPARALLEL NOMONITORING AS SELECT * FROM DBA_OBJECTS; A view on this table: CREATE OR REPLACE FORCE VIEW SYSTEM.TEST_VIEW ( OWNER, OBJECT_NAME, SUBOBJECT_NAME, OBJECT_ID, DATA_OBJECT_ID, OBJECT_TYPE, CREATED, LAST_DDL_TIME, TIMESTAMP, STATUS, TEMPORARY, GENERATED, SECONDARY ) AS SELECT "OWNER", "OBJECT_NAME", "SUBOBJECT_NAME", "OBJECT_ID", "DATA_OBJECT_ID", "OBJECT_TYPE", "CREATED", "LAST_DDL_T