The following example sets the last archive timestamp of OS audit trail type in instance number 1. Displays the last archive timestamp set using " audsettimestamp " command.
The following are examples of the audshowtimestamp command. The example below displays the last archive timestamp set for OS audit trail type. The example below displays the clusterwide timestamp information for OS audit trail type. The following example queries audit cleanup jobs configured for OS audit trail type.
Displays only the audit trail properties of unified audit trail type. The following example queries audit configuration parameters for OS audit trail type. Previous Next JavaScript must be enabled to correctly display this content. Note: Oracle does not recommend using identifiers for Oracle Database object names that must be quoted. Table Options for the audcleanaudittrail command Option Description --os Cleans up audit files of OS audit trail type.
Note: The default value for the age of an audit file is 5 Days and the default value for the size of an audit file is 10 MB.
Examples The following are examples of audclearproperty command. Clears the last archive timestamp set by audsettimestamp. Table Options for the audcleartimestamp command Option Description --os Clears the last archive timestamp set for OS audit trail type. The example below clears the last archive timestamp set for Unified audit trail type. The following are examples for audcreatejob command. Table Options for the audsetdebug command Option Description --debug Dumps all debug information into the traces.
Note: The default debug level is "error". The following example sets the debug level to " debug ". Sets the job interval for the specified audit purge job. Disks in a disk group should have similar size and performance characteristics. The Create Disk Group page appears. It displays a list of Oracle ASM disks that are available to be added to a disk group.
To force the inclusion of a disk in the disk group, select the Force Reuse check box for that disk. Optionally enter an Oracle ASM disk name for each selected disk.
Oracle ASM provides a name if you do not. When you drop a disk group, you delete the disk group, and all of its files.
You cannot drop a disk group if any one of its database files is open. After dropping a disk group, you can add its member disks to other disk groups or use them for other purposes. One reason to drop a disk group is to change redundancy normal, high, or external. Because you cannot change the redundancy of a disk group, you must drop the disk group and then re-create it with the proper redundancy. In this case, you must back up or move disk group data before you drop the disk group.
To delete the disk group even if it still contains files, expand Show Advanced Options and ensure that the Including Contents option is selected. If the disk group contains files and the Including Contents option is not selected, then you cannot drop the disk group. You add disks to a disk group to increase the total amount of storage space in a disk group. You can add one or multiple disks in a single operation. Oracle ASM then rebalances the disk group so that data is evenly distributed on all disks, including the newly added disks.
You can specify a number to control the power of the rebalance operation. The range of valid values depends upon the Oracle Database release you are using. The higher the number, the faster the rebalance operation completes. This leaves these resources available for the database. The default value of 1 minimizes disruption to the database. A value of 0 prevents the rebalance operation from happening.
Manual or automatic rebalancing can then occur at a later time. For example, you may want to postpone rebalancing because you want to wait for a time when there are fewer demands on the database, or because you want to add more disks or drop disks later and want the rebalancing to be done only once for all disk group changes.
Click a link in the Name column to select the disk group to which you want to add disks. The Add Disks page appears. It displays a list of Oracle ASM disks that are available to be added to the disk group. To force the inclusion of a disk in the disk group, select the Force Usage check box at the right. Optionally enter an Oracle ASM disk name for each disk. When you drop a disk from the disk group, the disk group is rebalanced by moving all of the file extents from the dropped disk to other disks in the disk group.
If a user is not in the disk group, then this command records an error and continues to drop other users, if any. If the latter case, then the user is deleted, along with all the files that the user owns. Replaces one operating system user with another in an Oracle ASM disk group. The replacement user must not be a user currently in the disk group user list. If the command succeeds, all files that were previously owned by current user are now owned by the replacement user.
The current user is automatically removed from the user list of the disk group. Adding the current user back to the disk group is possible, but this user does not own any files. When changing the owner of an open file, the new owner cannot be dropped with the owner's files until all instances within a cluster are restarted. Modifies permissions of an Oracle ASM file. Setting read only permission to a file that has read write permission revokes the write permission.
Only the file owner or the Oracle ASM administrator can change the permissions of a file. Changes the owner or group of a file to the specified user or user group name, respectively. If the specified user or user group name does not exist, this command fails with an error. Also, the user group name must exist, and the owner of the file must be a member of that group.
Previous Next JavaScript must be enabled to correctly display this content. UMASK This attribute determines which permissions are masked out on the creation of an Oracle ASM file for the user that owns the file, users in the same user group, and others not in the user group. To stripe data, Oracle ASM separates files into stripes and spreads data evenly across all of the disks in a disk group.
The coarse-grained stripe size is always equal to the AU size not the data extent size. The Oracle ASM instance is release For the first 20, extents, the extent size is 1 M and equals one allocation unit AU.
For the next 20, extents, the extent size is 4 M and equals 4 AUs. To identify the stripe chunks of the file, they have been labeled A.. X 24 letters using different fonts for successive series of A.. X until all the chunks have been identified. In Figure , the file is striped in K chunks labeled A.. X with each K chunk stored in an extent, starting at the first extent in disk 1, then the first extent in disk 2, and then continuing in a round-robin pattern through all the disks until the entire file has been striped.
As shown in this example, the striping chunks first fill up the first extent of each disk, then the second extent of each disk, and so on until the entire file has been striped. In Figure , the file is striped in 1 M chunks labeled A.. X with each 1 M chunk stored uniquely in an extent, starting at the first extent in disk 1, then the first extent in disk 2, and then continuing in a round-robin pattern through all the disks until the entire file has been striped. For the first 20, extents where the AU equals the extent size 1 M , the stripe equals the extent size and allocation unit size.
For the variable extents, where an extent is composed of multiple allocation units, the file stripe is located in an AU of the extent. The striping chunks are placed in the allocation units of the first extents of all the disks before the striping continues to the next extent. Templates are collections of attribute values that are used to specify disk regions, file mirroring, and striping attributes for an Oracle ASM file when it is created.
When creating a file, you can include a template name and assign desired attributes based on an individual file rather than the file type. A default template is provided for every Oracle file type, but you can customize templates to meet unique requirements. Each disk group has a default template associated with each file type. This section describes Oracle ASM disk group administration and it contains the following topics:. The disk discovery process locates the operating system names for disks that Oracle ASM can access.
Disk discovery finds all of the disks that comprise a disk group to be mounted. The set of discovered disks also includes disks that could be added to a disk group. Only path names that the Oracle ASM instance has permission to open are discovered. The exact syntax of a discovery string depends on the platform, ASMLib libraries, and whether Oracle Exadata disks are used.
The path names that an operating system accepts are always usable as discovery strings. A disk group must be mounted by a local Oracle ASM instance before database instances can access the files in the disk group. Mounting the disk group requires discovering all of the disks and locating the files in the disk group that is being mounted.
You can explicitly dismount a disk group. Oracle reports an error if you attempt to dismount a disk group without the force option when any of the disk group files are open. It is possible to have disks fail in excess of the Oracle ASM redundancy setting. If this happens, then the disk group is forcibly dismounted. If the disk group is forcibly dismounted, a database cannot access files in the disk group.
For more information about disk groups, see "Mounting and Dismounting Disk Groups".
0コメント