DRG-10000 failed to read columnstring
Cause:Error during read of specified text column.
Action:Check the existence and privileges of the column.
DRG-10001 can not access result tablestring
Cause:Specified table does not exist or server does not have write privileges.
Action:Check the result table.
DRG-10002 can not insert into result table
Cause:Text server is not privileged to insert, tablespace is exhausted.
Action:Check privileges and tablespace.
DRG-10011 invalid object namestring
Cause:A table, column or procedure name specified had an invalid format. It is either too long or contains illegal characters. Probably you are passing in incorrect parameters.
Action:Check parameter values.
DRG-10015 id exceeds limit(2147483642) of a number
Cause:The limit of an ID is 2147483642.
Action:Use an ID with value 214748364 or lower.
DRG-10016 you must be the owner to modify this object
Cause:An attempt was made to modify an object which you do not own.
Action:Have the owner modify the object.
DRG-10017 you must bestringto do this:string
Cause:An attempt was made to modify an object which you have no privilege.
Action:Ask the owner modify the object.
DRG-10100 invalid argument found:string
Cause:Invalid command argument was specified.
Action:Check the documentation for the legal arguments and re-execute the command.
DRG-10101 no value for argument:string
Cause:This argument requires value(s).
Action:Re-execute the command with the correct argument value(s).
DRG-10102 mandatory argument missing:string
Cause:This argument is mandatory.
Action:Re-execute the command and specify the argument.
DRG-10103 illegal value for argument:string
Cause:An illegal value was passed to this argument.
Action:Check the documentation for the legal values for this argument.
DRG-10200 invalid server personality mask:string
Cause:The specification for the server personality mask is invalid.
Action:Check the documentation and specify the correct mask.
DRG-10202 server failed to register
Cause:The server failed to register itself with the data dictionary.
Action:Look at the next error on the stack.
DRG-10203 server namedstringdoes not exist
Cause:Update was called with the name of a server that does not exist.
Action:Correct the name of the server.
DRG-10204 server update failed
Cause:The attempt to update the server failed.
Action:Look at the next error on the stack.
DRG-10205 server deregister failed
Cause:The attempt to deregister the server from the data dictionary failed.
Action:Look at the next error on the stack.
DRG-10206 failed to perform recovery for a server or client
Cause:The attempt to perform recovery for a server or client failed.
Action:Contact Oracle Support Services.
DRG-10301 timed out waiting for responses from servers
Cause:Not enough servers are running to handle the current system load, and a large backlog of commands has accumulated; perhaps no servers are running. This message could also indicate an internal error where one of the servers has crashed trying to process a given request.
Action:Check that enough servers are running, and that they are processing commands of the correct type. For instance, a DDL command might timeout if all the servers are setup to exclusively process query commands. Also, check the server log files.
DRG-10302 interrupted waiting for responses from servers
Cause:User interrupted the request before it was completed.
Action:Restart the request.
DRG-10303 could not queue given commands to be processed
Cause:The given command or commands could not (all) be queued. This could indicate an extremely high system load, but it is more likely an internal error.
Action:Check if any servers are running to process the command.
DRG-10304 unexpected error sending command(s) to Oracle Text server
Cause:There was an unexpected error sending commands to the server.
Action:Contact Oracle Support Services.
DRG-10305 pipestringis full
Cause:Could not send command to pipe, because the pipe was full.
Action:Check if any servers are running to process the commands on that pipe.
DRG-10306 server terminated unexpectedly while processing command
Cause:The server shut down during execution of your command. This could be caused by a SHUTDOWN ABORT, or by an internal error in the server.
Action:If the server terminated had an internal error, then contact Oracle Support Services.
DRG-10307 no servers running
Cause:Could not process command because no servers are running with the correct personality mask.
Action:Start some servers with correct personality mask.
DRG-10308 no server with the requiredstringpersonality mask is running
Cause:Could not process command because no servers are running with the correct personality mask.
Action:Start some servers with correct personality mask.
DRG-10309 not enough job queue processes
Cause:Could not process command because no servers with the correct personality mask are running.
Action:Increase theJOB_QUEUE_PROCESSESinitialization parameter or reduce the parallel degree for this statement.
DRG-10310 servers were shutdown before processing request
Cause:The command could not be completed because the servers were shut down or terminated before processing the request.
Action:Start another server with the correct personality mask.
DRG-10311 remote send not supported
Cause:An attempt was made to specify a database link in an index specification.
Action:Specify only local index names.
DRG-10312 logfile name must be specified
Cause:An attempt was made to start logging without specifying a log file name.
Action:Specify a log file name.
DRG-10313 logging has already been started
Cause:An attempt was made to start logging even though logging has already been started.
Action:Stop logging first or ignore this message.
DRG-10314 logging has not been started
Cause:An attempt was made to stop logging even though logging has not been started.
Action:Start logging first or ignore this message.
DRG-10315 logging is not supported on MTS
Cause:You tried to start logging on MTS
Action:
DRG-10500 CREATE_INDEX failed: column specstring
Cause:Failed to create text index on the specified column.
Action:See the next errors on stack and take appropriate action.
DRG-10501 invalid stopword:string
Cause:The stopword specified could be lexed into multiple tokens with current lexer preference.
Action:Check lexer preference and respecify the stopword.
DRG-10502 indexstringdoes not exist
Cause:The specified index does not exist or you do not have access to it.
Action:Check the name of the index and your access to it.
DRG-10503 tablestringcannot be indexed because it has no primary key
Cause:A text key needs to be a single column unique key whose length does not exceed 64 bytes. no such key was defined as an unique index or declared as a primary or unique key constraint.
Action:Create a suitable text key for the table or specify it explicitly in this procedure call.
DRG-10504 primary key is required when using the DETAIL_DATASTORE
Cause:you tried to use the detail datastore to index a table with no primary key constraint
Action:Add a primary key constraint on the table