Is it a requirement to have SYSDBA privileges in both databases when transporting a tablespace from one to the other? In 9i I'm pretty sure it was, but can't seem to find anything regarding this issue in 10g.
Printable View
Is it a requirement to have SYSDBA privileges in both databases when transporting a tablespace from one to the other? In 9i I'm pretty sure it was, but can't seem to find anything regarding this issue in 10g.
DBA will do. ;)
Right.... anything besides dba / sysdba. It looks like 9i can't do it, but 10g maybe with the following privs to get it out from A (haven't figured out the privs for getting it into B yet): alter tablespace (to make read only), execute_catalog_role (to tun dbms_tts.transport_set_check), exp_full_database (per the docs to include transport_tablespace=y)... Unfortunately, I don't have a 10g DB setup, I'd have to install a new DB just to test this.
Now you caught my attention.
Why are you so interested in this feature if you do not even have 10g installed?
Somebody might tell you to set undocumented parameter...
_ttablespace_security = false
...to allow anybody to do it and you wouldn't be able to tell if it works or not.
Good Question and interesting parameter you've mentioned. We've recently changed our hosted DB and APP to a new company that has DBA's (previous one did not) and the apps and DB have been mirgated to 10g. They won't allow dba permissions to an application user, a main part of our ETL load is using transportable tablespaces from a staging DB to a data warehouse.
I was just jocking, trying to make a point.Quote:
Originally Posted by wakedba
By the way, wouldn't be nice to have it? :)