DRG-10305: pipe string is 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
Category Archives: DRG Database Error Messages
DRG-10304: unexpected error sending command(s) to Oracle Text server
DRG-10304: unexpected error sending command(s) to Oracle Text server
Cause: There was an unexpected error sending command(s) to server
Action: Call customer support
DRG-10303: could not queue given commands to be processed
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-10302: interrupted waiting for responses from servers
DRG-10302: interrupted waiting for responses from servers
Cause: User interrupted the request before it was completed
Action: Restart the request
DRG-10301: timed out waiting for responses from servers
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-10206: failed to perform recovery for a server or client
DRG-10206: failed to perform recovery for a server or client
Cause: Contact oracle support
Action: Contact oracle support
DRG-10205: server deregister failed
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-10204: server update failed
DRG-10204: server update failed
Cause: the attempt to update the server failed
Action: look at the next error on the stack
DRG-10203: server named string does not exist
DRG-10203: server named string does not exist
Cause: update was called with the name of a server that does not exist
Action: correct the name of the server
DRG-10202: server failed to register
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