Kbase 9177: Release notes for Sequent 6.2A
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Release notes for Sequent 6.2A
900608-SLK01
ADDITIONAL NOTES FOR THIS RELEASE
PLATFORM: Sequent Symmetry
MEDIA TYPE: Cartridge Tape
SOFTWARE RELEASE: 6.2A
EXTRACT COMMAND: att cpio -iudcvBm </dev/rts0
INSTALL COMMAND: att ./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 executing in multi-user
mode. For example, when you run the following code in
multi-user, it 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, to set the environment
variable, you would enter:
DLCTK=/usr/dlctk;export DLCTK
and to execute _procomp, the line 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. Enter the following:
PROEXE=/usr/dlc/_progres;export PROEXE
convft database-name
o ORACLE GATEWAY
--------------
If you are running PROGRESS with the Oracle Gateway, i.e.,
$DLCORA/_progres, as a self-serving client and connect to an
Oracle database you need to append the username with '@f:'.
This prevents possible shared memory corruption from occuring.
Example: "$MBPRO odemo -db oraodemo -1 -dt ORACLE -ld oraodemo
-U odemo -P odemo"
would be replaced by:
"$MBPRO odemo -db oraodemo -1 -dt ORACLE -ld oraodemo
-U odemo@f: -P odemo"
Semaphores: Whenever you run PROGRESS with the @f: protocol,
Oracle leaves behind a semaphore with root permissions. You
will have to remove the semaphore with ipcrm when you leave
PROGRESS.
o Index Deactivation
------------------
If you are deactivating indexes, you should do it through the
Index Editor in the Modify-Schema menu. Deactivating indexes
through the Admin menu in the Dictionary will deactivate the
first 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.
o SHARED MEMORY
-------------
In Version 6 of PROGRESS, we use the Sequent System V shared
memory implementation. Therefore, both the /tmp/SysVshmem and
/usr/tmp/SysVshmem directories must exist. They must be
created as root with read, write, execute permissions for the
owner,
group, and other.
o File-Level Timestamp
--------------------
In the Dictionary's Field Editor, if you make 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 try to 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.
o 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 since
it makes schema modifications which these products do not
support.
o PROBUILD
--------
The second option on PROBUILD's product list (RUN-TIME PROGRESS)
does not include a compiler.
If you choose this option, you cannot build an executable that
includes the ORACLE Gateway. When you run the load script, it
fails with the following messages:
Undefined:
_smtrop
_smtrhs
_smegen
_smprhsc
script-name: Failed to load rt.
where script-name is the name of the script you tried to run.
To include the ORACLE Gateway in your executable, use the first
option on PROBUILD's product list (PROGRESS 4GL).
o Extended File Descriptor Tables
-------------------------------
Sequent users running a PROGRESS server that requires many file
descriptors may receive the following error message:
SYSTEM ERROR: unable to open or create (file #),
error 24 (354)
This message occurs when the PROGRESS server requests more file
descriptors than the operating system makes available. To solve
the problem, you need to:
o Set the MAXNOFILE and NOFILEEXT variables in the kernel
configuration file (param.c).
o Regenerate the kernel.
o Set the PROGRESS File Descriptor startup parameter (-Mv).
See the next section for details.
Set the MAXNOFILE and NOFILEEXT Variables
-----------------------------------------
The MAXNOFILE variable specifies the maximum number of open
files for a specific number of processes. The NOFILEEXT
variable specifies the number of processes that can access
the maximum number of file descriptors.
The default number of file descriptors available to a process on
Sequent machine is 20. However, a PROGRESS server needs at least
30 file descriptors to run. Therefore, the defualt value for the
MAXNOFILE variable is set to a minimum of 30 so your system can
run PROGRESS. But if your PROGRESS server needs more than 30
file descriptors, you need to change the MAXNOFILE value.
For example, if you need 40 more file descriptors than the
default of 30, set the MAXNOFILE to 70 (30 default + 40
additional file descriptors).
You then need to set the NOFILEEXT variable to determine the
number of processes that can access the maximum number of file
descriptors. Since each server needs 2 processes, you need to
consider the number of servers that you want to run with the
MAXNOFILE value. For example, if you have 3 servers that need
to run with 70 file descriptors, set the NOFILEEXT variable at
6 (2 processes x 3 servers).
You may need to adjust the following variables within the
kernel for the increased user activity: maxusers, NPROC,
and MAXUPRC.
Regenerate the Kernel
---------------------
Once you set the variables, regenerate the kernel. For details
on how to regenerate the kernel, see the "Reconfiguring the
DYNIX Kernel" section in the Sequent DYNIX System
Administration manual.
Set the PROGRESS File Descriptor Startup Parameter
--------------------------------------------------
After you set the variables and regenerate the kernel, you
must use the File Descriptor (-Mv) startup parameter the next
time you use PROGRESS so the server can request the additional
number of file descriptors.
For example, if you need 40 additional file descriptors when
starting a PROGRESS server with database mydb, enter:
: proserve mydb -Mv 40
NOTE: The system cannot provide file descriptors beyond the
number set for the MAXNOFILE variable in the kernel.
Therefore, the -Mv startup parameter number added to
the previously described default value of 30 should
total a number that is less than or equal to the number
set for the MAXNOFILE variable. For example, if the
MAXNOFILE variable equals 70, the File Descriptor
startup parameter should be 40 or less (40 + 30 = 70).
o PROGRESS UTILITIES (_dbutil)
------------------------------
If you run out of file descriptors while using _dbutil (i.e.,
executing procopy probkup prorest prostrct), PROGRESS allows
you to ask for more file descriptors with the -Mv option. The
option normally available with the server and client modules
is now also available with _dbutil, with the restriction that
the -Mv option should be the FIRST argument after _dbutil. It
cannot be used with the scripts, such as procopy and probkup.
Example:
_dbutil -Mv 30 procopy mydemo mymvdemo
Progress Software Technical Support Note # 9177