Connecting Tech Pros Worldwide Forums | Help | Site Map

Stored Procedures error SQL0440N on db2 8.1 fp5

shalini@austin.rr.com
Guest
 
Posts: n/a
#1: Nov 12 '05
All, we are trying to create and execute our stored procs on db2 ver
8.1 fp5. This is a new database that we setup and are having some
trouble. When I try and run the stored proc from the db2 command line,
I get the following error:

SQL0440N No authorized routine named "XXX" of type
"PROCEDURE" having compatible arguments was found. SQLSTATE=42884

When the application (java) tries to execute the sp. we see the
following error:

com.ibm.db2.jcc.c.....SqlException: DB2 SQL error: SQLCODE: -444,
SQLSTATE: 42724, SQLERRMC:

We have checked to make sure that:

- the schema exists
- the SP exists
- user executing the sp has execute permissions on the proc
- the user also has insert/update/delete rights on the table being
accessed in the sp

Please note that this is happening for all our stored procs.

Thanks!


Serge Rielau
Guest
 
Posts: n/a
#2: Nov 12 '05

re: Stored Procedures error SQL0440N on db2 8.1 fp5


shalini@austin.rr.com wrote:[color=blue]
> All, we are trying to create and execute our stored procs on db2 ver
> 8.1 fp5. This is a new database that we setup and are having some
> trouble. When I try and run the stored proc from the db2 command line,
> I get the following error:
>
> SQL0440N No authorized routine named "XXX" of type
> "PROCEDURE" having compatible arguments was found. SQLSTATE=42884
>
> When the application (java) tries to execute the sp. we see the
> following error:
>
> com.ibm.db2.jcc.c.....SqlException: DB2 SQL error: SQLCODE: -444,
> SQLSTATE: 42724, SQLERRMC:
>
> We have checked to make sure that:
>
> - the schema exists
> - the SP exists
> - user executing the sp has execute permissions on the proc
> - the user also has insert/update/delete rights on the table being
> accessed in the sp
>
> Please note that this is happening for all our stored procs.
>
> Thanks!
>[/color]
The number one reason for unexpected -440 is that the proc has a
CHAR() or SMALLINT argument and literals are provided (which are
VARCHAR() and INTEGER respectively).
Use CAST('hello' AS CHAR(..)) and CAST(1 AS SMALLINT) as required.
Once we get the -440 out of teh way let's look at the -444.

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
shalini@austin.rr.com
Guest
 
Posts: n/a
#3: Nov 12 '05

re: Stored Procedures error SQL0440N on db2 8.1 fp5


FYI...The same stored procs work on another database, same version. The
only thing that we changed when we created this new database, was the
schema. Any thoughts on that?

Serge Rielau wrote:[color=blue]
> shalini@austin.rr.com wrote:[color=green]
> > All, we are trying to create and execute our stored procs on db2[/color][/color]
ver[color=blue][color=green]
> > 8.1 fp5. This is a new database that we setup and are having some
> > trouble. When I try and run the stored proc from the db2 command[/color][/color]
line,[color=blue][color=green]
> > I get the following error:
> >
> > SQL0440N No authorized routine named "XXX" of type
> > "PROCEDURE" having compatible arguments was found. SQLSTATE=42884
> >
> > When the application (java) tries to execute the sp. we see the
> > following error:
> >
> > com.ibm.db2.jcc.c.....SqlException: DB2 SQL error: SQLCODE: -444,
> > SQLSTATE: 42724, SQLERRMC:
> >
> > We have checked to make sure that:
> >
> > - the schema exists
> > - the SP exists
> > - user executing the sp has execute permissions on the proc
> > - the user also has insert/update/delete rights on the table being
> > accessed in the sp
> >
> > Please note that this is happening for all our stored procs.
> >
> > Thanks!
> >[/color]
> The number one reason for unexpected -440 is that the proc has a
> CHAR() or SMALLINT argument and literals are provided (which are
> VARCHAR() and INTEGER respectively).
> Use CAST('hello' AS CHAR(..)) and CAST(1 AS SMALLINT) as required.
> Once we get the -440 out of teh way let's look at the -444.
>
> Cheers
> Serge
>
> --
> Serge Rielau
> DB2 SQL Compiler Development
> IBM Toronto Lab[/color]

Serge Rielau
Guest
 
Posts: n/a
#4: Nov 12 '05

re: Stored Procedures error SQL0440N on db2 8.1 fp5


shalini@austin.rr.com wrote:[color=blue]
> FYI...The same stored procs work on another database, same version. The
> only thing that we changed when we created this new database, was the
> schema. Any thoughts on that?
>
> Serge Rielau wrote:
>[color=green]
>>shalini@austin.rr.com wrote:
>>[color=darkred]
>>>All, we are trying to create and execute our stored procs on db2[/color][/color]
>
> ver
>[color=green][color=darkred]
>>>8.1 fp5. This is a new database that we setup and are having some
>>>trouble. When I try and run the stored proc from the db2 command[/color][/color]
>
> line,
>[color=green][color=darkred]
>>>I get the following error:
>>>
>>>SQL0440N No authorized routine named "XXX" of type
>>>"PROCEDURE" having compatible arguments was found. SQLSTATE=42884
>>>
>>>When the application (java) tries to execute the sp. we see the
>>>following error:
>>>
>>>com.ibm.db2.jcc.c.....SqlException: DB2 SQL error: SQLCODE: -444,
>>>SQLSTATE: 42724, SQLERRMC:
>>>
>>>We have checked to make sure that:
>>>
>>>- the schema exists
>>>- the SP exists
>>>- user executing the sp has execute permissions on the proc
>>>- the user also has insert/update/delete rights on the table being
>>>accessed in the sp
>>>
>>>Please note that this is happening for all our stored procs.
>>>
>>>Thanks!
>>>[/color]
>>
>>The number one reason for unexpected -440 is that the proc has a
>>CHAR() or SMALLINT argument and literals are provided (which are
>>VARCHAR() and INTEGER respectively).
>>Use CAST('hello' AS CHAR(..)) and CAST(1 AS SMALLINT) as required.
>>Once we get the -440 out of teh way let's look at the -444.
>>
>>Cheers
>>Serge
>>
>>--
>>Serge Rielau
>>DB2 SQL Compiler Development
>>IBM Toronto Lab[/color]
>
>[/color]
SET PATH = CURRENT PATH, <thatnewschema>

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
shalini@austin.rr.com
Guest
 
Posts: n/a
#5: Nov 12 '05

re: Stored Procedures error SQL0440N on db2 8.1 fp5


Thank you we figured out our issue. We were using a type 4 driver
instead of a type 2 driver to connect!


Serge Rielau wrote:[color=blue]
> shalini@austin.rr.com wrote:[color=green]
> > FYI...The same stored procs work on another database, same version.[/color][/color]
The[color=blue][color=green]
> > only thing that we changed when we created this new database, was[/color][/color]
the[color=blue][color=green]
> > schema. Any thoughts on that?
> >
> > Serge Rielau wrote:
> >[color=darkred]
> >>shalini@austin.rr.com wrote:
> >>
> >>>All, we are trying to create and execute our stored procs on db2[/color]
> >
> > ver
> >[color=darkred]
> >>>8.1 fp5. This is a new database that we setup and are having some
> >>>trouble. When I try and run the stored proc from the db2 command[/color]
> >
> > line,
> >[color=darkred]
> >>>I get the following error:
> >>>
> >>>SQL0440N No authorized routine named "XXX" of type
> >>>"PROCEDURE" having compatible arguments was found. SQLSTATE=42884
> >>>
> >>>When the application (java) tries to execute the sp. we see the
> >>>following error:
> >>>
> >>>com.ibm.db2.jcc.c.....SqlException: DB2 SQL error: SQLCODE: -444,
> >>>SQLSTATE: 42724, SQLERRMC:
> >>>
> >>>We have checked to make sure that:
> >>>
> >>>- the schema exists
> >>>- the SP exists
> >>>- user executing the sp has execute permissions on the proc
> >>>- the user also has insert/update/delete rights on the table being
> >>>accessed in the sp
> >>>
> >>>Please note that this is happening for all our stored procs.
> >>>
> >>>Thanks!
> >>>
> >>
> >>The number one reason for unexpected -440 is that the proc has a
> >>CHAR() or SMALLINT argument and literals are provided (which are
> >>VARCHAR() and INTEGER respectively).
> >>Use CAST('hello' AS CHAR(..)) and CAST(1 AS SMALLINT) as required.
> >>Once we get the -440 out of teh way let's look at the -444.
> >>
> >>Cheers
> >>Serge
> >>
> >>--
> >>Serge Rielau
> >>DB2 SQL Compiler Development
> >>IBM Toronto Lab[/color]
> >
> >[/color]
> SET PATH = CURRENT PATH, <thatnewschema>
>
> Cheers
> Serge
>
> --
> Serge Rielau
> DB2 SQL Compiler Development
> IBM Toronto Lab[/color]

Closed Thread