VDB Refresh fails with ORA-14694: Database Must Be in UPGRADE Mode to Begin MAX_STRING_SIZE Migration (KBA5254)
KBA
KBA# 5254Issue
A VDB refresh operation will fail if the value of MAX_STRING_SIZE on the Source is changed from STANDARD to EXTENDED.
VDB parameters are taken at the time the virtual database is created. As the virtual database was created with MAX_STRING_SIZE unset, that means that implicitly it is STANDARD.
Once the database is upgraded to use MAX_STRING_SIZE = EXTENDED, the Refresh operation fails with the Oracle error because it is using MAX_STRING_SIZE set to STANDARD, as those are the config parameters of the virtual database.
Applicable Delphix Versions
This article applies to the following versions of the Delphix Engine:
|
Major Release |
All Sub Releases |
| 6.0 | 6.0.0.0, 6.0.1.0, 6.0.2.0 |
|
5.3 |
5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0 5.3.6.0, 5.3.7.0 |
|
5.2 |
5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1 |
|
5.1 |
5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0 |
|
5.0 |
5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1 ,5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4 |
|
4.3 |
4.3.1.0, 4.3.2.0, 4.3.2.1, 4.3.3.0, 4.3.4.0, 4.3.4.1, 4.3.5.0 |
|
4.2 |
4.2.0.0, 4.2.0.3, 4.2.1.0, 4.2.1.1, 4.2.2.0, 4.2.2.1, 4.2.3.0, 4.2.4.0 , 4.2.5.0, 4.2.5.1 |
|
4.1 |
4.1.0.0, 4.1.2.0, 4.1.3.0, 4.1.3.1, 4.1.3.2, 4.1.4.0, 4.1.5.0, 4.1.6.0 |
Resolution
To resolve the issue VDB Refresh fails with ORA-14694: database must in UPGRADE mode to begin MAX_STRING_SIZE migration:
-
Create a new Template, for example Extended.
-
Add the following entry to this Template
MAX_STRING_SIZE=EXTENDED. -
Delete the VDB.
-
Reprovision the VDB using the newly created Template.
Troubleshooting
The following errors will be observed in the Command Output portion of fault when the VDB operation fails:
command: umask 027; . $DB_SCRIPT_DIR/setup-oraenv.sh; $DLPX_SHELL $DB_SCRIPT_DIR/doOpenDatabase.sh "$LOGON_STR" output:END_OF_SETUP WARNING: cannot read alert log file /u01/app/oracle/diag/rdbms/vdbomsr8a1718_wm8/VDBOMSR8A17WM8/alert/alert_VDBOMSR8A17WM8.log db_status=' || status from v$instance ALERT_LOG_FILE_PATH=/u01/app/oracle/diag/rdbms/vdbomsr8a1718_wm8/VDBOMSR8A17WM8/alert/alert_VDBOMSR8A17WM8.log PRE_OPEN_LINE_COUNT= alter database open resetlogs * ERROR at line 1: ORA-00603: ORACLE server session terminated by fatal error ORA-01092: ORACLE instance terminated. Disconnection forced ORA-14694: database must in UPGRADE mode to begin MAX_STRING_SIZE migration Process ID: 15294 Session ID: 162 Serial number: 3504 OPEN_DATABASE_ERROR
Related Articles
The following articles may provide more information or related information to this article: