Re: Oracle ASM Diskgroup Attributes Impact

 Thanks Jakub. I did the same and able to create clone manually with create pluggable command. I want to make sure that changing permission required by clone on testmaster is not impacting other Database sharing the diskgroup.

Thanks for sharing the details
Sanjay On Friday, January 18, 2019, 1:57:22 AM EST, Kuba Szepietowski <kuba.szepietowski_at_gmail.com> wrote:  

 Hi Sanjay,    

• If I change this Attribute for DATA diskgroup, Oracle manual says will not impact existing ASM files. What will happen to the new file created keeping in mind that there is only one user named ORACLE that owns all ASM/GI/RDBMS software on the system?  Do I need to be careful in setting ASM attribute umask ?

Once you add at least one user(oracle) to DISKGROUP all filles (existing and new) will be own by him.

In my case the oracle user was added only to DATA01 Diskgroup. 

ASMCMD> lsusr

DG_Name User_Num OS_ID OS_Name

DATA01  1        222   oracle_at_1ed1854e5445ff95bf0807bd35ebcad6

DATA01  2        30275 oragrid_at_1ed1854e5445ff95bf0807bd35ebcad6

now look at the file(and permission as I didn't change default umask(066)) of database which is not a test master

ASMCMD> pwd

•  Also testmaster setup runs the commands like below where it is adding the Group also. So how this new group can impact all other new files added to already running regular database and using the Diskgroup? Do I need to be careful in defining this new Group in ASM? 

ALTER DISKGROUP <diskgroup> ADD USERGROUP '<Group Provided in OEM Screen>';ALTER DISKGROUP <diskgroup> SET OWNERSHIP OWNER='<OSOWNER>',GROUP='<GroupAddedAbove>' for file '<ASM Full File Path>';ALTER DISKGROUP <diskgroup> SET PERMISSION OWNER=read only,GROUP=read only for file '<ASM Full File Path>';  I think there is even no need to add usergroup to diskgroup. Just enable ACL and add one user(oracle) as you have no role separation(no oragrid user). Then if you create test master database(as user oracle) the datafiles set to ownership and rights as follow: ALTER DISKGROUP DATA01 SET OWNERSHIP OWNER='oracle' for file '+data......';ALTER DISKGROUP DATA01 SET PERMISSION OWNER=read only,GROUP=read only for file '+data...';  This is output for files of test mast after settion to read only as you did in last command: ASMCMD> pwd

+DATA01/TM/DATAFILE ASMCMD> ls --permission

User                                     Group  Permission  Name

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  SYSAUX.372.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  SYSTEM.287.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  TBSX.272.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS1.375.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS2.374.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS3.376.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS4.369.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS5.373.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS6.371.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS7.270.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  UNDOTBS8.271.992969275

oracle_at_1ed1854e5445ff95bf0807bd35ebcad6          r--r-----  USERS.408.992969275

• Without setting this permission, Thin clone will fail to create the clone. Don't have any environment to play and so if someone can share their experience 

50%True :PEnable ACL on diskgroup where test master files are, add one user to this diskgroup, set correct attribute on sparse diskgroup(cell.sparse_dg and compatible.asm). No usergroup is required. Hope this help
-- Mit freundlichen Grüße/Best Regards/PozdrawiamJakub Szepietowski

**************************************Jakub SzepietowskiTel: +49 (0)152 31070846 

--
http://www.freelists.org/webpage/oracle-l