Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
In this lesson, we continue with the creation
of an Oracle database.
We've put in our password information.
And we click Next.
Our next option is for Listener Selection.
So we've already configured a listener called
listener running on port 1521.
And that status is up.
And so that's the listener that it wants to use.
And we will allow it to do so and leave that selected.
Click next.
Now, we come to the portion where
we choose a lot of the configuration parameters of how
the database will be stored.
So if we click this dropdown, notice
that we have a couple of options for storage type,
either File System or Automatic Storage Management.
So ASM is Oracle's file system for databases.
And that requires a separate installation
of the grid infrastructure, which is the software that's
used for RAC.
We can use ASM without running RAC,
but it does require us to install all of that framework.
So a lot of times, that's not done as often
as just installing it to a file system.
We can use database file locations from a template.
But we're going to choose Use Common Location
for All Database Files.
And that location will be in the Oracle base directory /oradata.
We can browse and choose somewhere else if we wish.
But that will be satisfactory.
We also want to click Use Oracle-Managed Files.
That's going to give us the option of allowing Oracle
to size our database files to allow
them to automatically extend and really manage
a lot of the day-to-day aspects of data file management.
So that's the database file section.
Now we have the Recovery Related Files Section.
And this is something that's really new in 12c, at least
this part of the DBCA process.
It defines this a little more specifically
than it did in previous versions of the DBCA.
So again, we have storage type of either putting our recovery
area on ASM or File System, which we'll leave.
We do have the option of just not specifying a Fast Recovery
Area at all.
But we'll leave that selected.
So the Fast Recovery Area is just a directory
that Oracle defines to hold all of the Recovery Related Files--
so backup files, image copy backup files,
archive log files.
All of those types of files are kept
in one place for easy access and for safety.
Rather than having those files spread
all over the file system, it keeps them all in one place
and manages them.
Now, we also need to specify this size for the Fast Recovery
Area.
So it has it as being 4815 megabytes.
So that will be adequate for us.
If we did have a database that required more than that--
so we did lots of backups and we wanted to keep lots
of backups--
we might need to increase that.
Click Next.
Next is the Database Components section,
of the options that we have.
If we've installed these options as a part of the Enterprise
Edition, we have the option here of including all
of the tables, views, indexes--
all of the schema components that
go along with those options.
Now, what I'm going to do is deselect most of these.
Because they're really not necessary for our purposes
and they can create a lot of clutter in the database.
I'm going to go ahead and leave the JVM running here.
But next, I'm going to click the Sample Schemas.
The Sample Schemas make it easy to do
some simple select statements.
It has some basic database tables that we could play with.
So they're a useful thing to have.
From a security standpoint, however, we
wouldn't want to put them in an actual company database
because they are accounts that are known.
And so that lends itself to poor security framework.
But for our purposes, we want to include those.
It's a bug in the installer-- or the DBCA, rather--
that the sample schemas are not allowed to be selected.
So what we're going to do is, we're
going to go down to this Custom Scripts.
And we're going to actually find the script in the database
installation that creates these scripts.
So I'm going to click Browse.
This is going to take us to the Oracle base directory.
Click product, 12.10, dbhome_1.
And we want to go over to a directory called RDBMS.
Then, the directory ADMIN.
We want to go all the way over to find
a script called utlsampl, or utl sample dot SQL.
So that's the full directory.
Click next.
Next, we have options about how we will size this in memory.
So how much memory are we giving to Oracle to run this database?
This is going to run by default based
on a percentage of the available memory that the machine has.
So this machine has about 8 gigabytes of memory.
It's going to take 40% to run Oracle.
I'm going to scale this back a little bit.
For the purposes of a learning database,
we really don't need to use quite that much memory.
I like to put it around 2 gig.
We have a lot of options here as far
as using automatic memory management.
We'll allow Oracle to decide how memory is distributed.
We also have some custom settings here
where we can specify our own sizes for memory.
For our purposes, we'll take kind
of what the defaults have given us here for an SGA and a PGA.
Next, we want to click the Sizing tab.
This asks us what the size of our database block should be.
We have different options here.
The default is 8192.
And that is good for a default. Processes
is the number of processes that can run on the database.
That default is good as well.
Character Sets, we'll use the default.
But we have lots of different options for our character sets
if we needed language support for other languages.
Connection Mode tab gives us an option for dedicated server
or shared server mode.
Shared server mode can be used in situations
where the resources of the machine
itself are pretty restricted.
We'd prefer to use dedicated server mode because it
has superior performance, generally speaking.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.