XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Modules Support forums / 
  3. Module usage questions 
  4.  / Got error 134 from storage engine
Register
11
xgarb
Re: Got error 134 from storage engine

  • 2007/7/21 13:38

  • xgarb

  • Not too shy to talk

  • Posts: 154

  • Since: 2003/3/30


so now the question is.. will my site slow down if I remove topic_id from the topicid_uid key?



topicid_uid INDEX 49965 topic_id uid

topicid_postid_pid INDEX 99930 topic_id post_id pid
12
DarinAllan
Re: Got error 134 from storage engine

I started getting this message after I upgraded my hosting to PHP5 MYSQL5 server. There doesn't seem to be a clear answer of what to do for us Database shy xoopers lol.

My forum doesn't seem to be affected from a user point of view everything still works, though for instance when I hit Sync Forums in Admin I get the error message 134.

I could just see myself screwing the database if I tried to fix it!

I will continue to read this thread I guess ;o)
13
script_fu
Re: Got error 134 from storage engine

bump
14
allnewtome
Re: Got error 134 from storage engine

  • 2007/9/1 16:40

  • allnewtome

  • Not too shy to talk

  • Posts: 175

  • Since: 2005/11/30


I have XOOPS 2.0.16 and have just upgraded from cbb 3.0.4 to 3.0.8. Php 5 and MySQL 5.

I also saw the "error 134 from storage engine" when upgrading. It still said "upgraded successfully" - and appears to work OK.

Any error message worries me. What should I do?

(I will upgrade to 2.0.17 once the problems with that release have been ironed out, but I am upgrading my modules now.)

Thanks!
15
terrion
Re: Got error 134 from storage engine

  • 2007/9/12 0:34

  • terrion

  • Friend of XOOPS

  • Posts: 299

  • Since: 2004/9/19


I continue getting these errors too:

More than one INDEX key was created for column `forum_id`
More than one INDEX key was created for column `topic_id`

Any new advice?
Terrion
Purchase, renew, or transfer your domain name to Ultranet Domains and get a FREE 10GB hosting account. Virtual Dedicated Servers around $35/monthly, no contract. FREE 24/7 telephone ...
16
Will_H
Re: Got error 134 from storage engine

  • 2007/9/15 1:59

  • Will_H

  • Friend of XOOPS

  • Posts: 1786

  • Since: 2004/10/10


I just fixed mine in about 5 minutes.

CBB tables are not the only ones affected either.

Basically I just dropped the ones that combined values already set, and removed fields from the ones that were combined.

I have not ran into a problem yet.

Example: _bb_topics
PRIMARY       PRIMARY       27        Edit        Drop        topic_id
forum_id     INDEX     None      Edit     Drop     forum_id
topic_last_post_id     INDEX     None      Edit     Drop     topic_last_post_id
topic_poster     INDEX     None      Edit     Drop     topic_poster
topic_forum     INDEX     None      Edit     Drop     topic_id
forum_id
topic_sticky     INDEX     None      Edit     Drop     topic_sticky
topic_digest     INDEX     None      Edit     Drop     topic_digest
digest_time     INDEX     None      Edit     Drop     digest_time
PRIMARY and INDEX keys should not both be set for column `topic_id`


Changed to
PRIMARY       PRIMARY       30        Edit        Drop        topic_id
forum_id     INDEX     None      Edit     Drop     forum_id
topic_last_post_id     INDEX     None      Edit     Drop     topic_last_post_id
topic_poster     INDEX     None      Edit     Drop     topic_poster
topic_sticky     INDEX     None      Edit     Drop     topic_sticky
topic_digest     INDEX     None      Edit     Drop     topic_digest
digest_time     INDEX     None      Edit     Drop     digest_time


0 errors after doing this to all tables

For god sakes back it up first.

My old topics didn't come back, but I think by dumping that table and reinjecting the data it should repopulate.
17
cripperz
Re: Got error 134 from storage engine

  • 2008/1/24 18:08

  • cripperz

  • Just popping in

  • Posts: 2

  • Since: 2006/10/31


hey all,

im just a newbie around trying out these stuff. somehow, im just lucky to solve my 134 error recently. here's my share of these issue,

check out http://cripperz.sg/members/modules/newbb/viewtopic.php?topic_id=25&post_id=32#forumpost32

cheers guys.. pls feedback if it does work for you ppl.
18
bilgikolik
Re: Got error 134 from storage engine

  • 2008/3/26 13:54

  • bilgikolik

  • Just popping in

  • Posts: 27

  • Since: 2007/10/8


i have this eror :(
it be in i updating 2.0.18 to 2.3 alpha 1. i do its but not clean eror :( Help me!!
i'm not speak english well :P sory for my erors :P
« 1 (2)

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

236 user(s) are online (205 user(s) are browsing Support Forums)

Members: 0

Guests: 236

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits