Oracle Database Errors or Warnings from Error ORA-37071 to ORA-37080

SQLServerF1

ORA-37071: You may not execute a parallel OLAP operation against updated but uncommitted AW string.
Cause: The user attempted to use a parallel feature against an AW which they updated but which has not been committed
Action: Commit the current changes
ORA-37072: (XSMCSESS00) Object workspace object has the wrong type.
Cause: The object is not of the object type specified in the APPLY clause
Action: Specify the correct object type
ORA-37073: (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
Cause: Applied relation has the different dimension from the dimension currently being maintained
Action: Maintain relation dimension

ORA-37074: (XSMCSESS02) Variable workspace object has no default aggmap.
Cause: The applied variable has no default aggmap
Action: Use variable with the default aggmap or aggmap directly
ORA-37075: (XSMCSESS03) You cannot rename a session-only dimension value.
Cause: The user tried to apply MAINTAIN RENAME to a SESSION value.
Action: Delete the old value and add a new one with the desired name.
ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
Cause: The user tried to add a SESSION value to a dimension type that does not support SESSION values.
Action: Use a dimension of one of the listed types.

ORA-37077: (XSMCSESS05) Object workspace object is specified more than once.
Cause: The same object name was given more than once in the apply clause or in the step dimension list.
Action: Remove the repetitions.
ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension.
Cause: The dimension being maintained was named as a step dimension.
Action: Remove this dimension from the list of step dimensions.
ORA-37079: (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
Cause: The current aggmap may be for ALLOCATE
Action: Choose the correct aggmap for AGGREGATE only.
ORA-37080: Advice requested for hierarchy with too many levels
Cause: A request was made for advice on a hierarchy with more levels than are supported.
Action: Only request advice for hierarchies with less than 32 levels.

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

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase 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-33911 to ORA-34061

SQLServerF1

ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
Cause: User attempted to define an object that requires a certain compatibility setting in an AW that has not been upgraded to that compatibility level.
Action: Make sure that the database is running in the appropriate compatibility mode, and upgrade the AW.
ORA-33918: (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
Cause: Not all kinds of dimensions can have surrogates. The user attempted to define a surrogate of a prohibited kind of dimension.
Action: Do not attempt to define a surrogate on this dimension.
ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP, or INTEGER.
Cause: The user attempted to define a surrogate without specifying a valid data type.
Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the definition of the surrogate.
ORA-33922: (MAKEDCL35) You cannot define a surrogate of dimension workspace object because it is a time dimension.
Cause: The user attempted to define a surrogate on a dimension that has type DAY, WEEK, MONTH, or YEAR.
Action: Do not attempt to define a surrogate on this dimension.

ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
Cause: The user attempted to include both a dimension and its surrogate in the DIMENSION statement of a model.
Action: Use either the dimension or the surrogate in the DIMENSION statement of the model, but not both.
ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.
Cause: The user attempted to include two dimension surrogates of the same dimension in the DIMENSION statement of a model.
Action: Use either of the two surrogates in the DIMENSION statement of the model, but not both.
ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
Cause: Either two concat dimensions which share a common leaf dimension, or a concat and one of its leaves where both specified in the DIMENSION statement(s).
Action: Do not specify overlapping concat dimensions, or any leaves of specified concat dimensions.

ORA-34019: (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.
Cause: User attempted to MAINTAINT ADD or DELETE a list value from a RANGE or CONCAT partition template.
Action: Partitioning in a RANGE or CONCAT partition template cannot be changed using the MAINTAIN command.
ORA-34021: (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
Cause: User attempted to MAINTAINT ADD or DELETE a list value from a LIST partition template, but didn’t specify which partition to add to or delete from.
Action: Specify the partition: maintain (template) add to partition (partitionname) (values) or maintain (template) delete from partition (partitionname) (values)
ORA-34059: (MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension workspace object.
Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value.
Action: Only use MAINTAIN DELETE to remove SESSION values from a concat dimension.
ORA-34061: (MSEXECUT11) Session-only values cannot be added to non-unique concat dimension workspace object, or any of its base dimensions.
Cause: Only UNIQUE concat dimensions can have custom member values.
Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.

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

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase 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.

 

SQL Server Errors or Failures from Error: 22511 to Error: 22530

SQLServerF1

 

Error: 22511, Severity: 16, The merge completed successfully.
Error: 22512, Severity: 16, Cannot use partition groups with unfiltered publications. Set “use_partition_groups” to “false” using sp_changemergepublication.
Error: 22513, Severity: 16, Cannot use partition groups because the join filter between the following articles contains one or more functions: “%s” and “%s”.
Error: 22514, Severity: 16, Cannot use partition groups because one or more filters reference the following view, which contains functions: “%s”.

Error: 22515, Severity: 16, The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in the publication. To use precomputed partitions, ensure that no circular join filter relationships exist.
Error: 22516, Severity: 16, The publication “%s” was defined as having dynamic filters, but it does not contain any dynamic filters.
Error: 22517, Severity: 16, The publication was defined as having no dynamic filters, but contains one or more dynamic filters.

Error: 22518, Severity: 16, Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: ‘%s’.
Error: 22519, Severity: 16, Cannot add a logical record relationship between tables “%s” and “%s” because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max) column was referenced in the join clause.
Error: 22520, Severity: 10, A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for details.
Error: 22521, Severity: 10, Unable to synchronize the row because the row was updated by a different process outside of replication.
Error: 22522, Severity: 16, Article ‘%s’ cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options parameter of sp_addmergearticle (nonoverlapping partitions with a single subscription per partition) cannot
Error: 22523, Severity: 16, An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check article “%s”.
Error: 22524, Severity: 16, Article ‘%s’ is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. The specified value must be the same in all merge publications. Either specify the same value as the exist
Error: 22525, Severity: 16, The publication “%s” cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3.
Error: 22526, Severity: 16, An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions per partition), and 3 (nonoverlapping partitions with single subscription per partition).
Error: 22527, Severity: 16, Invalid value specified for %s. Valid values are ‘day’, ‘days’, ‘dd’, ‘year’, ‘years’, ‘yy’, ‘yyyy’, ‘month’, ‘months’, ‘mm’, ‘week’, ‘weeks’, ‘wk’, ‘hour’, ‘hours’, ‘hh’, ‘minute’, ‘minutes’, ‘mi’.
Error: 22528, Severity: 16, Cannot use a retention period unit other than “days” for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
Error: 22529, Severity: 16, Cannot change the retention period unit for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
Error: 22530, Severity: 16, Cannot update any column in article “%s” that is used in a logical record relationship clause.

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: 16915 to Error: 16941

SQLServerF1

 

Error: 16915, Severity: 16, A cursor with the name ‘%.*ls’ already exists.
Error: 16916, Severity: 16, A cursor with the name ‘%.*ls’ does not exist.
Error: 16917, Severity: 16, Cursor is not open.
Error: 16922, Severity: 16, Cursor Fetch: Implicit conversion from data type %s to %s is not allowed.
Error: 16924, Severity: 16, Cursorfetch: The number of variables declared in the INTO list must match that of selected columns.
Error: 16925, Severity: 16, The fetch type %hs cannot be used with dynamic cursors.

Error: 16926, Severity: 16, sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column.
Error: 16927, Severity: 16, Cannot fetch into text, ntext, and image variables.
Error: 16928, Severity: 16, sp_cursor: Exec statement is not allowed as source for cursor insert.
Error: 16929, Severity: 16, The cursor is READ ONLY.
Error: 16930, Severity: 16, The requested row is not in the fetch buffer.
Error: 16931, Severity: 16, There are no rows in the current fetch buffer.
Error: 16932, Severity: 16, The cursor has a FOR UPDATE list and the requested column to be updated is not in this list.

Error: 16933, Severity: 16, The cursor does not include the table being modified or the table is not updatable through the cursor.
Error: 16934, Severity: 10, Optimistic concurrency check failed. The row was modified outside of this cursor.
Error: 16935, Severity: 16, No parameter values were specified for the sp_cursor-%hs statement.
Error: 16936, Severity: 16, sp_cursor: One or more values parameters were invalid.
Error: 16937, Severity: 16, A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
Error: 16938, Severity: 16, sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMPUTE BY, or variable assignments.
Error: 16941, Severity: 16, Cursor updates are not allowed on tables opened with the NOLOCK option.

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: 11038 to Error: 11108

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 11038 to Error: 11108

Error: 11038, Severity: 16,
The row is a pending insert row.

Error: 11039, Severity: 16,
DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source.

Error: 11040, Severity: 16,
Deleting the row violated the integrity constraints for the column or table.

Error: 11041, Severity: 16,
The row handle was invalid or was a row handle to which the current thread does not have access rights.

Error: 11042, Severity: 16,
Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS.

Error: 11043, Severity: 16,
The row has a storage object open.

Error: 11044, Severity: 16,
The provider ran out of memory and could not fetch the row.

Error: 11045, Severity: 16,
User did not have sufficient permission to delete the row.

Error: 11046, Severity: 16,
The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out.

Error: 11047, Severity: 16,
Updating did not meet the schema requirements.

Error: 11048, Severity: 16,
There was a recoverable, provider-specific error, such as an RPC failure.

Error: 11100, Severity: 16,
The provider indicates that conflicts occurred with other properties or requirements.

Error: 11101, Severity: 16,
Could not obtain an interface required for text, ntext, or image access.

Error: 11102, Severity: 16,
The provider could not support a required row lookup interface.

Error: 11103, Severity: 16,
The provider could not support an interface required for the UPDATE/DELETE/INSERT statements.

Error: 11104, Severity: 16,
The provider could not support insertion on this table.

Error: 11105, Severity: 16,
The provider could not support updates on this table.

Error: 11106, Severity: 16,
The provider could not support deletion on this table.

Error: 11107, Severity: 16,
The provider could not support a row lookup position.

Error: 11108, Severity: 16,
The provider could not support a required property.

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: 8391 to Error: 8413

SQLServerF1

 

Error: 8391, Severity: 10, The usage of 2-part names in DROP INDEX is deprecated. New-style syntax DROP INDEX ON { | }
Error: 8393, Severity: 10, The ability to not specify a column name when the datatype is timestamp will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
Error: 8394, Severity: 10, Usage of deprecated index option syntax. The deprecated relational index option syntax structure will be removed in a future version of SQL Server. Avoid using this syntax structure in new development work, and plan to modify applications that currently u

Error: 8396, Severity: 10, %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use %ls instead.
Error: 8397, Severity: 10, The TEXT, NTEXT, and IMAGE data types will be removed in a future version of SQL Server. Avoid using them in new development work, and plan to modify applications that currently use them. Use the varchar(max), nvarchar(max), and varbinary(max) data types
Error: 8398, Severity: 10, The use of more than two-part column names will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
Error: 8399, Severity: 10, %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.

Error: 8401, Severity: 16, This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue ‘%.*ls’.
Error: 8402, Severity: 16, The data type of the ‘%S_MSG’ in the ‘%S_MSG’ statement must be %s. The %s data type is not allowed.
Error: 8403, Severity: 16, The message type ‘%.*ls’ is specified more than once. Remove the duplicate message type.
Error: 8404, Severity: 16, The service contract ‘%.*ls’ is specified more than once. Remove the duplicate service contract.
Error: 8405, Severity: 16, An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State: %i.
Error: 8406, Severity: 16, The dialog lifetime can not be NULL. Specify a valid dialog lifetime value from %d to %d.
Error: 8407, Severity: 16, Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Service Broker endpoint.
Error: 8408, Severity: 16, Target service ‘%.*ls’ does not support contract ‘%.*ls’.
Error: 8409, Severity: 16, This message could not be delivered because the targeted service does not support the service contract. Targeted service: ‘%.*ls’, service contract: ‘%.*ls’.
Error: 8410, Severity: 16, The conversation timer cannot be set beyond the conversation’s lifetime.
Error: 8411, Severity: 16, The dialog lifetime value of %d is outside the allowable range of %d to %d. Specify a valid dialog lifetime value.
Error: 8412, Severity: 16, The syntax of the service name ‘%.*ls’ is invalid.
Error: 8413, Severity: 16, The syntax of the broker instance ‘%.*ls’ is invalid. The specified broker instance is too long, the maximum size is 256 bytes.

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: 7122 to Error: 7214

SQLServerF1

 

Error: 7122, Severity: 16, Invalid text, ntext, or image pointer type. Must be binary(16).
Error: 7123, Severity: 16, Invalid text, ntext, or image pointer value %hs.
Error: 7124, Severity: 16, The offset and length specified in the READTEXT statement is greater than the actual data length of %ld.
Error: 7125, Severity: 16, The text, ntext, or image pointer value conflicts with the column name specified.
Error: 7133, Severity: 16, NULL textptr (text, ntext, or image pointer) passed to %ls function.
Error: 7134, Severity: 16, LOB Locator is not supported as text pointer when using UPDATETEXT/WRITETEXT to update/write a text column.

Error: 7135, Severity: 16, Deletion length %ld is not in the range of available text, ntext, or image data.
Error: 7137, Severity: 16, %s is not allowed because the column is being processed by a concurrent snapshot or is being replicated to a non-SQL Server Subscriber or Published in a publication allowing Data Transformation Services (DTS) or tracked by Change Data Capture.
Error: 7138, Severity: 16, The WRITETEXT statement is not allowed because the column is being replicated with Data Transformation Services (DTS) or tracked by Change Data Capture.
Error: 7139, Severity: 16, Length of LOB data (%I64d) to be replicated exceeds configured maximum %ld. Use the stored procedure sp_configure to increase the configured maximum value for max text repl size option, which defaults to 65536. A configured value of -1 indicates no limit,

Error: 7140, Severity: 16, Cannot create additional orphans with the stored procedure sp_createorphan. Free up some of the orphan handles that you have created by inserting or deleting them.
Error: 7141, Severity: 16, Must create orphaned text inside a user transaction.
Error: 7143, Severity: 16, Invalid locator de-referenced.
Error: 7144, Severity: 16, A text/ntext/image column referenced by a persisted or indexed computed column cannot be updated
Error: 7151, Severity: 16, Insufficient buffer space to perform write operation.
Error: 7201, Severity: 17, Could not execute procedure on remote server ‘%.*ls’ because SQL Server is not configured for remote access. Ask your system administrator to reconfigure SQL Server to allow remote access.
Error: 7202, Severity: 11, Could not find server ‘%.*ls’ in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.
Error: 7212, Severity: 16, Could not execute procedure ‘%.*ls’ on remote server ‘%.*ls’.
Error: 7213, Severity: 20, The attempt by the provider to pass remote stored procedure parameters to remote server ‘%.*ls’ failed. Verify that the number of parameters, the order, and the values passed are correct.
Error: 7214, Severity: 16, Remote procedure time out of %d seconds exceeded. Remote procedure ‘%.*ls’ is canceled.

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