8 Deprecated and Desupported Features for Oracle Database 12c

Oracle Database 12c introduces behavior changes for your database in addition to new features. Changes in behavior include deprecated and desupported initialization parameters, options, syntax, and the deprecation and desupport of features and components. This chapter does not describe new features introduced in Oracle Database 12c, nor does it describe changes in earlier releases of Oracle Database.

This chapter describes behavior changes where features have been deprecated or desupported in this release. By deprecate, we mean that the feature is no longer being enhanced but is still supported for the full life of the 12.1 release. By desupported, we mean that Oracle will no longer fix bugs related to that feature and may remove the code altogether. Where indicated, a deprecated feature may be desupported in a future major release. For more information about support considerations, refer to My Oracle Support at http://support.oracle.com.

This chapter contains the following topics:

See Also:

8.1 Oracle Database Changes

Oracle Database 12c introduces changes that affect Oracle Database in general.

This section contains these topics:

8.1.1 Deprecation of Non-CDB Architecture

The non-CDB architecture is deprecated in Oracle Database 12c, and may be desupported and unavailable in a release after Oracle Database 12c Release 2. Oracle recommends use of the CDB architecture.

Note:

There remain a small number of features that do not work with the CDB architecture (see README, section 2.2.1 "Features Restricted or Not Available for a Multitenant Container Database"). If you need these features, then continue to use the non-CDB architecture until your required feature works with the CDB architecture.

8.1.2 Deprecation of catupgrd.sql Script and Introduction of New catctl.pl Utility

Oracle Database 12c introduces the new Parallel Upgrade Utility, catctl.pl. This utility replaces the catupgrd.sql script that was used in earlier releases. Although you can still use the catupgrd.sql script, it is deprecated starting with Oracle Database 12c and will be removed in future releases. Oracle recommends database upgrades be performed with the new Parallel Upgrade Utility, catctl.pl.

If you choose to run the catupgrd.sql script instead of running catctl.pl, doing so now requires an additional input parameter as follows:

SQL> catupgrd.sql PARALLEL=NO

If you run catupgrd.sql without the parameter, then Oracle displays the following error message:

NOTE
 
The catupgrd.sql script is being deprecated in the 12.1 release of 
Oracle Database. Customers are encouraged to use catctl.pl as
the replacement for catupgrd.sql when upgrading the database dictionary.
 
                cd $ORACLE_HOME/rdbms/admin
                $ORACLE_HOME/perl/bin/perl catctl.pl -n 4 catupgrd.sql
 
Refer to the Oracle Database Upgrade Guide for more information.
 
This database upgrade procedure must be called with the following
argument when invoking from the SQL prompt:
 
                @catupgrd.sql PARALLEL=NO

See Also:

"About the Parallel Upgrade Utility for Oracle Database" for information about catctl.pl and how to run it

8.1.3 Desupport of Oracle Enterprise Manager Database Control

Starting with Oracle Database 12c, Oracle Enterprise Manager Database Control is desupported and is no longer available. Oracle introduces Oracle Enterprise Manager Database Express (Oracle EM Express) as a replacement. Oracle EM Express is installed when you upgrade to Oracle Database 12c.

See Also:

8.1.4 Changes for Deinstallation and Cleanup of Oracle Base

The following topics discuss changes for deinstallation and cleanup of Oracle Base:

8.1.4.1 Change for Standalone Deinstallation Tool

Starting with Oracle Database 12c, the deinstallation standalone utility is replaced with a deinstall option using Oracle Universal Installer (OUI). You can also run the deinstallation tool using the runInstaller command on Linux and UNIX (or setup.exe on Windows) with the -deinstall and -home options from the base directory of the installation media for Oracle Database, Oracle Database Client, or Oracle Grid Infrastructure.

See Also:

8.1.4.2 Desupport of CLEANUP_ORACLE_BASE Property

In Oracle Database 12c, the CLEANUP_ORACLE_BASE property is removed and does not support an Oracle base removal during silent or response file mode deinstalls.

8.1.4.3 Deprecation of -cleanupOBase

The -cleanupOBase flag of the deinstallation tool is deprecated in this release.

See Also:

Oracle Database Installation Guide for your operating system

8.1.5 Deprecated and Desupported Parameters

In Oracle Database 12c, some database parameters are deprecated and desupported, or removed.

To obtain a current list of deprecated parameters, run the following query in SQL*Plus:

SQL> SELECT name from v$parameter 
         WHERE isdeprecated = 'TRUE' ORDER BY name;

The query returns a list of the deprecated parameters as of the date and time that you run it. The following example shows the query results that appear:

active_instance_count
background_dump_dest
buffer_pool_keep
buffer_pool_recycle
commit_write
cursor_space_for_time
fast_start_io_target
global_context_pool_size
instance_groups
lock_name_space
log_archive_start
max_enabled_roles
parallel_automatic_tuning
parallel_io_cap_enabled
parallel_server
parallel_server_instances
plsql_v2_compatibility
remote_os_authent
resource_manager_cpu_allocation
sec_case_sensitive_logon
serial_reuse
sql_trace
standby_archive_dest
user_dump_dest

8.1.5.1 LOG_ARCHIVE_LOCAL_FIRST

The LOG_ARCHIVE_LOCAL_FIRST initialization parameter is removed and desupported in Oracle Database 12c.

8.1.5.2 SEC_CASE_SENSITIVE_LOGON

The SEC_CASE_SENSITIVE_LOGON initialization parameter is deprecated in this release. See Oracle Database Reference for information about the SEC_CASE_SENSITIVE_LOGON initialization parameter.

8.1.5.3 FILE_MAPPING

The FILE_MAPPING initialization parameter is deprecated. It is still supported for backward compatibility. See Oracle Database Reference for information about the FILE_MAPPING initialization parameter.

8.1.5.4 DELETE_CATALOG_ROLE of the O7_DICTIONARY_ACCESSIBILITY Parameter

The DELETE_CATALOG_ROLE role is deprecated in Oracle Database 12c. See Oracle Database Reference for information about this role and dictionary objects.

8.1.5.5 RDBMS_SERVER_DN

RDBMS_SERVER_DN is deprecated in release 12.1.0.2. LDAP_DIRECTORY_ACCESS should be used instead. See Oracle Database Reference for information about this parameter.

8.1.6 Deprecated Views

The following views are deprecated in Oracle Database 12c:

See Also:

Oracle Database Administrator's Guide for information about specifying Scheduler job credentials

8.1.7 Deprecation of Oracle Streams

Oracle Streams is deprecated in Oracle Database 12c and may be desupported and unavailable in a later Oracle Database release. Use Oracle GoldenGate to replace all replication features of Oracle Streams.

Note:

Oracle Database Advanced Queuing is independent of Oracle Streams and continues to be enhanced.

See Also:

Oracle GoldenGate documentation for information

8.1.8 Deprecation of Advanced Replication

Oracle Database Advanced Replication is deprecated in Oracle Database 12c. Use Oracle GoldenGate to replace all features of Advanced Replication, including multimaster replication, updatable materialized views, hierarchical materialized views, and deployment templates.

See Also:

Oracle GoldenGate documentation for information

8.1.9 Deprecation of Single-Character SRVCTL CLI Options

The Server Control Utility (SRVCTL) command line interface (CLI) supports long GNU-style options in addition to short CLI options used in earlier releases. Starting with Oracle Database 12c, single-character options are deprecated and may be desupported in a later release.

8.1.10 Desupported Features on Microsoft Windows Platforms

In Oracle Database 12c, some features have been deprecated or desupported for the Windows platform. The following topics discuss these changes:

8.1.10.1 Desupport of Oracle COM Automation on Windows

Oracle Database 12c does not contain Oracle COM Automation. This was deprecated in Oracle Database 11g, which is the last database release that contains the database component Oracle COM Automation. Oracle recommends that you migrate your Oracle COM applications to current technology such as the .NET Framework.

See Also:

My Oracle Support Note 1175293.1 "Obsolescence Notice: Oracle COM Automation" on http://support.oracle.com

8.1.10.2 Desupport of Oracle Objects for OLE

Oracle Database 12c does not contain Oracle Objects for OLE. This was deprecated in Oracle Database 11g. You can migrate your code to the OLE DB data access standard and ActiveX Data Objects (ADO), or you can migrate your applications to .NET (or Java or another application architecture) and use another driver.

See Also:

My Oracle Support Note 1175303.1 "Obsolescence Notice: Oracle Objects for OLE" on http://support.oracle.com

8.1.10.3 Desupport of Oracle Counters for Windows Performance Monitor

Oracle Database 12c does not contain Oracle Counters for Windows Performance Monitor. This was deprecated in Oracle Database 11g. The counters were not installed by default in earlier releases, and the counters only work on Windows. For monitoring, Oracle recommends that you use Oracle Enterprise Manager Cloud Control.

See Also:

My Oracle Support Note 1175297.1 "Obsolescence Notice: Oracle Counters for Windows Performance Monitor" on http://support.oracle.com

8.1.10.4 Changes for Oracle Data Provider for .NET

The following Oracle Data Provider for .NET application programming interfaces for Transaction Guard are deprecated in Oracle Database 12c (12.1.0.2), and may be desupported in a future release.

  • OracleLogicalTransactionStatus class

  • OracleConnection.LogicalTransactionId property

  • OracleConnection.GetLogicalTransactionStatus method

8.1.11 Desupport of Oracle Cluster File System (OCFS) on Windows

Starting with Oracle Database 12c, Oracle Cluster File System (OCFS) is desupported on Windows. Support and distribution of OCFS on Linux (OCFS and OCFS2) remains unaffected by this desupport notice.

Databases currently using OCFS on Windows to host either the Oracle cluster files (Oracle Cluster Registry and voting files) or database files or both need to have these files migrated off OCFS before upgrading to Oracle Database 12c.

See Also:

8.1.11.1 About Upgrading Oracle Database Release 10.2 or 11.1 and OCFS and RAW Devices

If you are upgrading an Oracle Database release 10.2.0.5 or release 11.1.0.7 environment that stores Oracle Clusterware files on OCFS on Windows or RAW devices, then you cannot directly upgrade to Oracle Database 12c. You must first perform an interim upgrade to Oracle Database release 11.2 and migrate the Oracle Clusterware files to Oracle Automatic Storage Management (Oracle ASM). Then you can upgrade from release 11.2 to Oracle Database 12c.

See Also:

8.1.11.2 Desupport of cluvfy comp cfs for OCFS

The cluvfy comp cfs component verification command is removed from Oracle Database as Oracle Cluster File System (OCFS) is no longer supported.

See Also:

Oracle Clusterware Administration and Deployment Guide for more information about cluster administration

8.1.12 Deprecation of Stored List of Administrative Users for Cluster Administration

Starting with Oracle Database 12c, the method of cluster administration using a stored list of administrative users is being replaced with more comprehensive management of administrative user roles by configuring the access control list of the policy set.

See Also:

Oracle Clusterware Administration and Deployment Guide for more information about cluster administration

8.1.13 Desupport for Raw Storage Devices

Starting with Oracle Database 12c, Oracle Database and related technologies, such as Oracle Clusterware, no longer support the direct use of raw (block) storage devices. This means that files must be moved to Oracle ASM or a supported shared file system (cluster file system or Network File System (NFS)) prior to upgrading to Oracle Clusterware 12c.

This also affects the OCR and voting files for Oracle Clusterware. You cannot store the OCR or voting files on raw devices. Oracle Clusterware files stored on raw devices must be moved to Oracle ASM, a cluster file system, or Network File System (NFS) before upgrading.

8.1.14 Deprecation of -checkpasswd for QOSCTL Quality of Service (QoS) Command

The syntax qosctl -checkpasswd username password has been deprecated. See Oracle Database Quality of Service Management User's Guide for information about QOSCTL syntax and commands.

8.1.15 Change to VARCHAR2, NVARCHAR2, and RAW Datatypes

Starting with Oracle Database 12c, the maximum size of the VARCHAR2, NVARCHAR2, and RAW datatypes has been increased to 32767 bytes when the COMPATIBLE initialization parameter is set to 12.0 and the MAX_STRING_SIZE initialization parameter is set to EXTENDED.

See Also:

Oracle Database SQL Language Reference for more information about MAX_STRING_SIZE

8.1.16 Deprecation of JPublisher

Oracle JPublisher is deprecated in Oracle Database 12c Release 1, as of October 2014, and all JPublisher features are desupported and unavailable in Oracle Database 12c Release 2. Oracle recommends that you use the alternatives listed here:

  • To continue to use Web service callouts, Oracle recommends that you use the OJVM Web Services Callout utility, which is a replacement for the Web Services Callout utility.

  • To create Java client applications for PL/SQL programs and SQL objects, Oracle recommends that developers use other JDK development tools that assist you to create java STRUCT classes, and other prestructured options.

See Also:

My Oracle Support Note 1937939.1 for more information about JPublisher deprecation and desupport:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1937939.1

JDK Tools and Utilities on Oracle Technology Network:

http://docs.oracle.com/javase/8/docs/technotes/tools/

8.1.17 Changes for Oracle JDBC and SQLJ

In Oracle Database 12c, some features are deprecated or desupported that affect JDBC, UCP, SQLJ, JPublisher, and Java in the Database (Oracle JVM). The JDBC Javadoc also contains a page for all the deprecated APIs.

The following features are deprecated or desupported in this release for Oracle JDBC and SQLJ:

8.1.17.1 Deprecation of SQLJ Inside the Server

SQLJ usage inside the database server is deprecated in this release. The capability of translating and running SQLJ applications inside the database will not be available in later releases. SQLJ can only be used as a client tool to translate the applications that can connect to Oracle Database and run as a client. SQLJ cannot be used inside stored procedures, functions, or triggers.

8.1.17.2 Deprecated Oracle Update Batching

Oracle Update Batching is deprecated in Oracle Database 12c. Use Standard Update Batching instead.

The following APIs are deprecated and marked deprecated in the JDBC Javadoc:

  • OraclePreparedStatement.setExecuteBatch()

  • OraclePreparedStatement.getExecuteBatch()

  • OracleCallableStatement.setExecuteBatch()

See Also:

Oracle Database JDBC Developer's Guide for information on Oracle Update Batching

8.1.17.3 Deprecated EndToEndMetrics related APIs

EndToEndMetrics -related APIs are deprecated in Oracle Database 12c. Use Universal Connection Pool instead.

The following APIs are deprecated and marked deprecated in the JDBC Javadoc:

  • getEndToEndMetrics

  • getEndToEndECIDSequenceNumber

  • setEndToEndMetrics

  • setApplicationContext

  • clearAllApplicationContext

See Also:

Oracle Database JDBC Developer's Guide and the JDBC Javadoc for information about Universal Connection Pool

8.1.17.4 Deprecated Stored Outlines

Stored outlines are deprecated in Oracle Database 12c. Use plan baselines instead.

See Also:

Oracle Database SQLJ Developer's Guide for information about plan baselines

8.1.17.5 Deprecated Concrete Classes in oracle.sql Package

The concrete classes in the oracle.sql package are deprecated in Oracle Database 12c. These are replaced with new interfaces in the oracle.jdbc package.

See Also:

Oracle Database JDBC Developer's Guide for information about the new interfaces for oracle.jdbc

8.1.17.6 Deprecated defineColumnType Method

The JDBC method defineColumnType is deprecated in this release.

8.1.17.7 Deprecated CONNECTION_PROPERTY_STREAM_CHUNK_SIZE Property

The JDBC property CONNECTION_PROPERTY_STREAM_CHUNK_SIZE is deprecated in this release.

8.1.17.8 Desupported Implicit Connection Caching

Implicit Connection Caching is desupported in Oracle Database 12c. Use Universal Connection Pool instead.

8.1.18 Changes for Oracle Call Interface

The following Oracle Call Interface (OCI) features are deprecated in Oracle Database 12c, and may be desupported in a future release:

  • OCI deployment parameters in sqlnet.ora are deprecated. These include the following parameters:

    • OCI client result cache parameters: OCI_RESULT_CACHE_MAX_SIZE, OCI_RESULT_CACHE_MAX_RSET_SIZE, and OCI_RESULT_CACHE_MAX_RSET_ROWS

8.1.19 Changed Default for resource_limit Parameter

The Oracle RESOURCE_LIMIT parameter determines whether resource limits are enforced in database profiles. In this release, the RESOURCE_LIMIT parameter is set to TRUE by default. If Oracle resource limits are disabled, any defined profile limits will be ignored. This does not apply to password resources.

To check the resource_limit setting from SQL*Plus:

SQL> select value from v$parameter where name = 'resource_limit';

8.2 Oracle Business Intelligence and Data Warehousing Changes

Oracle Database 12c provides changes to business intelligence and data warehousing applications and features.

This section includes these topics:

8.2.1 Oracle Warehouse Builder (OWB) Not Installed with Oracle Database

Starting with Oracle Database 12c, Oracle Warehouse Builder (OWB) is not installed as part of the software for Oracle Database. An installer for Oracle Warehouse Builder is available on Oracle Technology Network. OWB components that may exist from earlier releases are not upgraded as part of the Oracle Database upgrade process.

8.2.2 Desupport of Change Data Capture

Oracle Change Data Capture is not included in Oracle Database 12c and has been replaced with Oracle GoldenGate.

See Also:

Oracle GoldenGate documentation for information

8.2.3 Desupported Features in Oracle Data Mining

The following Oracle Data Mining features are desupported in Oracle Database 12c:

  • The Oracle Data Mining Java API is no longer available. The programmatic interfaces to Oracle Data Mining 12c consist of two PL/SQL packages, DBMS_DATA_MINING and DBMS_DATA_MINING_TRANSFORM, and a family of SQL language functions for scoring data.

    See Also:

    Oracle Data Mining User's Guide for information about the Data Mining PL/SQL packages
  • The Adaptive Bayes Network (ABN) algorithm is no longer available. The Decision Tree algorithm replaces ABN in Oracle Data Mining 12c.

    See Also:

    Oracle Data Mining Concepts for information about the Decision Tree algorithm

8.2.4 Changes to Upgrading Oracle Data Mining Models

Starting with Oracle Database 12c, Oracle is desupporting the Data Mining Java API and the Adaptive Bayes Network (ABN) algorithm. Therefore, models created by the Oracle Data Mining Java API cannot be upgraded from Oracle Database release 11g to Oracle Database 12c. All other models and metadata are upgraded automatically during the upgrade from release 11g to Oracle Database 12c. ABN models can be upgraded, but you cannot use them in an Oracle Database 12c database. You must drop ABN models either before the upgrade or afterward. You can replace ABN models by building new classification models in the Oracle Database 12c database.

See Also:

Oracle Data Mining User's Guide for information about the Data Mining API and data mining models

8.2.5 Desupport of OLAP Catalog (AMD)

Starting with Oracle Database 12c, the Common Warehouse Metamodel (CWM) standard is desupported for the OLAP catalog (AMD). This support was deprecated in Oracle Database 11g Release 2 (11.2). If your existing database has CWM metadata in the OLAP catalog and you upgrade to Oracle Database 12c, then the upgraded database has the AMD component. If the database you upgrade does not have the AMD component, then the upgraded Oracle Database 12c database also does not have the AMD component because new installations for Oracle Database 12c do not include AMD. If your database has the AMD component and you want to remove it, then run the ORACLE_HOME/olap/admin/catnoamd.sql script before or after upgrading.

Note:

If the OLAP catalog exists in the database you are upgrading, you may see AMD OLAP Catalog OPTION OFF and invalid CWM OLAP objects. You can safely ignore the invalid OLAP objects as they are not needed.

See Also:

8.3 Oracle Database Security Changes

Oracle Database 12c includes changes to security features in Oracle Database Vault and Oracle Data Guard and other areas. This section contains these topics:

8.3.1 Changes to Security Auditing Features

The auditing functionality has been redesigned in Oracle Database 12c. When you create a new database with Oracle Database 12c, the full set of auditing enhancement features are automatically available. If you upgrade from an earlier release, then you are given the option of using some of the new audit features and the audit functionality from the release from which you upgraded. Oracle strongly recommends that you migrate to the full set of the latest audit features.

See Also:

8.3.2 Deprecated Functions and Parameters in Oracle Label Security

The following Oracle Label Security features are deprecated in Oracle Database 12c, and may be desupported in a future release:

8.3.3 Deprecated DBMS_NETWORK_ACL_ADMIN PL/SQL package Procedures

In Oracle Database 12c, the following procedures from the DBMS_NETWORK_ACL_ADMIN PL/SQL package are deprecated:

  • CREATE_ACL

  • ADD_PRIVILEGE

  • DELETE_PRIVILEGE

  • ASSIGN_ACL

  • UNASSIGN_ACL

  • DROP_ACL

  • ASSIGN_WALLET_ACL

  • UNASSIGN_WALLET_ACL

  • CHECK_PRIVILEGE

  • CHECK_PRIVILEGE_ACLID

See Also:

Oracle Database Security Guide for information about managing fine-grained access in PL/SQL Packages and Types

8.3.4 Deprecation of IGNORECASE and SEC_CASE_SENSITIVE_LOGON

The IGNORECASE argument of ORAPWD and the SEC_CASE_SENSITIVE_LOGON system parameter are deprecated in Oracle Database 12c. By default, passwords in Oracle Database 12c are case sensitive.

See Also:

Oracle Database Security Guide for more information about configuring authentication and password protection

8.3.5 Deprecation of SQLNET.ALLOWED_LOGON_VERSION Parameter

The SQLNET.ALLOWED_LOGON_VERSION parameter is deprecated in Oracle Database 12c. This parameter has been replaced with two new Oracle Net Services parameters:

8.3.5.1 Upgrading a System that Did Not Have SQLNET.ALLOWED_LOGON_VERSION Parameter Setting

If you are upgrading a system that did not have a SQLNET.ALLOWED_LOGON_VERSION parameter setting (that is, it was using the default 8), then you might need to set the value of the SQLNET.ALLOWED_LOGON_VERSION_SERVER to 8 in the upgraded Oracle Database 12c server to maintain compatibility with clients on earlier releases. Otherwise, if no setting for SQLNET.ALLOWED_LOGON_VERSION_SERVER (or the deprecated SQLNET.ALLOWED_LOGON_VERSION) parameter is made in the upgraded Oracle Database 12c server, then the new default value becomes 11 in the new Oracle Database 12c.

The effect of the new default value of 11 for SQLNET.ALLOWED_LOGON_VERSION_SERVER in Oracle Database 12c is that clients using Oracle Database release 10g and later can connect to the Oracle Database 12c server. Clients using releases earlier than Oracle Database release 11.2.0.3 that have not applied critical patch update CPUOct2012 or later patches must use the 10g password version.

Using a setting of 12 is most secure. However, this setting only permits Oracle Database 12c clients to connect.

See Also:

Oracle Database Readme for the topic "Protection Against Password-Guessing Attacks" and Oracle Database Net Services Reference for information about SQLNET.ALLOWED_LOGON_VERSION_SERVER

8.3.6 AUDIT_ADMIN and AUDIT_VIEWER Roles Note

In Oracle Database 12c, two roles may exist in your database that affect upgrading: AUDIT_ADMIN and AUDIT_VIEWER.

The Pre-Upgrade Information Tool and DBUA perform a pre-upgrade check to make sure such users or roles do not exist in the database. Oracle recommends that you do not use these names in your databases. If these users or roles exist, then you should rename or drop them as appropriate before upgrading to Oracle Database 12c.

See Also:

Oracle Database Security Guide for information on configuring privilege and role authorization for database security

8.3.7 Deprecation of Windows NTS Authentication Using the NTLM Protocol

Windows users can no longer authenticate using the NTS adaptor on Windows clients and servers that require the NT Lan Manager (NTLM) protocol. Because of security vulnerabilities, NTLM is deprecated as of Oracle Database 12c. Windows users can still use Kerberos. NTLM is still used for local user authentication, and in cases in which the database service runs as a local user.

A new client side sqlnet.ora boolean parameter NO_NTLM (defaulting to false) allows you to control when NTLM is used in NTS authentication. When you set NO_NTLM to true, this parameter value prevents NTLM from being used in Windows NTS authentication.

See Also:

Oracle Database Platform Guide for Microsoft Windows for information on changes that affect the Windows platform in this release

8.3.8 Deprecation of Public Key Infrastructure for Transparent Data Encryption

Public Key Infrastructure (PKI) is deprecated for Transparent Data Encryption (TDE) in Oracle Database 12c. To configure TDE, use the ADMINISTER KEY MANAGEMENT SQL statement. Other implementations of PKI are not affected.

See Also:

Oracle Database Advanced Security Administrator's Guide for information about configuring TDE

8.3.9 Desupported Cipher Suites for Secure Sockets Layer (SSL)

Oracle Advanced Security has desupported the following cipher suites in Oracle Database 12c:

  • SSL_DH_anon_WITH_DES_CBC_SHA

  • SSL_RSA_EXPORT_WITH_DES40_CBC_SHA

  • SSL_RSA_EXPORT_WITH_RC4_40_MD5

  • SSL_RSA_WITH_DES_CBC_SHA

See Also:

Oracle Database Security Guide for information about the supported SSL cipher suites

8.3.10 Desupport of Database Rules Manager (RUL) and Expression Filter (EXF)

Starting with Oracle Database 12c, the Expression Filter (EXF) and Database Rules Manager (RUL) features are desupported. If you are using Rules Manager, Oracle recommends that you consider migrating to Oracle Business Rules, a component of Oracle Fusion Middleware. The Continuous Query Notification feature of Oracle Database replaces Expression Filter.

This script is executed by the upgrade process. If you want to remove these components before upgrading, then you can run the catnoexf.sql script before the upgrade. The catnoexf.sql script is located under ORACLE_HOME/rdbms/admin/.

See Also:

Support note 1244535.1 Rules Manager and Expression Filter Features of Oracle Database on My Oracle Support at http://support.oracle.com/

8.3.11 Changes for Oracle Data Guard Broker

As part of Oracle Data Guard Broker's support for Separation of Duty features, the following broker properties are deprecated in Oracle Database 12c with no replacements:

  • LsbyASkipCfgPr

  • LsbyASkipErrorCfgPr

  • LsbyASkipTxnCfgPr

  • LsbyDSkipCfgPr

  • LsbyDSkipErrorCfgPr

  • LsbyDSkipTxnCfgPr

  • LsbySkipTable

  • LsbySkipTxnTable

8.3.12 Changes for Oracle Data Pump Export Utility

The XML_CLOBS option of the Oracle Data Pump Export DATA_OPTIONS parameter is deprecated.

See Also:

Oracle Database Utilities for information about the Export DATA_OPTIONS parameter

8.3.13 Changes for Oracle Database Vault

Starting with Oracle Database 12c, the Database Vault Configuration Assistant (DVCA) and Database Vault Administrator (DVA) are being deprecated. Use Oracle Enterprise Manager Cloud Control for Oracle Database Vault configuration and administration.

Additional Oracle Database Vault features are being deprecated in this release as follows:

8.3.13.1 Deprecated Default Rule Sets

The following rule sets have been deprecated for this release:

  • Allow Oracle Data Pump Operation rule set

  • Allow Scheduler Job rule set

See Also:

Oracle Database Vault Administrator's Guide for information on default rule sets

8.3.13.2 Deprecated Default Realms

The Oracle Data Dictionary realm and Oracle Enterprise Manager realm are deprecated in this release. The objects formerly protected by the Oracle Data Dictionary realm have been migrated to new realms.

See Also:

Oracle Database Vault Administrator's Guide for information about new realms and default realms

8.3.13.3 Deprecated API

The DVSYS.DBMS_MACADM.SYNC_RULES procedure has been deprecated because its functionality has been built into the rule creation functionality.

See Also:

Oracle Database Vault Administrator's Guide for information on rule creation

8.3.14 Changes for Oracle Database Semantic Technologies

The following features are deprecated for Oracle Database Semantic Technologies in Oracle Database 12c:

8.3.14.1 VPD Support in Oracle Database Semantic Technologies

Transition existing Semantic Technologies applications that depend on Virtual Private Database (VPD) to use Oracle Label Security (OLS) instead.

See Also:

Oracle Database Semantic Technologies Developer's Guide for information about fine-grained access control for RDF data

