Re: How to restrict database to use specific diskgroup within a Grid configuration

https://docs.oracle.com/en/database/oracle/oracle-database/19/ostmg/asm-access-control-diskgroups.html

On Thu, Mar 17, 2022 at 2:21 AM Martin Berger <martin.a.berger_at_gmail.com> wrote:

> Hi,
>
> I assume you are using Linux and no Exadata or similar.
> You can assign separate group IDs to the disks of the specific diskgroups
> and also start the DB instances with different users and group.
>
> If you are using PDBs Path_Prefix and Create_File_Dest can partially help
> - at least for datafiles.
>
> hth,
> Martin
>
>
>
> Am Mi., 16. März 2022 um 20:58 Uhr schrieb Sourav Biswas <
> biswas.sourav_at_hotmail.com>:
>
>> Hello Everyone,
>>
>> Current environment:
>>
>> OS: RHEL 7.9
>> Grid OS User: grid
>> Grid: 19.14
>> Oracle OS User: oracle
>> CDB: 19.14
>>
>> We are running multiple CDBs with one PDB each, on a single Grid. As per
>> our architecture, for every CDB, we have 3 sets of asm
>> diskgroups(DATA_CDBn,REDO_CDBn,ARCH_CDBn) created.
>>
>> For example,
>> CDB1 database will have DATA_CDB1, REDO_CDB1, ARCH_CDB1 diskgroups
>> CDB2 database will have DATA_CDB2, REDO_CDB2, ARCH_CDB2 diskgroup
>>
>> Since, at ASM level we can see all of the above 6 diskgroups, I would
>> like to introduce some restrictions to every database to read and write to
>> their dedicated diskgroups. I want to ensure that even the sysdba privilege
>> user of a database cannot create datafile on diskgroups belonging to other
>> database.
>>
>> Please advise how to implement this restriction.
>>
>>
>>
>> Regards,
>> Sourav Biswas
>>
>
>
> --
> Martin Berger Oracle ♠
> martin.a.berger_at_gmail.com _at_martinberx <https://twitter.com/martinberx>
> ^∆x http://berxblog.blogspot.com
>

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