Open a terminal window. From the directory you unzipped the files to, execute the following command to create a data dictionary corruption

./corr_setup.sh

Open a browser and enter the following URL:

http://<hostname>:1158/em

Enter sys as the username, specify the password oracle, select SYSDBA for Connect As and then click Login.

From the home page, scroll down and under Related Links, select Advisor Central.

Select the Checkers tab.

Click Dictionary Integrity Check.

Enter DicoCheck1 for the Value of the Parameter Run Name and click OK.

The check ran successfully. To view the details, select the DicoCheck1 Run from the list and click Details.

You can see some data corruption. In particular, you see the following finding: "SQL dictionary health check: invalid column number 9 on object TAB$ failed". This corresponds to a row in the TAB$ that references HR.OBETABLE. Click the Database breadcrumb.

From the home page, review the Alerts section. You see that you have a new critical alert (Data Failure) for the previously detected corruption.

Switch to your terminal window and executed the following commands:

sqlplus / as sysdba
alter system flush shared_pool;
alter system flush buffer_cache;
select * from hr.obetable;

Notice that you receive a end-of-file on communication channel error. This means that something is definitely wrong. You will now investigate the problem.

Switch back to Enterprise Manager and notice that you have an Active Incident in the Diagnostic Summary section of the Home page. Select the number link.

On the Support Workbench Problems page, you should see a new Active Incident whose Description is similar to ORA 7445 [qcstda()+515]. Select the + to expand the details for the problem.

Click the incident number.

The Incident Details page appears. Make note of the incident number. In the Application Information section, you see that the statement for SQL Text 'select * from hr.obetable' is what caused the incident. You also see two dump files generated.

On the Problem Details page, In the Investigate and Resolve section, select Quick Package.

On the Create New Package window, select No for Send to Oracle Support.

When the page is refreshed, click Next.

The incidents to be packaged are listed, click Next.

The manifest details are shown. Click Next.

Make sure Immediately is selected and click Submit.

The package is being generated.

The package file has been successfully generated. Click OK.

To view the package, in the Summary section, click Yes under Packaged.

Select the file that was generated and click View.

On the Packaging Details page, select the Files tab.

The list of files included in the package are displayed. This package can now be sent to Oracle Support for further analysis.

Switch back to your terminal window and execute the following script:

./corr_fix.sh

Switch to Enterprise Manager and select the link next to Problems in Package.

Select the checkbox in front of the problem and click Close.

To confirm, click Yes.

The incidents have been closed.