Procedure declarations section

Similar Questions

• Type mismatch Runtime in the stored procedure declaration

  Hello
  
  I met the following on Oracle 10 g. I created a stored procedure:
  
  create or replace procedure ttt's
  c number (9.2);
  Start
  c: = "Hello World";
  end;
  
  Execution of this product the ORA-06502: PL/SQL: digital or value error: character of number conversion error message, that I would have expected at the time of the declaration.
  
  Is this normal or is it a bug? Thanks in advance.
  
  Tamas

  Well as long as everyone will jump in and make the learning experience I'll give you the answer explicitly.

  What you wrote is:

  c number(9,2);
  begin
  c:='Hello world';
  

  ' 1. ' hello world ' is NOT a number
  ' 2 ' hello world ' is 11 bytes, which means that it cannot be drunk in nothing less than a VARCHAR2 or CHAR (11) (11)

  In addition: have you turn on PL/SQL warnings if you would see the following:
  1/2 PLW-06010: keyword 'C' used as a defined name
  4/2 PLW-07206: analysis suggests that the assignment to 'C' may be useless (which is)

  To enable warnings:
  http://www.morganslibrary.org/reference/plsql_warnings.html

• infinite loop in stored procedure

  I am trying to create an infinite loop to test an error condition. I do this in the stored procedure. I have not created a stored procedure before. I get errors when I am writing the script. Can you please tell me what I'm doing wrong with this script?
  
  
  CREATE OR REPLACE PROCEDURE blah.test_timeout
  
  IS
  
  number of deadline_days: = 1;
  grace_period number: = 0;
  
  BEGIN
  -get day of the date limit
  
  While deadline_days < 4000
  LOOP
  grace_period: = grace_period + 1;
  dbms_output.put_line (' Hello mum ');
  END LOOP;
  
  
  RAISE_APPLICATION_ERROR (-20071, "what_error error:' | ') SQLERRM (sqlcode));
  
  END;
  /
  
  
  
  
  Thank you!

  First tell me that this error message happens when you run this script.

  You can use only * $, _, #* when you give the name of procedure, function, package, variable, trigger. Here, you use * (.) * in your name of the procedure so it will give you error.

  and you first declare exception in your procedure declaration section. and raise it in Exception of procedure section.
  In this you have to give the condition for which exception condition must raise.

  This is a sample I'll send to your reefrence:-_

  CREATE OR REPLACE PROCEDURE raise_demo (inval NUMBER) IS
  evenno EXCEPTION;
  oddno EXCEPTION;
  BEGIN
  MOD IF (inval, 2) = 1 THEN
  RAISE oddno;
  ON THE OTHER
  RAISE evenno;
  END IF;
  EXCEPTION
  WHEN evenno CAN
  dbms_output.put_line (to_char (Inval) |) "is even");
  WHEN oddno THEN
  dbms_output.put_line (to_char (Inval) |) "is weird");
  END raise_demo;

• How a Variable are assigned just by being declared.

  Hello
  
  I'm new here. We use the Oracle 11.2. I have a question of PL/SQL.
  
  There is code below that takes variables in the DECLARE section and declares the variable v_sum_prcs_end that see you it used in the following select statement.
  
  Is there WAY TO this variable might have gotten one assignment by default other than NULL if not initialized? This variable is not mentioned anywhere before in this procedure. It is a procedure doesn't not part of a package.
  

            LOOP
                 <<Execute_Rule>>
                 DECLARE
                 v_sum_prcs_start DATE := TO_DATE ('19000101', 'YYYYMMDD');
                 v_sum_prcs_end DATE;
  
                 CURSOR PRD_DIM IS
                      SELECT *
                      FROM (
                           SELECT *
                           FROM (
                                  SELECT *
                                  FROM PRD_DIM_SRC
                                  WHERE wk_ending_dt BETWEEN v_sum_prcs_end - ((v_row_PRD_DIM_RUL.span_num_wks * 7) - 7 ) AND v_sum_prcs_end
                                  ORDER BY wk_ending_dt)
                           WHERE ROWNUM <= v_row_PRD_DIM_RUL.max_num_wks)
                      WHERE wk_ending_dt > v_sum_prcs_start
                      ORDER BY wk_ending_dt ASC;

  It is in a loop, as you can see, and he get initialized after this. Of course when the loop returns once again, it will have a value, but at the first pass, it is just ZERO? and if so the query returns all rows?
  
  Thank you

  Hello

  963236 wrote:
  Hello

  I'm new here. We use the Oracle 11.2. I have a question of PL/SQL.

  Whenever you have any questions, please post a complete script that people can use to recreate the problem and test their ideas. Include a full procedure or ananoymous PL/SQL block, and, if it is a procedure or a function, the code that calls it. Include CREATE TABLE and INSERT all necessary tables for instructions. See the FAQ forum<>
  Simplify the code you post as much as possible. In this case, the problem seems to depend on if or how a DATE variable to get the value before using a cursor. You can probably show only with a slider to 5 lines, without any of subqueries, using the column hiredate in scott.emp, which is widely available, so you don't have to post CREATE TABLE and INSERT statements for her.

  There is code below that takes variables in the DECLARE section and declares the variable v_sum_prcs_end that see you it used in the following select statement.

  Is there WAY TO this variable might have gotten one assignment by default other than NULL if not initialized? This variable is not mentioned anywhere before in this procedure. It is a procedure doesn't not part of a package.

  What you are showing is the DECLARE section. You're not showing how the cursor is open. If v_sum_prcs_end has a value when the cursor is actually used, then you must be giving the value before opening the cursor. (Add a few calls to dbms_output.put_line to display its values at various points in the code.) If there is nothing mysterious past, it will happen in the BEGIN section, which has no validation, and not DECLARE section.

  The only ways I know to which gives a value to a variable in a PL/SQL are:
  (1) using the variable on the left side of the: operator, =
  (2) use it in the clause of SELECT INTO... IN
  (3) if it is an argument, which gives a default value (which is clearly not the case in this issue.)
  (4) use it as an OUT or IN ARGUMENT to another procedure. (This is not really a separate way to set the value, because the procudeure must assign the new value using first 3 methods, or call another procedure that does.)
  Again, if the variable has a value when you open the slider, then I think you're one of the foregoing, before opening the cursor.

  Moreover, why you open a cursor inside a loop? There is almost always a more efficient way to get rid of the loop and do everything in the cursor. Like a lot of work as long as you can in the SQL statement and only use PL/SQL constructs, such as loops, when there is no other choice.

• declare

  Can we use declare section indoor environment.

  And this from the PL/SQL doc
  http://docs.Oracle.com/CD/B28359_01/AppDev.111/b28370/fundamentals.htm#CIHEAFBJ
  >
  DECLARE

  Signals the start of the declarative part of a PL/SQL block, which contains local declarations. Items reported locally exist only in the current block and all of its sub-blocks and are not visible for locking them blocks. The declarative part of a PL/SQL block is optional. It implicitly ends with the BEGIN keyword, which introduced the executable part of the block. For more information, see statements.
  . . .
  Scope and visibility of identifiers in PL/SQL
  References to an identifier are resolved according to its scope and visibility. The scope of a distinctive sign is the area of a unit of PL/SQL, where you can refer to the identifier. The visibility of an identifier is the region of a unit of PL/SQL, you can reference the identifier without qualifying.

  An identifier declared in a PL/SQL unit is local to that unit and comprehensive of its subunits. If a subunit redeclares a global identifier, then inside the Sub-unit, the two identifiers are in scope, but only the local identifier is visible. To reference the global identifier, the Sub-unit must qualify.

  You cannot declare an identifier twice in the same unit of PL/SQL, but you can declare the same identifier in two different units. The two elements represented by the identifier are distinct, and a modification does not affect the other.

  A unit of PL/SQL cannot reference identifiers declared in other units at the same level, because the identifiers are global or local to the block.

  Example 2-24 shows the reach and visibility of several identifiers the and global. The global identifier is redeclared a in the first subblock.

  Example 2-24 scope and visibility of identifiers

  SQL > DECLARE
  2 a TANK; -The scope of a (CHAR) starts
  3 b REAL. -Scope of b starts
  4 BEGIN
  5. visible: a (CHAR), b
  6
  7 REPORT
  8A WHOLE; -Start range to a number (INTEGER)
  9 C REAL; -Scope of c starts
  BEGIN 10
  11. visible: a number (INTEGER), b, c
  12 NULL;
  13 END; -The bodies of a number (INTEGER) and the end c
  14
  15 REPORT
  16 d REAL; -D scope starts
  BEGIN 17
  18. visible: a (CHAR), b, d
  19 NULL;
  20 END; -Scope of the ends d
  21
  22. visible: a (CHAR), b
  23 END; -A (CHAR) fields and b-end
  24.

  PL/SQL procedure successfully completed.

  SQL >

• Procedure check constraint

  Hi all
  
  My procedure should check, if the constraints are violated, and if they do then the insertion must be rejected.
  
  How can I insert a code to this procedure to verify if the constraints are vilolated?
  
  Procedure:
  
  CREATE PROCEDURE add_new_customer)
  IN cust_no customer. CUST_NO % TYPE,
  c_name IN client. C_NAME % TYPE,
  IN c_city customer. C_CITY % TYPE,
  client IN c_telno. C_TELNO % TYPE,
  client IN c_faxno. C_FAXNO % TYPE,
  client IN cust_code. CUST_CODE % TYPE,
  client IN office_no. OFFICE_NO % TYPE)
  AS
  
  v_cust_no NUMBER (5);
  v_c_name VARCHAR (30): = 'John ';
  v_c_city VARCHAR (30): = "London";
  v_c_telno VARCHAR (20): = '07812586060';
  v_c_faxno varchar (20): = ";
  v_cust_code VARCHAR (2): = ';
  v_office_no NUMBER (5): = 125;
  
  BEGIN
  INSERT INTO customer (cust_no, c_name, c_city, c_telno, c_faxno, cust_code, office_no)
  VALUES (CUST_NO_SEQ. NEXTVAL, Upper (v_c_name), Upper (v_c_city), v_c_telno, v_c_faxno, Upper (v_cust_code), v_office_no);
  END;
  /
  
  
  
  Constraints are the following:
  
  Check the cust_code IN('A+','A','B1','B2','C1','C2',null) CUSTOMER_CUST_CODE_CK
  Primary_Key CUSTOMER_CUST_NO_PK
  Foreign_Key CUSTOMER_OFFICE_NO_FK
  SYS_C009827 check the "CUST_NO" IS NOT NULL
  SYS_C009828 check the "C_NAME' IS NOT NULL
  SYS_C009829 check the "C_CITY' IS NOT NULL
  SYS_C009830 check the 'C_TELNO' IS NOT NULL
  
  
  Thank you very much!!!
  
  Published by: 899335 on December 12, 2011 11:38
  
  Published by: 899335 on December 12, 2011 11:39

  >

  My code does not work:

  It is probably for this reason

  e_values EXCEPTION;
  

  It is declared in the executable section, when it should be declared in the declaration section.
  This is how the variables.

  There are other problems with your procedure. I have listed below as well as additional comments on things
  You should and should not do.

  -- 1.
  -- Use CREATE OR REPLACE - Much easier to work with
  CREATE OR REPLACE PROCEDURE add_new_customer (
  -- 2.
  -- Naming formal parameters exactly like table columns is not a good
  -- idea. You can run into hard to detect scope problems.
  -- The convention is some prefix, like P_ or IN_
    in_cust_no     IN customer.cust_no%TYPE,
    in_c_name      IN customer.c_name%TYPE,
    in_c_city      IN customer.c_city%TYPE,
    in_c_telno     IN customer.c_telno%TYPE,
    in_c_faxno     IN customer.c_faxno%TYPE,
    in_cust_code   IN customer.cust_code%TYPE,
    in_office_no   IN customer.office_no%TYPE
  ) AS
  
  -- 3.
  -- These variables are exactly the same as input parameters, you don't need them
  --  v_cust_no     NUMBER (5);
  --  v_c_name      VARCHAR (30) := 'Marcelo';
  --  v_c_city      VARCHAR (30) := 'London';
  --  v_c_telno     VARCHAR (20) := '07812586857';
  --  v_c_faxno     VARCHAR (20) := '';
  --  v_cust_code   VARCHAR (2) := '';
  --  v_office_no   NUMBER (5) := 125;
  BEGIN
  -- 4.
  -- You cannot declare anything here, you are in executable section
    -- e_values EXCEPTION;
    INSERT INTO customer (cust_no,
                          c_name,
                          c_city,
                          c_telno,
                          c_faxno,
                          cust_code,
                          office_no
                         )
  -- 4.
  -- You probably want to use the procedure's input parameters here, otherwise they aren't used.
    VALUES      (cust_no_seq.NEXTVAL,
                 UPPER (in_c_name),
                 UPPER (in_c_city),
                 in_c_telno,
                 in_c_faxno,
                 UPPER (in_cust_code),
                 in_office_no
                );
  
  -- 5.
  -- This is dead code, like in never reached. If v_cust_code were null,
  -- this would not be reached since the INSERT INTO would have raised an
  -- exception.
  --   IF v_cust_code = NULL THEN
  --     RAISE e_values;
  --   END IF;
  
  -- 5.
  -- Most often it is a bad idea to COMMIT inside a stored procedure.
  -- If you do the procedure will not be useful as part of a bigger transaction.
  --  COMMIT;
  
  -- 6.
  -- If you do not have anything reasonable to do with exceptions, don't handle it.
  -- Printing it out is not exception handling. You gain nothing, compared to letting
  -- it be (Called let it propagate).
  -- It is perfectly fine to let exceptios propagate, and very common.
  -- EXCEPTION
  --   WHEN e_values THEN
  --     DBMS_OUTPUT.put_line ('Cust Code cannot be empty.');
  
  -- 7.
  -- Use End Identifiers. Especially, once you start working with packages, they
  -- are very useful to keep track of where things end and what ends.
  END add_new_customer;
  /
  

  So, if I remove all my comments now, your procedure now looks like:
  (I also gave it a slightly different name, because I bet that you will add all guests are 'new')

  CREATE OR REPLACE PROCEDURE add_customer (
    in_cust_no     IN customer.cust_no%TYPE,
    in_c_name      IN customer.c_name%TYPE,
    in_c_city      IN customer.c_city%TYPE,
    in_c_telno     IN customer.c_telno%TYPE,
    in_c_faxno     IN customer.c_faxno%TYPE,
    in_cust_code   IN customer.cust_code%TYPE,
    in_office_no   IN customer.office_no%TYPE
  ) AS
  BEGIN
    INSERT INTO customer (cust_no,
                          c_name,
                          c_city,
                          c_telno,
                          c_faxno,
                          cust_code,
                          office_no
                         )
    VALUES      (cust_no_seq.NEXTVAL,
                 UPPER (in_c_name),
                 UPPER (in_c_city),
                 in_c_telno,
                 in_c_faxno,
                 UPPER (in_cust_code),
                 in_office_no
                );
  END add_customer;
  /
  

  Nice, isn't it?

  Then, you create a PACKAGE, say CUST and place your new procedure inside that, instead
  to leave a standalone procedure, which is rarely used.

  Best regards
  Peter

