Working Around Oracle Bug 27044169 ORA-17500 (KBA9163)
KBA
KBA# 9163Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
-
Major Release All Sub Releases 6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1, 6.0.9.0, 6.0.10.0, 6.0.10.1, 6.0.11.0, 6.0.12.0, 6.0.12.1, 6.0.13.0, 6.0.13.1
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.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.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
How to Workaround Oracle Bug 27044169 ORA-17500
When trying to start a VDB, the Delphix engine reports an error similar to the following and the DB start fails:
ERROR at line 1: ORA-01142: cannot end online backup - none of the files are in backup ORA-06512: at line 6 SQL> alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel
This can be indicative of Oracle Bug 27044169 ORA-17500: ODM err:File exists when Creating Archivelog where the Rdbms is unable to create a new archivelog due to a file existing with a matching name (the log is prefixed with a full stop/period to mark as hidden), for example:
/mnt/provision/VDBNAME/archive/.1_958_1093039296.dbf
This hidden file will only remain if the archivelog fails to create successfully.
The easiest solution would be to refresh the VDB through the user interface (GUI). However, if that is not possible, the following steps can be used to workaround the issue.
To complete the workaround for Oracle Bug 27044169 ORA-17500
- Connect to the engine via ssh.
ssh admin@<delphix-engine>
-
Stop the VDB from automatically starting (this will mount the file systems but not start the database).
delphix-engine> source delphix-engine source> select VDBNAME delphix-engine source VDBNAME> disable delphix-engine source VDBNAME disable> commit delphix-engine source VDBNAME> enable delphix-engine source VDBNAME enable> set attemptStart=false delphix-engine source VDBNAME enable> commit
- On the target target host execute the following.
$ mv /mnt/provision/VDBNAME/archive/.1_958_1093039296.dbf /mnt/provision/VDBNAME/archive/1_958_1093039296.dbf
- Start the VDB through the user interface (GUI).
If this procedure is unsuccessful, then it will be necessary to refresh the VDB