Oracle Patch 11.2.0.3' title='Oracle Patch 11.2.0.3' />Readme Information for Oracle Database 1. Release 2 1. 1. 2. Troubleshooting of ORA12519 when Oracle 11gR2 Listener refused connection. Update As of May 2012, Oracle announced support for running Oracle 11. Body By Science Mcguff Pdf more. Oracle Linux 6 and Red Hat Enterprise Linux 6. CRMOracleIBM. Compatibility, Upgrading, Downgrading, and Installation. For late breaking updates and best practices about preupgrade, post upgrade, compatibility, and interoperability discussions, see Note 7. My Oracle Support at https support. FADB_Install_2.jpg' alt='Oracle Patch 11.2.0.3' title='Oracle Patch 11.2.0.3' />Oracle Application Express 4. Patch Set Notes. Oracle Database. Release Notes. 12 c Release 1 12. Microsoft Windows. Don Mock Guitar Secrets Revealed Pdf To Jpg. E5212011. March 2017. This document contains information that was not included in the. Updated October 20, 2017 Page 6 of 28 Copyright 2017, Oracle andor its affiliates. All rights reserved. Activity Who When 1. Build Customer Patch Profile. Oracle Patch 11.2.0.3' title='Oracle Patch 11.2.0.3' />Upgrade Companion web site for Oracle Database 1. Release 2. Caution. After installation is complete, do not manually remove or run cron jobs that remove tmp. Oracle software is running. If you remove these files, then Oracle software can encounter intermittent hangs. Oracle Patch 11.2.0.3' title='Oracle Patch 11.2.0.3' />Oracle Grid Infrastructure for a cluster and Oracle Restart installations fail with the following error. CRS 0. 18. 4 Cannot communicate with the CRS daemon. Upgrading to Release 1. Generates Suboptimal Plans for CHAR or NCHAR Data Type Columns. After upgrading to Oracle Database 1. Release 2 1. 1. 2. CHAR or NCHAR data type columns that have histogram statistics and when the OPTIMIZERFEATURESENABLE parameter is set to a value of 1. Describes lastminute features and changes not included in the Oracle Database Documentation Library for Oracle Database 11g Release 2 11. Oracle Database 1. Release 2 1. 1. 2. One workaround for this issue is to apply the patch for bug 1. For CHAR or NCHAR data type columns that have histogram statistics, this patch marks them as stale. This patch also helps if you are using automatic statistics gathering or if you are using manual statistics gathering with either the GATHER AUTO or GATHER STALE option to gather statistics on the problematic tables. Another workaround is to find the tables that have CHAR or NCHAR data type columns that have histogram statistics using the DBATABCOLSTATISTICS view and execute the GATHERTABLESTATS procedure on them. Instead of using the GATHERTABLESTATS procedure on the production system, gather statistics on a test system, export the statistics to a user statistics table, and then import the statistics into the production system. This workaround eliminates the need for the patch for bug 1. When you collect statistics, set the NOINVALIDATE parameter to FALSE so that the existing cursors with suboptimal plans are not shared when SQL statements are executed again. Gathering statistics for tables that have all of the following scenarios can also cause suboptimal plans The tables have CHAR or NCHAR data type columns. The OPTIMIZERFEATURESENABLE parameter is set to a value of 1. The tables have histograms. Later, you change the OPTIMIZERFEATURESENABLE parameter value to less than 1. Oracle Database and set the OPTIMIZERFEATURESENABLE parameter to a smaller value. In this scenario, you need to regather the statistics for those tables after changing the OPTIMIZERFEATURESENABLE parameter. Downgrading Release 1. Results in an Error When You Run catdwgrd. When downgrading from release 1. Bug 1. 18. 11. 07. ORA 2. 00. 00 Upgrade from version 1. Apply patch 1. 18. Applying this patch must be done prior to executing catdwgrd. Downgrading a Database Having Database Control Configured. Consider the following when downgrading the database while having Database Control configured reference Bug 9. If you are upgrading from 1. PSU2 bundle patch in order to downgrade Database Control as part of the database downgrade. Without this patch, the emdwgrd utility would fail with IMPORT impdp errors when restoring Database Control data. When running emdwgrd on 1. Oracle RAC databases, you may need to pass an additional parameter, service. Alias, if you do not have system identifier SID aliases defined in tnsnames. This is also needed for single instance if SID and database names are different. For example. emdwgrd save cluster sid SID service. Alias tnsalias path savedirectory. Tablespace TEMP cluster sid SID service. Alias tnsalias path savedirectory. In the case of in place downgrade from 1. Oracle home, you do not need to run emca restore before running emdwngrd restore. Performing force Upgrade Results in an Incorrect Grid Home Node List in Inventory. When a node crash occurs during an upgrade, a force upgrade can be performed to upgrade a partial cluster minus the unavailable node reference Bug 1. After performing a force upgrade, the node list of the Grid home in inventory is not in sync with the actual Oracle Grid Infrastructure deployment. The node list still contains the unavailable node. Because the node list in inventory is incorrect, the next upgrade or node addition, and any other Oracle Grid Infrastructure deployment, fails. After performing a force upgrade, manually invoke the following command as a CRS user. GRIDHOMEouibinrun. Installer update. Node. List CLUSTERNODEScommaseparatedalivenodelist ORACLEHOMEGRIDHOME CRStrue. Status May Show UNKNOWNAfter upgrading from release 1. UNKNOWN with the explanation being CHECK TIMED OUT reference Bug 1. The workaround is to kill the Oracle Notification Services ONS process and run srvctl start nodeapps. Purge the Database Recycle Bin Before Upgrading. If the following error is seen during the upgrade process, this may indicate that the recycle bin was not purged. ORA 0. 06. 00 internal error code, arguments 1. Prior to upgrade, empty the database recycle bin by running the following command. SQL PURGE DBARECYCLEBIN. Downgrade to Release 1. If you anticipate downgrading back to release 1. Bug 7. 63. 41. 19. This action avoids the following DBMSXSDATASECURITYEVENTS error. PLS 0. 03. 06 wrong number or types of arguments in call. INVALIDATEDSDCACHE DBMSXSDATASECURITYEVENTS. PLSQL Statement ignored. Apply this patch prior to running catrelod. Upgrading a Database With Oracle Data Mining ODMIf you upgrade a database with the Data Mining option from 1. DMSYS schema does not exist in your 1. If it does, you should drop the DMSYS schema and its associated objects from the database as follows. SQL CONNECT AS SYSDBA. SQL DROP USER DMSYS CASCADE. SQL DELETE FROM SYS. EXPPKGACT WHERE SCHEMA DMSYS. SQL SELECT COUNT FROM DBASYNONYMS WHERE TABLEOWNER DMSYS. If the above SQL returns non zero rows, create and run a SQL script as shown in the following example. SQL SET HEAD OFF. SQL SPOOL dirpathDROPDMSYSSYNONYMS. SQL. SQL SELECT Drop public synonym SYNONYMNAME FROM DBASYNONYMS WHERE TABLEOWNER DMSYS. SQL SPOOL OFF. SQL dirpathDROPDMSYSSYNONYMS. SQL. If you upgrade a database from 1. Data Mining metadata objects are migrated from DMSYS to SYS. After the upgrade, when you determine that there is no need to perform a downgrade, set the initialization parameter COMPATIBLE to 1. DMSYS schema and its associated objects as described above. Fails if the Time Zone File Version Used by the Database Does Not Exist in Oracle Home. The following error is returned when catrelod. DBMSDST PLSQL package to upgrade TIMESTAMP WITH TIME ZONE data to that version reference Bug 9. ORA 0. 06. 00 internal error code, arguments qcis. Set. Plsql. Ctx tzi init. See Step 2 of Downgrade the Database in Chapter 6 of the Oracle Database Upgrade Guide for more details. If you previously installed a recent version of the time zone file and used the DBMSDST PLSQL package to upgrade TIMESTAMP WITH TIME ZONE data to that version, then you must install the same version of the time zone file in the release to which you are downgrading. For example, the latest time zone files that are supplied with Oracle Database 1. Release 2 1. 1. 2 are version 1. If, after the database upgrade, you had used DBMSDST to upgrade the TIMESTAMP WITH TIME ZONE data to version 1.