Teradata SQL Error and Failure Codes from Error 12100 to 12109

SQLServerF1

12100 There is no current logmark.
Explanation: A logcont(), logcall() or logclear() service call was issued when there was no logmark region in effect. This
indicates an error in the program that issued the call.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

12101 Log message category is undefined.
Explanation: A logsetcat() service call was passes an undefined category code. This indicates an error in the program
that issued the call.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

12102 One or more CPU hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12103 One or more memory hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12104 One or more Bynet hardware category events have been discarded.
Explanation: Too many Bynet hardware category events were being received, so some of them have been discarded.
Preceding log messages for host events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no action is needed.

12105 One or more disk hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12106 One or more channel hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12107 One or more host category events have been discarded.
Explanation: Too many host category events were being received, so some of them have been discarded. Preceding log
messages for host events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no action is needed.

12108 One or more driver category events have been discarded.
Explanation: Too many driver category events were being received, so some of them have been discarded. Preceding log
messages for driver events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no response is needed.

12109 One or more resource category events have been discarded.
Explanation: Too many resource category events were being received, so some of them have been discarded. Preceding
log messages for resource category events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no response is needed.

Above are list of Teradata Errors or Failure Codes from Error 12100 to 12109 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Teradata SQL Error and Failure Codes from Error 11982 to 11991

SQLServerF1

11992 A client slot is vacated slot = %d old process id = %d old task id = %d new process id = %d new task id = %d
Explanation: The client slot assigned to a client has been re-assigned to another client from a different process.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The vacated client should close the RSS handle and either exit or re-acquire a new RSS handle thru the rssuseropen()
call.
Remedy: Contact the Global Support Center.

11993 RSS Client Service is disabled
Explanation: RSS Client Service is disabled by a flag in control GDO.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: To enable RSS Client Service, reset the RSS Disable Client flag in control GDO.
Remedy: Contact the Global Support Center.

11994 No vdisk found for VprocId %d
Explanation: RSS API rssgetsvdskidx did not find vdisk matching requested vproc id. Verify the AMP vdisk configuration
and status.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS messages are normally warnings only, but the calling routine may be coded to terminate after the error message
is displayed.
Remedy: Contact the Global Support Center.

11995 Two devices have the same device information.
Explanation: A new device being registered with RSS has the same identifying information as an existing device. May
be a system configuration issue.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
Remedy: Contact the Global Support Center.

11998 %$HeaderRSS debug event; %s.
Explanation: This event is used for RSS debugging.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The event is used in debugging environment only.
Remedy: Contact the Global Support Center.

11999 %$HeaderAn RSS internal software error occurred; %s.
Explanation: This event is used to report a variety of low-probability errors in RSS service calls.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

12000 %s
Explanation: This event code is used to log text messages received or generated by the PDE console subsystem.
Generated By: PDE console subsystem.
For Whom: System Support Representative.
Remedy: In some cases, this is simply an informational message and no action is needed. If the message text indicates
that an error occurred, or if the message is repeated frequently or appears to be associated with other abnormal console
behavior, save the portion of the log for the period in question and report the problem to the Global Support Center. Otherwise,
no response is needed.

12001 %s
Explanation: An unexpected message was received by the console interface module. The message text is a variable
string giving the reason for the error. This typically indicates a protocol violation of some kind in the dialog between the
PDE console control programs and the DBW database window. It has no impact on the actual operation of the DBS.
Generated By: PDE console subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

12010 The system debugger is not active.
Explanation: A start command was issued in the database console supervisor window with the debug option, requesting
that the task to be started run under the control of the system debugger, but the system debugger is not currently active.
The task has been started, but will not run until the debugger is attached and system execution continued.
Generated By: PDE console subsystem.
For Whom: Systems Engineer, Operator.
Remedy: Start the system debugger, attach to the system, set any breakpoints needed, and continue execution. Or stop
the task and restart it without specifying debug.

Above are list of Teradata Errors or Failure Codes from Error 11992 to 12010 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Troubleshooting Sybase Error Code from Error 315 to 538

SQLServerF1

Sybase Error Code 315
Sybase SQL Code –137
Table ‘%1’ requires a unique correlation name
Sybase Error Code 401
Sybase SQL Code –134
Feature ‘%1’ not implemented
Sybase Error Code 401
Sybase SQL Code –135
Language extension
Sybase Error Code 401
Sybase SQL Code –156
Invalid expression near ‘%1’

Sybase Error Code 404
Sybase SQL Code –890
Statement size or complexity exceeds server limits
Sybase Error Code 409
Sybase SQL Code 109
Null value eliminated in aggregate function
Sybase Error Code 409
Sybase SQL Code –90
Argument %1 of procedure ‘%2’ cannot be null
Sybase Error Code 504
Sybase SQL Code –265
Procedure ‘%1’ not found
Sybase Error Code 509
Sybase SQL Code –140
User ID ‘%1’ does not exist

Sybase Error Code 512
Sybase SQL Code –186
Subquery cannot return more than one row
Sybase Error Code 518
Sybase SQL Code 103
Invalid data conversion
Sybase Error Code 532
Sybase SQL Code 104
Row has been updated since last time read
Sybase Error Code 532
Sybase SQL Code 106
Value for column ‘%1’ in table ‘%2’ has changed
Sybase Error Code 538
Sybase SQL Code –627
Disallowed language extension detected in syntax near ‘%1’

Above are list of Sybase Error Code Messages from Error Code 315 to 538 received while performing certain operation against Sybase Database or related products.

What are Sybase Error Codes?

Sybase error codes are a set of error codes for use by all Sybase products, including Adaptive Server Enterprise. For every Sybase error code returned by Sybase IQ, there is a pair of matching Sybase IQ error codes (SQLCODE and SQLSTATE). In many cases Sybase IQ error codes offer a finer level of granularity than their Sybase error code counterparts, thus some Sybase error codes in the following table are non-unique.

Many of the errors contain the characters %1, %2 and so on. These are replaced by the parameters to the error message.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Sybase Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Oracle Database Errors or Warnings from Error ORA-13903 to ORA-13912

SQLServerF1

ORA-13903: Invalid combination of string threshold value and operator.
Cause: A non-positive number was used for “Blocked User Session Count” metrics while operator contains equal.
Action: Use a positive number for the threshold value or use “greater than” operator.
ORA-13904: The file has been dropped and recreated during the procedure call.
Cause: The file on which threshold is specified was dropped and recreated during the procedure call.
Action: Retry this operation.
ORA-13905: Critical or warning threshold have incorrect values
Cause: The tablespace threshold values can be in the range 0 to 100 only.
Action: Check the threshold values

ORA-13906: The tablepace is not of the right type.
Cause: An attempt was made to set a threshold on dictionary-managed tablespaces.
Action: Check the tablespace type and reissue the command.
ORA-13907: Threshold value is invalid.
Cause: An attempt was made to specify an invalid value for critical or warning thresholds.
Action: Use non-negative integers only for threshold values.
ORA-13908: Invalid combination of metrics id and object type parameters.
Cause: An attempt was made to specify an invalid combination of metrics id // and object type parameters.
Action: Specify a valid combination of metrics id and object type parameters.

ORA-13909: Invalid combination of threshold value and operator.
Cause: An attempt was made to specify an invalid combination of threshold value and operator.
Action: Check the operator and threshold values and reissue statement.
ORA-13910: Parameter string cannot be NULL.
Cause: An attempt was made to call GET_THRESHOLD procedure without a required parameter.
Action: Specify a valid value for this parameter.
ORA-13911: Threshold not found
Cause: The threshold did not exist with the specified threshold key.
Action: No action required.
ORA-13912: Critical threshold value is less than warning threshold value.
Cause: An attempt was made to call SET_THRESHOLD procedure with the critical threshold value less than the warning threshold value.
Action: Check the threshold values and reissue the statement.

Above are list of Oracle Database Errors or Warnings from Error ORA-13903 to ORA-13912 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Sybase Error Code from Error 230 to 315

SQLServerF1

Sybase Error Code 230
Sybase SQL Code –190
Cannot update an expression
Sybase Error Code 233
Sybase SQL Code –195
Column ‘%1’ in table ‘%2’ cannot be NULL
Sybase Error Code 233
Sybase SQL Code –733
Number of columns allowing NULLs exceeds limit
Sybase Error Code 257
Sybase SQL Code –157
Cannot convert %1 to a %2

Sybase Error Code 257
Sybase SQL Code –705
Return type of void from procedure ‘%1’ cannot be used in any expression
Sybase Error Code 262
Sybase SQL Code –121
%1
Sybase Error Code 264
Sybase SQL Code –637
Duplicate insert column
Sybase Error Code 285
Sybase SQL Code –708
READTEXT or WRITETEXT statement cannot refer to a view
Sybase Error Code 301
Sybase SQL Code –147
There is more than one way to join ‘%1’ to ‘%2’

Sybase Error Code 301
Sybase SQL Code –680
Invalid expression in WHERE clause of Transact-SQL outer join
Sybase Error Code 301
Sybase SQL Code –146
There is no way to join ‘%1’ to ‘%2’
Sybase Error Code 305
Sybase SQL Code –681
Invalid join type used with Transact-SQL outer join
Sybase Error Code 311
Sybase SQL Code –295
Cannot uniquely identify rows in cursor
Sybase Error Code 314
Sybase SQL Code –122
Operation would cause a group cycle
Sybase Error Code 315
Sybase SQL Code –136
Table ‘%1’ is in an outer join cycle

Above are list of Sybase Error Code Messages from Error Code 230 to 315 received while performing certain operation against Sybase Database or related products.

What are Sybase Error Codes?

Sybase error codes are a set of error codes for use by all Sybase products, including Adaptive Server Enterprise. For every Sybase error code returned by Sybase IQ, there is a pair of matching Sybase IQ error codes (SQLCODE and SQLSTATE). In many cases Sybase IQ error codes offer a finer level of granularity than their Sybase error code counterparts, thus some Sybase error codes in the following table are non-unique.

Many of the errors contain the characters %1, %2 and so on. These are replaced by the parameters to the error message.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Sybase Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Teradata SQL Error and Failure Codes from Error 11982 to 11991

SQLServerF1

11982 Cliend ID not available
Process id = %d Task id = %d
Explanation: Can not assign a client ID to the RSS environment
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The processes in the node may have opened too many RSS environments
Remedy: Contact the Global Support Center.

11983 Bad RSS handle
Explanation: The handle to the RSS environment is invalid.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the bad handle error.
Remedy: Contact the Global Support Center.

11984 Bad cliend ID Clientid = %d
Explanation: Client ID is either out of range or not in use.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The client may have already closed the RSS environment.
Remedy: Contact the Global Support Center.

11985 Buffer not available
Explanation: Buffer needed for the RSS service is not available.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The RSS buffer is either not available or can not be created.
Remedy: Contact the Global Support Center.

11986 Bad mode parameter
Explanation: The mode parameter is invalid.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The mode parameter has invalid flag combinations.
Remedy: Contact the Global Support Center.

11987 RSS was unable to unmap a memory mapped file. return status = %d file size = %d file name = %s
Explanation: RSS gets an error status unmapping a memory mapped file
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the unmap error.
Remedy: Contact the Global Support Center.

11988 Buffer creation fail
Explanation: The buffers needed for the RSS environment can not be created
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the buffer creation error.
Remedy: Contact the Global Support Center.

11989 Bad buffer size parameter
Explanation: The buffer size parameter is invalid.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The buffer size parameter contains invalid value.
Remedy: Contact the Global Support Center.

11990 RSS deamon is not ready
Explanation: The RSS deomon is not ready to service message requests
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The caller for RSS services may retry at a later point.
Remedy: Contact the Global Support Center.

11991 Bad process for RSS environment
Explanation: The handle to the RSS environment does not belong to the process
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS service is invoked by a process that does not own the RSS handle.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 11982 to 11991 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Troubleshooting Sybase Error Code from Error 176 to 230

