27-07-2012, 03:57 PM
Oracle Database
Oracle Database.pdf (Size: 150.8 KB / Downloads: 35)
Unsupported Products
The following products are not supported with Oracle Database 10g release
2 (10.2):
Grid Control Support
Oracle Database 10g release 2 (10.2) can be managed as a target by Grid
Control 10.1.0.4. Oracle Database 10g release 2 is not supported by Grid
Control 10.1.0.4 as a repository.
3 Accessibility Software Recommendations
Our goal is to make Oracle products, services, and supporting documentation
accessible to the disabled community. Oracle Database 10g release 2 (10.2)
supports accessibility features. To make best use of these accessibility features,
Oracle recommends the following software configuration:
Windows 2000 with Service Pack 2 or later
Sun Java Access Bridge 1.0.4 (included with the Oracle Database 10g release 2
(10.2) media)
JAWS screen reader 5.0
Microsoft Internet Explorer 5.5 or later
Additional accessibility information for Oracle products can be found at For the latest configuration information and for information about addressing
accessibility and assistive technology issues, see the Oracle Accessibility FAQ at
4 Installation, Configuration, and Upgrade Issues
Review the following sections for information about issues that affect Oracle
Database installation, configuration, and upgrade:
Database Upgrade Using Database Upgrade Assistant
Limitations with 32-Bit Windows
RAC and ASM Interoperability With Oracle Database 10g Release 2
Shutdown of Cluster Ready Services Stack May Leave Processes Running
Modifying a Virtual IP Address Node Application
10.2 RAC Installations on an Oracle Database Release 10.1.0.4 Cluster
Error While Deleting a Remote Instance From a RAC-Shared Oracle Home
Database
Reading a Downgraded Oracle Cluster Registry with Database Management
Tools
Oracle Database 9.2 Startup Error with srvctl when the Global Services
Daemon is Running in a 10.2 Home
Oracle Database 9.2 Startup Error with srvctl when the Global Services
Daemon is Running in an Oracle 10.2 Clusterware
Deleting a Node from Oracle Clusterware
Installing Enterprise Security Manager
Configuring Raw Devices for Storage
Central Configuration of Oracle Real Application Clusters Disabled on
Windows
Oracle C++ Call Interface (OCCI) Libraries
ODBC Online Help in Japanese is Not Installed
4.1 Database Upgrade Using Database Upgrade Assistant
If the database version does not match the Oracle release version, Database
Upgrade Assistant displays a warning message. The warning message
incorrectly instructs you to run catpatch.sql from the Oracle Database 10g
release 1 home. Do not do this. Instead, run catpatch.sql from the rdbms\
admin directory of the source Oracle home from which you are upgrading.
The issue is tracked with Oracle bug 4551401.
After the upgrade, the ORACLE_SID parameter is not defined in the Windows
registry.
Workaround:
1. Set ORACLE_SID=Oracle_Sid at the command prompt before you use
SQL*Plus.
2. Set the ORACLE_SID parameter in the registry (My Computer\
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_10.2UpgradeHome\
ORACLE_SID).
This issue is tracked with Oracle bug 4534421.
4.2 Limitations with 32-Bit Windows
If you do not have sufficient address space to allocate PGA memory, you can run
into ORA-04030 errors or system commands can fail with OS error 1450 or 997.
The following solutions are suggested:
Run a smaller work load and use less users.
RAC Installations on an Oracle Database Release 10.1.0.4
Cluster
When Oracle Universal Installer is performing a RAC 10g release 2 installation on
a cluster that already has Oracle Database release 10.1.0.4, Oracle Universal
Installer gives you an option of performing an upgrade on any databases
running on the system.
If you select this option to upgrade, Oracle Universal Installer invokes Database
Upgrade Assistant to perform the upgrade. As part of the database upgrade,
Enterprise Manager Database Control is also upgraded. This does not impact the
upgrade itself. The impact is that if the preupgrade version of the database is
10.1.0.4, Database Control may not start on one or more nodes after the upgrade.
As a result, if you run the following command on that node: