In the previous two parts of this article on implementing security in an environment of “Oracle Exadata Database Machine” it has shown the way in which security is created at the level of ASM (Part 1) and database level (Part 2) to meet the different requirements of the organization and accompany the entire lifecycle of the data. In the latter part of the article it will demonstrate how to remove security settings at both ASM and in terms of database, so not only the article in its three parts will help implement security in your organization but also to demonstrate the procedure of removing the security it provides a comprehensive article that can be used for testing purposes or for educational purposes. “Oracle Exadata Database Machine” every day is gaining popularity in the countries of Latin America, not only by low times used to process large amounts of data, compression cup provides “Hybrid Columnar Compression”, but because it provides many features facilitating the administration of database servers and storage, however, as there are many servers (22 servers in a “Full Rack”, and taking into account that “Oracle Exadata Database Machine is a scalable solution”) security is an emerging problem that can be compared with the security problem when a database the number of users is large. It is known that for managing user privileges easier there are roles, which is nothing more than a group of users, well, safety Exadata would become an analogy, where roles might be clusters of ASM and Users might be the databases, you can restrict access to the “Grid Disk” gathering the databases by using a single cluster of ASM (Coarse granularity) or you can restrict access to the “Grid Disk” by each of the databases (fine granularity).

Read More