• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WebSphere 4.0 "PiggyBank" Red Book

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Howdy Pardners.
I'm trying to run the PiggyBank example from IBM (http://publib-b.boulder.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg246134.html?Open).
* WebSphere 4.0 (trial edition) is on RedHat 7.1.
* Oracle 8.17i Enterprise edition runs on NT 4.0.
I'm trying to use Oracle as my CMP store, using classes12.zip from Oracle 8.17i, but I'm having very little luck.
The error I receive on startup is:
[01.08.29 13:02:20:519 GMT+11:00] 22330efb EJBEngine I WSVR0037I: Starting EJB jar: PiggyBank EJBs
[01.08.29 13:02:21:625 GMT+11:00] 22330efb JDBCPersister W JDBC persister creation failed
[01.08.29 13:02:21:721 GMT+11:00] 22330efb EJBEngine I WSVR0062E: Failed to start EJB, PiggyBank Application#piggybank-ejb.jar#Customer: String index out of range: -1
I've read the "Errata" from IBM regarding their use of the Oracle reserved word "NUMBER", and have made the changes accordingly. The persister now generates the following:
CREATE TABLE "CUSTOMER"
("ID" INTEGER NOT NULL,
"NAME" VARCHAR(32));
ALTER TABLE "CUSTOMER"
ADD CONSTRAINT "CUSTOMERPK" PRIMARY KEY ("ID");
CREATE TABLE "ACCOUNT"
("ACCNUMBER" INTEGER NOT NULL,
"BALANCE" INTEGER,
"CHECKING" SMALLINT,
"CUSTOMERID" INTEGER);
ALTER TABLE "ACCOUNT"
ADD CONSTRAINT "ACCOUNTPK" PRIMARY KEY ("ACCNUMBER");
Has anyone out there ever attempted the Pig and had similar problems?
Please let me know if I can provide addition details - I didn't want to completely clutter the page!
Thanks,
~NJ!~
 
Jim Shaw
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well, solved this one on my own. Seems that the datasource manager mishandles the combining of strings to create the complete Oracle URL. Might have been easier had I used DB2 for my first attempt.
*CLOSED*
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic