Subject: | |
From: | |
Reply To: | |
Date: | Wed, 8 Sep 2004 11:07:21 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Any IMAGE return status in the > 2999 and < 4000 range is an indexing
related error (OMNIDEX).
Here is a listing from ODXERROR:
-3000Indexes not synchronized
-3001Feature not yet implemented
-3021Invalid IMAGE Item or KEY
-3025Invalid Key
-3026All items aren't accessable in the set
-3028Invalid Range: leading '@' not allowed in range arguments
-3029Invalid Range: Start key is greater than stop key
-3033Invalid record count in argument
-3114Omnidex ID must be greater than 0
-3217No keywords qualified
-3219Unmatched quote
-3220Missing semicolon terminator in keyword find
-3230Unbalanced parenthesis in argument
-3231Wildcards not allowed in %DATE function
-3232Invalid %DATE function syntax
-3233Invalid %DATE function format type
-3234Error in formatting in %DATE function
-3235Invalid date specified in %DATE function
-3240Illegal same list syntax
-3241Invalid operator encountered
-3242Invalid use of parenthesis and operators
-3243Invalid parenthesis placement
-3244Too many quote pairs (max is 20)
-3246Missing keyword after operator
-3247Illegal range operator combination
-3248Missing start key
-3249Missing stop key
-3250Start key length exceeds keylength
-3251Stop key length exceeds keylength
-3351Missing components in composite key
-3352Invalid character for binary translation
-3353Unsupported size for binary data type
-3354Unable to translate real data type
-3355Can't quote binary conversion data
-3356Value specified contains too many digits for External or Packed Decimal
-3414Omnidex ID must be greater than 0
-3736More than 400 composite keys not supported by dbinfo mode 899
-3737Less than 200 composite keys exist for this database
-3775Database structure has changed since last installation
-3777Base ID not captured by NMDBOPENTPI
-3821TPIMaint error: Invalid New Item for mode 2
-3822TPIMaint error: Invalid Data Set for specified
-3831TPIMaint error: Invalid mode specified
-3885TPIInfo error: DBOPEN failed
-3886TPIInfo error: Couldn't locate base id
-3887TPIMaint requires database to be opened in mode -1 for maintenance
-3888TPIMaint maintenance dbopen failed
-3889TPIMaint ilcb link failed
-3890TPIMaint had a bad database name passed for mode 1001
-3891TPIMaint must have fully qualified database name for mode 1001
-3892TPIMaint error in writing to Dbinstal STDIN file
-3893TPIMaint error: Couldn't Build Dbinstal STDIN file
-3894TPIMaint error: Couldn't re-open database after build
-3896TPIMaint error: mode 313 dbiinfo call failed???
-3897TPIMaint error: Createprocess of Dbinstal failed
-3899TPIMaint error: Dbinstal build failed
-3900Cannot redirect XLOMNIDX on open of TPI enabled database
-3919DBINSTAL must be run without any XLs specified
-3991Omnidex installation needs validation, please run DBINSTAL
-3992No further undo for this domain available
-3993No active keyword find for this domain
-3994Cannot undo, no previous keyword find for this domain
-3995No active generic find
-3996No active keyword find
-3997Keyword ID list has collapsed
-3998Composite component offset invalid
-3999Generic key range list has collapsed
My particular version does not have 3949. Probably neither did
your's, hence the UNRECOGNIZED RETURN STATUS: 3949
But, if you see an IMAGE return status in the 3000's most likely it
is an indexing related issue.
pm
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|