package body "APPS. AD_ZD_ADOP' mistakes adoption apply fail

Similar Questions

• PACKAGE BODY APPS. AD_ZD_ADOP contains errors

  APP TIER - Linux - SLES 11 - SP2 - x86_64

  DB LEVEL - Linux for system Z - SLES 11 - SP2 - s390

  I encounter errors in the body to Package APPS. AD_ZD_ADOP, that has brought all the patches to a status quo on our schedule instance.

  The sequence of events have been

  The following hotfixes have been applied.

  1. Patch 19462638
  2. Patch 19197270
  3. Patch 21132723
  4. 19330775
  5. 20677045
  6. 19259764

  Doc 1617461.1 was followed - B path of

  After Patch 19259764 has been applied, all steps until step 8 of Doc 1617461.1 have been completed.

  Failure of the fs_clone step (step 9). My colleague opened a SR - advice was far from expected.

  Yesterday, I took this with success and more cloned the fix for the file system to perform file system (1383621.1) - however, I'm still not able to run fs_clone with success.

  Even a basic ADADMIN session fails.

  Here are the errors while trying to compile APPS package bodies. AD_ZD_ADOP

  SQL > alter package APPS. AD_ZD_ADOP compile body; WARNING: The bodies of Package modified with compilation errors. SQL > show errors; Errors for BODY of PACKAGE applications. AD_ZD_ADOP: LINE/COL ERROR -------- ----------------------------------------------------------------- 2503/3 PL/SQL: statement ignored 2503/7 PLS-00201: identifier ' SYS. DBMS_METADATA_UTIL' must be declared SQL >

  Also while trying to launch ADADMIN, I get errors themselves.

  Error of Administration AD:

  ORA-04063: package body "APPS. AD_ZD_ADOP"contains errors

  Could not insert the record of the action in the table of patches

  Error of Administration AD:

  Error when you try to insert adadmin task CMP_INVALID action

  Update running adadmin of failure actions

  Error of Administration AD:

  The following ORACLE error:

  ORA-01756: city not properly finished chain

  occurred while executing the SQL statement:

  UPDATE ad_adop_session_patches set status = 'F' where status = 'R' and

  as numero_de_bogue ' ADADMIN

  Error of Administration AD:

  Table ad_adop_session_patches update errors

  You must check the file

  /U02/fs_ne/EBSapps/log/ADadmin/log/ADadmin.log

  to find errors.

  Can someone please. I have also a SR - but nice try various channels to find a solution.

  Hello

  The necessary subsidies on the SYS package may be missing. DBMS_METADATA_UTIL.

  Try this command (as sysdba) and compile the package:

  Grant execute on SYS. DBMS_METADATA_UTIL applications;

  Kind regards

  Bashar

