How To Fix Eclipse Error - Java was started but returned exit code 13

Some times after installing sdk or new plugins to eclipse we will face the issue like

Java was started but returned exit code 13 message with dialog and we can't able to open eclipse

Resolve this issue by followed by below points:

1)open eclipse folder where your using eclipse

2)check for "eclipse.ini" file in the same folder

example path:

D:\Surya Android\eclipse-java-indigo-SR1-win32\eclipse here is eclipse is root folder

and check for eclipse.ini file

Right click and chose edit option

and now you can see the file like the below format:

-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
128M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
128m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.7
-Xms512m
-Xmx512m









at the end of the line just paste below 2 lines of text
-vm
C:/Program Files/Java/jdk1.7.0_75/bin/javaw.exe
And now save the file and restart the eclipse now eclipse will work fine.

Could not create the Java Virtual Machine.

I am using Eclipse IDE for development from so many years. recently i installed on plugin from the market place in eclipse. And i restarted eclipse,  at that time i can't able to open eclipse in my system.
i am facing below issue.

Error : Could not create the Java Virtual Machine.
Error: A fatal exception has occurred.Program will exit.

To resolve above issue i followed below point.

I just opened "eclipse.ini"file in eclipse folder.

And i  removed the -vm P:\Programs\jdk1.6\bin lines.

And i changed the required java version from

1.5 to 1.6 set  -Dosgi.requiredJavaVersion=1.6.

Import a large sql dump file to a MySQL database using command line

Steps to import large amount of data (dump ) file to mysql using command line. 

1. Open a command prompt (or shell) with administrative privileges

2. Connect to a MySQL instance using command line

If you are using online/hosted sql like (AWS)

$PATH_TO_MYSQL\mysql.exe -h 198.166.1.9 --port=3306 -u root -p

If you are in localhost you do not need host and port

$PATH_TO_MYSQL\mysql.exe -u root -p

3. Check your network buffer length value.

            SHOW VARIABLES LIKE 'net_buffer_length';

4. If the value is less than 1000000 .Set network buffer length to a large byte number. The default value may throw errors for such large data files

set global net_buffer_length=1000000;

5. Set maximum allowed packet size to a large byte number. The default value may throw errors for such large data files.

set global max_allowed_packet=1000000000;

6. Disable foreign key checking to avoid delays, errors and unwanted behavior

SET foreign_key_checks = 0;

SET UNIQUE_CHECKS = 0;

SET AUTOCOMMIT = 0;

7. Import your sql dump file

source C:\db_dumpfolder\filename.sql

Here “C:\db_dumpfolder\filename.sql” is a fully qualified path of your sql file.

8. Once total sql file execution completed. Don’t forget to enable foreign key checks when procedure is complete!

      SET foreign_key_checks = 1;

      SET UNIQUE_CHECKS = 1;

      SET AUTOCOMMIT = 1;

If you want to edit large amount of sql file(if you are unable to open large .sql file) use below Notepad.

http://www.editpadlite.com/

This Source from the:

https://cmanios.wordpress.com/2013/03/19/import-a-large-sql-dump-file-to-a-mysql-database-from-command-line/