Subscribe

SMO 3.1 - clone of read-only tablespaces

[ Edited ]

Hi,

we want to use SMO 3.1 for cloning our read-only tablespaces.
In the release notes of 3.1 there is one note:
Note 5092: SnapManager for Oracle does not support the cloning of databases that contain read-only tablespaces.
Is there any workaround?
Thanks
Sebastian

Re: SMO 3.1 - clone of read-only tablespaces

hi

SMO3.1 doesn't support cloning of databases that contain read-only tablespaces.

There exists no workaround for this as of now.

Clone cannot be created if any of the tablespace is read-only.

If you still want to clone the db, you should make the tablespace as read-write, now take a backup and then clone it.

-- Kanthan