• upgrade from 12.2 to 12.2.4 ORA-04063: package body "APPS. AD_ZD_PREP"contains errors

  Hello

  do 12.2 upgrade to 12.2.4 (doc: 1617458.1) did all the patch (doc: 1594274.1()

  1617461.1 section 3.2 step 5 (patch 18283295, 20034256,20075842) applied correctly

  apply also 4.1 critical fixes to AD (patch 20125137( )

  and in section 3.2 step 6 generate this error:

  AutoPatch error:

  Error: Cannot run enable_custom_user

  AutoPatch - aiuoraEnableCustom: INFO: ORA-04063: package body "APPS. AD_ZD_PREP"contains errors

  ORA-06508: PL/SQL: called program unit is not found: 'APPS. AD_ZD_PREP ".

  ORA-06512: at line 1

  ##

  SQL > select object_name, object_type of object where status = 'INVALID ';

  OBJECT_NAME OBJECT_TYPE

  ------------------------------ -------------------

  MATERIALIZED VIEW OE_ITEMS_MV

  MATERIALIZED VIEW OZF_EARNING_SUMMARY_MV

  ##

  ###

  SQL > SELECT abbreviation, codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('T2K', 'ad');

  ABBREVIA CODELEVEL

  -------- ---------

  C.5 announcement

  T2K C

  ###

  ####

  file: 1617461_1_adop step6.txt

  contain the adoption order run from doc: 1617461.1 section 3.2 step 6

  file: 19045166_diagnostic_info_serveurv12.serveurvm.zip

  contain the diagnosis of the 19045166

  file: 17537119_check.txt

  contain the diagnosis of the 17537119

  ####

  Please confirm that all the patches of RDBMS postinstall.sql scripts have been executed according to the instructions in the Readme of each patch.

  Thank you

  Hussein

• ORA-04063: package body "APPS. AD_FILE_SYS_SNAPSHOTS_PKG"contains errors

  Dear Sir
  
  OS: OUL5x6
  EBS R12 12.0.6
  running patch 7303030 12.1.1 upgrade
  
  
  
  ........
  ....
  Complete the cleaning of data base for the previous session.
  
  
  
  Try to get a lock...
  
  
  Attempt to instantiate the snapshot current view...
  ORA-04063: package body "APPS. AD_FILE_SYS_SNAPSHOTS_PKG"contains errors
  ORA-06508: PL/SQL: called program unit is not found: 'APPS. AD_FILE_SYS_SNAPSHOTS_PKG ".
  ORA-06512: at line 2
  
  AutoPatch error:
  Error executing statement (curr-vw inst)
  
  Call adusnapInstCurrVwSnapshot (AT_ebstestap2, 12.0.6) error.
  Error calling adphistLoadPtchHistFromFStoDB2
  
  Update of the snapshot current view...
  ORA-04063: package body "APPS. AD_FILE_SYS_SNAPSHOTS_PKG"contains errors
  ORA-06508: PL/SQL: called program unit is not found: 'APPS. AD_FILE_SYS_SNAPSHOTS_PKG ".
  ORA-06512: at line 2
  
  AutoPatch error:
  Error executing statement (updt curr-vw)
  
  
  
  Enter the directory where your Oracle Applications patch has been unloaded
  
  The default directory is [/ u01/TMP/7303030]
  
  
  ------
  After the execution of adpatch and receive errors above.
  Please advise a solution.
  Thank you very much
  Kind regards
  Tom

  Tom

  .. but for the workaround, I have set the parameter PLSQL_CODE_TYPE = INTERPRETED and restarted the database.
  then why I still get this error.

  Did you start the patch since the beginning?

  I think that this must be set to NATIVE as shown (Note: 396009.1). However, if the above does not help, just wait for help.

  Kind regards
  Hussein

• ORA-04063: package body "APPS. HZ_PARTY_STAGE"contains errors

  Hello

  Received the error when compile. Checked in the Note: 427418.1 did not work. Help, please. It's 12.1.3, 11.2.0.3 Linux database.
  

  SQL > alter package APPS. HZ_PARTY_STAGE compile body;

  WARNING: The bodies of Package modified with compilation errors.

  SQL > show err

  Errors for BODY of PACKAGE applications. HZ_PARTY_STAGE:

  LINE/COL ERROR

  -------- -----------------------------------------------------------------

  85/5 PL/SQL: statement ignored

  85/5 PLS-00201: identifier ' AD_CTX_DDL. DROP_PREFERENCE' must be

  has said

  95/5 PL/SQL: statement ignored

  95/5 PLS-00201: identifier ' AD_CTX_DDL. CREATE_PREFERENCE' must be

  has said

  96/5 PL/SQL: statement ignored

  96/5 PLS-00201: identifier ' AD_CTX_DDL. SET_ATTRIBUTE' must be declared

  3313/28 PL/SQL: statement ignored

  LINE/COL ERROR

  -------- -----------------------------------------------------------------

  3313/28 PLS-00201: identifier ' AD_CTX_DDL. SYNC_INDEX' must be declared

  3322/27 PL/SQL: statement ignored

  3322/27-PLS-00201: identifier ' AD_CTX_DDL. SYNC_INDEX' must be declared

  3352/24 PL/SQL: statement ignored

  3352/24 PLS-00201: identifier ' AD_CTX_DDL. SYNC_INDEX' must be declared

  3362/23 PL/SQL: statement ignored

  3362/23 PLS-00201: identifier ' AD_CTX_DDL. SYNC_INDEX' must be declared

  3399/26 PL/SQL: statement ignored

  3399/26-PLS-00201: identifier ' AD_CTX_DDL. SYNC_INDEX' must be declared

  3409/26 PL/SQL: statement ignored

  3409/26-PLS-00201: identifier ' AD_CTX_DDL. SYNC_INDEX' must be declared

  LINE/COL ERROR

  -------- -----------------------------------------------------------------

  3447/27 PL/SQL: statement ignored

  3447/27-PLS-00201: identifier ' AD_CTX_DDL. SYNC_INDEX' must be declared

  SQL > grant execute on AD_CTX_DDL. DROP_PREFERENCE applications;

  Grant execute on AD_CTX_DDL. Applications DROP_PREFERENCE

  *

  ERROR on line 1:

  ORA-04042: procedure, function, package, or package body does not exist

  The solution in the doc, you mentioned in your first post. Run the dctxpkg.sql script and pass the correct settings and make sure that it runs successfully.

  Thank you

  Hussein

• adoption apply phase failed. market to follow

  We are in the middle of the patching recommended on EBS R12.2.4 instance with 12.1.0.2.0 db. We conducted under activities up to now:

  adoption phase = prepare

  adoption phase = apply patches = 1

  adoption phase = patch = 2

  adoption phase = patch = 3

  .

  .

  .

  .

  .

  One of the patch failed:

  adoption phase = patch = 20592764

  We applied 30 patches up to now in adoption apply phase an and I still have to apply other hotfixes. Patch 20592764 failed due to incompatibility with the line of code R12.2 C.

  
  Error: AutoPatch error:
  --------
  This patch is not compatible with your current codelines.
  
  This patch is compatible with: "ad" - line of code entity ' R12. AD. B'.
  Your line of code on the current site for the entity 'ad' is: ' R12. AD. C
  

  It comes to the current state of the adoption:

  bash - $4.1 adop-status

  Enter the password for APPS:

  Current patch ID of Session: 75

  Name of node node Type Phase status started completed elapsed

  --------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ------------

  appsnodex master PREPARE FINISHED 1st Aug 15 20:27:59-05:00 1 August 15 20:52:23 - 05:00 0:24:24

  APPLY THE FAILURE 1 AUG 15 20:57:48 - 05:00 2 AUGUST 15 05:05:53 - 05:00 08:08:05

  FINALIZE NOT STARTED

  COMMISSIONING IS NOT STARTED

  CLEANING NOT STARTED

  Folder synchronization system used in this Patching Cycle: full

  For more information, run ADOPTION Status Report using - option detail

  Generating the ADOPTION status report to the location: /dhdr2i/applmgr/fs_ne/EBSapps/log/status_20150802_072959/adzdshowstatus.out

  Please wait...

  Done...!

  adopted out with status = 0 (success)

  We do not use cancel that we already applied 30 patches and it will start the cycle from scratch. We are yet to apply the fixes over 40. Also several times giving up is leading to corruption of data dictionary in our case and a bug is already raised with Support from Oracle.
  We can use: adopted phase = apply restart no = no = yes patches abandonment = 20592764

  Please suggest how to proceed with patching. Now we're stuck.

  Concerning

  Purnima Johari

  I suggest you start with the next patch using the 'abandonment = yes"parameter.

  It seems that I forgot to mention that in my previous post!

  Furthermore, why apply AD. Delta.6 instead of delta.5?

  Kind regards

  Bashar

• How to grant access to a package body to another user in execution

  Hello
  
  I have a package body that contains a single procedure and the owner of this APPS package.
  
  I have a requirement to grant access to this procedure which is inside the package to the user 'XXX' so that I can execute this procedure of user XXX in execution.
  
  When I tried under statement then it grant access to the package spec, not to the body. Please let me know how to give access to the package running body?
  Grant execute on KEI_TEK_IB_INTF_PKG to XXX.
  
  Thank you!

  PL, ensure that simultaneous program code is fully eligible package being called (i.e. APPS.) KEI_TEK_IB_INTF_PKG). If the scheme qualifier is omitted, you must create a public synonym (for example to create a public synonym KEI_TEK_IB_INTF_PKG for applications. KEI_TEK_IB_INTF_PKG) for this to work as expected.

  HTH
  Srini

• ORA-04063: package body 'SYS. DBMS_SQLTUNE error' during the upgrade

  Hello
  I am trying to upgrade the oracle 10.2.0.2 on 11.2.0.1 with dbua tool database. During the upgrade "Oracle Server" ORA-04063: package body 'SYS. DBMS_SQLTUNE"error has occurred.
  In the oracle server log:
  
  ---------------------------------------------------------------------------------------------------------------
  
  REM create the automated SQL Tuning task
  REM If the task exists already (catproc is re-of running) is not error.
  Start
  2 sys.dbms_sqltune_internal.i_create_auto_tuning_task;
  exception 3
  so 4 than others then
  5 if (sqlcode =-13607) then - task already exists
  6 null;
  7 other
  8 lift;
  9 end if;
  10 end;
  11.
  Start
  *
  ERROR on line 1:
  ORA-04063: package body 'SYS. DBMS_SQLTUNE"contains errors
  ORA-06508: PL/SQL: called program unit is not found: 'SYS. DBMS_SQLTUNE ".
  ORA-06512: at line 8 level
  
  ------------------------------------------------------------------------------------------------------------------------------------------------------------
  
  After unsuccessful upgrade I have restore and recover the database. SYS. The DBMS_SQLTUNE package and package body were valid. But when I compile them the package becomes invalid.
  I get the error and reach 390221.1 metalink Note:
  
  ------------------------------------------------------------------------------------------------------------------------------------------------------
  
  Solution
  -Drop synonyms
  Drop public synonym existsnode.
  excerpt from Drop public synonym;
  
  ----------------------------------------------------------------------------------------------------------------------------------------------------
  
  But there are no synonyms, which is mentioned in this note in my PB.
  
  How can I solve this problem? Thank you.

  If you have not read the note ORA-04063: package body 'SYS. DBMS_SQLTUNE' errors - upgrade to 10 G and 11 G fails on ID Dbms_sqltune 1271490.1+?

  Nicolas.

• ORA-04063: package body 'SYS. DBMS_CUBE_EXP"got error in expdp

  Oracle 11.2.0.2 on Redhat. Received the error when export a schema

  [oracle@cchorbi1 admin]$ expdp bi/pass@cchbi2 schemas=BISTG directory=DATA_PUMP_DIR parallel=12 
  dumpfile=bistg_bi2_0315_%U.dmp logfile=bistg_bi2_0315.log
  ....
  Starting "BI"."SYS_EXPORT_SCHEMA_02":  bi/********@cchbi2 schemas=BISTG directory              
  =DATA_PUMP_DIR parallel=12 dumpfile=bistg_bi2_0315_%U.dmp logfile=bistg_bi2_0315.              log
  Estimate in progress using BLOCKS method...
  Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
  ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS []              
  ORA-31642: the following SQL statement fails:
  BEGIN "SYS"."DBMS_CUBE_EXP".SCHEMA_CALLOUT(:1,0,1,'11.02.00.00.00'); END;
  ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
  ORA-06512: at "SYS.DBMS_METADATA", line 1245
  ORA-04063: package body "SYS.DBMS_CUBE_EXP" has errors
  ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_CUBE_EXP"
  
  ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
  ORA-06512: at "SYS.KUPW$WORKER", line 8353

  Thhs is a routine operation and still works. Recent changes to the database are down some patterns that we thought is perhaps not helpful, refer to

  http://abcdba.com/abcdbaserver11gdefaultschema 

  . Removed default schema users are

  ANONYMOUS,APPQOSSYS,CTXSYS,DIP,EXFSYS,MDDATA,MDSYS,OE,OLAPSYS,
  ORACLE_OCM,ORDDATA,ORDPLUGINS,ORDSYS,OWBSYS,OWBSYS_AUDIT,PM,SCOTT,
  SH,SI_INFORMTN_SCHEMA,SPATIAL_CSW_ADMIN_USR,SPATIAL_WFS_ADMIN_USR
  WMSYS

  The remaining default schemas are

  APEX_030200,APEX_PUBLIC_USER,DBSNMP,FLOWS_FILES,MGMT_VIEW,
  OUTLN,SYS,SYSMAN,SYSTEM,XDB,XS$NULL

  SYS objects. DBMS_CUBE_EXP causing ORA-06508 exists but not valid

  select owner,object_name,object_type,status from dba_objects where object_name='DBMS_CUBE_EXP'
  SYS     DBMS_CUBE_EXP     PACKAGE             VALID
  SYS     DBMS_CUBE_EXP     PACKAGE BODY     INVALID
  PUBLIC     DBMS_CUBE_EXP     SYNONYM             VALID

  We cannot restore the State before drooping users as it occurred last week and the backup is replaced by a more recent and a newapplication schema is generated and we want to keep?
  
  Is there a way to solve this problem without restoring database?
  
  Thank you

  In fact, I had the same problem with DBMS_CUBE_EXP. Oracle Enterprise Manager alert recommended remove EXECUTE on the public DBMS_LOB. This caused several * SYS packages and package bodies to go invalid.  I have granted EXECUTE the user (CTXSYS, OLAPSYS, ect) and then compiled the object successfully.

• installation of package body

  I did change in a package body procedure, I do not change the signature of procedure or anything, I just changed the code in a procedure.
  Now, I'll run this body with "CREATE or REPLACE PACKAGE BODY... "in the management of production database.
  1. my Spec package will go to the invalid state? I also should recompile Spec in the database?
  2 now, I understand that the sessions connected, clients java, use the older version of the package, not the most recent body database compiled just body. Will they have an error at the first appeal according to the packaging and the second call will succeed for them?
  
  I have Oracle 10 g.
  
  Published by: CharlesRoos on Sep 9, 2010 07:44

  Apart from what Sybrand said to do in the way of ITIL, an understanding of which is State package would be helpful...

  Packages tend to fail because of their 'package '. A package has a 'State' when it contains the package variable and constant level etc. and the package is called. On the first calling package, the 'State' is created in memory to hold the values of these variables, etc. If an object including the package depends on for example a table is changed somehow example deleted and recreated due to data dependencies, the package then takes a State not VALID. When you do then appealed to the package, Oracle examines the status and see that it is not valid, then determines that the package has a "State". Because something changed the package depended on, the State is taken as being obsolete and is ignored, which causes the error "State package has been abandoned" message.

  If a package has no variables of level package etc. i.e. the 'State' and then, taking the same example above, the whole takes an INVALID state, but when you make then a call to the package, Oracle considers as invalid, but knows that there is no 'State' attached to it and is therefore able to recompile the package automatically and then continue execution without causing error messages. The only exception here is if the thing that the package was dependent on a change of such kind that the package may not compile, in which case you will get an invalid error package type.

  And if you want to know how we prevent Jetty package States...

  Move all variables and constants in a stand-alone package specification and to refer to those of your original package. So when the status of your original packing is invlidated for some reason, it has no State package and can be recompiled automatically, however the packaging containing the vars/const is not cancelled because it has no dependencies, so the State that is in memory for this package will remain and may continue to be used.

  As for package-level sliders, you will need to make these premises to the procedures/functions using them as you won't be able of sliders reference in all of packages like that (not sure on the use of the REF CURSOR but... exists for me to study!)

  This first example shows the State being disabled by adding a new column on the table and causing to give a 'Package State scrapped' error...

  SQL> set serveroutput on
  SQL>
  SQL> create table dependonme (x number)
    2  / 
  
  Table created.
  
  SQL>
  SQL> insert into dependonme values (5)
    2  / 
  
  1 row created.
  
  SQL>
  SQL> create or replace package mypkg is
    2    procedure myproc;
    3  end mypkg;
    4  / 
  
  Package created.
  
  SQL>
  SQL> create or replace package body mypkg is
    2    v_statevar number := 5; -- this means my package has a state
    3
    4    procedure myproc is
    5      myval number;
    6    begin
    7      select x
    8      into myval
    9      from dependonme;
   10
   11      myval := myval * v_statevar;
   12      DBMS_OUTPUT.PUT_LINE('My Result is: '||myval);
   13    end;
   14  end mypkg;
   15  / 
  
  Package body created.
  
  SQL>
  SQL> exec mypkg.myproc
  My Result is: 25
  
  PL/SQL procedure successfully completed.
  
  SQL>
  SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
    2  / 
  
  OBJECT_NAME
  --------------------------------------------------------------------------------------------------
  OBJECT_TYPE         STATUS
  ------------------- -------
  MYPKG
  PACKAGE             VALID
  
  MYPKG
  PACKAGE BODY        VALID
  
  SQL>
  SQL>
  SQL> alter table dependonme add (y number)
    2  / 
  
  Table altered.
  
  SQL>
  SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
    2  / 
  
  OBJECT_NAME
  --------------------------------------------------------------------------------------------------
  OBJECT_TYPE         STATUS
  ------------------- -------
  MYPKG
  PACKAGE             VALID
  
  MYPKG
  PACKAGE BODY        INVALID
  
  SQL>
  SQL> exec mypkg.myproc
  BEGIN mypkg.myproc; END;
  
  *
  ERROR at line 1:
  ORA-04068: existing state of packages has been discarded
  ORA-04061: existing state of package body "SCOTT.MYPKG" has been invalidated
  ORA-06508: PL/SQL: could not find program unit being called: "SCOTT.MYPKG"
  ORA-06512: at line 1
  
  SQL>
  SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
    2  / 
  
  OBJECT_NAME
  --------------------------------------------------------------------------------------------------
  OBJECT_TYPE         STATUS
  ------------------- -------
  MYPKG
  PACKAGE             VALID
  
  MYPKG
  PACKAGE BODY        INVALID
  
  SQL>
  SQL> exec mypkg.myproc
  
  PL/SQL procedure successfully completed.
  
  SQL>
  SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
    2  / 
  
  OBJECT_NAME
  --------------------------------------------------------------------------------------------------
  OBJECT_TYPE         STATUS
  ------------------- -------
  MYPKG
  PACKAGE             VALID
  
  MYPKG
  PACKAGE BODY        VALID
  

  And the following example shows how to get the package in their own specifications of package variables, allows the package to automatically recompile when it is called even if it has become invalid by the action to add a column to the table.

  SQL> drop table dependonme
    2  / 
  
  Table dropped.
  
  SQL>
  SQL> drop package mypkg
    2  / 
  
  Package dropped.
  
  SQL>
  SQL> set serveroutput on
  SQL>
  SQL> create table dependonme (x number)
    2  / 
  
  Table created.
  
  SQL>
  SQL> insert into dependonme values (5)
    2  / 
  
  1 row created.
  
  SQL>
  SQL> create or replace package mypkg is
    2    procedure myproc;
    3  end mypkg;
    4  / 
  
  Package created.
  
  SQL>
  SQL> create or replace package mypkg_state is
    2    v_statevar number := 5; -- package state in seperate package spec
    3  end mypkg_state;
    4  / 
  
  Package created.
  
  SQL>
  SQL> create or replace package body mypkg is
    2    -- this package has no state area
    3
    4    procedure myproc is
    5      myval number;
    6    begin
    7      select x
    8      into myval
    9      from dependonme;
   10
   11      myval := myval * mypkg_state.v_statevar;  -- note: references the mypkg_state package
   12      DBMS_OUTPUT.PUT_LINE('My Result is: '||myval);
   13    end;
   14  end mypkg;
   15  / 
  
  Package body created.
  
  SQL>
  SQL> exec mypkg.myproc
  My Result is: 25
  
  PL/SQL procedure successfully completed.
  
  SQL>
  SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
    2  / 
  
  OBJECT_NAME
  --------------------------------------------------------------------------------------------------
  OBJECT_TYPE         STATUS
  ------------------- -------
  MYPKG
  PACKAGE             VALID
  
  MYPKG
  PACKAGE BODY        VALID
  
  SQL>
  SQL> alter table dependonme add (y number)
    2  / 
  
  Table altered.
  
  SQL>
  SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
    2  / 
  
  OBJECT_NAME
  --------------------------------------------------------------------------------------------------
  OBJECT_TYPE         STATUS
  ------------------- -------
  MYPKG
  PACKAGE             VALID
  
  MYPKG
  PACKAGE BODY        INVALID
  
  SQL>
  SQL> exec mypkg.myproc
  My Result is: 25
  
  PL/SQL procedure successfully completed.
  

• Package body is not VALID

  Hi friends,

  Could you help me understand this behavior in oracle.

  SQL > create or replace package mypkg is

  2 number of v_statevar: = 40;

  3 procedure MyProc;

  4 end mypkg;

  5.

  Package created.

  SQL > create or replace package body is mypkg

  2 procedure MyProc is

  3 myval number;

  4 start

  5. Select x

  6 in myval

  7 of dependonme;

  8

  9 - myval: = myval * mypkg.v_statevar;

  10 DBMS_OUTPUT. Put_line (' my result is: ' | myVal);

  11 end;

  12 end mypkg;

  13.

  Package body created.

  SQL > select object_name, object_type, status from user_objects where object_name = 'MYPKG ';

  OBJECT_NAME OBJECT_TYPE STATUS

  ------------------------------ ------------------- -------

  PACKAGE VALID MYPKG

  VALID PACKAGE BODY MYPKG

  SQL > set serveroutput on

  SQL > exec mypkg.myproc;

  My result is: 5

  PL/SQL procedure successfully completed.

  SQL > create or replace package mypkg is

  2 number of v_statevar: = 150;

  3 procedure MyProc;

  4 end mypkg;

  5.

  Package created.

  SQL > select object_name, object_type, status from user_objects where object_name = 'MYPKG ';

  OBJECT_NAME OBJECT_TYPE STATUS

  ------------------------------ ------------------- -------

  PACKAGE VALID MYPKG

  INVALID BODY PACKAGE MYPKG

  SQL > set serveroutput on

  SQL > exec mypkg.myproc;

  My result is: 5

  PL/SQL procedure successfully completed.

  SQL > select object_name, object_type, status from user_objects where object_name = 'MYPKG ';

  OBJECT_NAME OBJECT_TYPE STATUS

  ------------------------------ ------------------- -------

  PACKAGE VALID MYPKG

  VALID PACKAGE BODY MYPKG

  SQL >

  How did change the value of the variable in the package specification makes the invalid package body.

  How execution of the procedure of the package is once again the VALID State.

  Kimmy says:

  Hello carine,.

  I'm just setting the variable in the notebook, that variable was not referred to the procedure in the package body, also I'm not change any signature/details of the procedure described in the package specification, then what do the package body are invalid.

  There are two parts to this.

  (a) by recompiling package specifications, you then automatically invalidates all objects in the database that dependent on it.  In this case, the package body is dependent on, so get marked as invalid.  When you try and run something in the package Oracle try to compile the package, if it succeeds, it will mark it as valid again (as in your case).

  (b) the variables and declarations of a package (public and private) are what constitutes the 'State '.  By calling the package, you instantiate a copy in memory to create this state of package for this instantiation of the entire session.  By recompiling package specifications (it's not fair that you change the value of the variable, you recompile the spec), you can invalidate the State in memory and therefore potentially invalidate the package body.  It depends on your version of the database.  In 10g, by invalidating state you will get an exception "State package rejected" when you try to run the package after the change, and then it will automatically compile and validate the package, so that it eventually works ok.  From 11 g, there is more fine grain dependencies on the State, so if the change you have made has no effect on what you run, it can validate and run without causing the exception 'package State scrapped ';. He would only do that if it's something that you used.

• Procedure is not recognized in the package body

  I have this error message:

  Compile for HR.MILOS_PACKAGE BODY of PACKAGE errors

  Error: PLS-00323: subprogram or cursor "RAISE_SALARY" is declared in a package specification and must be defined in the package body

  Online: 19

  Text: IF (l_exists)

  I deffined in the whole of the body after the first procedure that is no problem.

  I don't know what the problem is. There is no other sugestions compiler.

  Procedure works very well when packing.

  PROCEDURE RAISE_SALARY (p_perc p_dep_id NUMBER, NUMBER) IS

  v_emp_id employees.employee_id%TYPE;

  v_sal employees.salary%TYPE;

  v_avg_sal employees.salary%TYPE;

  CURSOR c_salaries IS SELECT employee_id, salary employees

  If NOT EXISTS (SELECT 1 from employees e WHERE e.manager_id = employees.employee_id)

  and department_id = p_dep_id;

  CURSOR c_salaries_m IS SELECT employee_id, salary employees

  WHERE employe_id IN (SELECT distinct manager_id of employees)

  and department_id = p_dep_id;

  Start

  SELECT AVG (salary) IN the v_avg_sal FROM Employees WHERE department_id = p_dep_id;

  OPEN c_salaries.

  LOOP

  EXTRACT c_salaries INTO v_emp_id, v_sal;

  EXIT WHEN c_salaries % NOTFOUND;

  IF v_sal + 1 > 3 * v_avg_sal

  THEN UPDATE employees SET salary = 3 * v_avg_sal

  WHERE employe_id = v_emp_id;

  UPDATE of OTHER employees SET salary = salary * to_number ('1' |'.) ' || p_perc)

  WHERE employe_id = v_emp_id;

  END IF;

  END LOOP;

  CLOSE C_salaries;

  OPEN c_salaries_m.

  LOOP

  EXTRACT c_salaries_m INTO v_emp_id, v_sal;

  EXIT WHEN c_salaries_m % NOTFOUND;

  IF v_sal + 5 > 3 * v_avg_sal

  THEN UPDATE employees SET salary = 3 * v_avg_sal

  WHERE employe_id = v_emp_id;

  UPDATE of OTHER employees SET salary = salary * to_number ('1' |'.) ' || (p_perc + 50))

  WHERE employe_id = v_emp_id;

  END IF;

  END LOOP;

  CLOSE C_salaries_m;

  end RAISE_SALARY;

  Compile for HR.MILOS_PACKAGE BODY of PACKAGE errors

  Error: PLS-00323: subprogram or cursor "RAISE_SALARY" is declared in a package specification and must be defined in the package body

  We hear... you have defined the raise_salary procedure in the package specification but not in the package body. (pretty clear)

  not in the package body means:

  the statement could be different...

  PROCEDURE RAISE_SALARY (NUMBER, p_dep_id NUMBER p_perc)

  so:

  are identical named parameters?

  they have identical data types?

  vary according to the assigned default values?

  vary according to its use (IN/OUT/IN OUT) - (why did not specify the use anyway?)

  HTH

• Sqldev 4.0.2: When I change the package body, down to show me "calculation... bread crumbs for body" in infinitive loop until I get out.

  When I change the package body, down to show me ' calculation of breadcrumbs to... body "in infinitive loop until I get out.

  On
  —–

  Oracle SQL Developer 4.0.2.15
  Version 4.0.2.15
  Build 15.21

  The IDE version: 12.1.3.2.41.140418.1111
  Product ID: oracle.sqldeveloper
  Product version: 12.2.0.15.21

  Version
  ——-

  Version of the component
  ========= =======
  Oracle IDE 4.0.2.15.21
  Java (TM) Platform 1.7.0_65
  Support versioning 4.0.2.15.21

  Thanks for the update. I pass the developer and I hope he finds that they are useful.

  A preliminary analysis shows some problems of Java:

  1. report of the discharge of the thread Analyzer is a little misleading because of https://bugs.openjdk.java.net/browse/JDK-8036823

  2 possible endless loop in the ScaledBlit routine on the thread main event: https://bugs.openjdk.java.net/browse/JDK-8028539

  Question 2 currently has no resolution, but there are a few (a potential solution?) fix for jdk1.8.0_40 (8u40).  The latest official version is 8u11.

  Assuming that the number 2 is the culprit on Ubuntu, just like on Windows, then 1st edition probably does not concern us. Just for reference, a backport of the Java correction for the 1st edition exists on jdk 1.7 and 1.8, but has yet to be officially released on either.

  Kind regards
  Gary

• Hey, I just wanted to buy a package complete apps for creative cloud every time that I enter the stage at the confirmation stage its tells me there is a problem procedure and I need to contact customer service

  Hey, I just wanted to buy a package complete apps for creative cloud every time that I enter the stage at the confirmation stage its tells me there is a problem procedure and I need to contact customer service

  Make sure that you are logged on the Adobe site, having cookies enabled, clearing your cookie cache.  If he continues to not try to use a different browser.

• Package body dropped, but showing invalid

  Nice day:

  Oracle 11 g 2

  I created a Package with Package bodies, procedures 3, which works very well.  I can call it without error.  However, if I run this query:

  SELECT *.

  From user_objects

  Situation WHERE = "INVALID."

  I get the following result:

  OBJECT_NAME

  SUBOBJECT_NAME

  OBJECT_ID

  DATA_OBJECT_ID

  OBJECT_TYPE

  CREATED

  LAST_DDL_TIME

  TIMESTAMP

  STATUS

  TEMPORARY

  GENERATED

  SECONDARY

  NAMESPACE

  EDITION_NAME

  TASK_PROCEDURES

  28700

  PACKAGE BODY

  5 July 14

  July 11, 14

  2014-07 - 11:18:42:39

  Not valid

  N

  N

  N

  2

  It is an old package body, that I dropped it about 4 days ago.  That is always supposed to show if I run this query?

  I work with Oracle SQL Developer, using almost the same version too. I don't think that it has nothing to do with the tool as the data dictionary shows this info too.

  Could you post the exact commands that you run from a sql more session? And the sql like too much output.

  Example (demo of pseudo code)

  SQL > alter the package xxx body compilation;

  SQL > compiled package.

  SQL > show errors

  SQL > no error

  SQL > drop package xxx;

  SQL > package abandoned;

  SQL > drop package body xxx.

  ???

  SQL > select xxx.someFunction from double;

  I could explain the behavior if you have enabled the editions (CDE). But there is no air if in your case.

  Just to be absolutely sure of it. Make the select statement and after the release:

  select object_name, object_type, namespace, edition_name
  from user_objects_ae
  where object_name = 'YOURPACKAGENAME';