I actually can reproduce this issue consistently. So, "ooziedb.sh create -run" will not create the necessary tables if you have another oozie instance running in oracle under the same SID. For example, your oracle db has a SID of "xe". And you have oozie_1 and oozie_2 schemas. One cluster runs oozie with username oozie_1. And you want to setup a another cluster running oozie under oozie_2 schemas. Your db create will not work since it assumes the tables exist already. I think this is a defect or limitation of openJPA.meta.MappingTool.main function that doesn't take in a schema name as a param for oracle DB.
________________________________ From: Mona Chitnis <[email protected]> To: "[email protected]" <[email protected]>; "[email protected]" <[email protected]>; "[email protected]" <[email protected]> Sent: Friday, September 12, 2014 2:31 PM Subject: RE: oozie on oracle issue No not faced this issue before. That might be because we have Oracle instance dedicated to Oozie database. You have multiple db_owners because of a shared instance between say Oozie and other projects' schemas? Sent from Yahoo Mail for iPhone ________________________________ From: bowen zhang <[email protected]>; To: [email protected] <[email protected]>; Subject: oozie on oracle issue Sent: Thu, Sep 11, 2014 6:15:01 PM Hi guys, I just want to ask if any of you encountered this problem with oozie on oracle: under the same oracle SID, you have multiple db_owners with respective schema. ooziedb.sh create -run creates tables in another db_owner's schema even though your username in oozie-site.xml is correct. Bowen
