Oracle Database Errors or Warnings from Error ORA-19034 to ORA-19043

SQLServerF1

ORA-19034: Type not supported during schema generation
Cause: The object type contained a type that is not supported for schema generation.
Action: Use a different type or do not generate a schema.
ORA-19035: Invalid select item of the query in newContextFromHierarchy()
Cause: The query does not have a number select item followed by an XMLType select item only.
Action: Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be XMLType.
ORA-19036: Invalid query result set in newContextFromHierarchy()
Cause: The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query.
Action: Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query.

ORA-19037: XMLType result can not be a fragment
Cause: The select item of the query in newContextFromHierarchy() is an XML fragment.
Action: Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment
ORA-19038: Invalid opertions on query context
Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().
Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().
ORA-19039: Keyword string reserved for future use
Cause: The keyword is reserved for future use as a builtin function.
Action: Change the name mentioned above to a different one.

ORA-19040: Element string does not match expected string.
Cause: The given XML document had a different root element than expected.
Action: Insert/Update only the XML documents that conform to that particular schema and element.
ORA-19041: Comment data cannot contain two consecutive ‘-‘s
Cause: The given comment string expression has two consecutive ‘-‘s.
Action: Modify comment string to eliminate one or both of the consevutive ‘-‘s.
ORA-19042: Enclosing tag string cannot be xml in any case combination
Cause: The given enclosing tag matched ‘xml’ in some case combination
Action: Modify the enclosing tag so that it is not xml in any case combination.
ORA-19043: Multiply nested XMLROOT function disallowed
Cause: An XMLROOT function has an operand that is also an XMLROOT function.
Action: Modify the query so that there are no multiply nested XMLROOT functions.

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

 

Information About Waits Stats in SQL Server FILESTREAM Waits

SQLServerF1

SQL Server internally uses worker threads to execute SQL queries sent by various applications. While threads are executing they may be either running on CPU processing the request or would be waiting on a certain resource or waiting in waiting for its chance to run on CPU. SQL Server assigns a certain wait type to the worker thread that is waiting.

If a query is taking long time to complete, we can look at the query sessions wait type to get an understanding of what kind of resource it is the query waiting for and take appropriate action to avoid the queries to wait, thus making the queries complete fast.

Below are some of the SQL Server Wait Types related to FILESTREAM waits.

FS_FC_RWLOCK
Occurs when there is a wait by the FILESTREAM garbage collector to do either of the following:
o Disable garbage collection (used by backup and restore).
o Execute one cycle of the FILESTREAM garbage collector.

FS_GARBAGE_COLLECTOR_SHUTDOWN
Occurs when the FILESTREAM garbage collector is waiting for cleanup tasks to be completed.

FS_HEADER_RWLOCK
Occurs when there is a wait to acquire access to the FILESTREAM header of a FILESTREAM data container to either read or update contents in the FILESTREAM header file (Filestream.hdr).

FS_LOGTRUNC_RWLOCK
Occurs when there is a wait to acquire access to FILESTREAM log truncation to do either of the following:
Temporarily disable FILESTREAM log (FSLOG) truncation (used by backup and restore).
Execute one cycle of FSLOG truncation.

FSA_FORCE_OWN_XACT
Occurs when a FILESTREAM file I/O operation needs to bind to the associated transaction, but the transaction is currently owned by another session.

FSAGENT
Occurs when a FILESTREAM file I/O operation is waiting for a FILESTREAM agent resource that is being used by another file I/O operation.

FSTR_CONFIG_MUTEX
Occurs when there is a wait for another FILESTREAM feature reconfiguration to be completed.

FSTR_CONFIG_RWLOCK
Occurs when there is a wait to serialize access to the FILESTREAM configuration parameters.

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.

 

Information About Waits Stats in SQL Server synchronization Waits – Part 6

SQLServerF1

SQL Server internally uses worker threads to execute SQL queries sent by various applications. While threads are executing they may be either running on CPU processing the request or would be waiting on a certain resource or waiting in waiting for its chance to run on CPU. SQL Server assigns a certain wait type to the worker thread that is waiting.

If a query is taking long time to complete, we can look at the query sessions wait type to get an understanding of what kind of resource it is the query waiting for and take appropriate action to avoid the queries to wait, thus making the queries complete fast.

Below are some of the SQL Server Wait Types related to synchronization waits.

EC
Identified for informational purposes only. Not supported. Future compatibility is not guaranteed.

EE_PMOLOCK
Occurs during synchronization of certain types of memory allocations during statement execution.

