| administration
and manageability enhancements |
| Create
database enhancements: |
|
|
|
 |
SYS and SYSTEM
passwords can now be specified as part of the CREATE DATABASE statement. |
|
| Logging: |
|
|
|
| You
can force logging on tables and other objects at database,
controlfile and tablespace level,
overriding any nologging options specified at a lower level. |
|
| Locally
managed SYSTEM tablespace: |
|
|
|
| The
SYSTEM tablespace can now be managed locally, either from
the start in the CREATE DATABASE
statement or through migration using DBMS_SPACE_ADMIN. However,
for this to work you need to specify a default temporary
tablespace other than SYSTEM on creating
the database and also have a locally managed tablespace for your
rollback segments (which is normal when using
the automatic undo feature introduced in
9i Release 1). |
|
| File
Monitor: |
|
|
| To cope with the
increasing complexity of file storage systems, Oracle now provides a means of mapping files
to immediate storage layers and physical devices for I/O monitoring purposes. This feature
is implemented through a new background process (FMON, File Monitor); a new PL/SQL package,
DBMS_STORAGE_MAP and several new data dictionary views. The FMON process interacts with
Operating System-provided mapping libraries (described in the new filemap.ora file) to
facilitate the mapping process. |
|
| Auditing: |
|
|
|
| The SYS user
can now be audited like any other user. |
|
| Object
privileges: |
|
|
|
| The GRANT ANY
OBJECT privilege enables other users to grant privileges on someone else's objects. |
|
| Rename
features: |
|
|
|
| Columns and constraints
can now be renamed. |
|
| Obsolete
parameter: |
|
|
|
| The
DISTRIBUTED_TRANSACTIONS init.ora parameter has been made obsolete. |
|
| |
<<
previous page |
|
next
page >> |
|