Oracle Database Errors or Warnings from Error ORA-30493 to ORA-30508

SQLServerF1

ORA-30493: The percentile value should be a number between 0 and 1.
Cause: A percentile value for PERCENTILE_CONT or PERCENTILE_DISC function is specified out of range.
Action: Specify a value from [0,1].
ORA-30500: database open triggers and server error triggers cannot have BEFORE type
Cause: An attempt was made to create a trigger that fires before the database is open or before server errors, but these types of triggers are not supported.
Action: Do not attempt to create a trigger that fires before the database is open or before server errors.
ORA-30501: instance shutdown triggers cannot have AFTER type
Cause: An attempt was made to create a trigger that fires after an instance shutdown, but this type of trigger is not supported.
Action: Do not attempt to create a trigger that fires after an instance shutdown.

ORA-30502: system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
Cause: An attempt was made to create a system trigger with INSERT, UPDATE, or DELETE triggering events, but this type of trigger is not supported because a system trigger does not have a base table.
Action: Do not attempt to create a system trigger with INSERT, UPDATE, or DELETE triggering events.
ORA-30503: system triggers cannot have a REFERENCING clause
Cause: An attempt was made to use a REFERENCING clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.
Action: Do not use a REFERENCING clause with a system trigger.
ORA-30504: system triggers cannot have a FOR EACH ROW clause
Cause: An attempt was made to use a FOR EACH ROW clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.
Action: Do not use a FOR EACH ROW clause with a system trigger.

ORA-30505: system triggers should not reference a column in a WHEN clause
Cause: An attempt was made to use a WHEN clause to reference a column with a system trigger, but this type of trigger is not supported because a system trigger does not have a base table.
Action: Change the WHEN clause to an appropriate clause.
ORA-30506: system triggers cannot be based on tables or views
Cause: An attempt was made to base a system trigger on a table or a view.
Action: Make sure the type of the trigger is compatible with the base object.
ORA-30507: normal triggers cannot be based on a schema or a database
Cause: An attempt was made to base a normal trigger on a schema or a database, but normal triggers can be based only on tables or views.
Action: Make sure the type of the trigger is compatible with the base object.
ORA-30508: client logon triggers cannot have BEFORE type
Cause: An attempt was made to create a trigger that fires before logon. This type of trigger is not supported.
Action: Do not attempt to create a trigger that fires before logon.

Above are list of Oracle Database Errors or Warnings from Error ORA-30493 to ORA-30508 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.

 

Informix Error Messages and Error Codes From Error 2940 to 2953

SQLServerF1

Informix Error Code -2944 You may apply the after add, update, query, or remove commands to a table only — not a column.
The operations of Add, Update, Remove, and Query all apply to whole rows. Consequently, these control blocks must list only table names, not names of individual columns, in their opening command. Review the names in this statement, and change column names to the names of their tables.
Informix Error Code -2945 You may apply the after add, update, query, or remove commands to a table only — not a column.
Aggregates (AVG, MIN, MAX, COUNT, TOTAL) can only be performed on fields that are associated with tables (not on DISPLAYONLY fields), and the tables must be listed in the opening command of the same control block. Revise the form specification, and recompile.

Informix Error Code -2946 You may not calculate an aggregate on the display-only field name.
Aggregates can only be performed on fields that are associated with tables (not on DISPLAYONLY fields), and the tables must be listed in the opening command of the same control block. Revise the form specification, and recompile.
Informix Error Code -2950 The column name has no section which starts at 1. Remember that the first subscript is one, not zero.
Multiple substrings from the same column are assigned to display fields. However, the substrings do not cover adjacent, nonoverlapping portions of the column. Either there is no first section (starting from column 1), or one section overlaps another. Review the substrings that are specified. Consider using a multiline edit field instead of a group of substrings; it is simpler to code and provides better editing for data entry.

Informix Error Code -2951 The left and right delimiters must be specified in a two character string.
The DELIMITERS instructions require a string of exactly two characters, the left and right delimiter (marker) characters to be used when displaying fields. The characters can be the same, but there must be two of them.
Informix Error Code -2952 In order to use a picture, the picture length must be the same as the display field length.
The string that is specified with the PICTURE attribute must have exactly the same length as the field as depicted in the SCREEN section. Review the definition of this field, and make the two lengths agree.
Informix Error Code -2953 The name name is not a database column in this form.
All the columns that are named in a COMPOSITES list must be defined in the ATTRIBUTES section. Check the spelling of all the names, and make sure that they have been defined.

Above are list of Informix Error Messages and Errors Codes or Status Codes or Exit Codes along with Error and Warning messages received while performing certain operation against Informix applications or related products.

What are Informix Error Messages?
All Informix messages returned by the Informix server are assigned an error code.

In general, each Informix error contains the following information:
• The Informix Error Code or Informix Error status
• The message text. This text is usually returned with the Error code. 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.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informix Error Codes or Status Codes or Exit Codes and Error Messages on Windows, Linux Operating Systems.

 

Teradata SQL Error and Failure Codes from Error 3823 To 3834

3823 VIEW ’%VSTR’ may not be used for Help Index/Constraint/Statistics, Update, Delete or Insert.
Explanation: The view specified can only be used for retrievals. The user cannot use this view for INSERT, UPDATE, or
DELETE statements, nor can the user ask for index/statictics/constraint information on a view that is not on a single table.
Generated By: RES modules.
For Whom: End User.
Notes: A view that contains any expressions, joins, or aggregates cannot be used for manipulating the data in the underlying
table. The HELP INDEX, HELP STATISTICS, HELP CONSTRAINT statements will also not work on such views.
Remedy: Redefine the view or do not use a view.

3824 Macro ’%VSTR’ does not exist.
Explanation: The macro specified does not exist in the specified database(s).
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Check the spelling of the macro name; make sure that the correct database is specified.

3825 Incomplete table.
Explanation: A failed restore probably left a DBC table incomplete. An attempt was made to access the incomplete table
using a secondary index but nothing was found where there was supposed to be something. At the moment, a bad restore
is the only thing known to cause this error.
Generated By: RES modules.
For Whom: End User.
Remedy: Do a good restore .

3826 A 2PC parcel is only valid when in a 2PC session.
Explanation: A user issued a 2PC parcel while not in 2PC mode. A session must be logged on as a 2PC session.
Generated By: ParDrivr.
For Whom: End User.
Remedy: Logon a 2PC session and retry the request(s).

3827 A 2PC Vote, Commit, or Vote & Terminate was received while in an inner transaction.
Explanation: A user issued a 2PC parcel while in an inner transaction. VOTE, COMMIT and VOTE/TERMINATE
requests are only valid when no user generated transaction exists.
Generated By: ParDrivr and GncApply.
For Whom: End User.
Remedy: Re-execute the requests with properly matched BEGIN and END TRANSACTION statements.

3828 A commit is valid for in-doubt transactions only.
Explanation: A user issued a commit for a transaction that was not in-doubt. An in-doubt transaction results from a
VOTE request. This failure caused the transaction to be rolled back.
Generated By: ParDrivr.
For Whom: End User.
Remedy: Re-execute all the requests, except the commit, then issue a vote followed by a commit.

3829 DDL is not allowed in a 2PC session.
Explanation: Data Definition Language statements are not allowed in 2PC sessions.
Generated By: Resolver.
For Whom: End User.
Remedy: Execute the request without DDL statements.

3831 A 2PC parcel must be in a 2PC transaction.
Explanation: A 2PC parcel was received before the Parser received an SQL request.
Generated By: ParDrivr.
For Whom: End User.
Remedy: Issue the 2PC parcel after executing an SQL request.

3832 A 2PC parcel must not directly follow an Options parcel.
Explanation: A 2PC parcel was sent after an Options parcel. Options parcels must be followed by a non-2PC parcel.
Generated By: ParDrivr.
For Whom: End User.
Remedy: Parcels must be issued in proper sequence.

3833 A CHECKPOINT statement is not allowed in a 2PC session.
Explanation: CHECKPOINTS are not allowed in 2PC.
Generated By: Resolver.
For Whom: End User.
Remedy: Resubmit the request without using a CHECKPOINT statement.

3834 The session has an in-doubt transaction, which must be resolved before new requests can be submitted.
Explanation: This error is issued following a DBS reset when the session has an in-doubt transaction and the user or
application submitted a new request.
The transaction may be in-doubt because it updates a replicated table. Normally, such a transaction is eventually resolved automatically, but resolution may be delayed if the replication transport provider does not respond quickly enough.
Generated By: ParDrivr.
For Whom: End User.
Remedy: The application can proceed once the in-doubt transaction has been resolved. It may have to re-execute the indoubt transaction or use some other technique to determine its outcome before proceeding on to new work.

Above are list of Teradata Errors or Failure Codes from Error 3823 To 3834 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 Informatica Error Messages and Resolution – Part 180

JMS_3008Cannot create JMS message object: <error message>.
Cause:Internal error.
or
Cause:Out of memory error.
Action:Check the additional error message for more information.
or
Action:Contact Informatica Technical Support.
JMS_3009Cannot create message writer: <error message>.
Cause:Internal error.
or
Cause:Out of memory error.
Action:Check the additional error message for more information.
or
Action:Contact Informatica Technical Support.

JMS_3013Cannot create a message object because an invalid message type is given.
Cause:Internal error.
Action:Contact Informatica Technical Support.
JMS_3014The field <field name> is not a valid JMS target field.
Cause:The repository may contain inconsistencies.
Action:Contact Informatica Technical Support.
JMS_3015An invalid row type was encountered. JMS writer will publish a message if the row type is INSERT, UPDATE, and DELETE only.
Cause:The row type for the source rows is Data Driven, but must be Insert, Update, or Delete.
Action:From the Properties tab in the session properties, set the value for the Treat Source Rows As property to Insert, Update, or Delete.

JMS_3016JMS writer encountered an unknown row type error.
Cause:Your repository may contain inconsistencies.
Action:Contact Informatica Technical Support.
JMS_3017The value provided for <property name> in the JMS connection <connection name> is invalid. Reason: <error message>.
Cause:The value for the specified property is not valid.
Action:Provide a valid value for the property in the session properties.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

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

 

DB2 SQL Errors Codes and Error Messages and Warnings from Error -150 to -152

SQLServerF1

Error: DB2 SQL Error: SQLCODE=-150, SQLSTATE=42807, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE OBJECT OF THE INSERT,
DELETE, UPDATE, MERGE, OR
TRUNCATE STATEMENT IS A VIEW,
SYSTEM-MAINTAINED
MATERIALIZED QUERY TABLE, OR
TRANSITION TABLE FOR WHICH
THE REQUESTED OPERATION IS
NOT PERMITTED
Explanation: One of the following occurred:
v A transition table was named in an INSERT,
UPDATE, DELETE, MERGE, or TRUNCATE
statement in a triggered action. Transition tables are
read-only.
v The view named in the INSERT, UPDATE, DELETE,
MERGE, or TRUNCATE statement is defined in such
a way that the requested insert, update, delete, or
truncate operation cannot be performed upon it.
Inserts into a view are prohibited if:
– The view definition contains a join, a GROUP BY,
or a HAVING clause.
– The SELECT clause in the view definition contains
the DISTINCT qualifier, an arithmetic expression,
a string expression, a built-in function, or a
constant.
– Two or more columns of the view are derived
from the same column.
– A base table of the view contains a column that
does not have a default value and is not included
in the view.
Updates to a view are prohibited if:
– The view definition contains a join, a GROUP BY,
or a HAVING clause.
– The SELECT clause in the view definition contains
the DISTINCT qualifier or a built-in function.
Also, a given column in a view cannot be updated
(that is, the values in that column cannot be
updated) if the column is derived from an arithmetic
expression, a constant, a column that is part of the
key of a partitioned index, or a column of a catalog
table that cannot be updated.
Deletes against a view are prohibited if:
– The view definition contains a join, a GROUP BY,
or a HAVING clause.
– The SELECT clause in the view definition contains
the DISTINCT qualifier or a built-in function.
Truncates against a view are always prohibited.
v An auxiliary table or an XML table was named in a
TRUNCATE statement.
System action: The statement cannot be executed. No
data was inserted, updated, deleted, merged, or
truncated.
User response: The requested function cannot be
performed on the view. Refer to chapter 2 of SQL
Reference for further information regarding inserting,
deleting, updating, and truncating views.
If the error occurred on a CREATE TRIGGER
statement, remove the INSERT, UPDATE, MERGE, or
DELETE reference to the transition table.
SQLSTATE: 42807

Error: DB2 SQL Error: SQLCODE=-151, SQLSTATE=42808, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE UPDATE OPERATION IS
INVALID BECAUSE THE CATALOG
DESCRIPTION OF COLUMN
column-name INDICATES THAT IT
CANNOT BE UPDATED
Explanation: The requested function is not supported
by DB2.
column-name
The name of the column that could not be
updated.
The specified column cannot be updated for one of the
following reasons:
v The values for columns occurring in the partitioning
key of a partitioned table cannot be updated.
v The object table is a view and the specified column is
defined (in the definition of the view) in such a way
that it cannot be updated.
v The object table is a catalog table with no columns
that can be updated.
v The object column is a ROWID column.
v The object column is defined with the AS ROW
CHANGE TIMESTAMP and GENERATED ALWAYS
attributes.
v The specified column of catalog tables cannot be
updated because the column itself is not updatable.
Individual columns in a view cannot be updated for
one of the following reasons:
v The column is derived from an SQL function, an
arithmetic expression, or a constant.
v The column is defined for a column of an underlying
view that cannot be updated.
v The column is defined for a read-only view.
v The column is defined for a column that is in the
partitioning key of a partitioned table.
System action: The statement was not executed. No
data was updated in the object table or view.
Programmer response: Refer to the description of the
UPDATE statement in SQL Reference for information
about restrictions on the ability to update ROWID
columns, identity columns, row change timestamp
columns, and columns in partitioned tables and views.
SQLSTATE: 42808

Error: DB2 SQL Error: SQLCODE=-152, SQLSTATE=42809, SQLERRMC=TBSPACEID=, TABLEID=, COLNO=, DRIVER=
THE DROP clause CLAUSE IN THE
ALTER STATEMENT IS INVALID
BECAUSE constraint-name IS A
constraint-type
Explanation: The DROP clause of an ALTER TABLE
statement tried to drop a constraint that does not match
the constraint-type in the DROP clause. clause must
identify an appropriate constraint-type as follows:
REFERENTIAL CONSTRAINT
The identified constraint must be a referential
constraint.
CHECK CONSTRAINT
The identified constraint must be a check
constraint.
PRIMARY KEY CONSTRAINT
The identified constraint must be a primary
key constraint.
UNIQUE KEY CONSTRAINT
The identified constraint must be a unique key
constraint.
System action: The ALTER TABLE DROP statement
cannot be executed. No object was dropped.
Programmer response: Drop the existing object with
the correct DROP clause of the ALTER TABLE
statement.
SQLSTATE: 42809

Above are list of DB2 SQL Errors and Warnings from Error -150 to -152 received while performing certain operation against DB2 Database or related products.

SQLCODE – Regardless of whether the application program provides an SQLCA or a stand-alone variable, SQLCODE is set by DB2 after each SQL statement is
executed. DB2 conforms to the ISO/ANSI SQL standard as follows:
If SQLCODE = 0, execution was successful.
If SQLCODE > 0, execution was successful with a warning.
If SQLCODE < 0, execution was not successful.
SQLCODE = 100, “no data” was found. For example, a FETCH statement returned no data because the cursor was positioned after the last row of the result table.

SQLSTATE – SQLSTATE is also set by DB2 after the execution of each SQL statement. Thus, application programs can check the execution of SQL statements by testing SQLSTATE instead of SQLCODE.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about DB2 SQL Error Codes and Error Messages on Windows, Linux and Z/OS Operating Systems.

 

SQL Server Errors or Failures from Error: 33419 to Error: 33439

SQLServerF1

Error: 33419, Severity: 16, Function %ls is only valid on the varbinary(max) FILESTREAM column in a FileTable.

Error: 33420, Severity: 16, Unable to process object ‘%.*s’ because it is a three-part or four-part name. Specifying the server or database is not supported in the object identifer.
Error: 33421, Severity: 16, The object name ‘%.*s’ is not a valid FileTable object.
Error: 33422, Severity: 16, The column ‘%.*s’ cannot be added to table ‘%.*s’ as it is a FileTable. Adding columns to the fixed schema of a FileTable object is not permitted.
Error: 33423, Severity: 16, Invalid FileTable path name or format.
Error: 33424, Severity: 16, Invalid computer host name in the FileTable path.

Error: 33425, Severity: 16, Invalid share name in the FileTable path.
Error: 33426, Severity: 16, INSERT, UPDATE, DELETE, or MERGE to FileTable ‘%.*ls’ is not allowed inside a trigger on a FileTable.
Error: 33427, Severity: 16, Function %ls is not allowed on the deleted table inside a trigger.
Error: 33428, Severity: 14, User does not have permission to kill non-transacted FILESTREAM handles in database ID %d.
Error: 33429, Severity: 16, The non-transacted FILESTREAM handle %d does not exist.
Error: 33430, Severity: 10, Killed %d non-transactional FILESTREAM handles from database ID %d.
Error: 33431, Severity: 16, An invalid path locator caused a FileTable check constraint error. The path locator has a length of %d, which is longer than the limit of %d allowed for depth %d. Reduce the length of the path locator.
Error: 33433, Severity: 10, Unable to perform the Filetable lost update recovery for database id %d.

Error: 33434, Severity: 16, The current state of the database ‘%.*s’ is not compatible with the specified FILESTREAM non-transacted access level. The database may be read only, single user or set to emergency state.
Error: 33435, Severity: 16, Cannot publish the FileTable ‘%ls’ for replication. Replication is not supported for FileTable objects.
Error: 33436, Severity: 16, Cannot enable Change Data Capture on the FileTable ‘%ls’. Change Data Capture is not supported for FileTable objects.
Error: 33437, Severity: 16, Cannot publish the logbased view ‘%ls’ for replication. Replication is not supported for logbased views that depend on FileTable objects.
Error: 33438, Severity: 16, Cannot enable Change Tracking on the FileTable ‘%.*ls’. Change Tracking is not supported for FileTable objects.
Error: 33439, Severity: 16, Cannot use IGNORE_CONSTRAINTS hint when inserting into FileTable ‘%.*ls’, unless FILETABLE_NAMESPACE is disabled.

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.

 

SQL Server Errors or Failures from Error: 20051 to Error: 20070

SQLServerF1

 

Error: 20051, Severity: 16, The Subscriber is not registered.
Error: 20052, Severity: 16, The @metatype parameter value must be null, 1, 2, 5, or 6.
Error: 20053, Severity: 16, An article with a different %s value already exists for object ‘%s’.
Error: 20054, Severity: 16, Current database is not enabled for publishing.
Error: 20055, Severity: 16, Table ‘%s’ cannot be published for merge replication because it has a timestamp column.
Error: 20056, Severity: 16, Table ‘%s’ cannot be republished.

Error: 20057, Severity: 16, The profile name ‘%s’ already exists for the specified agent type.
Error: 20058, Severity: 16, The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribution), or 4 (Merge)
Error: 20059, Severity: 16, The @profile_type must be 0 (System) or 1 (Custom)
Error: 20060, Severity: 16, Compatibility level cannot be smaller than 60.
Error: 20061, Severity: 16, The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing.

Error: 20062, Severity: 16, Updating columns with the rowguidcol property is not allowed.
Error: 20063, Severity: 16, Table ‘%s’ into which you are trying to insert, update, or delete data has been marked as read-only. Only the merge process can perform these operations.
Error: 20064, Severity: 16, Cannot drop profile. Either it is not defined or it is defined as the default profile.
Error: 20065, Severity: 16, Cannot drop profile because it is in use.
Error: 20066, Severity: 16, Profile not defined.
Error: 20067, Severity: 16, The parameter name ‘%s’ already exists for the specified profile.
Error: 20068, Severity: 16, The article cannot be created on table ‘%s’ because it has more than %d columns.
Error: 20069, Severity: 16, Cannot validate a merge article that uses looping join filters.
Error: 20070, Severity: 16, Cannot update subscription row.

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