WordPress Database Error Disk Full

Recursive Ramblings

ramblings about software and other stuff in my life

working around “sqlite3.OperationalError: database or disk is full”

For my job at Intel, I recently started working with some python code that – among other stuff – accesses an sqlite database. The DB in question is currently around 3GB in size. One of the things this code does is generate a report for a given month, say “2013-10”, and it submits an sql statement to sqlite that goes something like

Since I’m expecting to have to run this for every month of 2013, and experience tells me that when my internal clients will want it, they’ll want it right now, I wrote a wrapper script around this code that calls this python script N times in parallel, each for a different month. This worked fine as long as N was 2 or less. When I started increasing N to 3 or more, sooner or later the sqlite ‘execute’ statement would throw an exception:

sqlite3.OperationalError: database or disk is full

but the disk the DB file is on is nowhere near full (unless you consider close to 700GB free space as “full” in this context ;-). After doing some research, I found out that this happens because sqlite uses /var/tmp to store temporary data, and /var/tmp (this is a linux box) is running out of disk space. This makes sense as /var/tmp had about 7.5G free space before I started my script, and this free space would drop to below 1GB during my tests.

Further research showed that using the sqlite pragma temp_store command I can tune where temporary data is stored, according to the documentation setting this value to 2 causes temporary data to be stored in memory. I first tried this using the commandline utility:

sqlite> pragma temp_store = 2;

but my tool still threw an exception. When I exited and then re-started sqlite, the value was back to 0 – this seems to be a per-connection setting. I put this piece of code into the session establishment function:

self.__cursor.execute("PRAGMA temp_store = 2")

This has caused the exception to disappear.


Support » Fixing WordPress » Fix for disk full usage issue ,error establishing a database connection

Fix for disk full usage issue ,error establishing a database connection

Due to this below issues

disk full issue ,error establishing a database connection

my site constantly goes down is there way to fix the issue

The page I need help with: [log in to see the link]

There’s no error at the moment.

If you’re getting an error that says “disk full”, it means that you’re using all of the allowed storage space in your hosting account. You need to contact your hosting company to upgrade your account to give it more space.

It’s also a good idea to have a look through your sites files to see if there’s anything tha maybe shouldn’t be there and is a large file size.

I already did that but thy say they have 2 manually add the disk ,but still this error occured twice ,right now 6,211.54 MB total disk space used ,but my host offers me unlimted

Support Team Volunteer

They may say you can use a gazillion bytes, but when the disk is full, the disk is full. They have to fix that.


WP Database Backup

Pro Version

WP Database Backup plugin helps you to create Database Backup and Restore Database Backup easily on single click.Manual or Automated Database Backups And also store database backup on safe place- Dropbox,FTP,Email,Google drive, Amazon S3

  • Create Database Backup
    WP Database Backup plugin helps you to create Database Backup easily on single click.
  • Autobackup
    Backup automatically on a repeating schedule
  • Download backup file direct from your WordPress dashboard
  • Easy To Install(Very easy to use)
    WP Database Backup is super easy to install.
  • Simple to configure(very less configuration), less than a minute.
  • Restore Database Backup
    WP Database Backup plugin helps you to Restore Database Backup easily on single click.
  • Multiple storage destinations
  • Store database backup on safe place- Dropbox,Google drive,Amazon s3,FTP,Email
  • Reporting- Sends emailed backups and backup reports to any email addresses
  • Exclude Table
  • Database backup list pagination
  • Search backup from list(Date/ Database Size)
  • Sort backup list (Date/ Database Size)
  • Save database backup file in zip format on local server And Send database backup file to destination in zip format
  • Documentation

Few of the Key Features

  • Database Backup easily on single click.
  • Autobackup.
  • Restore Database Backup easily on single click.
  • Store database backup on safe place- Dropbox,Google drive,Amazon s3,FTP,Email.
  • Pagination.
  • Search and sort database backup feature.
  • Documentation

Get Pro ‘WP All Backup’ Plugin

  • https://wpallbackup.com
  • www.wpseeds.com

WP All Backup will backup and restore your entire site at will, complete with FTP & S3 integration

Pro Features

  • Complete Backup
  • Create Database Backup easily on single click.
  • Autobackup Backup automatically on a repeating schedule
  • Backup Listing : Pagination.
  • Manual backup
  • Multisite compatible
  • Backup entire site
  • Exclude specific folders and files
  • Downloadable log files
  • Simple one-click restore
  • Set number of backups to store
  • Automatically remove oldest backup
  • Multiple storage destinations
  • FTP integration
  • Dropbox integration
  • Google drive integration
  • Amazon s3 integration
  • Email Notification
  • Reporting- Sends emailed backups and backup reports to any email addresses
  • ZipArchive
  • Backup zip labeled with the site name(Help when backing up multiple sites).
  • Select Backup Type: Only Database,Only Files, Complete Backup
  • Inline Help
  • Search backup from list(Date/Size)
  • Sort backup list (Date/Size)
  • Easy To Install(Very easy to use)
  • Simple to configure(very less configuration).
  • PclZip
  • Clone Site
  • Move Site
  • Change Backup folder name
  • Uses zip and mysqldump for faster back ups if they are available.
  • Exclude Tables from your back ups.
  • System Check (i.e backup folder permission, execution time etc)
  • Disk space checkup(memory available).
  • Support
  • Статусы
  • And More….


