Hi, Elena,

Aha! I think you've got it!

That database, miketest, is the old one which was damaged.

So, if I just remove that folder and its contents, do you think that will fix the problem?

In which case, I may need some help removing it because, as I remember, I left it there because I had trouble deleting it.

This also raises some other questions: If I were to develop the database on a different computer (my notebook, on which MariaDB now is working), then how could I move it onto the client's computer? What files would need to be moved, and how would I reset the password? Are there other considerations as well? Also, can you lead me toward on-line answers re any of these questions?

I am very glad that this project is looking more hopeful.

Thank you, thank you.

--Jill Miller

Hi Jill,

>> So, if I just remove that folder and its contents, do you think that will fix the problem?

No, I think it might make the situation worse, that's exactly the kind of thing that would cause similar problems in the first place.

For fixing it, your best shot is reading the article at the link that I posted above carefully and trying to apply it to your situation. It won't work 'as is", you'll have to adjust it. Unfortunately, there is no way to create a generic instruction for resolving it, because when it comes to this kind of damage/corruption, every case is unique and requires an individual approach. It's the same as with any application, basically – if you tamper with internal structures, you should expect problems which are not covered in the standard "user guide". If you can't fix it on your own, you might have to consider getting support involved.

>> If I were to develop the database on a different computer (my notebook, on which MariaDB now is working), then how could I move it onto the client's computer?
>> What files would need to be moved, and how would I reset the password? Are there other considerations as well? Also, can you lead me toward on-line answers re any of these questions?

If you want to copy the entire database, the whole datadir, including system tables and everything, it should be as simple as shutting down your server properly, removing the whole datadir on the client machine and placing your entire datadir instead. You would reset the password in the usual way, as you always do, right before copying the datadir.

If you only want to copy certain schema (or some of them), there are guidelines for copying/moving tables between machines in MySQL manual:
http://dev.mysql.com/doc/refman/5.5/en/innodb-migration.html
http://dev.mysql.com/doc/refman/5.6/en/innodb-migration.html
These links point at the same page in 5.5 and 5.6 manuals, correspondingly. Even though you are on 5.5, you should read the 5.6 page as well, it contains more information which is partially applicable to 5.5 too.
For non-InnoDB tables, you can also search the manual.
As long as you don't copy system tables, you shouldn't worry about the password since it won't be copied anyway.

Hi, Elena,

Hi Jill,

>> So, if I just remove that folder and its contents, do you think that will fix the problem?
> No, I think it might make the situation worse, that's exactly the kind of thing that would cause similar problems in the first place.

Now you have scared me. I am NOT a mysql administrator and, although I used to be a machine language programmer, that was many, many years ago. I had trouble setting a password for myself in mariadb, so I could use the 'create database' command to have a database to connect to with LibreOffice Base.

>> If I were to develop the database on a different computer (my notebook, on which MariaDB now is working), then how could I move it onto the client's computer?
>> What files would need to be moved, and how would I reset the password? Are there other considerations as well? Also, can you lead me toward on-line answers re any of these questions?
> If you want to copy the entire database, the whole datadir, including system tables and everything, it should be as simple as shutting down your server properly, removing the whole datadir on the client machine and placing your entire datadir instead. You would reset the password in the usual way, as you always do, right before copying the datadir.
Because the MariaDB installation went bad before I got much work done in it, I removed everything and started over again. It is fortunate that I had all the initial data in spreadsheets and don't have to type it all in.

I am now working on doing the (re)programming of the database which is more like my area of expertise. As you can see, I have a LOT of holes in my knowledge. It would be very nice if I could find a support group or mysql/mariadb and LibreOffice Base gurus nearby. Do you know of any group in the Boston, Massachusetts area?

Thank you again, from
--Jill Miller <[1]Jill@millermicro.com>

Hi Jill,

>> I am now working on doing the (re)programming of the database which is more like my area of expertise. As you can see, I have a LOT of holes in my knowledge. It would be very nice if I could find a support group or mysql/mariadb and LibreOffice Base gurus nearby. Do you know of any group in the Boston, Massachusetts area?

Sorry did not see the question before, formatting went rogue.
I don't know anything about groups in the USA, but if you are still interested, you might try to send the question to maria-discuss@lists.launchpad.net, maybe there are people who have information on the subject.

All in all, the initial problem should be solved together with MDEV-5252.