Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to analyze the patch problem of oracle 11.2.0.4. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Just after the Spring Festival, before going to work, a customer called and said that the database could not be started because of a power outage on the host computer.

Send an error report as follows:

ORA-00704: bootstrap process failure

ORA-00704: bootstrap process failure

ORA-00600: internal error code, arguments: [16703], [1403], [20], []

Oracle lost power unexpectedly and has never seen this mistake.

After repeated analysis, it is found that there is no problem with the control file. The important data dictionary of system tablespace system is corrupted.

But the judgment was caused by a power outage. Anyway, there is no way to recover the data. Users are advised to accept the results of data corruption.

Later, when I found two posts with the same problem on the Internet, I knew the seriousness of the problem.

It turns out that the 11.2.0.4 media we have has been tampered with.

On the linux platform, use the md5sum command to view the p13390677_112040_Linux-x86-64_1of7.zip file. If the last four digits of the value are 124173, it is tampered with, and the last four digits of the correct version should be F58F28.

The tampered version creates a trigger. This trigger is triggered every time the database is started. The database creation time is detected when triggered, and if the creation time exceeds 300 days, the core data dictionary table is deleted. Make the database down immediately, and then start up will not be able to open, reported to ORA-00704 and ORA-00600, with my own technical level, basically unable to recover data.

Select * from v$version

Check that if it is 11.2.0.4, check immediately to see if there is any tampered trigger.

Select text from all_source where type='TRIGGER' AND NAME='DBMS_SUPPORT_DBMONITOR'

Delete triggers, stored procedures, and packages using the following statement

Drop TRIGGER DBMS_SUPPORT_DBMONITOR

Drop PROCEDURE DBMS_SUPPORT_DBMONITORP

Drop PACKAGE DBMS_SUPPORT

About oracle 11.2.0.4 patch how to analyze the problem is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.