All language subtitles for [SubtitleTools.com] Understanding Oracle Connections - Learning Oracle 12c [Video]

af Afrikaans
ak Akan
sq Albanian
am Amharic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bn Bengali
bh Bihari
bs Bosnian
br Breton
bg Bulgarian
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranรฎ)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil)
pt Portuguese (Portugal)
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
si Sinhalese
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu

Original subtitles

In this lesson, we're going to talk

about how connections are made to an Oracle

database via a network.

So that's all about how Oracle does its networking component.

And Oracle's networking stack that's

included with its database product is called Oracle Net.

Now it's been called many different things

through previous versions, such as SQL Net, Net 8,

and so on and so forth, but Oracle Net

is the name given to it at this point.

And Oracle Net is really an amazing thing

because it allows a user to connect to a database

irrespective of the operating systems involved.

So I can have a client machine running

SQL Developer on Windows and still connect to an Oracle

database running on Linux.

And there's no network problems there because

of Oracle's networking stack.

And this has been in place for a long time

and was really one of the first commercial databases

to really make use of this technology.

And truthfully, the connection information involved and setup

are really pretty quite simple.

There's not a lot to administer Oracle networking.

It really just requires the knowledge

of a couple of different subjects.

So a database can participate in different network models.

So we can have a client-server model,

and that's a direct connection.

So that occurs when a user, say running SQL Developer,

makes a direct connection to a database, client to server.

This can also be certain applications

that make those types of connections.

So we might build and deploy an application to our users.

And in that application is connection information

on how to connect directly to an Oracle database.

So it's a direct connection, client to server.

We also have the network model that's really more popular

today that most DBAs would be more likely to see,

and that's a multi-tier network model.

And that's connection through another server.

So that would be a situation where a user connects

into a web server and then maybe an application server and then

a database server.

So there's multi-tiers involved, multiple tiers.

Oracle networking also supports two major server architectures

for the Oracle database.

The first is called dedicated server.

Dedicated server setup, a connecting user

is given a dedicated server process when they connect.

So if we have a database and then a user,

we have a process running on the database called a listener.

And the listener is only there and has

only the job of listening for incoming connections.

So Kara, when she makes an attempt

to connect to a database, she's actually

contacting the listener first.

If the listener isn't running, she

won't be able to make a network connection to the database.

Once her user name and password are negotiated

and she is authenticated, then she's

given her own dedicated server process

to do work on the database.

So, on the Linux operating system,

we would actually see that as an individual process

out on the operating system.

And so all work that Kara does in her session to the database

occurs through that pipe.

Oracle also supports what's called shared server.

And this has been called a number of different things

through past versions as well.

Multi-threaded server was one of its previous names.

And in a shared server model, the connecting user

is given a shared server process.

So it looks something like this.

We have a database here, and then we

have a process called a dispatcher.

And the dispatcher's job is really

to play traffic light for incoming connections.

So between this dispatcher and the database,

we have what's called shared servers

or shared server processes.

So these are dedicated connections into the database.

So we can think of them as pipelines into the database.

But when a user tries to connect to this database,

first, the user has to go through a dispatcher.

And the dispatcher will decide which shared server process

Kara gets to use.

So she may get this shared server process.

As long as she's doing work on that shared server process,

it acts almost as a dedicated server process.

But the moment that she becomes idle,

that shared server becomes available for someone else.

So Scott, if he were to connect in,

would get a different shared server process.

And no matter how many connections

are incoming to the database, they go through the dispatcher,

and they all have to negotiate through those shared server

processes.

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.