This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Svelte and Sapper in Action and have Mark Volkmann on-line!
See this thread for details.
Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Unable to Execute Entity Beans in WAS 4.0

 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
We have developed an application in websphere 3.5 and now shifting it into websphere 4.0. Since my beans are of EJB 1.0, I ran the EJBDeploy tool and generated EJB1.1 compatible beans.
My Session beans are running successfully. But Entity bean is giving the following error.
Non-application exception occured while processing method create:com.ibm.websphere.cpi.CPIException:COM.ibm.db2.jdbc.Db2Exception [IBM][CLI Driver] [DB2/NT] SQL0204N "DB2ADMIN.EJBPACKAGE_LOGINEB" (LOGINEB is my Entity bean which is in the EJBPACKAGE ejb group) is an undefined name. SQLSTATE= 42704.
I am using DB2 7.2 and WAS 4.0 Advanced Edition.
I have created the Driver and Datasource and assigned this datasource to the concerned EJBs.
I checked the specific error in the net and I ran
bind db2home\bnd\db2cli.clp
bind db2home\bnd\db2ubind.clp

Still I am getting the specific error.
Any suggestions please....
Regds
Rajesh
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The error means that there is no Database table by that name in DB2. Can you open the DB2 Control Center and see if there is a table by that name created by the user DB2Admin?
If not, use the createtable.ddl file that is included in the deployed JAR file for your EJB to create it. See my EJB workbook (http://www.oreilly.com/catalog/entjbeans3/workbooks/index.html) for WebSphere 4.0 for information on how to use this file.
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
A lot of people cry when they cut onions. The trick is not to form an emotional bond. This tiny ad told me:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
    Bookmark Topic Watch Topic
  • New Topic