Cannot export to reporting schema (File - Export - To Reporting Schema )

Question

I just installed SQL Data Modeler version 2.0.0 Build 584
Export to reporting schema (File -> Export -> To Reporting Schema ) is not working.
I created a report schema and tried to export the Sql Data Modeler (SDM) repository to the Oracle schema.
I received the following error from SDM: "Error occured while exporting to Reporting Schema. See the log for details".
I checked the log ( View -> Log ) and all the log contained was "2010-01-18 11:10:23 - Exporting to Reports Schema"
The reports schema contained 44 tables. None of the tables contain any data.
I can create a test table and add data to it in the reporting schema. There is lots of quota available to the reports schema.
I have tried the report export to Oracle several times with the former version with mixed results.
Any suggestion? Does the "export to reporting schema" work for anyone else?
The following script from TOAD describes the reports schema.
CREATE USER SDM_REPORT
IDENTIFIED BY <password>
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for SDM_REPORT
GRANT CONNECT TO SDM_REPORT;
GRANT RESOURCE TO SDM_REPORT;
ALTER USER SDM_REPORT DEFAULT ROLE ALL;
-- 15 System Privileges for SDM_REPORT
GRANT CREATE TRIGGER TO SDM_REPORT;
GRANT CREATE PROCEDURE TO SDM_REPORT;
GRANT DROP PUBLIC SYNONYM TO SDM_REPORT;
GRANT DEBUG CONNECT SESSION TO SDM_REPORT;
GRANT CREATE MATERIALIZED VIEW TO SDM_REPORT;
GRANT CREATE TABLE TO SDM_REPORT;
GRANT CREATE SESSION TO SDM_REPORT;
GRANT SELECT ANY DICTIONARY TO SDM_REPORT;
GRANT CREATE ROLE TO SDM_REPORT;
GRANT CREATE VIEW TO SDM_REPORT;
GRANT CREATE TYPE TO SDM_REPORT;
GRANT CREATE SEQUENCE TO SDM_REPORT;
GRANT CREATE PUBLIC SYNONYM TO SDM_REPORT;
GRANT CREATE ANY SYNONYM TO SDM_REPORT;
GRANT UNLIMITED TABLESPACE TO SDM_REPORT;
-- 1 Tablespace Quota for SDM_REPORT
ALTER USER SDM_REPORT QUOTA UNLIMITED ON USERS;

Answer 1

Problem solved: Data Modeler would export other designs to an Oracle schema but not the one I was working on (Babylon). I saved a copy of Babylon, BabylonReports and deleted everything except the relational model. Then I could export it to the repository. I assume that either the logical model or dataflow model had a problem which prevented Data Modeler from saving the export. Next time I'll run Design Rules to see if there is an error I can eliminate that will allow me to save an export.