Click here to Skip to main content
11,633,998 members (74,219 online)
Rate this: bad
good
Please Sign up or sign in to vote.
Hello,
New to forum and I need some help as soon as possible.

I have a procedure that I have written. When running the procedure in Oracle it works great gets the expected results, but when I try to call the procedure in Crystal 10.5 I get the error message PLS-00306: wrong number or types of arguments.

The issue seems to be with a parameter that is defined as a number. When I comment out that parameter or when i run another procedure without a "Number" parameter then I have no issues. Here is my procedure:

DROP TABLE XAGTLST_GT CASCADE CONSTRAINTS;
 
CREATE GLOBAL TEMPORARY TABLE XAGTLST_GT
(
ANGPNO VARCHAR2(8 BYTE) NOT NULL,
ANGPLC VARCHAR2(8 BYTE) NOT NULL,
ANBNTP VARCHAR2(2 BYTE) NOT NULL,
ANEFTO NUMBER NOT NULL
)
ON COMMIT DELETE ROWS
NOCACHE;
 

CREATE OR REPLACE PACKAGE XAGTLST_PKG
AS TYPE XAGTLST_CSR IS REF CURSOR
RETURN XAGTLST_GT%ROWTYPE;
END XAGTLST_PKG;
 

CREATE OR REPLACE PROCEDURE XAGTLST_PROC 
(XAGTLST_Cursor IN OUT XAGTLST_PKG.XAGTLST_CSR,
p_AgentID in umr_qlstage.AGENCM_TB.ANAGNT% type ,
p_EffectiveThruDt in umr_qlstage.AGENCM_TB.ANEFTO% type,
p_SourceDB in umr_qlstage.AGENCM_TB.SOURCE_DB% type
) 
AS
BEGIN
OPEN XAGTLST_Cursor FOR
SELECT ANGPNO,
ANGPLC,
ANBNTP,
ANEFTO
FROM UMR_QLSTAGE.AGENCM_TB
WHERE ANAGNT = p_AgentID
AND ANEFTO = p_EffectiveThruDt
AND substr(SOURCE_DB,1,2) = p_SourceDB;
END XAGTLST_PROC ;

[edit]Urgency removed, SHOUTING removed - OriginalGriff[/edit]
Posted 25-Sep-12 9:34am
Edited 26-Sep-12 1:14am
(no name)1.3M
v3
Comments
OriginalGriff at 26-Sep-12 7:15am
   
Urgency deleted: It may be urgent to you, but it isn't to us. All that your stressing the urgency does is to make us think you have left it too late, and want us to do it for you. This annoys some people, and can slow a response.

DON'T SHOUT. Using all capitals is considered shouting on the internet, and rude (using all lower case is considered childish). Use proper capitalisation if you want to be taken seriously.
Andrei Straut at 26-Sep-12 7:36am
   
How are you calling the procedure?

I have no idea about Crystal Reports, but are you using bound parameters? Take care that if you do, they may be bound positionally unless explicitly told be bound by name (I've had the same problem with a C# procedure I was calling, and got the same error).

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
0 OriginalGriff 8,758
1 Sergey Alexandrovich Kryukov 8,264
2 Mika Wendelius 6,755
3 F-ES Sitecore 2,344
4 Suvendu Shekhar Giri 2,095


Advertise | Privacy | Mobile
Web04 | 2.8.150728.1 | Last Updated 26 Sep 2012
Copyright © CodeProject, 1999-2015
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100