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!
171. In Unix environment, ONM can be accessed by executing netmgr
command and the same software can be accessed in windows under start>all
programs menu.
172. We will first create the listener on the machine running Oracle
Server using ONM.
173. Dynamic Service Registration happens only if we select the default
listener name, protocol and port.
174. Dynamic Service Registration happen only if we use default Listener
Name, Protocol, Port.
175. Manual registration of Oracle Instance is also possible using ONM.
176. Its not recommended that you create the listener.ora file using
text editor. Always use ONM as it’s programmed to produce listener.ora
file exactly in same format required by listener process.
177. Global database name, Oracle Home and SID is required to complete
the manual registration of Oracle database.
178. The sole purpose of the listener process is to listen to the
connection request.
179. Listener process never processes the request rather it bequeath the
connection to dispatcher or dedicated server process and then gets back
to listening state.
180. Do not forget to save the configuration as it only after saving,
things get written to listener.ora file.
181. Two ways to do Dynamic service registration namely, use the default
listener or specify the following three init.ora parameters
LOCAL_LISTENER, INSTANCE_NAME & SERVICE_NAMES
182. Net Service Name is the short description or Alias for the long set
of connection parameters that help client applications to connect to
Oracle Server.
183. Net Service Names get resolved through tnsnames.ora file.
184. Here we will define the meaning of the Net Service Name “asim” and
save it in tnsnames.ora file.
185. Whenever any client uses the word “asim” Oracle will decode or
resolve the word using tnsnames.ora file as it contains the name
resolution of “asim”.
186. Service Name over in this slide is the Global Database Name of the
Oracle Database your connection will be bequeathed to.
187. ONM generates the tnsnames.ora file once you save the
configuration.
188. Net Service Name has to be created on each of the machines from
where you want to run client application.
189. Net Service Name on one machine need not to be similar to Net
Service Name on the other machine although both will point to the same
Oracle database.
190. You can connect to and manage multiple databases scattered all over
the world using the same OEM window.
191. You need to create Net Service Name for each of these databases in
the same way.
192. All the Net Service Names for all the databases you want to connect
to through OEM will be defined under one tnsnames.ora file one the
machine running OEM.
193. Under Databases item in the tree OEM contains the Net Service Names
of the databases and not the databases names or global database names.
194. Two types of Administrator Authentication viz., OS authentication
or password file.
195. We can use either of the methods for local as well as remote
administration.
196. More than one distributed databases can be managed using OEM.
197. OEM communicates with Oracle Server using same SQL statements that
we use in manual database management or before the development of OEM.
198. OEM is java based client side application for complete management
of Oracle database(s) locally or remotely without using any SQL
statements.
199. OEM on the other hand communicates with Oracle using SQL in the
background.
200. Complete management of Oracle Database(s) is possible using OEM.
Oracle Key Concepts - Make Sure You Know All!
Share with others: