For the past couple of days, I have been getting quite a bit of the messages below with no clue how to fix them. I use temp tables in many of my procedures for processing.
Msg 0, Level 11, State 0, Line 0. A severe error occurred on the
current command. The results, if any, should be discarded
All my stored procedures have NO COUNT set to ON. I don't use a whole lot of CTEs and I drop all temp tables after use.
I checked the log files C:\Program Files\Microsoft SQL Server\MSSQL11.WORKBOX\MSSQL\Log but found nothing that I believe explains what is happening to me. I would appreciate any help tackling this issue please.
Related
I'm hoping someone else may have encountered this and been able to resolve. I'm presently waiting for an azure support tech to help, so figured I'd reach out here in the mean-time since I couldn't find anything online...
I have a read-only database that users can query all tables without issues except for one specific table. Azure recommended solution pointed to login to user mapping issues, however, that would not allow the user to access the database which is not the case here.
There are no long running queries or open transactions and the server is more or less idle. I'm not seeing any locking or blocking either, so this is quite puzzling to me.
I can reproduce the issue with all users of all types testing with:
SELECT TOP 1 * FROM dbo.{table 1} - results in no issues
SELECT TOP 1 * FROM dbo.{table 2} - gets following error
Msg 40197, Level 20, State 200, Line 3
The service has encountered an error processing your request. Please try again. Error code 8630.
Msg 0, Level 20, State 0, Line 1
A severe error occurred on the current command. The results, if any, should be discarded.
In the end, Azure Support had me scale up and scale down the database and that has resolved the issue.
I've had this query in BigQuery that I have been updating every day for the last few months. It's been fine - some occasional errors, but retrying has solved the problem.
Bet last few days I am getting the error: The job encountered an error during execution. Retrying the job may solve the problem.
The error description says that it's an external error, so how can I fix that?
I have been retrying (with rather long pauses in between), but I still get the error.
JobID example: bquxjob_152ced5d_169917f0145
Does anyone have any idea what's going on? Is there any data/time limitations I might encounter (but why just the last few days then)?
You can use CGP stackdriver to monitor your BigQuery process using this URL
Interesting information you can find among others are the queryTime heatmap and the Slot usage which might help you understand your problems better
On the subject of the external table usage, you can use Google transfer (See this link for details) to schedule a repeated transfer from CSV to BigQuery table.
The below Image show you how to get to the transfer set up page from the webUI
I encountered this dreadfully useless error in a scheduled query. It was working great and then one day it stopped working at all and has been failing ever since without any other explanation. The StackDriver (now "Logs Explorer") showed nothing more enlightening:
jobStatus: {
errorResult: {
code: 14
message: "Error encountered during execution. Retrying may solve the problem."
}
errors: [
0: {
code: 14
message: "Error encountered during execution. Retrying may solve the problem."
}
]
jobState: "DONE"
}
Figuring out the actual issue takes a long time because scheduled queries start slowly since they use BATCH priority. What I found in my case was that the partitioned table and "Partition field" setting in the scheduled query was the culprit. I dropped the table and removed the partition field and voila the thing works again (although far from ideal since I need partitioning).
I hope this helps someone else running up against that useless error but in any case, I hope the good folks working on BigQuery find a better error to bubble up.
I ran into this problem when replacing the contents of a partitioned table. Two retries did not help. When I removed the --range_partitioning from the command the update was processed correctly. The table remained partitioned.
So there seems to be an issue about updates to partitioned tables, and when that is the cause these errors might not benefit from retry. I don't know whether there are other causes of this error.
This kind of issue probably has a lot to do with BigQuery quota errors : https://cloud.google.com/bigquery/docs/troubleshoot-quotas#ts-number-column-partition-quota, as mentionned by other answers, such as the 4000 partitions-by-table quota.
I've made a very simple database and am trying
select * from klant;
I've verified the table exists, and last week was able to see data in it. Today however I keep getting
Statement failed, SQLSTATE = 42S02
Dynamic SQL Error
-SQL error code = -204
-Table unknown
-KLANT
-At line 1, column 15
The same select query in flameRobin gives the following error:
Error: *** IBPP::SQLException ***
Context: Database::Statistics
Message: isc_database_info failed
SQL Message : -902
can't format message 13:98 -- message file C:\WINDOWS\SYSTEM32\firebird.msg not found
Engine Code : 335544727
Engine Message :
Error writing data to the connection.
I have copied the firebird.msg to the system32 folder so it should be able to find it there.
Any pointers toward the solution would be greatly appreciated. Similar question all seem to point toward issues with transactions, I can't see that being the problem here.
Edit:
I'm using the included ISQL tool from firebird and start the session by connecting to the database that includes my table. Same for flamerobin, first connect to database, I can see the table that i want to select from but it gives this error.
Edit2:
Finally reinstalled Firebird making sure I gave it admin right, which I think it had before, but wasn't sure about. This seems to have fixed it.
We are getting the following error using Oracle:
[Oracle JDBC Driver]Application failover does not support non-single-SELECT statement
The error occurs when we try to make a delete or insert over a large number of rows (tens of millions of rows).
I know that the script works, because it was working for almost an year before these error messages start to pop.
We know that no one change any database configuration, so we figure out that the problem must be on the volume of processed data (row number is growing as time goes by...).
But we never see that kind of error before! What does it means? It seems that a failover engine tries to recover from an error, but when oracle is 'taken over' by this engine, it enter in a more restricted state, where some kinds of queries does not work (like Windows Safe Mode...)
Well, if this is what is happening, how can I get the real error message? The one that trigger the failover mechanism?
BTW, below is one of the deletes that triggers the error:
delete from odf_ca_rnv_av_snapshot_week
(we tried this one just to test the simplest delete we could think of... a truncate won't help us with the real deal :) )
check this link
the error seems to come not from Oracle or JDBC, but from "progress". It means that it can only recover from SELECT statements and not from DML.
You'll have to figure out why the failover occurs in the first place.
I am using Sql Server 2005.
I wanted to take back up of my database through simple sql command.
For this I referred THIS document.
Made command as follows:
backup database webbasednewsoft to disk 'e:\wb.bak'
but its giving me error as:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near 'e:\wb.bak'.
I dont understand what is syntax error in this?
I have made everything according to doccument.
I thought the issue was for escape sequence, hence i also tried,
backup database webbasednewsoft to disk 'e:\\wb.bak'
But the error was same.
Please guid me for this.
You need an = sign.
backup database webbasednewsoft to disk='e:\wb.bak'
See here for the MSDN for the BACKUP command
And if you look at your reference it too mentions using an = sign! but hey we're all guilty of eager reading I know I do it... :-)