relative to the parameter in a stored procedure returns

Similar Questions

• Ignoring the empty parameter in a stored procedure

  I am writing a SP that ignores an empty parameter in a where clause like this clause.
  Create procedure @myvar AS int blah
  Select * from companies
  where 1 = 1
  If @myvar is <>"
  and id = @myvar
  
  This seems to be a simple task, but it does not work. Thanks in advance
  

  Use the ISNULL trick, but at the beginning of your stored procedure, add the line:
  IF LTRIM (@myvar) = "SET @myvar = NULL

• How to pass an array as a parameter to a stored procedure

  Hi all
  I want to pass the name of a table as a parameter in a stored procedure, which will be used for cursors, etc..
  But when I pass the parameter and I compile the S.P. he gives me error (error: table exist not...)
  
  Any help?
  
  Thanks in advance, Marco

  Cannot open a cursor explicit when it comes to the dynamic table names or parameters. This is because the explicit and implicit cursors seek real table names since they are static.
  Here your name of the table is dynamic, so u need to use dynamic that is ref cursor to and not static cursor.

  I made the correction in the code below. Run it and check the result!

  CREATE OR REPLACE PROCEDURE "P_1" ( TAB1 VARCHAR2)
  AS
  field1 CHAR(5);
  field2 CHAR(5);
  
  c1 sys_refcursor;
  
  begin
  
  l_str := 'select a,b,c from '||tab1||' INNER JOIN tab2 ON a = .......';
  open c1 from l_str;
  
  /*OPEN C1;
  CURSOR C1
  IS
  SELECT a, b , c
  FROM TAB1
  INNER JOIN
  tab2
  ON a = .......
  OPEN C1;*/
  
  LOOP
  FETCH C1
  INTO ..... 
  
  EXIT WHEN C1%NOTFOUND;
  .....
  END;
  END LOOP;
  
  CLOSE C1;
  
  EXCEPTION
  WHEN OTHERS
  .....
  END;
  

• query as a parameter in a stored procedure

  Hi all
  
  I'm working on Oracle 10 g.
  Can I send a query as a parameter in a stored procedure?
  
  Thanks in advance

  You can, of course. Should you? At most, rarely.

  You can use SQL statements (EXECUTE IMMEDIATE or DBMS_SQL) Dynamics to run an arbitrary string as a SQL statement. There are serious security problems if someone how to pass a statement dangerous SQL in numbers (update the USERS table, remove all data from an important painting, etc.). If you pass in a SELECT statement and you do not know the structure of the result set, you must use DBMS_SQL rather than the simple EXECUTE IMMEDIATE and a more complicated API to describe the result set.

  Justin

• How to do a select on the results of a stored procedure?

  Hello

  I am new to Oracle. I work with SQL Developer.

  I'm doing a simple select on the results of a stored procedure call. I don't know how to do it. Here's what I have so far:

  declare
  type ref_cursor is ref cursor;
  results ref_cursor;
  Start
  MyStoredProcedure (123 results);
  Select * from results;
  end;
  /

  but he said to me:

  Error from the 1 in the command line:
  declare
  type ref_cursor is ref cursor;
  results ref_cursor;
  Start
  GET_TAX_TYPE_BY_TAX_ENTITY_KEY (60670100000000, results);
  Select * from results;
  end;
  Error report:
  ORA-06550: line 6, column 15:
  PL/SQL: ORA-00942: table or view does not exist
  ORA-06550: line 6, column 1:
  PL/SQL: SQL statement ignored
  06550 00000 - "line %s, column % s:\n%s".
  * Cause: Usually a PL/SQL compilation error.
  * Action:

  Obviously, select * results; is not the right way to do it. But what is?

  Thanks for any advice forthcoming.

  If a SQL cursor is built by a reporting system, a Java application, a c# program, or a PL/SQL call - the database doesn't care, because he doesn't know the difference. A Select SQL cursor created in PL/SQL through the ref cursor interface, won't be faster than the same SQL select in Eclipse. If the SQL source code is the same, the same cursor SQL program will be used by both.

  What give you BIRT is the flexibility of the use of code Server (PL/SQL) to create the slider - this code doing business and technical decisions on how to design side than SQL, Select. Which is a good thing because it summarized the data model and the complexity BIRT server technique.

  So my choice would be to use the procedural interface and return to the reporting system for the rendering of the ref Cursor.

  The question of a slider running via the slider (selection of a cursor), is questionable. Yes, there are a set of specifications that allows to do this kind of thing. But it must be very firmly justified and careful design because it really is an exception. I personally (blame my DBA) would need a justification because it is much more of an exception. I have never seen it put in place in production in more than a decade of DBA'ing, despite the developers try to use such a hack - as it has always been much more powerful and the deployment of alternatives.

  The concept for robust and efficient code for Oracle is: Maximise SQL. Minimize the PL/SQL (or Java / c# / etc.).

  That means when it comes to database power, write an SQL program to do. Stop thinking of SQL as a language of data recovery a single simplistic statement. Think of it as a programming language. Extremely complex problems can be resolved with a single SQL, which requires easy code 100 + lines of PL/SQL, Java, or c#. Write SQL programs. Not SQL one-liners for a grinding program PL/SQL or Java data.

  Why then PL/SQL? It is the best language to manage the creation of SQL, dealing with the process flow, conditional processing, and so on of exception handling. It is less than SQL (such as Java and c#) in the treatment of the data.

• Process the Message on a stored procedure

  Hi all
  
  How do I call and diplay APEX the message of a stored procedure?
  
  Example of form on stored procedre.
  
  Thank you

  Hello

  What do you mean by 'the message '? If you are referring to the 'success Message', then you can use the variable apex.

  APEX_APPLICATION.G_PRINT_SUCCESS_MESSAGE := 'This is success message for page process';
  

  Kind regards
  Hari

• Passing the params in mysql stored procedure

  Makes no mistake, but when I hard code the values in the stored procedure, I get results, I leave as params - if not.
  Something must be a miss with how I said, but I can't understand that:
  
  Can anyone help? details below:
  
  : the stored procedure:
  
  Create procedure keyword_getBySource (in sourceRecordName varchar (20), in sourceRecordId varchar (50))
  Start
  Select
  tblkeyword.*
  Of
  tblkeyword,
  tblrecordlink
  where
  tblrecordlink.sourceRecordName = @sourceRecordName
  and
  tblrecordlink.sourceRecordId = @sourceRecordId
  and
  tblrecordlink.linkRecordName = 'keyword'
  and
  tblkeyword.keywordId = tblrecordlink.linkRecordId
  ;
  end
  
  : cfm:
  
  "< cfstoredproc procedure ="keyword_getBySource"datasource =" "username =" "password =" ">
  < cfprocparam type = 'in' cfsqltype = "CF_SQL_VARCHAR" dbvarname = "sourceRecordName" value = "Log" / >
  < cfprocparam type = 'in' cfsqltype = "CF_SQL_VARCHAR" dbvarname = "sourceRecordId" value = "0d8a6d3e-cf1e - 19(d) 5-2b9fc8ee1de01ad0" / >
  < name cfprocresult = resultset "getBySource" = "1" / >
  < / cfstoredproc >

  @... seems mysql does not use these to designate the params in a stored procedure

  Take them out - it works.

• issues related to the parameter in the procedure

  Hi all

  I have a procedure which the code is given below:

  create or replace PROCEDURE seods01.get_cert_tx_lot_tmp (acct_alt_id_in in VARCHAR2

  , acct_alt_id_cntx_cde_in IN VARCHAR2 default 'COLA account number.

  ,                                              ibd_id_in               IN  INTEGER

  qry_rslt_out to sys_refcursor)

  IS

  BEGIN

  OPEN FOR Qry_rslt_out

  SELECT L.tx_lot_seq_nbr

  L.hld_prd_dte

  L.orig_purc_dte

  L.tx_lot_amt

  L.updt_tx_lot_amt

  L.tran_desc_txt

  OF v_acct_alt_id A

  v_cd_tx_lot L

  WHERE A.acct_alt_id = acct_alt_id_in

  AND A.acct_alt_id_cntx_cde = acct_alt_id_cntx_cde_in

  AND A.ibd_id = ibd_id_in

  AND L.eods_acct_id = A.eods_acct_id;

  EXCEPTION

  WHILE OTHERS THEN

  dbms_output.put_line(SQLCODE||) SQLERRM);

  END get_cert_tx_lot_tmp;

  now when I run the SP in the following way it works fine:

  VAR C1 REFCURSOR
  EXECUTE SEODS01.get_cert_tx_lot_tmp ('004000000000000093108026740', 'Number of COLA account', '1',: C1);

  PRINT C1

  When I try to ignore this value by default setting, then it is throwing ' wrong number or types of arguments "error

  VAR C1 REFCURSOR
  EXECUTE SEODS01.get_cert_tx_lot_tmp ('004000000000000093108026740 ', ' 1',: C1);

  PRINT C1

  and when I tried to put this as null or "then it gives me no results. only way through which I can produce results of this procedure without giving the default parameter is the name of the column with the value of the parameter as follows:

  VAR C1 REFCURSOR
  RUN SEODS01.get_cert_tx_lot_tmp (acct_alt_id_in = > '004000000000000093108026740', ibd_id_in = > '1', qry_rslt_out = >: C1);

  PRINT C1

  but the condition is that we do not want our consumers to put names of columns when they do not pass the default value setting, I hope that there should be a way to do it. Could someone help me please on this issue.

  Hello

  If you want to use positional notation, then you can only omit parameters by default when they are at the end of the parameter list. In your case, this would mean

  (acct_alt_id_in in VARCHAR2

  ibd_id_in in FULL

  qry_rslt_out ON sys_refcursor

  acct_alt_id_cntx_cde_in IN VARCHAR2 default 'COLA account number')

  Or you can put the procedure in a package and overload

  PROCEDURE seods01.get_cert_tx_lot_tmp

  (acct_alt_id_in in VARCHAR2

  acct_alt_id_cntx_cde_in IN VARCHAR2

  ibd_id_in in FULL

  qry_rslt_out to sys_refcursor)

  PROCEDURE seods01.get_cert_tx_lot_tmp

  (acct_alt_id_in in VARCHAR2

  ibd_id_in in FULL

  qry_rslt_out to sys_refcursor)

  In the procedure without the acct_alt_id_cntx_cde_in parameter, you can call the other version and provide the default value.

  Concerning

  Marcus

• Is it possible to move an Oracle null input parameter to a stored procedure

  I have a stored procedure taking 3 inputs and 1 output of donne. I use the Oracle parameter to add all the input parameters 3 as follows:
  
  OracleParameter = cmd inobj. Parameters.Add ("wid", OracleDbType.Int32, 50);
  inobj. Direction = ParameterDirection.Input;
  inobj. Value = _employeeID;
  
  and the addition of the setting of output as follows:
  
  OracleParameter outobj is _cmd. Parameters.Add ("w_first", OracleDbType.Varchar2, 50);
  outobj. Direction = ParameterDirection.Output;
  
  On the side of the user interface, the user has the option of providing 1 entry or all inputs or any 2 based on his interest. Stored proc looks like this:
  SP (inp1 in parameter, inp2 in inp3 in parameter, parameter, out parameter output1)
  
  If I just get 1 or 2 entries of the user, it is very good query output data using the same stored procedure or do I create stored procedures for each scenario (combination of different entries)?
  
  I get an error in pl/sql which indicates the invalid number of arguments?

  Maybe I can be more clear with c# code. :)

  void SaveSomethingInOracle(int param1, string param2 = null, decimal? param3 = null)
  {
  // Set up your oracle connection and query here
  OracleParameter inobj = _cmd.Parameters.Add("w_id", OracleDbType.Int32,50);
  inobj.Direction = ParameterDirection.Input;
  inobj.Value = param1;
  
  OracleParameter inobj2 = _cmd.Parameters.Add("name", OracleDbType.Varchar2,50);
  inobj2.Direction = ParameterDirection.Input;
  inobj2.Value = param2;
  
  OracleParameter inobj3 = _cmd.Parameters.Add("quantity", OracleDbType.Decimal,50);
  inobj3.Direction = ParameterDirection.Input;
  if (param3.HasValue)
  {
  inobj3.Value = param3.Value;
  }
  else
  {
  inobj3.Value = null;
  }
  }
  

  This c# method takes 3 parameters. The first is necessary, the other two are optional. If you do not set them, they take the value default null and passing it to the database. If you want to set the first and third only, you can still pass null as the other. If you have this piece of code to call the stored procedure any combination of parameters that you use, and the proc will get values or NULL values properly.

  Hope he says. You need only one together code to do what you want to do. :)

  Published by: Tridus on December 19, 2012 12:10

• How to take the user through a stored procedure input...

  Salvation has posted this earlier, but I'm sorry I think kept an incorrect object name...
  Here's my problem...
  
  First user will pass a parameter to insert or remove. Aftert that depeding on the insert or delete, we should as a user to spend still more values.
  I did the code below, but he was throwing an error.
  
  I'm not sure we can use '&' to enter the stored values Procedure.Bcause indidvidual States working with '& '.
  but not in the stored procedure.
  

  Individual Statement:
  insert into emp
        values      ( & emp_id  ,&emp_name ,&Manager_id,sysdate );

  --- Procedure :::::
  create or replace procedure emp_id ( p_test_input in varchar2 )
  as
    emp_id number;
  emp_name varchar2(20);
  manager_id
  begin
     if ( upper ( p_test_input ) = 'I' )
     then
        insert into emp
        values      ( & emp_id  ,&emp_name ,&Manager_id,sysdate );
     elsif ( upper ( p_test_input ) = 'D' )
     then
        delete from emp
        where       emp_id  = &emp_id;
     else
        dbms_output.put_line
           ( 'Please input ''A'' for ADD or ''D'' Delete  EMPLOYEE'
           );
     end if;
  end;

  Create a package and it contains an overloaded procedure, something like...

  CREATE OR REPLACE PACKAGE BODY
    emp_mgr
  AS
  PROCEDURE emp_update( in_emp_id   NUMBER,
                        in_emp_name VARCHAR2,
                             in_mgr_id   NUMBER )
  IS
  BEGIN
    INSERT
      INTO emp (emp_id, emp_name, manager_id )
    VALUES in_emp_id, in_emp_name, in_mgr_id;
  END emp_update;
  
  PROCEDURE emp_update (in_emp_id NUMBER )
  IS
  BEGIN
    DELETE
      FROM emp
     WHERE emp_id = in_emp_id;
  END emp_update;
  END emp_mgr;
  

  Now, if you call it with only the emp_id, it will remove. If you call it with emp_Id, emp_name and mgr_id, it will update.

• The execution of a stored procedure from inside the cursor for loop?

  I posted this in the SQL Developer forum, but I tried in SQLPlus and get the same error, so I think it's an encoding issue.
  I have a piece of code that I'm trying to write that will only be executed once. The goal: we have three tables relating to the pieces of information. Each table has a column that stores the number of site that belongs to the part. We want to copy the parts of a site to about 130 sites which don't have any info on parts. The number of site is stored in another table. So I created three stored procedures, one for each of the three tables that we, who take 2 inputs: a source and destination site. Procedure names are: ptfile_copy_fac, ptxref_copy_fac and ptvndrs_copy_fac.
  
  The problem I have is that I can run the procedures in a separate worksheet in SQL Developer, but when they are integrated in this cursor for loop, I get the following message from SQL Developer:
  
  ORA-06550: line 23, column 11:
  PLS-00103: encountered the symbol "PTFILE_COPY_FAC" during the expected in the following way:
  := . (@ %; immediate)
  The symbol ': = ' was replaced by 'PTFILE_COPY_FAC' continue.
  
  He repeated this for each of the three methods. I have attached the code I am trying to run below. He expects an assignment operator, but I have no idea why.
  
  If there is a better way to do this, by all means let me know. I'm a SQL Server guy, I'm not sure how to do what I do using PL\SQL.
  
  / * Declares the variables source_fac and dest_fac.
  The source_fac is the installation that we copy parts.
  The dest_fac is the installation we copy parts to.* /
  
  DECLARE
  source_fac facility.facility_num%type;
  INSTALLATION OF DEST_FAC. TYPE % FACILITY_NUM;
  
  / * Declare cursor to use loop for.
  Slider load number installation and the status of the installation.
  Is not installation of 1 or 2, since these will be
  the main source of facilities.*.
  
  CURSOR fac_cursor
  IS
  SELECT
  facility_num,
  div_state
  Of
  installation
  WHERE
  facility_num NOT IN (1,2);
  BEGIN
  FOR fac_row IN fac_cursor
  LOOP
  
  / * Test for the State of the installation. If a Canadian State, the source_fac value 2.
  Otherwise, the value source_fac 1.* installation.
  
  IF fac_row.div_state IN ("AB", "BC", "Mo", "NB", "NL", "NT", "NS", "NAKED", "WE", "PE",
  "QC", "SK", "YT")
  THEN
  source_fac: = 2;
  ON THE OTHER
  source_fac: = 1;
  END IF;
  
  / * Sets the installation of destination to the facility_num from the cursor * /.
  
  DEST_FAC: = FAC_ROW. FACILITY_NUM;
  
  / * Execute the three procedures, past of the source and dest AEC variable * /.
  
  run ptfile_copy_fac (source_fac, dest_fac);
  run ptxref_copy_fac (source_fac, dest_fac);
  run ptvndrs_copy_fac (source_fac, dest_fac);
  
  END LOOP;
  
  END;
  
  Published by: SunDevilKid on March 3, 2010 15:31
  Update the comments you make more sense of the code.

  EXECUTE is a SQLPlus command, change your code to

  dest_fac := fac_row.facility_num;
  ptfile_copy_fac(source_fac, dest_fac);
  ptxref_copy_fac(source_fac, dest_fac);
  ptvndrs_copy_fac(source_fac, dest_fac);
  END LOOP;
  

  Max
  http://oracleitalia.WordPress.com

• Error when the stored procedure returns a cursor in c pro

  
  Hello
  
  I tried to make things work, explained to the
  [2537153 m]
  
  He runs a stored procedure from pro c which returns a cursor.
  But when I compllie to c pro I get following error. My name of the procedure's TEST.
  If I change the output to an int value parameter. It compiles okay.
  
  
  
  PLS-S-00306, wrong number or types of arguments in the call to 'TEST '.
  Error on line 34, column 5 in file E:\C\Test\tt.pc
  TEST(:test_cursor);
  +.... 1 +.
  PLS-S-00000, ignored statement
  A semantic error on line 33, column 1, folder E:\C\Test\tt.pc:
  BEGIN
  + 1 +
  PCC-S-02346, PL/SQL found semantic errors
  
  Can make a point about what could be the error?
  I work from oracle 8i client. that connects to oracle 9.0.1.
  Operating system is win 2000 sp4
  
  

  Oh yes - differs from the code snippet I posted your with the declaration of the host cursor variable. A difference in the case. Is how important it?

  ( it's been almost 10 years since I've coded last in Pro * C, so be careful with these questions! ) ;-) )

• Version of 5.0.2.00.07(online à APEX) - error in the execution of a stored procedure through anonymous block

  DECLARE

  the stored procedure varchar2 (25);

  BEGIN

  -DBMS_OUTPUT. Put_line ("enter the name of the procedure :'||: procname");

  the stored procedure: =: procname;

  DBMS_OUTPUT. Put_line (' procedure :'|| stored procedure);

  stored procedure.

  END;

  : procname is a variable binding in the apex to switch the running value.

  

  This is the error I get

  ORA-06550: line 7, column 2:

  PLS-00221: "STORED procedure" is not a procedure or is not defined

  ORA-06550: line 7, column 2:

  PL/SQL: Statement ignored

  5the stored procedure: =: procname;

  6 DBMS_OUTPUT. Put_line (' procedure :'|| stored procedure);

  7. the stored procedure.

  8 END;

  SmtWtL wrote:

  DECLARE

  the stored procedure varchar2 (25);

  BEGIN

  -DBMS_OUTPUT. Put_line ("enter the name of the procedure :'||: procname");

  the stored procedure: =: procname;

  DBMS_OUTPUT. Put_line (' procedure :'|| stored procedure);

  stored procedure.

  END;

  : procname is a variable binding in the apex to switch the running value.

  This is the error I get

  ORA-06550: line 7, column 2:

  PLS-00221: "STORED procedure" is not a procedure or is not defined

  ORA-06550: line 7, column 2:

  PL/SQL: Statement ignored

  5. the stored procedure: =: procname;

  6 DBMS_OUTPUT. Put_line (' procedure :'|| stored procedure);

  7. the stored procedure.

  8 END;

  What you're trying to achieve?

  Bind variables cannot be used for the dynamic execution of stored programs. Dynamic SQL using lexical rather than bind substitution must be used to run when the program name is not known until execution of the programs.

  declare
    sproc varchar2(25);
  begin
    sproc := :procname;
    dbms_output.put_line('procedure:'||sproc);
    execute immediate 'begin ' || sproc || '; end;'; -- DO NOT DO THIS!
  end;
  

  It is a fundamental design flaw and a security disaster. It's stops essential compilation controls is performed and is open to attack by SQL injection and other security vulnerabilities. There is no good reason to do this.

• Could not import the Pentecost Entity Framework stored procedures

  Hi, I have a problem with Entity Framework 5 and stored procedures. I can add stored procedures to mi with "Update Wizard" solution, but them does not show in the Model Explorer and I can't use my code. I have ODAC 12 c Release 2 installed in my pc.

  There is a bug in the database Oracle 12 c that occurs only with a snap-in database. It is fixed in the next group of patches from database. (bug #17448545)

  There are three workarounds in the meantime:

  (1) to re-create the database without the shared option (no plug-in database)

  (2) install your schema in the database of the container instead of a snap-in database. You will need a user name as C ##HR to do. It is not advisable on a production database.

  Add 3) the section of manually in in the edmx file. Note that this is deleted when you "Generate database from model" or "Update model from database".

  for example:

  ...

  ParameterTypeSemantics = "AllowImplicitConversion" scheme = "SCOTT" >

• ORA-06565: cannot run the ROLE VALUE from stored procedures

  Hello!
  
  I'm trying to call a procedure from a function. Among the statements in the procedure stored is of dbms_session.set_role ('HAVE');
  
  I get the error "Cannot run a DEFINED ROLE less stored proceduers". I joined the call in an anonymous block above, but the error still exists.
  
  Any idea will really help me.
  
  Thank you

  >
  I'm trying to call a procedure from a function. Among the statements in the procedure stored is of dbms_session.set_role ('HAVE');

  I get the error "Cannot run a DEFINED ROLE less stored proceduers". I joined the call in an anonymous block above, but the error still exists.

  Any idea will really help me.
  >
  This will work only if the procedure is defined for the APPELLANT's rights.

  Roles are disabled in named PL/SQL blocks unless you use of the APPELLANT's rights by setting the code with AUTHID CURRENT_USER.

  The Oracle documentation provides a very clear explanation - based restriction is for the NAMED PL/SQL blocks rights DEFINER of this use (the default):
  >
  Roles used in the appointed with rights to define blocks

  All roles are disabled in any PL/SQL block named (stored procedure, function, or trigger) that runs with the rights of the author. Roles are not used to privilege control, and you cannot define roles within the procedure of a DEFINER rights.
  >
  The database Security Guide has the information in the section "operation of the roles in PL/SQL blocks (which, of course, wouldln was necessary if they didn't work.).
  http://docs.Oracle.com/CD/B28359_01/network.111/B28531/authorization.htm#i1007304
  >
  The use of roles in a PL/SQL block depends on if it is an anonymous block, or a block named (stored procedure, function, or trigger), and if it runs with the rights of the author or the rights of the applicant.

  Roles used in the appointed with rights to define blocks
  All roles are disabled in any PL/SQL block named (stored procedure, function, or trigger) that runs with the rights of the author. Roles are not used to privilege control, and you cannot define roles within the procedure of a DEFINER rights.

  The SESSION_ROLES view shows all roles that are currently enabled. If a named PL/SQL block that runs with DEFINER SESSION_ROLES rights issues, the query returns no rows.

  See also:

  Oracle database reference

  Roles used in blocks named with the rights of the plaintiff and anonymous PL/SQL
  Named PL/SQL blocks that run with the rights of the applicant and the anonymous PL/SQL blocks are executed at the end of the privileges granted through active roles. Current roles are used for verification within rights Summoner of privilege the PL/SQL block. You can use dynamic SQL statements to define a role in the session.