Oracle9i

Release Notes Addendum

Release 2 (9.2.0.1.0) for Windows

August 2002

Part No. B10076-01

This document is an update of the Oracle9i Release Notes Addendum Release 2 (9.2.0.1.0) for Windows, Part No. A97617-01, published May 2002. The August updates are included in sections 1. The contents of the May issue are included after section 1.

This Addendum contains important last minute information not included on the Oracle9i Database documentation library CD-ROM or in the \doc directory of the component CD-ROM.

The information in this Addendum is current as of August 2002. For the most current information, refer to updates of this document, which are located at the following Web sites:

http://docs.oracle.com

http://otn.oracle.com/docs/index.htm

This document contains these topics:

1 Specifying the OCOPY Size Option

Using the OCOPY size_1 and size_n options in multiple diskette copy mode, you can specify how OCOPY splits the file to be backed up. Option size_1 specifies the size (in kilobytes) of the first piece. Option size_n specifies the sizes of all remaining pieces. Table 1 shows the OCOPY backup syntax. If the file to be copied is too large to fit on one diskette, the OCOPY utility prompts you to insert new diskettes as needed. If the sizes specified result in more than 10 pieces, OCOPY returns an error.

If you back up a 10 MB hot file specifying size_1=2048 and size_n=4096, the file is split into three pieces of size 2 MB, 4 MB, and 4 MB respectively.

Table 1 OCOPY Backup Syntax in Multiple Diskette Mode

File Type	Syntax
FAT or NTFS files	`C:\> ocopy /B` `old_file` `a: [size_1 [size_n]]`
Logical raw	`C:\> ocopy /B \\.\x: a: [size_1 [size_n]]`
Physical raw	`C:\> ocopy /B \\.\physicaldriven a: [size_1 [size_n]]`

2 Building OCCI Demo for OTT Marker Support (mdemo1)

To build OCCI demo for Object Type Translator (OTT) marker support with the make mdemo1 command, ORACLE_HOME\rdbms\demo\make.bat must be updated.

Add the following lines in make.bat to specify the target (label):

if (%1) == ("mdemo1") goto occiottmakeobj
if (%1) == (mdemo1) goto occiottmakeobj
if (%1) == ("MDEMO1") goto occiottmakeobj
if (%1) == (MDEMO1) goto occiottmakeobj

Add the following target (label) and rules in make.bat after any existing target blocks:

:occiottmakeobj
ott userid=scott/tiger intype=%1.typ outtype=%1out.type code=cpp \ 
hfile=%1.h cppfile=%1o.cpp mapfile=%1m.cpp use_marker=true
cl -GX -DWIN32COMMON -I. -I%ORACLE_HOME%\oci\include -I. -D_DLL \ 
-D_MT %1.cpp %1m.cpp %1o.cpp /link \
/LIBPATH:%ORACLE_HOME%\oci\lib\msvc oci.lib msvcrt.lib \
msvcprt.lib oraocci9.lib /nod:libc
goto end

3 Oracle Internet Directory

This section contains these topics:

3.1 Pre-Upgrade Tasks for Upgrading Oracle Internet Directory

Before upgrading to Oracle Internet Directory release 9.2, the following pre-upgrade tasks must be performed on Oracle Internet Directory release 2.1.1.0 and Oracle Internet Directory release 3.0.1.1 if they were previously upgraded from 2.1.1.0. These steps are not required if Oracle Internet Directory 3.0.1.1 was the first release of Oracle Internet Directory installed on the affected node.

The Oracle Internet Directory Server should be running when steps 2 and 4 are performed.

Important:

If you copy and paste the following code lines into an editor to create a .sql script, remove any breaks at the ends of the long lines of code. Otherwise, the procedure fails.

Create a file del.ldif with the following contents (use no line break characters for the long lines):

dn: cn=subschemasubentry 
changetype:modify 
delete:objectclasses 
objectclasses:( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' SUP 
organizationalPerson STRUCTURAL MAY ( audio $ businessCategory $ carLicense $ 
departmentNumber$ displayName $ employeeNumber $ employeeType $ givenName $ 
homePhone $ homePostalAddress $ initials $ jpegPhoto $ labeledURI $ mail $ 
manager $ mobile $ pager$ photo $ preferredLanguage $ roomNumber $ secretary $ 
uid $ userCertificate $ x500UniqueIdentifier $ userSMIMECertificate $ userPKCS12 ) ) 

dn: cn=subschemasubentry 
changetype:modify 
delete:attributetypes 
attributetypes:( 2.16.840.1.113730.3.1.241 NAME 'displayName' DESC 'Preferred 
Name of a person to be used when displaying entries' EQUALITY caseIgnoreMatch 
SUBSTR caseIgnoreSubstringsMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' SINGLE-VALUE )

Use ldapmodify to load the del.ldif file, substituting my_host and my_port as appropriate:
```
ldapmodify -h my_host -p my_port -v -f del.ldif 
```

Create a file add.ldif with the following contents (use no line break characters for the long lines):

dn: cn=subschemasubentry 
changetype:modify 
add:attributetypes 
attributetypes:( 2.16.840.1.113730.3.1.241 NAME 'displayName' DESC 'Preferred 
Name of a person to be used when displaying entries' EQUALITY caseIgnoreMatch 
SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15' SINGLE-VALUE ) 

dn: cn=subschemasubentry 
changetype:modify 
add:objectclasses 
objectclasses:( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' SUP 
organizationalPerson STRUCTURAL MAY ( audio $ businessCategory $ carLicense $ 
departmentNumber$ displayName $ employeeNumber $ employeeType $ givenName $ 
homePhone $ homePostalAddress $ initials $ jpegPhoto $ labeledURI $ mail $ 
manager $ mobile $ pager$ photo $ preferredLanguage $ roomNumber $ secretary $ 
uid $ userCertificate $ x500UniqueIdentifier $ userSMIMECertificate $ userPKCS12 ) )

Use ldapmodify to load the add.ldif file, substituting my_host and my_port as appropriate:
```
ldapmodify -h my_host -p my_port -v -f add.ldif 
```

After completing the these steps, proceed with the upgrade procedure as described in the Oracle Internet Directory section of Chapter 2, "Preinstallation Requirements" of Oracle9i Database Installation Guide for Windows.

3.2 Oracle Directory Manager

(Oracle bug identification number 2339985)

Problem: When you start Oracle Directory Manager on Windows XP, the Directory Tree view pane (on the left side of the window) appears blank.

Workaround: Slightly resize the Oracle Directory Manager window after you start. Once the window is resized, the tree view appears.

4 Very Large Memory (VLM) and DB_BLOCK_SIZE

With a large DB_BLOCK_SIZE initialization parameter value, the default AWE_WINDOW_MEMORY registry value of 1 GB may not be sufficient to start the database. Out of memory errors display on configurations where the number of least recently used (LRU) latches is high. As a general guideline, increase the AWE_WINDOW_MEMORY registry value by 20 percent.

For example, if DB_BLOCK_SIZE is set to 8 K, AWE_WINDOW_MEMORY is set to 1 GB, and the number of LRU latches is set to 32 (16 processor computer), database startup fails with out of memory errors 27102 and 34. Increasing the AWE_WINDOW_MEMORY value to 1.2 GB fixes the out-of-memory errors.

See Also:

"VLM Instance Tuning" in Chapter 4, "Oracle9i Architecture on Windows" of Oracle9i Database Getting Started for Windows

5 Determining Whether Segments or Tablespaces are Using Compression

This section contains these database management topics:

5.1 Segments and Compression Settings

To find out which database segments use compression, log in to the database as the user SYS, and create the view all_segs with the following create or replace view statement:

SQL> create or replace view all_segs

(owner, segment_name,


partition_name, spare1

as
select u.name, o.name, o.subname, s.spare1
from sys.user$ u, sys.obj$ o, sys.ts$ ts, sys.sys_objects so,

sys.seg$ s, sys.file$ f

where s.file# = so.header_file

and s.block# = so.header_block
and s.ts# = so.ts_number
and s.ts# = ts.ts#
and s.ts# = so.object_id
and o.owner# = u.user#
and s.type# = so.object_type_id
and s.ts# = f.ts#
and s.file# = f.relfile#

union all
select u.name, un.name, NULLL, NULL
from sys.user$ u, sys.ts$ ts, sys.undo $ un, sys.seg$ s,

sys.file$ f

where s.file# = un.file#

and s.block# = un.block
and s.ts# = un.ts#
and s.ts# = ts.ts#
and s.user# = u.user#
and s.type# in (1, 10)
and un.status$ != 1
and un.ts# = f.ts#
and un.file# = f.relfile#

union all
select u.name, to_char(f.file#)|| '.' || to_char(s.block#), NULL, NULL
from sys.user$ u, sys.ts$ ts, sys.seg$ s, sys.file$ f
where s.ts# = ts.ts#

and s.user# = u.user#
and s.type# not in (1,5,6, 8, 10)
and s.ts# = f.ts#
and s.file# = f.relfile#

/

After creating this view, you can issue queries against the view to find out whether a segment currently is compressed, as shown in the following examples:

To determine if a segment is currently compressed, apply the following predicate in a query to the column spare1:
```
bitand(spare1, 2048) > 0
```
For example, to see if segments currently are compressed, issue a statement similar to the following:
```
SQL> select * from all_segs where bitand(spare1,2048) > 0;
```

To determine if a segment contains any compressed blocks, apply the following predicate in a query:

bitand(spare1, 4096) > 0

For example, to see which segments contain any compressed blocks, issue a statement similar to the following:

SQL> select * from all_segs where bitand(spare1, 4096) > 0;

5.2 Tablespaces and Compression Settings

When you want to determine compression settings on a tablespace, log in as SYS, and create the view compression_ts with the following create or replace view statement:

SQL> create or replace view compression_ts (tablespace_name, flags) as 
select ts.name, ts.flags from sys.ts$ ts where ts.online$ !=3;

After creating this view, you can issue queries against it to find out the compression state of tablespaces, such as determining if a tablespace is currently set as DEFAULT COMPRESS, or DEFAULT NOCOMPRESS, as illustrated in the following examples:

To determine if a tablespace is currently set as DEFAULT COMPRESS, use the following predicate:
```
bitand(flags, 64) > 0
```
For example, to see which tablespaces are currently DEFAULT COMPRESS, issue a statement similar to the following:
```
SQL> select * from compression_ts where bitand(flags, 64) > 0
```
To determine if a tablespace is currently set as DEFAULT NOCOMPRESS, use the following predicate:
```
bitand(flags, 64) == 0
```
For example, to see which tablespaces are currently DEFAULT NOCOMPRESS, issue a statement similar to the following:
```
SQL> select * from compression_ts where bitand(flags, 64) == 0;
```

6 Real Application Clusters Installation

If you are installing Oracle9i release 2 (9.2.0.1.0) Real Application Clusters for the first time on a cluster that already contains an Oracle home for a Real Application Clusters database from a previous release, then you must run the Oracle Universal Installer from that node of the cluster that has the install inventory on it. This ensures that the install inventories are synchronized on the nodes with information about the previous Oracle homes.
(Oracle bug identification number 2374492) CLUSTCA GSDCTL START THROWS JRE EXCEPTION. This is an intermittent problem that occurs only during Real Application Clusters installation on Windows NT. If you encounter this problem, exit the installation session. Go to each node in the cluster and run gsdservice -start. This creates and starts the OracleGSDService. This service is used by the system management tools.

7 Using SYS.DUAL for Updates

The use of table SYS.DUAL for updates (including SELECT FOR UPDATES) will be prohibited in a future release. If you need to update SYS.DUAL to enforce concurrency control of your application, see dbmslock.sql as an alternative. SYS.DUAL will still be available for selection.

8 ojspc.bat Script Correction

The ORACLE_HOME\bin\ojspc.bat script refers to a file in an incorrect location. This causes the script to fail immediately. To fix this, edit the script and change:

ORACLE_HOME\jsp\lib\servlet.jar

to:

ORACLE_HOME\lib\servlet.jar

After you save your edits and exit, the script works properly.

9 Editing STATSPACK Toolkit .sql files with Microsoft Notepad

Do not use Microsoft Notepad to edit .sql files in the STATSPACK toolkit. This is because some of these files are UNIX text files and not in CR-LF format. They do not retain their format when opened in Microsoft Notepad. If necessary, these files can be edited with Microsoft Wordpad without this loss of format.

10 Documentation Accessibility

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/.

Accessibility of Code Examples in Documentation

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.

Accessibility of Links to External Web Sites in Documentation

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 is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.