8.3.14.2 Version-Enabled Models Support In Oracle Database Semantic Technologies

The specific alternative to using Workspace Manager with semantic data depends on the purpose of the application. For information about use cases and recommended alternatives, see My Oracle Support Note 1468273.1.

See Also:

Oracle Database Semantic Technologies Developer's Guide for information about Workspace Manager support for RDF data

8.4 Oracle Globalization Support Changes

Oracle Database 12c provides changes to how Oracle supports globalization.

This section contains the following topic:

8.4.1 Desupport of CSSCAN and CSALTER

With the introduction of Oracle Database Migration Assistant for Unicode (DMU), Oracle is proceeding with the desupport of the legacy database tools, CSSCAN and CSALTER. DMU provides a complete end-to-end Unicode migration solution for database administrators. Starting with Oracle Database 12c, DMU is included with Oracle Database, and the CSSCAN and CSALTER tools are no longer included nor supported.

See Also:

8.5 Oracle Multimedia Changes

In Oracle Database 12c, ORDImage support for DICOM is deprecated.

See Also:

Oracle Multimedia Reference for information about ORDImage

8.6 Oracle Net Services Changes

In this release, Oracle Net Services has deprecated or no longer supports some features, parameters, and commands. This section contains the following topics:

8.6.1 Desupport of Oracle Net Connection Pooling

In Oracle Database 12c, Oracle Net connection pooling is no longer supported. Oracle Net connection pooling was deprecated in Oracle Database 11g. This includes the DISPATCHERS attributes TICKS, SESSIONS, and CONNECTIONS.

See Also:

Support note 1469466.1 about Oracle Net Connection Pooling on My Oracle Support at http://support.oracle.com/

8.6.2 Desupport of Oracle Names

Oracle Names has not been supported as a naming method since Oracle Database 11g. You must migrate to directory naming.

See Also:

Oracle Database Net Services Administrator's Guide for additional information about migrating to directory naming

8.6.3 Desupport of Oracle Net Listener Password

In Oracle Database 12c, the Oracle Net Listener password feature is no longer supported. This does not cause a loss of security because authentication is enforced through local operating system authentication.

See Also:

Oracle Database Net Services Reference for more information about Oracle Net Listener security

8.6.4 Desupport of SQLNET.KERBEROS5_CONF_MIT Parameter for Oracle Net Services

The SQLNET.KERBEROS5_CONF_MIT networking parameter is no longer needed (nor supported) in sqlnet.ora. This parameter is set to FALSE by default, which has no affect on the Kerberos configuration. Formerly when set to TRUE, this parameter specified that the configuration file should be parsed in a format as specified by MIT Kerberos 5. Starting with Oracle Database 12c, only this format of Kerberos configuration is supported. Thus, there is no longer a need for this parameter.

See Also:

Oracle Database Net Services Reference for information on Kerberos parameters for the sqlnet.ora file

8.6.5 Desupport of Oracle Names Control Utility for Oracle Net Services

The Oracle Names Control Utility is desupported and has not been available starting with Oracle Database 10g. This includes all the related control utility commands. Oracle Database clients cannot use a Names Server to resolve connect strings. Migrate your applications to Oracle Internet Directory with LDAP directory naming.

See Also:

Oracle Database Net Services Reference for information about configuring the directory naming method

8.6.6 Deprecated NT LAN Manager (NTLM) Protocol for Oracle Net Services

The NT LAN Manager (NTLM) protocol for domain authentication is deprecated in the Oracle Windows adapter. Only Kerberos authentication is used for the NTS adapter.

Tip:

Oracle Database Net Services Reference for information on Kerberos parameters for the sqlnet.ora file

8.7 Oracle XML Database Changes

In addition to being installed with the Oracle Database software, Oracle XML Database has changed features in Oracle Database 12c.

8.7.1 Oracle XML DB is Mandatory and Cannot Be Uninstalled

Starting with Oracle Database 12c, Oracle XML DB is a mandatory component of Oracle Database. You cannot uninstall Oracle XML DB, and there is no option to exclude it when you create an Oracle database. Oracle XML DB is automatically installed or upgraded when you upgrade an existing database to Oracle Database 12c.

8.7.2 Deprecated Features for Oracle XML Database

