11. Database system files (Database System Files)
The following database system used for files during operation the Oracle database, and is located on the database server. Note that the data files are physical files belonging to the database containers, will not be described here.
• control files: control files necessary files, data relating Use for storing files and online redo date blog metadata files; for example, the name and the status thereof. Database instance needs this information in order to open the database. Further comprising controlling the file metadata must be accessed when the database is not open. It is strongly recommended that you make the database server to control multiple copies of files in order to achieve ADVANCED available Use of.
• Parameter File: The files necessary to define the configuration of shutter mode when the database instance starts. It may be initialization parameter files (p fi le) or a server parameter files (sp fi le).
• Online redo date Chi files: These files necessary If this sort of change will be stored in the database changes, and Use in data recovery.
• Auto Diagnostic Repository (ADR): ADR is based repository of files, Use to store database diagnostic data, such as tracking, dumps, the alert date Chi, when running a health monitor reports. It has ⼀ across multiple systems and multiple instances of Contents structure of the product. Database, Oracle automatically Storage Management (Oracle ASM), a listener, Oracle Clusterware and other Oracle products or components store all diagnostic data in the ADR. Each instance of each product are stored in the main diagnostic data which Your Own at the ADR of Contents.
• Backup Files: Use these optional files in the database recovery. Typically, when a media failure or user error Using damaged or deleting the original files, can restore the backup files.
• archived redo date Chi files: These files contain optional database instance ⽣ into a continuous history of data changes. Using these files and database backup, you can recover lost data files. In other words, archived data files date Chi recoverable restored.
• Password File: This optional files Use the SYSDBA, SYSOPER, SYSBACKUP, SYSDG, SYSKM, SYSRAC and SYSASM ⻆ discolored Using the remote user can connect to the database instance and Perform administrative tasks.
• Purse: Use of the applications for password credentials to connect to the database zoomed scale deployment, these credentials can be stored in the client Oracle wallet. ⼀ Oracle wallet is a secure software containers, Use to store authentication and signing credentials. Possible Use in wallet purse including Oracle user credentials Use, Use transparent data encryption (the TDE) Use of encryption and backup Oracle wallet public cloud (OPC) cloud module wallet database. Wallet is optional, but recommended that you use.
• Change Tracking File Block: block change tracking record at block change tracking files in response to high performance from ⽽ incremental backups by blocks that were changed. In the incremental backup, Oracle Recovery Manager (RMAN) No need for scanning all the blocks to determine which blocks have changed, ⽽ Use this is to identify the files to be backed up is changed block. Block change tracking files are optional.
• Flashback date Chi: Flashback Database is similar to conventional point in time recovery in its results. It allows you to restore the database to the state near ⼀ times. Flashback Database Using the date of its logging mechanism Your Own, create a blog flashback date and stored in the fast recovery area. Only when Using flashbacks date chi can order Using Flashback Database. To facilitate Using this function, you must set up the database to create a flashback date blog. Flashback date Chi is optional.
Control files, online redo date files and archived redo Chi Chi date files can be multiplexed Use, which means you can automatically maintain the same two or more copies in a separate location.
Note: For more detailed information, see the following: Physical Storage Structures.
12. Use of the container shall (Application Containers)
It is an optional container of the applications created by the user CDB assembly Use, Use for storing data and metadata to apply it programs the PDB. CDB can contain zero or more of the applications of the container. ⼀ a container of the applications only one of the applications of ⼀ root of Contents and ⼀ or more of the applications PDB, which are the root of Contents Insert in the CDB. Of the applications belonging to the root of Contents CDB root of Contents, does not belong to other containers, and stores the public Use of metadata and data.
Typical of the applications will install a common object of the applications Using ordinary households, public objects and data link metadata links of. You can create multiple sales-related ⼀ PDB in a container of the applications, these PDB ⼀ a share of the applications back-end ⼀ public groups Using tables and table definition consists of.
Root of Contents of the applications, of the applications and types of submenus of the applications PDB has ⼀ a SYSTEM, SYSAUX, TEMP, USERS and optional UNDO table space. Each tablespace representatives ⼀ or more data files.
Note: For more detailed information, see the following: About Application Containers.
13. Auto diagnostic repository (Automatic Diagnostic Repository) (ADR)
Auto diagnostic repository (ADR) is Use diagnostic data in the database system date range tracking and logging central repository. It includes the following:
• Background trace files: Each database background process can write START associated track files. When a process detects an internal error, the process will dump information about the error to its trace in the file. Write-Protected track certain information for the database administrator's instruction files, ⽽ additional information about the support services for Oracle ⽀ Use. Typically, database background process trace file names containing the Oracle System Identifier (SID), a background process name and operating system process ID. Using the example in the RECO process of tracking files are mytest_reco_10355.trc.
• Reception tracking files: Each server process can write START associated track files. When a process detects an internal error, the process will dump information about the error to its trace in the file. The server process trace file names include Oracle SID, string ora and the operating system process ID. Examples of server process trace file names are mytest_ora_10304.trc.
• Dump File: diagnostic dump files are ⼀ special kind of tracking files, which contain information about the state or structure of the points detailed time information. Dump files usually respond diagnostic data event ⼀-time output, ⽽ tracking files tend to be continuous output diagnostic data.
• monitor when running a status report: Oracle database includes ⼀ framework called when running a health monitor, and shooting under the database when running a diagnostic check. When running a health check detectable damage files, logical blocks and physical damage, undo and redo damage, damaged data dictionary. Health checks will ⽣ to report on its findings and will provide recommendations to solve the problem in many cases.
• Event Package: For the upload diagnostic data to Oracle ⽀ hold of Custom Remedies, therefore especially your first data collection to intermediate logical structure called an event package (package) in. A package is a collection of metadata stored in the ADR, and points to the diagnostic data files and other files outside the ADR. When you create a package, select one or more issues to add to the package. Then, as ⽀ held ⼯ station issues associated with the selected question information, event information and diagnostic data (e.g., dump and trace files) is automatically added to the package.
• Dump Event: If this sort of event, one or more of the set remains in the database dump of Contents START write event created for the event. Dump event also includes an event number in the file name.
• alarm date Chi Files: Alarm date Chi database is the message and the wrong date of Chi in chronological order. Oracle recommends that you regularly check the alarm date blog.
Note: For more detailed information, see the following: Automatic Diagnostic Repository.
14. The backup files (Backup Files)
Database backup can be physical or logical backup backup.
• physical backup is a copy of the physical database files. You can use the Recovery Manager (RMAN) or operating system program into ⾏ Use real physical backup.
• logical backup includes tables, stored procedures and other logical data. You can use the Oracle database instance of the applications (such as Data Pump Export) extraction logic data, and stores it in ⼆ in binary files. Logical backup physical backup may be supplemented.
RMAN database backup storage for the creation of image copies or backup sets.
• An image copy data files, disk-by-bit control files or archived redo date Chi files are copied. You can use the program or operating system real Use RMAN to create image copies of physical files, and then either uses one ⼯ having to restore them. Using image copies on disk is very, because you can place an incremental update them and restore them.
• RMAN backup set is created with a proprietary format, which Contains either one or more data files, archived redo date Chi files, control files or data files in the server parameters. ⼩ units of the backup set is ⼀ a ⼆ binary files called backup of files. A backup set is RMAN can backup order is writing device (e.g. tape) the only ⼀ form. Another advantage of the ⼀ backup set is unused block RMAN Using Using compressed to save space in the backup data files. Backup set comprising only those data blocks of the file in the data storing Use. Backup set may be compressed, encrypted, transmitted to the tape, and use the data files of the copy is not available ADVANCED not been used for spatial compression.
RMAN can and media management library (MML), system backup to tape (SBT) software (can create backups to tape), Oracle database backup cloud services, or zero data loss recovery device interaction (commonly referred to as recovery equipment).
Note: For more detailed information, see the following:
Backup and Recovery
About Zero Data Loss Recovery Appliance
15. Process monitoring process (PMON)
Process monitoring process (PMON) is ⼀ a background process, which periodically scans all processes to find any abnormal process of death. Then, PMON is responsible for coordinating the clean-up of the main process (CLMN) and cleaning slaves (CLnn) Perform cleanup.
PMON as the operating system when running a process ⽽ not thread. In addition to the database instance, PMON also Operation with Oracle Auto Storage Management (ASM) instances and proxy instance Oracle ASM.
Note: For a complete list of processes, see the following: Background Processes.
The article is being updated, so stay tuned below ~