Tag Info

New answers tagged

2

How to get the 8.00.194 (!!!!!!) server to 8.00.2040: You can download Service Pack 4 (8.00.2039) from here, which you will need to install before you can install the 8.00.2040 hotfix. How to restore a 2000 .bak to a 2008 server: You may need to clarify your actual requirements and clean up the question, but if you are trying to ultimately restore a SQL ...


1

As Chris already mentioned LOAD is a utility and therefore the UTIL_HEAP_SZ must be set high enough (but don't ask too much, always monitor the memory free space with top). You need a lot of memory for a fast load (see DATA BUFFER below). Here are things that speed up the load: More containers for the tablespace where the table is (best on separate luns / ...


1

To troubleshoot, I would start by looking at the output of SELECT current_user; and SHOW search_path;. Also, the output of \dp termin in psql. My suspicion here is that you are stumbling over mixed case identifiers. The error message mentions a table Map Notice the capital letter M. Are you sure there is no mix-up with another table named map (lower ...


0

The Progress backup is a block-level image of the database & bi file, so there's no way to only restore certain tables. You'll need to restore the db on a machine with enough space for the old db and the smaller db, create an empty version of the db, dump the required tables from the restored db, load that table data into the new db file, then ...


0

I just use this backup THE WHOLE MYSQL FILES way to migrate a MySQL database, and it worked! here is my steps 1, install MySQL server on the 2nd server with exactly same configuration like 1st server; 2, stop 1st and 2nd mysqld server 3, change the 2nd mysql data folder name, which you can find in mysql configuration file (my.cnf): ...


1

As far as I know you can't do that with DB2. Deltas and Incrementals will be based off of the last full backup taken (either offline or online). If anything it would cause one to adjust your recovery strategy for that week. If you needed the data however, why not just copy the backups you need (the full and any deltas/incrementals) and restore those ...


1

usually mysqldump will take as long to backup as xtrabackup, but much slower when restoring. because xtrabackup copy back by blocks while sql file exported by mysqldump have to excute one bye one. I am quite sure use some ways could impove import speed, but still will cost you very long long time especially for such a huge database. so I truly recommend ...


2

If you're using largely innodb tables increasing the innodb_buffer_pool_size as large as possible (~80-90% system assuming nothing else but mysqld is really consuming ram). This requires a mysqld restart though Before the reload you can also set innodb_flush_log_at_trx_commit=2 to speed things up. This disables flushing to disk every commit (breaking the ...


1

This is expected as restore from mysqldump takes longer than taking the backup. To speedup process consider other backup tools: xtrabackup. non-blocking for InnoDB, almost as fast as file copy. takes binary backup(=copies InnoDB tablespace). mydumper. Takes logical backups, but can do it in multiple threads, so it's faster than mysqldump mylvmbackup. ...


0

To IMPORT: ype the following command to import sql data file: $ mysql -u username -p -h localhost DATA-BASE-NAME < data.sql In this example, import 'data.sql' file into 'blog' database using vivek as username: $ mysql -u sat -p -h localhost blog < data.sql If you have a dedicated database server, replace localhost hostname with with actual ...



Top 50 recent answers are included