The following features are deprecated in this release, and may be desupported in a future release. See Oracle XML DB Developer's Guide for a complete list and more information.

  • CLOB storage of XMLType, also known as unstructured storage, is deprecated. Use binary XML storage of XMLType instead.

    If you need to preserve insignificant whitespace then store two copies of your original XML document: one as an XMLType instance for database use and XML processing, the other as a CLOB instance to provide document fidelity.

  • Creation of an XMLIndex index over an XML fragment stored as a CLOB instance embedded in object-relational XMLType data is deprecated. If you need to index the data in such a fragment then store the document using binary XML storage, not object-relational storage.

  • The following PL/SQL subprograms in package DBMS_XMLSCHEMA are deprecated:

    • generateSchema

    • generateSchemas

    There are no replacements for these constructs and there is no workaround for this change.

  • PL/SQL package DBMS_XDB_CONFIG is new. All Oracle XML DB configuration functions, procedures, and constants have been moved from package DBMS_XDB to DBMS_XDB_CONFIG. They are deprecated for package DBMS_XDB. Oracle recommends that you use them in package DBMS_XDB_CONFIG instead.

    These are the subprograms that are deprecated in package DBMS_XDB:

    • ADDHTTPEXPIREMAPPING

    • ADDMIMEMAPPING

    • ADDSCHEMALOCMAPPING

    • ADDSERVLET

    • ADDSERVLETMAPPING

    • ADDSERVLETSECROLE

    • ADDXMLEXTENSION

    • CFG_GET

    • CFG_REFRESH

    • CFG_UPDATE

    • DELETEHTTPEXPIREMAPPING

    • DELETEMIMEMAPPING

    • DELETESCHEMALOCMAPPING

    • DELETESERVLET

    • DELETESERVLETMAPPING

    • DELETESERVLETSECROLE

    • DELETEXMLEXTENSION

    • GETFTPPORT

    • GETHTTPPORT

    • GETLISTENERENDPOINT

    • SETFTPPORT

    • SETHTTPPORT

    • SETLISTENERENDPOINT

    • SETLISTENERLOCALACCESS

    These are the constants that are deprecated in package DBMS_XDB:

    • XDB_ENDPOINT_HTTP

    • XDB_ENDPOINT_HTTP2

    • XDB_PROTOCOL_TCP

    • XDB_PROTOCOL_TCPS

    See Also:

    Oracle Database PL/SQL Packages and Types Reference, Chapter "DBMS_XDB_CONFIG"
  • All Oracle SQL functions for updating XML data are deprecated. Oracle recommends that you use XQuery Update instead. These are the deprecated XML updating functions:

    • updateXML

    • insertChildXML

    • insertChildXMLbefore

    • insertChildXMLafter

    • insertXMLbefore

    • insertXMLafter

    • appendChildXML

    • deleteXML

    See Also:

    Oracle XML DB Developer's Guide for the appendix that describes Oracle SQL functions for updating XML data that are deprecated and recommendations for replacements
  • Oracle SQL function sys_xmlgen is deprecated. Oracle recommends that you use the SQL/XML generation functions instead.

    See Also:

    Oracle XML DB Developer's Guide for information about SQL functions that you can use to construct XML data
  • The following Oracle XQuery functions are deprecated. Use the corresponding standard XQuery functions instead, that is, the functions with the same names but with namespace prefix fn.

    • ora:matches – use fn:matches instead

    • ora:replace – use fn:replace instead

  • The following Oracle constructs that provide support for XML translations are deprecated.

    • PL/SQL package DBMS_XMLTRANSLATIONS

    • Oracle XPath function ora:translate

    • XML Schema annotations xdb:maxOccurs, xdb:srclang, and xdb:translate

    There are no replacements for these constructs and there is no workaround for this change.

    See Also:

    Oracle XML DB Developer's Guide for more information
  • The following XML Schema annotations are deprecated:

    • xdb:defaultTableSchema

    • xdb:maintainOrder

    • xdb:mapUnboundedStringToLob

    • xdb:maxOccurs

    • xdb:SQLCollSchema

    • xdb:SQLSchema

    • xdb:srclang

    • xdb:storeVarrayAsTable

    • xdb:translate

    There are no replacements for these constructs, and there is no workaround for this change.

  • The value xml_clobs for export parameter data_options is deprecated starting with Oracle Database 12c.

    See Also:

    Oracle XML DB Developer's Guide for information about exporting and importing XMLType Tables

8.8 Oracle Text Changes

Oracle Database 12c introduces changes for Oracle Text.

8.8.1 Desupport of CTXXPATH in Oracle Text and Oracle XML DB

CTXSYS.CTXXPATH index is desupported as of Oracle Database 12c. This does not affect CTXCAT. Use XMLIndex indexes instead.

See Also:

Oracle XML DB Developer's Guide for more information about XMLIndex

8.8.2 Desupport of ALTER INDEX OPTIMIZE for Text Indexes

The ALTER INDEX OPTIMIZE [token index_token | fast | full [maxtime (time | unlimited)] operation is not supported for Oracle Database 12c. To optimize your index, use CTX_DDL.OPTIMIZE_INDEX.

See Also:

Oracle Text Reference for information about OPTIMIZE_INDEX

8.8.3 Desupport of SYNC [MEMORY memsize] for Text Indexes

The SYNC [MEMORY memsize] operation is not supported for Oracle Database 12c. To synchronize your index, use CTX_DDL.SYNC_INDEX.

See Also:

Oracle Text Reference for information about SYNC_INDEX