Study your flashcards anywhere!

Download the official Cram app for free >

  • Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key


Play button


Play button




Click to flip

28 Cards in this Set

  • Front
  • Back
  • 3rd side (hint)
Complete this SQL statement so that you can view whether you have any contention on your rollback segments:
SQL> SELECT class, count
2 from "x" (enter x variable in answer)
3 WHERE class IN
The advantage of small rollback segments is that they tend to remain what?
For OLTP, try to create many small rollback segments of perhaps "x" size and with "y" # of extents. (optimally with a rollback segment available for each transaction).
x=10kb-20kb size, y=2-4 extents
The small size of the rollback segments provides for a better chance of being cached in the SGA. There is probably very little dynamic growth of the extents.
For long queries, a good rule of thumb is to create rollback segments approximately x% the size of the largest table.
(most SQL statements affect only about x% of the data in a table).
It's is appropriate to create rollback segments approximately x% the size of the largest table.
For transactions that update large amounts of data, you should also use a larger rollback segment.
Which of the following is an advantage to using small
rollback segments?
More likely to remain cached in the SGA
In general, you can obtain the best performance of rollback I/O when there are approximately "x" # of extents of equal size per rollback segment.
x=10 to 20
As stated earlier, you want to avoid the dynamic space management that causes additional overhead and transactional delays. To determine whether rollback segments are a problem, look in this dynamic performance table?
This type of extent is defined as extents with uncommitted transaction data.
The number of times the rollback segment decreased in size. Each decrease may be one or more extents at a time.
using v$rollstat query output, if the average rollback extent size is close to the size set for "x", then "x" is set correctly. If either extends or shrinks is high, you must increase the value for "x".
In user accounts, "x" is used to assign privileges that allow the user to access different objects and operations, while "y" is used to control the amount of system resources that the user is allowed to consume.
x=role, y=profile
You can create user accounts using these 3 methods?
Enterprise Manager, Security Manager, or the CREATE USER command
You must have this system privilege to create a new user.
create user
There is little you can do with the CREATE USER command that you cannot do with the graphical tools except
You must have the this system privilege to modify a user account.
alter user
Where privileges are given via the "x", limitations on the user are typically assigned via the "y".
x=role, y=profile
These are created as an easier way of setting limitations on users.
how many profiles can a user be assigned?
primary way of allocating system privileges to the user community
Add Privileges to Roles is available by right-clicking on a role in which graphical utility?
security manager
Use this command to assign roles or system privileges to roles or users.
This command is just the opposite of the GRANT command; it will take a role or system privilege away from a user or role.
use this command to completely take away a role from the system.
works with the GRANT command to specify that the grantee has the right to pass this role or system privilege to any other user or role in the system.
with admin option
The Oracle sequence generator can generate sequential numbers of up to how many digits, without having to manually lock records
Sequences are incremented as they are accessed, independent of rollback or commit. If a transaction generates a sequence and then rolls back, the sequence is not replaced. This is referred to as?
sequential value holes
It can be efficient to use cached sequences to generate unique?
primary key values