The document discusses the key log and configuration files used by an Oracle database:
1) The alert log file contains messages and errors from the database.
2) Trace files contain process errors and diagnostic information.
3) The password file authenticates database users if the initialization parameter REMOTE_LOGIN_PASSWORDFILE is set.
4) The server parameter file (SPFILE) replaces the parameter file and allows dynamic parameter changes without restarting the database.
The document discusses the key log and configuration files used by an Oracle database:
1) The alert log file contains messages and errors from the database.
2) Trace files contain process errors and diagnostic information.
3) The password file authenticates database users if the initialization parameter REMOTE_LOGIN_PASSWORDFILE is set.
4) The server parameter file (SPFILE) replaces the parameter file and allows dynamic parameter changes without restarting the database.
The document discusses the key log and configuration files used by an Oracle database:
1) The alert log file contains messages and errors from the database.
2) Trace files contain process errors and diagnostic information.
3) The password file authenticates database users if the initialization parameter REMOTE_LOGIN_PASSWORDFILE is set.
4) The server parameter file (SPFILE) replaces the parameter file and allows dynamic parameter changes without restarting the database.
The document discusses the key log and configuration files used by an Oracle database:
1) The alert log file contains messages and errors from the database.
2) Trace files contain process errors and diagnostic information.
3) The password file authenticates database users if the initialization parameter REMOTE_LOGIN_PASSWORDFILE is set.
4) The server parameter file (SPFILE) replaces the parameter file and allows dynamic parameter changes without restarting the database.
Download as TXT, PDF, TXT or read online from Scribd
Download as txt, pdf, or txt
You are on page 1/ 3
1)ALERT LOG FILES:-
-->The alert log file (also referred to as the ALERT.LOG) is a chronological
log of messages and errors written out by an Oracle Database. Typical messages found in this file is: database startup, shutdown, log switches, space errors, etc -->Oracle will automatically create a new alert log file whenever the old one is deleted. --> Its location is defined by BACKGROUND_DUMP_DEST parameter.
2)TRACE FILES:- -->Trace File are trace (or dump) file that Oracle Database creates to help you diagnose and resolve operating System problems. -->Each server and background process writes to a trace file. When a process detects an internal error, it writes information about the error to its trace file. -->There is only one alert log file. While there could be any no of trace files.
3)PASSWORD FILE:- -->USED TO AUTHENTICATE DB USERS. -->THE INIT PARAMETER REMOTE_LOGIN_PASSWORDFILE SPECIFIES IF A PASSWORD FILE IS USED TO AUTHENTICATE THE DBA OR NOT. IF IT SET EITHER TO SHARED OR EXCLUSIVE A PASSWORD FILE WILL BE USED.
--->INTRODUCED FROM 9i --->USED BY DEFAULT BY ORACLE TO START DATABASE(FROM 9i) --->PERMITS DYNAMICALLY CHANGING PARAMETERS WITHOUT NEEDING TO RESTART THE DATABASE --->CANNOT EDIT FROM TEXT EDITOR AS ITS HEADER AND FOOTER THAT CONTAIN BINARY VALUES. --->SCOPE 1)SPFILE-->(For both static and dynamic parameters, changes are recorded in the spfile, and will take effect in the next restart.) 2)MEMORY-->(For dynamic parameters, changes are applied in memory only. No static parameter change is allowed) 3)BOTH---->(For dynamic parameters, the change is applied in both the server parameter file (SPFILE) and memory. No static parameter change is allowed.)
--->TO VIEW LOCATION:- SHOW PARAMETER SPFILE;(WILL ALWAYS SHOW LOCATION OF
5)PFILE:-(PARAMETER FILE) --->DEFAULT UNTIL 8i --->THIS FILE IS READ ONCE BY ORACLE AT STARTUP AND ALL PARAMETERS THEN GOES TO MEMORY --->CHNAGES IN PFILE ONLY TAKES PLACE AFTER RESTARTING DATABASE. ---CAN BE EDITED USING ANY TEXT EDITOR.
6)CONTROL FILE:- --->EVERY ORACLE DATABASE HAS A CONTROL FILE, WHICH IS A SMALL BINARY FILE THAT RECORDS THE PHYSICAL STRUCTURE OF THE DATABASE. THE CONTROL FILE INCLUDES: 1)THE DATABASE NAME 2)NAMES AND LOCATIONS OF ASSOCIATED DATAFILES AND REDO LOG FILES 3)THE TIMESTAMP OF THE DATABASE CREATION AND ITS BLOCK_SIZE. 4)THE CURRENT LOG SEQUENCE NUMBER 5)CHECKPOINT INFORMATION --->WITHOUT IT DATABASE CANNOT BE MOUNTED AND RECOVERY IS ALSO DIFFICULT. --->BY DEFAULT ONE COPY IS CREATED DURING DATABASE CREATION. --->IN ASM YOU CAN SPECIFY PATH IN INITIALIZATION PARAMETER AS IN DB_CREATE_FILE_DEST AND DB_RECOVERY_FILE_DEST TO CREATE CONTROL FILE. --->ORACLE STRONGLY RECOMMENDS TWO CONTROL FILES PLACED AT DIFFERENT PHYSICAL LOCATION.
--->SOME COMMANDS:- 1)SHOW PARAMETER CONTROL_FILE(SHOWS LOACTION OF CONTROL FILE) 2)SELECT * FROM V$CONTROLFILE;(SHOWS CONTROL FILE LOCATIONS)
7)REDOLOG FILES:- --->EVERY INSTANCE OF ORACLE DATABASE HAS ASSOCIATED REDO LOG TO PROTECT DATABASE IN CASE OF RECOVERY. --->DB HAS TWO OR MORE REDO LOG FILES.(ORACLE 12C RECOMMENDS 3) --->EVERY REDO LOG FILES HAS TWO OR MORE LOG GROUPS IN WHICH LOGS ARE PRINTED. --->SOME COMMANDS: A) SELECT * FROM V$LOG; (TO VIEW REDO GROUPS) B) SELECT * FROM V$LOGFILE; (TO VIEW ALL REDO LOGFILES WITH THEIR PHYSICAL LOCATION)
NAME:-REDO01,REDO02.... LOCATION:- WINDOWS:-D:\app\Dheeraj_kumar\oradata\orcl,YOU CAN CREATE OTHER FILES AT YOU OWN SPECIFIED LOCATION. LINUX:-ORACLE_BASE\oradata\DB_NAME
8)DATAFILES:- --->THESE ARE PHSICAL PART OF TABLESPACES. --->DATA IS ACTUALLY STORED IN DATA FILES ON HARD DISK. NAME:-FILE1.DBF LOCATION:- WINDOWS:-D:\app\Dheeraj_kumar\oradata\orcl LINUX:-ORACLE_BASE\oradata\DB_NAME
COMMANDS: A)SELECT * FROM V$DATAFILES.(SHOWS DETAILED INFO ABOUT EACH DATAFILE.) B)SELECT * FROM DBA_DATA_FILES.(SHOWS TOTAL SPACE FOR A DATAFILES,USED...) C)SELECT * FROM DBA_FREE_SPACE(SHOWS FREE SPACE IN DATAFILES)
