Oracle Key Concepts - Make Sure You Know All!
The content taken from
Title: Oracle Database Administration Concepts &
Implementation Made Simple
ISBN: 0-9770739-0-4
Author: Asim Abbasi
Oracle Key Concepts - Make Sure You Know All!
141. It’s better to have mirror copies of control file reside on
different physical disks.
142. We can always add data files, redo log groups and redo log members
after creation of the database using the ALTER DATABASE Statement.
143. Normally we cannot surpass the maximum limit in adding these files.
144. Each Tablespace can have one or more data files but each data file
can never be associated with two or more Tablespace.
145. All members within each redo log group are mirror copies of each
other.
146. Once the template will be saved, it will add on to the four
pre-built templates in DBCA.
147. Having a template helps in the creation of clone database.
148. SYS and SYSTEM accounts get created as default with default
passwords.
149. It’s highly recommended to change passwords of these accounts as
soon as possible.
150. SYS is the owner of Data Dictionary Views and SYSTEM is a DBA
account.
151. Oracle recommends to have at least two or more DBA account not just
one.
152. DBCA does network configuration for your database automatically so
that not only users but DBAs can also access it for remote database
management.
153. OEM is the tool used by DBAs for local/remote database
administration.
154. Oracle Net has to be there in both clients and server.
155. Configuration of Oracle Net on server side is actually the
development of listener.ora file.
156. Configuration of Oracle Net on the client side is actually the
development of tnsnames.ora file.
157. Oracle Net takes care of all different types of Network protocols.
158. Server and clients know how to speak with Oracle Net and Oracle Net
knows all different Network languages.
159. The sole job of the listener process is to bequeath the connection
to the dispatcher or dedicated server process.
160. tnsnames.ora file contains the resolution of “Net Service Name” or
“Connect String” that we will use to connect to Oracle Server.
161. Before starting the configuration process on clients and server
make sure ping commands result in success.
162. Creation of tnsnames.ora file on the server end is only required if
you want to run OEM on the server.
163. The purpose of tnsnames.ora file is that it contains the name
resolution of Net Service Name.
164. Net Service Name is basically the alias given to the set of TCP/IP
required connection parameters that can lead OEM, SQL*Plus etc. to the
Oracle Server.
165. In the Unix environment use the command <oemapp console> to start
the same OEM which you can start in windows under start>all programs
menu.
166. To connect as SYSDBA you have to be the member of operating system
OSOPER or OSDBA group.
167. Only DBA can be authenticated by Oracle with this externally
authenticated method.
168. Regular database users are verified through Oracle Server only.
169. Net Service Name gets resolved by tnsnames.ora file.
170. Oracle Network Manager should be preferred over Oracle Network
Configuration as recommended by Oracle.
Oracle Key Concepts - Make Sure You Know All!
Share with others: