Recolate pdb with AVAILABILITY MAX from 18.3 to 19c failed with error ORA-65188. Example: Recolate pdb with AVAILABILITY MAX from lower version to higher version. AVAILABILITY MAX means that we don't want customer to get any
downtime. Upgrade can be time consuming, and it is a manual action
currently. Recolate pdb from lower version to higher version, without using 'AVAILABILITY MAX'.Applies to:
Oracle Database - Enterprise Edition - Version 18.3.0.0.0 and later
Information in this document applies to any platform.
Symptoms
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL> create pluggable database <pdb_name> from <pdb_name>@<dblink> relocate availability max create_file_dest='xxxxx';
create pluggable database <pdb_name> from <pdb_name>@<dblink> relocate availability max create_file_dest='xxxxx'
*
ERROR at line 1::
ORA-65188: CANNOT RELOCATE A PDB OPENED WITH WARNINGSChanges
Cause
So AVAILABILITY MAX will still be a downtime for customer
application. Hence, we do not allow AVAILABILITY MAX during relocate
from lower version to higher version.Solution
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。




