Metalink bug statuses

14 December 2005 at 15:46 CET | In Oracle |

Today a support engineer at Oracle closed one of my low severity TARs. A new bug was filed for this TAR. Since it is a low severity TAR it is closed and I can monitor the bug myself on Metalink.

The support engineer gave me a list of statuses that would be visible on Metalink. This is a very handy list, since I keep wondering what all the bug statuses mean on Metalink.

Here it is:

Code Phase Description
10 Description Phase Development is requesting more information.
16 Support bug screening Bug is being reviewed by our Bug Diagnostics group
11 Code Bug (Response/Resolution) Bug is being worked by Development
30 Additional Information Requested Bug is being worked by Support and/or more information was requested by Development.
31 Could not reproduce, to filer Development genuinely can’t reproduce a bug using the available information
37 To Filer for Review/Merge Required Bug has been fixed but the patch will be merged into the next patchset
74 Closed, verified by QA Bug has been fixed, verified by QA and is closed (similar to 90)
80 Development to Q/A Bug is being regression tested for future release
81 Q/A to Dev/Patch or Workaround Avble Patch released via Metalink
90 Closed, Verified by Filer Bug has been fixed, verified by Support or Development and is closed (similar to 74)
91 Closed, Could Not Reproduce Bug is closed as not reproducible
92 Closed, Not a Bug Bug is closed as not a bug (not reproducible or setup issue)
93 Closed, Not Verified by Filer Bug has been fixed and is closed
95 Closed, Vendor OS Problem Bug is closed as an OS problem
96 Closed, Duplicate Bug Bug is closed as a duplicate bug

Update 17-dec-2005: Added status 31 and 74 as commented by Brian Duff

Update 17-dec-2005: I also found an official help page at Metalink explaining the statuses

10 Comments

TrackBack URI

  1. Hopefully you’ve checked back with oracle that you are allowed to publish this information - it might be considered internal as it was taken from metalink …
    Just a hint, probably it’s no issue …

    Comment by Martin — 14 December 2005 #

  2. You probably have a point there. I guess it’s not confidential, but asking it would have been the right thing to do. I’ll ask them anyway just to be sure.

    Comment by Wilfred — 14 December 2005 #

  3. I added a question to the TAR asking Oracle support if they object to publishing this information. They closed the TAR without further comments. So, I guess they don’t mind publishing it.

    Comment by Wilfred — 14 December 2005 #

  4. Thank you for posting this! This’ll be a great help, not just when I’m working TARs with an analyst, but also when I’m searching through open bugs on MetaLink.

    Comment by Natalka Roshak — 14 December 2005 #

  5. Status 10 usually means that the bug hasn’t been reproduced by development yet or investigated by BDE. This is slightly different from status 30, which usually means the bug is reproducable but some additional information is needed before it can be fixed. There’s also a status 31, which is “Could not reproduce, to filer”. Development will set a bug to this status if they genuinely can’t reproduce a bug using the available information.

    Not sure if it’s visible on metalink, but there’s also status 74, “Closed, verified by QA”. This status is similar to status 90. The main difference is usually that the fix for a status 90 bug was verified by the developer or support engineer who originally filed the bug. Fixes for status 74 bugs were verified by Quality Assurance. In JDeveloper, most of our bugs end up in 74 as the final state.

    (there are a whole bunch of other statuses, many of which I’ve never seen used before, but I’m not sure how many of these are visible in metalink).

    Comment by Brian Duff — 15 December 2005 #

  6. You have many other bugs missing.

    E.g what is bug 36, what is bug 52??

    Comment by Ajai — 25 February 2008 #

  7. Ajai,

    Back in 2005 the list of statuses was not published by Oracle, and these were the only statuses I could get my hands on. Later, Oracle published the complete list and there is a link to it at the end of the article.

    Comment by wilfred — 29 February 2008 #

  8. The “official help page at Metalink explaining the statuses” is no longer available, I get a 404. But then it’s nice to have your list still, since I can’t find it on MetaLink itself for some reason.

    Comment by Jacob — 16 December 2008 #

  9. I found a much more complete list here:

    http://achatzia.blogspot.com/2007/06/metalink-statuses.html

    Comment by Jacob — 9 January 2009 #

  10. And there is also this Metalink Note that is the same/similar to the mentioned Metalink help page in the original post:

    Subject: Oracle Bug Status Codes, Descriptions and Usage
    Doc ID: 365605.1 Type: BULLETIN
    Modified Date : 03-JUL-2009 Status: PUBLISHED

    Comment by Erik Ykema — 10 September 2009 #

Sorry, the comment form is closed at this time.

Powered by WordPress with Pool theme design by Borja Fernandez.
Entries and comments feeds.