SQLServerF1

Sybase Error Code 176
Sybase SQL Code –148
Unknown function ‘%1’
Sybase Error Code 182
Sybase SQL Code –159
Invalid column number
Sybase Error Code 201
Sybase SQL Code –639
Parameter name missing in call to procedure ‘%1’
Sybase Error Code 201
Sybase SQL Code –615
Parameter ‘%1’ not found in procedure ‘%2’
Sybase Error Code 201

Sybase SQL Code –737
Signature ‘%1’ does not match procedure parameters
Sybase Error Code 205
Sybase SQL Code –153
SELECT lists in UNIONN, INTERSECTT or EXCEPTT do not match in length
Sybase Error Code 207
Sybase SQL Code –124
More columns are being droppedd from table ‘%1’ than are defined
Sybase Error Code 207
Sybase SQL Code –143
Column ‘%1’ not found
Sybase Error Code 208
Sybase SQL Code –142
Correlation name ‘%1’ not found
Sybase Error Code 209

Sybase SQL Code –144
Column ‘%1’ found in more than one table — need a correlation name
Sybase Error Code 209
Sybase SQL Code –163
Derivedd table ‘%1’ has no name for column %2
Sybase Error Code 213
Sybase SQL Code –207
Wrong number of values for INSERTT
Sybase Error Code 217
Sybase SQL Code –274
Procedure or trigger calls have nested too deeply
Sybase Error Code 220
Sybase SQL Code –158
Value %1 out of range for destination
Sybase Error Code 230
Sybase SQL Code –191
Cannot modifyy column ‘%1’ in table ‘%2’

Above are list of Sybase Error Code Messages from Error Code 176 to 230 received while performing certain operation against Sybase Database or related products.

What are Sybase Error Codes?

Sybase error codes are a set of error codes for use by all Sybase products, including Adaptive Server Enterprise. For every Sybase error code returned by Sybase IQ, there is a pair of matching Sybase IQ error codes (SQLCODE and SQLSTATE). In many cases Sybase IQ error codes offer a finer level of granularity than their Sybase error code counterparts, thus some Sybase error codes in the following table are non-unique.

Many of the errors contain the characters %1, %2 and so on. These are replaced by the parameters to the error message.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Sybase Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Oracle Database Errors or Warnings from Error ORA-13865 to ORA-13902

SQLServerF1

ORA-13865: Module name must be specified
Cause: Attempt to enable/disable a service-level statistics aggregation without a module specification
Action: Supply module name
ORA-13866: Client identifier must be specified
Cause: Omitting client identifier while enabling/disabling tracing or aggregation
Action: Supply the client identifier
ORA-13867: Database-wide SQL tracing is already enabled
Cause: Attempt to enable a database-level tracing which has been already enabled
Action: Disable and re-enable tracing with different bind/wait options

ORA-13868: Instance-wide SQL tracing on instance string is not enabled
Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance
Action: No action required
ORA-13869: Instance-wide SQL tracing on instance string is already enabled
Cause: Attempt to enable an instance-level tracing which has been already enabled on a specific instance
Action: Disable and re-enable tracing with different bind/wait options
ORA-13870: Database-wide SQL tracing is not enabled
Cause: Attempt to disable a database-level tracing which was never enabled
Action: No action required

ORA-13871: Invalid instance name
Cause: Instance name is too long (exceeding 16 characters)
Action: Supply correct name
ORA-13900: missing or invalid parameter string
Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid.
Action: Specify a valid value for this parameter.
ORA-13901: Object string was not found.
Cause: An object name was passed to SET_THRESHOLD procedure that did not map to a valid object.
Action: Specify a valid object name.
ORA-13902: The specified file string is not a data file.
Cause: The object name was passed to a SET_THRESHOLD procedure that did not map to a valid data file.
Action: Specify a valid data file name.

Above are list of Oracle Database Errors or Warnings from Error ORA-13865 to ORA-13902 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Oracle Database Errors or Warnings from Error ORA-13855 to ORA-13864

SQLServerF1

ORA-13855: Tracing for service (module/action) string on instance string is already enabled
Cause: Attempt to enable a service-level tracing which has been already enabled on a specific instance
Action: Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options
ORA-13856: Service name must be specified
Cause: Omitting service name while enabling/disabling tracing or aggregation
Action: Supply the service name
ORA-13857: Invalid module name
Cause: Module name is too long (exceeding 48 characters)
Action: Supply correct name

ORA-13858: Invalid action name
Cause: Action name is too long (exceeding 32 characters)
Action: Supply correct name
ORA-13859: Action cannot be specified without the module specification
Cause: Action name is specified, but the module name is not
Action: Supply the module name
ORA-13860: Invalid service name
Cause: Service name is too long (exceeding 64 characters)
Action: Supply correct name

ORA-13861: Statistics aggregation for client identifier string is already enabled
Cause: Attempt to enable a client identifier aggregation which has been already enabled
Action: Supply correct client identifier
ORA-13862: Statistics aggregation for client identifier string is not enabled
Cause: Attempt to disable a client identifier statistics aggregation which was never enabled
Action: Supply correct client identifier
ORA-13863: Statistics aggregation for service(module/action) string is not enabled
Cause: Attempt to disable a service-level statistics aggregation which was never enabled
Action: Supply correct service(module/action) name
ORA-13864: Statistics aggregation for service (module/action) string is already enabled
Cause: Attempt to enable a service-level statistics aggregation which has been already enabled
Action: Supply correct service(module/action)

Above are list of Oracle Database Errors or Warnings from Error ORA-13855 to ORA-13864 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Teradata SQL Error and Failure Codes from Error 11973 to 11981

SQLServerF1

11973 Device Map call returns an error status. return status = 0x%08x.
Explanation: The call to get the Pdisk Device Map returns an error status. This failure may result in some pdisk attributes
having zero values in the ResUsageSpdsk table.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Pdisk ResUsage data may be invalid.
Remedy: Contact the Global Support Center.

11974 Pdisk count from device map is incorrect. count from device map = %d count from vconfig gdo = %d
Explanation: The number of Pdisk entries returned in the Pdisk device map is not matching the number of Pdisk entries
in the vconfig gdo. This failure may result in some pdisk attributes having zero values in the ResUsageSpdsk table.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Pdisk ResUsage data may be invalid.
Remedy: Contact the Global Support Center.

11976 rssd thread exit wait failed. WaitForSingleObject() returned 0x%08x, error code %d RSS may not log some or all data.
Explanation: The exit of the rssd thread is waited on during a tpareset. The wait has returned a failure status.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
Remedy: Contact the Global Support Center.

11977 Data overflow or negative in a resusage counter. Counter = 0x%08x index = %d value = %d interval = %d ticks Pdh data = %.2f elapse time = %d new data = %08x %08x old data = %08x %08x
Explanation: The counter value is either negative or overflowing the max value.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11978 Two disk devices have the same device ID. Device ID = 0x%08x Device index %d: Major=%d, Minor=%d Device index %d: Major=%d, Minor=%d
Explanation: The disk device ID is formed from the device major and minor numbers. Dupliation of device ID is
detected while scanning the device list.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
Remedy: Contact the Global Support Center.

11979 error encountered in deleting a file status = %d errcode = %d file = %s
Explanation: Error returned while deleting the RSS file.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: This RSS error message is informational only. Other events may have caused the file delete error.
Remedy: Contact the Global Support Center.

11980 CPU statistics error cpu number = %d cpu time = %d, expected time = %d, gather interval = %d percent err = %.2f%
Explanation: CPU usage time are expected to be within certain percentage with respect to the gather interval time. But
the gathered CPU time is outside this boundary.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the CPU statistic error.
Remedy: Contact the Global Support Center.

11981 Bad TOD value Current TOD sec = %d Current TOD usec = %d Previous TOD sec = %d Previous TOD usec = %d Elapse time = %d
Explanation: An unexpected Time Of Day value is detected.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the Bad TOD error.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 11973 to 11981 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 
1 2 3 7