Oracle FAQ

What

is Oracle?

Linda Bryne

Advisory Consultant, SCT

Copyright 1993. This document containing copyrighted material and trademarked names (BANNER, ORACLE, SQL*Forms, Windows, etc.) and may not be used without permission of the same.
Contents:

1. What is ORACLE?

2. What is a database?

3. Who uses the information stored in a database?

4. What is a database management system (DBMS)?

5. What are the advantages of a database management system (DBMS)?

6. How many kinds (or models) of database management systems are there?

7. What is a relational database management system (RDBMS)?

8. What is the basic structure of the ORACLE database?

a. What is a table?

b. Is there more than one kind of table found in ORACLE?

c. How is data stored on tables?

d. What is the average size of a table in ORACLE?

e. Do tables have names?

9. How does the user communicate with ORACLE?

10. How does ORACLE retrieve information for the user?

11. How flexible is ORACLE in retrieving information for the user?

a. What is a view?

b. What is an index?

c. What is a cluster?

12. Who oversees the ORACLE database?

13. How does ORACLE present information drawn from its tables for the user?

a. What is a form?

b. How are forms structured?

c. How do forms relate to individual database tables in ORACLE?

d. Are forms similar to screens on a computer terminal?

e. Is every form in BANNER like this?

f. Do forms have names?

14. Where does ORACLE reside in relation to the campus computing applications?

15. How does ORACLE affect any application it supports?

a. Forms

b. Navigation Techniques

c. Security

d. Systems development and upgrades

16. What is GUI?

17. How are forms influenced by GUI?

a. visual presentation of information on a form

b. navigation on a form

c. speed at which users may learn the application

18. Is it important for any user to understand how ORACLE operates in order to use the application?

19. How much about ORACLE do users need to understand?

20. How can users best prepare themselves for training on an ORACLE-based information system?

1. What is ORACLE?

ORACLE is the registered trademark of the database management system which is the foundation for all BANNER applications (Student, Human Resources, Finance, Financial Aid, Alumni).

ORACLE is produced and market by ORACLE Corporation.

2. What is a database?

A database is an integrated collection of data items recorded and stored within any large organization such as a university or college.

Organizations may have one or more data bases depending upon their size and complexity and the types of data needed to be stored there. Data items held within a database are easy to store and can be retrieved easily by a wide variety of users.

For example, think of the data stored a local Public Library about the books found there. The library would need to record the names of all books, authors of those books, the library reference number of the location of the book on library shelves, the number of copies of each book, a list of books checked out, a list of books on reserve, etc.

Since books are taken out of the same library by patrons, they would also need a database of patron names, addresses, telephone numbers, books borrowed, date on which books were borrowed and returned, etc.

The same library may have another database which stores the names of all employees, their start dates, current position, current salary, etc.

3. Who uses the information stored in a database?

A wide variety of people within the organization use the information in the database: managers and other end-users like yourselves, technical personnel, and the database administrator who manages the overall use of the database.

4. What is a database management system (DBMS)?

A database management system is a software program which does the following:

a. store, retrieves, and modifies data

b. guards the consistency of the data

c. regulates access to the data to multiple users

d. solves "concurrency" problems or solves the problem of how to let multiple users access the data within the database quickly and easily

5. What are the advantages of a database management system (DBMS)?

The advantages of these systems are numerous:

a. establishes the structure or "game plan" of the database, which organizes the data stored within for a variety of users.

b. easily records, stores, and updates information within the database.

c. provides an easy way for both non-technical personnel (clerical staff) and technical personnel (programmers, systems analysts) to retrieve selected information.

d. provides a organized means of managing and protecting the data, which is

then shared amongst a wide variety of users.

6. How many kinds (or models) of database management systems are there?

There are three (3) main models of data base management systems:

a. hierarchical database (developed for use 1960's)

b. network database (developed for use 1970's)

c. relational database (developed for use 1980's)

Each model is designed differently, records and stores information differently, and retrieves that information for the user differently. Each model has its own strengths and weaknesses, and we will examine only at the relational database model here.

7. What is a relational database management system (RDBMS)?

A relational database management system stores its information in the form of tables and then links or "relates" those table to one another to provide answers to users' diverse questions.

Relational databases are a very powerful means of organizing the information within a database. The table-like structure ensures great flexibility and an inherent analytical capability which is advantageous for all users. Relational databases were invented around 1970 (Codd), but were not used until 1985 when computer technology caught up with the idea.

There are / were many relational database management systems on the market today such as ORACLE, DBase, RDB, Paradox, Focus, etc.

8. What is the basic structure of the ORACLE database?

ORACLE is composed of numerous tables, each of which contains different kinds of data.

a. What is a table?

A table is the basic data storage structure in ORACLE. It is a two-dimensional matrix composed of a number of vertical columns (categories of information listed across the top) with horizontal rows (individual cases). An example of this structure appears below:

COLUMNS

ROWS

The entire row of information in a table (comprised of several columns) is called a "record". Sometimes an individual column will be referred to as a "field".

b. Is there more than one kind of table found in ORACLE?

ORACLE is composed of a number of different kinds of tables. Typically, there are base tables, repeating tables, and virtual tables found in ORACLE. Some ORACLE tables are created temporarily when processing or presenting information.

Base tables record only one set of data per category. A variation of this is found in a repeating table, which records more than one set of data per category. For example, a student can only have one major declared per semester and so, this would be recorded on a base table. In the same semester, the same student can be registered in more than one class, so this would be recorded on a repeating table, since one class registration record represents one set of data.

Another kind of table is called a virtual table.

This will be explained further in Question 11a.

c. How is data stored on tables?

The records on a database table are stored in sequential order i.e. in order of data entry. Due to the flexible nature of a relational database, it is not necessary to store records in a particular order such as alphabetical or numerical. This concept will be explained further in the Questions # 10 and 11.

Each table always has a column which is denoted as the "primary key". The primary key column (or field) denotes the data element around which the remainder of the data on that table is organized. Each column (or field) name on the table must also be unique.

An example appears below of a table which could be used to record some basic information about dog breeds:

DOG Table

Breed_typ Group_name Group_num Cou_origin

Airedale Terrier 4 England

Rottweiler Working 3 Germany

Otterhound Hounds 2 England

Shih Tzu Toys 5 China

Cairn Terrier 4 Scotland

Papillon Toys 5 Spain

Briard Herding 7 France

Pointer Sporting 1 England

Viszla Sporting 1 Hungary

Mastiff Working 3 England

Bassett Hounds 2 France

Chow Chow Non-sporting 6 China

Lakeland Terrier 4 England

Here is another example of information for some of the same breeds. This table lists features of different breeds such as average weight, coat type, etc.

FEATURES Table

Breed_typ Coat_typ Avg_wt_male Avg_wt_fem Eye_col

Cairn Wiry 20 18 brown

Chihuahua Smooth 5 4 brown

Mastiff Smooth 150 130 black

Lakeland Wiry 15 14 brown Bassett Smooth 75 65 brown

As you can see, these two tables contain separate information pertinent to the subject of the table, and each has a different number of columns. The width of these columns varies, depending upon the width of the information being stored.

The typical relational database is composed of many of these tables; the number of tables varies per database, depending upon the complexity of the information stored and the nature of the database itself. For example, the BANNER Student database has over 100 tables, each of which stores some aspect of data.

d. What is the average size of a table in ORACLE?

The size of the tables in ORACLE (including number of columns and rows) usually vary depending upon the data being stored on them. Some tables are small, and perhaps have only four or five columns; others are larger, and have many, many columns.

The "length" of these tables varies as well, depending upon the number of individual cases recorded for that data element in the table. For example, the SPRIDEN table in BANNER which records the names of persons has numerous columns, and can have many thousands of individual rows or records, depending on the client site.

The "width" of each column is likely to be different depending upon the width of the information recorded in each. For example, the column in the SPRIDEN table in BANNER which houses the IDs can be up to 9 spaces in width; other data base columns are shorter, some are longer. It all depends on the nature of the data recorded in that column or field.

The order of the columns on a table is entirely irrelevant, as is the order of individual rows or records of information. This concept will be further explained in Question # 11.

e. Do tables have names?

Yes, each table has a unique name which denotes the type of data being recorded and stored on that table. There are naming conventions for these tables followed by ORACLE and adopted by SCT. (See Question 13e)

9. How does the user communicate with ORACLE?

All relational databases communicate with users via an intermediate computing language. ORACLE uses a 4th Generation Language (4GL) called SQL. SQL stands for Structured Query Language and acts as the means of communication between the database and all users, from technical to non-technical.

SQL is used to create, store, change, retrieve, and maintain information in ORACLE and can even be used by those users who are not extremely technical. Users pose questions to the database using SQL, much as they would in talking with a co-worker, rather than by using formal computing commands. There are many kinds of SQL and it provides a basic means of entering and processing data to ORACLE itself. SQL*Plus will be used as the example in this document.

10. How does ORACLE retrieve information for the user?

The potential to answer an unlimited number of queries is basic to ORACLE, even queries which were not thought of when the database was created.

Relational databases use each table within as a means of answering queries. Sometimes, the appropriate information to answer the query can be found in only one table. More often, ORACLE must go to two or more tables in order to retrieve the separate data elements which can answer the query -- in other words, relational databases often "relate" the tables to one another to provide the answer to queries.

The real power of a relational database lay in its ability to provide answers to almost every kind of query, even those not thought of when the database was originally designed or when the needs of users change over the course of time.

ORACLE does this by using each table as the basic building block for larger, more complex tables. Complex tables are created whenever the user needs to answer specific queries which draw information from more than one table. The connection between these complex tables is called a "join". Individual tables are joined together on a common column to build a complex table. The information in the complex table is then manipulated via SQL to provide answers to the user's queries.

For example, we will return to the two tables (DOG, FEATURES) shown in Question #8:

Breed_typ Coat_typ Avg_wt_male Avg_wt_fem Eye_col

Cairn Wiry 20 18 brown

Chihuahua Smooth 5 4 brown

Mastiff Smooth 150 130 black

Lakeland Wiry 15 14 brown Bassett Smooth 75 65 brown

Breed_typ Group_name Group_num Cou_origin

Airedale Terrier 4 England

Rottweiler Working 3 Germany

Otterhound Hounds 2 England

Shih Tzu Toys 5 China

Cairn Terrier 4 Scotland

Papillon Toys 5 Spain

Briard Herding 7 France

Pointer Sporting 1 England

Viszla Sporting 1 Hungary

Mastiff Working 3 England

Bassett Hounds 2 France

Chow Chow Non-sporting 6 China

Lakeland Terrier 4 England

Using the Dog table alone, we can ask ORACLE the following question:

Which types of dog breeds originated in France?

We may also request that ORACLE list these records in a particular order or to format the information in a particular way. You will notice that the ordering of the data in these tables in unimportant because SQL makes the data so easy to retrieve.

The above request would be phrased in SQL in the following manner:

SQL> select Breed_typ from DOG

where Cou_origin = ‘France'

order by descending;

ORACLE would retrieve the following records for you:

Briard

Bassett

2 records selected.

For an example of a query requiring information from 2 tables, it is necessary to "join" those tables to one another. Joins are usually made on a column common to both tables. The common column for the DOG and FEATURES tables is that called "Breed_typ". You will notice that the name of this column is the same in each table, as are the data elements listed within.

You may now ask a question of ORACLE which combines elements of each table:

"What are the breed names and eye colour of dogs with wiry coats?"

The combination of the data in these two tables accomplished via a join creates a complex table.

The amended SQL*Plus statement now resembles the following:

SQL> select breed_typ, group_name, eye_colour

from DOG, FEATURES

where dog.breed_typ = features.breed_typ

and coat_typ = ‘wiry'

order by breed_typ;

SQL would join the tables and locate the following dog breeds:

Breed_typ Group_name Eye_colour

Cairn Terrier Brown

Lakeland Terrier Brown

2 records selected.

There are many kinds of joins which can be performed in ORACLE; the example above showed an "equijoin", another type is defined as an "outer join" or a "non-equijoin" and involves combining 2 or more tables with disparate column (or field) values.

11. How flexible is ORACLE in retrieving information for the user?

One of the main determinants in ORACLE'S flexibility in retrieving information is in its use of SQL. Because communication between the database and its users is comparatively quick and easy due to SQL, the order of records in all tables becomes unimportant and all are stored in sequential order of their entry.

ORACLE is also flexible in the way it lets users view information held within its tables. One main function of all relational databases is to answer queries. The ability to retrieve information from one or more tables is critical to this function and ORACLE is designed with many features to make information storage and retrieval easier for all users. Three other examples of this flexibility are shown on the following pages:

a. What is a view?

ORACLE is extremely flexible in the way it lets the user view information held within its tables. For example, the user may view only part of the information housed within any table(s) by creating a "view" of that table (or tables). A view is like a window into the database through which you can look at specific information.

A view resembles a table, but does not exist as such, although the data included within the view are drawn from database tables. Views provide simplicity for the user in looking at only the information he/she needs at the moment, and security for the managers of that database.

Views are also called "virtual" tables because their structure is tabular and may be given distinct names. Users can create views from one or more tables, and then manipulate that view via SQL to provide answers to different queries.

An example (drawn for the DOG table) appears below:

SQL> create view Breed_typ, cou_origin as

select Breed_typ, cou_origin

from DOG;

The following tabular view would be created:

Airedale England

Bassett France

Briard France

Cairn Scotland

Chow Chow China

Lakeland England

Mastiff England

Otterhound England

Papillon Spain

Pointer England

Shih Tzu China

Rottweiler Germany

Viszla Hungary

The user can then perform more sophisticated queries based on the extracted information above.

Views save users much work in facilitating complex queries by first extracting the appropriate columns of information from separate database tables . For those managing database, views provide an extra layer of security, in that specific users can see a subset of information drawn from one or more tables, without seeing other, more sensitive data.

Note: this can also be achieved now through value-based security in ORACLE.

b. What is an index?

An "index" is another method used by ORACLE to facilitate information retrieval.

An index is a pre-defined search path to data in the database. Indexes are files in the database which contain two items: the address of each record in the table and the matching key column (or field). Indexes can be either unique or non-unique, depending upon the nature of the information recorded on the database table.

An example of an index created for the DOG table appears below:

SQL> create index dogn

on DOG(Breed_typ, Group_name)

Searching for a record in an unindexed table is time-consuming for both the user and the database, as the search proceeds in a sequential order, moving through the table record by record to locate the appropriate records. Think of an index as the highway through which the data moves from its table location to the user.

Another reason for indexes within a database is to maintain an optimum response time for all users. Response time is critical in ORACLE and indexing is necessary if everyone concerned, from the database administrator to programmers to users, want to obtain quick answers from the database.

c. What is a cluster?

Retrieving information easily and quickly from the database is also facilitated by physically placing tables containing logically associated records in close proximity to one another on the disk. This technique is called "clustering", and is the means by which ORACLE controls the physical placement of its tables, thereby facilitating any queries drawn from those tables because all related data is in one location in the database.

Think of a cluster in terms of the following analogy: for lunch one day, you decide to have a peanut butter and jelly sandwich with a glass of milk. The items required for this are: peanut butter, jelly, bread, milk, glass, knife, and plate. Because these items are logically associated with one another (food, utensils, flatware, glasses), they are most likely found in one part of your house (kitchen), making the assembly of this lunch relatively easy. Imagine how difficult or lengthy would the assembly of this sandwich would be if the knife were in the upstairs closet, the peanut butter in the garage, the bread in the utility room, etc.?

Clusters accomplish much the same thing, allowing the user to benefit from the close physical placement of this related data with the database.

There are two kinds of cluster: intrafile (involving one table only) and interfile (involving 2 or more tables). Users are unaware of clusters in the database, but they are aware of the response time it takes to answer their queries. Another advantage to clustering is the reduction of the amount of stored data in the database, thereby reducing redundancy.

12. Who oversees the ORACLE database?

The Database Administrator (DBA) is the individual responsible for organizing and maintaining the database and all data within used by the organization.

System Analysts are those individuals responsible for the development and implementation of specific applications such as BANNER Student, Human Resources or Finance.

Programmers (or developers) are those individuals responsible for supporting the application, from managing code which affects the processing of data to writing entirely new programs.

13. How does ORACLE present information drawn from its tables for the user?

ORACLE presents its information via technical tools such as SQL in a specific way meant to benefit both the users and the technical staff who maintain the database.

a. What is a form?

Forms are the traditional and most user-friendly means of displaying information for the user from ORACLE. Forms provide an intermediary between the user and SQL and are produced form information in the ORACLE database using a tool called SQL*Forms.

Think of the Identification Form (SPAIDEN, PPAIDEN, etc.) which is basic to most BANNER applications.

b. How are forms structured?

Each form is divided into areas of information (or "blocks" are they are sometimes still called) which contain fields of data. These areas are usually framed, so that the user can easily identify them. Sometimes, these areas correspond directly to a "window". This concept will be explained further in Question 17a.

Within each area are separate fields which correspond to individual columns on database tables. Behind the scenes, these fields retain their formal column names. Some fields are required, others are not. Information entered into a field on any form is called a "value" or "data element".

c. How do forms relate to individual database tables in ORACLE?

Behind each block on a form is the database table from which ORACLE draws the information which appears in that block. When a form is displayed, it presents fields which correspond to columns on the database tables, and text such as field names, form titles, etc.

Forms act as a structured "guide" to information held in the database. Using a form, users can quickly insert, change, delete or save information to the database tables. Users can also use forms to query information from the database, using the fields to enter search criteria, rather than phrase the query in SQL terminology. Behind each field on a form, a developer has written a SQL statement which extracts the information from the database table and presents it to the user.

d. Are forms similar to screens on a computer terminal?

Yes, a "form" is very similar to a screen, but has some very important differences:

1. forms may be more than one page in length, depending upon the information to be shown on them

2. can be two dimensional in that they may have "layers" of information (or "records" in ORACLE terminology) attached to them

For an example of this effect, we will refer to the Identification Form (SPAIDEN) in BANNER Student and examine it horizontally:

If one can imagine these layers (or records) sideways, one could perhaps "see" them more clearly. It is possible to denote that the Current Identification area has only one layer (or record), while the Previous Identification area can have more than one and the Address Information area can have numerous records.

Sometimes, the number of these records is unlimited. For example, although this is not likely to happen, the Previous Identification area can store hundreds of name changes for one person. Sometimes, the number of records is predetermined by the user. For example, perhaps the user has decided that no more than three address types will be stored per person record, other users perhaps four or five.

e. Is every form in BANNER like this?

Not every form in BANNER will have this layering effect, but users must get used to the idea that what you see is not all that you may get on any form. ORACLE will advise users if there are records below or above the one at which they are currently located, by displaying a caret (^ or v) in the form.

Although forms are usually narrow in content and focus, reflecting the nature of database tables in ORACLE, they can be used to present views to the user, drawing information from numerous tables in the database. Forms can have an unlimited amount of SQL coding behind the scenes which allows for information processing and are relatively easy to modify and maintain.

f. Do forms have names?

Yes, each form has two names assigned by SCT and personalized to the system in which they reside. The first is the actual name of the form such as the "Person Identification Form" or "Registration Query Form". The second is a seven-letter encoded name which may be similar to the name of the table in ORACLE on which the information is housed.

For example, the seven-letter encoded name of the Identification Form is in BANNER Student is SPAIDEN. These letters stand for the following:

S -- Student System (SCT markets many types of systems, including Student, Human Resources, Finance, etc.)

P -- Person (name of the module or sub-system in which a particular type of data is found).

A -- Application Form (BANNER has taken the basic idea of the form and elaborated on it to create 4 specific kinds of forms, each of which performs a specific function in their systems).

IDEN -- Identification (the last four letters are an abbreviation for the actual name of the form).

The seven-letter encoded name often provides the user with a shortcut to navigation.

As well, these seven letters often provide the user with an indication of the ORACLE table name as well. This is not always the case, there are many database tables in a BANNER application.

14. Where does ORACLE reside in relation to the campus computing systems?

ORACLE is an application usually mounted on the server or operating platform. This provides ORACLE with a foundation upon which to function. Without such a foundation, ORACLE simply could not exist.

15. How does ORACLE affect any application it supports?

Any application which utilizes ORACLE as its technical understructure is greatly affected by all aspects of this relational database, from the physical storage of data and its subsequent presentation as information, to the words used (form, area, and record), to the keystrokes users may choose to press. In a subtle way, all systems which use ORACLE are very much influenced by the definition and scope of ORACLE itself.

a. Forms

Each form is narrowly defined in reference to the function and scope of the database tables behind that form. The scope of the data being recorded is broken down thematically into its smaller parts and then presented on these forms. It is as though the information becomes "compartmentalized" in many ORACLE-based systems, and the user must look on a specific form in a specific part of the system to find what he/she needs.

BANNER has taken this viewpoint and elaborated on it when developing their systems. Users must become accustomed to the narrowness of each form, especially in terms of the function it performs within the entire system.

BANNER has integrated each form within the overall application, so that the processing of information is achieved, but the singular nature of these forms and their relation to the system at large may present a very different viewpoint than that to which some users are accustomed.

b. Navigation Techniques

Any BANNER application using ORACLE as its technical understructure, is entirely dependent upon a set of functions defined by ORACLE. ORACLE uses these functions in order to execute commands to the database. In these systems, users do not as much as point and click or press a key, but actually perform a function to the database by pointing and clicking or pressing a key -- this concept is at the core of navigation techniques in ORACLE.

There are a wide range of functions in use in ORACLE, but read-only users need only learn a subset of these to be able to function fully. Others users, who are able to enter, delete, or change data, may need to learn the full set.

Users will also notice the physical manifestation of these functions may vary, depending on whether or not the user is working within a full GUI environment. Frequently, a function may be performed using more than one method (see Question 15b). During training sessions, users are strongly cautioned to hone in on the function performed, rather than its physical manifestation, during any training sessions.

c. Security

Any application using ORACLE can take advantage of its security features. For example, users can be given read-only access to forms or can be given full access, including the ability to enter, change or delete data.

ORACLE security can allow those in charge of a particular system to define security to great depth, giving users access to the information needed to perform his/her jobs, while ensuring that other sensitive information is restricted from those who are not entitled to see it.

Views are another method of allowing a user to view some information form a table (or tables) in ORACLE, while still ensuring that other, more sensitive data on those tables is protected. It is common to find forms in the BANNER applications which have been created from views.

d. Systems development and upgrades

ORACLE is an extremely flexible database with which to work and it is possible to "customize" or further enhance these systems when developing and implementing them. Because ORACLE exists as a separate entity within any BANNER system, upgrades to it can include new versions of ORACLE, as well as the specific BANNER application.

16. What is GUI?

GUI stands for "Graphical User Interface". GUI allows users to enact functions or other options (including navigation) by pointing and clicking on an icon or button or by pressing a function key instead. Any users who has a PC with Windows usually has GUI capabilities.

17. How are forms influenced by GUI?

Forms are influenced by GUI in three basic ways:

a. visual presentation of information on a form

GUI changes the look of a form entirely, portraying information formerly housed in areas or blocks into "windows". A window still contains a number of fields and are analogous to a table in ORACLE, but the presentation is slightly different compared to a non-GUI form.

Windows often contain other features such as icons, scroll bars, dialog boxes, buttons, etc. All of these may enact specific functionality in ORACLE or within the BANNER application. Sometimes windows are separated into areas or blocks still, sometimes not.

There is often more than one window attached to a form. The primary (or first) window viewed when the form is accessed is call the "root window".

Other windows accessed from this root window are called "branch windows".

b. Navigation on a form:

In a non-GUI environment, navigation is done solely by keystroke. However, one of the enormous advantages of GUI is that it allows users to enact functions against the database using any one of the following ways:

1. point and click

2. scroll bar

3. keystroke

4. icon

GUI does not change the basics of navigation in ORACLE, but allows the user to personalize navigation for himself / herself. For example, the user still performs a NEXT BLOCK function to move down a form from the root window onto branch windows. But, the actual manifestation of those functions is now different and the user may choose whichever best suits his / her needs or wishes.

c. Speed at which users may learn:

GUI is an extremely visual medium and one with which many users are probably already familiar. Anyone with a PC probably has used or is now using Windows. The visual nature of Windows can greatly assist users in learning BANNER.

As well, because users can perform ORACLE functions in a medium already familiar, navigation can be easier to learn and understand.

17. Is it important for any user to understand how ORACLE operates in order to use a BANNER application?

Yes, it is important for even the most casual user of a BANNER system to understand ORACLE, what it does, how it does it, why it does it, why information appears the way it does, etc. These systems are very, very ORACLE dependent.

Understanding that ORACLE is a separate entity with its own characteristics assists the user in conceptualizing and understanding these applications as a whole and ensures that the user does not just learn BANNER by rote.

For those users involved with developing these systems on-campus, a good understanding of ORACLE becomes critical. And, a user's understanding is better if they do understand some of the basics of ORACLE.

Furthermore, understanding BANNER applications "from the inside out" will give that user a very good idea as to what they are capable of doing or what kind of functionality is possible.

18. How much about ORACLE do users need to understand?

In order to use any ORACLE-based information system, most users need to understand the basics about ORACLE, including the following:

a. the organization of data within in a tabular format, including the way ORACLE stores and retrieves data.

b. the physical presentation of this data for users on forms, broken down into root and branch windows.

c. the nature of forms, including the scope of the information contained, their relation to individual database tables within ORACLE, and how these forms integrate within the BANNER application at large.

d. the kind of information processing performed by the entire BANNER application.

e. the various functions of ORACLE which are manifested on the various forms within the BANNER application.

19. How can users best prepare themselves for training on an ORACLE -based information system?

Any user who will be attending functional raining should do the following:

a. Do NOT be intimidated by the idea of training --- try to relax and look upon training as a tour to someplace new, where things are done differently than at home.

This is important because these systems may be conceptually different from those used previously on-campus and this alone can make some people apprehensive.

b. Do not try to remember everything covered in the training sessions, but do take notes on anything you feel is important. There is usually a great deal to cover in these sessions, so remembering absolutely everything is not realistic, especially when the concepts of these information systems are new to many users on-campus.

c. During the course of the training, try to make mental references to the in-house system and think of how BANNER's information relates to what you had before.

d. Be sure to ask questions if necessary --- if you are unsure about anything, ask the trainer to explain it again or clarify you understanding. Each portion of training acts as a foundation upon which the rest of the rests and so, make sure your understanding is progressive and that you comprehend as much as possible.

e. Do not worry about learning the various functions at the same time as learning what the forms do and the processing performed by the entire system.

Navigation skills may and should be treated as a separate issue in training. And, the Auto Hint in BANNER can explain what function you perform at a specific time to do navigate, access information on a form, etc.

f. Try to look at the "big picture" of navigation skills and do not try to associate navigation functions as attached to specific forms, but as techniques which are common to all forms in these systems. And remember, keystrokes can be learned quickly once you actually begin to use the system concerned.

g. Always try to aim for the "big picture" in training -- try to understand how the forms integrate into the entire system, the kind of processing these forms do within the scope of the BANNER Application. These systems are integrated, and your approach to training should be as well.

h. Be proactive in training ---- all ORACLE-based information systems demand that the user be pro-active in learning them. Look upon training as invested time and try to get as much from it as possible. And be prepared for an intensive week in terms of learning new things.