Shadowing Practice: Oracle database architecture explanation in details - Learn English Speaking with Video
בחר מצב תרגול
כל מצב פותח חדר תרגול במסך מלא.
160 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
Hi friends, today in this video I am going to talk about Oracle Database.
2
Oracle Database is basically one of the most demanding database which has started by Oracle Corporation in 1971.
3
So even when you are starting your career as Oracle Database,
4
in most of the interview you will get so many questions from Oracle Database Architect.
5
So in that perspective also and even for learning Oracle Database,
6
this is one of the most demanding topic that you have to must learn with deep understanding.
7
So I am going to explain with my personal experience on Oracle Database because I am a database administrator.
8
So with my personal understanding,
9
with my personal experience, I am going to explain the whole architecture.
10
so yeah first of all whenever any end user wants to connect
11
or a database so it connects through use any client machine
12
or through any application end user application
13
or even through sql developer there are multiple platform from there you people connects to the database
14
so you know client machine it will create a user user process
15
and between user process
16
and server process there will be a listener listener will have information about the host
17
and port of an database with on the
18
with that it will decide which database it has to connect so it will it will generate a one dispatch
19
dispatcher request when that dispatcher will send that request to the server process
20
and server process are when
21
when you create a database by default it creates a dedicated server process
22
and server process basically sits on uh servers oracle server side
23
so when we create a database it will get created by default it will be a dedicated server process
24
and for dedicated server process it will create a PGA
25
that is called program global area but
26
if you are choosing a shared global area for that it will create UGA that is user global area.
27
So server process is basically responsible for making that connection to the database
28
because it's interact to the database so it will send
29
that request to the database like if we are firing any uh selected statement
30
or any sql on a database so from server process it will go to a
31
sga sga is a shared global area basically is the is it's the largest part of the database instance
32
and the database is basically combination of instance background process
33
and the physical files so physical files are basically data file redlock file
34
and control file so these are the physical files and yes SGA is also the combination of different sub components
35
so in that whenever
36
that request will come from server process it will it will go to share pool first of all
37
and in share pool there are two sub components
38
that one is library cache and another is dictionary cache library cache is basically information of most recently executed SQLs
39
so most recently executed SQLs are basically when
40
that request goes from server process to SGA it will do the syntax check like
41
if that query is selected star from employee
42
so syntax it will validate from there like
43
if you execute select from employee it will not execute because the syntax is missed here like star is missed.
44
So it will not it will throw the error.
45
So that part is happening from library cache because it will do the syntax check,
46
cement text check and privilege checks are happening on share pool itself.
47
So, when the syntax check will happen after that it will validate
48
if it will find
49
that yes this SQL is present on the buffer cache then it will fetch
50
that particular query output
51
and it will return to the server process it will return to the client machine
52
and that that's the same process is getting followed for in case
53
if that particular SQL is not present in library case then it will create a execution plan for that and also like
54
yes data dictionary case is a metadata of a database like
55
it will have a object information like table views are stored into this
56
so it will it will do the validation from data dictionary case as well as
57
when library case will will not find that particular SQL it will
58
generate a new execution plan that is basically goes for hard parishing and there is two words
59
that we use in a database when any SQL get executed on a database side,
60
it will go to soft parishing either it will go to hard parishing.
61
So, soft parishing is the first case where it will find the SQL from the library cache itself
62
and then it will fetch the data from memory buffer cache memory and it will return to the client.
63
But in hard parishing case,
64
will create a new execution plan and it will go for optim or through a optimization in that it will
65
it will it will check from the buffer case if
66
that not there then after creating execution plan it will then the background process will come into the picture
67
and db writer will fetch that
68
DB writer will fetch
69
that particular data as per the query request it will fetch the data from the data file
70
and it will return to the library cache and library cache will
71
buffer cache sorry buffer cache and then DB buffer cache will return that
72
to server process and server process will return to the client so that's how
73
it works
74
so the next is as we know buffer cache is doing
75
all the things whatever the queries are coming it is getting executed in buffer cache itself
76
and it stores the in case
77
if you are executing any like a database change statement queries like insert or create or something like any DML.
78
So in those situation it will do the changes on the data
79
and in that situation read log and online read log and buffer
80
read log buffer will come into the picture so there first of all buffer case will change that
81
after doing the modification on the query it will get converted into a dirty buffer
82
and that dirty buffer will get written to the online reader log it might be uncommitted transaction
83
or it may it may be a committed transaction
84
so both can be possible
85
and from a read a log buffer it will get written
86
to the read a log file through log writer log writer
87
is responsible it's also a background process these are basically a
88
mandatory background process background processes are basically two type back mandatory background process and optional background process so
89
library cache is a mandatory background process
90
which is responsible for copying online redlock buffers to the online redlock files
91
so here redlock files are basically two online redlocks we can create like as per need we create
92
that redlock files so first it will start writing to read log one after
93
that once it will get filled up it will done the online read log switch will happen
94
and then it will start writing to second online read log so that's how whatever the change
95
transaction change modified data will come from online read log buffer to the
96
read log it will get written to log 1 and log 2
97
and similarly till the time after
98
that it will get written to through archiver process there is a optional optional background process
99
that is called archiver with with the help of
100
that it will get written to the archive read log
101
that we'll use for our backup
102
and recovery of our database in case i am our database fails
103
or it get crashed for any reason so that will be used for recovery so yeah so the next is
104
assist if we focus of our mandatory background process
105
so as one is system monitors as money is basically used for instance recovery
106
and yeah even for temporary table space management also it
107
will be responsible PMON is responsible for our transaction transition rollback
108
and for PMON is process monitor which is responsible for user session recovery
109
and doing the cleanup or even rollback statements this is responsible for making those cleanups on database
110
and yeah check pointer is a background process which is updating the scn number to data file and on
111
control control control file control file is a brain of a database
112
which will which will have information about the database creation and all the data file information and detail about the database.
113
So, this control file will be considered as a brain of a database.
114
So, SCN number whenever SCN number is getting generated very frequently through whenever the check pointer occurs,
115
the time SCN number is getting generated and
116
that is getting updated to the header of a data file
117
and control red log control file so yes there are some condition
118
when the log writer writes log writer writes whenever the online red log is more than 1 GB
119
or its one third full
120
or even every 3 second log writer writes the data on the buffer read log buffers to the online read log files.
121
So similarly there are few condition on
122
that basis DB writer writes those online read logs to the
123
online buffer cases changes to the data file like whenever the buffer case dirty buffer is filled up
124
or even its its there is no space left in the buffer cache
125
or even whenever any trunk truncate or any drop statement table space drop
126
or truncate statements are getting executed or even for every commit basically the DB writer writes and log writer
127
before the DB writer so that is also one condition
128
when log writer writes so these are the condition
129
when the log writer writes so apart from there is a parameter file
130
and password file parameter file is basically a file
131
which will it's a file which stores the information of every component which is
132
showing on the figure as a shared pool sga sga max sga target
133
and buffer cache a red log java pool large pool this
134
uh parameters uh this this components are uh declared into a
135
parameter file with how much size we we need it so those things are declared all the instance related come
136
parameters are declared into parameter file
137
so parameter files is two type like one is P file
138
and the another is SP file P file we we called it any dot aura file
139
and the this file is basically a static file
140
and SP file is a dynamic file so
141
if we are doing any change in p file for
142
that we have to restart our database
143
and basically for for starting our instance p file is responsible to to allocate the sga
144
so p file is equally important without p file we our database cannot run
145
and the next is password file it is used for user authentication
146
so this is the whole thing about the database in
147
that data file is actual physical file
148
and read lock files are all the change transactions are getting stored into
149
that and control file already I explained it
150
so this is the whole thing about the database
151
and this all components are like very much important yeah Java
152
pool basically this Java pool are getting used at the time
153
when you execute a statement with jvm or java related uh statements for
154
that case java pool is getting used
155
and large pool is getting used at the time
156
when uh we are performing any uh arman backup with i um higher higher io
157
and for our recovery um yeah for database recovery
158
in those conditions large pool is getting utilized
159
so this is the whole database instance that i have explained
160
if you any doubt please comment below thanks for watching till here
הורד אפליקציה
כל מה שאתה צריך כדי לדבר בשטף
הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק
FOR YOU
המלץ על סרטון
B21
205 משפטים
Solving Easy SQL Interview Questions on Analyst Builder
Interview EnglishUniversity StudentsWorking Adults
C11
392 משפטים
Uber Data Engineering Mock Interview - Ride-Sharing Data Warehouse Schema
Interview EnglishUniversity StudentsWorking Adults
C21
83 משפטים
PostgreSQL Architecture Explained: Deep Dive for Beginners
Business EnglishUniversity StudentsWorking Adults
C12
263 משפטים
Anthropic's CCA Exam as a Field-Guide for Agentic Engineering — Frank Coyle, UC Berkeley
Business EnglishInterview EnglishUniversity Students
C12
188 משפטים
IT System Administrator Interview Questions and Answers | How to Pass an IT System Admin Interview
Business EnglishInterview EnglishUniversity Students
B23
26 משפטים
english interview p1
Interview EnglishWorking Adults
C12
95 משפטים
API Gateways in System Design Interviews w/ Ex-Meta Staff Engineer
Business EnglishInterview EnglishUniversity Students
B22
187 משפטים
How to ACTUALLY Get a DevOps Job in 2026
Interview EnglishUniversity StudentsWorking Adults
B21
113 משפטים
Google Interview Tips That Actually Get You Hired
Interview EnglishWorking Adults
C18
324 משפטים
Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)
Business EnglishInterview EnglishUniversity Students
C12
239 משפטים
Excellent 2 Years AWS DevOps Engineer Mock Interview with Questions and Answers | Cloud | Docker
Business EnglishInterview EnglishUniversity Students
C13
214 משפטים
Data Structures Explained for Beginners - How I Wish I was Taught
Business EnglishInterview EnglishUniversity Students
אוצר מילים והערות הגייה לשיעור הזה
שיעור הדיבור הזה ברמה C2 מבוסס על הסרטון “Oracle database architecture explanation in details”. המילים שחוזרות הכי הרבה: file, database, process, log, buffer. בסרטון הזה יש 160 משפטים ו-1985 מילים לתרגול Shadowing. הדיבור נמשך 16:08. הדובר שומר על קצב יציב של כ-123 מילים בדקה, קצב נוח לתרגול Shadowing. רק 79% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית, כך שאוצר המילים מאתגר.
אוצר מילים מרכזי בסרטון הזה
13 המילים המתקדמות ביותר בסרטון, עם ההגייה והמשמעות שלהן:
| מילה | הגייה | משמעות |
|---|---|---|
| cache שם עצם | /kæʃ/ | מִצְבּוֹר, מַחְבּוֹא |
| execute פועל | /ˈɛksɪˌkjuːt/ | להוציא להרוג |
| syntax שם עצם | /ˈsɪn.tæks/ | תַּחְבִּיר |
| fetch פועל | /fɛt͡ʃ/ | הביא, השיג |
| dedicate פועל | /ˈdɛdɪˌkeɪt/ | הקדיש |
| dictionary שם עצם | /ˈdɪk.ʃəˌnɛ.ɹi/ | מִלּוֹן |
| listener שם עצם | /ˈlɪs(ə)nɚ/ | מַאֲזִין |
| password שם עצם | /ˈpæs.wɜɹd/ | סִיסְמָה |
| cleanup שם עצם | /ˈkliːnʌp/ | ניקוי |
| cement שם עצם | /səˈmɛnt/ | צֶמֶנְט |
| archive שם עצם | /ˈɑɹˌkaɪv/ | אַרְכִיּוֹן |
| insert פועל | /ɪnˈsɝt/ | לְהַכְנִיס |
| trunk שם עצם | /tɹʌŋk/ | גֶּזַע |
דקדוק בסרטון הזה
המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:
| מבנה | בסרטון |
|---|---|
| סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה | is called · is selected · is missed |
| משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דבר | database which has · monitor which is · process which is |
| הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו | has started · have explained |
הגייה ששווה לשים לב אליה
- הצלילים של “sh” ו-“zh”: cache /kæʃ/, optional /ˈɑp.ʃə.nəl/, dictionary /ˈdɪk.ʃəˌnɛ.ɹi/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/, optimization /ˌɑptəmaɪˈzeɪʃən/
- מילים ארוכות — שימו לב להטעמה: parameter /pəˈɹæm.ə.tɚ/, dictionary /ˈdɪk.ʃəˌnɛ.ɹi/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/, metadata /ˈmɛt.əˌdeɪ.tə/, optimization /ˌɑptəmaɪˈzeɪʃən/
צלילים שדוברי עברית מתקשים בהם:
- /w/ — שפתיים מעוגלות, לא /v/: query /ˈkwɪɹ.i/, password /ˈpæs.wɜɹd/
- /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: cache /kæʃ/, parameter /pəˈɹæm.ə.tɚ/, syntax /ˈsɪn.tæks/, dispatcher /ˈdɪs.pætʃ.ə(ɹ)/, validate /ˈvæl.ɪ.deɪt/
- /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: buffer /ˈbʌfəɹ/, oracle /ˈɔɹəkəl/, parameter /pəˈɹæm.ə.tɚ/, query /ˈkwɪɹ.i/, dictionary /ˈdɪk.ʃəˌnɛ.ɹi/
איך לתרגל עם הסרטון הזה
- הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
- תרגלו Shadowing משפט אחר משפט במהירות רגילה, וחזרו על כל משפט עד שהקצב שלכם תואם את הדובר.
- הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו cache, execute, syntax.
מהי טכניקת השאדואינג?
שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.