| Bug #10700 | mysqld-nt does not support --datadir option | ||
|---|---|---|---|
| Submitted: | 18 May 2005 7:07 | Modified: | 18 May 2005 12:29 |
| Reporter: | Disha | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0.5-beta-nt | OS: | Windows (Windows xp) |
| Assigned to: | CPU Architecture: | Any | |
[18 May 2005 12:29]
MySQL Verification Team
c:\mysql\bin>mysqld-nt --basedir=c:\mysql --console --standalone --datadir=c:\rtest\data InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 050518 9:28:04 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 050518 9:28:04 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 050518 9:28:05 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 050518 9:28:10 InnoDB: Started; log sequence number 0 0 050518 9:28:10 InnoDB: Starting recovery for XA transactions... 050518 9:28:10 InnoDB: 0 transactions in prepared state after recovery 050518 9:28:10 [Note] mysqld-nt: ready for connections. Version: '5.0.6-beta-nt' socket: '' port: 3306 Source distribution
Description: When try to start mysqld-nt server service with --datadir option it kicked me out. Pre-condition : c:\rtest\data folder is created. How to repeat: A) execute the following command from prompt. C:\MySql\bin>mysqld-nt --basedir=c:\mysql --console --datadir=c:\rtest\data B) Expected Result: Server service should start with option set C) Actual Result: Server service is not started with selected option and shows following output 050518 12:13:23 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 050518 12:13:23 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 36808. InnoDB: Doing recovery: scanned up to log sequence number 0 43655 050518 12:13:24 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 050518 12:13:24 InnoDB: Started; log sequence number 0 43655 050518 12:13:24 InnoDB: Starting recovery for XA transactions... 050518 12:13:24 InnoDB: 0 transactions in prepared state after recovery 050518 12:13:24 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist