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

This article mainly explains "how to solve the problem of PDB entering restricted mode after patching 12cRAC". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to solve the problem of PDB entering restricted mode after 12cRAC patching".

I. description of the environment

Operating system: Redhat 7.4

Database: 12cRAC 4 nod

Number of PDB: more than 20

Total data volume: 30T

RU:DATABASE JAN 2020 RELEASE UPDATE 12.2.0.1.200114

II. Main problems

After Node 1 runs datapatch verbose, one of the PDB enters restricted mode.

Third, problem description

After running. / datapatch verbose on Node 1 at about 12:00 in the evening, then wait all the time. After 2 hours, the terminal begins to give feedback.

The feedback is: more than 20 PDB patches successfully No errors. The remaining three PDB and CDB$ROOT show an error with a wait timeout:

CDBROOT: ORA-04021: timeout occurred while waiting to lock object SYS.DBMS_STATSPDB1:ORA-04021: timeout occurred while waiting to lock object SYS.DBMS_SPACE_ADMINORA-04021: timeout occurred while waiting to lock object SYS.DBMS_STATSPDB2:ORA-04021: timeout occurred while waiting to lock object SYS.DBMS_SPACE_ADMINORA-04021: timeout occurred while waiting to lock object SYS.DBMS_SNAPSHOT_UTLPDB3:ORA-04021: timeout occurred while waiting to lock object SYS.DBMS_STATS

Then the database starts to datapatch the four PDB automatically. After waiting for about half an hour, CDB$ROOT, PDB1 and PDB2 show that patching succeeded and NO erros,PDB3 failed, and then the database automatically ends patching. The error message is as follows:

OACX:ORA-04021: timeout occurred while waiting to lock object SYS.DBMS_STATS

After / datapatch verbose, check the log of PDB3, and all the ORA- errors displayed are marked with IGNORED ERROR. Then show pdbs, check the status of PDB, and find that PDB3 has entered a restricted state.

When all PDB is turned off, only PDB3 is turned on. Try rerunning the PDB3 alone. / datapatch verbose:

Only Nothing to roll back Nothing to apply will be displayed

Check the DBA_REGISTRY_SQLPATCH view and show that the status of PATCH is WITH ERRORS (RETRYABLE)

IV. Problem analysis

At that time, the PDB was retyped and rolled back on the scene, and all showed Nothing to roll back Nothing to apply. Then mention SR, let the people of the original oracle factory come to the scene for analysis, they have never encountered this kind of situation, the suggestion is to re-run datapatch after entering startup upgrade, but it is still the same situation.

By viewing the specific log, the possible reason is that the SYS.DBMS_STATS is locked during the time when the database automatically collects statistics, and the PDB is relatively large, and there are a large number of full-text indexes, which leads to the failure of the PDB to patch.

V. temporary treatment

After PDB enters restricted mode, ordinary users cannot connect to the database and must be granted permission to restricted session to connect. In addition, all job can't run automatically. It is solved by manually granting all business users restricted session and crontab to run job.

VI. The final solution

Restore the PDB on the test library through a data pump, then try to lock the SYS.DBMS_STATS package by collecting library-wide statistics, and then run datapatch, which recreates the problem. Finally, after continuous testing, it is found that the problem can be fixed by forcing a patch and specifying the number of the patch pack.

/ datapatch-force-verbose-bundle_series 200114-apply 30593149-pdb PDB3 Thank you for reading, the above is the content of "how to solve the problem of PDB entering restricted mode after 12cRAC patching". After the study of this article, I believe you have a deeper understanding of how to solve the problem of PDB entering restricted mode after 12cRAC patching, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.