DROP PACKAGE

Hello
I would like to help.
I have the following problem:

Site studies Web has an application that runs on top of JWPlayer plugin (SWF), but the site is by permission of lists all the rules of content filtering with the firewall for full access, and yet this fall packages. The following Packet monitor log.

Number of packages: 419 *.
Header values:
Captured bytes: 131, actual bytes on the wire: 131
The package info (time: 19/04/2016 10:08:32.624):
in:-, out: X 0 *, IGNORED, Code Drop: 41, Id of Module: 26, (Ref.Id: _5057_txGsIboemfJqQlu), 2:2)
Ethernet header
Ether Type: IP(0x800), CBC is [d0:67:e5:bc:19:43], Dst = [02:17:c5:c1:28:b4]
IP packet header
Type of intellectual property: (0 x 6) TCP, Src = [192.168.16.1], Dst = [179.127.4.146]
TCP packet header
TCP Flags = [ACK, PSH,], [54994] = Src, Dst is [1935], Checksum = 0xff0d
The request header
Knows not
Value: [0]
Hex and ASCII dump of the package:
0217c5c1 28b4d067 08004500 00753549 00007f06 e5bc1943 *... (.. g... C E... u5I... *.
{7d7fc0a8 1001b37f 0492d6d2 078f6f86 fd8beb1d 33125018 *}... o... 3.P. *.
0100ff0d 0000957a 390f7828 be450fb2 330019be 83f630f5 *... z9.x (.) E.. 3... 0 *
2c2b98c0 8f3155f9 90 d 87738 6ca283d8 2d9779c6 ec81717d *, +... {1U... w8l... there... _ q} *.
d33347d4 4ff9b8d1 13c4f201 26c244a8 f0979015 6bcd66e1 *.3G. O.......&. D...k. f *.
(2920ec7d ac727756 bef71e *).}. rwV... *.

As SCR 192.168.16.1 my internal IP and the DST 179.127.4.146 the IP Address of the request.

in which I already identified the port and the 1935 and published in this control of the App.

Note: I use Google Translator to be able to create the text, I apologize for the errors. Thank you.

Problem solved, after placing the IP address in the list of IPS, blocking Exclusions occurred for a reason any within the App advanced control

Thank you

Tags: Dell Tech

Similar Questions

Cisco IDS 4.1 probes in HA? monitor package drops?

Hello

can someone tell me if Cisco IDS sensors provide high availability or failover capabilities? If so, how and where to fix?

Is there a form any notification drop package when sensor starts a fall of packages under full load?

Hello

IDS sensors do not provide high availability or failover capability.

Under a high load of the sensor can be configured to alert of hamid question the 993 which States "package dropout rate exceeded the threshold. This threshold is set by default to 5% (Total dropped packets / Total packets received in a time interval). You must enable this GIS as it is disabled by default.

Hope this helps

Thank you

Madhu

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

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';

DBMS_REDEFINITION package leads to a PLS00201 compilation error

I try to put a logic of redefining online within a packet but direct issues, in particular the package doesn't seem to know DBMS_REDEFINITION. I can run DBMS_REDEFINITION, only not go in a package or a program named.

Here is a minimal example that fails:

-- Executed by the same user
-- This works just fine:
BEGIN
  DBMS_OUTPUT.PUT_LINE(SYS.DBMS_REDEFINITION.CONS_USE_ROWID);
END;


-- This generates PLS-00201 error on SYS.DBMS_REDEFINITION:
CREATE OR REPLACE PACKAGE testpkg
  AUTHID CURRENT_USER
AS
  gc_int PLS_INTEGER := SYS.DBMS_REDEFINITION.CONS_USE_ROWID;
END testpkg;


-- This does not work because testpkg is invalid:
BEGIN
  DBMS_OUTPUT.PUT_LINE(testpkg.gc_int);
END;

The problem is that I can run these instructions to the same user within the same session and I still get the error PLS. I even ran on my own system of sandbox (12 c VM) where I have system privileges, but it does not work. I fiddled with the AUTHID clause but that did not help.

Related discussions:

Any suggestions?

