Release 1 (9.0.1)
Part Number A90120-02
 Home |
 Book List |
 Contents |
 Index |  Master Index |  Feedback |
| Oracle9i Database New Features Release 1 (9.0.1) Part Number A90120-02 |
|
This chapter lists features and functionalities of the Oracle database server that have been desupported or are planned to be desupported. It contains the following sections:
This chapter contains a summary of deprecated and desupported features for Oracle9i. It also contains a summary of deprecated and desupported features in Oracle8 and Oracle8i for users who are migrating directly from Oracle7, or Oracle8, to Oracle9i.
Desupported features are features that are no longer supported in a release. Deprecated features are features that are not recommended for use because they are planned for desupport in a future release.
This section contains the following topics:
The DBMS_STATS package should be used to collect optimizer statistics instead of the ANALYZE statement. The ANALYZE statement may be desupported in a future release.
CONNECT INTERNAL and CONNECT INTERNAL/PASSWORD are not supported in Oracle9i. Instead, the following are the exact equivalents:
CONNECT/ as SYSDBA CONNECT username/password AS SYSDBA
Server-side support for the client-side REP80.DLL has been removed. This DLL enabled replication between Oracle server and Oracle Lite. See the Oracle Lite documentation for information about replacement functionality.
If a temporary tablespace has not been created for a user, Oracle must have somewhere to store temporary data for that user. Historically, Oracle has used SYSTEM for default temporary data storage.
In Oracle9i, users are encouraged to define a default temporary tablespace when creating the database. If this is not done, SYSTEM will still be used for default temporary storage. However, a warning will be shown in the alert log saying that a default temporary tablespace is recommended, and may be necessary in future releases.
The INCREMENTAL functionality of Export/Import is being deprecated. This functionality exports an entire table if any row in the table has changed since the last INCREMENTAL export.
Users can still use the Export utility to selectively export tables. However, tables to be exported must be specified. Tablespace backups can be used if users want to backup specific tablespace, and not the entire database or schema, and if each table is placed in its own tablespace. A tablespace backup or recovery is faster than the equivalent table export or import.
The NCHAR datatypes (NCHAR, NVARCHAR2, NCLOB) have been redefined in Oracle9i to be exclusively Unicode datatypes. You can store Unicode characters into columns of these datatypes regardless of the database character set.
National character sets for Unicode datatypes (NCHAR, NVARCHAR2, and NCLOB) are limited to AL16UTF16 or UTF8. The default character set is AL16UTF16.
Also, the AL24UTFFSS character set has been replaced by the UTF8 character set.
The following Oracle Net Services (formerly Net8) features are not supported in Oracle9i:
protocol.ora file
OPEN
The desupport of these features allows configuration decisions for the Internet to be streamlined.
In future releases, Oracle Names will not be supported as a centralized naming method. Because no new enhancements are being added to Oracle Names, consider using directory naming or migrating an existing Oracle Names configuration to directory naming.
In Oracle9i, the traditional method of user-managed tablespace point-in-time recovery (TSPITR) that used a clone database is deprecated. Only user-managed TSPITR with the transportable tablespace option is supported. Users are encouraged to use the transportable tablespace feature (TTS) to accomplish tablespace point-in-time recovery.
The relational geometry model of Oracle Spatial will not be supported in a future release. Only the object relational model will be supported.
Information about the relational model has been removed from the Oracle Spatial User's Guide and Reference and placed in a separate manual, Oracle Spatial Relational Model Guide and Reference, which is available on the Oracle Technology Network. Users should immediately begin using the object-relational model.
Server Manager is not supported in Oracle9i. Use SQL*Plus instead. Most Server Manager scripts should work in a SQL*Plus environment, but some scripts may need to be modified.
Single-task linking and non-deferred linking are not supported in Oracle9i.
The FOR RECOVER clause of ALTER TABLESPACE ... OFFLINE has been deprecated. The syntax is supported for backward compatibility. However, users are encouraged to use the transportable tablespaces feature for tablespace recovery.
Use the VARCHAR2 datatype instead of VARCHAR. The semantics of the VARCHAR datatype may change in a future release.
Oracle Visual Information Retrieval is not available in Oracle9i, and has been replaced by other image matching technology. In Oracle9i, image matching capability is available as part of interMedia.
Existing Visual Information Retrieval (VIR) applications will continue to be supported, but customers must convert the signature data and regenerate signature indices. Continued operation is facilitated by a VIR-compatible API that is implemented upon the new image-matching API. The VIR-compatible API is recommended for existing applications only and may be desupported in a future release. All new applications should be built using the interMedia image-matching API.
This section contains:
ALWAYS_ANTI_JOIN
ALWAYS_SEMI_JOIN
JOB_QUEUE_INTERVAL
OPTIMIZER_PERCENT_PARALLEL
HASH_MULTIBLOCK_IO_COUNT
DB_BLOCK_LRU_LATCHES
DB_BLOCK_MAX_DIRTY_TARGET
SORT_MULTIBLOCK_READ_COUNT
DB_FILE_DIRECT_IO_COUNT
GC_DEFER_TIME
GC_RELEASABLE_LOCKS
GC_ROLLBACK_LOCKS
LM_LOCKS
LM_RESS
USE_INDIRECT_DATA_BUFFERS
ROLLBACK_SEGMENTS
FAST_START_IO_TARGET
TRANSACTIONS_PER_ROLLBACK_SEGMENT
LOG_CHECKPOINT_INTERVAL
DB_BLOCK_BUFFERS
BUFFER_POOL_KEEP
BUFFER_POOL_RECYCLE
This section contains the following topics:
A string of zero length ('') is not equivalent to a NULL value. According to the ANSI SQL 1992 Transitional standard, a zero-length or empty string is not the same as NULL. Ensure that applications do not treat empty strings and NULL values equivalently.
In Oracle7, a space or punctuation character in the format string caused the corresponding character in the date string to be discarded. This caused incorrect dates to be entered into the database because alphanumeric characters were thrown out. In Oracle8i, an error occurs if an alphanumeric character is found in the date string when a punctuation character or space is found in the format string, as illustrated in the first row of the following table. The second row of the table displays an exception to the rule; the exception may be removed in future releases.
| SQL Syntax | Oracle7 Result | Oracle8 Result |
|---|---|---|
|
|
|
|
|
|
|
|
Also, Oracle8 allows matching of certain dates which produced an error in Oracle7. This matching occurs only when the correct date can be determined without ambiguity. However, this matching does not occur if the format model modifiers FX or FXFM are used.
The new matching rules are:
The following example yields the result 05/25/1905 in Oracle8:
TO_CHAR(TO_DATE('May 25, 1905', 'MM/DD/RRRR HH:MI:SS'), 'MM/DD/RRRR')
The SELECT privilege may be required on tables that users update. Always grant the SELECT privilege to a user or role if you grant the UPDATE or DELETE privileges on the table.
|
See Also:
Oracle9i Database Reference and its discussion of the |
The initialization parameter SERIALIZABLE=TRUE is not supported in Oracle8. The default behavior henceforth is as if SERIALIZABLE was set to FALSE. Use the SET TRANSACTION ISOLATION LEVEL SERIALIZABLE statement to achieve similar transaction isolation behavior.
BSTAT/ESTAT is not up to date with many of the new features introduced since 8.0, and eventually will be desupported.
Users who require help for performance tuning, and are running any release above Oracle 8.0, are asked to provide Statspack output rather than BSTAT/ESTAT. Statspack is much easier to interpret, provides more detailed information, and makes tuning faster and more effective.
Partition views are desupported in release 8.1.6. Instead, use partitioned tables.
In releases prior to Oracle8, the table_collection_expression clause was expressed as "THE (subquery)". That usage is desupported.
The contents of this file have been deleted, but the file remains because its existence is required by the Oracle database server. Do not delete this file. It may be desupported in a future release.
LONG columns may be desupported in a future release. You are advised to migrate LONG data into LOB columns.
The Oracle Security Server and Cryptographic Toolkit products do not exist in Oracle8i and later, however their functionality has been integrated into Oracle Advanced Security and Oracle Internet Directory.
|
 Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. | | Ad Choices. |
|