Kbase 8202: release notes for Sun 4 6.2A Commercial Release
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
release notes for Sun 4 6.2A Commercial Release
900529-SLK01
ADDITIONAL NOTES FOR THIS RELEASE
PLATFORM: Sun 4 os 4
MEDIA TYPE: Cartridge Tape
SOFTWARE RELEASE: 6.2A
EXTRACT COMMAND: cpio -iudcvBm </dev/rst0
INSTALL COMMAND: ./proinstall
MACHINE NOTES:
OPERATING SYSTEM NOTES:
TERMINAL NOTES:
SOFTWARE NOTES:
o This release was ported with ORACLE Version 6.
o This release supports Embedded SQL (HLI) for C.
o Online Backups:
--------------
The use of the -o (overlap factor) is not supported in this
release; you must restore the incremental backups exactly the
same way as you did when you backed them up or you will have
problems. For example,
proshut demo -C online /dev/rst8
proshut demo -C online /dev/rst8 incremental -o 2
After restoring the full backup, if you skip any of the
incrementals, you receive an error message indicating that
the tapes are out of sequence and the restore fails.
Workaround: Make sure all backups are restored in exact order.
o HLI (Embedded SQL for C)
---
A C program that has a combination of CREATE TABLE and INSERT INTO
TABLE statements may fail when executed in multi-user mode.
For example, the following code, when run in multi-user, produces
the errors:
SYSTEM ERROR: lkpurge: record not locked (430)
** Please save file named core for analysis (439)
EXEC SQL CREATE TABLE players (custnum int);
EXEC SQL INSERT INTO players (custnum)
SELECT cust\-num FROM order;
Workaround: Use two different C programs for your CREATE TABLE
and INSERT INTO TABLE statements.
o Toolkit
-------
In order to use the mkdump and procomp utilities, you must set
the environment variable DLCTK and modify the procomp script
to execute $DLCTK/_procomp. For example:
DLCTK=/usr/dlctk;export DLCTK
and the line that executes _procomp should read:
exec $DLCTK/_procomp -1 "$@"
o Fast Track
----------
If you use the convft utility to convert your database to a
Fast Track database, you must set the PROEXE environment
variable first:
PROEXE=/usr/dlc/_progres;export PROEXE
convft database-name
File-Level Timestamp
--------------------
In the Dictionary's Field Editor, any modifications to a field
(including format, label, help, etc.) defined as character
that is not a component in an index, the timestamp on your file
will change. This will invalidate any precompiled procedures
you currently have that reference
the file. For example, with the following procedure:
FOR EACH customer:
DISPLAY customer.
END.
if you compile and save this procedure to produce a .r:
COMPILE stamp.p save
then go back into the dictionary and change the label on the Address
field in the customer file, and then run stamp.p, you will receive
a message indicating that the dictionary has been modified
since stamp.p was compiled. You must recompile the procedure.
Index Deactivation
------------------
If you are deactivating indexes, do it through the Index Editor.
Deactivating indexes through the Admin menu in the Dictionary will
deactivate the top index.
For example:
In the customer file there are three indexes, Cust-num, State,
and Zip. If you choose to deactivate Zip, it deactivates Cust-num.
ORACLE ldemo
------------
The ldemo script that resides in subdirectory ora in
the directory where you install PROGRESS (e.g., /usr/dlc/ora/ldemo)
will not work with the Query/Runtime or
Runtime product. It makes schema modifications which
these products do not support.
Progress Software Technical Support Note # 8202