Designer/2000 Release Notes

Release 2.1.1 - Production

August 1998
Z23509-02

This document contains important information on installing and operating Release 2.1.1 of Designer/2000 for
Windows 95/NT. This information supersedes any similar information in the Designer/2000 Installation Guide and
the Designer/2000 online documentation.

This release comprises two CD-ROMs:

■ Designer/2000 Release 2.1.1

■ CASE Dictionary 5.1 Upgrade

The product package also contains a further CD-ROM:

■ Designer/2000 Object Extensions (Object Database Designer) Release 2.1.1

This is for users who wish to use the object-relational extensions provided by Object Database Designer. See
"Designer/2000 and Object Database Designer" below, and the separate Installation Guide and Release Notes for
Object Database Designer.

How to Install This Release

Full instructions for installing Designer/2000 Release 2.1.1 are given in the Designer/2000 Installation Guide
supplied with this release. An HTML version of this guide is provided on the Designer/2000 Release 2.1.1 CD.
To view this guide online, insert the CD into your CD-ROM drive and point your browser to the file named:
d:\STARTHERE.HTM
where d: is the identifier of the CD-ROM drive. Alternatively, if you have associated a Web browser with .HTM
files, locate this filename in Windows Explorer or File Manager and double-click it.

Before following the instructions in the Designer/2000 Installation Guide, please read the rest of these Release Notes.

In the event of minor discrepancies between the online and printed versions of the Designer/2000 Installation
Guide, the printed manual is the definitive version.

Z23509-02 Page 1
Product Name Change - Oracle Designer
In a future release, the product name will change from Designer/2000 to Oracle Designer. Some collateral
information already uses the new name.

New Features
Release 2.1.1 of Designer/2000 is a maintenance release, intended to fix important bugs and maintain product
stability. There are no features in this release that are new since Release 2.1.

For information on features new since Release 1.3.2, see the "What’s New" topic in the Help menu on the main
Designer/2000 window.

Designer/2000 and Object Database Designer

If you intend Designer/2000 and Designer/2000 Object Extensions (Object Database Designer) to co-exist on the
same client, we recommend that you install the main Designer/2000 product first, followed by Object Database
Designer.

Oracle7 and Oracle8 Information

Oracle7 and Oracle8 Certification
Designer/2000 Release 2.1.1 has been certified against Oracle8 Server, version 8.0.4, as well as Oracle8 Personal
Edition, version 8.0.4.

Designer/2000 Release 2.1.1 has been certified against Oracle7 Server, version 7.3.4, as well as Personal Oracle7,
version 7.3.4.

All of the above configurations have been certified under Windows NT 4.0, Windows 95 and Windows 98.

Upgrading an Oracle7 Repository to Oracle8

If your Repository is currently in an Oracle7 database (version 7.3.4) that you are upgrading to Oracle8, you
must recompile all packages after upgrading the database but before upgrading Designer/2000 to Release 2.1.1.
The procedure is as follows:

1. Upgrade the database from version 7.3.4 to version 8.0.4 or above.

2. Start your current (pre-2.1.1) version of Designer/2000.

3. In the Repository Administration Utility, click the Recreate button, then select Packages and click Start.

(Note: This operation can take a long time, even for a small Repository.)

Page 2 Z23509-02
 4. When you see the message "Operation Complete", click OK.

5. Close the Repository Administration Utility and Designer/2000.

6. Continue from "Upgrading from a Previous Release of Designer/2000" below.

Upgrading from a Previous Release of Designer/2000

The following table shows what you need to do in each case if you are upgrading from an earlier version of
Designer/2000 (or from its predecessor, CASE Dictionary).

Designer/2000 release Action at Client Action at Server

you are upgrading from

Don’t know/ - Determine the Repository version number and

not sure
2.1 Install client-side software on top of the
previous release, updating any out-of-date
products (see Chapter 1 of Designer/2000
Installation Guide)
1.x Deinstall 1.x client-side software, then install
2.1.1 client-side software (see Chapter 1 of
Designer/2000 Installation Guide)
CASE Dictionary 5.1 See CASE Dictionary to Designer/2000
Migration Guide - procedure involves
deinstalling client-side software and
installing 1.3.2 client-side software
patch level (see page 4), then follow "Action at
Client" and "Action at Server" for correct release
If the patch level is less than 077 (CI0217.077),
upgrade the Repository (see Chapter 2 of
Designer/2000 Installation Guide) to patch the API.
Manually perform a full reconcile (see "Additional
Instructions" below).
Upgrade the Repository (see Chapter 2 of
Designer/2000 Installation Guide) to upgrade the API
and instance data.
Migrate the Repository to 1.3.2 (see CASE
Dictionary to Designer/2000 Migration Guide), then
proceed as for migration from 1.x

Additional Instructions
■ After a server side upgrade from Release 2.1 to 2.1.1, manually perform a full reconcile: in the Repository
Administration Utility window, click the Recreate button, click Full Reconcile and then click Start.

Failure to do so may result in errors when using various tools and generators. For example, an error
message (RME-02124: Failed to execute SQL statement:...) may reference a missing object named
CDI_NLS_DEFAULT_PREFS, as reported in bug 707490.

■ If you install Release 2.1.1 on a machine that has a Release 2.1 seeded repository on it, a message will
appear at the end of the 2.1.1 client-side installation process informing you that the seeded repository
can be updated. Doing so will result in the loss of all data in the repository, as it is overwritten by the
new pre-configured data.

Z23509-02 Page 3
 ■ If you are using Developer/2000 Forms and have installed patch "DEV 2.1 24 JUN PATCH" for that
product, you must also install Designer/2000 patch "pa705539". Patch "pa705539" is available in the
PATCHES directory of the Designer/2000 Release 2.1.1 CD. The patch has been made necessary by
changes to the Developer/2000 Forms API and enables Designer/2000 Form Generator to perform
correctly. Installation instructions are given in the READ.ME file in the "pa705539" directory (note that
the Oracle_home directory should be d:\ORANT or d:\ORAWIN95).

■ After upgrading a user-extended Repository from Release 1.3.2, you need to resubmit the DDL for each
user-extended object and then perform a reconcile operation.

To do so, start the Repository Administration Utility, click "Maintain User Extensions" and locate User
Defined Elements (under ELEMENT TYPES). For each user-defined element, select the element, click
the Submit DDL button and click OK. Repeat the process for User Defined Associations and User
Defined Text Types. When you have finished, return to the Repository Administration Utility window,
click "Recreate", select Full Reconcile and click Start.

Determining the Repository Version Number and Patch Level

The current version number of the Repository helps to determine which release of Designer/2000 you have installed.

To find the Repository version number:

1. Open a SQL*Plus window and connect to the database as the Repository owner.

2. Enter the following SQL statement:

select * from cdi_dictionary_version;
3. Note the version number shown.

The Repository version number corresponds to the Designer/2000 release number as follows (only
Production releases are shown):

Repository Designer/2000
Version Number Release Number
6.0.6.0.0 1.0
6.0.7.0.0 1.1/1.1A
6.0.8.0.0 1.2/1.2A
6.0.9.0.0 1.3/1.3.2
7.0.3.0.0 2.1

If the Repository version number is 7.0.3.0.0, then you also need to find the Repository patch level (see
below) to determine whether a Repository upgrade is necessary.

If the version information that you obtain from step 2, above, is "CASE Dictionary (TM) : Version 5.1.x.x
- Production", you have a CASE Dictionary 5.1 Repository.

Page 4 Z23509-02
To find the Repository patch level:
1. Enter the following SQL statement:
select * from rm$patches order by patch_name;
2. From the last line displayed, note the last three digits following the decimal point (period) under
PATCH_NAME.

If the patch level is less than 077 (CI0217.077), you will need to upgrade the Repository.

SQL*Net, SQL*Plus and the Import/Export Utilities

All Designer/2000 tools are linked with Oracle7 libraries and use SQL*Net V2.3 to connect to the Oracle database
server, which can run either Oracle7 or Oracle8.

If a client machine has a local Oracle8 database, Designer/2000 uses SQL*Net to convert between SQL*Net V2.3
and Net8 protocols, so the client machine must be running a Net8 listener (see the Designer/2000 Installation Guide
and your Oracle8 Server documentation for more details).

If you are connecting to a remote database, Designer/2000 uses SQL*Net V2.3 to establish the remote connection.
Note that SQL*Net V2.3 uses the TNSNAMES.ORA file in the Oracle_home\NETWORK\ADMIN directory (or in
the directory indicated by the TNS_ADMIN registry variable) to resolve alias names when establishing a
connection.

Designer/2000 is configured by default to use SQL*Plus 3.3 and Import/Export 7.3. This configuration is
designed to work against an Oracle7 database, although you can use it against an Oracle8 database. In either case
you will need to have run the appropriate CATEXP script as described in Chapter 2 of the Designer/2000
Installation Guide.

For an Oracle8 database, you can choose to use version 8.0 of SQL*Plus and Import/Export when calling these
utilities from within Designer/2000. You can choose this configuration either during a client-side packaged
installation (from the Packaged Installation Settings dialog box, check Show Advanced Options and click OK to
see the current setting, which you can change). Alternatively you can choose "Use Oracle8 Tools" from the
Designer 2000 R2.1.1 option under Programs on the Start menu. Again, you will need to run the appropriate
CATEXP script as described in the Designer/2000 Installation Guide. Note that the version 8.0 utilities are linked
with the Net8 libraries and use the TNSNAMES.ORA file in the Oracle_home\NET80\ADMIN directory (or in
the directory indicated by the TNS_ADMIN registry variable) to resolve alias names.

The "Use Oracle8 Tools" and "Use Oracle7 Tools" menu options enable you to switch between the two sets of
tools if desired, always remembering to run the appropriate CATEXP script after each change.

Z23509-02 Page 5
CD-ROM Contents (Designer/2000 Release 2.1.1)
Designer/2000 Release 2.1.1 has been verified against all of its dependent products and its appropriate versions.
It is therefore important that the products on the enclosed CD-ROM are used. If you have a different version of a
product already installed on your machine, you must replace it with the version on the CD-ROM. The version
number of each product can be found in the following list:

Product Correct Version Number

Adobe Acrobat Reader 3.0 3.0
Assistant Common Files 1.0.1.0.0
Designer/2000 (Release 2.1.1) 7.0.20.7.0
Designer/2000 Common Workbench 7.0.20.5.0
Designer/2000 Front Panel 7.0.20.5.0
Designer/2000 Generators’ Parent (Release 2.1.1) 7.0.20.7.0
Designer/2000 Form Generator 5.0.20.11.0
Designer/2000 Library Generator 2.0.20.5.0
Designer/2000 MS Help Generator 2.0.20.5.0
Designer/2000 Report Generator 3.0.20.6.0
Designer/2000 Server Generator 7.0.20.5.0
Designer/2000 Visual Basic Generator 2.0.20.5.0
Designer/2000 WebServer Generator 2.0.20.6.0
Designer/2000 Process Modeller 2.0.20.5.0
Designer/2000 Repository Administration Utility 2.0.20.5.0
Designer/2000 Repository Administrator 2.0.20.5.0
Designer/2000 Repository Reports 2.0.20.6.0
Designer/2000 Required Files 7.0.20.5.0
Designer/2000 Systems Designer 2.0.20.5.0
Designer/2000 Design Editor 2.0.20.5.0
Designer/2000 Design Editor Common Files 2.0.20.5.0
Designer/2000 Systems Modeller 3.0.20.7.0
Designer/2000 Transformers 2.0.20.6.0
Designer/2000 Tutorial Support Files 7.0.20.5.0
Designer/2000 & ODD Seeded Repository 7.0.3.77.0
Designer/2000 Broadcast Server 1.0.20.5.0
Designer/2000 Online Documentation 7.0.20.5.0
Designer/2000 Tutorial Documentation 7.0.20.5.0
Designer Online Help Product 7.0.20.5.0
Common Designer/2000 Help Files
7.0.20.5.0
Designer/2000 Help Files
7.0.20.5.0
Developer/2000 - Graphics 3.0.3.10.0
Graphics Chart Wizard 3.0.3.7.0
Graphics Runtime 3.0.3.10.0
Developer/2000 - Reports 3.0.5.8.0
Reports Runtime 3.0.5.8.0
GUI Common Files 2.5.6.25.0
Information Navigator 1.0.4.0.0
INTERSOLV DataDirect Drivers* 2.12.0.1

Page 6 Z23509-02
 Product Correct Version Number
Java(TM) Runtime Environment 1.1.1.0.0
Oracle Administrator Toolbar 1.5.0.0.0
Oracle Call Interface 8.0.4.0.0
Oracle Data Manager 7.3.2.2.0
Oracle Enterprise Manager 1.5.0.0.0
Oracle Enterprise Manager SDK 1.5.0.0.0
Oracle Installer 3.3.0.1.3
Oracle Net8 Products 8.0.4.0.0
Oracle Net8 Assistant 8.0.4.0.3
Oracle Net8 Client 8.0.4.0.3
Oracle Protocol Adapters 8.0.4.0.0
Oracle LU6.2 Protocol Adapter 8.0.4.0.0
Oracle Named Pipes Protocol Adapter 8.0.4.0.0
Oracle SPX Protocol Adapter 8.0.4.0.0
Oracle TCP/IP Protocol Adapter 8.0.4.0.2c
Oracle OCX Pack 1.3.0.4.0
Oracle ODBC (16 Bit) Driver for Rdb for NT** 2.10.12.0.0
Oracle ODBC (32 Bit) Driver for Rdb for NT** 2.10.13.0.0
Oracle7 Utilities 7.3.4.0.0
Oracle8 Utilities 8.0.4.0.0
Required Support Files 7.3.4.0.0
Required Support Files 8.0.4.0.0
SQL*Net V2.3 Products
SQL*Net Client 2.3.4.0.0
SQL*Net Protocol Adapters
Oracle DECnet Protocol Adapter 2.3.4.0.0
Oracle LU6.2 Protocol Adapter 2.3.4.0.0
Oracle Named Pipes Protocol Adapter 2.3.4.0.0
Oracle SPX Protocol Adapter 2.3.4.0.0
Oracle TCP/IP Protocol Adapter 2.3.4.0.0
SQL*Plus 3.3.4.0.0
SQL*Plus 8.0.4.0.0
System Support Files 2.1.0.0.0
Tools Utilities 3.0.3.11.0D

* The INTERSOLV DataDirect drivers are provided for use with Server Generator, to generate to or capture
server designs from Oracle7 and ASCII files, as well as from non-Oracle database and other products (DB/2,
DB/2 Workbench, Rdb 6 and 7, SQL Server and Sybase).

** These drivers allow ODBC applications to access Oracle Rdb databases running under Windows NT.

You can install the INTERSOLV and ODBC drivers using the custom install mode of the Oracle Installer.

Z23509-02 Page 7
Directories on the CD
At the root level of the CD are the following directories:

\DOC
\EXTRAS
\INSTALLR
\PRODINFO
\PRODUCTS
\WIN32
\PATCHES

The \DOC directory

This directory has a number of subdirectories that contain documentation about various aspects of
Designer/2000. (Note: The easiest way to access this documentation is to point your browser to the file named
STARTHERE.HTM in the root directory of the CD-ROM.)
The various subdirectories are:
■ CHELP70 contains files relating to the installation of online documentation.
■ CMNHLP70 contains those online help files that are common to both Designer/2000 and Object
Database Designer.
■ CTUT70 contains the Designer/2000 Tutorial files.
■ DESHLP70 contains online help files that are exclusive to Designer/2000.
■ DOC contains a number of subdirectories (see below).
■ ODDHLP10 contains online help files that are exclusive to Object Database Designer.
The various subdirectories of \DOC\DOC are:
■ API contains an HTML version of the functional specifications for the Designer/2000 Application
Programmatic Interface.
■ INSGDE contains an HTML version of the Designer/2000 Installation Guide - see also "How to Install
This Release" above.
■ MODEL contains a complete specification of the Designer/2000 Repository model, in HTML format.
■ PRODOVER contains an HTML version of the Designer/2000 Product Overview.
■ REF contains a sample Windows Registry file for reference purposes (the Installer will automatically
update the Registry). The file ORACLE.REG contains entries for installed Oracle products. This file
contains a dump of the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE subkey from the Registry
Editor. If you need the contents of this file (for example, if your Registry becomes corrupted), merge it
manually, as installing this file will destroy any existing entries used by other products. Note that a
full installation will also add entries for registered OCXs. These can be installed by double-clicking on
the .OCX files in Oracle_home\BIN.

Page 8 Z23509-02
The \EXTRAS directory
In \EXTRAS you will find the following subdirectories:

■ ACROBAT - contains the Adobe Acrobat Reader executable, AR32E30.EXE. This reader is required for
viewing report files output in .PDF format. If you do not have Adobe Acrobat already installed on your
machine, you can install it using this executable.

■ AUTORUN - contains files specific to this CD’s use of Windows 95 AutoPlay.

The \INSTALLR directory

This directory has subdirectories relating to the Oracle Installer:

■ INSTALL contains version 3.3 of the Oracle Installer and its associated files. This uses an extended
version of the NT.PRD or WIN95.PRD product listing file. Once you have installed this version of
Oracle Installer, older versions will not be able to read the list of installed products. Installing any
products from the Designer/2000 CD will install version 3.3 of the Oracle Installer.

■ INSTALL322 contains version 3.2.2 of the Oracle Installer and its associated files, for those users who
need access to an earlier version of the Installer. Note that the use of this version to install products
from the Designer/2000 CD is not certified; in particular, some of the Net8 components will not be
installed as they require features found in version 3.3 of the Installer.

■ SHARADM and SHARAGT contain Oracle Client Software Manager (OCSM) scripts to support a client
shared installation. Note that Designer/2000 Release 2.1.1 is not initially certified for this method of
installation, as Oracle Installer version 3.3 does not support this feature.

The \PRODINFO directory

This contains copies of the PRODINFO.ORA files for the various CDs included with this product.

The \PRODUCTS directory

This contains the Designer/2000 products to be installed.

The \WIN32 directory

This contains the non-Designer/2000 Oracle products that are required for Designer/2000 to be installed and
run.

The \PATCHES directory

This contains any patches to the software that you may need to install.

Z23509-02 Page 9
Developer/2000 Products
Designer/2000 Release 2.1.1 is compatible with Developer/2000 Release 2.1. If you have any earlier versions of
Developer/2000 products installed, de-install these before proceeding.

The suite of products that make up Designer/2000 is dependent on some of the products from Developer/2000
(Forms, Reports, etc.), the Oracle Server (Oracle8 and Oracle7 Utilities), and SQL*Net (V2 client and various
Oracle protocol adapters). Some Developer/2000 products, and all of the other products, are included on the
Designer/2000 CD and are installed where required as dependent products when you install Designer/2000.

The only Developer/2000 Release 2.1 products included on the Designer/2000 CD are Reports Runtime and its
dependent products. Any further Developer/2000 products that you may need must be installed from your
Developer/2000 Release 2.1 CD. In order to use all the features of Designer/2000 Form Generator or Library
Generator, you will need Developer/2000 Form Builder. For Designer/2000 Report Generator, you will need
Developer/2000 Report Builder.

Note, however, that the Developer/2000 Release 2.1 CD uses an earlier version (3.2) of Oracle Installer than the
one used by Designer/2000 Release 2.1.1, which uses version 3.3. This earlier version cannot read information
written by version 3.3. While this should not cause problems, we recommend that you install any required
products from the Developer/2000 CD before you install Designer/2000. Alternatively, use the version 3.3
Installer to install the Developer/2000 products.

A patch to Developer/2000 was issued that included a later version of Developer/2000 - Forms than the one
against which Designer/2000 Form Generator was built. If you apply this patch to your Developer/2000
software, you should then apply a patch to Designer/2000 Release 2.1.1. You can find the Designer/2000 patch
in the \PATCHES directory of the Designer/2000 CD. See "Additional Instructions" on page 3 for information on
how to apply this patch.

Page 10 Z23509-02
CD-ROM Contents (CASE Dictionary 5.1 Upgrade)
The CASE Dictionary 5.1 Upgrade CD-ROM contains products from the Designer/2000 Release 1.3.2 CD that
enable you to upgrade a Repository from CASE Dictionary 5.1 to Designer/2000 Release 1.3.2. You can then
follow the standard upgrade path from Release 1.3.2 to Release 2.1.1. For complete instructions, see the CASE
Dictionary to Designer/2000 Migration Guide supplied with this release.

The contents of the CD-ROM are:

Product Correct Version

Number
Adobe Acrobat Reader - Beta 3.0B13
GUI Common Files 2.3.6.9.0
Oracle Data Manager 7.3.2.2.0
Oracle Designer/2000 (Release 1.3.2) 6.0.10.1.0
Designer/2000 Help 6.0.10.0.0
Designer/2000 Repository Administration Utilities 1.0.10.0.0
Designer/2000 Repository Administrator 1.0.10.0.0
Designer/2000 Required Files 6.0.10.0.0
Oracle Installer 3.1.4.1.3
Oracle7 Utilities 7.3.2.2.0
Required Support Files 7.3.2.2.0
SQL*Net Client 2.3.2.1.6A
SQL*Plus 3.3.2.0.2
System Support Files 2.0.1.3.2
Tools Utilities 2.1.10.7.0

Multiple Oracle Homes

Oracle Installer version 3.3 supports a new feature called Multiple Oracle Homes, which replaces an earlier
feature called Switch Homes. However, the Designer/2000, SQL*Net V2.3 and Oracle7 Utilities products on the
Designer/2000 CD do not support this new feature, so you cannot install Designer/2000 products in this way.

Z23509-02 Page 11
Installation and Deinstallation (Client-Side)
For full instructions on client-side installation and deinstallation, see the Designer/2000 Installation Guide.

The following client-side installation options have been tested and are known to work satisfactorily:

■ Install all products (custom install)

■ Install all products (packaged install)

Other options should work but have not been specifically tested.

Installing Products in Non-English Environments

When you run Installer from the Designer/2000 CD you are given the choice of many different languages to
choose from for your client side installation. Not all products that form part of the installation have been
translated to that language. The English (American) version of those products that have not been translated will
be installed. Where translated products have been installed and are being run, the user interface and messages
displayed to the user will be in the chosen language. Where English versions of the products have been installed
such UI and messages will be in English. Note that the installation itself will be in English even if it is installing
products translated into another language.

Pre-Installation Information
1. It is important not to install Oracle products intended for one operating system into the Oracle Home
where products intended for another operating system have been installed. Failure to observe this will
result in your installed products being unusable. Keep separate Oracle Home directories for Windows
NT and Windows 95 products. It is recommended that you always use the default Oracle Home
suggested by the Oracle Installer. It is also important to run a version of Designer/2000 under the
operating system for which it is intended.

2. Make sure that no Oracle products are running whilst you are using the Oracle Installer. You may find
that these products have locked certain files that the Installer is trying to upgrade. In particular make
sure that no other copy of the Oracle Installer is running and that you have closed the Oracle
Administrator Toolbar, and shut down any local Oracle Server and SQL*Net Listeners.

3. If installing under Windows NT, be sure to log in as the administrator for the local workstation and not
as the network administrator or any other user.

Logging in as the network administrator and installing Designer/2000 will add the Designer/2000
folders to the network administrator’s profile. If the network administrator then logs in at other
workstations on the network, the Designer/2000 folders will appear even though Designer/2000 may
not be available on those workstations.

Installation when logged in as a normal user will fail because special privileges are required to install
some components.

Page 12 Z23509-02
Installing Designer/2000 with Personal Oracle7 under Windows NT
If you have installed early versions of Personal Oracle7, you may find that it has installed an old version of the files
MFC30.DLL and MSVCRT.DLL into the ORANT\BIN directory. These files should have been installed into the Windows
SYSTEM directory. If you have installed Personal Oracle7 and not installed Designer/2000, and if these files exist in the
ORANT\BIN directory, move them to the Windows SYSTEM directory. To do so, issue commands such as the following:
move \orant\bin\mfc30.dll \Windows_dir\system\*.*
move \orant\bin\msvcrt.dll \Windows_dir\system\*.*
where Windows_dir is the directory where Windows NT is installed (for example, WINNT).

If the files exist in both places, use Explorer or File Manager to check the version numbers, delete the earlier
versions, and move the later versions of the files to the Windows SYSTEM directory.

If you install Designer/2000 after installing Personal Oracle7, these files will be removed for you.

If you install Personal Oracle7 after Designer/2000, delete the files ORANT\BIN\MFC30.DLL and
ORANT\BIN\MSVCRT.DLL. Failure to remove the files from the ORANT\BIN directory may result in the
following error message when you try to invoke Designer/2000:
Invalid ordinal in filename
where filename is the name of the .DLL file.

During Installation
If the installation hangs or fails completely whilst looking in the Registry for the file association for .TXT or
.HTM files (the progress text displays a message to this effect whilst it is happening), you will need to edit your
Registry by hand. Look in HKEY_CLASSES_ROOT for .txt (or .htm) and look at the file type - probably txtfile (or
NetscapeMarkup). Still under HKEY_CLASSES_ROOT, find the entry for txtfile (or NetscapeMarkup) and
expand the tree to display "txtfile → shell → open → command" (or "NetscapeMarkup → shell → edit →
command"). Select the "command" node to display the value. Rationalise this entry by removing embedded
quote characters, e.g. "notepad %1" and not "notepad" %1. Also make sure that if the value contains C-style
escape strings that the whole value is enclosed in quotes (edit the value to check this), e.g. "write /n %1" and not
write /n %1. If the installation fails because of this error, upon restarting the installation this section will be
skipped and a default value of "notepad %" used to read and edit .TXT and .HTM files from within
Designer/2000.

The Oracle Installer will try to upgrade the file CTL3D32.DLL in your Windows system directory if the version
of the file on the Designer/2000 CD is newer. If you are running any applications that have this file locked then
you will see an error message stating that the Installer cannot copy the file to your disk. Click the Ignore button
to proceed. Designer/2000 will not encounter problems with your older version of this file.

Z23509-02 Page 13
At clients where a previous version of Designer/2000 was installed, or where you are re-installing a component,
you may see a Windows error message as Oracle Installer tries to remove icons from a desktop folder that was
created as part of the previous version but which no longer exists. The message is of the form:
C:\WINNT\Profiles\All Users\Start Menu\Programs\Designer 2000 Bulletins is not accessible. The
folder was moved or removed.
Click OK to acknowledge this message.

Post-Installation Information
If you have installed earlier releases of Designer/2000, you may have obsolete products and Start menu entries
that you can now remove. You can also change the layout of the main Designer/2000 window.

Removing obsolete products

The following products are no longer available:

Designer/2000 SQL*Plus Generator

Designer/2000 Graphics Generator
Object Database Designer C++ Generator - MSVC 4.2 Support
Use the Oracle Installer in Custom mode to check whether any versions of these products are still installed, and
if so, remove them.

Removing obsolete Start menu entries

If you have obsolete Oracle entries in your Start menu, you should remove them as they relate to products that
have been upgraded and for which new entries exist. Following are some examples of obsolete entries:

Oracle Designer 2000*

Designer 2000 Bulletins*
Designer 2000 R2.0
Designer 2000 R2.0 Bulletins
Developer 2000 R2.0
Developer 2000 R2.0 Demos
Developer 2000 R2.0 Doc
* at some sites there may be a requirement for Release 1.3.2 and Release 2.1.1 to coexist on the same
client, in which case these two entries should be retained
To remove obsolete entries, proceed as follows.
Under Windows95, click Start and choose Settings → Taskbar → Start Menu Programs → Remove. Select a
folder to delete and click Remove, repeating this step as necessary.

Under Windows NT, ensure that you are logged on as a local administrator. Start Windows Explorer and
expand C: → Winnt → Profiles → All Users → Start Menu → Programs. Select a folder to delete and choose File
→ Delete, repeating this step as necessary.

Page 14 Z23509-02
Changing the layout of the Designer/2000 window
The default layout of the main Designer/2000 window is horizontally oriented. If you prefer, you can change it
to a vertically-oriented layout.

To change to the vertical layout:

1. Exit from Designer/2000 if it is active.

2. In Windows Explorer, double-click the file name VERTICAL.REG in the Oracle_home\DES2_70

directory.

3. Click OK to acknowledge the confirmation message.

4. Restart Designer/2000.

To revert to the horizontal layout, repeat this procedure, substituting HORIZONT.REG for the file name.

Deinstallation
On deinstalling the Designer/2000 products, some Designer/2000 entries will remain in the Windows Registry,
and some System Release Bulletin icons will remain in the Designer 2000 Bulletins folder or program group. This
will have no adverse effect on your system.

Z23509-02 Page 15
General Notes
Current Restrictions
1. Under certain circumstances, when running against an Oracle7 Server using SQL*Net, disconnecting
from the database does not free up DLL usages of SQLTCP.DLL, and the database connection is not
freed immediately. The effect will vary depending on the network configuration in use.

2. Designer/2000 can be run under VGA or SVGA, although SVGA is recommended.

3. We recommend that you run Designer/2000 under 256 colors (Control Panel → Display → Color Palette).

4. We recommend that you set the system font size to Small Fonts (Control Panel → Display → Font Size).

5. It is possible to create instances of elements with names that are SQL or PL/SQL reserved words. Users
should beware of this where these element names are likely to be used in SQL or PL/SQL statements.
Also, if a systems modeling element is created with a name that is a SQL or PL/SQL reserved word, it
may not be possible to transform it into a systems design element.

6. User defined preferences for Designer/2000 are held in the Registry under the key
HKEY_CURRENT_USER\SOFTWARE\ORACLE\..where they can be modified during the running of a
diagrammer (as opposed to only during installation time). In addition, such preferences can be modified
by a user who does not possess administrator privileges. Some preferences are directory search paths
which the diagrammers use to find data files or to save working files and as such may include drive letters
and fully qualified filenames. Please be aware that if you operate in a network environment or in a multi-
drive machine, you should always make sure that any drives that you specify in these preferences are
always mounted and mapped to the same drive letter on all the machines that you use.

This is particularly important in the Process Modeller, as when invoking the preferences dialog box for
the first time it will automatically fill in some of these preferences with the default values. These values
contain hard coded drive information for the location of the installed Process Modeller multimedia
files. If Process Modeller has been installed onto a networked drive then it may fail when the
multimedia option is invoked, if it cannot find the specified (network) drive.

7. Files created by Form Generator from module specifications have a filename that is the same as the module
short name. If the module short name is greater than 8 characters then the filename will also be greater than 8
characters. Make sure that your target file system supports long filenames if you use module names greater
than 8 characters in length (long filenames are those greater than the 8.3 limit imposed by DOS and the FAT
filing system). This problem will only be encountered if you mount a FAT based file system over the network.
Failure to ensure these requirements are met will result in an application error during generation. Please note
that some examples found in the tutorial have module names longer than 8 characters so ensure that you are
generating to a local drive or a file system that supports long file names.

8. The version of Oracle Installer (3.3) used to install this release of Designer/2000 does not support
installation by Oracle Client Software Manager (OCSM). Thus you cannot use OCSM in order to
manage a distributed network installation. Instead, please read "Installing Designer/2000 on a Local
Area Network" in the Installation Guide.

Page 16 Z23509-02
 9. If you install under Windows 95 you may, on starting a Designer/2000 tool, see a message indicating
that CTL3D32.DLL is the Windows NT version. If you see this message, delete CTL3D32.DLL from
your hard disk and locate the correct version, which can be found on the Designer/2000 CD in the
directory \WIN32\SSF21\CTL3D32.W95. Copy this file to your Windows 95 system directory as
CTL3D32.DLL.

10. If Developer/2000 - Reports is installed and a user deinstalls the component product Reports Runtime,
Designer/2000 Report Generator and Developer/2000 Report Builder will fail with an error stating that
the file R30LIB32.DLL cannot be located in the path.

11. If you install Designer/2000 and subsequently install or reinstall Developer/2000 products, some
Registry entries may be overwritten. This can result in Designer/2000 tools (such as Form Generator)
not being able to load a particular library.

12. In the MS Help Generator, Help Context ID Prefixes are nullified when upgrading to Release 2.1.1 from
a release up to and including Release 1.3.2. To restore them after an upgrade, generate the MS Help file
again, click Save after generation has finished, then regenerate all forms to link in the context IDs.

13. If you use the Find Setup Wizard in Windows Help to customize the search capabilities of the Find tab on
your help system, you may find that when you try to display a topic reported by the Find tab, you see the
error "Help could not read the current help file". In all probability, there is no error with your help file; this is
believed to be a problem with the Windows Help mechanism.

14. Avoid using Release 2.1.1 client-side tools with a Release 2.1 Repository, or vice versa. Ensure that all
clients and the Repository are operating at the same release level.

Design Editor
When you generate or capture objects, Design Editor sometimes proposes changes to the Repository. You can choose
Post Processing Mode to allow you to view, and optionally edit or abandon the changes before they are committed. If
you view the changes and open the Property Palette for an item and subsequently close the Property Palette without
saving the changes, all changes are lost. To avoid this, keep the Property Palette open while you save the changes.

A broadcast mechanism has been introduced to allow users of an application system to be notified of changes to
Repository objects in that application system as soon as those changes are made, even if that change is made by
another user on another machine. You may experience inconsistent behaviour with the mechanism, e.g. if many
transactions are being performed, you may not be informed of changes across tools.
The File → Change Connection menu option does not function correctly. To change the connection it is
necessary to close the Design Editor and restart it with the new connection details.

Z23509-02 Page 17
Tip: Using Modules Based on Views
If you want to reduce network traffic by creating a view for your base table and its lookup tables, create a
module component with a datasource type of VIEW. To do so:

1. Create the module component with the base table usage and lookups you want.

2. Create the TAPI for the tables used by the module on the target database.

3. Set the module components datasource type to VIEW.

4. Generate the MAPI for the module to the target database.

5. Generate the module.

The generator will create a physical view on the target database based on the base/lookup table usages you have
defined. This view will not appear as a view in the Repository.

Note: To create a module based on a view you have defined in the Repository, set the
datasource type to TABLE.

Form Generator and Report Generator (Year 2000 Compliance)

Form Generator and Report Generator generate code to set the date format for built-in, PL/SQL and database
operations. Form Generator uses the PRE-FORM trigger, and Report Generator uses the BEFORE REPORT
trigger to generate this code. The default date format mask is:
YYYY/MM/DD HH24:MI:SS
For more details, see the Design Editor help topic "Generating Year 2000 compliant applications".

Repository Administration Utility

After deleting one or more users from the Repository, the RAU may appear to hang when Reconcile is started.
The RAU is actually busy executing a query. Eventually the Control Status dialog will appear, showing the
progress of the Reconcile operation. The amount of time you have to wait before the dialog is displayed depends
upon the number of users deleted.

For more about restrictions relating to the Repository Administration Utility, refer to the System Release Bulletin
for this utility (see "System Release Bulletins" below).

Page 18 Z23509-02
SQL*Net
Designer/2000 Release 2.1.1 has been designed to work with SQL*Net Version 2.3. This is provided on the
Designer/2000 CD. If you have SQL*Net Version 1.1, Version 2.1 or Version 2.2 installed, please upgrade to
Version 2.3. Failure to do so may result in non-specific errors ORA-65535 or ORA-00001.

When installing SQL*Net, the Installer attempts to determine the network protocols that are installed and select
the appropriate Oracle protocol adapters for installation.

SQL*Plus
Before running the Repository Administration Utility, make sure that there are no SQL*Plus sessions running,
otherwise the Repository Administration Utility will not be able to spawn a new session. This will cause any
operations requiring a SQL*Plus session to hang.

It is possible, via SQL*Plus, for a subordinate user to update the Repository base tables (e.g. SDD_ELEMENTS,
SDD_STRUCTURE_ELEMENTS). At sites where this is undesirable, the DBA should use the product profile
table to prevent SQL*Plus connection for individual users.

OLE Compliance
Designer/2000 diagrammers (except for the Matrix Diagrammer) are OLE container applications. Data from
other OLE server applications (such as bitmap and text editors) can be embedded or linked in Designer/2000
diagrams by use of Edit → Paste New Object or Edit → Insert New Object.

Designer/2000 diagrammers are not full OLE servers, but pictures of the current diagram can be inserted into
OLE container applications. Use:
■ Edit → Copy in the Designer/2000 diagrammer, when there is no current selection.

■ Paste into an OLE container application (e.g. Microsoft Word).

You will not see any Designer/2000 diagrammers listed as OLE objects.

Once pasted, the picture cannot be re-activated inside the container. Any association with the original diagram is
broken.

Cut, copy and paste operations work between different diagrams of the same Designer/2000 diagrammer when
there is at least one item selected.

Users are advised to de-activate embedded OLE objects before saving the diagram. Failure to do so may result in
a corrupt diagram, which cannot be opened.

Z23509-02 Page 19
Additional Information
The following paragraphs provide additional information concerning the location of the System Release
Bulletins and the Designer/2000 schema files, as well as information on changes to error messages.

System Release Bulletins

For more information on current restrictions within Designer/2000, refer to the following online System Release
Bulletins (SRBs), which you can also find in the Designer 2000 R2.1 (or R2.1.1) Bulletins folder:

Application Design Transformer Oracle_home\REPADM20\ADWSRB.TXT

Database Design Transformer
Dataflow Diagrammer
Design Editor
Entity Relationship Diagrammer
Form Generator
Function Hierarchy Diagrammer
Library Generator
Matrix Diagrammer
MS Help Generator
Process Modeller
Report Generator
Repository Administration Utility
Repository Application
Programmatic Interface (API)
Repository Object Navigator
Repository Reports
Server Generator
Table to Entity Retrofit Utility
Visual Basic Generator
WebServer Generator
Oracle_home\REPADM20\DDWSRB.TXT
Oracle_home\SYSMOD30\AWD30.TXT
Oracle_home\SYSDES20\DEREAD.TXT
Oracle_home\SYSMOD30\AWE30.TXT
Oracle_home\CGENF50\OFGREAD.TXT
Oracle_home\SYSMOD30\AWF30.TXT
Oracle_home\CGENL20\OLGREAD.TXT
Oracle_home\REPADM20\AWM30.TXT
Oracle_home\CGENH20\HPGREAD.TXT
Oracle_home\BPMOD20\BPMOD20.TXT
Oracle_home\CGENR30\CRRSRB.TXT
Oracle_home\REPADM20\RAU.TXT
Oracle_home\REPADM20\CDAPI20.TXT
Oracle_home\REPADM20\CKRON20.TXT
Oracle_home\REPADM20\CKRPT.TXT
Oracle_home\CGENS70\OSGREAD.TXT
Oracle_home\REPADM20\T2ESRB.TXT
Oracle_home\CGENV20\VBGREAD.TXT
Oracle_home\CGENW20\WSGREAD.TXT

Note that some SRBs incorrectly specify the location of help files as Oracle_home\CHELP70. The correct location
is Oracle_home\CDOC70\HELP.

Page 20 Z23509-02
Designer/2000 Schema
Two files, each containing the Designer/2000 schema, are provided with this release for your information. The
following files are provided:
Oracle_home\DES2_70\MODEL\MODEL_20.DAT
Oracle_home\DES2_70\MODEL\MODEL_20.DMP
To load the MODEL_20.DAT file, use the Repository Object Navigator to create an empty application system,
then choose Utilities → Load, enter the file name in the "Command file" field and click Load. (But see bug 658816
in "Outstanding Bugs" below.)
Alternatively, to load the MODEL_20.DMP file, open the Repository Object Navigator and select Application →
Restore, enter the file name in the "Import file" field and click Import.

New and Changed Error Messages

The following error messages are new or changed in this release.

CDA-06028 Cannot unshare - Element is referenced from %0!s - %1!s

Cause: An attempt to unshare an element has failed because references to that element within the application
system exist.

Action: Remove references before unsharing.

CDA-06085 Cannot copy: invalid reference to %! : %!. Please change copy rules.
Cause: Could not copy element as the action would result in an invalid reference to another Repository object.

Action: Amend the copy rules to include the element pointed to by the invalid reference.

CDA-06086 Unable to identify type body for Oracle Object Type %0!s
Cause: An attempt was made to transfer an Oracle Object Type but the transfer utility could not identify the
type body applicable to the Oracle Object Type.

Action: Use the Repository Object Navigator to examine the Oracle Object Type and ensure it has a valid type
body. Repeat the transfer operation.

CDA-07000 %0!s is a checked out set. Repeat operation to unlock set.

Cause: An attempt was made to unlock a set which is currently checked out to a working application system.
Unlocking this set will reset the status of the set and all its members from ’CHECKED OUT’ and
’LOCKED’ to ’UNLOCKED’. It will not then be possible to run the checkin operation on this set to
accept the changes from the working application system.

Action: Repeat the operation to override this warning message and successfully UNLOCK the set.

Z23509-02 Page 21
Bug Information
Fixed Bugs
Information on bugs that have been fixed since the last release is given in the System Release Bulletin for the
appropriate tool. See "System Release Bulletins" above.

Outstanding Bugs
Some System Release Bulletins list outstanding bugs and known restrictions with the appropriate tool. In
particular, the following bugs are still outstanding:

714305 USER-DEFINED ACTION ITEM NOT DISPLAYED ON FORM IF HEIGHT IS NOT SPECIFIED
In Form Generator, if a module component has a custom action item that is directly assigned a user-defined
object library source and the height is not set, the corresponding form item (typically a button) is not displayed
on the generated form, as its height is effectively 0.

Workaround: Specify a height of at least 1 for the item before generation.

714285 FORCE DELETE IN TABLE DEFINITION, MODULE DIAGRAMMING CAUSES ERROR

In the Design Editor, when a column is force-deleted in the relational table definition for a table that is used in a
module, an error occurs when this module is displayed.

Workaround: Requery the module, or exit from and restart Design Editor.

713934 NAVIGATION ACTION ITEMS AUTOMATICALLY CREATED ON FORMS CAPTURE

In the Design Editor, it is possible to capture the design of a generated master-detail form that has a navigation
action item to navigate from the master to the detail. If you capture such a form with the Capture Control Blocks
option unchecked, an action item is created in the new module (no action item should be created in this case). If
you capture such a form with the Capture Control Blocks option checked, the action item is correctly captured
but another one is added on Commit.

711648 DERIVATION EXPRESSIONS USING STORED FUNCTIONS IN NON REPOS USER FAIL TO
COMPILE
In Form Generator, if a bound item is based on a column and the column has a derivation expression that calls a
server-side function, but that function is not in the repository user’s schema, then the .FMB file is generated but
fails to compile, giving:
FRM-30400: Formula required for formula item.
This happens even when you specify the correct remote user details in the Form Generator options dialog.

Workarounds:

■ Create synonyms in the repository user’s schema that point to the remote user’s schema objects. If the
remote user is on a different database , you will also need to create links to that database.

Page 22 Z23509-02
 ■ Create the remote user’s schema objects in the repository user’s schema.

■ In Form Builder, open the form that failed to compile and connect to the remote user. Edit the Formula
property of the formula item that failed to compile, and add a space to the end of the expression (or
make any other change that will not impact the content or syntax of the expression). Editing the
formula expression causes Form Builder to re-check the expression against the current database
schema. The form can now be compiled.

710971 ATTRIBUTE USAGE LIST - FULL LIST SCROLLS WITH EXTRA COLUMN
In the Function Hierarchy Diagrammer, if a function uses an entity that has 8 or more attributes, the Attribute
Usages tab of the Edit Function dialog box uses a vertical scroll bar to display all the attributes. If you then use
the horizontal scroll bar at the bottom of the screen to scroll all the way to the right, and subsequently scroll to
the left, the diagrammer terminates.

Workaround: Either avoid scrolling all the way to the right on the Attribute Usages tab, or use the Repository
Object Navigator to create or edit usages of entities with 8 or more attributes.

710910 TOOL PALETTE NOT ACTIVE ON FIRST CREATION OF NEW PROCESS

On creating a new application system, if you then start Process Modeller, create a new process diagram, click the
"Create New Root Process" button on the New Diagram dialog box, enter a short definition and a label and click
OK on the Create Process Step dialog box, you may find that the lower of the two toolbars is inactive.

Workaround: Save the new diagram. The toolbar is then activated.

708890 USER CAN CREATE NEW SAC ELEMENTS IN A SHARED OBJECT VIA ’COPY OBJECT’ UTILITY
In the Repository Object Navigator, it is possible to create new secondary access (SAC) elements within a shared
primary access (PAC) element through the use of the Copy Object utility. This unintended behavior will be
changed in a future release.

706906 GENERATING FORM WITH PRESERVE LAYOUT DUPLICATES LOOKUP ITEMS

In Form Generator, if you generate a form and then regenerate it with Preserve Layout set to Yes, lookup items
can be duplicated on the second generation with identical item names. Other superfluous items such as canvases
and blocks are also generated.

Workaround: Do not use the Preserve Layout option for modules with lookup table usages.

705502 RESTORE OF UPGRADED 132 APPSYS FAILS WITH UNIQUE CONSTRAINT VIOLATED (ORA-1)
In the Repository Object Navigator, if you restore an application system that has been archived from a Release
1.3.2 repository, the application system will be upgraded correctly but the restore may fail with the errors:
RME-02105: Oracle error occurred...
ORA-00001: unique constraint (REPOS.STR_PRIME) violated
Workaround: On the Application - Restore dialog box, select the Force Invalid References check box before
restoring.

Z23509-02 Page 23
704364 JAVASCRIPT ERROR CLICKING NEW BUTTON ON LIST/FORM STYLE DETAIL COMPONENT
In the WebServer Generator, if you generate a master-detail form and the detail Record List is displayed in a
frame, clicking the New button of the Record List frame may give the JavaScript error "document.forms[2] has
no properties".

Workaround: Use the New button on the View Form frame instead.

702264 FPA ANALYSIS LEVEL REPORT (CSDPAANL) REPORT DOES NOT RUN IN BITMAP MODE
In Repository Reports, the value of the Function Label parameter of the FPA Analysis Level (DATA USAGE)
report (filename CDFPAANL) is set to "%" by default. Running this report with the value "%" results in the error
"ORA-01427: single-row subquery returns more than one row" because the report contains fields that should
return only one row.

Workaround: Open a SQL*Plus window, connect as the Repository owner and enter the following SQL
statements to remove the preset default value:
update ck_report_parameter_usages
set rpu_default = ’’
where rpu_rpt_id = 105
and rpu_param_id = 43;

692369 ORACLE7 TRIGGERS HAVE INVALID SYNTAX, IF STATEMENT LEVEL OR HAVE WHEN
CONDITION
Triggers for Oracle 7.x are generated incorrectly whenever the trigger is Statement level, or when it is has a
’When’ condition. (A simple row level trigger with no When condition is generated correctly).

The last line of the trigger heading is followed directly by the first line of the PL/SQL block of the trigger, with
no newline or space. This means that the trigger syntax is invalid and cannot be executed.

Workaround: Before executing the generated files insert a newline after the trigger header for all affected
triggers.

This does not affect generation of triggers to Oracle8 databases, only Oracle7.

683911 GET AN INVALID MEMORY ADDRESS WHEN GENERATING MSHELP FOR MODULE NETWORK
In the Design Editor, an error can occur if you generate a module as MS Help (via Generate → Generate Module As →
Help System) and the module includes a reusable module component. The error occurs only if you open the Design
Editor and generate immediately, without expanding the module or module component node in the Navigator.

Workaround: Expand the node in the Navigator before generating.

Page 24 Z23509-02
673794 DE MUST BE RESTARTED IN ORDER FOR BROADCAST SETTING CHANGES TO TAKE EFFECT
In the Design Editor, after changing the broadcast settings from Desktop Only to Network you must restart the
Design Editor before the changes will take effect.

658816 LOADING MODEL_20.DAT FILE GIVES ERRORS

If you load the MODEL_20.DAT file (see "Designer/2000 schema" above), you will see the Loader error:
CDI-22941 Server raised error
followed by these API errors:
RME-00222: Failed to dispatch operation to Repository
RME-00011: Operation ’ins’ on GENERALISATION_ASSOCIATION has failed
CDA-03501: GENERALISATION ASSOCIATION <40644>: An association already exists
Workaround: Before loading, manually edit the MODEL_20.DAT file and change the sequence number of
"LargeString" and "LargeBinary" to 1, as follows:
M SEQUENCE *896 "8" change to M SEQUENCE *896 "1"
M SEQUENCE *899 "9" change to M SEQUENCE *899 "1"
Alternatively, apply the workaround to the REDO.LOG file and then load the REDO.LOG file into the same
application system.

653380 DOC: GENERATING ’NATIVE DATE FORMAT’ INDEPENDENT FORMS

In the past, a suite of forms could be generated which did not include any format masks for date items. The
forms could then be shipped to different countries (with different native languages). When running the forms, a
user would be able to enter date values into items in the user’s native country format (e.g. 27-12-95, 12-27-95).
This was made possible because the form used the value of the user’s local NLS_DATE_FORMAT variable to
establish what the native format mask is. Following the Year 2000 compliance work, this is no longer possible in
generated forms.

However an alternative and equally suitable mechanism exists. When generating forms, if all data column
usages in a module do not have an explicit format mask specified, the generated date items inherit their format
mask from the object library. When a suite of forms is generated to be shipped to another country, the shipped
object library which accompanies the set of forms can have the inherited source date item format mask changed
to the native format mask of each target country. This enables each target country to use the same generated
forms, but enter dates in different native formats.

652840 DE/ERD/ODD GPFS WHEN ATTEMPTING TO INSERT A NETSCAPE HYPERTEXT DOC IN A

DIAGRAM
There is a known problem inserting a "Netscape Hypertext document" as an OLE object in the Entity
Relationship Diagrammer, Module Diagrammer and Type Modeller. This may cause a program failure.

652188 CAPTURE VB APPLICATION LOGIC SAVES TO NEW LOGIC REPOSITORY AFTER REVERT
There is a known problem in the Design Editor with Capture Visual Basic Application Logic, which saves the
captured logic to the Repository even if you click Revert.

Z23509-02 Page 25
651968 USER SHOULD NOT BE ALLOWED TO CREATE ’MANDATORY’ PROPERTIES FOR STANDARD
ELEMENT
In the Repository Administration Utility, it is possible to create ’mandatory’ user-defined properties for standard
elements. This can affect the functionality of the Designer/2000 transformers and generators.

For example, if a mandatory user-defined property is defined for a table but no default value is specified for it,
running the Database Design Transformer for any entity will result in the API error "Property must NOT be
null".

Similarly, defining additional mandatory user-defined properties for modules can adversely affect the
functioning of the Application Design Transformer.

Currently, the Repository Object Navigator does not check for the presence of a value for a mandatory user-
defined property when you create an element instance. However, if a value is entered for a mandatory user-
defined property, saved and then edited to <NULL>, this does result in the "must not be NULL" error.

Workaround: Avoid creating mandatory user-defined properties for standard elements.

651614 CDI-20584 DIAGRAM FIXUP ID FAILED MESSAGE ON OPENING A RESTORED PROCESS

MODEL
In the Process Modeller, if you open a process diagram that has been archived and restored and which contains
objects that are out of date with the Repository, you see the message:
CDI-20584: Diagram ID Fixup Failed
Please close diagram and call Customer Support.
Workaround: Click OK at the message, then choose Edit → Requery → All. Alternatively, choose File → Save
Diagram As and save the diagram with a new name. The new diagram will now open correctly.

650048 UNRESOLVED JUMPS FROM CONTENTS PAGE IF CONTEXT ID PREFIXES NOT DEFINED
In the MS Help Generator, generating a module network as Help results in unresolved jumps from the Contents
page if the called modules have no Help Context ID Prefixes defined.

Help Context ID Prefixes for modules are optional. If you do not specify them, the Help Generator will
automatically allocate them.

If you generate Help for a module network, a Contents topic is created for the top level module, with jumps to
all the called modules’ help topics. However, if you have not defined Help Context ID Prefixes for these called
modules the jumps do not work. On compilation you get the warning:
Unresolved jump or popup ’0’
and the .RTF file for the top-level module contains jumps to 0.

Workaround: Either define Help Context ID Prefixes for all modules, or generate the module network as Help,
save the changes (the allocated prefixes) and then generate as Help a second time.

Page 26 Z23509-02
641358 ERROR IN CREATING DATAFILE/LOGFILE IF PATH PROPERTY IS SAME FOR BOTH
If you create definitions for data files and log files with the same path name, the operation fails with the error
messages:
RME-00224: Failed to close activity
RME-00222: Failed to dispatch operation to Repository
RME-00011: Operation ’close’ on ACTIVITY has failed
RME-00020: Internal API error - ORA-01422: exact fetch returns more than requested
Workaround: Specify unique path names when defining data files and log files.

585358 DOING SILENT INSTALL OF SQLNET CLIENT IN THE YEAR 2000 -> DR. WATSON.
If, for Year 2000 testing purposes, you set the system date to the year 2000 or beyond, subsequent installation or
deinstallation of Designer/2000 or some of its dependent products may cause Oracle Installer to fail during or
on completion of the operation.

This problem is fixed in a more recent version of Oracle Installer (version 3.3.1.4.30).

508660 DDT WILL NOT START IF APPLICATION NAME HAS AN APOSTROPHE

There is a known problem with the Database Design Transformer, which will not function if the application
system name contains an apostrophe.

Workaround: Rename application systems whose names contain apostrophes.

Z23509-02 Page 27
Page 28 Z23509-02