OraTransplant

Metalink bug statuses

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

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