Oracle Database 12c Release 2

Author: e | 2025-04-24

★★★★☆ (4.3 / 3378 reviews)

download hipchat for windows

Install Oracle Database 12c Release 2 on Windows 10 Oracle Database 12c Release 2How to Download Install Oracle Database 12c Release 2 (12.2.0.1.0) Enterpr

tigo sport costa rica

Oracle Database 12c - Install Oracle Database 12c Release 2 on

Oracle® Database Release Notes 12c Release 2 (12.2) for HP-UX Itanium E85845-01 May 2017 This document contains information that was not included in the platform-specific or product-specific documentation for this release. This document supplements Oracle Database Readme. This document may be updated after it is released. You can check for updates to this document and view other Oracle documentation at This document contains the following topics: Certification Information Latest Upgrade Information Unsupported Products Product Support Installation, Configuration, and Upgrade Issues for Release 12.2 Other Known Issues for Release 12.2 Documentation Accessibility Certification Information The latest certification information for Oracle Database 12c Release 2 (12.2.0.1) is available on My Oracle Support at: Latest Upgrade Information For late-breaking updates and best practices about preupgrade, postupgrade, compatibility, and interoperability discussions, refer to Note 1462240.1 on My Oracle Support that links to the "Upgrade Companion" page. Unsupported Products In addition to the items listed in section, "Features Not Available or Restricted in Oracle Database 12c," in Oracle Database Readme, the following products or features are not supported: Oracle Database Quality of Service Management Support Oracle Database Quality of Service Management is not supported on HP-UX Itanium. Cluster Health Monitor Support Cluster Health Monitor is not supported on HP-UX Itanium. Grid Infrastructure Management Repository Support Grid Infrastructure Management Repository is not supported on HP-UX Itanium. Rapid Home Provisioning Server Support Rapid Home Provisioning Server is not supported on HP-UX Itanium. Memory Guard Support Memory Guard is not supported on HP-UX Itanium. ASMLIB Support ASMLIB is

timer resolution fortnite

Oracle Database 12c Release 2

Database Hard disk space120 MB - Toad for Oracle 32 bit 150 MB - Toad for Oracle 64 bit Operating systemWindows 8.1 Windows 10 Windows 11 Windows Server 2012 R2 - 2 CPU required Windows Server 2016 Windows Server 2019 Database requirementsRequirementDetailsDatabase clientAn Oracle client must be installed and configured on the system where you are running Toad. The following are supported:Oracle Client or Instant Client 10.2.0.5 Oracle Client or Instant Client 11.2.0.1/11.2.0.3 Oracle Client or Instant Client 12c Release 1 and 2 Oracle Client or Instant Client 18c Oracle Client or Instant Client 19c Oracle Client or Instant Client 21c Note: You must use the 32-bit version of Toad with the 32-bit Oracle client, and the 64-bit version of Toad with the 64-bit Oracle client.Database serverOracle versions: 10g Release 2 11g Release 1 and 2 12c Release 1 and 2 18c 19c 21c (Linux and Oracle Cloud Infrastructure) Important: It is recommended that your client version be of the same release (or later) as your database server. This is an Oracle recommendation to prevent performance issues.Cloud database serviceOracle Database as a Service on Amazon EC2 and Oracle CloudNetworkInternet Protocol Version 6 (IPv6) is being adopted by the US Federal Government and industries around the world. In its most basic format, the new protocol uses 128-bit addresses instead of 32-bit addresses, which are used by the current IPv4 to route packets over the Internet. Toad for Oracle features, such as FTP, access the Internet through third-party vendors that are IPv6

With Oracle Database 12c Release 2

Editions Release 1 Oracle Database 11g Standard/Enterprise Editions Release 2 Oracle Database 12c Standard/Enterprise Editions Release 1 Fix Pack 5 or later is required if using JDBC.Oracle Database 12c Standard/Enterprise Editions Release 2 Fix Pack 8 or later is required. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java.Sybase Adaptive Server Enterprise 15.0 and future fix packs Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.Sybase Adaptive Server Enterprise 15.5 Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.Software IntegrationPrerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component.This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported.Sterling Connect:Direct for UNIX 4.1 and future fix packs (overview) (support) You may run a Sterling Connect:Direct bridge agent on the following operating systems: Solaris 10 SPARC and future OS fix packs Solaris 10 x86-64 and future OS fix packs (patch level (REV) dated 23 Aug 2011 or later) Solaris 11 SPARC and future OS fix packs Solaris 11 x86-64 and future OS fix packs The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems: Windows Unix z/OS 4690From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform.IBM 4690 Operating System Release Version 6 Release 2 Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packsIBM 4690 Operating System Release Version 6 Release 3 Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packsTransaction ManagerUsing the WebSphere MQ classes for JMS, WebSphere MQ can only. Install Oracle Database 12c Release 2 on Windows 10 Oracle Database 12c Release 2How to Download Install Oracle Database 12c Release 2 (12.2.0.1.0) Enterpr Changes in This Release for Oracle Database 2 Day DBA Changes in Oracle Database 12c Release 2 (12.2.0.1) xvii Changes in Oracle Database 12c Release 1 (12.1.0.2)

ORACLE-BASE - Oracle Database 12c Release 2

Across primary and standby databases can also be executed from the Oracle Data Guard broker DGMGRL command-line interface. This support enables database administrators, who use the standard interface to Oracle Data Guard (DGMGRL) in their broker configurations, to perform block comparisons between the primary database and any physical standby database. Oracle Data Guard Broker Support for Executing DGMGRL Command Scripts This feature enables command scripts to be executed through the Oracle Data Guard broker DGMGRL command-line interface; much like in SQL*Plus. DGMGRL commands, SQL commands using the broker SQL command, and operating system commands using the new HOST (or !) capability can be put into a file and executed on the DGMGRL command line. This feature enables customers who use the standard interface to Oracle Data Guard (DGMGRL) in their broker configurations to use scripts for Oracle Data Guard operations. Broker ConfigurationWideServiceName Configuration Property In previous releases, the Oracle Data Guard broker lacked a ConfigurationWideServiceName configuration property shared by all members. In particular, there was no guarantee that you could use a single connect identifier to connect to any database in the configuration because each database had its own services running, which may or may not have had the same service name. In Oracle Database 12c Release 2 (12.2), Oracle Data Guard broker can publish a service on each member in a configuration with a unified service name. This capability also enables the new capabilities of the Oracle Data Guard broker observer for automatic failover control. Having a ConfigurationWideServiceName configuration property allows users to easily connect to any database in the configuration and enables the new capabilities of the fast-start failover observer in Oracle Database 12c Release 2 (12.2). Enhancing Support for Alternate Destinations The concept of an alternate destination for redo transport was first introduced in Oracle Database release 9.2 and was designed to work as a single pair of destinations with simple failover when the initial destination was no longer available. In Oracle Database 12c Release 1 (12.1), this was enhanced to use one preferred destination, and the second as an alternate destination, with automatic reconfiguration and simple failback when the initial redo destination was once again available. The new Oracle Active Data Guard far sync and real-time cascade features introduced a number of additional use cases for alternate destinations that the Oracle Database 12c Release 1 (12.1) model was unable to support. This enhanced support for alternate destinations greatly increases the number of different use cases that can now be supported with complete user configuration control and completely automatic management. This feature greatly expands the number of alternate destinations that you can define. It provides greater flexibility to designate rules that define priority, and it provides numerous

Oracle Database 12c Release 2 Multitenant (Oracle

Export operation. The TTS_CLOSURE_CHECK parameter can also be used to indicate that tablespaces can remain read-write during a test mode transportable tablespace operation. This option is used to obtain the timing requirements of the export operation. It is for testing purposes only. The dump file is unavailable for import. Syntax and DescriptionTTS_CLOSURE_CHECK = [ ON | OFF | FULL | TEST_MODE ]The TTS_CLOSURE_CHECK parameter supports the following options: ON - indicates self-containment closure check be performed OFF - indicates no closure check be performed FULL - indicates full bidirectional closure check be performed TEST_MODE - indicates that tablespaces are not required to be in read-only mode ON,OFF, and FULL options are mutually exclusive. TEST_MODE is an Oracle Data Pump Export option only. Example TTS_CLOSURE_CHECK=FULL 2.4.51 VERSION The Data Pump Export command-line utility VERSION parameter specifies the version of database objects that you want to export. Default: COMPATIBLE Purpose Specifies the version of database objects that you want to export. Only database objects and attributes that are compatible with the specified release are exported. You can use the VERSION parameter to create a dump file set that is compatible with a previous release of Oracle Database. You cannot use Data Pump Export with releases of Oracle Database before Oracle Database 10g release 1 (10.1). Data Pump Export only works with Oracle Database 10g release 1 (10.1) or later. The VERSION parameter simply allows you to identify the version of objects that you export. On Oracle Database 11g release 2 (11.2.0.3) or later, you can specify the VERSION parameter as VERSION=12 with FULL=Y to generate a full export dump file that is ready for import into Oracle Database 12c. The export with the later release target VERSION value includes information from registered database options and components. The dump file set specifying a later release version can only be imported into Oracle Database 12c Release 1 (12.1.0.1) and later. For example, if VERSION=12 is used with FULL=Y and also with TRANSPORTABLE=ALWAYS, then a full transportable export dump file is generated that is ready for import into Oracle Database 12c. For more information, refer

Multimodel Database with Oracle Database 12c Release 2

Not supported. Product Support The list of supported products or features for Oracle Database 12c Release 2 (12.2.0.1) are as follows: Database Smart Flash Cache Support Database Smart Flash Cache is supported only on Oracle Solaris and Oracle Linux. Oracle ASM Filter Driver Support Oracle Automatic Storage Management Filter Driver (Oracle ASMFD) is supported only on Linux x86-64. Installation, Configuration, and Upgrade Issues for Release 12.2 There are no installation, configuration, and upgrade issues at the time of this release. Other Known Issues for Release 12.2 There are no known issues at the time of this release. Documentation Accessibility Oracle Database Release Notes, 12c Release 2 (12.2) for HP-UX Itanium E85845-01 Copyright © 2014, 2017, Oracle and/or its affiliates. All rights reserved. Primary Author: Tanaya Bhattacharjee This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing. Install Oracle Database 12c Release 2 on Windows 10 Oracle Database 12c Release 2How to Download Install Oracle Database 12c Release 2 (12.2.0.1.0) Enterpr Changes in This Release for Oracle Database 2 Day DBA Changes in Oracle Database 12c Release 2 (12.2.0.1) xvii Changes in Oracle Database 12c Release 1 (12.1.0.2)

Comments

User9437

Oracle® Database Release Notes 12c Release 2 (12.2) for HP-UX Itanium E85845-01 May 2017 This document contains information that was not included in the platform-specific or product-specific documentation for this release. This document supplements Oracle Database Readme. This document may be updated after it is released. You can check for updates to this document and view other Oracle documentation at This document contains the following topics: Certification Information Latest Upgrade Information Unsupported Products Product Support Installation, Configuration, and Upgrade Issues for Release 12.2 Other Known Issues for Release 12.2 Documentation Accessibility Certification Information The latest certification information for Oracle Database 12c Release 2 (12.2.0.1) is available on My Oracle Support at: Latest Upgrade Information For late-breaking updates and best practices about preupgrade, postupgrade, compatibility, and interoperability discussions, refer to Note 1462240.1 on My Oracle Support that links to the "Upgrade Companion" page. Unsupported Products In addition to the items listed in section, "Features Not Available or Restricted in Oracle Database 12c," in Oracle Database Readme, the following products or features are not supported: Oracle Database Quality of Service Management Support Oracle Database Quality of Service Management is not supported on HP-UX Itanium. Cluster Health Monitor Support Cluster Health Monitor is not supported on HP-UX Itanium. Grid Infrastructure Management Repository Support Grid Infrastructure Management Repository is not supported on HP-UX Itanium. Rapid Home Provisioning Server Support Rapid Home Provisioning Server is not supported on HP-UX Itanium. Memory Guard Support Memory Guard is not supported on HP-UX Itanium. ASMLIB Support ASMLIB is

2025-04-01
User5319

Database Hard disk space120 MB - Toad for Oracle 32 bit 150 MB - Toad for Oracle 64 bit Operating systemWindows 8.1 Windows 10 Windows 11 Windows Server 2012 R2 - 2 CPU required Windows Server 2016 Windows Server 2019 Database requirementsRequirementDetailsDatabase clientAn Oracle client must be installed and configured on the system where you are running Toad. The following are supported:Oracle Client or Instant Client 10.2.0.5 Oracle Client or Instant Client 11.2.0.1/11.2.0.3 Oracle Client or Instant Client 12c Release 1 and 2 Oracle Client or Instant Client 18c Oracle Client or Instant Client 19c Oracle Client or Instant Client 21c Note: You must use the 32-bit version of Toad with the 32-bit Oracle client, and the 64-bit version of Toad with the 64-bit Oracle client.Database serverOracle versions: 10g Release 2 11g Release 1 and 2 12c Release 1 and 2 18c 19c 21c (Linux and Oracle Cloud Infrastructure) Important: It is recommended that your client version be of the same release (or later) as your database server. This is an Oracle recommendation to prevent performance issues.Cloud database serviceOracle Database as a Service on Amazon EC2 and Oracle CloudNetworkInternet Protocol Version 6 (IPv6) is being adopted by the US Federal Government and industries around the world. In its most basic format, the new protocol uses 128-bit addresses instead of 32-bit addresses, which are used by the current IPv4 to route packets over the Internet. Toad for Oracle features, such as FTP, access the Internet through third-party vendors that are IPv6

2025-03-30
User8302

Across primary and standby databases can also be executed from the Oracle Data Guard broker DGMGRL command-line interface. This support enables database administrators, who use the standard interface to Oracle Data Guard (DGMGRL) in their broker configurations, to perform block comparisons between the primary database and any physical standby database. Oracle Data Guard Broker Support for Executing DGMGRL Command Scripts This feature enables command scripts to be executed through the Oracle Data Guard broker DGMGRL command-line interface; much like in SQL*Plus. DGMGRL commands, SQL commands using the broker SQL command, and operating system commands using the new HOST (or !) capability can be put into a file and executed on the DGMGRL command line. This feature enables customers who use the standard interface to Oracle Data Guard (DGMGRL) in their broker configurations to use scripts for Oracle Data Guard operations. Broker ConfigurationWideServiceName Configuration Property In previous releases, the Oracle Data Guard broker lacked a ConfigurationWideServiceName configuration property shared by all members. In particular, there was no guarantee that you could use a single connect identifier to connect to any database in the configuration because each database had its own services running, which may or may not have had the same service name. In Oracle Database 12c Release 2 (12.2), Oracle Data Guard broker can publish a service on each member in a configuration with a unified service name. This capability also enables the new capabilities of the Oracle Data Guard broker observer for automatic failover control. Having a ConfigurationWideServiceName configuration property allows users to easily connect to any database in the configuration and enables the new capabilities of the fast-start failover observer in Oracle Database 12c Release 2 (12.2). Enhancing Support for Alternate Destinations The concept of an alternate destination for redo transport was first introduced in Oracle Database release 9.2 and was designed to work as a single pair of destinations with simple failover when the initial destination was no longer available. In Oracle Database 12c Release 1 (12.1), this was enhanced to use one preferred destination, and the second as an alternate destination, with automatic reconfiguration and simple failback when the initial redo destination was once again available. The new Oracle Active Data Guard far sync and real-time cascade features introduced a number of additional use cases for alternate destinations that the Oracle Database 12c Release 1 (12.1) model was unable to support. This enhanced support for alternate destinations greatly increases the number of different use cases that can now be supported with complete user configuration control and completely automatic management. This feature greatly expands the number of alternate destinations that you can define. It provides greater flexibility to designate rules that define priority, and it provides numerous

2025-04-03
User8076

Export operation. The TTS_CLOSURE_CHECK parameter can also be used to indicate that tablespaces can remain read-write during a test mode transportable tablespace operation. This option is used to obtain the timing requirements of the export operation. It is for testing purposes only. The dump file is unavailable for import. Syntax and DescriptionTTS_CLOSURE_CHECK = [ ON | OFF | FULL | TEST_MODE ]The TTS_CLOSURE_CHECK parameter supports the following options: ON - indicates self-containment closure check be performed OFF - indicates no closure check be performed FULL - indicates full bidirectional closure check be performed TEST_MODE - indicates that tablespaces are not required to be in read-only mode ON,OFF, and FULL options are mutually exclusive. TEST_MODE is an Oracle Data Pump Export option only. Example TTS_CLOSURE_CHECK=FULL 2.4.51 VERSION The Data Pump Export command-line utility VERSION parameter specifies the version of database objects that you want to export. Default: COMPATIBLE Purpose Specifies the version of database objects that you want to export. Only database objects and attributes that are compatible with the specified release are exported. You can use the VERSION parameter to create a dump file set that is compatible with a previous release of Oracle Database. You cannot use Data Pump Export with releases of Oracle Database before Oracle Database 10g release 1 (10.1). Data Pump Export only works with Oracle Database 10g release 1 (10.1) or later. The VERSION parameter simply allows you to identify the version of objects that you export. On Oracle Database 11g release 2 (11.2.0.3) or later, you can specify the VERSION parameter as VERSION=12 with FULL=Y to generate a full export dump file that is ready for import into Oracle Database 12c. The export with the later release target VERSION value includes information from registered database options and components. The dump file set specifying a later release version can only be imported into Oracle Database 12c Release 1 (12.1.0.1) and later. For example, if VERSION=12 is used with FULL=Y and also with TRANSPORTABLE=ALWAYS, then a full transportable export dump file is generated that is ready for import into Oracle Database 12c. For more information, refer

2025-04-20
User6389

11g Standard/Enterprise Editions Release 1 Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client.Oracle Database 11g Standard/Enterprise Editions Release 2 Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client.Oracle Database 12c Standard/Enterprise Edition2 Release 1 Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client.Fix Pack 5 or later and APAR IT10748 is required if using JDBC.Oracle Database 12c Standard/Enterprise Editions Release 2 Fix Pack 8 or later is required. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java.Sybase Adaptive Server Enterprise 15.0 and future fix packs Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.Sybase Adaptive Server Enterprise 15.5 Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.SOAP SupportMicrosoft Internet Information Services 5.1 and future releases, mod levels and fix packs For running .NET services.Software IntegrationPrerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component.This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported.Sterling Connect:Direct for Microsoft Windows 4.6 and future fix packs (overview) (support) You may run a Sterling Connect:Direct bridge agent on the following operating systems: Windows XP SP2 Professional x86-32 and future OS fix packs Windows Server 2003 SP2 Enterprise and Standard Editions and future OS fix packs Windows Server 2008 SP2 Enterprise and Standard Editions and future OS fix packs The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems: Windows Unix z/OS 4690From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform.IBM 4690 Operating System Release Version 6 Release 2 Supported

2025-04-11
User3732

Fix packs Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.Informix Dynamic Server 12.10 and future fix packs Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.Oracle Database 11g Standard/Enterprise Editions Release 1 Oracle Database 11g Standard/Enterprise Editions Release 2 Oracle Database 12c Standard/Enterprise Editions Release 1 Fix Pack 5 or later is required if using JDBC.Oracle Database 12c Standard/Enterprise Editions Release 2 Fix Pack 8 or later is required. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java.Sybase Adaptive Server Enterprise 15.0 and future fix packs Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.Sybase Adaptive Server Enterprise 15.5 Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.Software IntegrationPrerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component.This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported.Sterling Connect:Direct for UNIX 4.1 and future fix packs (overview) (support) You may run a Sterling Connect:Direct bridge agent on the following operating systems: AIX 6.1 TL5 POWER System and future OS fix packs AIX 7.1 POWER System and future OS fix packs (Requires Connect:Direct 4.1.0.3 or above) The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems: Windows Unix z/OS 4690From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform.IBM 4690 Operating System Release Version 6 Release 2 Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packsIBM 4690 Operating System Release Version 6 Release 3 Supported version of

2025-03-30

Add Comment