[Oracle Notes] 2. Oracle Server entry and Oracle management routine

Oracle Server entry and oracle management routine
I. Common oracle database management tools
Oracle Universal Installer (OUI): used to install, upgrade, or delete Software Components
Oracle Database Configuration Assistant (DBCA): a graphical user interface tool that interacts with OUI. It can also be used independently to create, delete, or modify databases.
SQL * Plus: a utility used to access data in Oracle databases and the most commonly used tool for database operations during routine operations.
Oracle Enterprise Manager (OEM): A graphical interface for managing, monitoring, and optimizing one or more databases.
Ii. Oracle Universal Installer
1. It is used to install, upgrade, or delete software components, and also to create databases.
2. Based on Java Engine
3. Have the following features
Automatic correlation Parsing
Web-based Installation
Tracking component and kit installation list
You can uninstall installed components.
Supports multiple oracle Home Directories
Support for global technologies
4. How to start: $./runInstaller
5. to use the response file for non-interactive installation, you only need to compile custom Parameters Based on the editing template (the template is located in the stage/response directory). The command is :. /runInstaller-responsefile myrespfile-silent.
Iii. Oracle Database Configuration Assistant
1. Create a database
2. Configure Database options
3. delete a database
4. Manage templates
5. when a database is created, the user SYS and SYSTEM are automatically created and assigned the DBA role. SYS has more permissions than SYSTEM, and SYS has more permissions than SYSTEM to create databases, therefore, we usually use SYSTEM to operate databases.
Iv. SQL * Plus
1. An oracle tool that provides the following functions
Operate and control databases
Start and close databases, create and run queries, Add rows, modify data, and write definition reports
2. It is part of a standard SQL language with specific additional content
3. connect to SQL * Plus command: sqlplus/nolog → connect/as sysdba
V. Oracle Enterprise Manager
1. It is used as a DBA centralized system management tool and is widely used in enterprise production environments.
2. tools for managing, diagnosing, and optimizing multiple databases
3. tools for managing multiple network nodes and services from multiple locations
4. share tasks with other administrators
5. provides tools for managing parallel servers and replicated Databases
Vi. initialization parameters
1. entries in the file are dedicated to the routines to be started
2. There are two types of parameters:
Show: There is an entry in the file
Implicit: there are no entries in the file, but it is assumed that the default value of oracle is used.
3. Multiple initialization parameter files can exist.
4. the effective time of the change to the entries in the file depends on the type of the initialized parameter file used.
Static parameter file pfile: generally called initSID. ora
Permanent parameter file (spfile): is widely used after 9i. It is generally called spfileSID. ora.
VII. PFILE
1. Text File
2. Use the operating system editor for modification, such as the VI in linux
3. manually modify
4. The changes will take effect at the next startup.
5. open only during routine startup
6. The default location is $ ORACL_HOME/dbs.
8. SPFILE
1. binary files. For details about how to use the strings command in linux, see
2. It is maintained by the Oracle server and can only be modified in the routine. modifications made in the operating system using a text editor will invalidate the spfile file.
3. Always resident on the server side
4. The changes are permanently valid and are not affected by shutdown or startup.
5. You can adjust the parameter values.
6. enable the recovery manager to back up the initialization parameter file, and use the RMAN tool to back up
7. create spfile: create spfile = '$ ORACLE_HOME/dbs/spfileSID. ora' from pfile = '$ ORACLE_HOME/dbs/initSID. ora'
9. STARTUP command action
1. Priority
SpfileSID. ora
Default spfile
InitSID. ora
Default pfile
2. You can specify pfile at startup.
Startup pfile = $ ORACLE_HOME/dbs/initSID. ora
3. To start the database using a non-default spfile, you must specify the spfile = <complete path and file name> In pfile.
10. Modify parameters in spfile
1. Use alter system to change the parameter value
Alter system set undo_tablespace = 'undo2 ';
2. Specify whether the changes are temporary or permanent.
Alter system set undo_tablespace = 'undo2' scope = both;
3. alter system set parameter_name = parameter_value [comment 'text'] [scope = memory | spfile | both] [SID = 'sid' | '*']
Where
Parameter_name: name of the parameter to be modified
Parameter_value: the value to change the parameter
COMMENT: add comments next to parameters modified in SPFILE. SCOPE:
Determine whether the changes should be made in the memory, in the SPFILE, or both.
MEMORY: The parameter value can only be changed in the currently running routine.
SPFILE: You can only change the parameter value in SPFILE.
BOTH: The parameter value can be changed in the currently running routine and SPFILE.
SID: ORACLE_SID that identifies the SPFILE to be used
'Sid': Specifies the sid used to change the SPFILE.
'*': Use the default SPFILE.