I'm trying to run a query which, when successful, executes in 500-600 ms. However, sometimes the query fails and gives a message saying it couldn't connect to the server. The exact message is
Error: ('HY000', '[HY000] [Vertica][VerticaDSII] (10) An error occurred during query preparation: no connection to the server\n (10) (SQLExecDirectW)')
What is the root cause of this error and how do I fix it?
Related
I am having two servers; one has SQL Server another one has Oracle. SSIS package is setup to receive data from Oracle into SQL Server.
Trying to figure out the below error.
OnError,ServerNameAB,Domain\UserID,pkgLoad_Data,{794F09AE-9188-4F94-AC4F-950361612345},{D131842F-59AF-450A-BE1E-3E7EBB812345},3/14/2022 7:26:01 PM,3/14/2022 7:26:01 PM,-1071610805,0x,An exception has occurred during data insertion, the message returned from the provider is: A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
OnError,ServerNameAB,Domain\UserID,Data Flow Task,{7c7246a7-64e3-4866-9314-534074112345},{D131842F-59AF-450A-BE1E-3E7EBB812345},3/14/2022 7:26:01 PM,3/14/2022 7:26:01 PM,-1073450974,0x,SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "ADO NET Destination" (2) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (9). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
Troubleshooting tried:
rebooting the "receiving data" server
restarting SSMS
update: Below are the correct settings...
I am losing my patience with this problem. I'm running SQL Server 2008 R2 with all updates.
It is very intermittent. Every now and again this SQL server instance will report the error: Login failed for user 'XX'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection.
Error: 18456, Severity: 14, State: 46.
I know this is a good login, it works all of the other times, and no one changes the credentials.
The above error is immediately followed by this error:
The client was unable to reuse a session with SPID 150, which had been
reset for connection pooling. The failure ID is 46. This error may
have been caused by an earlier operation failing. Check the error logs
for failed operations immediately before this error message.
Error: 18456, Severity: 14, State: 46.
When this occurs a few minutes later this is reported also:
Message
All schedulers on Node 0 appear deadlocked due to a large number of worker threads waiting on ASYNC_NETWORK_IO. Process Utilization 0%.
The above message just keeps repeating until I restart the server.
From researching this issue I've increased the maximum worker threads (currently at 1100). The server has 72G memory and 4 vCPUs, running Windows Server 2008 R2.
i don't encounter this issue at all on my other database servers that run the same environment. Just this one. Any help would be greatly appreciated, I'm running out of options.
I have an SSIS package that reads data from an Oracle table and puts it into a Netezza table. For some reason, SSIS cannot read a specific column value (2% of the records) as shown in the screenshot here.
The column type in Oracle is NUMBER(3) and in my Netezza table it's SMALLINT. Any idea why this might be happening?
The error columns do not give me any information either.
What I have tried so far:
Tried to get a better Error Description using this MSDN article.
Reduced batch size from the default 1000, to 100.
Thanks in advance for any help.
EDIT
I let it fail and here are the error messages I am getting. I have 4 GB memory on the my laptop. Could that be an issue?
[DESTINATION_TABLE 2] Error: Open Database Connectivity (ODBC) error occurred. SQLExecute returned error while inserting row 35244
[DESTINATION_TABLE 2] Error: Open Database Connectivity (ODBC) error occurred. state: 'HY008'. Native Error Code: 51. Operation canceled
[DESTINATION_TABLE 2] Error: Open Database Connectivity (ODBC) error occurred. state: '01000'. Native Error Code: 1. Unable to write nzlog/bad files
[DESTINATION_TABLE 2] Error: Open Database Connectivity (ODBC) error occurred. state: '01000'. Native Error Code: 1. Unable to write nzlog/bad files
[DESTINATION_TABLE 2] Error: Open Database Connectivity (ODBC) error occurred. state: 'HY000'. Native Error Code: 46. ERROR: External Table : count of bad input rows reached maxerrors limit
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "DESTINATION_TABLE" (2) failed with error code 0x80004005 while processing input "ODBC Destination Input" (13). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
[SOURCE_TABLE [63]] Error: Failed to add row to output buffer.
[SOURCE_TABLE [63]] Error: Open Database Connectivity (ODBC) error occurred.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on SOURCE_TABLE returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Did you try data conversion in your data flow? Try to convert numeric to (DT_I2)in SSIS and then it shall work I believe
Can somebody help me get through the following Sql Exception : "A severe error occurred on the current command. The results, if any, should be discarded".
I'm running a drop replication (i.e sp_dropsubscription & sp_droparticle) script reading from the uploaded file using c#.net. I encounter the above error when running in Sql server 2008, but the same thing works fine in Sql Server 2005.
At the point of the Exception, I see that the Commands have actually got executed in the backend but can't figure out why the exception. Any idea ??
Thanks.
After a breakdown on my virtual webhost, they finally restored the container, but now I randomly get the error when I try to execute queries. I can do a
Select top 20000 from Orders
But
Select * from Orders (about 100k rows total)
Receives the error in my management studio:
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
And this error in my error log:
A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.
I have googled the error and can see that it could be because "Lightweight pooling" is enabled, but this is not the case here.
I run mssql 2008 express on a windows 2003 server.
We get the same random issue on MSSQL where I work and (for us any way) its down to network issues (too much traffic and such).
This blog post by Michael Aspengren explains the error message "A transport-level error has occurred when sending the request to the server."