3.0 final: Bugs NOT fixed.

Hi,
Going over the bugs fixed document, at least these are NOT :
* 9844655      Table export DDL contains duplicates for index creation statements
* 8315759      Provide a Roles node
* 9434464      Display role node in connections view and in other users
Thanks though for the dozens that did!
K.

Sue,
any chance you can ask somebody from dev team to have a look at
3EA3/ 3.0 production - Schema browser
SqlDev 3.0 prod - Messages Log
SqlDev 3.0 prod - Disconnect Connections
I guess the whole team went in a small & deserved holiday as i don't see them around here after the final release :)
Thanks,
Dani

Similar Messages

  • ICal Alarm Editing Bug, not fixed yet in 10.5.3?

    Hi All Mac users,
    I have noticed this bug for quite a long while, which I cannot remember from when, but I think it was from around 10.3 or 10.4. I am used to it, and can deal with this since I know it. But, it still seems to persist even after updating to 10.5.3, and I have finally wanted to raise the issue up to this forum, in order to get it fixed, or obtain knowledge on how to fix this in my Mac.
    When you double-click or Command+I an event in iCal, the detail of the event shows up, and you click "Edit" button at the bottom to edit it. Most of my events' "Alarm" are set as "Alarm with Sound". To edit this, you click right next to "Alarm" to bring out the pull-down menu. You can change "Alarm with Sound" to "No Alarm", etc. Also, you will see a list of the latest settings you used at the bottom of this pull-down menu, with date, time and sound, etc. to choose from.
    *My Bug Phenotype:*
    ALL of the listed settings in this pull-down menu are EXACTLY *4 hours* (FOUR HOURS) later of what that actually sets and do. For instance, I set a new event at "2008/6/1 10:00, playing Susumi sound". This setting will newly show up in the for-mentioned pull-down menu. But, because of a bug or by an unknown reason, within the list it shows "2008/6/1 14:00, playing Susumi sound", showing the time 4 hours later. Continuously, if you edit another event's alarm setting, and choose the previous setting of erroneous "2008/6/1 14:00, playing Susumi sound" that shows up from the pull-down menu, the event you're editing will actually be set to "2008/6/1 10:00, playing Susumi sound", which is correct with the very original setting I first used, but then again it is 4 hours ahead of what you see in the pull-down list. Once set, all event will show the proper Alarm time set, and work at the correct timing. It seems that there's a bug just in this pull-down menu showing the previous settings, adding and showing 4 hours later to what it should be, but also correctly stores and set the original time.
    Does everybody understand what I tried to explain?
    Does anyone else have the same experience?
    Is this just me?
    Is it always 4 hours?
    Any way to fix this?
    Is this an iCal Bug, to be fixed?
    Thanks for your help in advance!
    Dr.MORO
    PS: Is there a way to directly (Online) way to tell (email, post, etc) this problem to Apple?
    PPS: I have used many different disk maintenance tool of most kinds, both free and commercial, but nothing has helped.

    Dr.MORO,
    1. Try refreshing the iCal plist file. Navigate to your Macintosh HD/Users/yourusername/Library/Preferences Folder, and find the com.apple.iCal.plist file. Drag that file to your desktop, log out/in or restart.
    2. What time do you have set in your iCal Time Zone Window?
    3. Have you tried to change your settings in System Preferences...>International>Formats>(Region:) (Dates) (Times)? Customize... Quit iCal before changing these settings, and repeat #1 above before opening iCal.
    4. Do you have a default time checked in iCal>Preferences...>General>Add a default alarm to all new events and invitations?
    5. Do you have "Turn on time zone support" checked in iCal>Preferences>Advanced?
    6. Do you have the proper "Time Zone" selected in System Preferences...>Date & Time?
    7. Are you syncing any of your computers?
    PS: Is there a way to directly (Online) way to tell (email, post, etc) this problem to Apple?
    Only through AppleCare, but your equipment is probably no longer covered. As far as I know you could still use AppleCare but it would cost an arm and a leg for phone support since you no longer have a contract. Do you have an Apple Store or Authorized Apple Provider nearby?
    PPPS?: This is my second post on this iCal issue this year, last time on May 30, 2008, but no one seems to care...
    Since Apple Discussions participation relies entirely upon other users for possible solutions, it is my guess that no one had the same problem or could offer a reasonable solution. Sorry to hear that you did not get a response to your previous post, but I care.
    ;~)

  • Major bugs not fix on iOS5 since iOS1

    Hei apple here are a few bugs that hasnt' been resolved and some new ones
    1. During a call, SMS ringtone will be blasted through the earpiece when an SMS is received
    2. During a call, regardless of incoming SMS or notifications, phone will vibrate(if silent with vibrate on) which is very annoying, couldn't u give a more subtle nofification or non at all like what Nokia and Sony erricson has been doing for so long.
    3. During an iMessage conversation, with iMessage app open, phone will keep on vibrating with every message receive(if vibrate is on) which is very annoying as im already reading the convo and its like vibrating on every iMessage text i receive( should have an option like whatsapp to turn on/off in-app notifications)
    4. Sometimes iOS5 notification centre do not log notifications and will errase the past 9 eventho i specify to log 10 most recent but it keeps on updating only to the latest one.
    5. Users werent aware that your photo editing is destrutive!!. Please have a non-destrutive photo editing
    Thanks. Please fix those bugs soon.
    p,s: For the 1st two bugs, come on apple even the most basic hanphones can do those and why not the most expensive and advance phone.

    This is sad they create one of most advance smartphones but cant get basic functions like this right. Thanks for your response

  • DMA bug not fixed in NI-DAQmx 7.3

    With the help of an NI Application Engineer I identified a fault with DAQmx at a beta version of DAQmx 7.2 whereby the PCI-MIO-16XE-50 does not work in DMA transfer mode. To get round this I was lent a 16XE-4 by the UK support team.
    I was told that 7.2 was too close to release to incorporate the fix, but it would be in the next release.
    Imagine my disappointment then when I downloaded 7.3, installed it, and found that the bug had actually not been fixed at all!!!!
    Why is this? When will it be fixed? NI UK want their loan card back!
    Jamie Fraser

    Unfortunately there isn't always the time/resources needed to implement certain changes to the software. I imagine the fix will be included in any future releases of NI-DAQ, but cannot give you a definitive answer as to when it will be addressed.
    Have you contacted the loans department or your local sales representative to try and arrange an extension to the loan in the meantime?

  • Safari 6.0.5 bugs not fixed...

    After entering my user/PW about five times in the developer bug report process, I got this We'll be back soon (don't know how long it's been down) so I am posting here...
    some of my websites are losing their filled colors in cells
    http://www.ahmium.org
    http://www.apapas.com
    for example, the text and cell becomes blank (hit the refresh button)
    if you click in the text and Select All the text and cell color returns
    this started only recently, I noticed with Safari 6.0.3 or so
    Safari is the only browser I notice that does it...

    STILL HAVING THIS ISSUE only on OSX 10.8.4, Safari 6.0.5, on two MacBook Pros (2011)
    do not have it on two Mac pros running 10.6x and 10.7x (or in any other web browser i've tested, including those running under 10.8.4)
    on apapas.com I just completely tore the home page apart, colored Table (vs Cells), removed content from each Cell one by one and problem persists...

  • 3.1EA2 bug still not fixed - Members of package body not listed in the tree

    Hi, I was working today with SQL Developer again and found that this bug is still not fixed even when it was reported more than 1 year ago!!!
    I did a quick search and found it here
    Package Body Tree not always showing
    The problem is when you expand the package specification or package body tree, not all members of the specification/body are listed. This is mostly observable in the package body, but it regards to the specification as well.
    Consider this case:
    CREATE TABLE EMP (
        ID               NUMBER(6,0) DEFAULT 0,
        NAME             VARCHAR2(20 BYTE) DEFAULT NULL,
        DEPT             VARCHAR2(20 BYTE) DEFAULT NULL,
        FUNCTION         VARCHAR2(20 BYTE),
        PROCEDURE        VARCHAR2(20 BYTE));
    CREATE TABLE LOOP (
      AREA    VARCHAR2(5),
      VALUE   VARCHAR2(2));
    CREATE OR REPLACE PACKAGE Test_Package1 AS
    gvc_const CONSTANT VARCHAR2(10) := 'xxx';
    PROCEDURE Test(p_RC OUT NUMBER,
                   p_ID IN NUMBER);
    END Test_Package1;
    CREATE OR REPLACE PACKAGE BODY Test_Package1 AS
    PROCEDURE Test(p_RC OUT NUMBER,
                   p_ID IN NUMBER)
    IS
    BEGIN
      --INSERT INTO EMP (ID, NAME, DEPT, PROCEDURE) VALUES (1, 'Tina', 'xxx', 'xxx');
      --INSERT INTO EMP (ID, NAME, DEPT, FUNCTION) VALUES (2, 'Jeff', 'xxx', 'xxx');
      --INSERT INTO LOOP(AREA, VALUE) VALUES('a','b');
      NULL;
    END;
    END Test_Package1;Compile the package specification and the body. Expand the spec + body in the tree. Uncomment any of the commented lines in the package body and compile the body again. Now expand the package body again and look what is displayed.
    Why? It is because SQL Developer handles words "Function", "Procedure" and "Loop" as keywords and according to them does the parsing.
    Another case
    CREATE OR REPLACE PACKAGE Test_Package1 AS
    gvc_const CONSTANT VARCHAR2(10) := 'xxx';
    TYPE Loop_rec IS RECORD(
      item1   LOOP.AREA%TYPE);
    PROCEDURE Test(p_RC OUT NUMBER,
                   p_ID IN NUMBER);
    END Test_Package1;Compile just this specification and try to expand it in the tree. Again, during parsing the package, SQL Developer takes the word "LOOP" into consideration and fails to parse the specification.
    There is exactly the same problem when you declare functions from external dll libraries in package body. Since there is no "END;" in this case, SQL Developer's parser fails...
    To me it seems you simply blindly took some keywords like "FUNCTION" and expect there will be some "END;" keyword corresponding with it.
    Can anyone have a look at this and finally fix it?

    Hi,
    Thanks for trying out SQL Developer 3.1 EA2 and providing a clear, reproducible test case for this issue. I logged an internal bug for it:
    Bug 13438696 - 3.1EA2: FORUM: CERTAIN KEYWORDS IN PKG BODY BLOCK MEMBERS FROM CONN VIEW TREE
    It seems the bug noted in the other forum thread you reference has been fixed, but really had nothing to do with problems discussed either here or there. That fix involved adding an Edit Body... item to the Package context menu in the Schema Browser, not displaying Package members correctly in the Connection view tree.
    Regards,
    Gary
    SQL Developer Team

  • Dear Apple, why not fixing basic bugs?

    I was sure that installing Leopard and using the new Mail.app I was finally able to use rich text format with my own font having all my recipients receiving the email message with the correct font.
    This is still not happening!! I can't believe it...
    So, why adding "300 new features" and not fixing this kind of annoying (and really old) bugs?
    I do have the most advanced operating system running, but I still have to "write the message, select all text, and set the font" everytime I send a new eMail.
    Any plan to finally fix this problem, forever?

    This is one:
    http://discussions.apple.com/thread.jspa?threadID=448785&start=0&tstart=0
    There is a bug mentioned there which I think has not been fixed in Leopard.
    If you try to use the font button in the new message pane to set a new font size with rich text for the same font which you have set as the Message Font in the Mail preferences, it will seem to work but in fact the html generated by Mail contains only the size and not the font name. So it will be displayed at the other end in whatever font the user has set for his default. The workaround for that has been to make sure these fonts are different.
    This also seems to happen with Leopard Stationery. If you create a custom stationery for Helvetica 36 while your Message Font in preferences is set to Helvetica, the stationery code will have no font name in it. The way around that is to create your custom Helvetica stationary while your Message Font is set to something else. That stationery can then be used later whatever your Message font is set to.
    Though totally different from the question of having a preference setting for a default outgoing font, this really is something Apple should fix.

  • IPad Safari Landscape innerHeight/outerHeight bug still not fixed in iOS 7.1.1

    iPad Safari Landscape innerHeight/outerHeight bug still not fixed in iOS 7.1.1
    No bug in Chrome or other third party browsers.
    When are Apple going to fix this bug? It's painful.
    more info here:
    http://stackoverflow.com/questions/19012135/ios-7-ipad-safari-landscape-innerhei ght-outerheight-layout-issue

    Tell Apple not other users.
    Use http://www.apple.com/feedback/ipad.html

  • LabVIEW 8.6.1 did not fix glaring Mixed Signal Graph bug :(

    I'm pretty dissapointed that NI has JUST NOW released 8.6.1 (more than 6-months after releasing the buggiest LabVIEW version, ever).  The Mixed Signal Graph bug still exists and is very annoying.  The visual bug occures when you add more than 1 plot on a mixed signal graph and then try to resize the legend.  The Y-Axis labels do not move appropriatly.  You really can't resize the legend with this bug.
    Where can I find a list of known bugs in LabVIEW and verify that this is in that list?  How can I add weight to this bug report so that NI will address it for the LabVIEW release?  How can I express to NI that I don't want LabVIEW 9 until they can fix all the problems in v8?

    LV_Pro wrote:
    One way might be to get in on the LabVIEW 2009 Beta, see if it fixes the problem, if not, report it while there may still be time to fix it.
    Not sure about the "buggiest version",  v2.5 had its share. Had to save your work every 1/2 hr. or risk loosing everything when you got the almost guaranteed "insane error" which always seemed to occure when you had done the most editing since your last save.
    Message Edited by LV_Pro on 02-10-2009 09:07 PM
    The OP obviously never had to work withLabVIEW versions prior to 5.1. 
    And while 8.6 had a few nagging bugs including visual ones it is actually quite stable and good. No comparison with 8.0 for instance or even 8.0.1
    Nickerbocker wrote:
    I'm pretty dissapointed that NI
    has JUST NOW released 8.6.1 (more than 6-months after releasing the
    buggiest LabVIEW version, ever).  The Mixed Signal Graph bug still
    exists and is very annoying.  The visual bug occures when you add more
    than 1 plot on a mixed signal graph and then try to resize the legend. 
    The Y-Axis labels do not move appropriatly.  You really can't resize
    the legend with this bug.
    Where can I find a list of
    known bugs in LabVIEW and verify that this is in that list?  How can I
    add weight to this bug report so that NI will address it for the
    LabVIEW release?  How can I express to NI that I don't want LabVIEW 9
    until they can fix all the problems in v8?
    You just did! But unless you are a site with several 1000 LabVIEW licenses you will not outweigth those other customers who do have that many licenses and do want more features as soon as possible rather than an annoying graph display bug getting fixed.
    Rolf Kalbermatter
    Message Edited by rolfk on 02-11-2009 10:02 AM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • [10.7.1] Not fix bug login screen!

    The latest update (10.7.1) does not fix the bug on the login screen. There is still need to disable the 'automatic gearbox graphics card'!

     

  • HT4589 Final Cut X 10.0.5 utube update not fixed

    Final cut version 10.0.5 update "Allows for YouTube uploads longer than 15 minutes" is not fixed
    Advice on how to resolve is appreciated.
    Jimbo R.

    Hi Jon.
    Thanks for your help. I´ve seen a post telling the same thing. I finally let Final cut pro X about 8 hours and it finally opened the project, but i couldn´t make anything with it. Tried to export xml and import it to another project without success. The problem persists. So i also tried to cut some parts from the project and is still the same. For each test we must wait 8 hours and it´s not reasonable time to test things. I just sent the project to apple engineers, so if is there any solution i will post in here.
    Thanks.

  • Restart fixes BadPaddingException: Given final block not properly padded ??

    (I have seen quite a few posts on this and other forums regarding BadPaddingExceptions, however all of them seem to be easily reproducible. This one is random and has been impossible for us to reproduce in a test environment.)
    Anyone have any idea why we might encounter this problem during decryption (e.g cipher.doFinal(<base64 encoded byte[]>) ) , but restarting the JVM clears it up?
    Once it starts happening, all decryption fails with "BadPaddingException: Given final block not properly padded"
    and once we restart the JVM, all is well again.
    We are currently running j2sdk1.4.2_04 and are using PBEWithMD5AndDES.
    Any help is much appreciated,
    -Marc

    I have plenty of ideas for what is wrong but why should I enumerate them. It would be much quicker if you posted (using [code] tags) your encryption and decryption code.
    Edited by: sabre150 on Nov 29, 2007 12:09 PM

  • 4.2.1 Does Not Fix" Crash-on-screen saver" bug or metadata issues

    ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
    You have to set screen saver to "Never" to prevent crashing.
    No one checks these things?
    Message was edited by: Mike Kwiatkowski

    Mike Kwiatkowski wrote:
    ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
    Metadata issues still hosed.
    Not seen the screensaver issue.
    Personally I think this update was a patch to fix the DVI flickering issues that rendered the device unusable for many people - other annoyances can be fixed later but we better keep reminding them:
    http://www.apple.com/feedback/appletv.html

  • ACR 7.x known bugs and fixes

    Since Adobe stopped supplying Camera Raw downloads, I've noticed that it's become harder to track bugs and fixes. Hopefully, someone here can put me straight on the current state of play.
    Can anyone summarise the well-known problems with version 7, and when they were fixed (or are still ongoing)? Is there a 'changelog' somewhere? What is/are the main outstanding issues at the moment?
    Unfortunately, I'm getting to that age where my short–medium term memory isn't very good at retaining this sort of information, so it's good to have it written down!

    Jeff,
    I have been dealing with this since November. Steve G knows about it but hasn't had time to do anything. Here's the deal...I am on Windows 7 and Photoshop CS6. I shoot with a Canon 7D and G11.  I do all my initial work in the metadata template...my own info, description, keywords, location, etc. etc.  This creates an .xmp file. When the update from RAW 7.2 to 7.3 came through in November, I downloaded it, as I have all other updates. Then, suddenly, all images in folders with RAW files that had ANY metadata applied, would regenerate endlessly. This only happens with RAW files, not with folders containing jpegs or tifs.
    I tried resetting preferences. I tried creating new folders. I have asked if this problem is seen with Nikon RAW files and I'm not sure there has been an answer. I think people have recreated this even with DNG files tho I am not sure. I do know that someone in Adobe has recreated it.
    I then discovered that previous .8bi folders were no longer readily available. Getting to one is way, way, way above my ability and involved all kinds of ridiculous backflips but I finally got one. Then followed a solid week of me trying replace the 7.3 .8bi file with the 7.2. Of course, with no instructions, I was putting the wrong file in the wrong folder (32 bit and 64 bit). When I finally got THAT straightened out, it still didn't work. It took someone at Adobe taking over my computer to successfully revert to 7.2.
    I lost hours and days of work time trying to deal with this. Meanwhile, should I buy a new camera, I won't be able to see my own RAW CR2 files and will, instead, have to convert to DNG, which, frankly, I find to be a royal pain. Am I peeved. You bet I am. I've been asking, pleading, begging for something to be done since November. Some thoughtful soul suggested I try updating to 7.4 to see if it fixed the problem (the 'fixed problems' listed for 7.4 does NOT mention the recalibration). You can understand, after the problems I had in November, why I will NOT do this until I am absolutely sure the current, latest update has fixed my problem. And I will NOT spend another two hours on the phone with adobe alleged tech help to finally get someone in India who doesn't know what I am talking about. This forum has been far more helpful but please underestand, I am an old school film photographer who has had my share of problems understanding this digital stuff and mucking around with the basic technology of my computer only leads to horrifying outcomes for me.
    Jeff, are you with Adobe? Can you look into this?

  • Bug CSCun42967 fixed: ISE 1.2 : SNMP process stops randomly

    As of June 9th, the status of this bug is "Fixed" with "Known Affected Releases" being 1.2(0.899), which is the one we are running.
    Known Fixed Releases is (0) and then there is a link to the download area where I can download an update to 1.2.1. The release notes does not mention bug "CSCun42967"
    Does anyone know if this bug has been fixed?

    Hi,
    I just ran into the same issue.
    I would assume that if it was fixed in 1.3 it would be mentioned in the release notes as resolved caveats. Can anyone confirm the problem is fixed in 1.3?
    Soren, have you upgraded and is the issue resolved?
    Thank you :)

Maybe you are looking for