In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)05/31 Report--
This article mainly introduces "how to solve the ORA-65294 error after PDB recovery from different machines". In daily operation, I believe many people have doubts about how to solve the ORA-65294 error after PDB recovery from different machines. Xiaobian consulted all kinds of information and sorted out simple and easy operation methods. I hope to help you answer the question of "how to solve the ORA-65294 error after PDB recovery from different machines"! Next, please follow the small series to learn together!
I. Description of the problem
ORA-65294 error occurs when PDB is inserted into another CDB after PDB is recovered from different machines:
SQL> CREATE PLUGGABLE DATABASE SDC_TEST USING '/home/oracle/SDC.xml' NOCOPY TEMPFILE REUSE;CREATE PLUGGABLE DATABASE SDC_TEST USING '/home/oracle/SDC.xml' NOCOPY TEMPFILE REUSE*ERROR at line 1:ORA-65294: PDB's compatible parameter value (12.2.0.1.0) is higher than CDB'scompatible parameter value (12.2.0.0.0).
II. Problem Analysis
When a backup group colleague restores CDB by using RMAN on a different machine, the compatible specified by the pfile parameter used is 12.2.0.1, resulting in compatible=12.2.0.1 for the restored PDB. The default compatible for 12c is 12.2.0, i.e. 12.2.0.0.0. Therefore, the compatible value of PDB is larger than that of CDB.
$ oerr ora 6529465294, 00000, "PDB's compatible parameter value (%s) is higher than CDB's compatible parameter value (%s). "// *Cause: An attempt was made to plug in or clone from a pluggable database// with a higher compatible parameter value than the compatible// parameter value of the multitenant container database (CDB).// *Action: Create a pluggable database with the same or lower compatible// parameter value of the multitenant container database.//
III. Solutions
Because the compatible parameter cannot be modified, we cannot do it the way the alter system does.
You can manually modify the parameters of the unplug xml file, SDC.xml file above.
1 PMIS 5 1 203424000 12.2.0.1.0 12.2.0.1.0 12.2.0.1.0 0.0.0.0.24 24 8.0.0.0.0.................................................... CATALOG=12.2.0.1.0 CATPROC=12.2.0.1.0 OWM=12.2.0.1.0 RAC=12.2.0.1.0 XDB=12.2.0.1.0 processes=1500 sessions=2280 large_pool_size=0 java_pool_size=50331648 db_block_size=8192 compatible='12.2.0.1.0' db_files=2048....................................
We only need to modify the following parameters to the compatible value of the target CDB:
12.2.0.1.012.2.0.1.0compatible='12.2.0.1.0' At this point, the study on "How to solve ORA-65294 error after PDB recovery from different machines" is over. I hope we can solve your doubts. Theory and practice can better match to help everyone learn, go and try it! If you want to continue learning more relevant knowledge, please continue to pay attention to the website, Xiaobian will continue to strive to bring more practical articles for everyone!
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.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.