Icorrect table creation statements being generated for DB2

Question

Hi,
I am using JDeveloper 903 and I have a datsource of IBM DB2 ver 7.3 type. I am creating a CMP2.0 beans Person and Address. When I try running these beans from JDeveloper on the embedded OC4J, I get the following exception :
AAuto-creating table: create table Person_current_workspace_app__vkk_AmsNTO_Project1_classes_ (id BIGINT not null primary key, firstName VARGRAPHIC(255) null, lastName VARGRAPHIC(255) null, middleName VARGRAPHIC(255) null)
Auto-creating table: create table Address_current_workspace_app__vkk_AmsNTO_Project1_classes_ (id BIGINT not null primary key, address1 VARGRAPHIC(255) null, address2 VARGRAPHIC(255) null, city VARGRAPHIC(255) null, state VARGRAPHIC(255) null, zip VARGRAPHIC(255) null, type VARGRAPHIC(255) null, Address_addresses BIGINT null)
Auto-creating table: create table Address_addresses_Address_Address_addresses_current_workspace_app__vkk_AmsNTO_Project1_classes_ (Address_id BIGINT not null)Error creating table: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "," was found following "VARGRAPHIC(255) null". Expected tokens may include: "<references_spec>". SQLSTATE=42601Error creating table: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "," was found following "VARGRAPHIC(255) nu[i]Long postings are being truncated to ~1 kB at this time.

Answer 1

Thanks wildmight for the reply.
You're right on with the tip you provided -- I figured that this had to be related to some DB object setting in the Physical Layer. As I've never been able to find any documentation from Oracle on the definition of the "Features" tab settings, I just began trial-and-error troubleshooting with the settings to see what I could find. I actually tested it by selecting every "Value" checkbox in the 'Features" tab to see what I'd get. :D
Apparently, when I selected "DB2/AS400" as the database object's data source type in the "General" tab, the "Features" tab also got updated to default DB2 features that OBIEE thinks are appropriate. HOWEVER, there is one +slightly+ important feature is then automatically deselected (and also not listed as "default") in the list:
*DERIVED_TABLES_SUPPORTED*
Once I put a check in the "Value" column of the "Features" tab and re-ran my query, it actually submitted one unified query to the DB as I had hoped!
I have a fact table with about 30 million rows and when I would ask for only a month's worth of data, it previously would return ALL 30M records and then filter down on my month. That query was taking about 15 minutes. After I got the view to work properly, the same query took 19 seconds. :)
Cheers,
Jeremy