Db2 805 Sql Error
Contents |
Recovery CICS DB2 High Availability IMS LPAR Migration Networks Performance Security Systems Management Tivoli Virtualization Workload Management BI and Analytics
Db2 Sqlcode 905
Business Applications Competitive Advantage Consolidation Executive perspective Green IT ROI CLOUD
Sqlcode 805 Sqlstate 51002
COMPUTING IBM ANNOUNCEMENTS IBM RESEARCH LINUX MOBILE MODERNIZATION OPEN SOURCE SECURITY SOA SOCIAL MEDIA WHAT'S NEW z/OS sqlcode 805 error z/VM zTALK Backup Data Management Disk Flash Servers Software Support Tape Automotive Banking/Finance Government Healthcare Insurance Manufacturing Miscellaneous Retail Application Development Miscellaneous System Tuning Systems Management Stop http://www.ibm.com/support/knowledgecenter/SSHT6S_8.1.0/com.ibm.tadz.doc/tshoot/ts_sqlcode805_error.html Run By Troy L Coleman Tweet RSS Recent Posts DB2 12 In-Memory Table Optimization 10/04/2016 DB2 12 In-Memory Index Optimization 09/27/2016 Open Source Tools and Languages for z/OS 09/20/2016 Become a Part of Generation z 09/13/2016 DB2 12 Continuous Delivery Model Webinar 09/06/2016 Links General DB2 sites: Troy L. Coleman DB2USA DB2 Pod Cast Interesting http://www.ibmsystemsmag.com/Blogs/DB2utor/January-2015/Solving-SQL-Error--805/ DB2 Sites Blogs: EXEC I/O Mainframe Craig Mullins: DB2 Portal Blog Willie Favero: Getting the Most out of DB2 for z/OS and System z Chris Eaton: An Expert’s Guide to DB2 Technology Education Library: DB2 V9.1 for z/OS Library FTP Directory of IBM Presentations User Groups: DB2 International User Group Midwest Database User Group (Chicago) Development Leading Edge: DB2 purXML Developer Works Alpha Works General Mainframe sites: CA IBM Mainframe IBM Destination z Previous Post | Next Post | See All Posts Solving SQL Error -805 January 27, 2015 In my career as a DBA, developers have asked me countless times about SQL Error -805. I'll tell you what I've always told them: This error can be triggered for any number of reasons. Developers who program in traditional languages (e.g., COBOL, Assembler, C, C++) on IBM z/OS may encounter SQLCODE -805 during the precompile process. Here's a sample of the error message: -805 DBRM OR PACKAGE NAME location-name.collection-id.dbrm-name.consistency-token NOT FOUND IN PLAN plan-name. R
Events Forums DB2-LDB2-L ArchivesNA ConferenceEMEA Conference Resources BlogsIDUG eBulletinIDUG NewsroomCommunitiesRegional User Groups Articles&Content IDUG Content ArticlesTech ChannelBeginner's BlogDB2 Hot Topics BlogContent LibraryIDUG YouTubePast Conference ContentCodeplace Library GetInvolved Volunteering with IDUGVolunteer PositionsJoin a Regional User GroupBecome an IDUG MentorSponsorship OpportunitiesJoin a CommunitySpeaker Community DB2 V9 on zOS - SQLCODE = http://www.idug.org/p/fo/et/thread=42481 -805 NOT FOUND IN PLAN DISTSERV Gary Snider DB2 V9 on zOS - SQLCODE = -805 NOT FOUND IN PLAN DISTSERV August 12, 2013 02:22 PM Hello, I am following up on and issue where a developer received the following messages while trying to call a stored procedure via DRDA on our development system. Programmer indicated that the program and package had not been recompiled or bound and was working some time ago. db2 sql DSNT408I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DEVL.ZOS.Y4061001.192773- B01333DC76 NOT FOUND IN PLAN DISTSERV. REASON 02 DSNT418I SQLSTATE = 51002 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNXEPM SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = -251 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'FFFFFF05' X'00000000' X'00000000' X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION They checked the SYSPACKAGE table and the package was valid and operative. In fact it db2 sql error was rebound (we do this for all packages weekly) on the previous Friday without any errors. I am told that the problem was resolved by freeing the package and binding the program again. What I find puzzling is that the message indicates that DB2 was looking for the package in plan DISTSERV. It should have been looking in plan ZOS. I don't understand why performing the bind again resolved the problem. Could someone please explain. Thanks. Philip Sevetson DB2 V9 on zOS - SQLCODE = -805 NOT FOUND IN PLAN DISTSERV August 12, 2013 02:46 PM (in response to Gary Snider) That stored procedure has a default Workload Manager (WLM). One thing to look at is whether it concatenates (to STEPLIB or JOBLIB) the same Load Libraries that received the compile of the stored procedure (I assume this is an external stored procedure?). -----Original Message----- From: Gary Snider [mailto:[login to unmask email] Sent: Monday, August 12, 2013 3:22 PM To: [login to unmask email] Subject: [DB2-L] - DB2 V9 on zOS - SQLCODE = -805 NOT FOUND IN PLAN DISTSERV Hello, I am following up on and issue where a developer received the following messages while trying to call a stored procedure via DRDA on our development system. Programmer indicated that the program and package ha