Liferay 6.1 - MySQL - Database connection could not be established.

[Nikhil Sood, modificado hace 11 años.]

Hello,

I am trying to install Liferay 6.1 with MySQL 5.5.
1. I installed MySQL and set the root user with a valid password.
2. I checked my connection using the same password in the MySQL Workbench, and it is successful.
3. I successfully installed liferay 6.1.
4. In the basic configuration wizard, I selected MySQL and it defaulted the JDBC URL and JDBC Driver Class Name.
5. I entered the UserName and Password for MySQL.

No when I clicked on Finish Configuration button, I get the following error:

Database connection could not be established. Please check your connection settings.

Sceenshot is attached for reference. Appreciate any responses.

Thanks,
Nikhil

[Oliver Bayer, modificado hace 11 años.]

Hi Nikhil,

I'm not sure but shouldn't the jdbc url contains the port of your mysql instance? Otherwise check the tomcat console logs for a jdbc exception.

Greets Oli

[Nikhil Sood, modificado hace 11 años.]

Hi Oli,

Thanks for your response. I found my mistake. Basically you need to create a database schema in MySQL and then replace it with IPortal in the JDBC URL.

Cheers,
Nikhil

[serafino sorleti, modificado hace 11 años.]

Nikhil Sood:

Hi Oli,

Thanks for your response. I found my mistake. Basically you need to create a database schema in MySQL and then replace it with IPortal in the JDBC URL.

Cheers,
Nikhil

Thanks a lot!!!

[Jiechao Wu, modificado hace 10 años.]

Hello,
I want to ask a question: after creating a database schema in MySQL, how to replace it with IPortal in the JDBC URL?
Thanks!

Cheers,
xiaodanding

[Priyanka M, modificado hace 10 años.]

Hello Jiechu,

Am sure you already have an answer by now - but for the sake of others who might stumble on this post.
You need to replace the "lportal" in JDBC URL that appears in the box by default with the Schema name you just created.

Other option for ease is you could use the name lportal for the schema you create and then you dont need to make any changes. (Not a good thing though for production instances using default values)

Cheers,
Priyanka.