UBB.threads PHP Forum Software Community Forums UBB.threads 7 Bug Reports Non Bugs [NOTABUG] Accessing Topic Error

I am receiving this error message when trying to access topics:


Is there a MySql command for rebuilding topics?

It seems to be a topic_views field problem.

Is there a command for rebuilding that field?

Will the repair field command fix the problem?

I tried the repair command and received the following error message:

I am at a loss on what to do next.

What kind of file is that?

I tried creating a new file to test out this viewing problem, however, I received the following error message instead:

I guess I have no other choice now but to wait until somebody here is able to help me as it all seems to impact on this missing ubbt_TOPIC_VIEWS.MYD file.

In the meantime I have closed down my board/forum.

I discovered one topic that I can read, however, when I reply to it I receive the following error message:

The strange thing though is that when I hit my back button, I can see the new post, but, so far, this only works in this one topic, which, so far, is the only topic I can view.

I do hope somebody will be able to tell me exactly what to do in relation to this missing ubbt_TOPIC_VIEWS.MYD file, which seems to be causing the whole mess.

I looked at my fields and this is what I see:

The one causing me all the problem is saying "in use" rather than "MyISAM" like the rest of the fields are also showing.

What does "in use" mean in relation to all of the others?

MySQL databases are stored as flatfiles on the system; where the table "ubbt_TOPIC_VIEWS" has the flat file "ubbt_TOPIC_VIEWS.MYD" that holds the information on the server.

The erorr message is stating that the table is missing from the server; not sure why, or how, this would be missing however...

How can I correct this?

It also says this field is "in use" with zero rows.

What does that mean?

Is this a problem that only Rick can solve for me?

I have no idea the cause, the original error message indicates the myd file isnt where it's supposed to be; so one would lead to think that something was deleted on the server somehow; has your host by chance disabled MySQL for your server?

Really grasping at straws here, I googled the error message and found a thread on a site stating that their host had disabled MySQL and had a similar error...

You could try the standard mysql tools, try to repair the table, and all that fun jazz...

Daryl,

Can you promote me to admin on your site. I'd like to login and do a couple database queries.

Will do.

You are now an Admin there.

Everything else in MySql works.

Even one topic is accessible in a weird sort of way.

Ok, give it a shot now. Since this table is just a temporary table I just did the following:

delete from ubbt_TOPIC_VIEWS

and then

repair table ubbt_TOPIC_VIEWS

Will do.

Working OK now.

I wish I had your knowledge.

Do you know what caused the problem in the first place?

It's hard to say. It's a table that does get accessed quite frequently, each time someone views a topic. We may try moving this to a table that just resides in memory instead of being written to disk.

Well, if it happens to somebody else, they can look at this topic to see how they can fix it.

Thank you once again.

This problem has happened again, except it has also closed everything down including the Control Panel.

I am getting the following message when trying to access the forums:


When I try accessing the Control Panel, I get the following message:


It looks like things will need to be corrected by going to the server itself via phpMyAdmin.

error 127 is a crashed table. YOu can try to repair by running the following sql command via phpmyadmin

REPAIR table ubbt_CACHED_PERMISSIONS

Will do.

I can also drop the table and do the repair table command for the ubbt_TOPIC_VIEWS ???

Yes, I noticed both are saying in use.

I will do the topics one first and then the other one.

Yeah, you can repair the ubbt_TOPIC_VIEWS the same way as earlier. We are going to move this to a memory table in 7.1 that should stop these problems.

Everything is working again.

Thank you.

I am slowly learning a lot on all of this.

I may even be a pro someday.

constantly break things, like us, and soon you'll be runnin the place hehe...

I need help on this again.

I dropped the ubbt_TOPIC_VIEWS table using MySql, however, when I do the repair table ubbt_TOPIC_VIEWS command it tells me the table no longer exists.

What now?

You can't just drop the table. Now you will need to create table nameoftable;

Think you were just supposed to repair it.
http://dev.mysql.com/doc/refman/5.0/en/repair-table.html

I don't know enough of the internal workings of the board code to help you out much more than that.

Hopefully someone with more experience or knowledge will stop by soon to give you further advice.
 

I am trying to create the ubbt_TOPIC_VIEWS table again.

Can somebody give me the exact command here to do that with the proper number of columns, etc.???

Thank you in advance.

I dropped it before and did the repair command without any problem which you can read about earlier in this topic.

I am having a problem now though.

I know Rick could help me very quickly, if he were on here now.

Hopefully, somebody in the know will be able to help me really, really soon.

