Tuesday, June 23, 2009

Oracle Bug Status Codes, Descriptions and Usage

Status Description Usage
10 New, not ready for development Use to file a bug without all the needed information (for instance, trace files from the customer), to inform Development that a bug will soon become Status 11.
11 Assigned to Development Use to indicate that the bug is ready for Development, or to indicate that additional required information has been provided for a Status 30 bug.
12 To External (User Group) Review Use to send an enhancement to Oracle User Group review.
13 Assigned to a Technical Writer Use to request documentation enhancement.
14 Bug Assigned to Solution Partner Use to keep track of bugs which are fixed by third party companies.
15 To Internal (Oracle) Review Use to send an enhancement to Oracle's product managers.
16 Support bug screening Used by BDE to pre-sort well-formed bugs before development start fixing.
19 Approved for User Group Voting Use to include the enhancement to the report for the User Group.
20 To Requestor, Need More Information Use to request more information from the filer.
21 Cost Required, To Development Use to request a product enhancement cost estimate from product managers.
22 Approved for Future Release Use to send an enhancement to product managers for scheduling.
23 Scheduled for Future Release Use to send an enhancement to Development to be included in a release.
30 More Info Required. To Filer Use to request more information from the bug filer.
31 Could Not Reproduce. To Filer Use to notify filer that bug cannot be reproduced
32 Not a Bug. To Filer Use to notify filer that bug was not valid
33 Suspended, Req'd Info not Avail Use to notify filer that the work has been suspended until info is received.
35 To Filer for Review Use to request verification of the bug fix from bug filer.
36 Duplicate Bug. To Filer Use to respong to filer that the bug is a duplicate.
37 To Filer for Review/Merge required Use to request verification of the bug fix from bug filer and to request that integration merge the fix into the base code.
39 Approved, waiting for codeline to open Use to indicate that a backport has been approved and is waiting for codeline to open. When the codeline is opened, status will be changed to 40.
40 Waiting for the base bug fix Use to show that bug is waiting for another bug to be fixed. 43 Product/Platform , to Filer Use to indicate that the bug will not be fixed and that filer should approve by updating the bug to Status
83: Closed, Product/Platform .
44 Not Feasible to fix, to Filer Use to indicate that the bug will not be fixed and that filer should approve by updating the bug to Status
84: Closed, Not Feasible to Fix. (Use only when the product or platform is near the end of its lifecycle or when the fix would require a major re-write).
45 Vendor OS Problem, to Filer Use when an operating system problem is the cause of the bug, to indicate that, following verification, bug filer should update to Status 95.
51 Support approved backport - to Dev Use to approve a backport (GPU=B). This status is reserved for use by Worldwide Support only.
52 Pending approval by PL (Product Line) Use to approve a backport and to indicate that a porter can begin to work on the bug. This status is reserved for use by porting managers.
53 Backport/Patchset Req Rejected Use to notify filer that the request to backport this bug is rejected.
60 CM: Awaiting Promote Configuration Management : Use to indicate that the fix has been developed and is awaiting promotion to the TEST environment.
66 CM: Awaiting Deployment Configuration Management : Use to indicate that the fix has been tested and is awaiting a patch or release.
70 Closed, data fix, cause - user error Applications : Use when the user performed an illegal operation, such as directly updating data using plsql. This includes bad data being populated by custom code. This caused the data to be inconsistent and required that the data be fixed using a data fix script.
71 Closed, data fix, cause - data import Applications : Use when bad data was imported into the system, either via automated batch load, or as the result of data conversion during the installation of the product. This caused the data to be inconsistent and required that the data be fixed using a data fix script.
72 Closed, data fix, cause - code error Applications : Use when bad data was populated into the database due to an error in Oracle supported software. This caused the data to be inconsistent and required that the data be fixed using a data fix script.
73 Closed, data fix, cause - unknown Applications : Use when bad data was found to exist in the customers database, which required that the data be fixed using a data fix script. The root cause was never determined.
74 Closed, Verified by QA Applications : Use to close bugs verified by Quality Assurance team. 80 Development to Q/A Use to indicate that a fix is available, but the code has not passed Quality Assurance. 81 Q/A to Dev/Patch or Workaround Available Use to indicate that a patch or workaround is available, but the code has not passed Quality Assurance.
82 Q/A to Enhancement Evaluation Use to indicate that a product enhancement has been implemented, but the code has not passed Quality Assurance.
83 Closed, Product/Platform Use to close a bug that was not fixed because of product or platform obsolescence.
84 Closed, not feasible to fix Use to close a bug that was not fixed because the fix was not feasible.
87 Fix verified/Merge Required Use to indicate that the fix has been verified, but the code has not passed Quality Assurance, and to request that integration merge the fix into the base code.
89 Q/A to Technical Writing Use to indicate that a documentation bug has been fixed, and is available for technical review.
90 Closed, Verified by Filer Use to close a bug that has been fixed and verified .
91 Closed, Could Not Reproduce Use to close a bug that development could not reproduce.
92 Closed, Not a Bug Use to close a bug that was not a bug.
93 Closed, Not Verified by Filer Use to close a bug that could not be verified by the bug filer. 94 Closed, Duplicate Enhancement Use to close a bug that is a duplicate of another enhancement request.
95 Closed, Vendor OS Problem Use to close a bug that is a vendor operating system problem. 96 Closed, Duplicate Bug Use to close a bug that is a duplicate of another bug.
97 Suggestion Rejected Use to indicate that a suggestion has been rejected.
98 Suggestion Implemented Use to indicate that a suggestion has been implemented.
99 Closed, Documentation Bug Fixed Use to close a documentation bug

No comments: