2011-04-18 07:11 AM - edited 2015-12-18 01:27 AM
2011-04-18 10:05 PM
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.