Which statements are true regarding the creation of an incident package file by using the EM Workbench
Support? (Choose all that apply.)
A.
You can add or remove the trace files to the package.
B.
You can create the incremental incident package ZIP file for new or modified diagnostic information for the
incident package already created.
C.
You can add SQL test cases to the incident package.
D.
You cannot create an incremental incident package when the physical files are purged from the ADR.
Explanation:
About Quick Packaging and Custom Packaging
The Enterprise Manager Support Workbench provides two methods for creating and uploading an incident
package: the quick packaging method and the custom packaging method.
Quick Packaging—This is the more automated method with a minimum of steps, organized in a guided
workflow (a wizard). You select a single problem, provide a package name and description, and then schedule
upload of the package contents, either immediately or at a specified date and time. The Support Workbench
automatically places diagnostic data related to the problem into the package, finalizes the package, creates the
zip file, and then uploads the file. With this method, you do not have the opportunity to add, edit, or remove
package files or add other diagnostic data such as SQL test cases. However, it is the simplest and quickest
way to get first-failure diagnostic data to Oracle Support. Quick packaging is the method used in the workflowdescribed in “Investigating, Reporting, and Resolving a Problem”.
Note that when quick packaging is complete, the package that was created by the wizard remains. You can
then modify the package with custom packaging operations at a later time and manually reupload.
Custom Packaging—This is the more manual method, with more steps. It is intended for expert Support
Workbench users who want more control over the packaging process. With custom packaging, you can create
a new package with one or more problems, or you can add one or more problems to an existing package. You
can then perform a variety of operations on the new or updated package, including:
Adding or removing problems or incidents
Adding, editing, or removing trace files in the package Adding or removing external files of any type
Adding other diagnostic data such as SQL test cases
Manually finalizing the package and then viewing package contents to determine if you must edit or remove
sensitive data or remove files to reduce package size.
You might conduct these operations over a number of days, before deciding that you have enough diagnostic
information to send to Oracle Support.
With custom packaging, you create the zip file and request upload to Oracle Support as two separate steps.
Each of these steps can be performed immediately or scheduled for a future date and time.
Select the Full or Incremental option to generate a full package zip file or an incremental package zip file.
For a full package zip file, all the contents of the package (original contents and all correlated data) are always
added to the zip file.
For an incremental package zip file, only the diagnostic information that is new or modified since the last time
that you created a zip file for the same package is added to the zip file. For example, if trace information was
appended to a trace file since that file was last included in the generated physical file for a package, the trace
file is added to the incremental package zip file. Conversely, if no changes were made to a trace file since it
was last uploaded for a package, that trace file is not included in the incremental package zip file.