Skip to main content
Delphix

VDB Refresh fails with ORA-14694: Database Must Be in UPGRADE Mode to Begin MAX_STRING_SIZE Migration (KBA5254)

 

KBA

KBA# 

5254

Issue

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

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

4.0

4.0.0.0, 4.0.0.1, 4.0.1.0, 4.0.2.0, 4.0.3.0, 4.0.4.0, 4.0.5.0, 4.0.6.0, 4.0.6.1

3.2

3.2.0.0, 3.2.1.0, 3.2.2.0, 3.2.2.1, 3.2.3.0, 3.2.4.0, 3.2.4.1, 3.2.4.2, 3.2.5.0, 3.2.5.1, 3.2.6.0, 3.2.7.0, 3.2.7.1

3.1

3.1.0.1, 3.1.1.0, 3.1.2.0,  3.1.2.1, 3.1.3.0 , 3.1.3.1, 3.1.3.2, 3.1.4.0, 3.1.5.0, 3.1.6.0

3.0

3.0.0.3, 3.0.0.4, 3.0.1.0, 3.0.1.1, 3.0.1.2, 3.0.1.3, 3.0.2.0, 3.0.2.1, 3.0.3.0, 3.0.3.1, 3.0.4.0, 3.0.4.1, 3.0.5.0, 3.0.6.0, 3.0.6.1

Resolution

To resolve the issue VDB Refresh fails with ORA-14694: database must in UPGRADE mode to begin MAX_STRING_SIZE migration:

  1. Create a new Template, for example Extended.

  2. Add the following entry to this Template MAX_STRING_SIZE=EXTENDED.

  3. Delete the VDB. 

  4. Reprovision the VDB using the newly created Template.

Note

Note:

Once the first refresh with the template-EXTENDED is used, there is no need for the virtual database to have a template anymore. It will only be needed when refresh to a snapshot with MAX_STRING_SIZE=standard is needed.

Troubleshooting

Typical error in debug.log:

[2019-11-20 21:01:53,264][INFO][jcm.impl.JobInstance#execute:355][Worker-129312|JOB-56320|DB_REFRESH(ORACLE_DB_CONTAINER-557)][] job failed with user error
com.delphix.common.exception.messages.OracleTargetscriptsExceptions$DbResetlogs: exception.oracle.targetscripts.db.resetlogs {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 /XXXXXXXXX/oracle/diag/rdbms/xxxxxxx/xxxxxxx/alert/alert_xxxxxx.log
db_status=' || status from v$instance
ALERT_LOG_FILE_PATH=/XXXXXXXXX/oracle/diag/rdbms/xxxxxxx/xxxxxxx/alert/alert_xxxxxx.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: 19902
Session ID: 234 Serial number: 3489
OPEN_DATABASE_ERROR
}

 

 

Related Articles

The following articles may provide more information or related information to this article: