CHAPTER 2. ConText Option Internal Messages
This chapter provides a list of the internal errors you may receive while performing ConText Option operations, as well as an explanation of each error.
The errors are presented in numerical order, grouped according to type.
50000--50099: Buffer Service
DRG--50000 max. string length larger than pagesize: str %(1)s, pagesize %(2)s
| Cause: | The Max string length specified (or defaulted) is larger than page size. | |
| Action: | Use a smaller max string size. | |
50100--50199: Core
DRG--50100 CORE LSF error: %(1)s
| Cause: | Detected a CORE LSF error. | |
| Action: | Look up the core error and take appropriate action. | |
DRG--50101 CORE LEM error: %(1)s
| Cause: | Detected a CORE LEM error while reading the error stack. | |
| Action: | Contact customer support. | |
50200--50299: Dictionary
DRG--50200 invalid policy id: %(1)s
| Cause: | The specified policy ID cannot be found in the dictionary. | |
| Action: | Contact customer support. | |
50300--50399: Dispatcher
DRG--50300 error sending message from server to client
| Cause: | This is a database error or an internal ConText error. | |
| Action: | Contact customer support | |
DRG--50301 server error reading request queue
| Cause: | This is a database error or an internal ConText error. | |
| Action: | Contact customer support. | |
DRG--50302 server error reading OOB break queue; cannot detect interrupts
| Cause: | This is a database error or an internal ConText error. | |
| Action: | Contact customer support. | |
DRG--50303 error in bufout
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50304 error in execute()
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50305 getcmd() called when one of the queue names is NULL
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
50400--50499: Engine
DRG--50400 maximum number of fuzzy match candidates exceeded: %(1)s
| Cause: | This is an internal error; probably resulting from a large number of indexed words. | |
| Action: | Contact customer support. | |
50500--50599: Framework
DRG--50501 failed to construct or open object: %(1)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
50600--50699: General Internal
DRG--50600 assertion failed
| Cause: | An internal check-condition has been violated. | |
| Action: | Contact customer support. | |
DRG--50601 fatal error
| Cause: | A fatal error has occurred. | |
| Action: | Contact customer support. | |
DRG--50602 function is not implemented yet
| Cause: | The named function has not been implemented. | |
| Action: | Contact customer support. | |
DRG--50603 unrecognized operation code %(1)s
| Cause: | Bad operation code was encountered (reached switch default:). | |
| Action: | Check .h files versions. | |
DRG--50604 invalid length for database object name
| Cause: | A name constructed for a database object exceeded the limit. | |
| Action: | Shorten the length of the object name. | |
DRG--50606 database object already exist : %(1)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50607 failed to obtain column info for cid %(1)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
50700--50799: Listener
DRG--50700 unknown command (args=queue, command)
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50701 error in listener.get_cmd()
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50702 error in drtlsleep()
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50703 listener startup error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
50800--50899: OCI/SQL
DRG--50800 failed to open cursor
| Cause: | Too many cursors open for internal queries. | |
| Action: | Implement cursor cleanup routine. | |
DRG--50801 failed to parse cursor
| Cause: | Parse error on an internal query. | |
| Action: | Check versions of code. | |
DRG--50802 failed to bind input
| Cause: | Bind error on an internal query. | |
| Action: | Check versions of code. | |
DRG--50803 failed to define output
| Cause: | Define error on an internal query | |
| Action: | Check versions of code. | |
DRG--50804 failed to exec cursor
| Cause: | Exec error on an internal query. | |
DRG--50805 failed to close cursor
| Cause: | Cursor close error on an internal query. | |
| Action: | Check versions of code. | |
DRG--50850 %(1)s
| Cause: | This is an ORACLE error. | |
| Action: | Refer to the Oracle7 documentation. | |
DRG--50851 SQL execute failed
| Cause: | Failed to execute a SQL statement. | |
| Action: | Contact customer support. | |
DRG--50852 failed to turn SQL trace on
| Cause: | This is an internal error. | |
| Action: | Contact customer support | |
DRG--50853 fetch error
| Cause: | Fetch error on an internal query. | |
| Action: | Check versions of code. | |
DRG--50854 bad key fetch (null/truncated)
| Cause: | Key value is to long or or is null. | |
| Action: | Check table definition and limit on key length. | |
DRG--50855 logoff fail
| Cause: | Fail to logoff from the database. | |
| Action: | Check versions of code. | |
DRG--50856 dbms_alert.waitone failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
50900--50999: Parse
DRG--50900 text query parser error on line %(1)s, column %(2)s
DRG--50901 text query parser syntax error on line %(1)s, column %(2)s
DRG--50902 unexpected character %(1)s
DRG--50903 invalid weight %(1)s
DRG--50904 weight %(1)s outside valid range 0.1 to 10.0
DRG--50905 invalid score threshold %(1)s
| Cause: | Invalid score threshold. | |
DRG--50906 score threshold %(1)s is not an integer
| Cause: | Invalid score threshold. | |
DRG--50907 score threshold %(1)s outside valid range 1 to 100
| Cause: | Invalid score threshold. | |
DRG--50908 invalid maximum number of documents %(1)s
| Cause: | Invalid maximum number of documents. | |
DRG--50909 maximum number of documents %(1)s is not an integer
| Cause: | Invalid maximum number of documents. | |
DRG--50910 max documents requested %(1)s outside valid range 1 to 65535
| Cause: | Invalid maximum number of documents. | |
DRG--50911 invalid first document number %(1)s
| Cause: | Invalid first document number. | |
DRG--50912 first document number %(1)s is not an integer
| Cause: | Invalid first document number. | |
DRG--50913 first document requested %(1)s is not a positive number
| Cause: | Invalid first document number. | |
DRG--50914 invalid last document number %(1)s
| Cause: | Invalid last document number. | |
DRG--50915 last document number %(1)s is not an integer
| Cause: | Invalid last document number. | |
DRG--50916 last document %(1)s is less than first document
| Cause: | Invalid last document number. | |
DRG--50917 escape on at end of text query string
| Cause: | Unbalanced escape characters. | |
DRG--50918 mismatched close escape character
| Cause: | No matching open escape character for close escape. | |
| Action: | Match open and close escape characters. | |
DRG--50919 NEAR operand not a phrase, equivalence or another NEAR expression
| Cause: | Invalid operand type for NEAR operator. | |
| Action: | Correct operand type. | |
DRG--50920 part of phrase not itself a phrase or equivalence
| Cause: | Invalid type of expression which is part of phrase. | |
DRG--50921 EQUIV operand not a word or another EQUIV expression
| Cause: | Invalid operand type for EQUIV operator. | |
| Action: | Correct operand type. | |
DRG--50922 PL/SQL execution failed for %(1)s
| Cause: | PL/SQL function may not exist or is returning bad value. | |
| Action: | Verify that function exists or contact customer support. | |
DRG--50923 could not rewrite PL/SQL for execution
| Cause: | This is an internal parser error. | |
| Action: | Contact customer support. | |
DRG--50924 PL/SQL inside PL/SQL not supported
| Cause: | PL/SQL function call returned another PL/SQL call. | |
| Action: | Remove recursive PL/SQL. | |
DRG--50925 could not parse return value of PL/SQL
| Cause: | String returned by PL/SQL function could not be parsed. | |
| Action: | Fix PL/SQL function being called. | |
DRG--50926 invalid text query string
| Cause: | Query string is empty or made up of invalid characters. | |
DRG--50927 parser failed on line %(1)s on column %(2)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50928 reserved failure on line %(1)s on column %(2)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50929 parser internal on line %(1)s on column %(2)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50930 parser memory failure on line %(1)s on column %(2)s
| Cause: | Memory allocation or freeing error. | |
| Action: | Context customer support. | |
DRG--50931 parser not opened
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50932 parser preference initialization failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50933 parser hash insert failure
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50934 parser hash create failure
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50935 parser component failure
| Cause: | This is an internal error. | |
| Action: | Look for related erros and contact customer support. | |
DRG--50936 query word %(1)s is too complex for index
| Cause: | This is an internal error. | |
| Action: | Look for related erros and contact customer support. | |
DRG--50937 query too complex
| Cause: | Query is too complex for query evaluator. | |
| Action: | Make query smaller. | |
DRG--50938 parser already bound
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--50939 parser not set
| Cause: | This is an internal error. | |
| Action: | Look for related erros and contact customer support. | |
DRG--50940 parser not parsed
| Cause: | This is an internal error. | |
| Action: | Look for related erros and contact customer support. | |
DRG--50941 PL/SQL function %(1)s cannot be executed
| Cause: | PL/SQL function may not exist or cannot be executed by user. | |
| Action: | Rewrite PL/SQL function specified in query. | |
DRG--50942 errors: %(1)s%(2)s
| Cause: | PL/SQL function encountered error -- the message text for the error is provided. | |
| Action: | Refer to error message to determine next action. | |
DRG--50943 query token too long on line %(1)s on column %(2)s
| Cause: | A query token is longer than 256 bytes. | |
DRG--50944 NEAR operator not supported for theme index
| Cause: | NEAR operator used in theme index query. | |
| Action: | Rewrite query without NEAR operator. | |
DRG--50945 Illegal phrase in query for theme index
| Cause: | Phrase incorrectly defined in theme index query. | |
DRG--50946 Invalid unary operator for theme index
| Cause: | Stemming, fuzzy match, and Soundex not allowed for theme index. | |
DRG--50947 Invalid use of theme expansion operator for non-theme index
| Cause: | Invalid use of theme expansion unary operator. | |
51000--51099: Wordlist
DRG--51000 wordlist function initialization failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51001 wordlist preference initialization failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51002 unexpected component failure
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51003 WL does not exist
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51004 WL not all words were mapped to tags
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51005 WL inserts failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51006 WL commit failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51007 WL unexpected OCI failure
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51008 WL not all tags found
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51009 WL query uncancelled
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51010 WL not bound
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51011 WL to many input words
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51012 WL failed to create table
| Cause: | Invalid preference. | |
| Action: | Fix preference describing layout of word list table. | |
DRG--51013 WL failed to create wordlist index
| Cause: | Invalid preference. | |
| Action: | Fix preference describing layout of word list table. | |
DRG--51014 WL query cancelled
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51015 WL not set
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51016 WL failed to drop wordlist table
| Cause: | Invalid preference. | |
| Action: | Fix preference describing layout of word list table. | |
DRG--51017 unable to open storage buffer for fuzzy match candidates
| Cause: | This is an internal error; probably a result of insufficient memory. | |
| Action: | Contact customer support. | |
DRG--51018 unable to destroy fuzzy match object
| Cause: | Internal error; probably a result of corrupted memory | |
| Action: | Contact customer support. | |
DRG--51019 unable to open or illegal format for fuzzy match data file: %(1)s
| Cause: | Unable to open OS file containing fuzzy matching information or the file was not of the correct format. | |
| Action: | Consult the ConText Option documentation for correct location of the fuzzy match information files and check for file damage. | |
DRG--51020 out of memory in fuzzy matcher
| Cause: | Cannot allocate more memory. | |
| Action: | Contact your system adminstrator. | |
DRG--51021 undefined error in fuzzy matcher
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51022 undefined error in stemmer
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51023 stemmer file cannot be opened
| Cause: | Unable to open OS file containing stemmer lexicon, or the file contents were not correct | |
| Action: | Consult the ConText Option documentation for for correct location of the stemmer lexicons and check for file damage | |
DRG--51024 out of memory in stemmer
| Cause: | Cannot allocate more memory. | |
| Action: | Contact your system administrator. | |
DRG--51025 an invalid character was passed to the stemmer
| Cause: | Invalid character in word input to the stemmer. | |
| Action: | Remove invalid character from word to be stemmed. | |
51100--51199: Utility Argument Processing
DRG--51100 invalid program argument index
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51101 argument processing callback failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
51200--51299: Keymap
DRG--51200 open keymap failed for a policy: id = %(1)s
| Cause: | Failed to initialize the keymap for the column ID specified. | |
| Action: | Check policy ID. Contact custmoer support if caused by. | |
DRG--51201 failed to perform DDL operation: database object %(1)s
| Cause: | Textkey mapping service failed on DDL operation. | |
| Action: | Check Oracle error and take corrective action. | |
DRG--51202 invalid key mapping operation mode : %(1)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51203 found doc ids without mappings during get maps
| Cause: | Found DOCIDs without mappings during get mapping by DOCIDs; this indicates the index data and keymap service are out of synch. | |
| Action: | Contact customer support. | |
51300--51399: DML Queue
DRG--51300 error getting dml Queue lock
| Cause: | A server may have hung while processing the DML Queue, leaving the queue locked. | |
| Action: | Contact customer support. | |
DRG--51301 error releasing dml Queue lock
| Cause: | This is an internal database error; possibly the queue lock was dropped while in use. | |
| Action: | Contact customer support. | |
DRG--51303 error advancing timestamp
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51304 error calculating minimum timestamp in progress
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51305 timeout getting dml Queue lock
| Cause: | A server may have hung while processing the DML Queue, leaving the queue locked. | |
| Action: | Contact customer support. | |
DRG--51306 error creating trigger
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51307 error dropping trigger
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51308 failed to sync to timestamp %(1)s
| Cause: | The system could not perform the sync to given timestamp. | |
| Action: | See next error on stack to determine course of action. | |
DRG--51309 Get_batch() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51310 batch_done() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51311 exec_ddl() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51312 dm_addlist() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51313 dm_uniqlist() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51314 dm_getpol() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51315 dm_collist() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51316 dm_colreplace() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51317 dm_colexpand() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51318 dm_make_row_trigger() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51319 dm_do_triggers() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51320 dm_add() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51321 dm_remove() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51322 dm_stripe() failed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51323 %(1)s queue is in a disabled state
| Cause: | An earlier Oracle error has caused this queue to be disabled. | |
| Action: | The Oracle error reported earlier needs to be corrected before reenabling the queue. | |
DRG--51324 DML queue has been disabled - %(1)s
| Cause: | Oracle errors, typically space management errors, occurred. | |
| Action: | Correct the underlying Oracle error before enabling the queue. | |
DRG--51325 could not disable %(1)s queue - shutting down server
| Cause: | The queue table cannot be updated to disable the queue, following the detection of Oracle errors. | |
| Action: | Correct the underlying Oracle error before enabling the queue. | |
51400--51499: DDL
DRG--51400 error getting dbms lock on text index. polid = %(1)s, status = %(2)s
| Cause: | Error acquiring an user lock for text index access. | |
| Action: | Contact customer support. | |
DRG--51401 error releasing dbms lock on text index. polid = %(1)s, status = %(1)s
| Cause: | Error acquiring an user lock for text index access. | |
| Action: | Contact customer support. | |
DRG--51402 invalid index access mode. mode = %(1)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
51500--51599: Filter
DRG--51500 could not initialize filter
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51501 could not bind filter to a column
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51502 could not fetch from filter
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51503 bad mode for opening extended file
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51504 cannot open an extended file which is already open
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51505 cannot open a store-based extended file for write
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51506 use of extended file is inconsistent with its open-mode
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51507 unknown format id
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51508 there is no filter function for this format
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
51600--51699: Indexing
DRG--51600 invalid indexing operation attempted
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51601 fewer document count %(1) given by datastore
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51602 index buffer too small: %(1) bytes
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
51700--51799: Sequence (Doclist)
DRG--51700 argument expected to create list manager
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51701 attempt to open dummy list
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51702 attempt to open multiple scan on a list
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51703 attempt to register a dummy list
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51704 list found with illegal attribute
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
51800--51899: I/O
DRG--51800 NULL file handle found
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51801 failed to seek in file: %(1)
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51802 failed to read from file: %(1)
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51803 failed to open file: %(1)
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51804 failed to write to file: %(1)
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51805 failed to read directory: %(1)
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
51900--51999: Pipe
DRG--51905 pipe.get_lock: called with non_numeric address %(1)s
| Cause: | Server tried to read from an illegal shared pipe. | |
| Action: | Contact customer support. | |
DRG--51906 pipe.get_lock: error in dbms_lock
| Cause: | Internal error occurred while dispatching commands to server. | |
| Action: | Contact customer support. | |
DRG--51907 pipe.get_lock: error getting lock
| Cause: | Internal error occurred while dispatching commands to server. | |
| Action: | Contact customer support. | |
DRG--51908 pipe.release_lock: error releasing lock
| Cause: | Internal error occurred while dispatching commands to server. | |
| Action: | Contact customer support. | |
DRG--51909 pipe.lput: unexpected return from dbms_pipe.send_message
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51910 pipe.lput: error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51911 pipe.get error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51912 pipe.purge error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51913 pipe.put error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51914 pipe.local_remove: internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51915 pipe.trim_blanks internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51916 pipe.get_oracle_sid internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51917 pipe.get_domain internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51918 pipe.get_instance_name internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51919 pipe.local_addr internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51920 pipe.get_inst_pipe internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51921 pipe.remove: internal error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51922 array to list overflow error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51923 list to array overflow error
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--51924 problem with instance name
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
52000--52099: Result Table Management
DRG--52000 invalid type of table requested
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52001 failed to allocate a table to the caller
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52002 failed to create pool of result tables
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52003 the named result table is not registered
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52004 failed to recover all tables allocated to this session id
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52005 error allocating table
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52006 error deallocating table
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52007 error recovering allocated tables
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
52100--52199: Context Internal
DRG--52100 %(1)s returned internal error code %(2)s
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52101 an invalid session handle was passed to ConText
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52102 an invalid transaction handle was passed to ConText
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52103 the ConText environment could not reset
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52104 the ConText environment could not initialize
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52105 no delete function found
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
DRG--52106 ConText service results could not be committed
| Cause: | This is an internal error. | |
| Action: | Contact customer support. | |
