Mysql assigns its session IDs sequentially as they come in. I suspect, however,
that you're looking for session IDs as used by websites -generation of those is
entirely not a mysql issue, it is only a potential store for them.
Steven Siebert wrote:
>Hello all,
>
>I've looked though, what I beli
Am 20.06.2013 23:47, schrieb Peter:
>> Hello,
>>>
>>> I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
>>> database directory) from one crashed machine to another.
>>> I find that I cannot start database to get the database data any more.
>>
>>
>>> How did you copy the d
>Hello,
>>
>>I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
>>database directory) from one crashed machine to another.
>>I find that I cannot start database to get the database data any more.
>
>
>>How did you copy the database?
>>Manuel
>
>I copy the files ib_logfile
#sql files are temp tables that vanish when the ALTER (or whatever) finishes.
If you find one sitting around, it sounds like a crash happened in the middle
of the ALTER.
> -Original Message-
> From: Reindl Harald [mailto:h.rei...@thelounge.net]
> Sent: Wednesday, June 19, 2013 12:19 PM
i know what happened but how get rid of these two bullshit files
after *three years* not touched and used by mysqld
Am 20.06.2013 21:28, schrieb Rick James:
> #sql files are temp tables that vanish when the ALTER (or whatever) finishes.
> If you find one sitting around, it sounds like a crash ha
On Thu, Jun 20, 2013 at 3:28 PM, Rick James wrote:
> #sql files are temp tables that vanish when the ALTER (or whatever)
> finishes. If you find one sitting around, it sounds like a crash happened
> in the middle of the ALTER.
Yes the crash happened during an ALTER: the table `logs/#sql-ib203`
On Thu, Jun 20, 2013 at 7:13 AM, Denis Jedig wrote:
>
> If you already tried enclosing the table name in backticks (DROP TABLE
> `#sql-ib203`) and using the DROP TEMPORARY TABLE syntax without success,
Yep, no success with:
DROP TEMPORARY TABLE `logs/#sql-ib203`;
DROP TEMPORARY TABLE `/#sql-ib20
Hello all,
I've looked though, what I believe to be, the relevant areas in the MySQL
docs as well as standard search engine searches without luck. I was
hoping to find some documentation that would tell me:
- how MySQL session Ids are generated (specifically, are they considered
"random")
- do
This may be a naive question, but I'm not sure I can see you've covered
this: Have you tried "USE logs" before DROP TABLE `#sql-ib203` (without
the "logs/" bit)?
/ Carsten
On 19-06-2013 21:00, Franck Dernoncourt wrote:
Hi all,
A table `logs/#sql-ib203` appeared after a MySQL crash due to dis
2013/6/20 Peter
>
>2013/6/20 Peter
>
>Hello,
>>
>>I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
>>database directory) from one crashed machine to another.
>>I find that I cannot start database to get the database data any more.
>
>
>>How did you copy the databa
Am 20.06.2013 15:18, schrieb Peter:
>>
>>> I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
>>> database directory) from one crashed machine to another.
>>> I find that I cannot start database to get the database data any more.
>
>>> How did you copy the database?
>>> M
Am 20.06.2013 15:18, schrieb Peter:
>>
>>> I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
>>> database directory) from one crashed machine to another.
>>> I find that I cannot start database to get the database data any more.
>
>>> How did you copy the database?
>>>
2013/6/20 Peter
>
> 2013/6/20 Peter
>
> Hello,
>
> I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
> database directory) from one crashed machine to another.
> I find that I cannot start database to get the database data any more.
>
>
> >How did you copy the database?
>
2013/6/20 Peter
Hello,
>
>I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
>database directory) from one crashed machine to another.
>I find that I cannot start database to get the database data any more.
>How did you copy the database?
>Manuel
I copy the files ib_lo
Am 20.06.2013 15:18, schrieb Peter:
> 2013/6/20 Peter
>
> Hello,
>>
>> I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
>> database directory) from one crashed machine to another.
>> I find that I cannot start database to get the database data any more.
>
>> How did y
Franck,
Am 19.06.2013 21:00, schrieb Franck Dernoncourt:
A table `logs/#sql-ib203` appeared after a MySQL crash
the #sql-ib tables are temporarily created during an
ALTER TABLE operation for recovery purposes. Apparently these
temporary tables might stay in certain circumstances even after
2013/6/20 Peter
> Hello,
>
> I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
> database directory) from one crashed machine to another.
> I find that I cannot start database to get the database data any more.
How did you copy the database?
Manuel
Am 20.06.2013 10:11, schrieb Peter:
> 130620 00:47:08 mysqld_safe Starting mysqld daemon with databases from
> /var/lib/mysql
> InnoDB: Error: tablespace size stored in header is 456832 pages, but
> InnoDB: the sum of data file sizes is only 262080 pages
> InnoDB: Cannot start InnoDB. The tail o
Hello,
I copied innodb database (ib_logfile0 ib_logfile1 ibdata1 and the whole
database directory) from one crashed machine to another.
I find that I cannot start database to get the database data any more.
I tried innodb_force_recovery=1
or innodb_force_recovery=4, it doesn't help.
Here is th
19 matches
Mail list logo
