Reuse Variable In Packages

I have a scenario where I need to reuse the variable in several packages without refreshing it. For example I have package 1, 2 and 3. I have defined a variable var_timestamp with latest value and declare this variable in package 3, I have generated scenario of package 1 and 2 and insert it in package 3. I refresh the variable as first step and reuse the variable in package 1 and 2 without refreshing it but var_timestamp value is not recognized in package 1 and 2.I didn't declare these variable in package 1 and 2 as I dont want it to be refresh again. I have tried Not Persistant variable as well but it didn't work. Any clue how can we reuse the variable without refreshing it in different packages.
Thanks
Kash

When you use a variable in a package it is important to declare it
Use the variable as Latest Value
Dont use the Historize or Persistent
If you have declared and refreshed it in package 3.......there might be 2 steps right?
1st step as declare and another step as refresh
In your packages 1 & 2, you should make a step as declare variable only, where you should drag your variable in the package and make it a declare variable step
And re-generate the scenario to be able to get the effect of this change in your scenario
Let me know in case you face any difficulties

Similar Messages

How do I use bin variable in package without asking a user?

hi,
I would like to write an SQL but I want to use bind variable in package as a static without asking user? Like below?
I would like to ask you, below there is a emp_id variable? Is this BIND variable?
DECLARE
bonus NUMBER(8,2);
emp_id NUMBER(6) := 100;
BEGIN
SELECT salary * 0.10 INTO bonus FROM employees
WHERE employee_id = emp_id;
END;
If not, like this SQL how can define a BIND variable as static inside a code? not asking a user?
db version. 9.2.0.8
regards and thanks

OracleADay wrote:
I would like to ask you, below there is a emp_id variable? Is this BIND variable?
DECLARE
bonus NUMBER(8,2);
emp_id NUMBER(6) := 100;
BEGIN
SELECT salary * 0.10 INTO bonus FROM employees
WHERE employee_id = emp_id;
END;
/In the query "SELECT salary * 0.10 INTO bonus FROM employees WHERE employee_id = emp_id" emp_id is turned into a bind variable because
if you are coding static SQL in PL/SQL then PL/SQL wil automatically use bind variables: please read http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/overview.htm#sthref145.
This can also be proved with SQL trace. The following code:
alter session set sql_trace=true;
declare
v number;
c number;
begin
select count(*) into c
from t
where x=v;
end;
show errors
alter session set sql_trace=false;generates following raw trace file section with 10G XE:
=====================
PARSING IN CURSOR #2 len=79 dep=0 uid=69 oct=47 lid=69 tim=33338762257 hv=2860574766 ad='3c10120c'
declare
v number;
c number;
begin
select count(*) into c
from t
where x=v;
end;
END OF STMT
PARSE #2:c=46800,e=329811,p=0,cr=9,cu=0,mis=1,r=0,dep=0,og=1,tim=33338762253
=====================
PARSING IN CURSOR #1 len=35 dep=1 uid=69 oct=3 lid=69 tim=33338788761 hv=3539261652 ad='3c10053c'
SELECT COUNT(*) FROM T WHERE X=:B1
END OF STMT
PARSE #1:c=0,e=216,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=1,tim=33338788755
=====================Edited by: P. Forstmann on 17 mai 2011 17:47
Edited by: P. Forstmann on 17 mai 2011 17:55

Global Variable in Package Specification

Hello,
I created global variable in package specification,
Is it valid for the current session or it will work for all the session.
Thanks,Kannan.K

Package varaibles are session bound, to demonstrate, a simple test:
--session 1:
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
SQL> exec dt_test_pack.set_global(50);
PL/SQL procedure successfully completed.
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
        50
--Session 2 at the same time
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
SQL> exec dt_test_pack.set_global(100);
PL/SQL procedure successfully completed.
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
       100
--Back to session 1:
SQL> exec dt_test_pack.set_global(null);
PL/SQL procedure successfully completed.
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
--Back to session 2:
SQL> select dt_test_pack.get_global from dual;
GET_GLOBAL
       100HTH
David

Query property "Save and reuse variable value" doesn't work in BW EHP1

We have a workbook which contain 4 queries, every different worksheet is a different query.
All the queries are on the Same InfoCube and all the queries use the same variables.
In the properties of the query n.2 we set the parameter "Save and reuse variable values" then we refresh the 1st query and all work fine (the system asks the variable values) but when we refresh the 2nd query the system doesn't use the same variable values that we have inserted for the query n.1
We don't have the same problem in 7.0.
Any help is appreciated.
Luca

Hi,
I suppose, you need to set the 'Save and reuse variable values' for each query individually in the workbook. I am not sure however there is a option where you can specify to apply the settings of one query to all queries in the work book.
Please check and hope it helps.
Regards,
Adarsh Mhatre

What are the Advantages & Disadvantages of Global Variable at Package Level

Dear Expprts
Please tell me,
What is mean by Global Variable?
What are the Advantages and Disadvantages of Global Variable at Package Level against Private Variable?

HI
GLOBAL VARIABLE UR USE ANY BLOCK IN PLSQL
BUT LOCAL VARIABLE USED ONLY THERE THEY DECLARE.
REGARDS
MOHAMMADI

Passing Record Variable through Packages

I have a question and hope that someone can help me to find the solution.
I'm developing an application and I need to pass values form one procedure PR in package B to a function FN in package A. The why I try to go is passing the values by using a variable of record type.
I have defined in both packages the same record structure that I also use in the declarations of procedure and function. I first compiled successfully the package A but when I try to compile the package B I get a compilation error:
PLS-00306: wrong number or types of arguments in call to 'B.FN'
It looks like the parameter definition or reference gets lost.
Here below a very schematic example of my application:
create or replace package A is
type Rec1 is record
( rf1 T.f1%type,
rf2 T.f2%type,
rf3 T.f3%type)
function FN ( Par in Rec1 ) return boolean;
end;
create or replace package A is
function FN ( Par in Rec1 ) return boolean is
V_ret boolean;
begin
whatever it does
return V_ret ;
end;
end;
create or replace package B is
type Rec1 is record
( rf1 T.f1%type,
rf2 T.f2%type,
rf3 T.f3%type)
procedure PR ( Par in Rec1 ) return boolean;
end;
create or replace package B is
procedure PR ( Par in Rec1 ) is
VP Rec1;
V_go boolean;
begin
VP.rf1:= something_1;
VP.rf2:= something;
VP.rf3:= something;
V_go:=FN ( VP ); <= here the compiler complaints
whatever it does
end;
end;
Many thanks for a quick answer.

Okay I didn't notice the error message text in the body of the paragraph above.
PS. If I specify singularly the fields in the parameter list I pass the compilation
but I would like to use a record variable as one.Did you see my post where I always reference the record variable in package A?
create or replace package B is
procedure PR ( Par in A.Rec1 ) return boolean;
end;
create or replace package B is
procedure PR ( Par in A.Rec1 ) is
VP A.Rec1;
V_go boolean;
begin
VP.rf1:= something_1;
VP.rf2:= something;
VP.rf3:= something;
V_go:=A.FN ( VP ); <= here the compiler complaintsIt should work.

Trouble passing variable into package

I am having an issue reading a variable in a script task that I'm passing in from a windows service. I should be able to pass the param in from .NET and load it into one of my package vars right? The windows service is a file watcher service.
Windows Service code
                    Package pkg;
                    Application app;
                    DTSExecResult pkgResults;
                    Variables vars;
                    app = new Application();
                    pkg = app.LoadPackage(pkgLocation, null);d because I log it to a log file.
                    vars = pkg.Variables;
                    vars["User::FileName"].Value = sFileName.ToString();
                    pkgResults = pkg.Execute(null, vars, null, null, null);
The sFileName variable in the service is populated because I write it to a log file.
In the package I list the FileName variable as read/write. Have checked the spelling.
package code snippet:
      public void Main()
      //get file and path info
      string sFileName = Dts.Variables["User::FileName"].Value.ToString();
the package fires but the variable is empty and I log an exception to the sysssislog:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentOutOfRangeException: Index and length must refer to a location within the string. Parameter name: length
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)     at ST_5a4733488a6149abb109d633296e2c38.csproj.ScriptMain.Main()     --- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)     at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)     at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object
target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)     at Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTATaskScriptingEngine.ExecuteScript()
I cannot find what the issue is. In the package I log to a text file the value of FileName variable and as expected it is empty.
I appreciate your help wit

The scripting task which is designed to retrieve the file name from the package var User::FileName is listed in the scripting tasks read/write variables and it is a package level variable. Is that what you mean by "expects" Arthur? If so then yes. But is
there a property setting on the script task that has to be set?
I could use the config file but the file name changes daily with a date stamp suffix. I could also just sweep the directory when the file watcher executes the package but that all seems so sloppy considering that I should be able to pass the filename in
as a variable.
Thanks for talking through this with me. I appreciate it.

Using global variable in package

Hi. I have created a function (Retrieve_SerialNo) which returns a variable, which I use throughout my package. I would like to assign this variable as a global variable to be used by all functions and procedures in the package. Can someone help me in the declaration of this variable as a global variable? Also, is it necessary for me to initialize this variable whenever the package executes. If yes, how would I do this?
CREATE OR REPLACE PACKAGE BODY Supply_Item_Interface AS
FUNCTION Retrieve_SerialNo RETURN VARCHAR2 IS
    v_serial_no VARCHAR2(20);
    CURSOR Serial_Code IS
      SELECT S.Serial_Code
        FROM Spare_Parts s, Orders r
       WHERE s.serial_code = r.serial_code;
BEGIN
    OPEN Serial_Code;
    LOOP
      FETCH Serial_Code
        INTO v_serial_no;
      EXIT WHEN Serial_Code%NOTFOUND;
      v_serial_no := v_serial_no;
    END LOOP;
    CLOSE Serial_Code;
    RETURN v_serial_no;
EXCEPTION
    WHEN OTHERS THEN
      RETURN NULL;
END;

user13415143 wrote:
Hi. I have created a function (Retrieve_SerialNo) which returns a variable, which I use throughout my package. I would like to assign this variable as a global variable to be used by all functions and procedures in the package.All variables have scope or "visibility". A variable defined in a procedure is only visible within that procedure.
A variable defines in a package body. is visible within that package body (i.e. procedures and functions in that package body can "see" that variable.
A variable defined in the package definition? Well, who can see the definitions of procedures and function in a a package header/definition? Everyone else basically (other PL/SQL packages and procedures and functions). So this is also true for variables defined in the package interface. These are global variables that not only can be used by the code in that package's body, but also can be used by other packages and PL/SQL code.
So when you create a global variable you need to decide on its scope:
- define it in package header for global usage in all PL/SQL code
- define it in package body for global usage within that package only
CREATE OR REPLACE PACKAGE BODY Supply_Item_Interface AS
..snipped..Ugly code as there is no need to use an explicit cursor if returning a value from a single row. Also buggy code. If there are multiple rows returned by the cursor, the function returns the serial of the last random row. How does this make sense?
This is what I would expect to see from a function like this. You pass it a unique identifier and it returns the applicable attribute (column) value for it.
E.g.
create or replace function GetSerialNo( orderNo number ) return number is
serialNo number;
begin
select
    s.serial_code into serialNo
from spare_parts s,
       orders o
where s.serial_code = o.serial_code
and o.order_no = orderNo;
return( serialNo );
exception when NO_DATA_FOUND then
return( null )
end;Also note that there is no need to write ugly uppercase code. This is not a proper coding standard. Programming standards for all languages (ranging from C# to Java to Delphi to Visual Basic to C/C++) specify that camelcase should be used for variables and pascalcase for procedures/functions/methods. Uppercase is very seldom used and then only for constant names and compiler options/flags for example.
Coding reserved words in uppercase? That is just plain silly - and not found in today's programming languages. Do yourself a favour and forget the idiotic standards used by some for PL/SQL and look at the standards for Java and .Net/C# - as the latter are the de facto standards for programming (and have been for the last 2 decades and more).

&& Substitution Variable in Package Body using SQL Developer

Hi Folks,
I've moved over to working to in SQL Developer (its a very early version - 1.0.0) from a combination of SQL*Plus command line and a text editor. I'm trying to get this upgrgraded, but I think the question will be the same with a newer version anyway.
I am creating a package, and in the package body I have some &&my_var substitutions that I was previoulsy prompted for when calling the .sql from the command line SQL*Plus. I need this as the variable needs to be different for the development and live environment.
When working in SQL Developer, I can load the package body from Connection->Packages->My Package->My Package Body, and click the edit button to edit the code, however, when I click the Compile button in the top of the window my code error's because of the substituion variablle. An example is:
CREATE OR REPLACE
PACKAGE BODY MY_PACKAGE AS
PROCEDURE MY_PROCEDURE
BEGIN
my_variable := &&my_function_from_live_or_dev_database
END MY_PROCEDURE
Can anyone tell me if there is a way of defining a compiler variable within the IDE widow while editing a package body stored in the database, without manually copying the code into the Worksheet and running it as a script?
Thanks,
AM

953104 wrote:
Thanks for the reply, the code was just quickly typed to show the sort of thing I am doing, it wasn't actual code form my project.
I've come from a C background so what I would have done would be create a #define and changed to when on live or development - or passed the variable to the build environment from the IDE or makefiles and the change would have reflected through my whole project.
What I want to be able to do is alter a definition of some sort that will reflect throughout my whole project, so I can change it in one location to minimize code changes before going live. I don't really want to be prompted at all. On one system it needs to be DEV_10 and on the other it needs to be LIVE_10.Is there a possibility to elimiante this difference at all?
For example if DEV_10 is the oracle schemauser on the development database and LIVE_10 would be the one on the production system. THen you could just remove all references to the schema from your code.
IF you are already connected to this schema, then you don't need to specify the schema name anymore.
example
instead of
create or replace package dev_10.myPackage
...you can simply use
create or replace package myPackage
...If needed you can alter the cuurently connected user just before you run the script.
alter session set current_schema = LIVE10;
create or replace package myPackage
...This would be a different working window in the developer (script worksheet, instead of direct pl/sql editor).
Substitution variables are allowed there.

ODI-SET VARIABLE IN PACKAGE

HI.
I am using odi11g.
i set variable "STARTTIME" To sysdate .
And "END_DATE" to a default value-- '20-JUNE-1981'.
Now in package i dropped the variable "end_date",and put the TYPE to "SET VARIABLE" and the value as below:
#VARIABLES_STARTTIME.[ The projects name is VARIABLES]
But the value of "end-date" isnt getting reset to STARTTIME.
should there be a different syntax.

HI,
Refresing the variable is working thanks.BUT i was trying to use the variable in a loop.
Where when the package is run fo rthe 1'st time the variable 'LAST_UPDATE' value should be '20-JUNE-1981' and then it should get set to the value present in 'STARTTIME" for the next time the package is run.
So, in this case, i need to set the value of the variable in the package itself.
#VARIABLES.STARTTIME isnt getting set.
i tried the package as per the below link:[ i use odi1g though]
http://blogs.oracle.com/dataintegration/entry/using_variables_in_odi_the_tim

Persistent variable in package

Hey,
I am not sure where exactly to ask about this, so if I posted in the wrong forum forgive me.
My problem is this: I am writing an application which interacts with a remote server using the functions in the utl_tcp package. This works with no problems in testing, but after I put a web interface on it I discovered that what I thought were global variables (defined in the package spec) are being reset every time a new call is made to the server. The interface works by repeatedly calling a certian function in my package which checks the tcp stream (what I want to be my 'global' variable) for any new information coming downstream. When it does this though the stream is gone, the variable has been reset with every request.
I tested this with a more simple variable too to make sure it just wasnt some quirk of the tcp connection type. What I want to happen in the code is everytime the procedure 'increment' is hit the variable would increase. This is that test code:
PACKAGE test IS
testNum number := 0;
PROCEDURE increment;
END test;
PACKAGE BODY test IS
PROCEDURE increment IS
BEGIN
testNum := testNum + 1;
htp.prn('Current value: ' || testNum);
END;
END test;
After hitting that procedure a few times the output was 1 every time, so it would seem what I had believed to be 'global' variables are actually local to the request, reset every time, and that is not going to work for me. I need some persistance.
Someone mentioned something to me about storing variables in a session object, but I don't know anything about that (yet)...
Any help would be appreciated.

Hey,
I am not sure where exactly to ask about this, so if I posted in the wrong forum forgive me.
My problem is this: I am writing an application which interacts with a remote server using the functions in the utl_tcp package. This works with no problems in testing, but after I put a web interface on it I discovered that what I thought were global variables (defined in the package spec) are being reset every time a new call is made to the server. The interface works by repeatedly calling a certian function in my package which checks the tcp stream (what I want to be my 'global' variable) for any new information coming downstream. When it does this though the stream is gone, the variable has been reset with every request.
I tested this with a more simple variable too to make sure it just wasnt some quirk of the tcp connection type. What I want to happen in the code is everytime the procedure 'increment' is hit the variable would increase. This is that test code:
PACKAGE test IS
testNum number := 0;
PROCEDURE increment;
END test;
PACKAGE BODY test IS
PROCEDURE increment IS
BEGIN
testNum := testNum + 1;
htp.prn('Current value: ' || testNum);
END;
END test;
After hitting that procedure a few times the output was 1 every time, so it would seem what I had believed to be 'global' variables are actually local to the request, reset every time, and that is not going to work for me. I need some persistance.
Someone mentioned something to me about storing variables in a session object, but I don't know anything about that (yet)...
Any help would be appreciated.

Define variable in package access from trigger

i want to accessing a variable that is defined in the package from trigger..how i must define this variable in the package ?

To add one more point to Justin,
Package variables are global variables. If you want to make it local to single call use PRAGMA SERIALLY_REUSABLE.
create or replace package pkg_variable
as
g_var number := 1;
end;
create or replace package pkg_variable_local
IS
PRAGMA SERIALLY_REUSABLE;
g_var number := 1;
end;
/ Testing Above Two pakcages
set serveroutput on
begin
dbms_output.put_line ( 'Test 1 :');
dbms_output.put_line ( 'Global Var: ' || pkg_variable.g_var);
dbms_output.put_line ( 'Local Var: ' || pkg_variable_local.g_var);
end;
Result:
Test 1:
Global Var : 1
Local Var : 1
begin
pkg_variable_local.g_var := 10;
dbms_output.put_line ( 'Test 2 :');
dbms_output.put_line ( 'Global Var: ' || pkg_variable.g_var);
dbms_output.put_line ( 'Local Var: ' || pkg_variable_local.g_var);
end;
Result:
Test 2:
Global Var : 10
Local Var : 10
begin
dbms_output.put_line ( 'Test 3 :');
dbms_output.put_line ( 'Global Var: ' || pkg_variable.g_var);
dbms_output.put_line ( 'Local Var: ' || pkg_variable_local.g_var);
end;
Result:
Test 3:
Global Var : 10
Local Var : 1
But remember, Serially reusable packages cannot be accessed from database triggers.

Passing Script variable to Package variable, ultimately used as fileName

Following an excellent post by Geplaatst door Joost, I put together a script which SHOULD populate a package variable, then use that variable as a file name.
The Script code is as follows:
public class ScriptMain : UserComponent
string iScriptVar;
public override void PreExecute()
base.PreExecute();
public override void PostExecute()
base.PostExecute();
Variables.ExtractName = iScriptVar.ToString();
public override void Input0_ProcessInputRow(Input0Buffer Row)
if (!Row.CUSIP_IsNull)
iScriptVar = Row.CUSIP.ToString();
A Windows message box (put in as debug, but removed for brevity here) shows the correct value is being set to iScriptVar at all points it was inserted.
The "ExtractName" variable is checked as a ReadWriteVariables for the Script properties.
But, the "ExtractName" package variable is not being passed to the Expressions for the FlatFile Connection properties, which is set to: @[User::ExtractName].
Where have I gone wrong?

Why not to provide the link to the post already?
iScriptVar
is a local to script variable this explains why it did not you need the full wiring
e.g.
Dts.Variables["User::iScriptVar"].Value = iScriptVar
Arthur
MyBlog
Twitter

How to declare bind variable in package

hi,
i have created one package with insert and returning the value in procedure using bind variable.
-- spec part.
SET SERVEROUTPUT ON
VARIABLE id NUMBER
CREATE OR REPLACE PACKAGE pack_sale AS
PROCEDURE pro_insert_SOHeader (
SO_HEADER_ID NUMBER,
SO_NO VARCHAR2,
SO_TYPE VARCHAR2,
SO_APPROVED_FLAG VARCHAR2,
SO_DATE DATE,
CUST_HEADER_ID NUMBER);
END pack_sale;
-- body part
CREATE OR REPLACE PACKAGE BODY pack_sale AS
PROCEDURE pro_insert_SOHeader (
SO_HEADER_ID NUMBER,
SO_NO VARCHAR2,
SO_TYPE VARCHAR2,
SO_APPROVED_FLAG VARCHAR2,
SO_DATE DATE,
CUST_HEADER_ID NUMBER) IS
BEGIN
INSERT INTO SO_Header VALUES (SEQ_SOHEADER.NEXTVAL,SO_NO,SO_TYPE,SO_APPROVED_FLAG,SO_DATE,CUST_HEADER_ID)
RETURNING SEQ_SOHEADER.CURRVAL INTO :id;
COMMIT;
END pro_insert_SOHeader;
END pack_sale;
I have run this package in sql*plus,it will return the warning message like
PLS-00049: bad bind variable 'ID'.
i do not know how to rectify this error
and how to execute this procedure in sql*plus.
please help me...

hi,
when i was running the body script the error is displayed in
sql*plus like
SQL> @"D:\Viji Share\ex_body"
SP2-0042: unknown command "ï»¿" - rest of line ignored.
15 /
Warning: Package Body created with compilation errors.
SQL> show error
Errors for PACKAGE BODY PACK_SALE:
LINE/COL ERROR
11/30 PLS-00049: bad bind variable 'ID'

Access variables in Package.

Hi I have a apackage called share.server , in which I have defined
Hashtable hash;
i have another file in share package as Impl, here i want to call the "hash"
how can i access the same "hash" in Impl.java from FilServer which is in share.server package.
Please respond urgent, assignment is due soon.
Thanks for any response.

what?!
variables belong to classes, not packages. If you want to access variables between classes you need to define some kind of public interface for them (getters and setters... ring any bells?). This is basic basic OOP, and is called encapsulation. First thing you need to do is get a basic 'OOP with java' type book and read it fully. We can't help you if you can't help yourself/

Reuse Variable In Packages

Similar Messages

Maybe you are looking for