Some that I find interesting (without having tested them, but only relying on the documentation) are :
NULL) despite the data dictionary reflecting the change to a default value of
NULL. The statements that are impacted are
NUMBER DEFAULT 99)followed by a subsequent
yis a nullable column.
DEFAULT TRIM(''))statement which has the same semantic result as unsetting the default.
DBA_HISTviews. A full list can be found using the following command:
SELECT OWNER, OBJECT_NAME FROM ALL_OBJECTS WHERE SHARING='OBJECT LINK' AND OBJECT_TYPE='VIEW'
OPTIMIZER_DYNAMIC_SAMPLINGinitialization parameter is set to the default value of
UNION ALLis automatically invoked for qualifying statements only when the
UNION ALLstatement is in a subselect statement. For example, the following command will execute all branches concurrently:
SELECT * FROM (SELECT FROM ... UNION ALL ... UNION ALL)
UNION ALLstatement not executed as a subselect statement will not.
UNION ALLconstruct as a subselect statement or use the following statement to disable legacy code constraints:
ALTER SESSION SET "_fix_control"='6748058:0';
Bug 14851837Tables containing
TIMESTAMP WITH LOCAL TIME ZONEdata cannot be moved between databases using transportable tablespace technology when the time zones of the source and target databases are different. Each affected table will be flagged during import with the following error:ORA-39360, Table "
" skipped due to transportable import and TSLTZ issues.Workaround: Convert the target database to the same time zone as the source database or move the affected tables with the conventional Data Pump Export and Import.Bug 14621745Certain errors raised while using the
ALTER TABLE MOVE ONLINEstatement can be ignored.Bug 13877504When threaded execution is enabled (
threaded_execution=TRUE) in the initialization parameter file on UNIX platforms, native authentication (that is,
connect / as sysdba or connect /) is not supported.Workaround: Use password-based authentication. Native authentication will not work for connections where the server execution is a thread.Bug 14575666In 12.1, the default value for the
SQLNET.ALLOWED_LOGON_VERSIONparameter has been updated to
11. This means that database clients using pre-11g JDBC thin drivers cannot authenticate to 12.1 database servers unless the
SQLNET.ALLOWED_LOGON_VERSIONparameter is set to the old default of
8.This will cause a 10.2.0.5 Oracle RAC database creation using DBCA to fail with the
ORA-28040: No matching authentication protocolerror in 12.1 Oracle ASM and Oracle Grid Infrastructure environments.Use the workaround before running 10.2.0.5 DBCA to create a database using 12.1 Oracle ASM and Oracle Grid Infrastructure.Bug 16177073Mixed case hostnames are not supported by the Oracle Universal Installer (OUI) for Oracle RAC or Cluster Ready Services (CRS) homes.Bug 16903140A new feature was added in Oracle Database 12c Release 1 (12.1) to support change tracking across resetlogs during the execution of an
ALTER DATABASE OPEN RESETLOGSstatement. This is achieved by deleting bitmaps that are not required because they cover changes that were made after the specified resetlogs point-in-time. There is an issue with the bitmap deleting that can cause error
OPEN RESETLOGS.Workaround: Disable and reenable change tracking. You must disable change tracking before executing the
ALTER DATABASE OPEN RESETLOGSstatement, and then re-enable change tracking after the open resetlogs operation is complete....