SAP Error Messages and Error Codes from SAP Error 29-389 to 29-398

SQLServerF1

SAP Error: 29-389
Desc: The selected components cause recursiveness
SAP Internal Error: 9611
SAP Error: 29-390
Desc: Component causes recursiveness
SAP Internal Error: 9612
SAP Error: 29-391
Desc: Class type not supported in configurable objects
SAP Internal Error: 9613

SAP Error: 29-392
Desc: Variant class type not supported in BOMs
SAP Internal Error: 9614
SAP Error: 29-393
Desc: Material not allocated to class
SAP Internal Error: 9615
SAP Error: 29-394
Desc: Document not allocated to class
SAP Internal Error: 9616

SAP Error: 29-395
Desc: Resulting item category only supported in BOMs relevant to PM
SAP Internal Error: 9617
SAP Error: 29-396
Desc: BOM usage cannot be used with resulting item category
SAP Internal Error: 9618
SAP Error: 29-397
Desc: If the resulting item category is (variable should be entered here – variable1), PM assembly is required
SAP Internal Error: 9619
SAP Error: 29-398
Desc: No base unit of measure for BOMs defined in class
SAP Internal Error: 9620

Above are list of SAP Error codes and Error Messages and their Description including SAP Internal state and exact error code from SAP Error 29-389 to 29-398 received while performing certain operation against SAP and related products.

What are SAP Error Messages and Error Codes?

There are many different types of error messages received while using SAP Suites which include different types of errors received while performing different operations against any SAP products like Customer Relationship Management (CRM), Enterprise Resource Planning (ERP), Product Lifecycle Management (PLM), Supply Chain Management (SCM), Supplier Relationship Management (SRM). Each SAP 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 where required. The received error will include Error code, Error Message or Warning Message and Internal Error.

Hope this was helpful.

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

 

Teradata SQL Error and Failure Codes from Error 9705 To 9728

9705 A network disconnect during a LOB client-to-server transfer caused an abort.
Explanation: A session using Redrive or Recoverable Network Protocol was transferring a LOB from the client to the
database when a network disconnect occurred. The Gateway initiated an abort of the transaction.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Resubmit the request and transaction.

9721 Left-over spool(Final Response) table found : transaction aborted.
Explanation: This error occurs if a left-over spool is a Final response spool, which is used by a transaction other than the
transaction for which it was created. The transaction attempting to use this left-over spool is aborted, and diagnostic information
about the left- over spool appears on the system-console screen.
Generated By: AMP
For Whom: Site Support Representative.
Notes: Developers researching the left-over spool problem will be interested in the console-screen output produced by
the logging of this error.
Remedy: Contact your Support Representative.

9722 Attempt to access a down Table or Index contains down region
Explanation: A statement has attempted to access a table or index that has been set down. It is not currently accessible
for SQL statements.
Generated By: AMP (STP, S2S, SUT).
For Whom: End User.
Remedy: Reset the down table or index status before resubmitting the SQL statement. Some of the ways to reset the
down status are: – ALTER TABLE SQL statement – Fast path DELETE ALL/ DROP table SQL statement – Rebuild the Table
– Restore the table from backup – Drop and recreate the index

9723 Table operator error on the AMP, details: %VSTR
Explanation: This message indicates a table operator processing error on the AMP.
Generated By: AMP
For Whom: End user or Field Engineer or the concerned site support representative.
Remedy: Check the table operator source code if the problem persists contact support personnel.

9724 An AMP is down and fallback sub-table data cannot be used in %VSTR.
Explanation: The query attempted to perform an operation on fallback table data that is not supported while an AMP is
down.
Generated By: AMP (STP).
For Whom: End User.
Remedy: Bring down AMPs back online and retry query.

9725 The same user is already logged on and running other BAR jobs.
Explanation: The restore job is rejected as same user is already running other BAR jobs.
Generated By: AMP
For Whom: End User.
Remedy: Logoff the sessions where same user is running other BAR jobs.

9726 DBQL AWT DPS cache fault isolated (count %s).
Explanation: The AMP DBQL software encountered a fault while using the awtDPS cache to collect AMP usage data
(Algorithm 3 primarily). The fault was isolated to allow the step to continue. DBQL capture of AMP request and step data
is impacted and the QryLog view DBQLStatus field (DBQLogTbl) will reflect that.
Generated By: AMP Worker Task (awtdps and other modules).
For Whom: System administrator & Site support representative.
Notes: This message is logged once per AMP and if faults continue on an AMP it is logged once more no sooner than 60
minutes after the first. The count value (faults isolated for this AMP) helps identify the extent of the problem. DBS Control
parameter DBQLSnapLimit controls snapshot dumps.
Remedy: This error should be reported to the site support representative including any snapshot dump for the error.
Some DBQL AMP usage data is not being collected. When the system is restarted the awtDPS cache is created new, the
same as a normal DBS TPA start and DBQL collection is no longer impacted. If this message reoccurs, report it. DBQL
Algorithm 1 may be selected in DBS Control general 64 until the issue with Algorithm 3 is resolved. Be aware that DBQL
usage data logged varies depending on the algorithm selected.

9727 DBQL AWT DPS cache failed assertion test, %s.
Explanation: The AMP DBQL software detected a problem in the awtDPS cache used to collect AMP usage data (Algorithm
3 primarily). The failure is indicated by the variable part of the message.
Generated By: AMP Worker Task (awtdps and other modules).
For Whom: System administrator & Site support representative.
Notes: This message may be logged under the DBQL awtDPS fault isolation code.
Remedy: This error should be reported to the site support representative.

9728 Retry later as currently a load operation is in progress on the table %DBID.%TVMID.
Explanation: The LDI table is being loaded as a concurrent load isolated operation.
Generated By: AMP Modules.
For Whom: End user.
Remedy: The command must be re-issued after the load operation is completed

Above are list of Teradata Errors or Failure Codes from Error 9705 To 9728 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 9665 To 9678

9665 VPROC %d:AutoTempComp can no longer
uncompress database %s (%04X %04X). Uncompressing
will leave this database with less than %d%% (as defined by
DBSControl tunable UncompressReservedSpace) of its allocated
space available. Depending on other activities against database
%s further uncompression may occur in the future.
Explanation: TBBLC background task stops uncompressing database, if free space is lower than UncompressReserved-
Space threshold
Generated By: AMP
For Whom: End user or Field Engineer or the concerned site support representative.
Remedy: Free some space in database or adjust the DBSControl’s UncompressReservedSpace tunable to lower value

9666 DBQL AWT DPS cache overflow, %s.
Explanation: The AMP DBQL Performance Statistics (DPS) cache cannot grow above the current DBS Control
“DBQL_AWTDPS_CacheMaximum” limit. DBQL capture of AMP request and step data is impacted and the QryLog
DBQLStatus field (DBQLogTbl) will reflect that.
Generated By: AMP Worker Task (awtdps module).
For Whom: System administrator & Site support representative.
Notes: This message is only logged once per AMP, however If you increase the limit this message will occur if the new
limit is reached.
Remedy: Determine whether this condition represents an error to report to the site support representative. If the limit
should be raised to accommodate more DBQL data collection, increase the internal field
’DBQL_AWTDPS_CacheMaximum’ value in DBS Control.

9672 Fastload is not allowed on a normalized table with no primary index.
Explanation: Fastload is not allowed on a normalized NOPI table.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9673 Normalize specification was not copied.
Explanation: This is only a warning to let the user know that Normalize specification will not be copied to the table
being created. This is the case where a table name was specified in the Create Table As/Like statement with column names
defined in the Create Table clause. For example,
CREATE TABLE Table1 (field_1, field_2) Table2 WITH [NO] DATA; Normaliz specification on Table2 (if exist) will not be copied to Table1.
Generated By: Resolver.
For Whom: End User.
Remedy: The message is for information only.

9674 Multiple Normalize clauses are defined.
Explanation: Multiple Normalize clauses are defined.
Generated By: SYN module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9675 Extended MultiLoad Protocol does not allow target table in a Replication group.
Explanation: Replication is not allowed with the Extended MultiLoad Protocol.
Generated By: OPH module.
For Whom: End User.
Remedy: Do not use MultiLoad.

9676 MERGE-INTO DELETE does not allow target table in a Replication group.
Explanation: Replication is not allowed with MERGE-INTO DELETE.
Generated By: GNS module.
For Whom: End User.
Remedy: Do not submit MERGE-INTO DELETE with target table in a Replication group.

9677 BEGIN QUERY CAPTURE already in progress into %VSTR query capture database.
Explanation: There is already an active BEGIN QUERY CAPTURE session in progress on a different Query Capture
Database whose name is contained in %VSTR. BEGIN QUERY CAPTURE can be enabled only on one Query Capture Database
at a time for a user.
Generated By: parser.
For Whom: User.
Remedy: To enable BEGIN QUERY CAPTURE on the new Query Capture Database, the existing BEGIN QUERY CAPTURE
session should be ENDED. If not, the BEGIN QUERY CAPTURE session currently in progress will remain active.

9678 The UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING specification is not
supported for FIRST_VALUE/LAST_VALUE.
Explanation: The FIRST_VALUE/LAST_VALUE functions do not support the UNBOUNDED PRECEDING AND
UNBOUNDED FOLLOWING specification.
Generated By: Opt modules
For Whom: End User.
Remedy: Resubmit the request with a valid ROWS expression.