mysql> describe ubbt_TOPIC_VIEWS;
+----------+------------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+----------+------------------+------+-----+---------+-------+
| TOPIC_ID | int(11) unsigned | NO | MUL | | |
+----------+------------------+------+-----+---------+-------+

mysql> show tables;
+------------------------------+
| Tables_in_ubbt7 |
+------------------------------+
| ubbt_address_book |
| ubbt_admin_searches |
| ubbt_announcements |
| ubbt_banned_emails |
| ubbt_banned_hosts |
| ubbt_cache |
| ubbt_cached_permissions |
| ubbt_calendar_events |
| ubbt_categories |
| ubbt_censor_list |
| ubbt_display_names |
| ubbt_files |
| ubbt_forum_last_visit |
| ubbt_forum_permissions |
| ubbt_forums |
| ubbt_graemlins |
| ubbt_groups |
| ubbt_import_map |
| ubbt_languages |
| ubbt_mailer |
| ubbt_member_searches |
| ubbt_moderator_notifications |
| ubbt_moderator_permissions |
| ubbt_moderators |
| ubbt_online |
| ubbt_poll_data |
| ubbt_poll_options |
| ubbt_poll_votes |
| ubbt_portal_boxes |
| ubbt_posts |
| ubbt_private_message_posts |
| ubbt_private_message_topics |
| ubbt_private_message_users |
| ubbt_ratings |
| ubbt_registration_fields |
| ubbt_reserved_names |
| ubbt_rss_feeds |
| ubbt_saved_queries |
| ubbt_search_results |
| ubbt_shout_box |
| ubbt_styles |
| ubbt_topic_views |
| ubbt_topics |
| ubbt_user_data |
| ubbt_user_groups |
| ubbt_user_notes |
| ubbt_user_profile |
| ubbt_user_titles |
| ubbt_users |
| ubbt_version |
| ubbt_watch_lists |
+------------------------------+
51 rows in set (0.02 sec)

Link here for creating the table

http://dev.mysql.com/doc/refman/5.0/en/create-table.html
 

That is quite complicated.

All I am looking for is the command line/info specific to this particular table, which you could look up for me in your own database for this particular table.

Ian,

I hope you can help me here as I see you are online.

Thank you Ian for the command line information, which I am also placing here, just in case somebody else has this type of problem.

Here ya go. We'll just go ahead and create this as a heap table as 7.1 will do which should stop the corruption:

create table ubbt_TOPIC_VIEWS (
TOPIC_ID int(11) unsigned not null,
index topic_ndx (TOPIC_ID)
) TYPE=heap

I forgot to edit the table into that quote, therefore, thank you for correcting that oversight.

I will also now do the alter command and see what happens.

Sorry to leave you hanging Daryl. I was on my way out when I replied to some of your requests.

Glad to see it looks like you've got it back under control again.


Rick is this something to do with PHP coding? It's not normal for a table to get corrupted especially on modern hardware.

It was the third time for me in regards to a corrupted table, and the same corrupted table at that.

I am now in "heap" mode, therefore, we will see how that goes.

Corruption can happen to tables that are updated frequently. Since every update requires a write to the table, sometimes tables can become corrupted especially on slower hard drives. The TOPIC_VIEWS table is updated every time someone views a topic so it is an extremely active table.

Since this table only stores temporary data, we can convert it to a heap table so it doesn't write it to disk, it just stores it in memory, which should stop the corruption.

I am still having the problem from last evening, therefore, I thought I would place it here as it seems to be related somewhat.

The ubbt_POSTS table isn't working.

My server provider tried repairing it, but received this error:


Is this a temporary table that the delete from ubbt_POSTS command can be used followed by the repair table ubbt_POSTS command?

From what I have read, it doesn't sound like a temporary table.

What can be done next?

Is this something only Rick can answer?

I will be gone for a few hours, but I will check back here and elsewhere after I return.

I tried the delete from command which gave a failed message pertaining to zero rows.

I then tried the repair command that said:


It seems that they tried to do the same thing.

What is really needed is a _forums/ubbt_POSTS.MYD file.

From the database it is saying ubbt_POSTS in use, which is exactly what the ubbt_TOPIC_VIEWS used to say before it was altered to HEAP.

I sure do hope Rick will be on here soon as it has been over 24 hours since this happened.

What would happen if I tried the following command?

create file ubbt_POSTS.MYD ???

Or is this even a valid command?

Talked with you via your PM, Daryl.

I also just now answered you there.