A table space can only belong to a database
There is a minimum of a control file for each database (suggest 3, which is placed on different disks)
There is a minimum of a table space per database (System table space)
The purpose of establishing the SYSTEM table space is to try the same table as possible to improve the efficiency of use, and should only store data dictionary.
There are fewer online log groups for each database, each set of one online log file
A data file can only belong to a table space
Once a data file is added to a table space, it is no longer removed from this table space, and can no longer be added to other tablespaces.
Establish new tablespace needs to create new data files
After commit, the data is not necessarily written immediately (data files)
An a transaction will be written to the redo log even if it is not submitted.
Oracle Server can start multiple databases at the same time
A plurality of version of the Oracle database system can be installed on a set of operating systems (UNIX can, NT can not be)
A set of Oracle database systems can have multiple Oracle databases and their corresponding instances
How do I start learning Oracle HOW Do I get started with oracle?
THIS is Actually A Fairly Common Questions and not one what is offen addressed adequately. The folload is the, slightly edited text of a reply Sent by Howard Rogers
www.dizwell.com to someone who asked this exact question. The post is so good, that with Howard's permission I reproduce it here. The 'here' referred to below is the usenet group comp.databases.oracle.server which can be reached Via The Link on The Left Or Via Your Favourite NewsReader.
Be patient. You're starting from scratch, so there's a lot to learn, and much of it may seem very strange to begin with. Visit The online documentation set to get access to the latest Oracle documentation (though your CD set will probably include .. already) Read the official Concepts Guide Then visit sites such as that maintained by Jonathan Lewis, and Ask Tom Visit Google and hunt around for advice Take nothing on face value:.. test it yourself to destruction lurk here for a month. or two, and try and pick up on the sort of questions being asked, and ask yourself how * you * would answer them. Then see what answers actually come through, and compare. When you're feeling brave, post some of your answers And see how it is beken by people.buy books. Anything with the name
Jonathan Lewis, OR
Thomas Kyte on the cover are * extremely * good bets for accurate advice. O'Reilly are good. As are Apress (used to be Wrox) Avoid anything that mentions OCP (Oracle Certified Professional). The qualification is not worth a damn, and Leads you straight into myth territory.
If you can afford an Oracle training course (most people can not), go. Go to DBA Fundamantals I if you can ... the architecture stuff they cover on that is extremely good (but you play Russian Roulette with the instructor you get . If the guy starts reading from the course notes in the first hour, then leave and ask to be scheduled with someone else at a later date). DBA Fundamentals II is quite good, but is light on networking, and the Backup and Recovery stuff is not difficult. Do not bother with Performance Tuning, because it's a badly-written course that addresses none of the real issues. I think the general thing is to get involved and to get communicating, and you've already started that by posting here. Just do not stop now.The other general thing is to test and test and test, and verify for yourself. Experiment, and stuff the consequences. The other thing I would suggest, given your background, is that you learn Oracle at The Command Line, And Learn * Oracle *. Worry About Putting A GR aphical front-end app. on top of Oracle later. When you've got command-line Oracle sorted, the graphical front-ends will come as second nature, and will be better for the understanding you have of the back-end architecture and INNER-WORKINGS.
