Optional Offer for WinThruster by Solvusoft Overview of SQLPLUS.EXE What Is SQLPLUS.EXE? SQLPLUS.EXE is a type of EXE file associated with Enterprise Edition developed by Oracle for the Windows Operating System. The latest known version of SQLPLUS.EXE is 1.0.0.0, which was produced for Windows. This EXE file carries a popularity rating of 1 stars and a security rating of 'UNKNOWN'. What Are EXE Files? EXE ('executable') files, such as SQLPLUS.EXE, are files that contain step-by-step instructions that a computer follows to carry out a function.
When you 'double-click' an EXE file, your computer automatically executes these instructions designed by a software developer (eg. Oracle) to run a program (eg. Enterprise Edition) on your PC. Every software application on your PC uses an executable file - your web browser, word processor, spreadsheet program, etc. making it one of the most useful kinds of files in the Windows operating system.
The Oracle website is confusing to navigate After reading closer this download maybe the one you need. Oracle Database 10g Release 2 (10.2.0.4.0) Enterprise/Standard Edition for Microsoft Windows Vista x64 and Microsoft Windows Server 2008 x64.
Without executable files like SQLPLUS.EXE, you wouldn't be able to use any programs on your PC. Why Do I Have EXE Errors? Because of their usefulness and ubiquity, EXE files are commonly used as a method of delivery for virus / malware infection. Often, viruses will be disguised as a benign EXE file (such as SQLPLUS.EXE) and distributed through SPAM email or malicious websites, which can then infect your computer when executed (eg. When you double-click the EXE file).
In addition, viruses can infect, replace, or corrupt existing EXE files, which can then lead to error messages when Enterprise Edition or related programs are executed. Thus, any executable files that you download to your PC should be scanned for viruses before opening - even if you think it is from a reputable source. When Do EXE Errors Occur?
EXE errors, such as those associated with SQLPLUS.EXE, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. Common SQLPLUS.EXE Error Messages The most common SQLPLUS.EXE errors that can appear on a Windows-based computer are:. 'SQLPLUS.EXE Application Error.' . 'SQLPLUS.EXE is not a valid Win32 application.' .
'SQLPLUS.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.' . 'Cannot find SQLPLUS.EXE.' . 'SQLPLUS.EXE not found.' .
'Error starting program: SQLPLUS.EXE.' . 'SQLPLUS.EXE is not running.' . 'SQLPLUS.EXE failed.'
. 'Faulting Application Path: SQLPLUS.EXE.' These EXE error messages can appear during program installation, while a SQLPLUS.EXE-related software program (eg. Enterprise Edition) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your SQLPLUS.EXE error occurs is a critical piece of information in troubleshooting the problem. Recommendation: Optional Offer for WinThruster by Solvusoft Causes of SQLPLUS.EXE Errors SQLPLUS.EXE problems can be attributed to corrupt or missing files, invalid registry entries associated with SQLPLUS.EXE, or a virus / malware infection. More specifically, these SQLPLUS.EXE errors can be caused by:.
Corrupt Windows registry keys associated with SQLPLUS.EXE / Enterprise Edition. Virus or malware infection that has corrupted the SQLPLUS.EXE file or related Enterprise Edition program files. Another program maliciously or mistakenly deleted SQLPLUS.EXE-related files. Another program is in conflict with Enterprise Edition and its shared referenced files.
Corrupt download or incomplete installation of Enterprise Edition software. Caution: We do not recommend downloading SQLPLUS.EXE from 'EXE download' sites. These sites distribute EXE files that are unapproved by the official SQLPLUS.EXE file developer, and can often be bundled with virus-infected or other malicious files. If you require a copy of SQLPLUS.EXE, it is recommended that you obtain it directly from Oracle. Below is a list of troubleshooting steps to resolve your SQLPLUS.EXE problems. These troubleshooting steps get progressively more difficult and time consuming, so we strongly recommend attempting them in ascending order to avoid unnecessary time and effort. Please Note: Click the image to expand the troubleshooting instructions for each step below.
You can also click the image to hide the instructions as you proceed through each step. Sometimes SQLPLUS.EXE and other EXE system errors can be related to problems in the Windows registry. Several programs can share the same SQLPLUS.EXE file, but when these programs are uninstalled or changed, sometimes 'orphaned' (invalid) EXE registry entries are left behind. Basically, what this means is that while the actual file path may have changed, its incorrect former location is still recorded in the Windows registry. When Windows tries looking up these incorrect file references (file locations on your PC), SQLPLUS.EXE errors can occur. In addition, malware infection may have corrupted the registry entries associated with Enterprise Edition.
Thus, these invalid EXE registry entries need to be repaired to fix the root of the problem. Manually editing the Windows registry to remove invalid SQLPLUS.EXE keys is not recommended unless you are PC service professional. Incorrectly editing your registry can stop your PC from functioning and create irreversible damage to your operating system. In fact, one misplaced comma can prevent your PC from booting entirely! Because of this risk, we highly recommend using a trusted registry cleaner such as (Developed by Microsoft Gold Certified Partner) to scan and repair any SQLPLUS.EXE-related registry problems. Using a automates the process of finding invalid registry entries, missing file references (like the one causing your SQLPLUS.EXE error), and broken links within the registry.
A backup is automatically created before each scan, with the ability to undo any changes in a single click, protecting you against the possibility of PC damage. The best part is that can also dramatically improve system speed and performance. Caution: Unless you an advanced PC user, we DO NOT recommend editing the Windows registry manually.
Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. We do not guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to SQLPLUS.EXE (eg. Enterprise Edition):. Click the Start button.
Type ' command' in the search box. DO NOT hit ENTER yet!.
While holding CTRL-Shift on your keyboard, hit ENTER. You will be prompted with a permission dialog box. A black box will open with a blinking cursor. Type ' regedit' and hit ENTER.
In the Registry Editor, select the SQLPLUS.EXE-related key (eg. Enterprise Edition) you want to back up. From the File menu, choose Export. In the Save In list, select the folder where you want to save the Enterprise Edition backup key. In the File Name box, type a name for your backup file, such as 'Enterprise Edition Backup'. In the Export Range box, be sure that ' Selected branch' is selected. Click Save.
The file is then saved with a.reg file extension. You now have a backup of your SQLPLUS.EXE-related registry entry. The next steps in manually editing your registry will not be discussed in this article due to the high risk of damaging your system. If you would like to learn more about manual registry editing, please see the links below. Tip: If you do not already have a malware protection program installed, we highly recommend using Emsisoft Anti-Malware. They offer a malware removal guarantee that is not offered by other security software. Over time, your computer accumulates junk files from normal web surfing and computer use.
If this junk isn't occasionally cleaned out, it can cause Enterprise Edition to respond slowly or provides an SQLPLUS.EXE error, possibly due to file conflicts or an overloaded hard drive. Cleaning up these temporary files with Disk Cleanup might not only solve your SQLPLUS.EXE error, but can also dramatically speed up the performance of your PC.
Tip: Although Disk Cleanup is a wonderful built-in tool, it will not completely clean up all of the temporary files on your computer. Other programs that you frequently use such Microsoft Office, Firefox, Chrome, Live Messenger, and hundreds of other programs are not cleaned up with Disk Cleanup (including some Oracle programs). Because of the shortcomings of the Windows Disk Cleanup (cleanmgr) tool, we highly recommend using a specialized hard drive cleanup / privacy protection software such as (Developed by Microsoft Gold Partner) to clean up your entire computer.
Running once per day (using automatic scanning) will ensure that your computer is always clean, running fast, and free of SQLPLUS.EXE errors related to temporary files. How to run Disk Cleanup (cleanmgr) (Windows XP, Vista, 7, 8, and 10):. Click the Start button. Type ' command' in the search box. DO NOT hit ENTER yet!.
While holding CTRL-Shift on your keyboard, hit ENTER. You will be prompted with a permission dialog box. A black box will open with a blinking cursor. Type ' cleanmgr' and hit ENTER. Disk Cleanup will begin calculating how much occupied disk space you can reclaim.
The Disk Cleanup dialog box will appear with series of checkboxes you can select. In most cases, the 'Temporary Files' category will occupy the most disk space. Check the boxes of the categories you want to clean and click OK.
SQLPLUS.EXE errors can be related to corrupt or outdated device drivers. Drivers can work one day, and suddenly stop working the next day, for a variety of reasons. The good news is that you can often update the device driver to fix the EXE problem. Finding the exact driver for your SQLPLUS.EXE-related hardware device can be extremely difficult, even directly on the Oracle or related manufacturer's website. Even if you are experienced at finding, downloading, and manually updating drivers, the process can still be very time consuming and extremely irritating. Installing the wrong driver, or simply an incompatible version of the right driver, can make your problems even worse. Because of the time and complexity involved in updating drivers, we highly recommend using a such as (Developed by Microsoft Gold Partner) to automate the process.
Updates all of your PC device drivers, not just those associated with your EXE error. Proprietary One-Click Updateâ„¢ technology not only ensures that you have correct driver versions for your hardware, but it also creates a backup of your current drivers before making any changes. Maintaining a driver backup provides you with the security of knowing that you can rollback any driver to a previous version if necessary. With updated device drivers, you can finally unlock new hardware features and improve the speed and performance of your PC. Please Note: Using System Restore will not affect your documents, pictures, or other data.
To use System Restore (Windows XP, Vista, 7, 8, and 10):. Click the Start button. In the search box, type 'System Restore' and hit ENTER. In the results, click System Restore. Enter any administrator passwords (if prompted). Follow the steps in the Wizard to choose a restore point. Restore your computer.
If your SQLPLUS.EXE error is related to a specific program, reinstalling Enterprise Edition-related software could be the answer. Instructions for Windows 7 and Windows Vista:. Open Programs and Features by clicking the Start button. Click Control Panel on the right side menu. Click Programs. Click Programs and Features. Locate SQLPLUS.EXE-associated program (eg.
Enterprise Edition) under the Name column. Click on the Enterprise Edition-associated entry. Click the Uninstall button on the top menu ribbon. Follow the on-screen directions to complete the uninstallation of your SQLPLUS.EXE-associated program. Instructions for Windows XP:. Open Programs and Features by clicking the Start button. Click Control Panel.
Click Add or Remove Programs. Locate SQLPLUS.EXE-associated program (eg. Enterprise Edition) under the list of Currently Installed Programs. Click on the Enterprise Edition-associated entry. Click the Remove button on the right side. Follow the on-screen directions to complete the uninstallation of your SQLPLUS.EXE-associated program.
Instructions for Windows 8:. Hover the cursor in the bottom left of the screen to produce the Start Menu image. Right-Click to bring up the Start Context Menu. Click Programs and Features. Locate SQLPLUS.EXE-associated program (eg. Enterprise Edition) under the Name column. Click on the Enterprise Edition-associated entry.
Click the Uninstall/Change on the top menu ribbon. Follow the on-screen directions to complete the uninstallation of your SQLPLUS.EXE-associated program. After you have successfully uninstalled your SQLPLUS.EXE-associated program (eg. Enterprise Edition), reinstall the program according to the Oracle instructions.
Tip: If you are positive that your EXE error is related to a specific Oracle program, uninstalling and reinstalling your SQLPLUS.EXE-related program will likely be the solution to your problem. System File Checker is a handy tool included with Windows that allows you scan for and restore corruptions in Windows system files (including those related to SQLPLUS.EXE). If System File Checker finds a problem with your EXE or other critical system file, it will attempt to replace the problematic files automatically. To run System File Checker ( Windows XP, Vista, 7, 8, and 10):. Click the Start button.
Type ' command' in the search box. DO NOT hit ENTER yet!. While holding CTRL-Shift on your keyboard, hit ENTER.
You will be prompted with a permission dialog box. A black box will open with a blinking cursor. Type ' sfc /scannow' and hit ENTER. System File Checker will begin scanning for SQLPLUS.EXE and other system file problems (be patient - the system scan may take a while). Follow the on-screen commands. Microsoft is constantly updating and improving Windows system files that could be associated with SQLPLUS.EXE. Sometimes resolving your EXE problems may be as simple as updating Windows with the latest Service Pack or other patch that Microsoft releases on an ongoing basis.
To check for Windows Updates (Windows XP, Vista, 7, 8, and 10):. Click the Start button. Type ' update' into the search box and hit ENTER. The Windows Update dialog box will appear.
If updates are available, click the Install Updates button. Caution: We must emphasize that reinstalling Windows will be a very time-consuming and advanced task to resolve SQLPLUS.EXE problems. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process. If you are not currently backing up your data, you need to do so immediately to protect yourself from permanent data loss. This step is your final option in trying to resolve your SQLPLUS.EXE issue. Reinstalling Windows will erase everything from your hard drive, allowing you to start again with a fresh system.
Furthermore, a clean install of Windows will also quickly clean out any and all 'junk' that has accumulated over the normal usage of your computer. Filename: SQLPLUS.EXE Latest Known Version: 1.0.0.0 Developer: File Size (Bytes): 43280 Software: Operating System: Windows Description: 8.0.6 MD5: 0479F633D9A77CE4C963EB4CE090D6A2 SHA1: 06FDFA4D7BA8F0A001DB504A6AD997 Operating System Information SQLPLUS.EXE error messages can occur in any of the following Microsoft Windows operating systems:.
Windows 10. Windows 8. Windows 7. Windows Vista. Windows XP. Windows ME. Windows 2000 Are You Still Experiencing SQLPLUS.EXE Issues?
Please reach out to us anytime on social media for more help. Solvusoft: Microsoft Gold Certified Company Recognized for best-in-class capabilities as an ISV (Independent Software Vendor) Solvusoft is recognized by Microsoft as a leading Independent Software Vendor, achieving the highest level of completence and excellence in software development.
Solvusoft's close relationship with Microsoft as a Gold Certified Partner enables us to provide best-in-class software solutions that are optimized for performance on Windows operating systems. How is the Gold Competency Level Attained? To achieve a Gold competency level, Solvusoft goes through extensive independent analysis that looks for, amongst other qualities, a high level of software expertise, a successful customer service track record, and top-tier customer value. As a Gold Certified Independent Software Vendor (ISV), Solvusoft is able to provide the highest level of customer satisfaction through delivering top-level software and service solutions, which have been subject to a rigourous and continually-audited approval process by Microsoft.
MySQL Community Edition is a freely downloadable version of the world's most popular open source database that is supported by an active community of open source developers and enthusiasts. MySQL delivers enterprise features, including:. Partitioning to improve performance and management of very large database environments.
Row-based/Hybrid Replication for improved replication security. Event Scheduler to create and schedule jobs that perform various database tasks. XPath Support. Dynamic General/Slow Query Log.
Performance/Load Testing Utility (mysqlslap). Improved!
Full Text Search (faster, new dev templates). Improved! Archive engine (better compression, more features).
Improved! User session and problem SQL identification. Improved! MySQL embedded library (libmysqld).
Additional INFORMATIONSCHEMA objects. Faster data import operations (parallel file load). ACID Transactions to build reliable and secure business critical applications. Stored Procedures to improve developer productivity.
Triggers to enforce complex business rules at the database level. Views to ensure sensitive information is not compromised. Information Schema to provide easy access to metadata. Pluggable Storage Engine Architecture for maximum flexibility. Archive Storage Engine for historical and audit data. Compilation Notes: Windows builds now use the default runtime libraries (builds use the /MD flag).
CMake support was added for compiling with Developer Studio 12.6. Configuration Notes: MySQL failed to compile if -DENABLEDEBUGSYNC=OFF AND -DWITHDEBUG=ON were both given. The ENABLEDEBUGSYNC option has been removed and enabling WITHDEBUG enables Debug Sync. Packaging Notes: Changes in RPM package structure require a larger set of packages to be removed to install MySQL Server cleanly. To avoid potential race conditions, Debian packages now use the GNU install utility rather than a combination of mkdir, touch, and chown.
CMake-generated packaging for Debian/Ubuntu packages was refactored for improved maintainability. The change includes updated logic for correctly replacing native distribution packaging in Debian and Ubuntu. Reminder: MySQL 5.6 requires the Microsoft Visual C 2010 Redistributable Package to run on Windows platforms. Users should make sure the package has been installed on the system before starting the server. The package is available at the Microsoft Download Center. Security Notes: The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.2k.
For a description of issues fixed in this version, This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. The mysqloptions C API function now supports a MYSQLOPTSSLMODE option. The only permitted option value is SSLMODEREQUIRED, to require a secure connection to the server.
It causes mysqlrealconnect to fail if an encrypted connection cannot be obtained, without falling back to an unencrypted connection. Thus, mysqlrealconnect returns an error if the server does not support SSL or the client is not configured to use SSL. The client/server exchange terminates immediately after the initial server packet has been received if the server indicates that it does not support SSL. To require an encrypted connection in MySQL 5.6, the standard MySQL client programs call mysqloptions to set MYSQLOPTSSLMODE if the -ssl-mode=REQUIRED command-line option was specified. Third-party applications that must be able to require encrypted connections can use the same technique.
For details, see mysqlsslset. The minor C API version number was not incremented for this change. Application programs compiled for MySQL 5.6 that require MYSQLOPTSSLMODE may fail to operate properly if the dynamic loader provides an older client library without MYSQLOPTSSLMODE. Such applications must be written to handle this possibility by checking whether the mysqloptions call succeeds or fails.
Thread Pool Notes: To improve threadpool plugin performance, connection authentication and initialization have been moved from the acceptor thread to the thread pool worker threads that handle client connections. This enables the acceptor thread to handle new connections at a higher rate with reduced latency. The INFORMATIONSCHEMA TPTHREADGROUPSTATE table now contains a CONNECTTHREADCOUNT column that indicates the number of threads that are processing or waiting to process connection initialization and authentication. There can be a maximum of four connection threads per thread group; these threads expire after a period of inactivity.
Functionality Added or Changed: Replication: When a negative or fractional timeout parameter was supplied to WAITUNTILSQLTHREADAFTERGTIDS, the server behaved in unexpected ways. With this fix: A fractional timeout value is read as-is, with no round-off. A negative timeout value is rejected with an error if the server is on a strict SQL mode; if the server is not on a strict SQL mode, the value makes the function return NULL immediately without any waiting and then issue a warning.
The performance of UTF-8 binary collations was improved. Consistency and maintainability of Debian/Ubuntu packaging maintainer scripts was improved.
Mysqlsecureinstallation is more strict about what it considers valid yes and no responses. Bugs Fixed: InnoDB: The restriction that required the first undo tablespace to use space ID 1 was removed. The first undo tablespace may now be assigned a space ID other than 1. Space ID values for undo tablespaces are still assigned in a consecutive sequence.
InnoDB: Compiling the server without the Performance Schema caused a build failure. InnoDB: The file handle type name for InnoDB file I/O Performance Schema instrumentation was changed from ospfsfilet to pfsosfilet. InnoDB: A server exit on restart was caused by missing mythreadinit and mythreadexit functions for background threads that initialize the stmythreadvar structure. InnoDB: A memcached read operation with a non-default read batch size configuration resulted in a server exit. InnoDB: Performance Schema instrumentation for InnoDB file I/O was disabled on Windows. InnoDB: The rowsearchmvcc function unnecessarily traversed the entire table for a range query, which occurred when the record was not in the transaction read view.
Replication: When using a multi-threaded slave (slaveparallelworkers greater than 0) the value of SecondsBehindMaster was incorrect when rotating a relay log. Mysqldump failed to properly quote certain identifiers in SQL statements written to the dump output. Client preauthorization by the server was missing a length check for a length-encoded string. For Debian/Ubuntu packages, user-defined collation files could be overwritten during MySQL upgrades. Charset files are now marked as conffiles so that user customizations generate a prompt during upgrades whether to overwrite them.
For CREATE TABLE statements that specified the table name with a database qualifier and included a DATA DIRECTORY or INDEX DIRECTORY option, an error occurred if there was no default database. Starting the server with performanceschemadigestssize=1 caused an abnormal exit. Mysqldsafe did not check whether the directory named by the -basedir option existed. Mysqldsafe failed if the error log file named by the -log-error option was a FIFO. Mysqldsafe could fail if the -datadir option value ended with a / character. A recent change to mysqldsafe caused the mysql.server script to be unable to start it if the base directory was specified as an absolute path that differed from the compiled-in default absolute path.
The fix for Bug #78777 had different effects depending on whether the Performance Schema is enabled. The connectioncontrol plugin failed to compile if the Performance Schema was disabled.
For System V init scripts for RPMs, the mysqld option-file section was being ignored for some options, such as pid-file. Init scripts failed to launch mysqldsafe if a non-default base directory was used. Mysqldsafe -no-defaults did not work (inadvertent consequence of an earlier bug fix). Semicolon (;) characters within or between statements could cause distinct digests to be generated from identical statements. For a client linked against libmysqlclient, invalid memory access could occur during use of prepared statements. The fix for Bug #25088048 caused the command used by mysqldsafe to start the MySQL server to no longer include the mysqld path.
Executing a stored procedure containing a query that accessed a view could allocate memory that was not freed until the session ended. A query could produce incorrect results if the WHERE clause contained a dependent subquery, the table had a secondary index on the columns in the select list followed by the columns in the subquery, and GROUP BY or DISTINCT permitted the query to use a Loose Index Scan. Creation of a MyISAM temporary table during query processing could fail if the key length in the query was greater than the maximum MyISAM key length, resulting in a server exit.
The DebugPrintTest and DebugPrintDeathTest unit tests did not handle divide-by-zero testing properly on the Aarch64 platform. Thanks to Alexey Kopytov for the patch. Changes made to mysqldsafe in recent MySQL releases require the -ledir, -mysqld, -mysqld-version options to be specified on the command line; they can no longer be specified in option files. This could cause failure of init scripts that invoke mysqldsafe.
Such scripts now pass the value of the MYSQLDOPTS environment variable as the first command-line argument to mysqldsafe, with the value set to such command line-only mysqldsafe option values as may be required. On platforms that use /etc/sysconfig/mysqld, the MYSQLDOPTS value can be set in that file with a line such as this: MYSQLDOPTS=' -ledir=/mysqldledir -mysqld=mywrapper ' The value of MYSQLDOPTS can also include mysqld options for mysqldsafe to pass to mysqld. For LOAD DATA used to insert data into an updateable view, the check to verify whether a column is actually updatable was missing. On Debian/Ubuntu platforms, the systemd startup script for MySQL ignored datadir settings in /etc/mysql/my.cnf. A regular expression pattern match into a large string could result in a server exit due to memory allocation failure or integer overflow.
An incorrect error was reported for CREATE TABLE statements with a large value for the CONNECTION table option. The value is now limited to 1024 bytes.
MySQL now uses readdir rather than readdirr. The latter has been deprecated since glibc 2.24 and caused debug builds of MySQL and builds using GCC 6.1 to fail. Additionally, several problems resulting in GCC 6.1 compiler warnings were corrected. The -DWITHEDITLINE=system CMake option failed with recent versions of the editline library.
Grant tables with incorrect structure may cause problems in user management operations. As a consequence of the fix for this, for any operation that modifies a grant table, the server now checks whether the table has the expected structure and produces an error if not. Mysqlupgrade must be run to update the tables to the expected structure. The QUOTE function could allocate excessive memory.
A limit of maxallowedpacket bytes is now imposed and returns NULL with a warning for attempts to allocate more. When attempting to locate the data directory, mysqldsafe incorrectly considered $MYBASEDIRVERSION/var as one of the possible locations. The main.logtables-big test case could be unstable on highly loaded hosts.
Thanks to Laurynas Biveinis for the patch. Queries that used an aggregate function with DISTINCT could produce incorrect results. With the useindexextensions flag of the optimizerswitch system variable disabled, some SELECT DISTINCT queries could return incorrect results. Debian packages were missing an AppArmor-related include file and incorrectly were marked dependent on AppArmor (making it impossible to disable AppArmor by uninstalling it).
In a replication environment, SET PASSWORD or ALTER USER could fail to execute on the slave due to failure to parse the hash string correctly. On non-Linux Unix systems, the mysql.server startup script used the Linux command pidof rather than pgrep. Starting multiple instances of mysqldsafe after an abnormal server exit could result in one mysqldsafe instance killing another.
As a consequence of the bug fix, the mysqldsafe.pid file is no longer used. The -help message for mysqldsafe was corrected to mention that the -no-defaults, -defaults-file, and -defaults-extra-file options, if given, must be the first argument. The bounds check for the XML parser position stack for each level (which has a fixed depth) used the size of the array as the upper limit, and so was off by one. This is fixed by decreasing the allowable depth by one, which actually matches the maximum number of elements in the position stack. Timestamps for server-side prepared statements could be written to the binary log up to a second behind timestamps for the corresponding nonprepared statements, leading to time value differences between master and slave servers.