topic Re: [resolved] Unable to deploy data container AGAIN! in Talend Data Catalog

[resolved] Unable to deploy data container AGAIN!

Anonymous — Wed, 06 Aug 2014 12:34:24 GMT

Hi there,
I'm trying to deploy a data container which I had previously successfully deployed and I get the following error:

The server log reads:
2014-08-06 12:31:50,640 WARN No SQL storage defined for data model 'Media'. No SQL storage to update.
2014-08-06 12:31:50,640 WARN No SQL staging storage defined for data model 'Media'. No SQL staging storage to update.
2014-08-06 12:31:50,646 INFO DMUpdateEvent
2014-08-06 12:32:00,209 INFO Container 'Media' does not exist in revision 'null', creating it.
2014-08-06 12:32:00,210 INFO Reading from datasource file at 'D:\Program Files\TOS_MDM-Server-r111943-V5.4.1\jboss-4.2.2.GA\server\default\conf\datasources.xml'.
2014-08-06 12:32:00,233 INFO Reading from datasource file at 'D:\Program Files\TOS_MDM-Server-r111943-V5.4.1\jboss-4.2.2.GA\server\default\conf\datasources.xml'. 2014-08-06 12:32:00,255 INFO Reading from d

To see the whole post, download it here

Re: [resolved] Unable to deploy data container AGAIN!

Anonymous — Wed, 06 Aug 2014 13:33:57 GMT

Hi Facoda,
The following exception in your trace


Caused by: org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode

would make me say that you may have many Talend MDM processes running at the same time, causing a database file-lock issue (H2 is relying on files with exclusive locks : first-come first-served). Can you double-check that there's only one process related to Talend MDM running ?
Regards,
Cyril.

Re: [resolved] Unable to deploy data container AGAIN!

Anonymous — Wed, 06 Aug 2014 16:00:12 GMT

Brilliant! Thanks Cyril. You were correct there was a lock on the H2 database because I had used H2 Console to view the contents of the Media DB. I killed the H2 process by ending the javaw.exe for Windows in task manager.

Re: [resolved] Unable to deploy data container AGAIN!

_AnonymousUser — Wed, 25 Jan 2017 14:09:52 GMT

Hi there,
I'm trying to deploy a data container which I am deploying newly deployed and I got the above error mentioned.

Unable to deploy data container to the cluster ....
Please help me in checking this issue.

Re: [resolved] Unable to deploy data container AGAIN!

Anonymous — Mon, 09 Jul 2018 15:33:01 GMT

Hi AnonymousUser.

I was in the same problem like you and the only problem was my grants on database. I got MySQL and when I did check it, my dbuser won't have the appropriate grants.

if you have the same database try this:

mysql> show grants for 'username';

+--------------------------------------------------------------------------------------------------------------------------------------+

| Grants for username@%                                                                                                              |

+--------------------------------------------------------------------------------------------------------------------------------------+

| GRANT ALL PRIVILEGES ON `MDM_STAGING`.* TO 'username'@'%'                                                                |

| GRANT ALL PRIVILEGES ON `MDM_MASTER`.* TO 'username'@'%'                                                                 |

| GRANT ALL PRIVILEGES ON `MDM_MASTER`.* TO 'username'@'%'                                                                  |

| GRANT ALL PRIVILEGES ON `TMDM_DB_SYSTEM`.* TO 'username'@'%'                                                                       |

+--------------------------------------------------------------------------------------------------------------------------------------+

4 rows in set (0.00 sec)

Like you notice I just have permission to modify my Database but I don't have permission to create another one.

mysql> GRANT ALL PRIVILEGES ON *.* TO 'username'@'%' WITH GRANT OPTION;
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)

Restart the MDM Server and try it again.

So I hope it helps you.

Oscar