Click here to Skip to main content
15,886,689 members

PLS-00306: wrong number or types of arguments

Member 9458988 asked:

Open original thread
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:

SQL
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]
Tags: Oracle, CrystalReports

Plain Text
ASM
ASP
ASP.NET
BASIC
BAT
C#
C++
COBOL
CoffeeScript
CSS
Dart
dbase
F#
FORTRAN
HTML
Java
Javascript
Kotlin
Lua
MIDL
MSIL
ObjectiveC
Pascal
PERL
PHP
PowerShell
Python
Razor
Ruby
Scala
Shell
SLN
SQL
Swift
T4
Terminal
TypeScript
VB
VBScript
XML
YAML

Preview



When answering a question please:
  1. Read the question carefully.
  2. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
  3. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
  4. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
Please note that all posts will be submitted under the http://www.codeproject.com/info/cpol10.aspx.



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900