Lukas, I figured out my problem just after I posted here. I had the inputSchema in lower-case! When I changed it to upper-case, it worked beautifully.
Two minor suggestions: 1. since Oracle only allows upper-case schema names, you could use upper(schema_name) in your code and thus avoid this problem (basically treat it as if schema name is case-insensitive). This could be done for all other object names in Oracle as well. 2. if the code generation creates no table objects, you could output the query that likely caused this (in my case, the one that used the lower-case schema name) as informational (INFO) message to user. Since this would generally be an unexpected result, it would be helpful for newbies to see some output that helps them solve the problem. In any case, it is a satisfying first step to get that working. I'm looking forward to exploring further... thanks, john On Thursday, May 10, 2012 1:02:49 AM UTC-7, Lukas Eder wrote: > > I'm sorry I've missed the subject line. Your case is about Oracle.... > Can you post the code generation properties xml? Also, can you please > indicate what type of user you're using to generate code with? >
