Category: Marking Architectural Decisions

Making Read-Only Tables- Tables and Constraints

You can place individual tables in read-only mode. Doing so prevents any INSERT, UPDATE, or DELETE statements from running against a table. An alternate way to do this is to make the tablespace read-only and use this tablespace for the tables that are static for read-only.There are several reasons why you may require the read-only […]

Assigning Database Object Privileges- Users and Basic Security

Database object privileges allow you to access and manipulate other users’ objects. The types of database objects to which you can grant privileges include tables, views, materialized views, sequences, packages, functions, procedures, user-defined types, directories, and now with 23c schemas. To be able to grant object privileges, one of the following must be true: •     […]

Understanding Schemas vs. Users- Users and Basic Security

A schema is a collection of database objects (such as tables and indexes). A user is an account to connect to the database with the username and password. Users can also own objects, which then the owner is the schema of the objects. Already discussed was how there are default schemas created to own database […]

Configuring a Centrally Managed User- Users and Basic Security

A centrally managed user is considered to be a user in one place, such as Active Directory or another LDAP service. The user can be managed for authentication and authorizations centrally, such that a user in Active Directory will have authentication managed via password or another type of key and, with the use of security […]

Marking Architectural Decisions- Managing Control Files, Online Redo Logs,and Archivelogs

When you implement archivelog mode, you also need a strategy for managing the archived log files. The archive redo logs consume disk space. If left unattended, these files will eventually use up all the space allocated for them. If this happens, the archiver cannot write a new archive redo log file to disk, and your […]

Determining the Optimal Number of Redo Log Groups- Managing Control Files, Online Redo Logs,and Archivelogs

Oracle requires at least two redo log groups to function. But, having just two groups sometimes isn’t enough. To understand why this is so, remember that every time a log switch occurs, it initiates a checkpoint. As part of a checkpoint the database writer writes all modified (dirty) blocks from the SGA to the data […]