Above are list of Teradata Errors or Failure Codes from Error 9665 To 9678 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 MYSQL or MariaDB Errors from Error 1471 to 1480

SQLServerF1

MariaDB ERROR Code 1471
MySQL SQL State HY000
ER_NON_INSERTABLE_TABLE
The target table %s of the %s is not insertable-into
MariaDB ERROR Code 1472
MySQL SQL State HY000
ER_ADMIN_WRONG_MRG_TABLE
Table ‘%s’ is differently defined or of non-MyISAM type or doesn’t exist
MariaDB ERROR Code 1473
MySQL SQL State HY000
ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT
Too high level of nesting for select

MariaDB ERROR Code 1474
MySQL SQL State HY000
ER_NAME_BECOMES_EMPTY
Name ‘%s’ has become ”
MariaDB ERROR Code 1475
MySQL SQL State HY000
ER_AMBIGUOUS_FIELD_TERM
First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY
MariaDB ERROR Code 1476
MySQL SQL State HY000
ER_FOREIGN_SERVER_EXISTS
The foreign server, %s, you are trying to create already exists.

MariaDB ERROR Code 1477
MySQL SQL State HY000
ER_FOREIGN_SERVER_DOESNT_EXIST
The foreign server name you are trying to reference does not exist. Data source error: %s
MariaDB ERROR Code 1478
MySQL SQL State HY000
ER_ILLEGAL_HA_CREATE_OPTION
Table storage engine ‘%s’ does not support the create option ‘%s’
MariaDB ERROR Code 1479
MySQL SQL State HY000
ER_PARTITION_REQUIRES_VALUES_ERROR
Syntax error: %s PARTITIONING requires definition of VALUES %s for each partition
MariaDB ERROR Code 1480
MySQL SQL State HY000
ER_PARTITION_WRONG_VALUES_ERROR
Only %s PARTITIONING can use VALUES %s in partition definition

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1471 to 1480 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

MYSQL Error Messages and Failure Codes from Error 1471 to 1480

SQLServerF1

Error: 1471 SQLSTATE: HY000 (ER_NON_INSERTABLE_TABLE)
Message: The target table %s of the %s is not insertable-into
Error: 1472 SQLSTATE: HY000 (ER_ADMIN_WRONG_MRG_TABLE)
Message: Table ‘%s’ is differently defined or of non-MyISAM type or doesn’t exist
Error: 1473 SQLSTATE: HY000 (ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT)
Message: Too high level of nesting for select

Error: 1474 SQLSTATE: HY000 (ER_NAME_BECOMES_EMPTY)
Message: Name ‘%s’ has become ”
Error: 1475 SQLSTATE: HY000 (ER_AMBIGUOUS_FIELD_TERM)
Message: First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY
Error: 1476 SQLSTATE: HY000 (ER_FOREIGN_SERVER_EXISTS)
Message: The foreign server, %s, you are trying to create already exists.

Error: 1477 SQLSTATE: HY000 (ER_FOREIGN_SERVER_DOESNT_EXIST)
Message: The foreign server name you are trying to reference does not exist. Data source error: %s
Error: 1478 SQLSTATE: HY000 (ER_ILLEGAL_HA_CREATE_OPTION)
Message: Table storage engine ‘%s’ does not support the create option ‘%s’
Error: 1479 SQLSTATE: HY000 (ER_PARTITION_REQUIRES_VALUES_ERROR)
Message: Syntax error: %s PARTITIONING requires definition of VALUES %s for each partition
Error: 1480 SQLSTATE: HY000 (ER_PARTITION_WRONG_VALUES_ERROR)
Message: Only %s PARTITIONING can use VALUES %s in partition definition

Above are MYSQL Error Codes from Error 1471 to 1480 received while performing certain operation against MYSQL Database or related products.

What are MYSQL Errors?
MySQL programs have access to several types of error information when the server returns an error.

The MYSQL message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

MYSQL Error Messages and Failure Codes from Error 1261 to 1270

SQLServerF1

Error: 1261 SQLSTATE: 01000 (ER_WARN_TOO_FEW_RECORDS)
Message: Row %ld doesn’t contain data for all columns
Error: 1262 SQLSTATE: 01000 (ER_WARN_TOO_MANY_RECORDS)
Message: Row %ld was truncated; it contained more data than there were input columns
Error: 1263 SQLSTATE: 22004 (ER_WARN_NULL_TO_NOTNULL)
Message: Column set to default value; NULL supplied to NOT NULL column ‘%s’ at row %ld

Error: 1264 SQLSTATE: 22003 (ER_WARN_DATA_OUT_OF_RANGE)
Message: Out of range value for column ‘%s’ at row %ld
Error: 1265 SQLSTATE: 01000 (WARN_DATA_TRUNCATED)
Message: Data truncated for column ‘%s’ at row %ld
Error: 1266 SQLSTATE: HY000 (ER_WARN_USING_OTHER_HANDLER)
Message: Using storage engine %s for table ‘%s’

Error: 1267 SQLSTATE: HY000 (ER_CANT_AGGREGATE_2COLLATIONS)
Message: Illegal mix of collations (%s,%s) and (%s,%s) for operation ‘%s’
Error: 1268 SQLSTATE: HY000 (ER_DROP_USER)
Message: Cannot drop one or more of the requested users
Error: 1269 SQLSTATE: HY000 (ER_REVOKE_GRANTS)
Message: Can’t revoke all privileges for one or more of the requested users
Error: 1270 SQLSTATE: HY000 (ER_CANT_AGGREGATE_3COLLATIONS)
Message: Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation ‘%s’

Above are MYSQL Error Codes from Error 1261 to 1270 received while performing certain operation against MYSQL Database or related products.

What are MYSQL Errors?
MySQL programs have access to several types of error information when the server returns an error.

The MYSQL message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

SQL Server Errors or Failures from Error: 22978 to Error: 22997

SQLServerF1

 

Error: 22978, Severity: 16, Could not update the cdc.captured_columns entry for column ‘%s’ of change table ‘%s’ to reflect a data type change in the corresponding column of the source table ‘%s’. Change Data Capture column meta data for table ‘%s’ no longer accurately reflects the
Error: 22979, Severity: 16, The unique index ‘%s’ on table ‘%s’ is used by Change Data Capture. The constraint using this index cannot be dropped or disabled.
Error: 22980, Severity: 16, The unique index ‘%s’ on table ‘%s.%s’ is disabled and cannot be used as a unique index by Change Data Capture. Enable the index.
Error: 22981, Severity: 16, Object does not exist or access is denied.

Error: 22982, Severity: 16, Could not create internal stored procedures used to populate the change table for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
Error: 22983, Severity: 16, The unique index ‘%s’ on source table ‘%s’ is used by Change Data Capture. To alter or drop the index, you must first disable Change Data Capture on the table.

Error: 22984, Severity: 16, An error occurred while waiting on the log reader history cache event. This error is reported by the internal task scheduling and might be transient. Retry the operation.
Error: 22985, Severity: 16, Change data capture has not been enabled for source table ‘%s.%s’. Specify the name of a table enabled for Change Data Capture. To report on the tables enabled for Change Data Capture, query the is_tracked_by_cdc column in the sys.tables catalog view.
Error: 22986, Severity: 16, Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming
Error: 22987, Severity: 16, Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if
Error: 22988, Severity: 16, This instance of SQL Server is the %s. Change data capture is only available in the Enterprise, Developer, and Enterprise Evaluation editions.
Error: 22989, Severity: 16, Could not enable Change Data Capture for database ‘%s’. Change data capture is not supported on system databases, or on a distribution database.
Error: 22990, Severity: 16, The value specified for the parameter @pollinginterval cannot exceed 24 hours or be less than 0. Specify a polling interval (in seconds) that is less than or equal to 24 hours (86,400 seconds).
Error: 22991, Severity: 16, The value specified for the parameter @maxtrans must be greater than 0.
Error: 22992, Severity: 16, The specified @job_type, %s, is not supported. The value specified for the parameter @job_type must be N’capture’ to indicate a capture job, or N’cleanup’ to indicate a cleanup job.
Error: 22993, Severity: 16, The Change Data Capture job table containing job information for database ‘%s’ cannot be found in the msdb system database. Run the stored procedure ‘sys.sp_cdc_add_job’ to create the appropriate CDC capture or cleanup job. The stored procedure will creat
Error: 22994, Severity: 16, The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to 52594800. When creating or modifying the cleanup job, specify a retention value (in minutes) that is within that range. If this erro
Error: 22995, Severity: 16, A value for the parameter @retention cannot be specified when the job type is ‘capture’. Specify NULL for the parameter, or omit the parameter from the statement.
Error: 22996, Severity: 16, When adding or modifying the CDC cleanup job, @pollinginterval, @maxtrans, @maxscans, and @continuous may not be assigned non-null values.
Error: 22997, Severity: 16, The Change Data Capture ‘%s’ job does not exist in the system table ‘msdb.dbo.cdc_jobs’. Use the stored procedure ‘sys.sp_cdc_add_job’ to add the Change Data Capture job.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 
1 2