JAVA error when exporting to reporting schema ODDM 4.1

When attempting to export a design to a reporting schema, we received the following error:
ERROR ReportsHandler - error exporting to reporting schema:
java.lang.classcastException: oracle.dbtools.crest.model.design.relational.column cannot be cast to oracle.dbtools.crest.model..design..relational.columnView
at oracle.dbtools.crest.exports.reports.RSViewColumn.export (RSViewColumns.java:43
at oracle.dbtools.crest.exports.reports.RSRelationalModel.export (RSRelationalModel.java:62)
at oracle.dbtools.crest.exports.reports.ReportsHandler.export (ReportsHandler.java:135)
at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run (ControllerApplication.java:2079)
We downloaded and installed ODDM 4.1 (EA-1) build 4.1.0.866 to resolve an issue with column widths when exporting to the reporting schema (per SR 3-10154440761).  This is the 64 bit version with the included JAVA 1.8 JRE.

David,
We migrated this model from data modeler 3.3.  That Model was created from an import from Oracle Designer.  We have not yet tried to import the data model from Oracle Designer directly into v4.1 but are planning to do so shortly.   When we tried to export that design (from v3.3) to the reporting schema, it failed with object too large for column errors.  We wrote SR 3-10154440761 and were advised by Michael Wickham to use v4.1 EA as the column size issue had been resolved in this version.  It was apparent that the export to the reporting schema was making more progress before it failed on the JAVA error.
We are trying to migrate from Oracle designer to Oracle Data Modeler

Similar Messages

  • EA2:Error on Export to Reporting Schema

    While i was trying to export the created desing to the reporting schema, found the below error in the log.
    2010-11-29 16:01:26,741 [Thread-56] ERROR ReportsHandler - Error Exporting to Reporting Schema:
    java.sql.SQLException: ORA-12704: character set mismatch
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)
         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1008)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3530)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
         at oracle.dbtools.crest.exports.reports.RSCommentsInRDBMS.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.RSEntities.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.RSLogicalModel.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
         at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
    Can someone help me understanding what is going wrong here or suggest on what should be characterset defined for the database.

    From the stack trace it appears that the problem area is the "Comments in RDBMS" in one of the Entities in the Logical Model.
    Are there any special characters in any of these text panels?

  • Crystal Reports: Print Engine Error when exporting a report

    We recently upgraded from Crystal Reports 2008 to BusinessObjects Edge Series X3.1. When exporting a report to an excel data-only format we get "Crystal Reports: Print Engine Error". All other formats work fine.  Any help is highly appreciated.
    Thanks,
    Jaseem

    Anyone?

  • File I/O error when exporting a report

    Post Author: Beth
    CA Forum: Exporting
    Hi,I have a program that runs as a scheduled task daily that runs four reports and exports them to rtf format.  This process has been running fine for a long time (several years).  However I've noticed now that I occasionally get an exception with the message "File I/O error", and the stacktrace doesn't give a much more useful information (see below): 5/4/2007 7:47:29 PM exception caught - Message:File I/O error.  5/4/2007 8:36:25 PM    at  . F(Int16   , Int32   )   at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)   at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export()   at CrystalDecisions.CrystalReports.Engine.ReportDocument.Export()   at EmailReport.Form1.ExportReport(TableLogOnInfo crTableLogOnInfo, String exportFilePath, String reportLocation)   at EmailReport.Form1.crystalReportViewer1_Load(Object sender, EventArgs e)As mentioned, this exception message and stack trace don't give me any information as to what the problem might be, and a search on the web hasn't yielded anything to help either.  Is there anyway to find more information as to the root cause of the exception?  Does anyone know what the File I/O Error means?As I said, this is not a new report, but something that has been in Production a long time.  My best guess is some upper limit on the report has been reached, and at this particular time the number of records being processed for this report is too big.  But I don't know how to prove this - the report was written by someone who has long left the company, so I don't know too much about the details of the report (as I don't know much about Crystal Reports to begin with).System Info:The machine exporting the report is a W2K machine.The executable was build using VS2003 with .NET 1.1 framework and CR8.5 and C#.The program itself contains a Form with a CrystalReportViewer object. Then creates a ReportDocument object, sets the appropriate parameters, then calls Export().Does anyone have any insight into what this exception means?Thanks,Beth  

    Chapter markers are not relevant to this. How long's the movie? What drive are you exporting to? How much space is on the drive? Did you render everything (Opt-R) before exporting? Did you mixdown the audio (Cmd-Opt-R) before exporting?

  • CRAXDRT Error when exporting a report to Excel

    I have a large report in Crystal Reports, using the browser, inside a COTS package called Medgate. It's 521 pages. I can export to PDF just fine, but when I export to Excel, I get "CRAXDRT Error Occured on Server: -2147206450: Disk full." The popup window is titled "Report Viewer Export."
    The disk is not in fact full. How can I resolve this error?

    Did you write that software, COTS package called Medgate?
    If not then ask that company for support. No one here would know how to fix it. They are using the CR RDC report engine.
    Thank you
    Don

  • Logon Failed when exporting crystal report to PDF

    Hi, I am Teguh
    i want to ask about error when export crystal report to pdf
    error message
    CrystalDecisions.CrystalReports.Engine.LogOnException: Logon failed
    [LogOnException: Logon failed.]
       .I(String , EngineExceptionErrorID ) +506
       .D(Int16 , Int32 ) +537
       .C(Int16 ) +10
       CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext) +577
       CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportFormatType formatType) +141
       Falcon.CRTransferSlip.Page_Load(Object sender, EventArgs e) in C:\inetpub\wwwroot\Falcon\CRTransferSlip.aspx.vb:77
       System.Web.UI.Control.OnLoad(EventArgs e) +67
       System.Web.UI.Control.LoadRecursive() +35
       System.Web.UI.Page.ProcessRequestMain() +750
    environment:
    OS : Windows server 2008 standard SP1
    IIS: Version 7.0
    SQL: Sql server 2000
    VS : Visual studio 2003
    i really confused with this error,
    please help me for this problem
    many thank's

    Hi Ludek
    Thank you for your response. I have installed SP3 and ProcMon and still the same result.
    I applied a filter on ProcMon to filter out items where the path contains 'export'.
    There are a few items where the result is 'NAME NOT FOUND' but I don't think it necessarly had anything to do with the barcode. These include items such as 'EXPORT\MailDestType','EXPORT\DisableExportLiveOfficeSupport'','EXPORT\ExportDirectory' to name a few.
    What drew my attention was the ACCESS DENIED result on specifically the EXPORT\PDF folders. The detail for these are  Desired Access : All access, however the very same entry appears a little futher on as a SUCCESS but this is detailed as Desired Access: Query Value.
    So in summary it looks something like this:
    User : Server\XXX
    Operation : RegOpenKey
    Path : HKU\.DEFAULT\Software\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf
    Result : ACCESS DENIED
    Desired Access : All Access
    User : Server\XXX
    Operation : RegOpenKey
    Path : HKU\.DEFAULT\Software\Business Objects\Suite 12.0\Crystal Reports\Export\Pdf
    Result : SUCCESS
    Desired Access : Query Value
    There are a few other entries that follow this pattern that exists in other locations such as HKLM\Software...
    Could this 'ACCESS DENIED' be the problem? and If so how do I, and should I give user XXX this ALL Access its looking for.
    Regards
    Elroy

  • Data Modeler version 2.0.0 - Export to reporting schema error

    Hi i have the Oracle SQL Developer Data Modeler version 2.0.0 installed.
    When i try to export one diagram to the reporting schema, i get the following error : "Error occurred while exporting to Reporting Schema.See the log file for details".
    The log file has no errors.
    The repository owner is DBA.
    The connection is ok.
    Can you help me?
    Thanks in advance
    Paolo.

    Sorry for the log. I looked at the one at the bottom of the window, i didn't know of the one in the directory.
    I purged the log and i tried again with an account with only connect,resource privileges.
    At the bottom of the message you'll find the log.
    The java.exe points refers to the one in the java directory of the data modeler (i downloaded the one with Java included).
    Thanks for the answer
    Paolo.
    SQL> create user p identified by p default tablespace f2 temporary tablespace temp;
    User created
    SQL> grant connect,resource to p;
    Grant succeeded
    2009-10-23 09:53:10,921 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler Version: 2.0.0 Build: 570
    2009-10-23 09:53:11,546 [main] WARN AbstractXMLReader - There is no file with default domains (path: domains name: defaultdomains)
    2009-10-23 09:56:36,984 [Thread-4] ERROR ReportsHandler - Error Exporting to Reporting Schema:
    java.sql.SQLException: Missing IN or OUT parameter at index:: 10
         at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
         at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:110)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:171)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
         at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1737)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3376)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3462)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1061)
         at oracle.dbtools.crest.exports.reports.RSCheckConstraint.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.RSColumns.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.RSRelationalModel.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
         at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)

  • Error when exporting reports using MAPI

    We created a .NET class that wraps CR 2010 .NET Crystal Reports functions and made it COM visible. This class is used to create a COM object in a js script which in turn used to export reports to a PDF file with the destination MAPI.
    It exports reports just fine without any errors however if prior to instantiation the exporting class we instantiate a class that has nothing to do with the Crystal Reports functions, our exporting object throws u201CExternal component has thrown an exception.u201D error when exporting. It appears that it has something to do with the SideBySide feature. I was wondering if somebody knows what causes this and if there is a way to fix this problem.
    Thanks for your help!
    <br>
    <br>
    Below are 2 procmon.exe outputs, the first when exporting works and the second when it doesnu2019t
    <br>
    <br>
    <br>
    1) Procmon.exe output when exporting works fine
    <br>
    <br>
    <br>HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     Desired Access: Read
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir     SUCCESS     Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     FAST IO DISALLOWED     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
    <br>7:16:30.7403615 AM     test.exe     4396     FASTIO_QUERY_INFORMATION     C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     FILE LOCKED WITH ONLY READERS     SyncType: SyncTypeCreateSection, PageProtection:
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     SyncType: SyncTypeOther
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Image Base: 0x79260000, Image Size: 0x1073000
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     Type: QueryNameInformationFile, Name: \Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide     SUCCESS     Desired Access: Read
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide     SUCCESS     KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest     NAME NOT FOUND     Length: 20
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>
    <br>
    <br>//////////////////////////////////////////////////////////////////////
    <br>2) Procmon.exe output when exporting doesnu2019t work, notice that it tries to open MSO.dll at the same location as in the output above but fails, it tries then to open it at several other locations and fails
    <br>
    <br>
    <br>HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     Desired Access: Read
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir     SUCCESS     Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
    <br>HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     FAST IO DISALLOWED     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL     SUCCESS     Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     FILE LOCKED WITH ONLY READERS     SyncType: SyncTypeCreateSection, PageProtection:
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     SyncType: SyncTypeOther
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL     SUCCESS     
    <br>C:\Users\Paul\projects\temp\test\Debug\MSO.dll     FAST IO DISALLOWED     
    <br>C:\Users\Paul\projects\temp\test\Debug\MSO.dll     NAME NOT FOUND     Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
    <br>C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll     FAST IO DISALLOWED     
    <br>C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll     NAME NOT FOUND     Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
    <br>C:\Windows\SysWOW64\MSO.dll     FAST IO DISALLOWED     
    <br>C:\Windows\SysWOW64\MSO.dll     NAME NOT FOUND     Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
    <br>C:\Windows\system\MSO.dll     FAST IO DISALLOWED     
    <br>C:\Windows\system\MSO.dll     NAME NOT FOUND     Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
    <br>C:\Windows\MSO.dll     FAST IO DISALLOWED     
    <br>C:\Windows\MSO.dll     NAME NOT FOUND     Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

    I tried to run exporting code in a .net application and got the same error. I first created the COM object that causes the problem and then ran exporting CR functions. It works fine if I run the code without creating the COM object.
    Below is the code I used.
                Type objClassType = Type.GetTypeFromProgID("ebms.main");
                object objMain = Activator.CreateInstance(objClassType);
                try
                    object[] p = new object[4];
                    p[0] = "C:\\ebms\\co1";
                    p[1] = "C:\\ebms\\co1";
                    p[2] = "Administrator";
                    p[3] = "";
                    objClassType.InvokeMember("LoginToCompany", System.Reflection.BindingFlags.InvokeMethod, null, objMain, p);
                catch (Exception ex)
                this.RPTDoc = new ReportDocument();
                this.RPTDoc.Load(@"C:\\Users\\Paul\\Desktop\\AR Customer List.rpt");
                PdfRtfWordFormatOptions pdfOpts = ExportOptions.CreatePdfRtfWordFormatOptions();
                MicrosoftMailDestinationOptions mailOpts = ExportOptions.CreateMicrosoftMailDestinationOptions();
                ExportOptions exportOpts = new ExportOptions();
                pdfOpts.UsePageRange = false;
                exportOpts.ExportFormatOptions = pdfOpts;
                mailOpts.MailMessage = "something";
                mailOpts.MailSubject = "something";
                mailOpts.MailToList = "emailaddress";
                exportOpts.ExportDestinationOptions = mailOpts;
                exportOpts.ExportDestinationType = ExportDestinationType.MicrosoftMail;
                exportOpts.ExportFormatType = ExportFormatType.PortableDocFormat;
                try
                    this.RPTDoc.Export(exportOpts);
                catch (Exception ex)
                    MessageBox.Show(ex.Message, "Error", MessageBoxButtons.OK, MessageBoxIcon.Error);

  • Changing default color scheme when exporting ALV report to Excel spreadshee

    Hi all,
    We have a bunch of FI reports created using OOPS in abap.  Each of the reports has the functionality to be exported to an excel spreadsheet.  When exporting to Excel, the headers are a very dark brown color, making them difficult to read and it has been requested that they are shaded a lighter color.  I have not defined any sort of color scheme within the report itself, and I was wondering if there was a way to change the color scheme when exporting the report to excel.  Let me know if there is anything that can be done, thanks!

    check ur fcat

  • Sql Developer Data Modeler 3.0 EA1: Export - To reporting schema

    When launching Export -> To reporting schema the schema tables are created and messages show that data is being generated but after indicating that it "Exporting Diagrams" I get the following error message:
    "Error occurred while exporting to Reporting Schema. See the log file for details."
    and all the tables are left empty.
    The message log is not indicating that anything went wrong.
    What could be the problem?
    - Marc

    This is probably what you are looking for:
    2010-10-14 14:56:43,680 [Thread-11] ERROR ReportsHandler - Error Exporting to Reporting Schema:
    java.lang.NullPointerException
         at oracle.dbtools.crest.model.design.DesignPart.doSetMainViewVisible(Unknown Source)
         at oracle.dbtools.crest.model.design.DesignPart.setMainViewVisible(Unknown Source)
         at oracle.dbtools.crest.model.design.DesignPart.setMainViewVisible(Unknown Source)
         at oracle.dbtools.crest.exports.reports.RSDiagrams.ensureMainViewVisible(Unknown Source)
         at oracle.dbtools.crest.exports.reports.RSDiagrams.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
         at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
    What does it mean?
    / Marc de Oliveira

  • Data modeler, error when exporting to csv files

    hi, i have a relational model and i need to export this model to csv files, when exporting the model it errors,
    displaying the following error nmessage:
    Oracle SQL Developer Data Modeler Version: 2.0.0 Build: 584
    Oracle SQL Developer Data Modeler Export Log
    Date and Time: 2010-09-21 15:17:17
    Design Name: Diagram
    Model Name: CSV
    Export Finished
    Errors: 1
    Warnings:0
    <<<<< ERRORS >>>>>
    java.lang.NullPointerException
    the issue is a file is missing when exporting proccess is done, the file is DM_CommentsRDBMS.csv, this file contains the commens of columns.
    Thanks.

    Hi,
    I logged bug however information is not enough to locate the problem.
    You can use export to reporting schema in order to get your model exported - in database in that case.
    We are not going to extend "export to CSV file" functionality any further - it'll be as it is now.
    Philip

  • Export to Reporting Schema failure

    Can I get some help with the below error when attempting to export to reporting schema. I've reviewed the repository and 79 tables were created, but no data. I looks like this error occurs at the end of the process, but prior to sql commit. The DB is Oracle XE 10g.
    "Error occurred while exporting to Reporting Schema.See the log file for details"
    2011-11-12 06:33:45,859 [Thread-11] ERROR ReportsHandler - Error Exporting to Reporting Schema:
    java.lang.NullPointerException
         at oracle.dbtools.crest.model.xtdmapping.XtdMapping.isOwnerDesignPartLoaded(Unknown Source)
         at oracle.dbtools.crest.model.xtdmapping.XtdMapping.getOwnerObject(Unknown Source)
         at oracle.dbtools.crest.exports.reports.RSMappings.export(Unknown Source)
         at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
         at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
    Environment
    About
    Oracle SQL Developer Data Modeler 3.0.0.665
    Version 3.0.0.665
    Build 665
    Copyright © 2008,2010 Oracle. All Rights Reserved.
    IDE Version: 11.1.1.4.37.59.36
    Product ID: oracle.datamodeler
    Product Version: 3.0.0.665
    Version
    Component     Version
    =========     =======
    Java(TM) Platform     1.6.0_23
    Oracle IDE     3.0.0.665
    Versioning Support     3.0.0.665

    Hi,
    you can try Data Modeler 3.1 EA1 (available here http://www.oracle.com/technetwork/developer-tools/datamodeler/overview/index.html) or EA2 when it's published - mappings problem is fixed there.
    Philip

  • 4.0 EA1 Error during setting up reporting schema

    Hello,
    during creation of the reporting schema the following error window pops-up:
    Error occured while creating Reporting Schema. See the log file for details.
    The log file contains the following information:
    2013-08-20 09:20:00,036 [Thread-57] ERROR SchemaFactory - SchemaFactory create
    java.sql.SQLException: ORA-01450: maximum key length (3118) exceeded
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
    at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
    at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:999)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1315)
    at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1890)
    at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1855)
    at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:304)
    at oracle.dbtools.crest.exports.reports.SchemaFactory.createSchema(Unknown Source)
    at oracle.dbtools.crest.exports.reports.ReportsHandler.checkDB(Unknown Source)
    at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
    at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
    Build: 4.0.0.816
    Joop

    Hi,
    This exception is thrown by index creation and basically it depends on database db_block_size parameter.
    What you can do is setup the reporting repository from DM 3.3. After that run manually /datamodeler/reports/DMRS_Upgrade_Script_DM3.3_DM4.0.sql against the database. One (probably DESIGNS__IDX) of the index creation statements will fail. We'll fix the message in the log file with the exact index name.
    Thanks for reporting the issue

  • 'file could not be written due to an error' when exporting jpg

    I'm working with an Illustrator file in CS2 and after a certain point it has started saying 'the file could not be written due to an error' when exporting to a jpg.
    i've tried a couple things like deleting layers and although the file is much smaller, it still says the same error when exporting.
    at its highest it was 130mb as an illustrator file and jpgs were 2-5mb.
    i''ve tried copying some of the layers into a new file but the error report still comes when i'm exporting.
    i have vector and raster based data in the file and tried turning off/deleting either of the layers and there is no difference.
    i don't understand why it's started doing this because before it had no problem at all exporting before.
    ANY IDEAS ANYONE?  I'm trying not to have to reproduce days of work to remake the file.
    many thanks,
    P

    Mylenium,
    Sounds like you know a good deal about this product.  Is there any way to restore a color profile/setting to an earlier point?
    I don't recall changing it and to tell you the truth, wouldn't be able to say which it may have been set to before - if different.
    Thanks,
    Paul

  • Getting error while exporting the report

    Hi,
    I am facing error while exporting the report. Getting below error.
    "No data can be exported because there are no rows.Operation failed."
    how come this error is coming even though my report contains data.
    please do the needful.
    i am using the version discoverer 10g.
    Thanks,
    RC.

    I am having the same problem. I found this article in which the user was exporting 100,000 plus records and had the same issue exporting (Discoverer workbook exported to excel error - No dta can be exported and they were able to fix it by adjusting two memory settings in their pref.txt file. However, in my report there are only 1,100 records with eleven columns being returned. I export much larger reports on a daily basis.
    Originally, the report was returning records and when I would go to retrieve all records it would tell me that all the rows could not be returned and the data may be incomplete. After scrubbing my SQL I no longer get that message, but the report still will not export and I get the same error as you.
    I have not tried the pref.txt settings fix but may try it today to see if that is a workaround. I will then have to evaluate whether it is a good fix or just a band-aid.

Maybe you are looking for