Kbase P13829: Error 444 occurs during a VERIFY with Oracle DataServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/02/2003 |
|
Status: Unverified
FACT(s) (Environment):
Oracle DataServer
FACT(s) (Environment):
Progress 8.3x
FACT(s) (Environment):
Progress 9.x
FACT(s) (Environment):
Progress 9.1x
SYMPTOM(s):
** Attempt to expand record beyond the maximum allowed size. (444)
Error occurs when verifying table definitions between ORACLE and schema holder
Oracle objects can be pulled into schema holder
CAUSE:
Bug# 20010302-011
CAUSE:
Currently the verify utility allows the user to compare schema the foreign datatasource to definitions contained in the schema holder. If there are too many discrepancies, the procedure will end with an error stating that the 32K limit for assigning to a variable or record has been exceeded.
The issue is caused when the table (being verified) has such a large "retainable" information that the variable value is too large, thus goes beyond the Progress 32K limit.
FIX:
This issue has been fixed in Progress 8.3DPATCH, 8.3E, 9.1CPATCH, 9.1D.
SCO OpenServer 8.3D06
HP/UX 11 8.3D06
HP/UX 8.3D07
LINUX Intel 8.3D07
IBM AIX 8.3D07
MIPS V.4 8.3D07
UNIX V.4 8.3D08
Compaq Tru64 UNIX 8.3D10
SUN SOLARIS 8.3D10
WIN NT 32 Intel 8.3D12
LINUX Intel 9.1C03
SUN SOLARIS INTEL 9.1C04
UNIX V.4 9.1C04
HP/UX 11 9.1C04
IBM AIX 9.1C04
HP-UX 64-bit9.1C04
Compaq Tru64 UNIX 9.1C05
SUN SOLARIS 9.1C05
WIN NT Developer's WebClient (webinst.exe) 9.1C06
WIN NT 32 Intel 9.1C06
An enhancement has been made to this feature in Progress 9.1E:
The utility will be changed to allow the user to specify that the report should go to a FILE instead of to the SCREEN. This should eliminate the code assigning too much data to the temporary table. The verify option screen will now have a toggle box for the user to select to output to a file. This option allows for very large files to be verified without the user being given an error message for exceeding the 32K limit on the size of a variable.
The file that is produced will be called <ldbname> + ·.vfy· and will be created in the working directory. A message box will be displayed at the end of the verification telling the user what the name of the file is.