BUG: Export bugs

Cant export some results :
Case1 :
excute,
select 'xxxx' as ccc,null as ccb from dual
union all
select 'xxxx' as ccc ,null as ccb from dual
then try to export the result ---> some errors about "from" being not where it suppose to be ....
Case2:
Cannot give out the data but make a few unions with normal and literal fields and some function output string fields (like decode)
try to export the result, you get nothing but the console gives this error:
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at oracle.dbtools.raptor.dialogs.actions.TableExportAction.launchDlg(TableExportAction.java:176)
at oracle.dbtools.raptor.format.ui.ExportContextMenuListener$1.actionPerformed(ExportContextMenuListener.java:138)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1225)
at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1266)
at java.awt.Component.processMouseEvent(Component.java:6216)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5981)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4583)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4413)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4556)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4220)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4150)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2475)
at java.awt.Component.dispatchEvent(Component.java:4413)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Errors occur at any type of export ...
Last edit: here is an example of the second case:
select 'xxxxb' as ccc,null as ccb from dual
union all
select 'xxxxa' as ccc ,null as ccb from dual
order by ccc
Edited by: user7403061 on 01.Nis.2009 04:07
Edited by: user7403061 on 01.Nis.2009 05:29

Hi,
Confirmed that this is a reproducible issue. Have filed corresponding bug "8400792"
- Rakesh
Edited by: RakeshR on Apr 1, 2009 6:03 AM

Similar Messages

CR6.4 RC1 - XMP export bug, anybody else has it?

I think I found a bug, and although I also found a workaround, here it is.
My environment: Windows 7, Photoshop CS5, Camera Raw 6.4 RC1, all of them 64-bits.
Steps to reproduce the bug:
1. Open several raw files at once in Camera Raw (in my case, Olympus E-PL2 ORF files, but it probably doesn`t matter). For this bug, take images that are likely to have different white balance settings. Also make sure that those are original files, never modified by Camera Raw (or anything else) and that they have no XMP sidecars yet.
2. Wait until thumbnails are generated (may not be relevant...). Don't click on any of them, just let them be created.
3. Click on "Select All". Again, don't change the displayed image, just select them all.
4. In Basic/White Balance, select Auto. All thumbnails are properly updated
5. Export settings to XMP (from the menu on the right-most toolbar, i.e. still "Basic" if you haven`t changed it)
6. Keep Camera Raw open, and have a look at the XMP files.
The BUG : they all contain the same white balance settings (crs:WhiteBalance, crs:Temperature and crs:Tint) which happen to be the computed settings for the first image (the only one displayed so far). All other settings seems to be fine though (i.e. they are from their respective image).
However, if you go back in Camera Raw and then click on some other images, not all of them. You can see that their WB settings are different and properly computed (as far as "Auto" can properly compute them). Export to XMP again. WB settings are then right, but only for the images that you clicked on. Those that were never displayed full size still have the wrong WB settings (from the first image).
Obviously, the workaround is to click on each of them. Still that's a bit awkward, especially in my "quite-automated" workflow, where I'm not yet to the point to look at each image individually. Can't tell if this bug exist too on any other version of CR, and my E-PL2 raw files can only be opened in CR 6.4 anyway (unless I change some tags to fool CR).
Can anybody can reproduce that bug on similar or different environment? And could Adobe fix it, if it is a bug?

btw, don't know why I wrote RC1... I just meant Release Candidate!

I think I've found a bug... (CS 4 6.0.4, export to EPUB, w/ test case)

Hi everyone,
I think I've found a bug. I suppose I would like to see if others can reproduce it - I've managed to on 2 work machines, but the more the merrier. I suppose I'm also hoping that giving this bug more exposure will increase the likelihood of it getting resolved. I can dream
The bug shows itself when exporting an InDesign document (or book) to "Digital Editions", or as an EPUB file. The InDesign source needs to have a Table of Contents, and this TOC has to be used by the EPUB to create TOC entries (see the "contents" tab of the export window). In certain cases, using the InDesign TOC causes the EPUB export to garble certain characters; unicode-specific characters, in my experience.
Steps to reproduce:
Create a new document, add a blank text frame and fill it with placeholder text. add a heading to this text frame, styled appropriately.
Create a table of contents, using the heading style you defined and used previously.
Add some unicode characters to the end of your text frame. I've been using "bêche-de-mer — a genus", which has 2 unicode characters. My tests have shown about 1715 characters in the text frame is enough to trigger this bug.
Save the document and export to digital editions. under the "contents" tab, check the "include indesign TOC entries" option.
Open the EPUB (or unzip it and view the xhtml content). I would expect to see "bêche-de-mer — a genus" at the end. However, I see something more like "b√™che-de-mer ‚Äî a genus" instead. I do see the correct output if I don't check the "include indesign TOC entries" option when exporting to EPUB.
I've confirmed the fonts I've tried are unicode-compliant and have the relevant character codes. I'm running the latest update to InDesign CS4 (6.0.4) on OSX 10.4.11. This character encoding problem doesn't manifest itself in the PDF or IDML export, only the EPUB export. Choosing whether or not to include embedded fonts in the EPUB doesn't make a difference to the outcome. I have run this test on my machine and a workmates, which is OSX 10.5.[something]
I'll attach a test document to see if others can reproduce this bug. I'd be interested to hear if others can, or cannot reproduce it. I have submitted a bug report at https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform, but that doesn't exactly imbue me with confidence that anything will get done in a hurry...
This problem is pretty annoying; I can either have EPUB navigation, or uncorrupt text. My current (proposed) workaround is for the operator to create 2 EPUBs, one with a TOC and one without, and merge the two together... EPUB transplant if you will. A bit ugly....
thanks for listening!

Hiya Joe (and Archie)
It is indeed an annoying bug - I spent a few days looking around it before posting (wow, it must be nearly a year ago now).
Fortunately, it really is straightforward (if a bit of a hassle) to workaround:
- make 2 EPUBs, identical except one will have a TOC generated (epub-a), the other will not (epub-b)
- extract the TOC file from epub-a and insert it into epub-b
remembering that EPUB is a zip package, this is very easy indeed. On OSX you have /usr/bin/zip and /usr/bin/unzip to assist with extraction / insertion in a script (bash, applescript, etc). I don't think Windows comes with command-line zip programs, so you'd need to hunt around a bit.
Good luck. I don't know if this is resolved in the latest 6.0.5 patch - if you haven't updated to that, it might be worth a shot. And if you have and it's still a problem, please respond to this message just so there's a log stating as much.
Steve

ORA-20876 in csv export from interactive report = Possibly a bug?

Hi Apex team,
yesterday i tried to download data to csv from an interactive report. The resulting csv file contained a "ORA-20876: Stop APEX Engine" only and no other data. I played around with other reports in my application and had no problems with exports.
After some investigation i found out that the buggy report contains a column of display type "Display as text (based on a LOV, escape special characters)". When I changed this column type to "Standard Report Column" for example, the error didn't appear anymore and the csv export contained complete data.
Maybe this is a bug? The environment is Apex 4.1.1.00.23 on 11g (UTF-8). Is there a workaround available?
Regards,
Jens
Edited by: j.gauger on 06.02.2013 14:10
Additional Information
The problem seems to occur only if a Shared Components LOV of type "Static" is referenced in the IR column.

Hi,
what happens if you take the query from IR report and create a new classic report?
On this report enable csv export and then try the export.
Maybe that (format) data are causing export to fail.
Try to export just one row in your IR report (and classic report), so that you add where rownum < 2.
Regards,
Aljaz
Edited by: Aljaz on 6.3.2012 23:11
Edited by: Aljaz on 6.3.2012 23:29

Color Shift Happening When Exporting - Bug in Acrobat Export?

