|
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|
| Oracle9i Client Release Notes Release 2 (9.2.0.1.0) for Windows Part Number A97205-01 |
|
Release 2 (9.2.0.1.0) for Windows
May 2002
Part No. A97205-01
These Release Notes contain important last minute information not included in the Oracle9i Database documentation library. They may also contain information regarding products not on your component CD-ROM.
This document contains these topics:
Meet the requirements in this section before installing Oracle9i.
This section contains these topics:
The information in these Release Notes is current as of the release date for Oracle9i. For the most current information, refer to the online Release Notes, which are located at the following Web site:
http://docs.oracle.com
If you need assistance with navigating the Oracle Documentation site, refer to the following Web site:
http://docs.oracle.com/instructions.html
To download free release notes, installation documentation, white papers, or other collateral, visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at:
http://otn.oracle.com/admin/account/membership.html
If you already have a username and password for OTN, then go directly to the documentation section of the OTN Web site at:
http://otn.oracle.com/docs/index.htm
To access the database documentation search engine directly, visit:
http://tahiti.oracle.com
Refer also to the Certify Web pages on OracleMetaLink, which provide certified configuration information for Oracle and non-Oracle products. To access Certify:
http://metalink.oracle.com
Our goal is to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle Server release 9.2 supports accessibility features. To make best use of these accessibility features, Oracle Corporation recommends the following software configuration:
Additional accessibility information for Oracle products can be found at:
http://www.oracle.com/accessibility
For the latest configuration information, and for information on addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at:
http://www.oracle.com/accessibility/faq.html
Additional product README files are located:
\doc\readmes directory of the first component CD-ROM. These README files are accessible before installation.
ORACLE_BASE\ORACLE_HOME directory. These README files are accessible after installation.
ORACLE_BASE\ORACLE_HOME\relnotes directory. These README files are accessible after installation.
Oracle9i is not supported on Windows 95. Ignore occurrences of support for Windows 95 in the Oracle9i Database documentation library.
This section contains these topics:
Installation may hang on Windows NT while registering one of the dynamic link libraries (DLLs). This hang occurs because of Microsoft's known regsvr32 problem with silent registration. This problem is with version 2.40.4514 of Microsoft's Oleaut32 DLL. The workaround is to terminate the regsvr32 process using Windows NT Task Manager. Terminating this process allows the installation to continue.
You can register the DLL later by executing the following command from the command prompt:
C:\> regsvr32 ORACLE_BASE\ORACLE_HOME\bin\OraOLEDB.dll
|
See Also:
This Microsoft Knowledge Base article (PRB: Oleaut32 Hidden Window Blocks Apps Broadcasting Messages Q189427) at the Microsoft Product Support Services Web site. Microsoft Web site organization is subject to change. If you cannot find this URL, search for key words from the main Microsoft Web page, such as "Q189427" and "Oleaut32".
|
When mounting a CD-ROM on a Novell drive to a Windows NT client and running Oracle Universal Installer, the following error may appear:
The Java Runtime Environment was not found at location hence the Oracle Universal Installer cannot be run.
Because the Novell server does not support long filenames by default, the directory path for JRE_LOCATION is not recognized (some of the directory names have more than eight characters). Therefore, this configuration is not supported. Try mounting the CD-ROM locally or on a Windows NT Server. When you still want to use the Novell server as a CD-ROM file server, you need to install the OS/2 Namespace Extension to activate long filename support for NetWare.
On systems with a combination of Windows NT 4.0 Service Pack 5.0 and an ATI display driver, a memory dump occurs when the Oracle Universal Installer window is moved around the screen. Selecting a smaller display for the screen can reduce the frequency of this occurrence. This problem is a display driver conflict and no Windows NT patch is available at this time.
When installing Oracle9i on dual boot systems, the software uses the same physical space on both operating systems. Therefore, any tasks done on one operating system are also done on the other operating system, including deinstallation.
This situation can be avoided by performing the following steps:
For installations using a response file, the path to the response file must be the full path on the computer. Oracle Universal Installer does not properly handle relative paths.
Due to a Sun JRE bug, a command prompt window appears whenever a configuration tool is launched. Leave this window open until the configuration tool finishes. Closing the window kills the process and causes the configuration tool to fail.
When you use Database Configuration Assistant to create a custom database that includes Oracle JVM (OJVM), be aware that it can take over an hour to finish loading OJVM into the database, depending on your computer's hardware configuration.
If you use Database Configuration Assistant to create a database, be aware that you are required to change the SYS and SYSTEM passwords at the end of the configuration process. This is a new security procedure designed to protect access to your data.
The mod_plsql component in Oracle HTTP Server depends on the environment variable WV_GATEWAY_CFG. Since there can only be one value for this variable in the system, it is not possible to start multiple Oracle HTTP Server listeners using the Services dialog box of the Control Panel.
This limitation can be overcome by starting one of the Oracle HTTP Server listener's from the Services dialog box of the Control Panel and the remaining ones using the command prompt after setting WV_GATEWAY_CFG appropriately.
For example, assume that you have two Oracle HTTP Server instances installed. Listener1 is installed under c:\oracle\home1 and Listener2 is installed under c:\oracle\home2. Start both listeners as follows.
WV_GATEWAY_CFG. For example, if WV_GATEWAY_CFG is set to c:\oracle\home1\Apache\modplsql\cfg\wdbsvr.app, then Listener1 is the one that can be started from the Control Panel.
apache_start.cmd with the following commands:
set WV_GATEWAY CFG=c:\oracle\home2\Apache\modplsql\cfg\ wdbsvr.appc:\oracle\home2\Apache\Apache\Apache -k start
apache_stop.cmd with the following commands:
set WV_GATEWAY_CFG=c:\oracle\home2\Apache\modplsql\cfg\ wdbsvr.app c:\oracle\home2\Apache\Apache\Apache -k shutdown
apache_start.cmd from the command prompt.
apache_stop.cmd from the command prompt.
The Note in Oracle9i Database Getting Started for Windows, chapter 4, section "Oracle9i Scalability on Windows", sub section "Support for Very Large Memory (VLM) Configurations" after step 4 "Initialization parameters DB_BLOCK_BUFFERS and DB_BLOCK_SIZE must be set to values you have chosen for Oracle9i database", should be as follows:
(Oracle bug identification number 2255993). Oracle Workflow provides versions of the following Windows files as part of the installation for Oracle Workflow Builder:
When you install Oracle Workflow Builder, Oracle Universal Installer checks whether there are already existing versions of these files in the Windows system directory.
If you plan to use Oracle supplied operating system dependent (OSD) clusterware, then you must install Oracle9i release 2 (9.2) OSD clusterware on all nodes of the cluster on which you plan to run an Oracle9i release 2 (9.2) cluster database instance. This is the case even if you had installed Oracle9i release 1 (9.0.1) OSD clusterware on these nodes. Use Oracle Cluster Setup Wizard to install this OSD clusterware.
For accessibility requirements, Oracle Cluster Setup Wizard requires JAWS 4.0.2 as the minimum configuration.
(Oracle bug identification number 2279588).
Problem: When you try to retrieve the configuration information for a cluster database from the SRVM configuration repository using SRVCTL, it expects that database name argument be the same case as that in the SRVM configuration repository.
Use this workaround:
SRVCTL, provide the database name and instance names arguments in lowercase.
If you plan to create an Oracle Enterprise Manager repository in an existing database, and plan to use the DRSYS tablespace for the repository, ensure that the DRSYS tablespace raw partition data file has an additional 50 MB of free space. This is in addition to the 250 MB size documented for this raw partition.
If you use Oracle Database Upgrade Assistant to upgrade an earlier Oracle database version (the source database) to Oracle9i release 2 (9.2) (the target database), then the target database will always use the server parameter file SPFILE by default to store init.ora file parameters.
If the source database also uses SPFILE (either a cluster file system file or a shared raw partition), then the target database also uses the same SPFILE.
If the source database does not use an SPFILE, then the target database uses a default server parameter file, spfile.ora, which is located in the %ORACLE_HOME%\database directory.
If your platform does not support a cluster file system, you must move the SPFILE to a shared raw partition, using the following procedure:
SPFILE with the following commands:
C:\ sqlplus "/ as sysdba" SQL> create pfile='?\database\initdbname.ora' from spfile='?\ database\spfile.ora'; SQL> create spfile='\\.\dbname_spfile' from pfile='?\database\ initdbname.ora';
SQL> exit;
where dbname is the name of your database.
%ORACLE_HOME%\database\initsid.ora file, where sid is the system identifier of the instance on the node. The initsid.ora file must contain the following line:
SPFILE='\\.\dbname_spfile'
initsid.ora file to the remote nodes on which the cluster database has instances, where sid in the original file name corresponds to the system identifier of the local node instance and sid in the target file name corresponds to system identifier of the instance on the remote node.
For example,
C:\ database> copy initoradb1.ora \\node2\c$\oracle\ora9i\database\ initoradb2.ora
C:\ srvctl stop database -ddbnameC:\ srvctl start database -ddbname
After you have created a cluster database using Database Configuration Assistant, SYSDBA privileges are automatically revoked for all users. You must grant SYSDBA privileges explicitly to the database user account that you plan to use for adding or deleting an instance to or from the cluster database.
For example, to grant SYSDBA privileges to the administrative user SYS, issue the following commands:
C:\ sqlplus "/ as sysdba" SQL> grant sysdba to sys; SQL> exit;
The space requirements listed on the Available Products window of Oracle Universal Installer apply to installations that include a database. If you select the Software Only configuration type, then 2 GB is required.
(Oracle bug identification number 1817913). Because CONNECT INTERNAL is no longer supported in Oracle9i, operating system authentication must be used for SYSDBA authorization to upgrade an Oracle7 release 7.3.4 database.
This section contains these topics:
Oracle Corporation supports NATIVE PL/SQL compilation using the Microsoft Visual Studio 6.0 C compiler, the LD link-editor, and the GMAKE make utility.
When a procob application is run, which is not linked using the /litlink option, the following error may occur at runtime:
Load error: file 'ORASQL8'
The solution is to copy orasql9.dll to orasql8.dll in the same directory where orasql9.dll exists.
Different Java Developer's Kit versions are used on Windows 2000 and Windows XP. Review individual product readmes for detailed information.
Before using Oracle Performance Monitor for Windows NT to view Oracle-specific counters, you must specify the SYSTEM password using operfcfg.exe located in the ORACLE_HOME\bin directory.
To set the SYSTEM password, enter the following command:
C:\> operfcfg.exe -U SYSTEM -P password [-D database_name]
Alternatively, if you have Oracle Administration Assistant for Windows NT, then select Properties from the popup menu. After entering the password for SYSTEM, click the Apply button, and then OK button.
Oracle Services for Microsoft Transaction Server supports .NET transactional applications with OLE DB .NET through the Oracle Provider for OLE DB and ODBC .NET through the Oracle ODBC driver.
(Oracle bug identification number 605297). If the value of the parameter MAX_SHARED_SERVERS is smaller than the value of TRANSACTIONS, then Real Application Clusters may hang.
If you are using shared server configurations on Real Application Clusters, then set TRANSACTION to a value smaller than MAX_SHARED_SERVERS to avoid this bug.
(Oracle bug identification numbers 2244347 and 2244356). For Java versions later than Java 1.1.n, whenever a monitor component has 16 colors, Oracle Universal installer 2.2.0.1.0 fails to come up. This is because monitors with 16 colors are not supported by Sun in JDK versions later than Java 1.1.n
Due to a Sun JRE bug, keyboard navigation may not work when two consecutive modal dialogs are displayed by Oracle Universal Installer. This happens in the following two locations:
To interact with these dialogs, the user must either use the mouse instead of the keyboard or switch to another application, then switch back to Oracle Universal Installer.
This section contains these topics:
By default Oracle Internet Directory server is started on port 389. If this port is unavailable, Oracle Internet Directory server starts on a different port that is logged in file the ORACLE_HOME/ldap/install/oidca.out.
Oracle Internet Directory upgrade is supported from Oracle Internet Directory release 2.1.1.x and 3.0.1.x. If the Oracle home where you intend to perform the upgrade of Oracle Internet Directory also contains a complete Enterprise Edition installation, then you must perform the Oracle Internet Directory upgrade before the Enterprise Edition upgrade.
If the Oracle home where you intend to perform the upgrade of Oracle Internet Directory also contains a complete Enterprise Edition installation, then you must perform the Oracle Internet Directory upgrade before the Enterprise Edition upgrade.
When performing Oracle Internet Directory installation through the Custom installation type, do not change the global database name or the Oracle system identifier (SID) when prompted by Database Configuration Assistant.
Installing Oracle Internet Directory release 9.2 using the Custom installation type launches Database Configuration Assistant during the installation sequence. Because you have already entered this information, do not change either the Global Database Name or the Oracle SID from within Database Configuration Assistant.
To run the Directory Integration Server on Windows NT:
odisrvreg.
oidctl.
When installing Oracle Internet Directory in an Oracle home where the Oracle Enterprise Edition for Oracle9i release 2 (9.2) is already installed, the option to create a new database for Oracle Internet Directory does not work. You must create a database prior to the Oracle Internet Directory installation. After the database has been created, use this database for your Oracle Internet Directory installation by choosing the option to use an existing database and specifying the appropriate database SID.
The Oracle JDBC class files, classes12.zip and classes111.zip, provide character set support for the thin and Oracle Call Interface (OCI) drivers. The files contain all the necessary classes to provide complete character set support for all Oracle character sets for CHAR and NCHAR datatypes not retrieved or inserted as part of an Oracle object or collection type. See "Oracle Character Datatypes Support" of Oracle9i JDBC Developer's Guide and Reference for a description of CHAR and NCHAR datatypes.
However, in the case of the CHAR and VARCHAR data portion of Oracle objects and collections, the thin and OCI drivers require nls_charset12.zip for JDK 1.2.x and 1.3.x or nls_charset11.zip for JDK 1.1.x for most Oracle character sets (except US7ASCII, WE8DEC, WE8ISO8859P1, and UTF8). These two nls_charset*.zip files are included in the Oracle JDBC driver installation. To obtain this support, you must add the appropriate nls_charset*.zip file to your CLASSPATH or the logical equivalent, depending on the application.
(Oracle bug identification number 1892470). If you are trying to start Object Type Translator (OTT) from the command prompt and do not receive any output, make sure that the CLASSPATH includes the following:
Java_installation\jdk1.3.1\lib\dt.jar; Java_installation\jdk1.3.1\lib\tools.jar;%CLASSPATH%;
The following requirements are also necessary to start OTT from the command prompt:
PATH must point to Java_installation\jdk1.3.1\bin before \bin.
ocijdbc9.lib must be pointed to by the LIB environment variable. The location of ocijdbc9.lib is %ORACLE_HOME%\lib.
This section contains these topics:
Current user database links are not supported with Windows Native Authentication.
On Windows NT and Windows 2000, the Oracle database service runs in the security context of the LocalSystem or a specific local or domain user. When using Active Directory, if the database service runs in the security context of LocalSystem, manually add the computer name in which the database service is running to the access control entries on the OracleDBSecurity container object. Set read permissions on the OracleDBSecurity container object.
For example, if the database service OracleServiceORCL is running in the security context of LocalSystem in the computer MYPC1, then add MYPC1 to the access control entries on the OracleDBSecurity container object with READ permissions on the OracleDBSecurity object.
(Oracle bug identification number 1993113) Oracle Net Configuration Assistant fails while upgrading the Oracle8i release of Oracle Schema and Oracle Context in Active Directory. The Oracle Schema and Oracle Context in Active Directory can be upgraded manually for Active Directory as follows:
orclProductVersion: 90000 or orclVersion: 90000.
dn: cn=BASE,cn=OracleSchemaVersion,cn=configuration,AD_Domain_DN changetype: add objectclass: orclSchemaVersion cn: BASE orclProductVersion: 90000 dn: cn=NET,cn=OracleSchemaVersion,cn=configuration,AD_Domain_DN changetype: modify replace: orclProductVersion orclProductVersion: 90000 dn: cn=RDBMS,cn=OracleSchemaVersion,cn=configuration,AD_Domain_DN changetype: modify replace: orclProductVersion orclProductVersion: 90000 dn: cn=OracleContext,AD_Domain_DN changetype: modify replace: orclVersion orclVersion: 90000
dc=acme,dc=com
C:\>ldapmodify-Z-hAD_Host_Name-ffilename
where:
AD_Host_Name is the host name of the Windows 2000 Domain Controller where your Active Directory is located and filename is the name of the file you created in steps 1 and 2.
(Oracle bug identification number 993548). When operating system native authentication is not enabled for the database, users are unable to view the database thread information using Oracle Administration Assistant for Windows NT. If this is the case, and users want to view the database thread information using Oracle Administration Assistant for Windows NT, they must run a utility called ocfgutil.exe with the arguments username and password. This utility stores the username and password in the registry location \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleOraConfig, which is read by the Oracle Remote Configuration Agent to log in to the database.
This section supplements generic information provided in Oracle9i Net Services Administrators's Guide to configure a listener on Windows operating systems to exclusively handle external procedures.
For a higher level of security, you are instructed in Oracle9i Net Services Administrators's Guide to start the listener for external procedures from a user account with lower privileges than the oracle user. For Windows operating systems, this requires that you change the user account from LocalSystem to a local, unprivileged user for the OracleHOME_NAMETNSListenerextproc_listener_name service.
To change the listener account:
OracleHOME_NAMETNSListenerextproc_listener_name service by selecting Stop.
OracleHOME_NAMETNSListenerextproc_listener_name service and then display the properties of the service.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.
This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Oracle is a registered trademark, and Oracle9i, Oracle8i, Oracle8, Oracle interMedia, PL/SQL, and Pro*C are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2002, Oracle Corporation.
All Rights Reserved.
|
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|