Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
7 subscribers
Views
1720 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
We are having an issue with 3 environments that were shutdown unexpectedly when
Forrest Richardson
Certified Lead Developer
over 10 years ago
We are having an issue with 3 environments that were shutdown unexpectedly when trying to connect to MySQL. When trying to restart jboss the primary DB cannot be initialized for what appears to be a mysql DATABASECHANGELOGLOCK issue i have come across in other forum posts.
"SQL UPDATE `DATABASECHANGELOGLOCK` SET `LOCKED` = 1, `LOCKEDBY` = 'hildev902.hil.us (192.168.#.###)', `LOCKGRANTED` = '2015-02-18 03:58:30.799' WHERE `ID` = 1 AND `LOCKED` = 0: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
"
The problem is that when I view the table I cannot find the entry listed in the log. For example LOCKEDBY` = 'hildev902.hil.us does not appear in the table. There is only one entry and it appears to be correct accordi...
server2_17.log
OriginalPostID-138771
OriginalPostID-138771
Discussion posts and replies are publicly visible
Parents
0
Forrest Richardson
Certified Lead Developer
over 10 years ago
We were able to resolve the issue by making 2 changes
1. We also recently installed a new version of MYSQL and had to update the configuration file to :
([mysqld]
binlog_format = 'ROW'
)
.The binlog_format was not set and we did not see the error until are unexpected loss of service.
2. We dropped the DATABASECHANGELOCK table.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Forrest Richardson
Certified Lead Developer
over 10 years ago
We were able to resolve the issue by making 2 changes
1. We also recently installed a new version of MYSQL and had to update the configuration file to :
([mysqld]
binlog_format = 'ROW'
)
.The binlog_format was not set and we did not see the error until are unexpected loss of service.
2. We dropped the DATABASECHANGELOCK table.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data