Hi, we are using InDesign CS3 and trying to output a file to send to a printer. We are desiring to have all colors converted to the printer's CMYK color space upon exporting (they sent us their ICC profile).
But we are getting a bizarre bug that I cannot figure out. It seems like it's actually a software bug, not an issue with settings. I'll try to describe the issue here:
Upon using 'Convert to Destination (Preserver Numbers or Not)' in the PDF export dialog in InDesign (using PDF/X-4 setting), using the 'Document CMYK' profile, there is a shift in color for 1 particular element. We have a grayscale image of a bunch of dots (black dots on solid white background) that is placed in a frame in InDesign. This image is 'colorized' in InDesign by setting an image color and a frame color (the image color appears as the 'foreground' and the frame color is the 'background'). We've been doing this all the way back to the Quark days (many years). But if the 'background/frame' color is a combination of C+M+Y (with no black), the Magenta and Yellow values are shifted to the Yellow and Black channels (for example - 52c, 5m, 10y, 0k becomes 52c, 0m, 5y, 10k).
I have never run into this before, and we've run this job with the same element many times now over the last couple years. But I have always used 'No Color Conversion' in my PDFs in the past. So it has something to do with the 'conversion'.
So far I've tried:
- Creating new document with just the single element, also created from scratch. So it's not an error in the file.
- Starting with different profiles (to make sure the profile wasn't corrupt).
- Choosing 'Preserve Numbers' or not when outputting PDF.
- All sorts of color combinations. It also appears that if there is black in the color, this value gets shifted to the magenta channel, then the magenta & yellow bump down.
- Checked the grayscale image to make sure it was flat, and using pure black & white colors. It is.
I've also tried printing to Distiller (we have Acrobat 8 Pro), but the settings are a lot different here so I'm not sure if I set it up properly. I made a duplicate of the default PDFX3 2002 profile, then edited the color settings to 'Convert Everything to CMYK' and set our printer's profile as the CMYK Color Space. But images are converted to 'DeviceCMYK' and not the profile I put.
- ANYBODY have any ideas or even know where I would start???
THANKS. This job needs to go out, but I'm also trying to get a solid workflow down for the future.

Looks like the issue in the CM thread.
I'm trying to replicate the issue but haven't done it yet. Still grasping at straws
1. Did the ID doc ever undergo Convert to Profile?
2. In Swatch Panel do "Add unnamed colors". Make sure the grayscale is colored with swatches, not colors created in the Color Picker
3. Do the color values in the swatches have crazy decimal values? Is the color mode of the swatches CMYK?
4. What format are the grayscale links - TIFF or PSD?
5. Make certain they are links, not embedded (I'm sure they are links though)
6. The colorization - are there tints applied to the object colors, or are they 100%?

MAJOR EDL Export BUG in 8.2!

I just upgraded to version 8.2 and now there is a major bug when exporting EDLs with audio clips!   EDLs (cmx3600 format) should only export Timecode In/Out for Source & Record.   The latest 8.2 version is now incorrectly outputting SAMPLE FORMAT for EDLS for any audio clips! This is a major bug and potentially show-stopping.
What 8.2 is exporting:
What it used to (and should continue to) export before 8.2:

with my PP 8.2.0 (65) Build, I get the same error with edl WAV audio clips until I 'link' video clip with audio clip below on the timeline
I believe after linking the video clip to the audio clip (below on the timeline), then exporting the edl, the timecode format displays properly
However, my edl export ability still needs work, because I would think my video timecode needs to match my audio timecode (for linked clips) so I am still working on importing the edl into Speedgrade and 'hearing' the audio
I was getting the same error audio text file as AjentJJ30, until I 'linked' video with audio,
so far my edl text file appears as below
TITLE: edl with wav link
FCM: DROP FRAME
001 AX       V     C        00:00:00:00 00:00:24:23 00:00:00:00 00:00:24:23
* FROM CLIP NAME: bmpcc_1_2015-02-05_0951_C0005_[000000-002420].mxf
002 AX       AA    C        01:03:06:05 01:03:30:28 00:00:00:00 00:00:24:23
* FROM CLIP NAME: full shoot
003 AX       V     C        00:00:24:23 00:00:41:22 00:00:24:23 00:00:41:22
* FROM CLIP NAME: bmpcc_1_2015-02-05_0955_C0001_[000000-004258].mxf
004 AX       AA    C        01:06:32:22 01:06:49:21 00:00:24:23 00:00:41:22
* FROM CLIP NAME: full shoot
005 AX       V     C        00:00:41:22 00:01:00:10 00:00:41:22 00:01:00:12
* FROM CLIP NAME: bmpcc_1_2015-02-05_0958_C0003_[000000-004444].mxf
006 AX       AA    C        01:09:17:29 01:09:36:17 00:00:41:22 00:01:00:12
* FROM CLIP NAME: full shoot
EDIT: as you can see my WAV file does not show the proper clip name, as well as not displaying the .wav file extension.
I chase after the edl displaying proper WAV data, but could not achieve any solid results. My dng video clips from the bmpcc have wav files, normally they do not import into Speedgrade with the dng sequence, so using the video clips to test the edl process isn't very helpful.
I can not get results to support having the WAV edl data working when importing into SpeedGrade.
Sorry to think otherwise.

Is this a BUG??? Database Export not including Foreign Key Constraints

I'm using SQL Developer 1.5.4 with both the 59.47 and 59.59 patches installed. I want to do a database export from a 10g XE schema, and include all objects in the resulting DDL. So, I select ALL the checkboxes in the export wizard and when I get to Step 3 to specify objects, I don't see any of my constraints in the listbox... no foreign key constraints, no primary key constraints, no check constraints, nothing. Is this a bug, or is there a workaround, or what could I possibly be doing wrong? We want to be able to use the database export feature to easily transport and track modifications to our entire schema using source control compare.
Any help or alternate suggestions would be apprieciated.
Thanks,
Matt

Thanks skutz, we just figured that out this morning. Also, it should be noted that you need to be logged in as the owner of the schema otherwise selecting nothing in the filter will give you nothing, but selecting items in the filter will give you those items even if you're not connected as the schema owner. I wonder if that is the detail of the Bug 8679318.
Edited by: mattsnyder on Jul 14, 2009 9:24 AM

Pixel Aspect Ratio bug in Media Encoder export

Having a weird bug in media encoder exports that I can't seem to figure out. I have a 1080p sequence with a mix of 1080p footage and PAL DV assets. The PAL assets have a pixel aspect ratio of 1.0940. When I format them in my Premiere sequence, I am able to scale them correctly and they look fine. When I export them directly from premiere to broadcast standards it's also fine.
However, when I try to export these sequences in Media Encoder via File->Export->Media-> Queue using the same exact settings (I'm using a preset), Media Encoder formats the PAL assets as if they have square pixels. Thus, half of the footage in my sequences gets horizontally "squished." Note that this does not happen for footage that natively has square pixels, such as my 1080p camera footage.
Has anyone encountered this bug? It seems strange to me that Media Encoder would treat items in a sequence differently that Premiere during export, I was under the impression they were using the same rendering engine... It's really a problem as I'm going to have to crank out multiple versions of this 48-minute film and not being able to queue those exports is going to be a huge headache.
Using latest version of CC 2014.1 (8.1.0).

Screenshot of Premiere Export (fills screen):
Screenshot of Media Encoder export: (notice the pillar-boxing)

Bug: Can't view photos in a slide when Exporting to PDF viewing files on XP

Hi,
I'm completely new to the discussion forum.
So hope this hasn't been covered, but the bug is there none the less.
When Exporting a Keynote 09 slide or slides that use some of the
new Layout themes(Kyoto style etc), nothing shows up when the
PDF is opened on Windows XP machines.
I have tried it on several machines at work and at schools,
and cant get photos or text to show up.
This never happened in 08, as i often have to use PDF to do presentations
at schools that dont have powerpoint no their pcs. PDF exporting
is really important in my daily work with keynote.
I really hope there is a fix or that Apple can release a fix
for this bug, as I would love to use the new layout themes
in presenting.
Strangely older themes have no problem opening and show all text and
photos as they should when exported using keynote 09 to pdf...
so i assume its an issue with the newer themes only ;(
wierd.. (cries)
Thanks in advance to anyone that can help me here. Apple!!! I luv you
but this issue is annoying the heck out of me.
D

Wow, thank you so much for quick replies!
Ok ill try and explain more.
1) I used to the Export feature (now I used SHARE > Export > choose PDF > save to desktop... view it.. its all good)
2) I then save the file onto a flash drive and put in a XP OS run PC
3) The slide background only shows up.. i.e. no content just the template itself
4) This only happens to the newer templates.
5) This happens when dragging a picture into the preset template picture boxes,
the picture just doesnt show up on the pc
6) havent checked file sizes, because i could do this process on keynote 08.. so i assumed its a BUG and not the fault of mine
7) Most importantly, i can do the same process and it works with the keynote 08
backgrounds and themes within 09.. but i cant get my PDFs on an XP to show when using the newer themes... just shows blank themes.. even for Kyoto theme, the tea pot picture isnt there.. its just the background
i am thinking of taking my mac into a mac store,
but im almost certain this is a bug.
to view the PDF on both my macbook and on XP i just double click
whats on the desktop and it usually shows.. but since buying 09,
as i said before, i can only get this to work for slides that use
the old 2008 keynote templates ;( ;(
i have not tried exporting using the print feature.. i will give that a shot today. but its so wierd that it shows up for some templates and not for others.
thanks again for your kind help. i really appreciate the time and effort
you are all putting in in helping.
D

"Preserve Aspect Ratio" Bug w/ DV Export

Hi,
I searched around and found no mention of this behavior, so figured I'd post what I discovered. There is a subtle bug in QuickTime when you convert to DV and check "Preserve Aspect Ratio" in the Size options. It's intimately connected with how QuickTime scales DV for display on screen.
DV resolution is 720x480, but with rectangular pixels. So some scaling is done to display the image using the computer screen's square pixels. The height to width ratio of a DV pixel is 1.1, so the correct resolution (i.e. no distortion of the image) to use on screen is about 654x480. But wait! QuickTime plays back DV at 640x480, and it's not distorted. What gives?
QuickTime knows the correct scaling factor and is actually displaying the image at 654x480, but it's chopping 7 pixels off the left and right sides to fit it in a 640x480 window. (The effect is even more pronounced with anamorphic 16x9 DV - 11-12 pixels get lopped off either side.) It's only a display issue - the pixels are still there, they're just not being drawn. It's a subtle effect you never really notice, and you get distortion-free playback.
The problem occurs when you need to export some video to DV that's not a standard aspect ratio (like the 2:1 clips I was converting). When you check the "Preserve Aspect Ratio" box, QuickTime scales your video to the 640x480 display area, keeping the original aspect ratio like it's supposed to. BUT it then proceeds to take the full 654x480 frame and encode it to DV. You end up with a very thin black border on the left and right, and ironically the aspect ratio you wanted to preserve is ever so slightly squished!
You never see the problem in QuickTime Player because of the display scaling trick, so all looks well. But bring the converted DV into iDVD or Final Cut and you can see the black border. (Again, it's more pronounced with anamorphic widescreen.) "Preserve Aspect Ratio" thus only exactly preserves the aspect if the only thing you're going to use to view the video is QuickTime. It is subtle, but if you're compositing the converted video with DV from another source it can be bothersome.
Hope this proves helpful,
-Robb
Dual-Core 2 GHz G5 Mac OS X (10.4.8) QuickTime Pro 7.1.5

I've seen the border in Final Cut. This is good to know - thanks.

Bug with exporting project to java source

Hi,
This is in TopLink 9.0.4.2 (Build 040311).
We're in the process of trying to determine if we should upgrade our TopLink from 2.5 to 9.0.4, and have not yet purchased a support contract because we haven't made the final decision yet, so I'm posting this bug here in hopes that someone can submit the bug.
In one of our projects, we have an AggregateObjectMapping (AOM) for a Measurement object that is owned by 2 different objects, each with 2 to 4 instances of this Measurement class. I set up the instances of the AOM in the workbench just fine, and looking at the XML descriptors that are written out, it appears fine. Exporting the project session XML file works fine as well. However, when it is exported to a Java file, the instances of the AOM are exported incorrectly as described below.
Here is the abbreviated mapping of the attributes of the Measurement class:
<mappings>
<mapping>
<inherited>false</inherited>
<instance-variable-name>mPrecision</instance-variable-name>
<default-field-names>
<default-field-name>direct field=yPrecision</default-field-name>
</default-field-names>
<uses-method-accessing>false</uses-method-accessing>
<read-only>false</read-only>
<mapping-class>MWDirectToFieldMapping</mapping-class>
</mapping>
<mapping>
<inherited>false</inherited>
<instance-variable-name>mQuantity</instance-variable-name>
<default-field-names>
<default-field-name>direct field=y</default-field-name>
</default-field-names>
<uses-method-accessing>false</uses-method-accessing>
<read-only>false</read-only>
<mapping-class>MWDirectToFieldMapping</mapping-class>
</mapping>
<mapping>
<inherited>false</inherited>
<instance-variable-name>mUnit</instance-variable-name>
<uses-method-accessing>false</uses-method-accessing>
<read-only>false</read-only>
<reference-descriptor>com.cimsoft.lws.units.Unit.ClassDescriptor</reference-descriptor>
<private-owned>false</private-owned>
<uses-batch-reading>false</uses-batch-reading>
<table-reference-mapping-reference-handle>
<reference-handle>
<reference-table>csrSlotGenericValue</reference-table>
<reference-name>csrSlotGenericValue_csdUnit</reference-name>
</reference-handle>
</table-reference-mapping-reference-handle>
<uses-joining>false</uses-joining>
<one-to-one-mapping-indirection-policy>
<indirection-policy>
<uses-indirection>false</uses-indirection>
</indirection-policy>
</one-to-one-mapping-indirection-policy>
<mapping-class>MWOneToOneMapping</mapping-class>
</mapping>
<mapping>
<inherited>false</inherited>
<instance-variable-name>UNDEFINED_MEASUREMENT</instance-variable-name>
<mapping-class>MWUnmappedMapping</mapping-class>
</mapping>
</mappings>
Notice that there are two direct to field mappings (mPrecision and mQuantity) and one OneToOneMapping (mUnit). The exported sessions XML file has the correct XML for instances of this object. Here is an example from a class that has 3 instances of this Measurement object mapped:
<database-mapping>
<attribute-name>mAlarmSize</attribute-name>
<read-only>false</read-only>
<reference-class>com.cimsoft.lws.units.Measurement</reference-class>
<is-null-allowed>true</is-null-allowed>
<aggregate-to-source-field-name-associations>
<association>
<association-key>unitId</association-key>
<association-value>csrStock.alarmSizeUnitId</association-value>
</association>
<association>
<association-key>y</association-key>
<association-value>csrStock.alarmSize</association-value>
</association>
<association>
<association-key>yPrecision</association-key>
<association-value>csrStock.alarmSizePrecision</association-value>
</association>
</aggregate-to-source-field-name-associations>
<type>oracle.toplink.mappings.AggregateObjectMapping</type>
</database-mapping>
<database-mapping>
<attribute-name>mCurrentSize</attribute-name>
<read-only>false</read-only>
<reference-class>com.cimsoft.lws.units.Measurement</reference-class>
<is-null-allowed>true</is-null-allowed>
<aggregate-to-source-field-name-associations>
<association>
<association-key>unitId</association-key>
<association-value>csrStock.currentSizeUnitId</association-value>
</association>
<association>
<association-key>y</association-key>
<association-value>csrStock.currentSize</association-value>
</association>
<association>
<association-key>yPrecision</association-key>
<association-value>csrStock.currentSizePrecision</association-value>
</association>
</aggregate-to-source-field-name-associations>
<type>oracle.toplink.mappings.AggregateObjectMapping</type>
</database-mapping>
<database-mapping>
<attribute-name>mLotSize</attribute-name>
<read-only>false</read-only>
<reference-class>com.cimsoft.lws.units.Measurement</reference-class>
<is-null-allowed>true</is-null-allowed>
<aggregate-to-source-field-name-associations>
<association>
<association-key>unitId</association-key>
<association-value>csrStock.lotSizeUnitId</association-value>
</association>
<association>
<association-key>y</association-key>
<association-value>csrStock.lotSize</association-value>
</association>
<association>
<association-key>yPrecision</association-key>
<association-value>csrStock.lotSizePrecision</association-value>
</association>
</aggregate-to-source-field-name-associations>
<type>oracle.toplink.mappings.AggregateObjectMapping</type>
</database-mapping>
However, here are the corresponding mappings in the exported Java file (with what it really should be manually inserted by me in comments):
     AggregateObjectMapping mAlarmSizeMapping = new AggregateObjectMapping();
     mAlarmSizeMapping.setAttributeName("mAlarmSize");
     mAlarmSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
     mAlarmSizeMapping.setIsNullAllowed(true);
     mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSizeUnitId", "unitId");
     mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSize", "y");
     mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSizePrecision", "yPrecision");
     descriptor.addMapping(mAlarmSizeMapping);
     AggregateObjectMapping mCurrentSizeMapping = new AggregateObjectMapping();
     mCurrentSizeMapping.setAttributeName("mCurrentSize");
     mCurrentSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
     mCurrentSizeMapping.setIsNullAllowed(true);
     mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSize", "alarmSize");
     mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizeUnitId", "unitId");
     mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizePrecision", "alarmSizePrecision");
     // should be: mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSize", "y");
     // should be: mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizePrecision", "yPrecision");
     descriptor.addMapping(mCurrentSizeMapping);
     AggregateObjectMapping mLotSizeMapping = new AggregateObjectMapping();
     mLotSizeMapping.setAttributeName("mLotSize");
     mLotSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
     mLotSizeMapping.setIsNullAllowed(true);
     mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizeUnitId", "unitId");
     mLotSizeMapping.addFieldNameTranslation("csrStock.lotSize", "currentSize");
     mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizePrecision", "currentSizePrecision");
     // should be: mLotSizeMapping.addFieldNameTranslation("csrStock.lotSize", "y");
     // should be: mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizePrecision", "yPrecision");
     descriptor.addMapping(mLotSizeMapping);
It appears that the actual Measurement descriptor is being modified accidentally as it's being exported, as you'll notice that the first mapping (for mAlarmSize) correctly maps the default "y" to "alarmSize", and then the next mapping (for mCurrentSize) instead of mapping "y" to "currentSize" maps "alarmSize" to "currentSize", and the next AOM maps "currentSize" to "lotSize" instead of "y" to "lotSize".
Thanks,
Greg

No one ever responded, so I'm commenting to bring it up again. It turns out that the error happens not just exporting to Java, but anytime the command-line project generation is used. If the Workbench is used to export either to XML or to a Java file, the file is generated correctly. It is not generated correctly if you try to do it from the commandline (e.g. from a build environment).
This has happened with 9.0.4.2 through the current 9.0.4.5.
Here are different ways I've tried doing it from the commandline, and they all generate the erroneous XML and Java files:
java oracle.toplink.workbench.external.api.JavaSourceGenerator inputMWP outputJava.java
and
java oracle.toplink.workbench.external.api.DeploymentXMLGenerator inputMWP outputXML.xml
which are recommended by the documentation. Also recommended by the documentation:
JavaSourceGenerator.generate( inputFile, outputFile )
and
DeploymentXMLGenerator.generate( inputFile, outputFile ).
From decompiling the management workbench to see what it was doing differently:
MWProject project = WorkbenchSession.instance().openProject( inputFile );
if ( doXML )
project.setProjectDeploymentXmlDirectory( directory );
project.setProjectDeploymentXmlFileName( filename );
project.exportDeploymentXml();
else
project.setProjectSourceRootDirectory( directory );
project.setProjectClassName( classname );
project.exportJavaSource( outputFile );
//Also tried plain old project.exportJavaSource(); which appears to actually do something different.
Any ideas? It looks like a bug to me, particularly that different java or XML deployment files are generated when run from the commandline versus run from the UI. Obviously, the commandline is very important because it is what the build system needs.
Thanks,
Greg

Story does not correctly export fdx file with scene numbers? Bug needs to be fixed.

Story does not correctly export fdx file with scene numbers? Bug needs to be fixed.

Okay, Even if i remove the scene numbers from Story and export the file to Final Draft 8. The format in incorrect. The "transitions" ex. CUT TO: are not in the correct allignment. Also there are numbers on each of the dialogues
Pretty much alot of the formatting is not the same. Spaces that break dialouge and action which are there in Story, are not converted over to Final Draft.
Please fix this as soon as possible.
thanks,
Rohit

Strange bug when exporting a spreadsheet to a pdf

I am using Numbers 3.5 on a brand new Mac with Yosemite and I think that I have found a bug. When I export a spreadsheet into either a pdf or excel file it works fine if I save it to my default location (Documents). But if I change to a subfolder within Documents before I do the export I get an error message that says "The file name.pdf doesn't exist!" (Where name is the filename that I have specified for the export.) It's as if Numbers is trying to open an existing file instead of exporting to make a new one. Any ideas on this?
Thank you,
Paul H.

I will reply to my own question. I spent some time with an Apple tech support person and at first I stumped him. Eventually he got it to work and he thinks that the key was to get my computer to reindex my file structure. He did that by creating another folder inside Downloads, exported to it OK, and then was able to export to my previously existing subfolders. Thank you Apple!

Bug: Temp files with 0-Byte size are not removed after PDF export

Post Author: chaplin
CA Forum: Exporting
When exporting to PDF through the CR-API (CRPE) the temporary files epfHHHH.tmp and ctmHHHH.tmp in the windows temporary path (with HHHH = hexadecimal number with 4 digits) are not deleted when they are 0-Byte in size - even after closing the application which called the CRPE-API. When HHHH reaches its limit (hex FFFF = dec 65535) the Crystal Reports DLLs are not able to create more PDFs - the export aborts with an error and the PDFs are 0-Byte in size.
This behaviour was tested/reproduced with Crystal Reports 8.5, but (as many other long-term bugs) might be also exist in later releases of Crystal Reports as well as on the other SDK interfaces.
KBase Article ID:2009412, Track ID: ADAPT00011016 and Escalation ID: 1472 describes a solution for this problem and Business Objects says that using Crxf_pdf.dll, version 8.6.0.108, dated 04/25/2002 or later solves the problem. We are using a newer one from 2003 (version 8.6.2.429) and still see this problem. It seems that 0-Byte-Files are ommitted from the deletion.
Does anybody know a workaround or solution for this bug?

Wendell,
This forum is for handling issues migrating from non-Oracle databases to Oracle databases.
As this is an Oracle to Oracle issue using SQL*Developer export it would be better to open a new thread in the SQL*Developer forum -
SQL Developer
There will be more people there who can help with this problem.
Regards,
Mike
Edited by: mkirtley on May 14, 2010 10:16 AM

Bug v4.0 - no input field for file name in export dialog

Hello,
I run a query, right click in the result grid and choose "Export". There is no input field to provide a file name. I can only export to the default file.
Version 4.0.0.13 on XP
Edit: Seems to be an issue with the settings (maybe those migrated from 3.2.2). When I install without migrating settings I get the full dialog. I will try some combinations and update this post.
Edit: I installed again without migration my settings. When I set the preferences manually I cannot reproduce the bug. Maybe some bug in the import for the preferences? Maybe it only happens on German XPs.
Regards
Marcus

Thank you, 5p given.
However this is what I execute and in my file chooser dialog the filename field is still blank.
ExampleFileFilter filter = new ExampleFileFilter();
    filter.addExtension("html");
    filter.addExtension("csv");
JFileChooser chooser = new JFileChooser(new File("REPORT_ONE_"));
    chooser.setDialogTitle( "Save Report" );
    chooser.setFileSelectionMode(chooser.FILES_AND_DIRECTORIES);
    chooser.setFileFilter(filter);
    int returnVal = chooser.showSaveDialog(this);
    ...It is in try-catch, no errors are returned.
Operating System: WindowsXP
Java Version: 1.3.1

In Indesign CS6 I export an artboard to TIFF with the sdk's funtion SnapshotUtilsEx- ExportImageToTIFF(iStream) and, the resulting file is one pixel too large in the X, leaving a transparent strip on one edge. Any idea if there is a bug in the sdk?

In Indesign CS6 I export an artboard to TIFF with the sdk's funtion SnapshotUtilsEx->ExportImageToTIFF(iStream) and, the resulting file is one pixel too large in the X, leaving a transparent strip on one edge. Any idea if there is a bug in the sdk?

An easy example to prove this bug of Indesing CS6: I create a psd with Photoshop CS6, with width 505 pixels, height 317 pixels and a resolution of 300 pixels per inch. This psd is placed on a page in InDesign CS6. Then I try to export it as a tiff with the functions:
fSnapshotUtilsEx->Draw(flags,fullResolutionGraphics,greekBelowPtSize,enableAntiAliasing,tr ansparencyQuality,abortCheck,pVPAttrMap,bDrawNonPrintingObjects);
and
SnapshotUtilsEx-> ExportImageToTIFF (iStream)
The resulting tiff has a width of 506 pixels (one pixel more in width). It will happen the same if we start with a width of 507 pixels, etc.
This error does not occur with Indesign CS5, nor Indesing CC.

BUG: Export bugs

Similar Messages

Maybe you are looking for