DB2 Connect 8.1 - ODBC problem (error: SQL0440N, routine named SQLTABLES)

ED

DB2 Connect 8.1 - ODBC problem (error: SQL0440N, routine named SQLTABLES)
Hello DB2-Lers,

Recently I installed DB2 Connect Personal Edition v8.1 with FixPak 2, in order to access DB2 OS/390.
Whenever I try to connect from any ODBC application (such as MS Excel's Query, or MS Visio 2002), I receive the following error message:

SQL0440N No authorized routine named "SQLTABLES" of type "" having compatible arguments was found. SQLSTATE=42884
SQLCODE -440

Previously I used DB2 Connect PE v7.2 and it was running perfectly.
Why couldn't v8.1 serve me as v7.2 used to?

Any help appreciated. Thanks...


Rich Gugel

Re: DB2 Connect 8.1 - ODBC problem (error: SQL0440N, routine name d SQLTABLES)
(in response to ED)
Have your database adiministrator install PQ62965

APAR Identifier ...... PQ62695
<file:///C:/ibmlink/link2/sis/sisPage.jsp?applJsp=documentBrowse.jsp&docNumb
er=PQ62695&searchStr=PQ62695&navItem=sis.jsp> Last Changed ........
03/08/07
ADD STORED PROCEDURES AND VIEWS FOR USE BY ODBC AND JDBC DRIVERS


-----Original Message-----
From: ED [mailto:[login to unmask email]
Sent: Saturday, September 13, 2003 6:29 AM
To: [login to unmask email]
Subject: DB2 Connect 8.1 - ODBC problem (error: SQL0440N, routine named
SQLTABLES)


Hello DB2-Lers,

Recently I installed DB2 Connect Personal Edition v8.1 with FixPak 2, in
order to access DB2 OS/390.
Whenever I try to connect from any ODBC application (such as MS Excel's
Query, or MS Visio 2002), I receive the following error message:

SQL0440N No authorized routine named "SQLTABLES" of type "" having
compatible arguments was found. SQLSTATE=42884
SQLCODE -440

Previously I used DB2 Connect PE v7.2 and it was running perfectly.
Why couldn't v8.1 serve me as v7.2 used to?

Any help appreciated. Thanks...
To change your subscription

http://listserv.ylassoc.com. The owners of the list can be reached at
[login to unmask email]




Steve Whittaker

DB2 Connect error
(in response to Rich Gugel)
We're running DB2 Connect Enterprise Edition / v7.2 Fixpak 5 on an NT Win 2000 machine.
I'm seeing these errors this morning in our db2diag file. Anyone have any thoughts on what could be the cause? Haven't seen anything like this before:

2003-12-04-01.29.49.975000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
base_sys_utilities sqleGetAgent Probe:75

Agent not allocated, sqlcode = -1226

2003-12-04-01.29.49.991000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
common_communication sqlcctcpconnmgr_child Probe:125
DIA3003E Error encountered in "TCPIP" protocol support. Return code from
"sqleGetAgent" was "-1226".

2003-12-04-01.29.50.007000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
base_sys_utilities sqleGetAgentFromPool Probe:97
DIA3847C An error occurred in a database page header.

thanks:
--Steve....

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

paul martin

Re: DB2 Connect error
(in response to Steve Whittaker)
Seems like you will have to increase maxagents in you DBM CFG on the DB2
Connect system
Here's what I have ours set at:
Max number of existing agents (MAXAGENTS) = 200
Paul

-----Original Message-----
From: Whittaker, Stephen [mailto:[login to unmask email]
Sent: Thursday, December 04, 2003 8:14 AM
To: [login to unmask email]
Subject: DB2 Connect error


We're running DB2 Connect Enterprise Edition / v7.2 Fixpak 5 on an NT Win
2000 machine.
I'm seeing these errors this morning in our db2diag file. Anyone have any
thoughts on what could be the cause? Haven't seen anything like this before:

2003-12-04-01.29.49.975000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
base_sys_utilities sqleGetAgent Probe:75

Agent not allocated, sqlcode = -1226

2003-12-04-01.29.49.991000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
common_communication sqlcctcpconnmgr_child Probe:125
DIA3003E Error encountered in "TCPIP" protocol support. Return code from
"sqleGetAgent" was "-1226".

2003-12-04-01.29.50.007000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
base_sys_utilities sqleGetAgentFromPool Probe:97
DIA3847C An error occurred in a database page header.

thanks:
--Steve....

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm


CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may
contain confidential and privileged information for the use of the
designated recipients named above. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Alice Frus

Re: DB2 Connect error
(in response to paul martin)
I was told fix pak 5 was buggy - try fikpak 6 - we have used that with no
problems.



"Whittaker, Stephen"
<stephen.whittaker@P To:
[login to unmask email]
GNMAIL.COM> cc:
Sent by: "DB2 Data Subject: DB2 Connect error
Base Discussion
List"
<[login to unmask email]
>
12/04/2003 08:14 AM
Please respond to
"DB2 Database
Discussion list at
IDUG"




We're running DB2 Connect Enterprise Edition / v7.2 Fixpak 5 on an NT Win
2000 machine.
I'm seeing these errors this morning in our db2diag file. Anyone have any
thoughts on what could be the cause? Haven't seen anything like this
before:

2003-12-04-01.29.49.975000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
base_sys_utilities sqleGetAgent Probe:75

Agent not allocated, sqlcode = -1226

2003-12-04-01.29.49.991000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
common_communication sqlcctcpconnmgr_child Probe:125
DIA3003E Error encountered in "TCPIP" protocol support. Return code from
"sqleGetAgent" was "-1226".

2003-12-04-01.29.50.007000 Instance:DB2 Node:000
PID:1320(db2syscs.exe) TID:1584 Appid:none
base_sys_utilities sqleGetAgentFromPool Probe:97
DIA3847C An error occurred in a database page header.

thanks:
--Steve....

---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm





**********
The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use of the
addressee. Unauthorized use, disclosure, distribution or copying is strictly
prohibited and may be unlawful. If you have received this communication in
error, please notify the sender immediately at (312)653-6000 in Illinois;
(972)766-6900 in Texas; or (800)835-8699 in New Mexico.
**********

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Myron Miller

Re: DB2 Connect error
(in response to Alice Frus)
FP6 is seriously more stable than FP5. But FP10a is out and should be used.
Any thing less than this has some security holes that a determined hacker could
use to compromise the system.

Myron
--- [login to unmask email] wrote:
> I was told fix pak 5 was buggy - try fikpak 6 - we have used that with no
> problems.
>
>
>
> "Whittaker, Stephen"
> <stephen.whittaker@P To:
> [login to unmask email]
> GNMAIL.COM> cc:
> Sent by: "DB2 Data Subject: DB2 Connect error
> Base Discussion
> List"
> <[login to unmask email]
> >
> 12/04/2003 08:14 AM
> Please respond to
> "DB2 Database
> Discussion list at
> IDUG"
>
>
>
>
> We're running DB2 Connect Enterprise Edition / v7.2 Fixpak 5 on an NT Win
> 2000 machine.
> I'm seeing these errors this morning in our db2diag file. Anyone have any
> thoughts on what could be the cause? Haven't seen anything like this
> before:
>
> 2003-12-04-01.29.49.975000 Instance:DB2 Node:000
> PID:1320(db2syscs.exe) TID:1584 Appid:none
> base_sys_utilities sqleGetAgent Probe:75
>
> Agent not allocated, sqlcode = -1226
>
> 2003-12-04-01.29.49.991000 Instance:DB2 Node:000
> PID:1320(db2syscs.exe) TID:1584 Appid:none
> common_communication sqlcctcpconnmgr_child Probe:125
> DIA3003E Error encountered in "TCPIP" protocol support. Return code from
> "sqleGetAgent" was "-1226".
>
> 2003-12-04-01.29.50.007000 Instance:DB2 Node:000
> PID:1320(db2syscs.exe) TID:1584 Appid:none
> base_sys_utilities sqleGetAgentFromPool Probe:97
> DIA3847C An error occurred in a database page header.
>
> thanks:
> --Steve....
>
>
---------------------------------------------------------------------------------
>
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
> "Join or Leave the list". If you will be out of the office, send the SET
> DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
> can be reached at [login to unmask email] Find out the latest on
> IDUG conferences at http://conferences.idug.org/index.cfm
>
>
>
>
>
> **********
> The information contained in this communication is confidential, private,
> proprietary, or otherwise privileged and is intended only for the use of the
> addressee. Unauthorized use, disclosure, distribution or copying is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify the sender immediately at (312)653-6000 in Illinois;
> (972)766-6900 in Texas; or (800)835-8699 in New Mexico.
> **********
>
>
---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
> "Join or Leave the list". If you will be out of the office, send the SET
> DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can
> be reached at [login to unmask email] Find out the latest on IDUG
> conferences at http://conferences.idug.org/index.cfm


__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm