Hello Neil,
On 1/22/2016 3:23 PM, Neil Tompkins wrote:
2016-01-22 19:43:48 2556 [ERROR] InnoDB: Attempted to open a previously
opened tablespace. Previous tablespace mysql/innodb_table_stats uses space
ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace
sportstrader/event
database. You can see below, that my machine shut down normally, yet when
>> I restarted the machine back up, I'm getting the error
>> 'mysql\innodb_table_stats.ibd. Cannot open tablespace' and am having to
>> delete the current database and restore my backup.
>>
k up, I'm getting the error
>> 'mysql\innodb_table_stats.ibd. Cannot open tablespace' and am having to
>> delete the current database and restore my backup.
>>
>> Here is my Error log file.
>>
>> 2016-01-22 18:06:28 2540 [Note] MySQL: Normal shutdown
>
below, that my machine shut down normally, yet when
> I restarted the machine back up, I'm getting the error
> 'mysql\innodb_table_stats.ibd. Cannot open tablespace' and am having to
> delete the current database and restore my backup.
>
> Here is my Error log file.
estore my
> database. You can see below, that my machine shut down normally, yet when
> I restarted the machine back up, I'm getting the error
> 'mysql\innodb_table_stats.ibd. Cannot open tablespace' and am having to
> delete the current database and restore my backup.
>
>
My disk drive has about 3 gb free space. The sequence of events is
1. Create database
2. Restore the data
3. Use the database, SELECT data etc
4. Shut down PC
5. When I restart PC I get this error
Hi,
Hoping someone can help me identify why I keep having to restore my
database. You can see below, that my machine shut down normally, yet when
I restarted the machine back up, I'm getting the error
'mysql\innodb_table_stats.ibd. Cannot open tablespace' and am having to
del
On Mon, Aug 2, 2010 at 8:35 PM, Johnny Withers wrote:
>
> Now when i run the same show table status command, the comment field says:
> InnoDB free: 6144 kB
>
> Is that telling me that I only have 6MB of storage left even though I
> increased the table space by 8GB?
>
I seem to recall - but am o
Hi Johnny,
Sorry about that - i just overlooked and the simple way to calculate the
sizes is to query the information_schema table called "tables" for data and
index sizes.
On Tue, Aug 3, 2010 at 8:55 PM, Johnny Withers wrote:
> About the above - it is saying 6144 KB so it is 6.1 GB.
>
> Ar
About the above - it is saying 6144 KB so it is 6.1 GB.
Are you sure? I would think 6144KB = 6.144 MB, or 6144 * 1000 = 6,144,000
bytes.
I think since InnoDB, by default, extends the table space by 8MB increments,
this is reporting the free space in this increment. How can I tell total
remain
Hey john,
Yes you can add it but safe to keep auto-extend at the end and monitor the
disk space as well.
"Now when i run the same show table status command, the comment field says:
InnoDB free: 6144 kB
Is that telling me that I only have 6MB of storage left even though I
increased the table spac
I recently ran out of table space on a production server that had the
following configuration line:
innodb_data_file_path=ibdata1:1G;ibdata2:1G;ibdata3:1G;ibdata4:1G;ibdata5:1G;ibdata6:2G:autoextend:max:8G
Before I changed this line and restarted the server, I ran SHOW TABLE STATUS
LIKE 'table' o
or you may have copied the InnoDB
> tablespace but not the InnoDB log files. "
>
> GOAL: Trying to restore mysql backup on different host
> using InnoDB backup that copes the backed up files to a files sever where I
> pulle them down to the new host
> I place all the MySQL dat
WHY do I see this error when restoring my backup db :
" InnoDB: Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. "
GOAL: Trying to restore mysql backup on different host
using InnoDB backup that copes the backed up files to a f
Hi All,
I have three databases namley nddata, archivedata and alldata. I want to
create three table space for all the three
databases. Is it possible. If yes then how to do this thing.
Thanks
--
Krishna Chandra Prajapati
MySQL DBA,
Ed Ventures e-Learning Pvt.Ltd.
1-8-303/48/15, Sindhi Colony
P.G
only re-use space from that one file.
>
> Therefore the sum table size will be larger with many files.
> Depending on how much data you regularly delete.
I would claim that the file-per-table method reduces fragmentation and
overall tablepsace size as compared to the tablespace method:
Olaf Stein wrote:
Hi all,
Are there any reasons why one would NOT use separate ibd files for each
table (--innodb_file_per_table). It seems logical to me to separate what
does not belong together logically (different databases), but I as the
shared tablespace is the default I wonder if it has
to separate what
does not belong together logically (different databases), but I as the
shared tablespace is the default I wonder if it has nay advantages I am not
aware of
Thanks
Olaf
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://
abases), but I as the
shared tablespace is the default I wonder if it has nay advantages I am
not
aware of
Thanks
Olaf
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hi all,
Are there any reasons why one would NOT use separate ibd files for each
table (--innodb_file_per_table). It seems logical to me to separate what
does not belong together logically (different databases), but I as the
shared tablespace is the default I wonder if it has nay advantages I am
""Gary Richardson"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Can I pre-create innodb tablespace using something like dd (or any other
> better tool)?
I'm afraid it can't be done that way, because fresh datafile is not simply
an e
Hi,
Can I pre-create innodb tablespace using something like dd (or any other
better tool)?
I have a server that is getting low on innodb table space and I want to add
15GB or so, but I want to minimize downtime. The server is a bit slow and I
estimate it will take around 10-20 minutes or so. I
David Sparks wrote:
> I want to move 3 100GB .ibd files into a new DB.
>
> I followed the instructions here:
>
> http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html
>
> But it doesn't work:
>
> mysql> alter table reports discard tablespace;
&g
I want to move 3 100GB .ibd files into a new DB.
I followed the instructions here:
http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html
But it doesn't work:
mysql> alter table reports discard tablespace;
Query OK, 0 rows affected (0.04 sec)
mysql> alter table rep
Hi
I'm running MySQL 4.0.25 on a Linux machine dual xeon 3.0GB Ghz(32 bit)
with 6 GB RAM
the data is connected to a SAN storage
I wander what is the best tablespace configuration (except RAW) of
configuraing?
my configuration is as follows:
innodb_data_file_path=ibdata1:10G;ibdata
Using SQL : SHOW TABLE STATUS, we could see Innodb free size from inno
db table's comment.
Is there any SQL to know total tablespace size allocated?
--
Regards,
Ady Wicaksono
HP: +628562208680
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubs
Reply by me.
How stupid i'm :(
I've finished this warning error problem by adding
4 files --> 3 file each 3 Gbyte and 1 file 500Mbyte
Thx mr. heiiki :D
Sorry
Ady Wicaksono wrote:
|Dear All,
As subject, Actually i've been ever meet this case
when i see :
InnoDB: Erro
|Dear All,
As subject, Actually i've been ever meet this case
when i see :
InnoDB: Error: tablespace size stored in header is 877184 pages, but
InnoDB: the sum of data file sizes is 953856 pages
And Mr. Heikki tell me to do these steps:
(953856 - 877184) / 64 = 1198 MB
1) Stop the m
Hi list,
I have the following error in a MySQL server:
050617 09:16:35 mysqld started
InnoDB: Error: tablespace size stored in header is 8660992 pages, but
InnoDB: the sum of data file sizes is only 6432768 pages
050617 9:16:40 InnoDB: Started
/usr/sbin/mysqld-max: ready for connections
And
From: "Andreas Schildbach"
> Is it possible to configure MySQL so that it uses one InnoDB tablespace
> file per database schema, instead of mixing all data into the shared
> tablespace?
No, but you can use a file per table:
http://dev.mysql.com/doc/mysql/en/multiple-tablesp
Hello everyone,
Is it possible to configure MySQL so that it uses one InnoDB tablespace
file per database schema, instead of mixing all data into the shared
tablespace?
I'd like to keep my applications data seperate, and having one file per
application (schema) should make data migrations e
I've always figured that if your tablespaces are tight enough to
autoextend, you're going to take a performance hit. InnoDB uses the
tablespace for some transaction/rolebacks -- if you have a large
transaction going through it will be slowed down by an autoextend
operation. Plus, once yo
I expect the data size is no more then 1.5TB.
Why don't you like to let tablespace auto grow?
Is it performace issue or not?
If I create ten innodb_data_file and each size of innodb_data_file is 50G,
dose some issues must be take care?
Because the 50G is really very big for a file, I nev
periodically
The running environment is follows,
Server: Dual Intel Xeon 3.2G with 4G DDR2 Memory.
OS: FreeBSD 5.3-RELEASE
MySQL: 4.1 branch
Operation: 70 ~ 80% operation is query (select statement)
According to the above terms,
how to plan the Tablespace in the mysql server?
Using raw devices for the
Sabeer,
- Original Message -
From: "Sabeer MZ" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, February 04, 2005 7:33 PM
Subject: Multiple Tablespace
Hi ALL,
Im using mySQL Distrib 4.0.18 and using single Tablespace
(/data/ibdata/ibdata1).
No
Hi ALL,
Im using mySQL Distrib 4.0.18 and using single Tablespace
(/data/ibdata/ibdata1).
Now Im planning to upgrade to 4.1.8 and move single tablespace to
Using Per-Table Tablespaces.
Please share your expertise in moving single TB to using per-table TB
with my existing data also.
Thanks
arsten" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm using InnoDB with the "innodb_file_per_table" option on.
> But now my .MYD-file has reached the maximum filesize of my filesystem
> and i have to add a new tablespace.
>
> Can someone tell me h
Carsten,
- Original Message -
From: ""Grumm, Carsten"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 26, 2005 4:22 PM
Subject: Out of tablespace when using innodb_file_per_table
Hello,
I'm using InnoDB with the "i
Hello,
I'm using InnoDB with the "innodb_file_per_table" option on.
But now my .MYD-file has reached the maximum filesize of my filesystem
and i have to add a new tablespace.
Can someone tell me how?
Thanks in advance for your help
Carsten
--
MySQL General Mailing List
For list
[snip]
I assume that the space of "InnoDB free: 201787392 kB" was resulted from the
dropping of DB_B. Will this chunk be re-used when new data is inserted?
[/snip]
InnoDB tablespace will not shrink when data is removed. The space the you
have from the dropped database will be reused.
esulted
from the dropping of DB_B. Will this chunk be re-used when new data is
inserted?
2. If the answer for Question 1 is no, I believe I unfortunately have to
follow the instruction on
http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html to decrease
the size the tablespace. Since I have
IGN KEY (`proteinOid`) REFERENCES
> `Protein` (`oi
> d`) ON UPDATE CASCADE,
> CONSTRAINT `Alias_ibfk_2` FOREIGN KEY (`aliasGroupOid`) REFERENCES
> `AliasGroup
> ` (`oid`) ON UPDATE CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
>
> --
> -Message d'origine-
> De : Jeff Mat
RENCES `AliasGroup
` (`oid`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-Message d'origine-
De : Jeff Mathis [mailto:[EMAIL PROTECTED]
Envoyé : 14 janvier 2005 16:15
À : Duhaime Johanne
Cc : mysql@lists.mysql.com
Objet : Re: actual size of a innodb tablespace
if y
if you issue a "show table status" command from the mysql prompt, you'll
get an estimate of how much free space exists in the files.
Duhaime Johanne wrote:
Hello
Context: innodb per table.
Is it possible to know the actual size of my innodb file? What part of
the initial size (10M: autoexten
Hello
Context: innodb per table.
Is it possible to know the actual size of my innodb file? What part of
the initial size (10M: autoextend) is actually used? I would like to
have an idea of the data space progression? Per database (I have 3).
Thank you in advance
Johanne Duhaime
IRCM
courr
On Thu, 6 Jan 2005 11:30:33 +0200
"Heikki Tuuri" <[EMAIL PROTECTED]> wrote:
> > innodb_data_file_path = ibdata2:7M;ibdata1:10M:autoextend
>
> You have to add new data files to the end of the line, not to the
> start. Please follow the instructions at
> http://dev.mysql.com/doc/mysql/en/Adding_an
Ian,
- Original Message -
From: "Ian Grant" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 05, 2005 4:47 PM
Subject: Re: InnoDB: Error: tablespace size stored in header is 17024 pages,
Dear Heikki
Many thanks for your reply.
On Mon, 3 J
now so it is too late to go
back tho that copy.
> What does the old .err log contain? Any message about disk space
> running out?
>
> The error below probably has not corrupted your tablespace. Best to
> run CHECK TABLE on some of your tables, though.
I did that on all tables and
Ian,
are you sure that you copied the complete ibdata1 file to the new place? It
is strange how 7 MB can be missing from the file end.
What does the old .err log contain? Any message about disk space running
out?
The error below probably has not corrupted your tablespace. Best to run
CHECK
First of all, thanks for the mailing list for giving details about myisamchk.we
used them but we got some errors which I have reported in 'myisamchk errors'
mail to mysql.
At present we are working in mysql 3.23.32 ,windows xp os.
Are there any system tables that store mysql related info.(like me
Dear MySQL people
I have a question regarding the error:
InnoDB: Error: tablespace size stored in header is 17024 pages, but
InnoDB: the sum of data file sizes is only 16576 pages
which appeared when I upgraded from 4.0.7 to 4.1.7.
Somehow I am 448 pages (7M) short of table space.
Can I fix
to be autoextended else your application will run
into errors once the data needs to grow pass the tablespace.
Having multiple table spaces on different spindles enable the data to be
segmented a bit more getting a few more bits of speed, but at the
possible detriment of needed to access both sep
Hello!
I have what seems to be a trivial question, but have not been able to
find a definite answer and your help would be greatly appreciated.
Question:
When creating InnoDB table spaces, are there any advantages to using
multi table spaces for each table or is it better to create a few larg
2004 10:41 AM
Aihe: Re: Problem on InnoDB - Tablespace enough but engine said table full
> I try to detect using MC (Midnight Commander) and found that after
;/data4/ibdata25:1802M
>
> it won't write anymore...
>
> I remove these data file and add /ibdata1/ibdata10:1500M and
/data1/ibda
Ady,
- Alkuperäinen viesti -
Lähettäjä: "Ady Wicaksono" <[EMAIL PROTECTED]>
Vastaanottaja: "Ady Wicaksono" <[EMAIL PROTECTED]>; "Heikki Tuuri"
<[EMAIL PROTECTED]>
Kopio: <[EMAIL PROTECTED]>
Lähetetty: Friday, September 03, 2004 10:41
data1/ibdata8:1500M;/data1/ibdata9:1500M;/data4/ibdata25:1802M;/data1/ibdata10:1500M
;/data1/ibdata11:1500M
It's working since i know i have 877184 pages now, later i simply add something like
/data1/ibdata12:1500M
but, i still have error when starting, here is
InnoDB: Error: table
May i know, how could i know which of the data files that InnoDB MySQL engine is not
used ?
Did i i made a mistake when adding table space ?
Heikki Tuuri <[EMAIL PROTECTED]> wrote:
Ady,
InnoDB thinks that the tablespace size is 10 706 MB.
You have specified 36 782 MB of data files
Ady,
InnoDB thinks that the tablespace size is 10 706 MB.
You have specified 36 782 MB of data files in the my.cnf line :(.
Now you should figure out what are the data files that InnoDB is using, and
remove the end of the innodb_data_file_path line, as well as the unused
ibdata files. Remember
nd so on
but said table is full when i try to write data to table
The question is why ?
Secondly
What is the meaning of
InnoDB: Error: tablespace size stored in header is 685184 pages, but
InnoDB: the sum of data file sizes is 235404
David Griffiths writes:
>Oracle cannot shrink datafiles (same idea as InnoDB datafiles) when data
>is deleted either.
Actually, Oracle has been able to resize data files since 7.2. It
is usually done with an 'alter tablespace ... coalesce' followed by an
'alte
In article <[EMAIL PROTECTED]>,
Jeff Mathis <[EMAIL PROTECTED]> writes:
> my understanding is that the datafiles are created when the server
> initializes, and this this is the designed and expected behavior. Most
> other database products use a similar model. Your scenario cannot
> happen. You sp
To: [EMAIL PROTECTED]
Subject: Re: InnoDB TableSpace Question
Oracle cannot shrink datafiles (same idea as InnoDB datafiles) when data
is deleted either.
David
Marc Slemko wrote:
>On Tue, 3 Aug 2004 12:42:03 -0400 , David Seltzer <[EMAIL PROTECTED]>
wrote:
>
>
>>Thanks Marc,
st
a workaround, and there are a lot of disadvantages to that method ...
especially the fact that free space is now per table instead of per
tablespace.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQ
ink if you do an optimize table it will end up shrinking the file
for that table since it will recreate it. However that really is just
a workaround, and there are a lot of disadvantages to that method ...
especially the fact that free space is now per table instead of per
tablespace.
--
MySQL
On Tue, Aug 03, 2004 at 01:08:58PM -0400, [EMAIL PROTECTED] wrote:
>
> I agree with David. If there is no present way to recover unused
> InnoDB tablespace, then we (as a community) seriously need to create
> a tool to do just that. How have we gone so long without it?
Because it&
;
> jeff
> [EMAIL PROTECTED] wrote:
>> I agree with David. If there is no present way to recover unused
>> InnoDB tablespace, then we (as a community) seriously need to create
>> a tool to do just that. How have we gone so long without it? I always
>> assumed it wa
there is no present way to recover unused InnoDB
tablespace, then we (as a community) seriously need to create a tool to do
just that. How have we gone so long without it? I always assumed it was
possible (I guess I have been just lucky enough to not need to do it
yet)
What if, during the
:09 PM
To: David Seltzer
Cc: [EMAIL PROTECTED]
Subject: RE: InnoDB TableSpace Question
I agree with David. If there is no present way to recover unused InnoDB
tablespace, then we (as a community) seriously need to create a tool to do
just that. How have we gone so long without it? I always
I agree with David. If there is no present way to recover unused InnoDB
tablespace, then we (as a community) seriously need to create a tool to do
just that. How have we gone so long without it? I always assumed it was
possible (I guess I have been just lucky enough to not need to do it
yet
it. However that really is just
a workaround, and there are a lot of disadvantages to that method ...
especially the fact that free space is now per table instead of per
tablespace.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
: [EMAIL PROTECTED]
Subject: Re: InnoDB TableSpace Question
On Tue, 3 Aug 2004 10:07:25 -0400 , David Seltzer <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> I've been searching the archives & mysql documentation for a while and I
> can't seem to find an answer to my questio
On Tue, 3 Aug 2004 10:07:25 -0400 , David Seltzer <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've been searching the archives & mysql documentation for a while and I
> can't seem to find an answer to my question -
>
> Is there a way to force InnoDB to shrink its filesize? I just dropped a 7GB
> tab
Hi all,
I've been searching the archives & mysql documentation for a while and I
can't seem to find an answer to my question -
Is there a way to force InnoDB to shrink its filesize? I just dropped a 7GB
table, but it hasn't freed up the disk space and I need it back. From what
I've been reading,
Hi, ( hopefully a MySQL developer sees this at some point! )
I am giving InnoDB a good workout before rolling it out onto
production systems, and found a bug in the way the tablespace gets fragmented
when doing basic add/drop of indexes. Below my sig is a series of SQL
commands I used to
Hi,
I need to manage Innodb Tablespace very effectively from my application. To do that I
require clear picture of Innodb tablespace file and its organization. My application
needs to do the following
1. backup/restore of databases
While doing so should calculate the size of source
Chris,
- Original Message -
From: "Chris Elsworth" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Saturday, February 07, 2004 7:25 PM
Subject: InnoDB Hot Backup & new tablespace format
> Hello,
>
> Does anyone know if InnoDB Hot Backu
Hello,
Does anyone know if InnoDB Hot Backup supports the new tablespace
format being introduced in the latest versions of InnoDB?
I'm quite tempted to switch from MyISAM to InnoDB using the new
tablespace format, but I'm put off by how inflexible InnoDB files seem
to be. I like bei
How about we just all agree that SCO's OSes can't handle large files,
and therefore should all be avoided in favour of completely superior
OSes, like FreeBSD, OpenBSD, Linux, NetBSD and DOS 2.11
Regards,
Chris
Pete Harlan wrote:
On Wed, Nov 05, 2003 at 12:08:29PM +1100, Chris Nolan wrote:
MAIL PROTECTED]>,
Mark Lubratt writes:
I'm considering this option to keep database maintenance to a minimum
(running out of tablespace issues). That way, InnoDB already owns
all
the disk space and I don't have to continually be adding tablespace
files.
Huh? What's wro
On Wed, Nov 05, 2003 at 12:08:29PM +1100, Chris Nolan wrote:
> To my knowledge, ext2 does have the [2GB filesize] limitation but
> ext3 does not.
ext2 does not have this limitation. It was never a limitation of the
filesystem, only kernel/glibc. On 64bit architectures ext2 has been
handling larg
, November 4, 2003, at 10:25 AM, Harald Fuchs wrote:
In article <[EMAIL PROTECTED]>,
Mark Lubratt writes:
I'm considering this option to keep database maintenance to a
minimum
(running out of tablespace issues). That way, InnoDB already owns
all
the disk space and I don't hav
bratt writes:
I'm considering this option to keep database maintenance to a minimum
(running out of tablespace issues). That way, InnoDB already owns
all
the disk space and I don't have to continually be adding tablespace
files.
Huh? What's wrong with ":autoextend"?
:au
On Tue, Nov 04, 2003 at 01:42:23AM -0600, Mark Lubratt wrote:
> I'm considering using the raw tablespace from InnoDB for a project I'm
> working on. I noticed a couple of years ago that there were reports of
> tablespace corruption on Linux and these raw tablespaces. Hav
,
>>>
>>>Mark Lubratt writes:
>>>>I'm considering this option to keep database maintenance to a
>>>>minimum (running out of tablespace issues). That way, InnoDB
>>>>already owns all the disk space and I don't have to continually be
>
at 10:25 AM, Harald Fuchs wrote:
> > In article <[EMAIL PROTECTED]>,
> >
> > Mark Lubratt writes:
> >> I'm considering this option to keep database maintenance to a minimum
> >> (running out of tablespace issues). That way, InnoDB already owns all
On Tuesday, November 4, 2003, at 11:25 AM, Harald Fuchs wrote:
In article <[EMAIL PROTECTED]>,
Mark Lubratt <[EMAIL PROTECTED]> writes:
I'm considering using the raw tablespace from InnoDB for a project I'm
working on. I noticed a couple of years ago that there were
On Tuesday, November 4, 2003, at 10:25 AM, Harald Fuchs wrote:
In article <[EMAIL PROTECTED]>,
Mark Lubratt writes:
I'm considering this option to keep database maintenance to a minimum
(running out of tablespace issues). That way, InnoDB already owns all
the disk space and I do
I'm considering using the raw tablespace from InnoDB for a project I'm
working on. I noticed a couple of years ago that there were reports of
tablespace corruption on Linux and these raw tablespaces. Have these
problems been fixed? I'm considering running it on a hardware RA
Heikki,
Great! Thank you!
Regards,
Eduardo
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 26, 2003 4:31 PM
Subject: Re: Multiple tablespace + subqueries
> Eduardo,
>
> - Original Me
Eduardo,
- Original Message -
From: ""Eduardo D Piovesam"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, September 25, 2003 10:45 PM
Subject: Multiple tablespace + subqueries
> Hello all,
>
> We want to use MySQL (InnoDB) f
On Thu, Sep 25, 2003 at 04:35:29PM -0300, Eduardo D Piovesam wrote:
> Hello all,
>
> We want to use MySQL (InnoDB) for a corporate/non-stop environment, but we
> really want/need multiple tablespace support + subqueries.
>
> When will both be available for a production environm
Hello all,
We want to use MySQL (InnoDB) for a corporate/non-stop environment, but we
really want/need multiple tablespace support + subqueries.
When will both be available for a production environment? Only in 4.1.x? Any
date?
Thank you!
Eduardo
--
MySQL General Mailing List
For list
Vincent Ferretti wrote:
> I need help!
>
> I'm making some testing with innodb tables and there're some issues I
> don't understand.
>
> I created a small tablespace of 10M:
>
>innodb_data_file_path = ibdata1:10M;
>
> Then I created this sim
I need help!
I'm making some testing with innodb tables and there're some issues I
don't understand.
I created a small tablespace of 10M:
innodb_data_file_path = ibdata1:10M;
Then I created this simple database:
CREATE DATABASE trace_db;
use trace_db;
CREATE TAB
Hi MySQL ,
I have made a test database for performance testing
and my InnoDb tablespace grew from 1Gig to 8 Gig...
After I dropped that test database, the tablespace
stayed to the same size. How can I "resize" it to its
original size?
=
-
Benoit St-J
In the last episode (Feb 03), Prasanth Krishna said:
> Is there any concept of Tablespace for MyISAM tables in MySQL? Even
> if it is not present, is there any concept in MySQL which is
> equivalent to Tablespace in Oracle?
MyISAM tables are stored as separate files in the filesyste
Hi all
Is there any concept of Tablespace for MyISAM tables in MySQL?
Even if it is not present, is there any concept in MySQL which is
equivalent to Tablespace in Oracle?
Where could i get the information about it?
Thanks in advance
Prasanth
Shakeel,
- Original Message -
From: "Shakeel Sorathia" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Wednesday, November 13, 2002 9:39 PM
Subject: InnoDB: Error: tablespace size stored in header
> Hi, we're using Innodb here and I just upped the nu
Hi, we're using Innodb here and I just upped the number of datafiles
that innodb was using. When I did a show table status I noticed that I
didn't get all the space that I had added. When I looked at the error
log, I got recieved the following error.
InnoDB: Error: tablespace size
At 14:50 +0200 10/25/02, Natale Babbo wrote:
innodb_data_file_path=ibdata1:100M:autoextended:max:200M
anyone knows what happen if the above innodb
tablespace reach the limit of 200M?
It stops getting bigger. :-)
What do you mean by "what happen"? That is, what are the conditions
1 - 100 of 112 matches
Mail list logo
