ORA-600 Troubleshooting Tool

ORA-600 Troubleshooting Tool

 

 

 

The ORA-600 Troubleshooting tool will provide recommendations to resolve ORA-600 errors by analyzing uploaded files. When a known solution is available, the tool will display the symptoms and causes which can lead to the issue and one or more suggestions for resolving the issue.  If a known solution is not available, the tool will display the knowledge document which explains the ORA-600 error and provides a list of resolved bugs for the ORA-600 error.

Benefits of using the ORA-600 Troubleshooting tool:

  • Analyzes uploaded files to provide recommendations when a known solution is available
  • When a known solution is unavailable, points to knowledge document for the specified ORA-600 error
  • Troubleshooting report can be saved for later use
  • Create SR option available which will automatically populate many of the SR fields

Accessing the ORA-600 Troubleshooting Tool

Click here to access the Troubleshooting Tool (Standalone Version).

  • Note: The Troubleshooting Tool can also be accessed during SR creation when the "ORA-600" error AND the arguments is entered in the "Error Codes" field. This is referred to as the "Create SR Version" below.
  • Note: Some tool features are only available with the Standalone Version and are designated as "Standalone Version Only" below.

Using the Troubleshooting Tool

 
Troubleshoot a New Issue (Standalone Version Only)

Describe Problem page

  • Choose the “Troubleshoot a new issue” option.

Upload Files page

  • In order to troubleshoot a new ORA-600 issue you will need to upload the requested files.
  • See the “File Upload Options” section below for file options.
  • Choose the option which is appropriate for the type of file you have available to upload.
  • Save these files to a safe place in case they are needed for future use.

Review Recommendations page

  • Review the solution
    • Issue section
      • Lists the symptoms and causes which can lead to the error. 
      • Lists the symptoms and causes which have been identified from your uploaded files. 
    • Resolution section
      • Lists the solutions you can use to resolve the issue.
  • Save the report
    • Use this option to save the report for future use.
    • Enter a name for the report and click the “Save” button.
    • Refer back to the report any time while you are implementing the recommended solutions. 
    • Save the files used for this report to a safe place in case the solutions do not resolve the issue and you need to log a SR.
  • Provide feedback
    • Let us know if the recommendation provided was helpful.
    • Provide any feedback which could help us improve the tool.
    • Click the "Submit Feedback" button once you have completed the fields.
  • Create a SR
    • When logging a SR, the details from the files uploaded will be used to automatically populate many of the fields in the SR.
    • Note: If your issue is not resolved and you saved the troubleshooting report, you will need to re-upload the files before creating a SR when you return.
    • Note: If you have already created an SR for this saved session then you will not be able to create another SR. Please review your SR list.
  • Print Recommendation.
    • Use the printer icon to print the recommendation.
  • Email recommendataion.
    • Use the mail icon to email the recommendation.
 
Troubleshoot a New Issue (Create SR Version Only)

Upload Files page

  • In order to troubleshoot a new ORA-600 issue you will need to upload the requested files.
  • See the “File Upload Options” section below for file options.
  • Choose the option which is appropriate for the type of file you have available to upload.
    • Update the fields with the files to upload and click the "Upload" button.
    • Once the upload is complete, click the "See Solution" button.
  • Save these files to a safe place in case they are needed for future use.

Review Recommendations page

  • Review the solution
    • Issue section
      • Lists the symptoms and causes which can lead to the error. 
      • Lists the symptoms and causes which have been identified from your uploaded files. 
    • Resolution section
      • Lists the solutions you can use to resolve the issue.
  • Create a SR
    • When logging a SR, the details from the files uploaded will be used to automatically populate many of the fields in the SR.
  • Print Recommendation.
    • Use the printer icon to print the recommendation.
  • Email recommendataion.
    • Use the mail icon to email the recommendation.
  • Solved my problem
    • Please let us know if the solution solved your issue
 
Review a Troubleshooting Report (Standalone Version Only)

From the Describe Problem page, you can choose to review a troubleshooting report that was saved during a previous session. 

  • Choose the “Review a troubleshooting report” option
  • Choose the name of the report from the drop down list.

File_Upload_Options

In order to troubleshoot a new issue involving the ORA-600 error set, you will need to upload the requested files. The following combinations of files can be uploaded:

  • TFA output with errors
  • Incident Packaging Service (IPS) package or any archive file containing trace files with the error
  • Alert log AND Incident dump file (Release 11g or higher)/Trace file (Prior to Release 11g)

Consider the following when uploading files:

  • For all databases 11G onwards, TFA is the recommended approach and will gather all relevant diagnostics for the problem using one command:
  • For all 10G or lower databases or if you choose not to use TFA, then follow the instructions in Document 2165632.1.
    • Ensure that the trace file being uploaded contains the error
      • Upload the trace file from the instance that is encountering the error
      • Use the alert log to determine which file to upload
      • For Oracle Database versions 9.0 to 10g, upload the regular trace
      • For Oracle Database version 11i and higher, upload the incident trace file
    • The alert log should contain the following when possible:
      • The ORA-600 error in question
      • Startup which occurred prior to the ORA-600 error
    • The IPS file should contain the following:
      • alert log with the ORA-600 error
      • trace file with the error
posted @ 2020-08-13 22:02  耀阳居士  阅读(143)  评论(0编辑  收藏  举报