I am aware that SQL Server is not designed for such scenarios and the correct solution is to fix the cause of the power loss […]
Actually it's designed to deal with power loss, that's why there are things like write ahead logging (WAL) and crash recovery upon startup (or whatever you want to call it). One of the ways this is done is by choosing to not cache ...
If the tablet has a working battery, you can configure Windows to shut down when the battery power is low.
If the tablet has a non-working battery, consider replacing the battery. (I've had laptops like that - you'd be surprised how inexpensive replacement batteries can be on eBay. They don't work as well as OEM, but hey, anything's better than nothing in ...
I was able to repro on 2008 R1 SP3 10.00.5512 but installing the latest CU (14) fixed it.
Reviewing the bugs fixed in the intervening versions it looks as though you need to upgrade to a build that includes the following fix.
Access violation when you run a query that contains many constant values in an IN clause in SQL Server 2008 or in SQL Server 2012
REPAIR TABLE works for MyISAM, ARCHIVE, and CSV tables.
In other words, REPAIR TABLE does nothing for InnoDB. InnoDB has its own automatic crash recovery that it runs on startup.
But InnoDB crash recovery only works for lost changes that were in progress at the time of the crash. It uses ...
I just had the same problem, this was fixed by issuing a command, assuming mysql data dir is on /var/lib/mysql/mysql
myisamchk -q -r /var/lib/mysql/mysql/proc
Source : http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html
TL;DR: Except for a specific bug in PostgreSQL 9.3 prior to 9.3.4 which it's vital that you patch, index corruption after crash is never expected and hasn't been since PostgreSQL 7.1 was released in 2001.
The advice/folklore you got was wrong.
I am told that a long time ago in a galaxy far, far away (PostgreSQL 8.4 under Ubuntu 12.04), PostgreSQL ...
Assuming you have a local DB on the forklift rather than a server because of spotty wireless connections? Obviously getting SQL off the forklift would be the preferable solution.
Anyway, like Brent suggested, set the tablet to power down on its own after x minutes on battery power or some similar criteria.
Failing that, a small UPS that can initiate a ...
Follow the steps outlines in How to use the DBCC MEMORYSTATUS command to monitor memory usage on SQL Server. The remedy action will depend on your findings. You can also read How to Identify Microsoft SQL Server Memory Bottlenecks which is more accessible.
One word of caution though: is unlikely you will find individual queries to blame. Tracking downs ...
In the end, it was only after changing my hosting plan (and moving away from cPanel, which seemed to obscure some of the logging) that I was able to see the issue. Turns out that from time to time, memory usage would spike (I'm guessing that this was because of a dramatic spike in apache child processes) and this would cause memory pressure. The out-of-...
Looks like a known issue with it not handling an exception error properly and also the wrong version:
WB 6.3.5 (and also older release like 6.1.7) can connect to MariaDB.
> How to repeat:
> 1. Download WB 6.3.5 CE 64 bit (32 bit has the same issue)
> 2. Download MariaDB 10.0.22 64 bit windows
No, rollbacks cannot be done in the background. Both that and the double write checks have to be done before accepting connections again (meaning that if you kill it, you will have to start again on restart). REDO process, however, can and is done in the background.
What you can do is kill mysql (again) and restart it skipping that step:
As per your log it shows you have corruption in the InnoDB tablespace.
InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB:
InnoDB: about forcing recovery.
As per MySQL documentation Here for Forcing InnoDB Recovery
you can add the following line to the [mysqld] ...
This happened to me recently and this thread has been invaluable for helping me understand what's happening.
I'm running a LAMP stack on Ubuntu 14.04 with 1GB Ram. My server kept crashing due to web traffic spikes. For me, fiddling with the mysql config file only extended the amount of time I'd experience another random crash. To test and fix this, I ...
Overall, no, you did not do anything wrong with your .NET code. There is a minor technical issue, but we will get to that in a moment.
I was able to reproduce this (both error and non-error scenarios) in SQL Server 2008 R2 RTM. At first, in the "non-error" scenario, I was getting another error for:
specified cast is invalid
This error was a result of ...
You will have to mysqldump around moments_production_wp
I have old posts to bypass databases and tables
Dec 16, 2011 : How do you mysqldump specific table(s)?
Feb 20, 2013 : Any option for mysqldump to ignore databases for backup?
Using the same concepts, here is how to mysqldump all except moments_production_wp
Community Wiki answer generated from comments on this and the previous question.
sp_BlitzErik: Threadpool waits can happen for reasons other than just long running queries. Number of connections, number of simultaneous queries (especially if going parallel), and number of background tasks can also contribute, and that's just within SQL.
Enable the Remote ...
Shutdown the server and tried to move the VM to another drive but it
fails with File Error.
My latest suspicion is this is being caused by
a bad block but running badblocks seemed to trigger a crash at 25%
complete. During the fsck I see this: fsck critical medium error, dev
sda, sector 147306432
Don't waste your time on DB tuning & others ...
I've found that the database diagram tool seems to crash if you modify things outside of the diagram.
Diagrams appear to remain stable if:
The database diagram tool is used to do all of your modifications, thus retaining all metadata of the process within the diagram.
Your database structure is modified outside of the diagram which is then deleted and ...
I am not totally convinced MySQL is running out of memory. Here is why:
When you use mysqltuner.pl, it calculates the total usage in the worst case scenario. It does it by adding 3 figures together
thread_memory : max_connections * the sum of
I need the tables to be InnoDB and in sync. Those two statements crashing.
Does it crash with a stack trace in the server logs? Could you share it here? I tried the above two commands on a 2-node MariaDB-5.5.47 cluster and it worked as expected.
As @jkavalik suggested, you could do something like the following :
Create a new INNODB table with the same ...
I finally figured it out. The main reason for the crashes and the mysql_upgrade error was related to missing and/or corrupted primary keys of the mysql table.
There were also a couple missing records in the mysql.db table, which likely couldn't update previously due to the GRANT crashes and would have been related to Plesk "Database Servers" ...
First of all there is a documented bug that has seen the recovery performance of 5.7 degrade, this is discussed here https://bugs.mysql.com/bug.php?id=80788 which seems to have been fixed in 5.7.19
Otherwise, these suggestions might help:
The underlying os has to guarantee either a successful write or an error is returned. The os in turn relies on drivers which in turn rely on firmware which relies on the hardware If either the drivers,firmware oe hardware lie there is nothing windows or sql server can do about that.
This is why you need to check with the driver/firmware/hardware ...
This is harmless.
That message is sent by the server to the client when a process has crashed and the backend is about to die (quickdie in postgres.c) so that crash recovery can begin.
You are only seeing the message sent by the primary server to the WAL receiver. Note the WARNING: this is not even an error. This only gets logged because log_min_messages on ...
It was OOM.
The first thing I was suspect was memory. But:
VM's dmesg didn't output any messages until I reboot container. Only after that I saw messages, like
[0.000000] Out of memory in UB 101: OOM killed process 779 (mysqld) score 0 vm:16724384kB, rss:13130908kB, swap:2250952kB
MySQL error log (and another system logs of VM and node) didn't complain ...
See if any of these help:
Power failure and innodb
New install with backup from older version
MySQL issues ...or not?
Cannot start MySQL after forced shutdown
Finding the cause of a crashed table
MySQL Cluster - 4 node - Windows - 1st Install
MySQL/innodb database malfunctioning
have to restart mysql every day
Heavy data lost in ...
In 1GB of RAM, you may be able to set innodb_buffer_pool_size to 50M, maybe 100M. But definitely not 800M. The 80% advice is predicated on having at least 4GB of RAM, and 80% is too high even for that.
Having other things on the same machine (Apache?) adds to the cramped quarters. If you have Apache, lower MaxClients to 10.
Other things to keep out of ...
MyISAM support in galera is cough beta at best.
The best thing to do is:
mysqldump ... -T db table_name > dump.sql (this will make a .sql and .txt file)
drop the myisam table
edit the .sql file and change ENGINE=MYISAM to ENGINE=INNODB
LOAD DATA INFILE 'table.txt' INTO TABLE table_name;
Do this on whatever node that you want to treat as the "source of ...