Restoring Your Database From Backup

Using phpMyAdmin

phpMyAdmin is a program used to manipulate databases remotely through a web interface. A good hosting package will have this included. For information on backing up your WordPress database, see Backing Up Your Database.

Information here has been tested using phpMyAdmin 4.0.5 running on Unix.

The following instructions will replace your current database with the backup, reverting your database to the state it was in when you backed up.

Restore Process

Using phpMyAdmin, follow the steps below to restore a MySQL/MariaDB database.

  1. Login to phpMyAdmin.
  2. Click "Databases" and select the database that you will be importing your data into.
  3. You will then see either a list of tables already inside that database or a screen that says no tables exist. This depends on your setup.
  4. Across the top of the screen will be a row of tabs. Click the Import tab.
  5. On the next screen will be a location of text file box, and next to that a button named Browse.
  6. Click Browse. Locate the backup file stored on your computer.
  7. Make sure SQL is selected in the Format drop-down menu.
  8. Click the Go button.

Now grab a coffee. This bit takes a while. Eventually you will see a success screen.

If you get an error message, your best bet is to post to the WordPress support forums to get help.

Using MySQL/MariaDB Commands

The restore process consists of unarchiving your archived database dump, and importing it into your MySQL/MariaDB database.

Assuming your backup is a .bz2 file, created using instructions similar to those given for Backing up your database using MySQL/MariaDB commands, the following steps will guide you through restoring your database:

1. Unzip your .bz2 file:

Note: If your database backup was a .tar.gz file called blog.bak.sql.tar.gz, then

is the command that should be used instead of the above.

2. Put the backed-up SQL back into MySQL/MariaDB:

Parthokonar’s Blog

Just another WordPress.com weblog

Archive Log Full in Oracle

What happens if a archive log destination is filled up in oracle. This is a common problem Oracle DBA’s usually face.

When our Oracle database running in archive log mode with automatic archiving turned on. And When the archive
log destination disk space becomes full, the automatic archiving will stop.

When this happens we will get errors like ORA-00257

ORA-00257: archiver error. Connect internal only, until freed.

Cause: The archiver process received an error while trying to archive a redo log.
If the problem is not resolved soon, the database will stop executing transactions.
The most likely cause of this message is the destination device is out of space to store the redo log file.

Action: Check archiver trace file for a detailed description of the problem.
Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for

When all of the online redo logs are filled up, the database will be in a hung state.

If we attempt to manually archive the files with commands “archive log next” or “archive log all”
you may receive errors

1. Increase the filesyatem where the archive logs are been generated.

If it is a veritas filesyatem we can resize in run time.

The commands are.

Check how much space is available in diskgroup.

vxassist — create, relayout, convert, mirror, backup, grow, shrink, delete, and move volumes

maxsize – Reports the maximum size a volume could be created with given the attributes specified and
given the free storage available.

root@datahouse1# vxassist -g lduprd_dg maxsize
Maximum volume size: 182728704 (89223Mb)

Resize the volume.

The example below resizes a filesystem to 8 GB.

root@datahouse1# /usr/lib/vxvm/bin/vxresize -g lduprd_dg lduprd_db231_lv +8g

2. Delete all the archivelogs in the archive destination.

Then connect to recovery catalog and target database and issue the command in rman prompt.

allocate channel for maintenance type disk;
change archivelog all crosscheck;
release channel;

Note :- Crosscheck command checks whether the specified backups and copies exist. If RMAN cannot find
backup pieces, it marks them as having the status expired. It marks all other types of absent files–image
copies and archived redo logs–as deleted.

If the files are on disk, RMAN queries the file headers. For other device types, RMAN queries the media
manager to see whether the file exists in the media management catalog.

Take a incremental level 0 database backup from rman.

3. Take the backup of all archivelogs through RMAN

Backup archivelog all delete input.

4. Use the command:

alter system archive log all to ‘/u07/app/oradata/DBADB/archive’;

The command archives all redo log file groups that are full but have not been archived.

The gives Oracle a valid location for the archive logs. Even after using this the archive log destination
parameter is still invalid and automatic achive does not work. This solution is best for systems
that do not archive regularly but cannot be shutdown. You can also use this to allow you to do a
Shutdown immediate instead of Shutdown abort.

Shutdown and restart of the database resets the archive log destinstation parameter to be valid.
Do not forget to make disk space available before starting the database.

5. Use the REOPEN attribute of the LOG_ARCHIVE_DEST_n init .ora parameter.

Or run the following comand:

alter system set LOG_ARCHIVE_DEST_n = ‘reopen’

The REOPEN and the NOREOPEN attributes of the LOG_ARCHIVE_DEST_n parameter specify the minimum number
of seconds before the archiver processes (ARCn) or the log writer process (LGWR) should try again to
access a previously failed destination. You can turn off the attribute by specifying NOREOPEN.

6.Use the commands:

alter system archive log stop;
alter system archive log start;

Leave a Reply

Your email address will not be published. Required fields are marked *