Bug #72374 Cannot import sql file in my database through phpmyadmin
Submitted: 17 Apr 2014 20:36 Modified: 18 May 2014 18:30
Reporter: Rohit Patil Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:MySQL Community Server 5.6.10 OS:Microsoft Windows (8.1)
Assigned to: CPU Architecture:Any
Tags: Troubleshooting tablespace error while importing sql file

[17 Apr 2014 20:36] Rohit Patil
Description:
I am getting this below Error while importing the sql file:
#1813 - Tablespace for table '`jobsite`.`jobberland_admin`' exists. Please DISCARD the tablespace before IMPORT. 

Below is the exact error description which I am getting:

Error
SQL query:

--
-- Database: `jobtemp`
--
-- --------------------------------------------------------
--
-- Table structure for table `jobberland_admin`
--
CREATE TABLE IF NOT EXISTS  `jobberland_admin` (

 `id` INT( 11 ) NOT NULL AUTO_INCREMENT ,
 `username` VARCHAR( 16 ) NOT NULL ,
 `passwd` VARCHAR( 32 ) NOT NULL ,
PRIMARY KEY (  `id` )
) ENGINE = INNODB DEFAULT CHARSET = utf8 AUTO_INCREMENT =2;

MySQL said: Documentation

#1813 - Tablespace for table '`jobsite`.`jobberland_admin`' exists. Please DISCARD the tablespace before IMPORT. 

I want to import sql file but cannot do it due to this error Please help me solving this problem I tried a lot to troubleshoot it but its not working

Thank You

How to repeat:
Please give me feedback me through my Email ID: rohitp777@gmail.com

Suggested fix:
Troubleshooting tablespace error while importing sql file, And Corrupted table Error due to which mysql server is getting lost
[18 Apr 2014 18:30] Sveta Smirnova
Thank you for the report.

Please provide output of SHOW TABLES FROM jobsite, SHOW VARIABLES LIKE 'innodb_file_per_table' and output of `dir MYSQL_DATADIR\jobsite`
[19 May 2014 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".