• How do you manage exceptions / errors in stored procedures?

  How do you manage exceptions / errors in stored procedures?

  Exceptions/errors can be handled in different ways in the stored procedures.
  (1) could be using an EXCEPTION block in the procedure in which to use WHEN THEN.
  (2) may declare a variable in the DECLARE section as EXCEPTION type,
  raise it to the extent necessary using STIMULUS and manipulate in EXCEPTIONAL setting using the WHEN clause.
  (3) could use keywords SQLCODE & SQLERRM to display no errors and the error code...

• What is the significance of the CURSOR WITH HOLD clause in a cursor declaration?

  What is the significance of the CURSOR WITH HOLD clause in a cursor declaration?

  A cursor that has been declared with the clause WITH HOLD, after the word CURSOR remains open after a COMMIT or a ROLLBACK. The following example shows how to use the following clause:

       EXEC SQL          DECLARE C1 CURSOR WITH HOLD          FOR SELECT ENAME FROM EMP          WHERE EMPNO BETWEEN 7600 AND 7700      END-EXEC.
  

  The cursor must not be declared for the UPDATE. The WITH HOLD clause is used in DB2 to override the default, which is to close all cursors on validation. Pro * COBOL provides this clause in order to facilitate the migration of applications to DB2 to Oracle. When MODE = ANSI, use Oracle DB2 default, but all host variables must be declared in a declare Section.

  Reference:

  Oracle documentation!
  http://docs.Oracle.com/CD/B10501_01/AppDev.920/a96109/pco03dbc.htm

• How to run a procedure with parameters in pl/sql collections?

  I created a procedure with parameter from the collection. Can somone help me how to run a procedure in passing the parameters in the collection.
  Package and how to create is successful. But I get the error message when executing the procedure.
  
  ORA-06550: line 3, column 19:
  PLS-00222: no function with name 'T_TAB' does exist in this scope
  
  I gave the example of code here. Can someone please help me solve this problem.
  
  -Spec package
  
  create or replace package pkg_dist is
  
  TABLE index IS THE NUMBER of t_tab_num TYPE of PLS_INTEGER;
  
  
  procedure prc_test (a t_tab_num IN,
  b IN t_tab_num,
  c IN OUT t_tab_num);
  end pkg_dist;
  
  -Package body
  
  create or replace package body is pkg_dist
  
  procedure prc_test (a t_tab_num IN,
  b IN t_tab_num,
  c IN OUT t_tab_num) is
  
  
  Start
  
  
  IF (a (16) = 0) then
  (16) c: = 0;
  c (17): = 0;
  c (18): = 0;
  end if;
  c (15): = (14)-(15)-a (16);
  (16) c: = b (16) /b (17);
  c (17): = 50;
  (18) c: = a (16) * 2;
  
  end prc_test;
  end pkg_dist;
  
  -executeing procedure
  
  declare
  TABLE index IS THE NUMBER of t_tab TYPE of PLS_INTEGER;
  x t_tab: = t_tab (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16);
  y t_tab: = t_tab (0,10,15,20,25,30,35,40,45,50,60,75,100,125,150,200,250,500);
  z t_tab;
  BEGIN
  pkg_dist.prc_test (x, y, z);
  dbms_output.put_line (z (18));
  END;
  
  Error:
  --------------------------------------------------------------------------------
  ORA-06550: line 3, column 19:
  PLS-00222: no function with name 'T_TAB' does exist in this scope

  My suggestion would be:

  CREATE OR REPLACE PACKAGE pkg_dist IS
  
     PROCEDURE prc_test (a IN SYS.odcinumberlist, b IN SYS.odcinumberlist, c IN OUT SYS.odcinumberlist);
  END pkg_dist;
  
  CREATE OR REPLACE PACKAGE BODY pkg_dist IS
     PROCEDURE prc_test (a IN SYS.odcinumberlist, b IN SYS.odcinumberlist, c IN OUT SYS.odcinumberlist) IS
     BEGIN
        IF (a (16) = 0) THEN
           c (16) := 0;
           c (17) := 0;
           c (18) := 0;
        END IF;
  
        c (15) := a (14) + a (15) + a (16);
        c (16) := b (16) / b (17);
        c (17) := 50;
        c (18) := a (16) * 2;
     END prc_test;
  END pkg_dist;
  /
  
  DECLARE
     x   SYS.odcinumberlist;
     y   SYS.odcinumberlist;
     z   SYS.odcinumberlist;
  BEGIN
     x := sys.odcinumberlist (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16);
     y := sys.odcinumberlist (0,10,15,20,25,30,35,40,45,50,60,75,100,125,150,200,250,500);
     z := sys.odcinumberlist (0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0);
     pkg_dist.prc_test (x, y, z);
     DBMS_OUTPUT.put_line (z (18));
  END;
  /
  

  See you soon,.
  Manik.

• declare a global temporary table

  Hello
  can I use the declare global temporary table (...) ststement of pl/sql, I need a temporary table for the current session.
  
  
  If not, what should be the alternative?
  
  Thank you...
  
  Published by: Amoeba on 23 August 2012 13:39
  
  Published by: Amoeba on 23 August 2012 13:41

  Hello

  >
  can I use declare global temporary table (...) as ststement of pl/sql, like I need a temporary table for the current session.

  If not, what should be the alternative?

  Thank you...
  >
  This query actually belongs to SQL and PL/SQL Forum. Please take care and post in the correct forum.

  In any case...
  CREATE TABLE TEMPORARY global is a DDL command. Once created TWGS will exist until he FELL. Try to create a TWG with the same name will fail. just like any table, view, etc. See http://docs.oracle.com/cd/B28359_01/server.111/b28310/tables003.htm#i1006400

  a: you can create a TWG once and use/re-use it anywhere in your code.
  (b) as it is a DDL you can not use in the DECLARE section. You can use BEGIN and EXCEPTION.

  See you soon,.

• Calling a procedure stored since SQL * PUS

  Hi all
  
  I want to call a procedure from SQL * MORE who returns the number, varchar2 and one OUT parameter as table index.
  I can declare a variable for the number and varchar2.
  How can I manipulate the array index passed into the procedure output parameter.
  
  Thanks, Sandeep

  declare
  a number, varchar2 (20) b;
  type t as table of varchar2 (10) index directory. -identical to your procedure declaration
  c t;
  Start
  procedure (a, b, c);
  end;
  /

• I am back! test a procedure through PL/SQL block

  Hi all!
  
  Do you know how to test a procedure? Please check mine, its gave me an error of what follows:-see the bottom of my test pls/sql code:
  ORA-06550: line 4, column 1:
  PLS-00306: wrong number or types of arguments in the call to 'MEMBER_CK_SP '.
  ORA-06550: line 4, column 1:
  PL/SQL: Statement ignored
  2 lv_name varchar2 (20);
  3. start to
  4 member_ck_sp('rat55','kile',lv_name);
  5 end;
  6. /
  
  CREATE OR REPLACE PROCEDURE member_ck_sp
  (p_id IN VARCHAR2,
  p_pw IN OUT VARCHAR2,
  p_cook ON the NUMBER,
  p_check OUT VARCHAR2)
  IS
  BEGIN
  SELECT firstname. » '|| LastName, cookie
  IN p_pw, p_cook
  OF bb_shopper
  WHERE username = p_id
  AND password = p_pw;
  EXCEPTION
  WHEN NO_DATA_FOUND THEN
  p_check: = 'INVALID ';
  END;
  /
  -This is the test of the procedure-
  declare
  lv_name varchar2 (20);
  Start
  member_ck_sp ('rat55', 'kile', lv_name);
  end;
  /

  For not being "Captain obvious" but your procedure takes 4 parameters, and you go to 3... so the wrong number of arguments error...

• Error in the PL/SQL procedure

  Kindly suggest how to correct the error in below given procedure
  
  DECLARE
     l_error   VARCHAR2 (4000);
  BEGIN
     FOR i IN 1 .. apex_application.g_f02.COUNT
     LOOP
        IF   (apex_application.g_f18(i)) IS NOT NULL
         AND (apex_application.g_f19(i)) IS NULL
         AND (apex_application.g_f20(i)) IS NULL
         AND (apex_application.g_f21(i)) IS NULL
        THEN
           l_error :=' Enter values for column  19,20,21 ';
        END IF;
     END LOOP;
   
     RETURN (l_error);
  END;
   
  I get the error - In a procedure, RETURN statement cannot contain an expression

  user12957777 wrote:

  Kindly suggest how to correct the error in below given procedure
  
  DECLARE
  l_error   VARCHAR2 (4000);
  BEGIN
  FOR i IN 1 .. apex_application.g_f02.COUNT
  LOOP
  IF   (apex_application.g_f18(i)) IS NOT NULL
  AND (apex_application.g_f19(i)) IS NULL
  AND (apex_application.g_f20(i)) IS NULL
  AND (apex_application.g_f21(i)) IS NULL
  THEN
  l_error :=' Enter values for column  19,20,21 ';
  END IF;
  END LOOP;
  
  RETURN (l_error);
  END;
  
  I get the error - In a procedure, RETURN statement cannot contain an expression
  

  You are in an anonymous PL/SQL block. By definition, they cannot return no matter what... you create a function if you want to use a RETURN order you are trying.

• Procedure call to different users

  HelloW to all,
  
  I have three database users
  1 USER1
  2 USER2
  3 USER3
  
  I created a procedure to User1
  
  Now, I want to use this same process in the User2 and user3 without created in these users.
  
  is there a way to do this?
  
  Any help will be appreciated...

  Hervé wrote:
  It is the use of tables of sml users...
  I want to use the tables of the bus user...

  The procedure declared to the SML schema must be created in the procedure of the appellant's rights. It's

  AUTHID CURRENT_USER

  Unlike the default
  DEFINE AUTHID

  Read all about it
  http://download.Oracle.com/docs/CD/E11882_01/AppDev.112/e25519/subprograms.htm#LNPLS682

  Concerning
  Peter

• Anyone? Store procedures

  Good afternoon everyone,

  I created a stored procedure in SQL for:

  < name cfquery = "rsDisposition" datasource = "#REQUEST.datasource #" >
  SELECT tlkp_Defects.Defect_Title,
  Sum (case when tbl_Assembly_Holds.Disposition_ID = 1 Then 1 else 0 end) FixedOnLine,
  Repair of Sum (case when tbl_Assembly_Holds.Disposition_ID = 2 Then 1 else 0 end),
  Sum (case when tbl_Assembly_Holds.Disposition_ID = 3 Then 1 else 0 end) Scrap
  
  Of
  tbl_Assembly_Holds
  Join tlkp_Disposition on tbl_Assembly_Holds.Disposition_ID = tlkp_Disposition.Disposition_ID
  Join tbl_Assembly_Hold_Defects on tbl_Assembly_Hold_Defects.TagNumber = tbl_Assembly_Holds.TagNumber
  Join tlkp_Defects on tbl_Assembly_Hold_Defects.Defect_ID = tlkp_Defects.Defect_ID
  WHERE
  tbl_Assembly_Holds.Record_date between "#FORM.dateFrom #" and "#FORM.dateTo #".
  GROUP BY
  tlkp_Defects.Defect_Title
  < / cfquery >

  I'm trying to call from CF8 but I get errors, here is my code:

  < cfstoredproc procedure = "defect_yield" datasource = "#REQUEST.datasource #" >
  < cfprocparam type = 'IN '.
  CFSQLType = CF_SQL_DATE
  value = "#FORM.dateFrom #" >
  < cfprocparam type = 'IN '.
  CFSQLType = CF_SQL_DATE
  value = "#FORM.dateTo #" >

  < / cfstoredproc >

  Any ideas on how to make this work? I want to convert most of the queries to stored procedures.

  Thanks in advance,

  DJ Khalif

  Defect_yield procedure has no parameters and arguments were provided.

  ALTER PROCEDURE. [defect_yield]

  (No settings here)

  AS

  SELECT

  As the error message said, you pass two arguments (#FORM.dateFrom # and #FORM.dateTo #) int, but your procedure does not provide everything. If you want the variable dates in the procedure, you must add these parameters to your procedure declaration

  ALTER PROCEDURE. [defect_yield]

  @DateFrom DATETIME,

  @DateTo DATETIME

  AS

  SELECT

  .....

  WHERE productDetails

  . dbo.tbl_Assembly_Holds.Record_date between

  "productDetails.dbo.tbl_Assembly_Holds.Record_date" and

  'productDetails.dbo.tbl_Assembly_Holds.Record_date '.

  GROUP BY...

  Once you add parameters, you can use these SQL variables within the query of the procedure, as well as in your original cfquery. More or less.

  WHERE the tbl_Assembly_Holds.Record_date between @DateFrom AND @DateTo...