
                Oracle Products Release 7.2 for OS/2 CD-ROM

 Release Notes October 1995

   These release notes include updated information and known restrictions 
   to Oracle7 Server for OS/2 operation and the accompanying products in 
   the Oracle7 Products Release 7.2 for OS/2 CD-ROM. Information on the 
   following products are included in this release note:

   * Oracle7 Server
   * Oracle Database Tools
   * Network Products
   * Pro*C
   * Pro*COBOL
   * SQL*Plus
__________________________________________________________________________

 Oracle7 Server for OS/2
 Version 7.2.2.4.0 Production

   * Starting the Database with a Local Instance

     When starting an Oracle7 database, you must enter a database name in 
     the Oracle Database Manager dialog box. If you do not enter a database 
     name and instance, the Oracle Database Manager defaults to the local 
     database instance. The name of the local database instance is defined 
     in your CONFIG.SYS file. However, if you change or delete the name of 
     your local database instance without making the appropriate changes 
     in the CONFIG.SYS, you will receive an error message. Make sure you 
     give an alias to your local database instance when renaming or 
     creating a new local database.

   * 7.1 and 7.2 Compatibility

     When using the OS/2 Database Manager version 7.1, the parameter 
     compatibility must be set to 7.2 to startup a 7.2 database.
__________________________________________________________________________

 Oracle Database Tools for OS/2 Release Notes
 Version 7.2.2.4.0 Production

   * System Initialization Parameters

     The Initialization Parameters at startup are dependent on the two 
     methods to start the database:
     - SQL*DBA, or
     - the Database Manager tool
     The accompanying User's Guide describes these startup methods.

     If you start your database with SQL*DBA, the database uses the 
     initialization parameters defined in the \ORAOS2\DATABASE\INITORCL.ORA 
     file. If you need to edit this file, you can use any text editor to 
     edit INITORCL.ORA.

     If you start your database with the Database Manager, the database 
     uses the parameters defined in the \ORAOS2\RDBMS72\VS10.INI file. If 
     you need to edit this file, edits are performed using the Database 
     Manager tool through the Edit Database Parameters dialog box.

     To maintain database performance and ensure database recoverability, 
     the VS10.INI file and the INIT.ORA file must be identical in parameter 
     settings. Before you restart the database or after you shut down the 
     database, verify that the VS10.INI file and the INIT.ORA file have the 
     same parameter settings. Performing this prevents degradation of 
     database performance and ensures database recoverability.

   * Modifying the Local Instance System Identifier (SID)

     If you start an instance on your local machine using a SID other than 
     ORCL, Oracle recommends that you update your CONFIG.ORA file and make 
     the following change:
       SQLNET DBNAME LOCAL=2:<local_sid>

     Example: If you want to use the instance named, "test", then define 
     your local system identifier as:
       SQLNET DBNAME LOCAL=2:test

     When you use any of the database tools, specify 'LOCAL' as your 
     database connect string.
__________________________________________________________________________

 Oracle Network Products for OS/2
 Version 2.2.2.0.1 Production
 
 *** Oracle NetBIOS Protocol Adapter for OS/2

   * Configuring Oracle NetBIOS Protocol Adapter in an OS/2 Environment

     The following explains the relationship between NetBIOS resource 
     allocation and the number of connections you may have in an OS/2 
     client/server environment. Please read the information and examples 
     carefully before configuring your system to your number of connections.

     Note: This discussion assumes that all NetBIOS resources configured 
     are available to the Oracle NetBIOS protocol adapter.

     Each Oracle connection requires 2 or more NetBIOS sessions. The number 
     of sessions per connection depends on the maximum number of database 
     links required in SQL statements.

     If no database links are required in a particular Oracle client/server 
     environment, you can decrease the number of server sessions per 
     connection to enable more connections.

     To configure the server sessions:
     1.  Create the PROTOCOL.ORA file in ORACLE_HOME\NETWORK\ADMIN directory 
         on the server machine.
     2.  Enter
           netbios.nsessions=x
         where "netbios.nsessions" is the key word, and "x" is the number 
         of sessions used for each connection, a value between 2 to 99.

     An Oracle server requires that the netbios.nsessions=2 or higher. The 
     default is netbios.nsessions=3.

     Note: The number of NetBIOS connections that an OS/2 server can handle 
     depends upon the server's NetBIOS and memory resources. Your network 
     card may have difficulties obtaining more than twenty connections. For 
     example, the Etherlink III network adapter card--using the 
     netbios.nsessions=2, 48 sessions, 144 NCBs, and 96 Names--supports 
     a maximum of 20 connections.

     For the default of 3 sessions per server, only 2 database links are 
     allowed in SQL statements. You can increase the number of database 
     links that an Oracle server can handle by increasing the number of 
     sessions (netbios.nsessions). The maximum number of sessions is 99.

     Typical scenarios for using Oracle NetBIOS protocol adapter include 
     the following:

       1 Network Card                        2 Network Cards
       netbios.nsessions = 2                 netbios.nsessions = 2
       netbios.nsessions = 3 (default)       netbios.nsessions = 3 (default)

     The two tables below provided examples of how to set the values and 
     provide resources, including resources for the network listener 
     process(es), if you are using a single network card.
                                         
     Oracle       
     Connections   Sessions                    NCBs                        Names
       Formula:    (# of connections times 3)  (# of connections times 9)  (# of connections times 6)
                     + 3 for listener            + 9 for listener            + 6 for listener          
         5         15 + 3                      45 + 9                      30 + 6
        10         30 + 3                      90 + 9                      60 + 6

     Table 5   NETBIOS.NSESSIONS=3 (default setting) with 1 Network Card
             
     Oracle      
     Connections   Sessions                    NCBs                        Names
       Formula:    (# of connections times 2)  (# of connections times 6)  (# of connections times 4)
                   + 2 for listener            + 6 for listener            + 4 for listener          
        10         20 + 2                      60 + 6                      40 + 4
        20         40 + 2                      120 + 6                     80 + 4

     Table 6   NETBIOS.NSESSIONS=2 with 1 Network Card

     The two tables below provided examples of how to set the values and 
     provide resources, including resources for the network listener 
     process(es), if you are using two network cards.

     Oracle      
     Connections   Sessions                    NCBs                        Names
       Formula:    (# of connections times 6)  (# of connections times 9)  (# of connections times 6)
                   + 3 + 3 for listeners       + 9 + 9 for listeners       + 6 + 6 for listeners 
         5         30 + 3 + 3                  45 + 9 + 9                  30 + 6 + 6
        10         60 + 3 + 3                  90 + 9 + 9                  60 + 6 + 6

     Table 7   NETBIOS.NSESSIONS=3 (default setting) with 2 Network Cards

     Oracle      
     Connections   Sessions                    NCBs                        Names
       Formula:    (# of connections times 4)  (# of connections times 6)  (# of connections times 4)
                   + 2 + 2 for listeners       + 6 + 6 for listeners       + 4 + 4 for listeners 
        10         40 + 2 + 2                  60 + 6 + 6                  40 + 4 + 4
        20         80 + 2 + 2                  120 + 6 + 6                 80 + 4 + 4

     Table 8   NETBIOS.NSESSIONS=2 with 2 Network Cards

 *** Oracle TCP/IP Protocol Adapter for OS/2

   * Running IBM TCP/IP V2.0 for OS/2 under OS/2 Warp

     IBM supports the IBM TCP/IP V2.0 for OS/2 Base Kit with patch revision 
     UN64092 Corrective Service Diskette(s) [CSD].

     You can obtain the CSD from IBM via the internet site 
     SOFTWARE.WATSON.IBM.COM, which is an FTP server that accepts anonymous 
     user connections.

   * JSB VSLOS2.INI file must have 'transport=' line

     The OS/2 TCP/IP Protocol Adapter 2.1.4.0.1 relies on the VSLOS2.INI 
     file to set the runtime choice for the third party protocol stack. If 
     you have problems connecting, verify that the 'transport=' line of 
     \OS2\VSLOS2.INI targets the correct vendor reference. The vendor 
     reference choices and corresponding transport lines are listed below:

       Third Party TCP/IP      CONFIG.ORA TCP_VENDOR   VSLOS2.INI transport
         IBM TCP/IP V2.0         TCP_VENDOR=IBM          transport=ibm2
         FTP PC/TCP              TCP_VENDOR=FTP          transport=ftp
         Novell LAN Workplace    TCP_VENDOR=LWP          transport=novlwp

   * Configuration Steps for OS/2 V2.1x Systems

     If you are using an OS/2 V2.1x System, substeps 3 and 5 of Step 3 of 
     the Configuration Steps section of TCP/IP for OS/2 should read as follows:

     3. Open the Settings dialog box
          OS/2 V2.1x Systems
            click on the right hand arrow next to the "Open" menu item
            click on the "Settings" menu option

     5. Open the WIN-OS/2 Settings screen
          click on the WIN-OS/2 Settings button
__________________________________________________________________________

 Pro*C for OS/2
 Version 2.1.2.0.0 Production

   * No Support for NLS

     This release of Pro*C does not fully support National Language Support (NLS).
     The message file, PR2US.MSB, is not translated to other languages. Therefore,
     when specifying any language, PR2US.MSB defaults to the English version.

   * C++ Syntax Error

     A syntax error message occurs when you add C++ remarks after the statement
       #include<file.h>.

     Example:
       #include <stdio.h>   // this is a test

     As a solution, move the remark to any other line or use the parse=none option
     instead of the parse=full.

     Note: For Borland C++ users, the iostream.h includes the line:
       #include < mem.h>  //to get memcpy and NULL.

     The syntax error message you receive is pcc-2014. The .pc file is preprocessed
     correctly, so you can disregard the error message and continue the compilation.
     This problem also appears in the C++ sample files as cppdemo1.pc that includes
     iostream.h. These files process correctly and are usable.

     Attention: A software patch will be issued to resolve the limitations in this release
     of Pro*C for OS/2.
__________________________________________________________________________

 Pro*COBOL for OS/2
 Version 1.7.2.0 Production

   No restrictions were noted at time of release.
__________________________________________________________________________

 SQL*Plus for OS/2
 Version 3.2.2.0 Production

   No restrictions were noted at time of release.

