How do I use MySQL Binlog for PITR [closed] - mysql

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 24 days ago.
Improve this question
I am attempting to recover lost data using mysqlbinlog. Admittedly I am far from an expert in using MySQL, and even farther when using command line, so any advise would be very very welcome. I've seen so many docs that say what to do to view the binlogs, but it does not work at all on my machine. What am I doing wrong here?
This is exactly what happens every time
I've tried running this multiple times. I've also tried listing out the path to the binlog file in that Data folder.
Update: Same thing happens when using MySQL Shell

Run the mysqlbinlog command at a shell prompt, not in the MySQL client.

Related

Cannot login into Phpmyadmin (user/pass is correct) [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I'm trying to login into my phpmyadmin but it keep getting redirected to the login page. I know user and password are correct because my website is still working properly and I can even connect to mysql using putty.
I noticed I'm getting "Cant create/write to file '/tmp/XXXXXXX' Errcode28" on one of my tables which apparently means lack of disk space so I deleted all the rows but it didn't resolve the issue.
I used df -h command and it says I have only used 13% of /dev/vdal1.
I don't even know where to start. Has anyone experienced this before?
Ok for all those out there feeling helpless like me here is the solution:
SSH to your server
type df -i to see if your inode usage is full if yes
type cd/
type this:echo -e "Inode count forpwd:\n"; /bin/ls -A|awk '{print "count=find \""$0"\"|wc -l; echo \""$0" \t\t $count\""}'|sh|awk '$NF != "1" {inode=$NF;$NF="";print "printf \"%-50s %8d\\n\" \""$0"\" \""inode"\""}'|sh && printf "%-50s %8d\n" "Total:" "find ${pwd}|wc -l"
this shows you which directory is using that space the most.
cd into that directory and repeat step 4 and 5 until you get to the directory that has the highest usage
clear as much as you can in that directory
reboot
enjoy :)

Is it OK to copy DB files from one MySQL server to another? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have two identically configured MySQL 5.6.10 servers and needed to move the data files fast from one to the other. Is this an OK procedure?
Here is what I did:
1) Shut down both servers
2) Moved all the files from one box to the other (DATA is on a separate drive on both machines)
3) Turned the second server on
4) Connected it back to the app server
It took about 5 minutes to move all files (~50GB) and all seems to work. I just wonder if I missed anything?
Thanks much for your feedback.
If both the server versions are same, then I think, it's perfectly fine, not just OK, as I have done the same many times, without any data loss, but this method comes with cost:
You have to shut down mysql server (which is not good, if it's a production server)
You have to make sure the permission of data (mysql) directory is same as the previous one.
You will have to monitor the mysql_error log while starting the second server.
You can use mysqldump, but if you don't want to, then you can use Mysql Workbench's migration wizard, it really takes care of everything.
A much safer and recommended way would be Database Backup And Recovery.
Do a full backup from server1 and restore it to server2. Later then on, you can go for a differential backup.

Restore MySQL Database from another server, will it affect current databases? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Morning, we have 8 databases on our live server. I have created a new one on our test/development server. In MySQL Administrator I've backed up this new database to an SQL file, this file is on the new server. If I use "restore" in MySQL Administrator to create this database, will it affect the other databases that are there or will they carry on working as normal?
Is there a better way to do this?
The new DB is only a few k in size, the others contain many years of info and data and are huge. Any help appreciated
No, it won't. As you said that your DB is small it will not affect at all the other DB. It would if it was bigger, most probably it would slow dow your server a bit during the import (if it was bigger, huge to be precise), after the import the database will work normally. Of course it will share resource to keep one more instance working. And with time, it will make some difference in performance (depending on how big this DB grow). But you will have to be more concerned with hardware capabilities then the database itself.
Of course, I assume that when you say database you are saying about a new instance on your database.

To store data in mySQL using editText android [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
I have a concepts of storing a data in mySQL using editText(ie, UserName and Password), But i'm not having any idea how to proceed, Could anyone send me a link for above.. Thanks in advance
first of all, Android doesnt support mySql, it supports SQLite. Read about SQLiteOpenHelper to get some overview on this.
If you want to use an outter database which works on mySql, you need to create some sort of php API that will handle your requests
Without using the web server you can't even think about Database server.

ejabberd mysql script bug? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Hihi, not sure if i am just plain dumb.. Have installed ejabberd on amazon ec2 and recently managed to switch to use mysql based on the guide: https://support.process-one.net/doc/display/MESSENGER/Using+ejabberd+with+MySQL+native+driver
I have an issue now after switching to mysql db, not able to add roster to my user, and the log shows that the table rosterusers does not exist.
And now I am confusing, I grabbed the mysql.sql db schema from ejabberd github at https://github.com/processone/ejabberd/blob/master/src/odbc/mysql.sql, and found that
there isn't any rosterusers table to be created, instead, it creates a table called rosteritem.
there isn't any table called rostergroups, but rostergroup (without 's'). After some googling around, i think rostergroups should be the correct naming.
Is there anyone here knows is this a bug in the mysql schema, or i am missing something?
Thanks in advance!
I have not gotten any feedback regarding this question, but eventually, I have manually changed some of the table schema created from the mysql.sql script to matched the one from mssql.sql.
Everything works fine thereafter!
:)