| Bug #18199 | PURGE BINARY LOGS fails silently with missing logs | ||
|---|---|---|---|
| Submitted: | 13 Mar 2006 21:01 | Modified: | 5 Apr 2008 16:24 |
| Reporter: | Kolbe Kegel | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.0.18 | OS: | Linux (Linux) |
| Assigned to: | Andrei Elkin | CPU Architecture: | Any |
If the data you need to attach is more than 3MB, you should create
a compressed archive of the data and a README file that describes the data
with a filename that includes the bug number (recommended filename:
mysql-bug-data-18199.zip) and upload one to sftp.oracle.com.
A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com)
and a client that supports SFTP are required in order to access the SFTP server.
To upload the file to sftp.oracle.com:
- Open an SFTP client and connect to
sftp.oracle.com. Specify port2021and remote directory/support/incoming/. - Log in with your newly created Oracle Web account (email address) and password.
- Upload the archive to
/support/incoming. - Once you have uploaded the file, add a comment to this bug to notify us about it.
sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming
Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.
