OMBPlus example to bind package function to premapping_process operator

Does anyone have a script snippet showing how to bind a function within a package to a premapping_process operator ?
I got this far before the script ref let me down :
OMBALTER MAPPING 'MY_MAP' \
ADD PREMAPPING_PROCESS OPERATOR 'FACT_TRANS_PMO' \
BOUND TO xxxxxxx '../MY_PROJECT/xxxx'
Any idea what the value of the bindabletype is for a package function ?
Thanks

Folks, I figured it out. For those who may face this problem in the future you may want to take note for future reference.
Oracle does not allow you to assign the return value of a REF CURSOR from a FUNCTION ( not Procedure - - there is a difference) directly to a host variable. This is the case even if that host variable is declared a CURSOR variable.
The trick is as follows: Declare the REF CURSOR within the PL/SQL BEGIN Block, using the TYPE statement, that will contain the call to the package function. On the call, you then assign the return REF CURSOR value that the function is returning to your REF CURSOR variable declared in the DECLARE section of the EXEC SQL .... END-EXEC PL/SQL Block.
THEN, assign the REF CURSOR variable that was populated from the function call to your HOST cursor varaible. Then fetch this HOST Cursor variable into your Host record structure variable. Then you can deference individual fields as need be within your C or C++ code.
I hope this will help someone facing a deadline crunch. Happy computing !

Similar Messages

How to use type, packages, functions, and procedures in another schema ?

I have two target schema in one OWB project, such as A and B. In a mapping of A, I would like to use some types, packages, functions, and procedures from B. I have tried the method of synonym as suggested, but I could not find the metadata of these when importing ... The only type of synonym I can import is the synonym for table. Is there a bug for synonym?
If I cannot use synonym for this issue, is there another way to solve the problem?

Now, in some instances you will absolutely need to create the second module as Carsten describes, however it should also be noted that you can reference objects in things like Expressions even if you have not loaded up the metadata. It is only when you need strong binding that it becomes neccessary to import objects. For everything else, as long as the reference will resolve at compile-time then you are good to go.
For example, I have a function in one target schema (S1) and a private synonym to it in another(s2). A mapping in the S2 schema has an expression object that uses the synonym to the function in the expression property for a couple of the output attirbutes. The synonym has not been loaded into metadata - indeed OWB has no knowledge of its existance. But it resolves at compile time so the mapping validates and generates successfully.
Mike

Example of calling a function with passing parms

Does anyone have an example of calling a function that returns a refcursor, but also has passing parms? I've looked at the samples and they don't have passing parms. I've tried what you would think (adding an in passing parm to the function call and I get an ora-06550 error. If I don't pass the in parm, it works.
i.e. FUNCTION MyFunction(ininteger in integer) returns refcursor;
Thanx in advance,
Frank

Here is an example:
plsql code:
CREATE OR REPLACE PACKAGE testfun IS
TYPE RefCursor IS REF CURSOR;
FUNCTION fun1(keyid_in IN VARCHAR2) RETURN RefCursor;
END testfun;
SHOW ERRORS;
CREATE OR REPLACE PACKAGE BODY testfun IS
FUNCTION fun1(keyid_in IN VARCHAR2) RETURN RefCursor IS
     myCur RefCursor;
BEGIN
     OPEN myCur FOR
SELECT table_name
FROM user_tab_columns
WHERE rownum < 20;
     RETURN(myCur);
END fun1;
END testfun;
SHOW ERRORS;
c# code:
using System;
using System.Data;
using Oracle.DataAccess.Client;
using Oracle.DataAccess.Types;
namespace ODPSample
     /// <summary>
     /// Sample: Demonstrates array binding
     /// </summary>
     class ArrayBind
          static void Main(string[] args)
               // Connect
               string connectStr = "User Id=fedpro;Password=password;Data Source=fedprodev";
               OracleConnection connection = new OracleConnection(connectStr);
               connection.Open();
               OracleCommand loCommand = new OracleCommand("testfun.fun1", connection);
               loCommand.CommandType = CommandType.StoredProcedure;
               //RETURN VALUES MUST BE FIRST IN THE LIST OF PARMS!!!
               OracleParameter loReturnValue = loCommand.Parameters.Add("refcursor",OracleDbType.RefCursor);
               loReturnValue.Direction = ParameterDirection.ReturnValue;
               //Parm1
               OracleParameter loParm1 = loCommand.Parameters.Add("keyid_in",OracleDbType.Varchar2);
               loParm1.Direction = ParameterDirection.Input;
               loParm1.Value = "TEST";
               //Create an OracleDataAdapter
               OracleDataAdapter loDataAdapter = new OracleDataAdapter(loCommand);
               DataTable loDataTable = new DataTable();
               try
                    //Execute the function call
                    loCommand.ExecuteNonQuery();
                    //Populate the DataTable
                    loDataAdapter.Fill(loDataTable,(OracleRefCursor)loReturnValue.Value);
                    int rowcnt = loDataTable.Rows.Count;
                    Console.WriteLine(rowcnt);
               catch (Exception e)
                    Console.WriteLine(e.Message);
                    throw;

2.1.0.62: Problem with Package.Functions and Unit Tests

I like the new Sqldeveloper - I startet trying Unit Tests as described here: Link: [http://www.oracle.com/technology/obe/11gr2_db_prod/appdev/sqldev/sqldev_unit_test/sqldev_unit_test.htm#t4]
It worked with a test-procedure. Now i am trying to test my package functions, but all i get is this:
Die folgende Prozedur wurde ausgeführt.
Ausführungsaufruf
BEGIN
:1 := "PKG_MYPACK"."CREATEFUNCTION"(IN_PROGRAMMEID=>:2,
IN_AMOUNT=>:3,
IN_SWS=>:4);
END;
Bind-Variablen verwendet
1 INTEGER OUT (null)
2 INTEGER IN 1
3 INTEGER IN 10
4 INTEGER IN 11
Ausführungsergebnisse
ERROR
Ungültige Konvertierung angefordert
oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:110)
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:171)
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:439)
oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:7723)
oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7496)
oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7978)
oracle.jdbc.driver.OracleCallableStatement.setObject(OracleCallableStatement.java:4063)
oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:221)
oracle.dbtools.raptor.datatypes.strategies.callablestatement.CallableBindingDatum.customBindIN(CallableBindingDatum.java:135)
oracle. ...
what can i do?

Created
Bug 8976245 - EA1: UNIT_TEST: INVALID CONVERSION ERROR USING INTEGER PARAMETER
and have asked bug responder to keep you updated on status here in the forum.
Bad news is that any INTEGER parameter for which you specify a non-null value will fail.
Possibly helpful news is that if you create a 'clone' of you function using NUMBER as the data type, you can continue to experiment with how unit testing may be of use to you.
Sorry no instant answer. :(
Brian
SQL Developer Team

Using a packaged function in a query

Hi ,
I have read the following statement (correct option for the question)in 1z0-147 questions.
The question is :: WHEN USING A PACKAGED FUNCTION IN A QUERY which of the following is true ::
The packaged function cannot execute DML statements against the table that is being queriedI tried the following to understand the above statement
create or replace package test_pk is
function fn_test(i number) return number ;
end;
create or replace package body test_pk is
function fn_test (i number) return number is
j number:=1;
begin
    insert into a values(200,300);
    commit;
   return j;
   end;
end test_pk; Upon executing the above function in the select statement
select TEST_PK.FN_TEST(1) from dualI got the error saying that Can't perform DML Inside SElect
Is this example for the above statement is TRUE ????
Could you please explain me if my example is wrong
Thanks
Edited by: Smile on Nov 22, 2012 9:47 AM

No, it is not true. Any function used in SQL is not allowed to perform a DML operation other than SELECT regardless if it is against the table that is being queried or not. Select is allowed against any table. And function in your example does INSERT which is not allowed. Also, Any function used in SQL is not allowed to perform commit/rollback/savepoint.
SY.
Edit: unless function is autonomous transaction.
Edited by: Solomon Yakobson on Nov 22, 2012 10:22 AM

Calling a package function inside a sql

Hi friends!!!
First of all happy Christmas! And them please help! :)
We have a query calling a package function:
SELECT * FROM DW025H WHERE DW025H_NR=MPPCI.ENCR ('0000000000000000');There is a primary key just with one column DW025H_NR and the problem is that is not accessing by INDEX UNIQUE SCAN,
it's accessing by TABLE ACCESS FULL.
May be the problem is that we are calling a procedure inside the query?
I have been able to run that query accessing by primary key from my computer but a workmate hasn't!
We both are connecting the same data base 10.2.0.4 and using Oracle SQL Developer!
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 5343K| 1406M| 15670 (7)| 00:02:43 |
|* 1 | VIEW | DW025H | 5343K| 1406M| 15670 (7)| 00:02:43 |
|* 2 | FILTER | | | | | |
| 3 | TABLE ACCESS FULL| DW025H | 5343K| 1406M| 15670 (7)| 00:02:43 |
Predicate Information (identified by operation id):
1 - filter("DW025H_NR"="MPPCI"."ENCRIPTAPAN"('0000000000000000'))
2 - filter(CASE "OPS$SISINFO"."IS_USER_DNI"() WHEN 1 THEN
SYS_AUDIT('OPS$SISINFO','DW025H','CMINFOGR001',3) ELSE NULL END IS
NULL)
The correct path would be:
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 276 | 3 (0)| 00:00:01 |
|* 1 | FILTER | | | | | |
| 2 | TABLE ACCESS BY INDEX ROWID| DW025H | 1 | 276 | 3 (0)| 00:00:01 |
|* 3 | INDEX UNIQUE SCAN | PK_DW025H | 1 | | 2 (0)| 00:00:01 |
Predicate Information (identified by operation id):
1 - filter(CASE "OPS$SISINFO"."IS_USER_DNI"() WHEN 1 THEN
SYS_AUDIT('OPS$SISINFO','DW025H ','CMINFOGR001',3) ELSE NULL END IS NULL)
3 - access("DW025H_NR"="MPPCI"."ENCR"('0000000000000000'))
Please any ideas!?!?!
Thanks a lot!
José
Edited by: jamv on Dec 20, 2011 10:50 AM

Hello
Have a read of this and try to pull together the information in it and post it up here. That will help immensely with getting to the root of your problem...
HOW TO: Post a SQL statement tuning request - template posting
In the mean time:
From the execution plan you have extra predicates that aren't present in the query you supplied, so that's either not the SQL or you have something like VPD switched on.
Anyway, there could be lots of reasons for the difference in execution plan. Sorry if this is very basic and possibly patronising question but it's always worth checking the basics I think - are you both definitely connecting to the same database? If so, have a look in v$sqlarea for this SQL statement and find the SQL_ID, use this to query v$sql and look at the child_number column.
select
    sql_id
from
    v$sqlarea
where
    sql_text like '%SELECT * FROM DW025H WHERE DW025H_NR=MPPCI.ENCR%(''0000000000000000'')%'
and
    sql_text not like '%v$sqlarea%'
select child_number from v$sql where sql_id='<enter the sql id returned by the query above>'as an example...
XXXX> select /* my sql statement*/ rownum id from dual;
        ID
         1
1 row selected.
Elapsed: 00:00:00.10
XXXX> select sql_id from v$sqlarea where sql_text like '%my sql statement%'
and sql_text not like '%v$sqlarea%';
SQL_ID
a6ss4v79udz6g
1 row selected.
Elapsed: 00:00:03.56
XXXX> select child_number from v$sql where sql_id='a6ss4v79udz6g'
2 /
CHILD_NUMBER
           0
1 row selected.   If you have more than one row in v$sql there could be differences in the optimiser environment. The supplied like shows you how to gather the information that should help find what the differences are if any.
Also as a side note if you're calling PL/SQL functions from SQL, you can take advantage of subquery caching to help reduce the number of calls (depending on your version). As it stands, your function is most likely going to be called for every row - when there is only a single row returned, that's not necessarily a problem but for multiple rows, the overhead can quickly grow. If there's no way to get rid of the function call, select the function from dual instead i.e.
SELECT * FROM DW025H WHERE DW025H_NR= (SELECT MPPCI.ENCR%('0000000000000000') FROM dual);This also (as I learnt a couple of weeks ago) works when you're using columns in the table your selecting from as parameters to the function.
HTH
David

Use a package function inside a select of the same package

Hi.
How can i use a function defined inside a package, with a select used inside that same package ?
Example
... package example
CREATE OR REPLACE PACKAGE BODY pkg_example
AS
     FUNCTION sum_two_values(p_val1 NUMBER,p_val2 NUMBER) RETURN NUMBER
     IS
     BEGIN
     RETURN p_val1 + p_val2;
     END sum_two_values;
     FUNCTION use_another_function_example RETURN VARCHAR2
     IS
     v_value NUMBER;
     BEGIN
     SELECT sum_two_values(2,2) INTO v_value FROM dual;
     RETURN 'waaaazzzzupppppp'
     END use_another_function_example;
END pkg_example;
This will not work
-- SELECT sum_two_values(2,2) INTO v_value FROM dual;
How can i call a function inside a select statement, a function of the same package where the query is being called.
(i have Oracle 9.2x)
Cheers.

are you sure? you are not using package1, you are using pack1
SQL> CREATE OR REPLACE PACKAGE package1
2 IS
3     FUNCTION f1
4        RETURN NUMBER;
5
6     FUNCTION f2
7        RETURN NUMBER;
8 END;
9 /
Package created.
SQL> CREATE OR REPLACE PACKAGE BODY package1
2 IS
3     a   NUMBER;
4
5     FUNCTION f1
6        RETURN NUMBER
7     IS
8     BEGIN
9        RETURN 1;
10     END;
11
12     FUNCTION f2
13        RETURN NUMBER
14     IS
15     BEGIN
16        SELECT package1.f1
17          INTO a
18          FROM DUAL;
19
20        RETURN a;
21     END;
22 END;
23 /
Package body created.
Why not just this
SQL> ed
Wrote file afiedt.buf
1 CREATE OR REPLACE PACKAGE BODY package1
2 IS
3     a   NUMBER;
4     FUNCTION f1
5        RETURN NUMBER
6     IS
7     BEGIN
8        RETURN 1;
9     END;
10     FUNCTION f2
11        RETURN NUMBER
12     IS
13     BEGIN
14        a:= f1;
15 RETURN a;
16     END;
17* END;
SQL> /
Package body created.formatted
Message was edited by:
devmiral

Using package functions in an update

Okay, I have a package function that returns a correct value when used in a SELECT, but when used in an UPDATE, it returns Null. Why can't I used its result in the UPDATE?
Package Spec
FUNCTION fpub_get_contract_attribute
     (     n_contract_id_in                    IN               CONTRACT.CONTRACT_ID%TYPE,
          s_attribute_in                         IN               VARCHAR2 )
RETURN VARCHAR2;
PRAGMA RESTRICT_REFERENCES(fpub_get_contract_attribute,TRUST,WNDS);
Source :
clear;
rollback;
select
     contract_functions.fpub_get_contract_attribute(CONTRACT_ID,'ORIGINAL_SALES_CHANNEL') "Before",
     original_sales_channel
from contract
where contract_id = 52549615;
update contract
set original_sales_channel = NVL(contract_functions.fpub_get_contract_attribute(CONTRACT_ID,'ORIGINAL_SALES_CHANNEL'),'Null')
where contract_id = 52549615;
select
     NVL(contract_functions.fpub_get_contract_attribute(52549615,'ORIGINAL_SALES_CHANNEL'),'Null') "After",
     original_sales_channel
from contract
where contract_id = 52549615;
rollback;
Result :
Rollback complete
Before                ORIGINAL_SALES_CHANNEL
RE
1 row updated
After                 ORIGINAL_SALES_CHANNEL
Null                  Null
Rollback completeAny ideas?
Thanks,
Jason

Pragma restrict_references has not been required since 8i, so you can get rid of that. However, certain things will still be enforced, with or without the pragma. For example, you cannot perform DML from within a packaged function when that function is used in a select statement, although you can perform DML within a packaged function when it is used in an update statement. So, if you are performing some sort of DML in your function, it would not raise an error when used in the update statement, but would cause it to return whatever is specified in the exception block when used in a select statement, causing the different results.
Please see the demonstration below in which I have created a sample function that contains an insert statement. When I use the function from a select statement, it raises an error and does not insert a row. However, when I use the function in an update statement, it does not raise an error and inserts a row. I have then added an exception clause to the function and re-tested. When I used the function in a select statement, it now returns the value in the exception block, but still does not insert a row. When I used the function in an update statement, it returns a different value, not from the exception block, and inserts a row. Then I removed the insert statement from the function and re-tested. Now it returns the same value, whether used in a select statement or an update statement.
scott@ORA92> SELECT banner FROM v$version
2 /
BANNER
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
PL/SQL Release 9.2.0.1.0 - Production
CORE     9.2.0.1.0     Production
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production
scott@ORA92> CREATE TABLE test
2    (col1 VARCHAR2(30))
3 /
Table created.
scott@ORA92> CREATE TABLE contract
2    (contract_id            NUMBER,
3      original_sales_channel VARCHAR2(30))
4 /
Table created.
scott@ORA92> INSERT INTO contract (contract_id) VALUES (52549615)
2 /
1 row created.
scott@ORA92> COMMIT
2 /
Commit complete.
scott@ORA92> CREATE OR REPLACE PACKAGE contract_functions
2 AS
3    FUNCTION fpub_get_contract_attribute
4       (n_contract_id_in IN CONTRACT.CONTRACT_ID%TYPE,
5        s_attribute_in   IN VARCHAR2 )
6       RETURN            VARCHAR2;
7 END contract_functions;
8 /
Package created.
scott@ORA92> SHOW ERRORS
No errors.
scott@ORA92> -- test with insert statement and no exception handling:
scott@ORA92> CREATE OR REPLACE PACKAGE BODY contract_functions
2 AS
3    FUNCTION fpub_get_contract_attribute
4       (n_contract_id_in IN CONTRACT.CONTRACT_ID%TYPE,
5        s_attribute_in   IN VARCHAR2 )
6       RETURN            VARCHAR2
7    IS
8    BEGIN
9       INSERT INTO test (col1) VALUES ('inserting');
10       RETURN 'Null';
11    END fpub_get_contract_attribute;
12 END contract_functions;
13 /
Package body created.
scott@ORA92> SHOW ERRORS
No errors.
scott@ORA92> SELECT * FROM contract
2 /
CONTRACT_ID ORIGINAL_SALES_CHANNEL
   52549615
scott@ORA92> COLUMN "Before" FORMAT A30
scott@ORA92> select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "Before",
2          original_sales_channel
3 from   contract
4 where contract_id = 52549615
5 /
select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "Before",
ERROR at line 1:
ORA-14551: cannot perform a DML operation inside a query
ORA-06512: at "SCOTT.CONTRACT_FUNCTIONS", line 9
scott@ORA92> SELECT * FROM test
2 /
no rows selected
scott@ORA92> update contract
2 set    original_sales_channel = NVL (contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL'), 'Null')
3 where contract_id = 52549615
4 /
1 row updated.
scott@ORA92> SELECT * FROM test
2 /
COL1
inserting
scott@ORA92> COLUMN "After" FORMAT A30
scott@ORA92> select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "After",
2          original_sales_channel
3 from   contract
4 where contract_id = 52549615
5 /
select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "After",
ERROR at line 1:
ORA-14551: cannot perform a DML operation inside a query
ORA-06512: at "SCOTT.CONTRACT_FUNCTIONS", line 9
scott@ORA92> SELECT * FROM test
2 /
COL1
inserting
scott@ORA92> --
scott@ORA92> -- repeat test with insert statement and exception handling:
scott@ORA92> ROLLBACK
2 /
Rollback complete.
scott@ORA92> CREATE OR REPLACE PACKAGE BODY contract_functions
2 AS
3    FUNCTION fpub_get_contract_attribute
4       (n_contract_id_in IN CONTRACT.CONTRACT_ID%TYPE,
5        s_attribute_in   IN VARCHAR2 )
6       RETURN            VARCHAR2
7    IS
8    BEGIN
9       INSERT INTO test (col1) VALUES ('inserting');
10       RETURN 'Null';
11    EXCEPTION
12       WHEN OTHERS THEN RETURN 'RE';
13    END fpub_get_contract_attribute;
14 END contract_functions;
15 /
Package body created.
scott@ORA92> SHOW ERRORS
No errors.
scott@ORA92> select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "Before",
2          original_sales_channel
3 from   contract
4 where contract_id = 52549615
5 /
Before                         ORIGINAL_SALES_CHANNEL
RE
scott@ORA92> SELECT * FROM test
2 /
no rows selected
scott@ORA92> update contract
2 set    original_sales_channel = NVL (contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL'), 'Null')
3 where contract_id = 52549615
4 /
1 row updated.
scott@ORA92> SELECT * FROM test
2 /
COL1
inserting
scott@ORA92> select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "After",
2          original_sales_channel
3 from   contract
4 where contract_id = 52549615
5 /
After                          ORIGINAL_SALES_CHANNEL
RE                             Null
scott@ORA92> SELECT * FROM test
2 /
COL1
inserting
scott@ORA92> --
scott@ORA92> -- repeat test with no insert statement and no exception handling:
scott@ORA92> ROLLBACK
2 /
Rollback complete.
scott@ORA92> CREATE OR REPLACE PACKAGE BODY contract_functions
2 AS
3    FUNCTION fpub_get_contract_attribute
4       (n_contract_id_in IN CONTRACT.CONTRACT_ID%TYPE,
5        s_attribute_in   IN VARCHAR2 )
6       RETURN            VARCHAR2
7    IS
8    BEGIN
9       RETURN 'Null';
10    END fpub_get_contract_attribute;
11 END contract_functions;
12 /
Package body created.
scott@ORA92> SHOW ERRORS
No errors.
scott@ORA92> select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "Before",
2          original_sales_channel
3 from   contract
4 where contract_id = 52549615
5 /
Before                         ORIGINAL_SALES_CHANNEL
Null
scott@ORA92> SELECT * FROM test
2 /
no rows selected
scott@ORA92> update contract
2 set    original_sales_channel = NVL (contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL'), 'Null')
3 where contract_id = 52549615
4 /
1 row updated.
scott@ORA92> SELECT * FROM test
2 /
no rows selected
scott@ORA92> select contract_functions.fpub_get_contract_attribute (CONTRACT_ID, 'ORIGINAL_SALES_CHANNEL') "After",
2          original_sales_channel
3 from   contract
4 where contract_id = 52549615
5 /
After                          ORIGINAL_SALES_CHANNEL
Null                           Null
scott@ORA92> SELECT * FROM test
2 /
no rows selected
scott@ORA92>

Calling public package functions and variables through dblink

Is it possible to call a global public variable in a package in one database from another package procedure in another database using a database link? If so, could you let me know the syntax? Same question for package functions.

Hi,
check this documentation link especially the stmt...
http://www.mcs.csueastbay.edu/support/oracle/doc/10.2/appdev.102/b14251/adfns_packages.htm#i1007858
You cannot access remote package variables and constants.May be you can write a function in the remote db which when called will return the variable value.
for calling remote package functions...
syntax from documentation is [[schema.]package.]function_name[@dblink][(param_1...param_n)]
an example given in the above link for this...
EXECUTE fire_emp1@boston_server(1043);
Ravi Kumar
Edited by: ravikumar.sv on Aug 31, 2009 11:29 AM

Oracle Package Function

hello,
I have written a package function but I cannot call it from .net environment correctly.
I want to ask you that is there anything wrong in the package:
Specification Part:
CREATE OR REPLACE PACKAGE SAGECM AS
TYPE T_CURSOR IS REF CURSOR;
FUNCTION COUNTREQ
p_ID IN VARCHAR2,
p_version IN VARCHAR2,
num_of_req OUT NUMBER
RETURN NUMBER;
END SAGECM;
Body Part:
CREATE OR REPLACE PACKAGE BODY SAGECM AS
FUNCTION COUNTREQ
p_ID IN VARCHAR2,
p_version IN VARCHAR2,
num_of_req OUT NUMBER
RETURN NUMBER
IS
BEGIN
SELECT count(*) INTO num_of_req FROM SAGECM_REQ WHERE ID=p_ID AND Version=p_version;
return num_of_req;
END COUNTREQ;
END SAGECM;

is there anything wrong in the packageYes. You are attempting to RETURN an OUT parameter. This is bad. I suspect you don't understand the difference between a procedure and a function....
CREATE OR REPLACE PACKAGE SAGECM AS
TYPE T_CURSOR IS REF CURSOR;
FUNCTION COUNTREQ
p_ID IN VARCHAR2,
p_version IN VARCHAR2
RETURN NUMBER;
PROCEDURE COUNTREQ
p_ID IN VARCHAR2,
p_version IN VARCHAR2,
num_of_req OUT NUMBER
END SAGECM;
CREATE OR REPLACE PACKAGE BODY SAGECM AS
FUNCTION COUNTREQ
      p_ID IN VARCHAR2,
      p_version IN VARCHAR2
    RETURN NUMBER
IS
    return_value NUMBER;
BEGIN
    SELECT count(*) INTO return_value
    FROM SAGECM_REQ
    WHERE ID=p_ID AND Version=p_version;
    RETURN return_value;
END COUNTREQ;
PROCEDURE COUNTREQ
      p_ID IN VARCHAR2,
      p_version IN VARCHAR2,
      num_of_req OUT NUMBER
    ) IS
BEGIN
    num_of_req := COUNTREQ(p_ID,p_version);
END COUNTREQ;
END SAGECM;
/Note: the above is for illutrative purposes only and is not intended as an example of good programming practice!
Find out more in the docs!
Cheers, APC

How to execute a packaged function from within DML

Hi
can someone explain in how many ways can we execute a packaged function from within a DML statement.
examples will help.
Thanks

Hi,
There's no difference between using functions in DML and using functions in any other SQL statement. Almost any place where a literal is allowed, you can have any kind of expression, including a an expression involving one or more functions.
For example, in
UPDATE table_x
SET column_a = 0
WHERE column_b > SYSDATE;You could use functions instead of 0, column_b, or SYSDATE. (Actually, SYSDATE is a function.) You can not use functions instead of table_x or column_a (since it is to the left of the "=" sign).

Calling Package Function dynamically using Forms_DDL

I am trying to write a validation trigger which will validate entries within a text field. It will call a packaged function based on an entry within the Rule form field. As the data within the text field will vary (sometimes numeric, date, text etc), the validation function will also vary accordingly. Example details are shown below (this example will force the entry of a Y or an N):
FORM FIELDS
ARG_DEFAULT1 X (This is the parameter to be submitted to the function)
RULE1 VAL_CHK_0001 (Function to be called).
FUNCTION CODE
FUNCTION VAL_CHK_0001 (P1 VARCHAR2) RETURN NUMBER IS
SQL_RESULT NUMBER;
ALERT_ID ALERT;
ALERT_OK NUMBER;
BEGIN
IF UPPER(P1) NOT IN ('Y', 'N') THEN
:GLOBAL.MSG := 'You must enter either "Y" for Yes or "N" for No - please re-enter';
SQL_RESULT := '1';
ALERT_ID := FIND_ALERT('VAL_ERROR_ALT');
SET_ALERT_PROPERTY(ALERT_ID, TITLE, 'Validation Error');
SET_ALERT_PROPERTY(ALERT_ID, ALERT_MESSAGE_TEXT, :global.msg);
ALERT_OK := SHOW_ALERT(ALERT_ID);
RAISE FORM_TRIGGER_FAILURE;
RETURN SQL_RESULT;
ELSE
SQL_RESULT := '0';
RETURN SQL_RESULT;
END IF;
END VAL_CHK_0001;
VALIDATION TRIGGER CODE (CURRENT)
DECLARE
PKG_RUN VARCHAR2(200);
BEGIN
IF :PARAMETER_BK.RULE1 IS NOT NULL THEN
PKG_RUN := ENV_VALIDATE_PKG.VAL_CHK_0001(:PARAMETER_BK.ARG_DEFAULT1)):
FORMS_DDL(PKG_RUN);
END IF;
END;
When the Rule1 field data is hard coded in (as shown above), it all runs fine and the Alert box is displayed as expected.
I need the function name to refer to the rule1 parameter (and not a specific value) as shown below:
PKG_RUN := 'ENV_VALIDATE_PKG.'||:PARAMETER_BK.RULE1||'('||:PARAMETER_BK.ARG_DEFAULT1||')';
The form compiles without any errors but when the trigger runs, it completely ignores the Forms_ddl call and does nothing.
I have hunted through this forum, Metalink, Ask Tom etc and have had no success in finding any solution. I have followed the instructions within NOTE:1017160.6 (How to programmatically call a procedure or function using Oracle Forms) which has got me this far. Nothing that I have read so far has suggested that what I am attempting to do is impossible.
We are using Oracle Forms 10G with an Oracle 9.0.4 database.
Any suggestions or advice will be greatly received!
Thanks

Like the others have said, Forms_DDL is a one-way street. You can only pass values to it, nothing can be returned. But you could probably get Forms_DDL to work if you wrote your validations as stored procedures that had only IN parameters. Then if the edit ran ok, just terminate normally, but if there is an edit error, to a Raise_application_error.
Then you could use Forms_DDL to call the procedure, and check for Form_Success after the call. If it failed, you might be able to retrieve the error message from the Raise_application_error by checking SQLERRM. But that is completely untested, so I do not know whether it would work.
The more sure method would be to call a package procedure on the database that calls Execute_Immediate, and then returns the result back to the calling form.
Now a little advice: For generic routines such as this, pass dates and numbers as text, and you could cut down on the number of procedures you need to create and use.
And last note: Do NOT define numeric variables, like SQL_Result, and then set the value using quotes. You are forcing the PL/SQL process to convert text to number. Always set numeric values like this:
SQL_Result := 1;
Now the question I am almost afraid to ask: What problem are you solving by creating these generic edit routines? I am wondering if you could just as easily write simple edit processes faster. ...the only way to completely parameterize editing would be to call a process on the database for each column value, passing the column name and value.

DBMS_JOB using Packaged Functions but Package goes invalid

Is there any way to check a package while running a PL/SQL procedure to see if it's state is valid and then catch the exception?
In my case usually just calling any function in the package 1x clears it up but the procedure in question runs as a DBMS_JOB it just keeps failing. This procedure could run often enough that Oracle will mark it as broken but I want to give it every shot at execution on time instead of having to make it wait till the next cycle.
What I would like to do is to catch the exception for the package state being invalid and basically have it go back to the beginning of the procedure and give it another try before failing in case it is just a failure because the package has been altered.
Is there any way to do this?

Firstly, I'll copy/paste my standard response regarding package state going invalid as it usually helps to have an understanding of these things...
Packages tend to fail because of their "package state". A package has a "state" when it contains package level variables/constants etc. and the package is called. Upon first calling the package, the "state" is created in memory to hold the values of those variables etc. If an object that the package depends upon e.g. a table is altered in some way e.g. dropped and recreated, then because of the database dependencies, the package takes on an INVALID status. When you next make a call to the package, Oracle looks at the status and sees that it is invalid, then determines that the package has a "state". Because something has altered that the package depended upon, the state is taken as being out of date and is discarded, thus causing the "Package state has been discarded" error message.
If a package does not have package level variables etc. i.e. the "state" then, taking the same example above, the package takes on an INVALID status, but when you next make a call to the package, Oracle sees it as Invalid, but knows that there is no "state" attached to it, and so is able to recompile the package automatically and then carry on execution without causing any error messages. The only exception here is if the thing that the package was dependant on has changes in such a way that the package cannot compile, in which case you'll get an Invalid package type of error.
And if you want to know how to prevent discarded package states....
Move all constants and variables into a stand-alone package spec and reference those from your initial package. Thus when the status of your original package is invlidated for whatever reason, it has no package state and can be recompiled automatically, however the package containing the vars/const will not become invalidated as it has no dependencies, so the state that is in memory for that package will remain and can continue to be used.
As for having package level cursors, you'll need to make these local to the procedures/functions using them as you won't be able to reference cursors across packages like that (not sure about using REF CURSORS though.... there's one for me to investigate!)
This first example shows the package state being invalided by the addition of a new column on the table, and causing it to give a "Package state discarded" 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        VALIDAnd this next example shows how having the package variables in their own package spec, allows the package to automatically recompile when it is called even though it became invalidated by the action of adding 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.---------------------------------------------------------------------------------------------
Secondly, from this above standard response, you can see how to check for package state if you want to determine it programatically.
;)

New ISC BIND packages [Security Advisory]

Hi there.
A new version of BIND 9.3.x (9.3.4) has been released addressing a DoS vulnerability as seen on SecurityFocus:
http://www.securityfocus.com/bid/22231
I don't know what's the "legal" procedure, maybe I had to mark the bind package as old before posting or something, but I just wanted to let the developers know about this.
Thanks for paying attention... now I'll go and mark bind as old.
Last edited by ckristi (2007-01-30 06:22:08)

Thanks for the answer. I am using Arch as my primary workstation OS. And I am a very happy user. But I think it feels bad to see, for example, updates for beryl and not for a security advisory. I am kind of a "Linux literate". I will always use Slackware for a server due to its stability. But speed of Arch and the easiness in using it made me think that at some point I could switch at least my home server to Arch, too. Also I can and, if that's the case, will compile my possibly vulnerable program from sources before an updated package is in the repo (and if I or some security advisory site thinks it is a critical vulnerability). I was just thinking about people who think they're safe if they run "pacman -Syu" at least every day and who don't have "securityfocus dot com" or some other security advisory site in their bookmarks menu. I am one of the people who just occasionally visits securityfocus.com just to see how serious is a problem. And now, what dragged me to securityfocus was the update of bind in Slackware and Fedora which happened 4-5 days ago and no bind update for Arch.

Calling Oracle Package Function from Visual Basic

Hi,
Oracle Client 8.04
Oracle ODBC Driver 8.00.04
VB 6.0
Windows 2000
I'm stumped here. I want to have a Oracle stored procedure run a
query and return a result set which I can assign to a recordset
object in VB. Based on things I've read here and on MS's site,
here's what I've done:
In the Oracle Schema Manager under the Packages folder I created
the following package:
PACKAGE test
IS
TYPE test_cur IS REF CURSOR;
FUNCTION mycur RETURN test_cur;
END test;
and under the Package Body folder created:
PACKAGE BODY test
IS
FUNCTION mycur RETURN test_cur
IS
c_return test_cur;
BEGIN
OPEN c_return FOR
SELECT * FROM table_A;
RETURN c_return;
CLOSE c_return;
END mycur;
END test;
They both compile without errors and in Oracle SQL Worksheet I
can enter the following:
variable x refcursor;
execute :x :=test.mycur;
print x;
and the query results are displayed as expected.
The problem is trying to get the result back into a VB recordset
object.
In VB 6.0 I have done this:
Dim RS As ADODB.Recordset
Dim Conn As ADODB.Connection
Dim sConnection As String
Dim sSQL As String
sSQL = "{call test.mycur}"
sConnection = "Provider=MSDASQL;UID=" & sUserID & ";PWD=" &
sPassword & ";Driver={Microsoft ODBC for Oracle}; Server=" &
sInstance & ";"
Conn.Open sConnection
RS.CursorLocation = adUseClient
RS.Open sSQL, Conn, adOpenForwardOnly, adLockOptimistic,
adCmdStoredProc ' or adCmdText
but get:
?err.Number -2147217900
?err.Source Microsoft OLE DB Provider for ODBC Drivers
?err.Description [Microsoft][ODBC driver for Oracle]Syntax error
or access violation
The problem is not with the connection or permissions, since the
query works fine when I just use the select statement in the
package function as the string, instead of calling the function
in the package (eg sSQL = "Select * from table_A") and can
process the resulting recordset in VB.
I've also tried variations using:
Set RS = Conn.Execute("{call test.mycur}")
or using a Command object something like:
Dim com As ADODB.Command
Set com = New ADODB.Command
With Conn
.ConnectionString = sConnection
.CursorLocation = adUseClient
.Open
End With
With com
.ActiveConnection = Conn
.CommandText = sSQL
.CommandType = adCmdText
End With
Set RS.Source = com
RS.Open
But still get the same errors. Any help is appreciated. Also, in
my package body, is it necessary to explicitly close the cursor,
or does the function just exit when it executes the return and
not ever hit the close statement?
Thanks,
Ed Holloman

Hi
i don't know if you got your answer, but i work with VB and
Oracle.
the procedure in the DB should have the cursor like you writen
in your mail.
to call a procedure in Oracle and get the data back
into a recordset you shuld use a Command object like this:
Dim conn As ADODB.Connection
Dim cmd As ADODB.Command
Dim rs As ADODB.Recordset
Set conn = CreateObject("adodb.connection")
Set cmd = CreateObject("adodb.command")
Set rs = CreateObject("adodb.recordset")
With conn
.ConnectionString = ""
.CursorLocation = adUseClient
.Open
End With
'THE IMPORTENT SECTION IS THIS WHERE YOU SET THE COMMAND TO THE
STORE PROCEDURE TYPE
With cmd
.ActiveConnection = conn
.CommandText = "proc.fun"
.CommandType = adCmdStoredProc
End With
'Then you set the rs to the command
Set rs = cmd.Execute
Set conn = Nothing
Set rs = Nothing
Set cmd = Nothing

OMBPlus example to bind package function to premapping_process operator

Similar Messages

Maybe you are looking for