在MOS中查看Bug database，会看到每个bug都有自己的status，那么这其中常见的status有哪些，又都分别是什么含义呢？
我们可以通过MOS中的Advanced Search功能查找特定状态的Bug，比如有哪些是已经确认为Bug移交到研发部门但是还没有补丁写出来的？
比较常见的status有以下这些。而这些状态也基本上表明了一个bug从接收到解决的流程。
10 – Description Phase
Development is requesting more information. 研发部门需要更多信息。
16 – Support bug screening
Bug is being reviewed by our Bug Diagnostics group. Bug诊断小组正在评估。
11 – Code Bug (Response/Resolution)
Bug is being worked by Development. 已经确认为Bug，研发部门正在尝试修正。
30 – Additional Information Requested
Bug is being worked by Support and/or more information was requested by Development. 技术支持已经参与工作，不过研发部门正在要求更多信息。这意味着补丁已经写完，正在让技术测试去测试是否有效。研发部门从现有的bug描述和上传的log截图等信息中还无法确定问题，要求bug的提交者提供其他更加详细的信息。
37 – To Filer for Review/Merge Required
Bug has been fixed but the patch will be merged into the next patchset. Bug已经修正但是补丁在下一个补丁集中一起发布。
80 – Development to Q/A
Bug is being regression tested for future release. Bug被移交到质量控制部门做回归测试。
81 – Q/A to Dev/Patch or Workaround Avble
Patch released via Metalink. 补丁发布到Metalink上。
90 – Closed, Verified by Filer
Bug has been fixed and is closed. Bug已经修正并且关闭。
91 – Closed, Could Not Reproduce
Bug is closed as not reproducible. Bug被关闭因为无法重现。
92 – Closed, Not a Bug
Bug is closed as not a bug (not reproducible or setup issue). Bug被关闭因为这不是个bug，可能是因为无法重现也可能仅仅是因为客户的安装问题。
93 – Closed, Not Verified by Filer
Bug has been fixed and is closed. Bug已经修正并且关闭。
95 – Closed, Vendor OS Problem
Bug is closed as an OS problem. Bug被关闭因为这是操作系统问题。
96 – Closed, Duplicate Bug
Bug is closed as a duplicate bug. Bug被关闭因为已经有重复的bug已经被报告了。
其中10, 16表示技术支持部门（也就是Oracle的OSS）提交了一个bug，但是研发部门还没有确认和接受它是一个真正的bug。
11表示bug已经移交到研发部门，研发人员正在尝试修正，还在工作过程中，目前为止还未修正。
80, 81, 90 , 93表示bug已被修正，补丁可以下载或者请求下载了。