How grant you permission to this user to use dbms_redefinition? It must be a direct subsidy without a role:

Connected to:
Oracle Database 11g Release 11.2.0.4.0 - 64bit Production                      

SQL> CREATE OR REPLACE PACKAGE testpkg
  2    AUTHID CURRENT_USER
  3  AS
  4    gc_int PLS_INTEGER := SYS.DBMS_REDEFINITION.CONS_USE_ROWID;
  5  END testpkg;
  6  /                                                                         

Warning: Package created with compilation errors.                              

SQL> drop package testpkg;                                                     

Package dropped.                                                               

SQL> conn / as sysdba
Connected.                                                                     

SQL> grant all on dbms_redefinition to hr;                                     

Grant succeeded.                                                               

SQL> conn hr/hr
Connected.
SQL> CREATE OR REPLACE PACKAGE testpkg
  2    AUTHID CURRENT_USER
  3  AS
  4    gc_int PLS_INTEGER := SYS.DBMS_REDEFINITION.CONS_USE_ROWID;
  5  END testpkg;
  6  /                                                                         

Package created.

current state of the package has been abandoned...

Hi all..

I get the following error only for the '"first run" ", even the package is in State"valid ". If the execute the same package to new "second run", it works ok.

usually we complie all 'invalid objects"in the diagram, when we pass the TEST or PRE-PRODUCTION code approx.

but I get the following error, even if the package is in State "valid".

ERROR at line 1:
ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package "TEST_OWNER.TEST_PKG" has
been invalidated
ORA-04065: not executed, altered or dropped package
"TEST_OWNER.TEST_PKG"
ORA-06508: PL/SQL: could not find program unit being called:
"TEST_OWNER.TEST_PKG"
ORA-06512: at line 2

I went through the next thread, blu explained the cause of this error,
but we receive this error even when the package is 'valid' State too?

Re: When should be package invalidated?

Which session refers to a package for first time package is instantiated in memory of the session. If the package is recompiled, Oracle assumes he may have changed and the package in memory session instance is no longer valid. This is why any reference to this package made by this session will raise an error.

Session 1:

SQL> create or replace
  2  package pkg1
  3  is
  4  g_n number;
  5  procedure p1;
  6  end;
  7  /

Package created.

SQL> create or replace
  2  package body pkg1
  3  is
  4  procedure p1
  5  is
  6  begin
  7  for rc in (select * from emp) loop
  8  dbms_output.put_line(rc.empno);
  9  end loop;
 10  end;
 11  end;
 12  /

Package body created.

SQL> exec pkg1.p1;

PL/SQL procedure successfully completed.

SQL>

This package is instantiated PKG1 is session1. Then session 2:

SQL> alter package pkg1 compile body;

Package body altered.

SQL>

Back to session 1:

SQL> exec pkg1.p1;
BEGIN pkg1.p1; END;

*
ERROR at line 1:
ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package body "SCOTT.PKG1" has been invalidated
ORA-04065: not executed, altered or dropped package body "SCOTT.PKG1"
ORA-06508: PL/SQL: could not find program unit being called: "SCOTT.PKG1"
ORA-06512: at line 1

SQL>

SY.

ORA-04068: current state of the packages was waived - avoid

Hello
I fight with the bad behavior of developers that is, something like this:

CREATE OR REPLACE PACKAGE pkg1 IS

g_version VARCHAR2(20) := '7.3';
    TYPE t_id_kon IS RECORD(
    id_kon VARCHAR2(12),
    sr_id    NUMBER(5));

  TYPE t_id_kont IS TABLE OF t_id_kon INDEX BY BINARY_INTEGER;
  FUNCTION get_version RETURN VARCHAR2;
END pkg1;
/

I did some tests and looks like when you recompile pkg1 with
Global g_version variable it is ORA-04068 generated for all sessions using this pkg1 before recompiling.
But what about type and table_type declared in pkg1 they cause same behavior as g_version global varialbe?

And generally how to treat than the types of situations of application point of view, you must catch this exception and re-run your application just?
concerning
GregG

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.

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...

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

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

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.

error ORA-4068:-l' current state of the package is invalidated

Hai friends,

Please see this link

Problem we faced, it is ' error ora-4068:-l' current state of the package is disabled "in the application.initiallly of customer, we migrated to oracle 9i and 10g 10.2.0.4.0

We have discussed and obtained the solution as the timestamp of the objects may be different. (we expect the access rights of the table sys.obj$) pls see the link

Re: oracle error-4068

But now we are informed senior as below

(1) error ora-4068 will come only when recompile us the view. is this true?

(2) 6136074 bug is fixed in 10.2.0.4.0. is it?

Gurus of give your valuable suggestions

S

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

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

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.

How to use the DBMS_ROWID package
Hello

I am not able to use this DBMS_ROWID package, I ran this script in my schema dbmsrwid.sql

When I use this sql I get the following error:

SQL > select DBMS_ROWID. ROWID_BLOCK_NUMBER (ROWID)
2 FROM emp3
3 where id = 1;
Select DBMS_ROWID. ROWID_BLOCK_NUMBER (ROWID)
*
ERROR on line 1:
ORA-04067: not executed, the package body "KAM. DBMS_ROWID' does not exist
ORA-06508: PL/SQL: called program unit is not found: "KAM. DBMS_ROWID.
ORA-06512: at line 1

and also when I try to use below that I get the same above erro

SQL > DBMS_ROWID. () ROWID_BLOCK_NUMBER

If I connect with scott so I am able to do it as below:

SQL > select DBMS_ROWID. ROWID_BLOCK_NUMBER (ROWID)
2 FROM emp
3. WHERE ename = 'KING '.

DBMS_ROWID. ROWID_BLOCK_NUMBER (ROWID)
------------------------------------
30
Thank you and best regards,
Kam
Did you run dbmsrwid.sql in the KAM schema? Because it seems that the DBMS_ROWID package has been created it there.

I suggest you drop the package in the KAM schema version, unless there is a specific reason that you need (very, very unlikely that you do).
```
DROP PACKAGE kam.dbms_rowid
```
If you do this, the SELECT statement that has worked in the SCOTT schema should also work in the KAM schema.

SQL > SYS. DBMS_ROWID. () ROWID_BLOCK_NUMBER
SP2-0734: unknown command starts 'SYS. DBMS_R... "- rest of line is ignored.

You cannot call a function like this just to the SQL * quicker. You need to put it in a SELECT statement. If you add the SYS prefix to the query that you previously had, it should work as well. But if you do not file the package, you will always have an invalid version of DBMS_ROWID in the KAM schema.

Justin

Newbie question ASA QoS

Forgive the question probably simple, but is QoS applied only when an interface is maxed out and congested? I put to the traffic of policy for a single IP address, limiting to 384 KB of bandwidth with a connected only T-1. It does not "kick" and limit under normal traffic, so I think that QoS is not serious as long as best effort is bumping against the maximum speed of the line?

I hope that I wrote that correctly! Thank you!

Steve

cool... so try to run DSL speed test now on any of your internal hosts and see the fun... :-)

Yes you are right... If you exceed 384 Kbps... FW reset the connection or file your application

have you configured globally or only on the Interface of your interior?

Other commands that would help are

(config) # sh - political global service

(config) # sh police service-policy

ASA5510-Single (config) # sh service-policy

International policy:

Service policy: global

Class-map: MyClass

Inspect: pptp, package 0 0 drop, reset - drop 0

Class-map: global-class

Inspect: error icmp, package 0 0 drop, reset - drop 0

Inspect: pptp, package 0 0 drop, reset - drop 0

Inspect: rtsp, package 0 0 drop, reset - drop 0

Inspect: http, 0, 0 drop package, reset - drop 0

Inspect: icmp, package 0 0 drop, reset - drop 0

Inspect: ftp, packet 0 0 fall, reset - drop 0

Inspect: dns, 0, 0 drop package, reset - drop 0

Class-map: telnet

Set the connection policy:

Set the connection time-out policy:

TCP 24:00:00

Class-map: IPS-CLASS

IPS: status of card upward, inline mode rescue

sachet bag of 0, input output 0, fall 0, reset-drop 0

ASA5510-Single (config) #.

IPSec parody detected asa

Hello

I get the error on asa parody ipsec detected a Drop package in vpn remote access

Please give the reason for everything to get this message and the proposal at this

Hello

I've seen this message before and as I remember it means that traffic coming to claire who should be protected by IPsec.

Possible solution: check the encryption access list

Hope that helps,

MiKa

BGP multihomed with HSRP

Hello

Is it possible with elegance the convergent eBGP neighbor stopped to the other CE router connection with zero drop package or power failure?

We have 2 CES linked together using iBGP and eBGP that both connect to the different EPP but on the same you.

CE1-> PPE1 - AS12345

iBGP and HSRP between these

CE2-> PPE2 - AS12345

I tried using the command ' neighbor 10.10.10.10 stop ' but I have a blackout for a few seconds.

Thank you

Hello

Latest IOSes are supported a feature called BGP soft stop that is described here:

http://www.Cisco.com/c/en/us/TD/docs/iOS-XML/iOS/iproute_bgp/configuration/XE-3s/IRG-XE-3s-book/configuring_bgp_graceful_shutdown.html

You might be interested in checking if this device can be used on your devices.

In general, however, a phasing out of a neighbour in BGP usually is possible in making sure these routers stop to consider the routes learned from each other as usable routes before going down. This can be done in several ways in BGP - change local preference in iBGP, changing the MED or, better, the AS_PATH in eBGP, filtering the routes so marked with a specific Community (progressive shutdown of BGP relies on the use of a specific community to do it this way).

HSRP is out of the question - its placement is to end hosts, not between routers.

Best regards
Peter

PPTP VPN Cisco IOS router through

Hi all

I was wondering if there is a trick to get PPTP to work through a Cisco router. He was in fact at some point, but I don't remember what has been changed over time... However, it no longer works.

Current configuration includes:

* CBAC applied inbound and outbound on the Internet interface (I needed to add incoming to fix a problem with the mode passive FTP doesn't work is not on a FTP server hosted behind this router)

* CBAC inspects, among other things, PPTP

* ACL applied inbound on interface Internet, GRE and TCP 1723 admitted any intellectual property

* No other ACL on the router

* IOS 15.0 (1)

* Inbound configuration NAT for TCP 1723 (currently using the WAN IP address)

One thing I saw was so Troubleshooting "IKE Dispatcher: IKEv2 version detected 2, Dropping package! - but I think that it is a wrong journal (router as the Cisco VPN configuration example).

The server is definitely okay - we are able to connect over PPTP VPN from the local network to the server. So I think it's a sort of NAT problem, because I don't see anything dropped by the firewall.

Anyone able to point me in the right direction?

Thank you

Hello

Thanks for fix the "sh run". Could you change the following:

IP nat inside source static tcp 10.77.99.11 1723 1723 road-map repeating sheep ccc.ccc.ccc.ccc

to do this:

IP nat inside source static tcp 10.77.99.11 1723 1723 extensible ccc.ccc.ccc.ccc

It would be prudent to proceed with this change in the removal of the map of the route if no one connects to the server via the PPTP VPN.

Let me know.

Kind regards

ANU

P.S. Please mark this question as answered if it was resolved. Note the useful messages. Thank you!

Appeal of a trigger

Hello

I would like to know how to call a procedure of a trigger.

I have included a script to create the objects for my problem.

In the trigger named TABLE_A_BI , I noticed the lines that do not work for me.

The lines look like this (it doesn't).

--  :NEW.COL_A_DATE :=
-- BEGIN
-- CALL TEST_PKG.INSERT_RECHECK_RECORD_PRC (:NEW.ID);

The script will set the scene for the following to be run (it runs successfully);

BEGIN
TEST_PKG.INSERT_RECHECK_RECORD_PRC
(1
);
END;

Its the above procedure I would like to run from my trigger.

Concerning

Ben

I have included the code below.

Generate the Script

CREATE TABLE TABLE_A
  (
    ID             NUMBER NOT NULL,
  TABLE_B_ID     NUMBER NOT NULL,
    COL_A_DATE     DATE,
    SYS_CREATED_BY VARCHAR2(50 CHAR) NOT NULL ENABLE,
    SYS_CREATED_ON DATE DEFAULT SYSDATE NOT NULL ENABLE,
    SYS_UPDATED_BY VARCHAR2(50 CHAR),
    SYS_UPDATED_ON DATE
  );

ALTER TABLE TABLE_A ADD CONSTRAINT TABLE_A_PK PRIMARY KEY (ID);

CREATE SEQUENCE TABLE_A_SEQ MINVALUE 1 MAXVALUE 1000000000000000000000000000 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER  NOCYCLE ;

create or replace
trigger TABLE_A_BI
BEFORE
  INSERT OR UPDATE ON TABLE_A
  FOR EACH ROW BEGIN

  IF INSERTING THEN

    IF :NEW.ID IS NULL THEN
      SELECT TABLE_A_SEQ.nextval INTO :NEW.ID FROM dual;
    END IF;

    IF :NEW.SYS_CREATED_BY IS NULL THEN
      :NEW.SYS_CREATED_BY  := NVL(V('APP_USER'),USER);
    END IF ;

  ELSIF UPDATING THEN

    :NEW.SYS_UPDATED_BY :=
      CASE
        WHEN V('APP_USER') IS NOT NULL THEN
          V('APP_USER')
        ELSE
          NVL(:NEW.SYS_UPDATED_BY,USER)
        END;

    :NEW.SYS_UPDATED_ON :=
      CASE
        WHEN :NEW.SYS_UPDATED_ON IS NULL THEN
          SYSDATE
        ELSE
          NVL(:NEW.SYS_UPDATED_ON,SYSDATE)
      END;

--  :NEW.COL_A_DATE :=
-- BEGIN
-- CALL TEST_PKG.INSERT_RECHECK_RECORD_PRC (:NEW.ID);

  END IF;

END;
/

CREATE TABLE TABLE_B
  (
  ID                  NUMBER NOT NULL ENABLE,
    COL_B_NUM           NUMBER NOT NULL ENABLE,
  SYS_RECHECK_CREATED VARCHAR2 (3 CHAR) DEFAULT 'NO' NOT NULL ENABLE,
    SYS_CREATED_BY      VARCHAR2(50 CHAR) NOT NULL ENABLE,
    SYS_CREATED_ON      DATE DEFAULT SYSDATE NOT NULL ENABLE,
    SYS_UPDATED_BY      VARCHAR2(50 CHAR),
    SYS_UPDATED_ON      DATE
  ) ;

ALTER TABLE TABLE_B ADD CONSTRAINT TABLE_B_PK PRIMARY KEY (ID);

CREATE SEQUENCE TABLE_B_SEQ MINVALUE 1 MAXVALUE 1000000000000000000000000000 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER  NOCYCLE ;

create or replace
TRIGGER TABLE_B_BI
BEFORE
  INSERT OR UPDATE ON TABLE_B
  FOR EACH ROW BEGIN

  IF INSERTING THEN

    IF :NEW.ID IS NULL THEN
      SELECT TABLE_B_SEQ.nextval INTO :NEW.ID FROM dual;
    END IF;

    IF :NEW.SYS_CREATED_BY IS NULL THEN
      :NEW.SYS_CREATED_BY  := NVL(V('APP_USER'),USER);
    END IF ;

  ELSIF UPDATING THEN

    :NEW.SYS_UPDATED_BY :=
      CASE
        WHEN V('APP_USER') IS NOT NULL THEN
          V('APP_USER')
        ELSE
          NVL(:NEW.SYS_UPDATED_BY,USER)
        END;

    :NEW.SYS_UPDATED_ON :=
      CASE
        WHEN :NEW.SYS_UPDATED_ON IS NULL THEN
          SYSDATE
        ELSE
          NVL(:NEW.SYS_UPDATED_ON,SYSDATE)
      END;

  END IF;

END;
/

ALTER TABLE  table_a
    ADD CONSTRAINT fkey_test FOREIGN KEY
    (
table_b_id
    )
    REFERENCES table_b
    (
id
    )
;
/

create or replace
PACKAGE test_pkg
AS

PROCEDURE insert_recheck_record_prc
(p_table_b_id_in IN NUMBER
);

END test_pkg;
/

create or replace
PACKAGE BODY test_pkg
AS

PROCEDURE insert_recheck_record_prc
(p_table_b_id_in IN NUMBER
)
IS
BEGIN

INSERT INTO table_b
( col_b_num
)
SELECT b.col_b_num
  FROM table_a a
     , table_b b
WHERE a.table_b_id = b.id
   AND b.col_b_num IN (1)
   AND b.sys_recheck_created IN ('NO')
   AND b.id = p_table_b_id_in;
              
UPDATE table_b
   SET sys_recheck_created = 'YES'
WHERE id = p_table_b_id_in;

END insert_recheck_record_prc;

END test_pkg;
/

INSERT INTO TABLE_B (COL_B_NUM) VALUES ('1');
INSERT INTO TABLE_A (TABLE_B_ID) VALUES ('1');
UPDATE TABLE_A SET COL_A_DATE = TO_DATE('07/OCT/15', 'DD/MON/RR') WHERE ID = 1;

Cleanup script

drop table table_a;
drop table table_b;
drop sequence table_a_seq;
drop sequence table_b_seq;
drop package test_pkg;

I think I did that obviously it is.

I'm trying to call a procedure from a trigger. I'm not having any success in getting this work.

The trigger performs the following:

When a column in the Table_A ("COL_A_DATE") is inserted or updated it raises an event that inserts a duplicate TABLE_B and updates the record first to TABLE_B with SYS_RECHECK_CREATED = 'YES '.

The lines below work when executing the procedure in a sql window, so for me

call a procedure/function of a trigger in the same way you call it anywhere else

do not work.

OK - Thanks for the extra info.

A trigger is PL/SQL code. You call a procedure in the SAME WAY in PL/SQL if you are using a trigger or not. Just use the name of the procedure and pass arguments.,.

http://docs.Oracle.com/CD/B28359_01/AppDev.111/b28370/subprograms.htm#CHDBEJGF

Subroutine calls

A subroutine call has this form:
subprogram_name [ (parameter [, parameter]... ) ]
A procedure call is a PL/SQL statement. For example:
raise_salary(employee_id, amount);
A function call is part of an expression. For example:
IF salary_ok(new_salary, new_title) THEN ...

This article from doc for details and includes the example code

When a column in the Table_A ("COL_A_DATE") is inserted or updated it raises an event that inserts a duplicate TABLE_B and updates the record first to TABLE_B with SYS_RECHECK_CREATED = 'YES '.

You probably don't want to go, but this process will NOT scale and is likely to have performance problems, but also problems of consistency of the data as well.

Oracle is a multiuser database which means another user MAY BE editing the same table at the same time as you.

A trigger is part of a transaction and delivers NO validations. And a trigger BEFORE UPDATE FOR EACH ROW can often get restored and restarted by Oracle. He might even get thousands of times, restarted.

So whatever data your trigger shown in table B at first may be totally different if the trigger is restarted.

Yes - I know - you probably won't hear how this architecture is, but it is BAD.

Invalid db SGD objects after upgrade to R4

When I try to deploy ZFS plugin, I met under failure.
EM-04101: as a result of invalid objects are in the repository of the EM: BODY of PACKAGE: EM_ASR_PKG. Retry deployment of plug-in after recompilation of things all invalid.
Select dba_objects owner, object_name, object_type, State where object_name = 'EM_ASR_PKG ';
STATUS OF OWNER OBJECT_TYPE OBJECT_NAME
------------------------------ --------------- ------------------- -------
SYSMAN EM_ASR_PKG PACKAGE AVAILABLE
SYSMAN EM_ASR_PKG INVALID BODY PACKAGE
Manually recompiling report error below:
"WARNING: Package body changed with compilation errors.

Your question is similar to the internal Bug 20436809.

According to the guidelines of this bug, EM_ASR_PKG package is no longer necessary after the 12.1.0.4.

If please drop this package and try again.

em_asr_pkg drop package;

commit;

It should work.

DROP PACKAGE

Similar Questions

Maybe you are looking for