Move mysql database to another user

The benefit of the doubt...

I agree with Floyd. With me, the benefit of the doubt isn't the issue. The issue is that you've checked everything, but I haven't.

When people hire me and pay me by the hour (at well over a dollar a minute) I always take steps in the order in which I believe I should, even if the admin tells me s/he has already taken those steps.

Over half the time, it's one of those steps that solves the problem.

Those of us with years of experience on fixing problems can generally see the problem immediately, or at least how to test for it, once we see the real details.

Otherwise we're guessing, with even less information than you have. For me that's simply a waste of time I could be using to help other clients, to offer no-cost help on these forums.

My opinion only, of course.

Jeff
 
I agree with Floyd. With me, the benefit of the doubt isn't the issue. The issue is that you've checked everything, but I haven't.

When people hire me and pay me by the hour (at well over a dollar a minute) I always take steps in the order in which I believe I should, even if the admin tells me s/he has already taken those steps.

Over half the time, it's one of those steps that solves the problem.

Those of us with years of experience on fixing problems can generally see the problem immediately, or at least how to test for it, once we see the real details.

Otherwise we're guessing, with even less information than you have. For me that's simply a waste of time I could be using to help other clients, to offer no-cost help on these forums.

My opinion only, of course.

Jeff
I agree with both of you, but you could just ask:
what are the permission for this database?
or
could you run this command (changing USERNAME with the real username)?
and see if I really know what to do.

I never assumed you know the problem I have, so you should assume I at least know the user/db names...
 
Old American saying:

When you ASSUME you make an ASS out of U and ME :).

So let's just use the word presume instead.

I can presume anthing, but I've made the same mistake over and over again myself; but fresh eyes have seen the problem.

My previous post stands as my take.

Besides, it doesn't really matter. If you want Floyd's help, you give him the information he requires. If you want mine, you give me the information I require.

If not, then hopefully someone else will log in and respond to your question. That's the beauty of a community support forum.

Jeff
 
as @floyd says the database "should" (in most situations) be in the format DAusername_databasename - and usually appears in the mysql section of the DA CP. Try this - and see how you go.

If that doesn't solve the problem, then use one of them - they're both really good :)

מזל טוב
 
Without knowing the database name and the new username ...
Code:
old_user_name = bestcoil
new_user_name = heronet
dbname = bestcoil_best
(please don't quote this, so I could remove/delete it later)
 
try chaning the DBName to heronet_best and see if it appears in the mysql management section.
 
try chaning the DBName to heronet_best and see if it appears in the mysql management section.
tried that already - didn't work.
actually it didn't even write the "swapping..." like before...
 
The database name does not match the new username. I don't care if you have already tried it. That is at least part of your problem of the new user not being able to see the database. The new user will never be able to see the database if the database name still uses the old username in it name.

See that is why I require information.
 
The database name does not match the new username. I don't care if you have already tried it. That is at least part of your problem of the new user not being able to see the database. The new user will never be able to see the database if the database name still uses the old username in it name.

See that is why I require information.
I tried it before posting here.
tried it when suggested here.
re-tried it a few seconds ago...

should the new user (db user) & new db exists, or should it be created/moved by the script?
 
If you continue with olduser_databasename then the new user will NEVER see it in DirectAdmin. That is how DirectAdmin determines whole should see what database. That is the number one first thing you have to correct. If you still have a problem after that then we can address those as well. But if you do not change the database name to match the new user then I am done.
 
If you continue with olduser_databasename then the new user will NEVER see it in DirectAdmin. That is how DirectAdmin determines whole should see what database. That is the number one first thing you have to correct. If you still have a problem after that then we can address those as well. But if you do not change the database name to match the new user then I am done.
but that is the problem I'm having.
I've tried the USER, the DBUSER, the USER_DBNAME - none worked...
 
You are stubborn and will not listen to those trying to help you. I am done.
 
You are stubborn and will not listen to those trying to help you. I am done.
we keep misunderstanding each other, I'm not trying to argue with you.
you say something i simply reply that I tried that.
you asked for the names, I gave you the names...
 
And I am trying to to you that changing the database name is the first step in resolving the problem. But you are not willing to do that. I do not care that you tried it already. If you tried it and it did not work then something ELSE is the problem.

"The way of the foolish one is right in his own eyes, but the one listening to counsel is wise."


Until you correctly name the database I am done.
 
And I am trying to to you that changing the database name is the first step in resolving the problem. But you are not willing to do that. I do not care that you tried it already. If you tried it and it did not work then something ELSE is the problem.

"The way of the foolish one is right in his own eyes, but the one listening to counsel is wise."


Until you correctly name the database I am done.
OK, you were right.
manually changing the DBname did the trick.

shouldn't this be taken care of by the script...?
 
shouldn't this be taken care of by the script...?
Do you mean by the script which moves the domain to a different user? If so, then note that this has been discussed previously in this thread.

The script cannot. Because it has no idea which database is required for which domain name.

Jeff
 
Do you mean by the script which moves the domain to a different user? If so, then note that this has been discussed previously in this thread.

The script cannot. Because it has no idea which database is required for which domain name.

Jeff
no I mean the script that moved the DB from one user to the other.
 
I just scanned the entire thread; I can't find that script mentioned. Please post the full pathname of the script.

Jeff
 
I just scanned the entire thread; I can't find that script mentioned. Please post the full pathname of the script.

Jeff
the entire discussion here is about: http://help.directadmin.com/item.php?id=224 (Moving a database to a different user)

and the problem is that the db seem to have moved (in the sense of permissions) but hasn't move logically to appear in the newuser's list of DBs, because of the naming convention: olduser_dbname
 
OK, you were right.
manually changing the DBname did the trick.

shouldn't this be taken care of by the script...?

try chaning the DBName to heronet_best and see if it appears in the mysql management section.

as @floyd says the database "should" (in most situations) be in the format DAusername_databasename - and usually appears in the mysql section of the DA CP. Try this - and see how you go.

If that doesn't solve the problem, then use one of them - they're both really good :)

מזל טוב

I dont know how many times we had to tell you :cool:
 
Back
Top