print Printer View e-mail E-mail this page Bookmark Bookmark

SQL*Plus Release Notes Continued

<< Back

5 Bugs Fixed

The following section lists bugs fixed in SQL*Plus. Numbers in parentheses following the problem description refer to bug numbers in the Oracle Bug Database.

5.1 Bugs Fixed in SQL*Plus 9.2 Production

  • Describe command now produces the correct result for a VARRAY of NCHAR (2216859)

  • SQL*Plus no longer terminates abnormally when entering SHOW ERRORS for an errored PL/SQL block which contains comments between the package type and package name (2026644)

  • Correct number of characters retrieved for a SELECT of NCLOB datatype with NLS_NCHAR environment parameter set (1987259)

  • SQL*Plus displays an error if a substitution variable exceeds 240 bytes (1934520)

  • When attempting to connect to an invalid connection identifier as a privileged user, either an invalid error is reported, or the user is granted an idle instance connection to a local database (1778036)

  • DESCRIBEing an object type after a SELECT no longer causes garbage in the object name (2151078)

  • Setting NLS_DATE_FORMAT from ALTER SESSION within a function changes the date format (1914259)

  • Running a SQL script with a path longer than 80 characters no longer results in abnormal termination on Windows NT (1925208)

  • SQL*Plus Windows graphical user interface no longer terminates abnormally with SET PAUSE ON (1902459)

  • SET CONSTRAINTS now works in NLS MODE (1883466)

  • Now able to change the password for a username that contains white space, such as "ab ab" (1852419)

  • No longer able to login with invalid Oracle account for OS authenticated user (1815491)

  • Now displays correct output in multibyte for WORD_WRAPPED and SERVEROUTPUT when MARKUP HTML ON (1805106)

  • SELECT on a TIMESTAMP datatype on HP (64 bit) platform no longer results in "ORA-01877: string is too long for internal buffer" (1782816)

  • A failed connection request to a remote database no longer results in connection to a local database without the user being aware this has occurred. An error is now displayed (1777627)

  • Control-C interrupts in a SQL*Plus session now reaches shadow process (1751168)

  • SQL*Plus no longer terminates abnormally when using the BREAK command (1723633)

  • EOF encountered during substitution with input redirection no longer results in error (1686205)

  • SQL*Plus no longer terminates abnormally when using DESCRIBE command to describe a nested table of type 'anydata' (1656591)

  • SQL*Plus no longer terminates abnormally when using the DESCRIBE command to describe a public synonym for a non-existent table (1727607)

  • SQL*Plus no longer terminates abnormally when trying to insert data that is 4000 characters long (1397704)

  • The column width of the column defined "fold_after" is now correctly set (716638)

  • HTML output from COLUMN: is no longer missing after word_wrap (1872657)

  • The error indicator shows the position of the error in HTML output (including iSQL*Plus) (1477471)

  • DESCRIBE of FLOAT(x) now shows FLOAT(x) instead of NUMBER(x) DESCRIBE of REAL now shows FLOAT(63) (2042623)

  • SQL*Plus no longer terminates abnormally when trying to copy an object datatype which is not supported in the COPY command (2221928)

  • Internal code changes (2127638, 2088130, 2088085, 1930054, 1903571, 1808191, 1776566, 1764208, 1764205, 1762466, 1635304, 1584406, 1479508, 1855842)

5.2 Bugs Fixed in SQL*Plus 9.0.1 Production

  • Recovery dialog no longer prompts for a log when end of disabled thread reached (1111709)

  • Recovery dialog no longer terminates when bad log name is entered (1169101)

  • Describe command can now describes synonyms based on schema object created with double quotes (1598520, 1217127, 1035350)

  • SQL*Plus now displays ORA-28002 when password expiry is in grace period (1326865)

  • SHOW ERRORS shows the errors for ALTER TYPE COMPILE BODY (1341524)

  • SQL*Plus now gives an error instead of prompting for a password when a user is not in the DBA group (1657213)

  • SQL*Plus now accepts scripts from the Operating System with a space between the '@' sign and the script name (1714104, 1617267)

  • SQL*Plus now handles input files that have a control/d (EOF) character (1265859)

  • "SP2-0614: Server version too low for this feature" will no longer appear when "glogin.sql" contains 'set serveroutput on' (1552238)

  • SQL*Plus now allows for blank spaces before the '/' to terminate and execute a PL/SQL block (1312929)

  • An abnormal termination when re-executing a select with a break statement has been fixed (996778)

  • The TABLE clause was added to SET MARKUP usage message (1288901)

  • AUTOTRACE no longer gives an error for small values of ARRAYSIZE (1364197)

  • Some problems with SHOW ERRORS for Java source with multibyte characters have been fixed (1458572)

  • The usage statement is no longer displayed when issuing a valid 'SHOW ERRORS' command for a Java source/class (1485281)

  • HTML tags for output after a SKIP are now valid (1477515)

  • A problem with HTML tag markup and BTITLE has been fixed (1477529)

  • Numeric variables in titles are no longer displayed correctly if a NULL value is the first data item selected (1265664)

  • DESCRIBE object does not give consistent information for object type method has been fixed (997861)

  • SQL*Plus bind variable assignment results in a 'PLS-00553' error if issued within the same SQL*Plus session used to shutdown and restart the database (1335603)

  • Compilation of a Java source results in SQL*Plus hanging when the character set is a multi-byte character set (1381064)

  • Now when MARKUP HTML OFF is issued, no HTML output is produced. It does not matter if MARKUP HTML SPOOL is ON or OFF (1420656)

  • An invalid password change issued from the SQL*Plus PASSWORD command should not disconnect the user (1620381)

  • SET AUTOTRACE ON does not work with certain character set on the client side. It results in ORA-00923 (1200008)

  • SQL*Plus should allow CONNECT AS SYSDBA when instance is hung (1508783)

  • Internal code changes (1290197, 1301950, 1353644, 1286724, 1674627, 1705536, 1713564, 1265887, 1687097, 1698337, 1698361, 1698379, 1698422, 1702306, 1705970, 1706081, 1707889, 1715102, 1715112, 1715121, 1716888)

6 Support

For SQL*Plus and iSQL*Plus support, please contact your local Oracle Support Services Center. There is also an iSQL*Plus Discussion Forum on the Oracle Technology Network located at / which may be helpful.

7 Desupport Notices

This section gives advance notice of the desupport of SQL*Plus commands and interfaces. It is not official notice of desupport dates, nor is it intended to replace the Oracle obsolescence process. This information provides you with advance warning that Oracle Corporation intends to desupport these features/interfaces in upcoming releases.

7.1 COPY Command

COPY supports the datatypes listed for the COPY command in the SQL*Plus User's Guide and Reference, but no new datatypes will be supported. The COPY command may be obsoleted in a future release of SQL*Plus.

7.2 Windows Graphical User Interface

The SQL*Plus for Windows graphical user interface (GUI) will be desupported in future releases of SQL*Plus. The browser-based iSQL*Plus user interface will replace the SQL*Plus for Windows GUI. The SQL*Plus for Windows command line (DOS) interface will continue to be supported.

8 Documentation Errata

The section describes known errors in the documentation.

8.1 iSQL*Plus Online Help

The following are known changes to the iSQL*Plus online help by section.

8.1.1 User Interface

In iSQL*Plus Extension for Microsoft Windows, under the heading "Context Menu" there should be an additional bullet point:

  • choose the language to use from a list of configured languages

8.1.2 Configuring iSQL*Plus

In Configuring the Client Tier>Retained Session Settings, the first three bullet points should not appear:

    • Username

    • Connection identifier

    • Privilege

In this same section, the final para should read:

    Your username, password and your output preferences are not saved.

In Configuring the iSQL*Plus Server, the following bullet points should be added:

    • Set the iSQLPlusHashTableSize parameter

    • Set the iSQLPlusConnectIdList parameter

    • Set the -idle-timeout parameter

    • Set the iSQLPlusAllowUserEntMap parameter

The following subsections associated with the bullet points should also be added:

    Setting the iSQL*Plus Hash Table Size Parameter

    The number of hash table entries is defined by the iSQLPlusHashTableSize initialization parameter. Each user session consumes one entry in the hash table even if it is idle. Its default value is derived from the value of the iSQLPlusNumberOfThreads parameter value. However, iSQLPlusHashTableSize can be set independently to tune the system.

    You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the hash table size. The syntax of the line to change in the configuration file is: 

    FastCgiServer ... -initial-env iSQLPlusHashTableSize=n

    Where n is the number of entries in the hash table.

    Enabling or Disabling Restricted Database Access

    The restricted database parameter limits the databases that users can access in iSQL*Plus. When enabled, a dropdown list of available databases is displayed in place of the Connection Identifier text field on the Login screen. This allows greater security for iSQL*Plus Servers in hosted environments. Connection identifiers are listed in the order defined in iSQLPlusConnectIdList.

    You can edit the iSQL*Plus configuration file, isqlplus.conf, to restrict database access. The syntax of the line to change in the configuration file is: 

    FastCgiServer ... -initial-env "iSQLPlusConnectIdList=SID1, SID2,..."

    where SID1, SID2, ... is a comma separated list of Oracle Net connection identifiers specifying permitted databases. For example: 

    FastCgiServer ... -initial-env "iSQLPlusConnectIdList=ABC1, PROD2, DEV3"

    Note the use of quotes in the example. The opening quote must occur before the iSQLPlusConnectIdList parameter name, the closing quote at the end of the list of SIDs.

    For more information about restricted database access, see "Enabling or Disabling Restricted Database Access".

    Setting the iSQL*Plus Idle Timeout

    The FastCGI timeout parameter or idle timeout is the time the Oracle HTTP Server waits for results from iSQL*Plus. It is set to a value likely to prevent iSQL*Plus timing out before the web browser. It is sufficient for many long queries to return results before iSQL*Plus times out.

    The idle timeout should not be confused with the iSQLPlusTimeOutInterval which manages the lifetime of a user's session.

    You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the idle timeout value. The syntax of the line to change in the configuration file is: 

    FastCgiServer ... -initial-env -idle-timeout=n

    Where n is the number of seconds of the Oracle HTTP Server waits for results from iSQL*Plus. The default value is 3600 seconds.

    Controlling User Entity Mapping

    In HTML, entity mapping replaces characters of special significance with printable representations of those characters. Entity mapping is enabled by default, preventing the use of user defined HTML in iSQL*Plus output. The entity mapping parameter controls whether an iSQL*Plus Server permits users to change the entity mapping setting.

    You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the iSQLPlusAllowUserEntMap value. The syntax of the line to change in the configuration file is: 

    FastCgiServer ... -initial-env iSQLPlusAllowUserEntMap=all|none

    Where the parameter is set to none, or if it does not exist or has an invalid value, the use of SET MARKUP HTML ENTMAP and COLUMN ENTMAP will generate an error. If the MARKUP ENTMAP radio button on the System Variables screen is changed to Off, the value is ignored and reverts to On. The default value for iSQLPlusAllowUserEntMap is none.

    Where the parameter is set to all, users can execute SET MARKUP HTML ENTMAP and COLUMN ENTMAP commands to change the status of entity mapping for the iSQL*Plus session or report column. This enables custom HTML to be included in iSQL*Plus report output.

8.1.3 Using iSQL*Plus

In Username and Password, the following text is incorrect:

    Default logins are created and displayed in messages during Oracle9i installation. The default login username/password combinations created are:

    • SYS/CHANGE_ON_INSTALL

    • SYSTEM/MANAGER

    Default passwords and your database account password should be changed as soon as possible. You can change your password in the Change Password screen which is accessed from the Preferences screen. See Changing Your Password.

It should read:

    Default logins are created and you are prompted for associated passwords during Oracle9i installation. The default login usernames created are:

    • SYS

    • SYSTEM

    You can change your password in the Change Password screen which is accessed from the Preferences screen. See Changing Your Password.

8.2 SQL*Plus User's Guide and Reference

The following are known changes to the SQL*Plus User's Guide and Reference by chapter.

8.2.1 Chapter 3, Configuring SQL*Plus

In iSQL*Plus Configuration > Configuring the Middle Tier: iSQL*Plus Server > Editing the iSQL*Plus Configuration File, the following bullet point should be added:

    • iSQLPlusAllowUserEntMap

The following subsection associated with the bullet point should also be added:

    Enabling User Entity Mapping

    In HTML, entity mapping replaces characters of special significance with printable representations of those characters. Entity mapping is enabled by default, preventing the use of user defined HTML in iSQL*Plus output. The entity mapping parameter controls whether an iSQL*Plus Server permits users to change the entity mapping setting.

    You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the iSQLPlusAllowUserEntMap value. The syntax of the line to change in the configuration file is: 

    FastCgiServer ... -initial-env iSQLPlusAllowUserEntMap=all|none

    Where the parameter is set to none, or if it does not exist or has an invalid value, the use of SET MARKUP HTML ENTMAP and COLUMN ENTMAP will generate an error. If the MARKUP ENTMAP radio button on the System Variables screen is changed to Off, the value is ignored and reverts to On. The default value for iSQLPlusAllowUserEntMap is none.

    Where the parameter is set to all, users can execute SET MARKUP HTML ENTMAP and COLUMN ENTMAP commands to change the status of entity mapping for the iSQL*Plus session or report column. This enables custom HTML to be included in iSQL*Plus report output.

8.2.2 Chapter 4, Starting SQL*Plus

In Login Username and Password, the following text is incorrect:

    Default logins are created and displayed in messages during Oracle9i installation. The default login username/password combinations created are:

    • SYS/CHANGE_ON_INSTALL

    • SYSTEM/MANAGER

    Default passwords and your database account password should be changed as soon as possible. See "Changing your Password" following. For further information about the default logins, see the Oracle9i Database Administrator's Guide.

It should read:

    Default logins are created and you are prompted for associated passwords during Oracle9i installation. The default login usernames created are:

    • SYS

    • SYSTEM

    See "Changing your Password" following. For further information about the default logins, see the Oracle9i Database Administrator's Guide.

Oracle, Oracle9i, iSQL*Plus and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners

Copyright © 1996, 2002 Oracle Corporation.

All Rights Reserved.

<< Back
E-mail this page
Printer View Printer View
Oracle Is The Information Company About Oracle | Oracle RSS Feeds | Careers | Contact Us | Site Maps | Legal Notices | Terms of Use | Privacy