EE_SPECPROC_MAP_INIT
Occurs during synchronization of internal procedure hash table creation. This wait can only occur during the initial accessing of the hash table after the SQL Server instance starts.

ERROR_REPORTING_MANAGER
Occurs during synchronization of multiple concurrent error log initializations.

EXCHANGE
Occurs during synchronization in the query processor exchange iterator during parallel queries.

EXECSYNC
Occurs during parallel queries while synchronizing in query processor in areas not related to the exchange iterator. Examples of such areas are bitmaps, large binary objects (LOBs), and the spool iterator. LOBs may frequently use this wait state.

EXECUTION_PIPE_EVENT_INTERNAL
Occurs during synchronization between producer and consumer parts of batch execution that are submitted through the connection context.

FAILPOINT
Identified for informational purposes only. Not supported. Future compatibility is not guaranteed.

FCB_REPLICA_READ
Occurs when the reads of a snapshot (or a temporary snapshot created by DBCC) sparse file are synchronized.

FCB_REPLICA_WRITE
Occurs when the pushing or pulling of a page to a snapshot (or a temporary snapshot created by DBCC) sparse file is synchronized.

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.

 

Information About Waits Stats in SQL Server Waits – Part 6

SQLServerF1

SQL Server internally uses worker threads to execute SQL queries sent by various applications. While threads are executing they may be either running on CPU processing the request or would be waiting on a certain resource or waiting in waiting for its chance to run on CPU. SQL Server assigns a certain wait type to the worker thread that is waiting.

If a query is taking long time to complete, we can look at the query sessions wait type to get an understanding of what kind of resource it is the query waiting for and take appropriate action to avoid the queries to wait, thus making the queries complete fast.

Below are some of the SQL Server Wait Types related to MSDTC waits.

DTC
Occurs when a task is waiting on an event that is used to manage state transition. This state controls when the recovery of Microsoft Distributed Transaction Coordinator (MS DTC) transactions occurs after SQL Server receives notification that the MS DTC service has become unavailable.
This state also describes a task that is waiting when a commit of a MS DTC transaction is initiated by SQL Server and SQL Server is waiting for the MS DTC commit to finish.

DTC_ABORT_REQUEST
Occurs in a MS DTC worker session when the session is waiting to take ownership of a MS DTC transaction. After MS DTC owns the transaction, the session can roll back the transaction. Generally, the session will wait for another session that is using the transaction.

DTC_RESOLVE
Occurs when a recovery task is waiting for the master database in a cross-database transaction so that the task can query the outcome of the transaction.

DTC_STATE
Occurs when a task is waiting on an event that protects changes to the internal MS DTC global state object. This state should be held for very short periods of time.

DTC_TMDOWN_REQUEST
Occurs in a MS DTC worker session when SQL Server receives notification that the MS DTC service is not available. First, the worker will wait for the MS DTC recovery process to start. Then, the worker waits to obtain the outcome of the distributed transaction that the worker is working on. This may continue until the connection with the MS DTC service has been reestablished.

DTC_WAITFOR_OUTCOME
Occurs when recovery tasks wait for MS DTC to become active to enable the resolution of prepared transactions.

DUMP_LOG_COORDINATOR
Occurs when a main task is waiting for a subtask to generate data. Ordinarily, this state does not occur. A long wait indicates an unexpected blockage. The subtask should be investigated.

DUMPTRIGGER
Identified for informational purposes only. Not supported. Future compatibility is not guaranteed.

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.

 

Operating System Error 3002 to Operating System Error 10054 for SQL Server

SQLServerF1

As a SQL Server DBA, there are various occasions where SQL Server returns Operating System errors as it causes some failure performing certain SQL Server operations. Below are Operating System Errors from Error 3002 to Operating System Error 10054

The Operating System Error 3002(The spool file was not found.)
ERROR_SPOOL_FILE_NOT_FOUND

The Operating System Error 3003(A StartDocPrinter call was not issued.)
ERROR_SPL_NO_STARTDOC

The Operating System Error 3004(An AddJob call was not issued.)
ERROR_SPL_NO_ADDJOB

The Operating System Error 3005(The specified print processor has already been installed.)
ERROR_PRINT_PROCESSOR_ALREADY_INSTALLED

The Operating System Error 3006(The specified print monitor has already been installed.)
ERROR_PRINT_MONITOR_ALREADY_INSTALLED

The Operating System Error 3007(The specified print monitor does not have the required functions.)
ERROR_INVALID_PRINT_MONITOR

The Operating System Error 3008(The specified print monitor is currently in use.)
ERROR_PRINT_MONITOR_IN_USE

The Operating System Error 3009(The requested operation is not allowed when there are jobs queued tothe printer.)
ERROR_PRINTER_HAS_JOBS_QUEUED

The Operating System Error 3010(The requested operation is successful. Changes will not be effectiveuntil the system is rebooted.)
ERROR_SUCCESS_REBOOT_REQUIRED

The Operating System Error 3011(The requested operation is successful. Changes will not be effectiveuntil the service is restarted.)
ERROR_SUCCESS_RESTART_REQUIRED

The Operating System Error 4000(WINS encountered an error while processing the command.)
ERROR_WINS_INTERNAL

The Operating System Error 4001(The local WINS can not be deleted.)
ERROR_CAN_NOT_DEL_LOCAL_WINS

The Operating System Error 4002(The importation from the file failed.)
ERROR_STATIC_INIT

The Operating System Error 4003(The backup failed. Was a full backup done before?)
ERROR_INC_BACKUP

The Operating System Error 4004(The backup failed. Check the directory to which you are backing thedatabase.)
ERROR_FULL_BACKUP

The Operating System Error 4005(The name does not exist in the WINS database.)
ERROR_REC_NON_EXISTENT

The Operating System Error 4006(Replication with a nonconfigured partner is not allowed.)
ERROR_RPL_NOT_ALLOWED

The Operating System Error 6118(The list of servers for this workgroup is not currently available)
ERROR_NO_BROWSER_SERVERS_FOUND

The Operating System Error 10053(Connection aborted. (An established connection was aborted by the software in your host machine.))
WSAECONNABORTED

The Operating System Error 10054(Connection reset by peer. (An existing connection was forcibly closed by the remote host))
WSAECONNRESET

This is applicable for below versions of Operating Systems

Windows Server 2003
Windows Server 2008 R2
Windows Server 2012

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.

 

Operating System Error 1822 to Operating System Error 1906 for SQL Server

SQLServerF1

As a SQL Server DBA, there are various occasions where SQL Server returns Operating System errors as it causes some failure performing certain SQL Server operations. Below are Operating System Errors from Error 1822 to Operating System Error 1906

The Operating System Error 1822(No principal name registered.)
RPC_S_NO_PRINC_NAME

The Operating System Error 1823(The error specified is not a valid Windows NT RPC error code.)
RPC_S_NOT_RPC_ERROR

The Operating System Error 1824(A UUID that is valid only on this computer has been allocated.)
RPC_S_UUID_LOCAL_ONLY

The Operating System Error 1825(A security package specific error occurred.)
RPC_S_SEC_PKG_ERROR

The Operating System Error 1826(Thread is not canceled.)
RPC_S_NOT_CANCELLED

The Operating System Error 1827(Invalid operation on the encoding/decoding handle.)
RPC_X_INVALID_ES_ACTION

The Operating System Error 1828(Incompatible version of the serializing package.)
RPC_X_WRONG_ES_VERSION

The Operating System Error 1829(Incompatible version of the RPC stub.)
RPC_X_WRONG_STUB_VERSION

The Operating System Error 1830(The idl pipe object is invalid or corrupted.)
RPC_X_INVALID_PIPE_OBJECT

The Operating System Error 1831(The operation is invalid for a given idl pipe object.)
RPC_X_INVALID_PIPE_OPERATION

The Operating System Error 1832(The idl pipe version is not supported.)
RPC_X_WRONG_PIPE_VERSION

The Operating System Error 1898(The group member was not found.)
RPC_S_GROUP_MEMBER_NOT_FOUND

The Operating System Error 1899(The endpoint mapper database could not be created.)
EPT_S_CANT_CREATE

The Operating System Error 1900(The object universal unique identifier (UUID) is the nil UUID.)
RPC_S_INVALID_OBJECT

The Operating System Error 1901(The specified time is invalid.)
ERROR_INVALID_TIME

The Operating System Error 1902(The specified form name is invalid.)
ERROR_INVALID_FORM_NAME

The Operating System Error 1903(The specified form size is invalid.)
ERROR_INVALID_FORM_SIZE

The Operating System Error 1904(The specified printer handle is already being waited on)
ERROR_ALREADY_WAITING

The Operating System Error 1905(The specified printer has been deleted.)
ERROR_PRINTER_DELETED

The Operating System Error 1906(The state of the printer is invalid.)
ERROR_INVALID_PRINTER_STATE

This is applicable for below versions of Operating Systems

Windows Server 2003
Windows Server 2008 R2
Windows Server 2012

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 3 4