You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Dmytro Sen <ds...@hortonworks.com> on 2014/10/26 16:12:06 UTC
Review Request 27207: Schema upgrade failed after upgrade from 1.6.0
to 1.7.0
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27207/
-----------------------------------------------------------
Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko.
Bugs: AMBARI-7975
https://issues.apache.org/jira/browse/AMBARI-7975
Repository: ambari
Description
-------
Schema upgrade failed
15:33:04,218 WARN [main] DBAccessorImpl:535 - Error executing query: ALTER TABLE clusterconfig MODIFY config_data CLOB
java.sql.SQLException: ORA-22859: invalid modification of columns
Solution:
Upgrade fails because column datatype altering from CLOB to CLOB fails. Since it's CLOB in 1.6.0 and 1.6.1 DB initial scripts, this altering can be skipped for Oracle DB.
Alter statements for config_data were added in order to set same data type for config_data in different tables for Postgres and MySQL
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java c756a29
Diff: https://reviews.apache.org/r/27207/diff/
Testing
-------
[INFO] Ambari Server ..................................... SUCCESS [22:39.687s]
[INFO] Ambari Agent ...................................... SUCCESS [9.434s]
[INFO] Ambari Client ..................................... SUCCESS [0.277s]
[INFO] Ambari Python Client .............................. SUCCESS [0.568s]
[INFO] Ambari Groovy Client .............................. SUCCESS [14.351s]
[INFO] Ambari Shell ...................................... SUCCESS [0.040s]
[INFO] Ambari Python Shell ............................... SUCCESS [0.041s]
[INFO] Ambari Groovy Shell ............................... SUCCESS [10.764s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
+
[root@c6401 ~]# ambari-server upgrade
Using python /usr/bin/python2.6
Upgrading ambari-server
Updating properties in ambari.properties ...
Adjusting ambari-server permissions and ownership...
Ambari Server 'upgrade' completed successfully.
[root@c6401 ~]# ambari-server start
Using python /usr/bin/python2.6
Starting ambari-server
Ambari Server running with 'root' privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start....a................
Ambari Server 'start' completed successfully.
Thanks,
Dmytro Sen
Re: Review Request 27207: Schema upgrade failed after upgrade from
1.6.0 to 1.7.0
Posted by Andrew Onischuk <ao...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27207/#review58556
-----------------------------------------------------------
Ship it!
Ship It!
- Andrew Onischuk
On Oct. 26, 2014, 3:12 p.m., Dmytro Sen wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27207/
> -----------------------------------------------------------
>
> (Updated Oct. 26, 2014, 3:12 p.m.)
>
>
> Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko.
>
>
> Bugs: AMBARI-7975
> https://issues.apache.org/jira/browse/AMBARI-7975
>
>
> Repository: ambari
>
>
> Description
> -------
>
> Schema upgrade failed
>
> 15:33:04,218 WARN [main] DBAccessorImpl:535 - Error executing query: ALTER TABLE clusterconfig MODIFY config_data CLOB
> java.sql.SQLException: ORA-22859: invalid modification of columns
>
>
> Solution:
> Upgrade fails because column datatype altering from CLOB to CLOB fails. Since it's CLOB in 1.6.0 and 1.6.1 DB initial scripts, this altering can be skipped for Oracle DB.
> Alter statements for config_data were added in order to set same data type for config_data in different tables for Postgres and MySQL
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java c756a29
>
> Diff: https://reviews.apache.org/r/27207/diff/
>
>
> Testing
> -------
>
> [INFO] Ambari Server ..................................... SUCCESS [22:39.687s]
> [INFO] Ambari Agent ...................................... SUCCESS [9.434s]
> [INFO] Ambari Client ..................................... SUCCESS [0.277s]
> [INFO] Ambari Python Client .............................. SUCCESS [0.568s]
> [INFO] Ambari Groovy Client .............................. SUCCESS [14.351s]
> [INFO] Ambari Shell ...................................... SUCCESS [0.040s]
> [INFO] Ambari Python Shell ............................... SUCCESS [0.041s]
> [INFO] Ambari Groovy Shell ............................... SUCCESS [10.764s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
>
> +
>
>
> [root@c6401 ~]# ambari-server upgrade
> Using python /usr/bin/python2.6
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'upgrade' completed successfully.
> [root@c6401 ~]# ambari-server start
> Using python /usr/bin/python2.6
> Starting ambari-server
> Ambari Server running with 'root' privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start....a................
> Ambari Server 'start' completed successfully.
>
>
> Thanks,
>
> Dmytro Sen
>
>
Re: Review Request 27207: Schema upgrade failed after upgrade from
1.6.0 to 1.7.0
Posted by Mahadev Konar <ma...@apache.org>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27207/#review58557
-----------------------------------------------------------
Ship it!
Ship It!
- Mahadev Konar
On Oct. 26, 2014, 3:12 p.m., Dmytro Sen wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27207/
> -----------------------------------------------------------
>
> (Updated Oct. 26, 2014, 3:12 p.m.)
>
>
> Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko.
>
>
> Bugs: AMBARI-7975
> https://issues.apache.org/jira/browse/AMBARI-7975
>
>
> Repository: ambari
>
>
> Description
> -------
>
> Schema upgrade failed
>
> 15:33:04,218 WARN [main] DBAccessorImpl:535 - Error executing query: ALTER TABLE clusterconfig MODIFY config_data CLOB
> java.sql.SQLException: ORA-22859: invalid modification of columns
>
>
> Solution:
> Upgrade fails because column datatype altering from CLOB to CLOB fails. Since it's CLOB in 1.6.0 and 1.6.1 DB initial scripts, this altering can be skipped for Oracle DB.
> Alter statements for config_data were added in order to set same data type for config_data in different tables for Postgres and MySQL
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java c756a29
>
> Diff: https://reviews.apache.org/r/27207/diff/
>
>
> Testing
> -------
>
> [INFO] Ambari Server ..................................... SUCCESS [22:39.687s]
> [INFO] Ambari Agent ...................................... SUCCESS [9.434s]
> [INFO] Ambari Client ..................................... SUCCESS [0.277s]
> [INFO] Ambari Python Client .............................. SUCCESS [0.568s]
> [INFO] Ambari Groovy Client .............................. SUCCESS [14.351s]
> [INFO] Ambari Shell ...................................... SUCCESS [0.040s]
> [INFO] Ambari Python Shell ............................... SUCCESS [0.041s]
> [INFO] Ambari Groovy Shell ............................... SUCCESS [10.764s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
>
> +
>
>
> [root@c6401 ~]# ambari-server upgrade
> Using python /usr/bin/python2.6
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'upgrade' completed successfully.
> [root@c6401 ~]# ambari-server start
> Using python /usr/bin/python2.6
> Starting ambari-server
> Ambari Server running with 'root' privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start....a................
> Ambari Server 'start' completed successfully.
>
>
> Thanks,
>
> Dmytro Sen
>
>
Re: Review Request 27207: Schema upgrade failed after upgrade from
1.6.0 to 1.7.0
Posted by Dmytro Sen <ds...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27207/
-----------------------------------------------------------
(Updated Окт. 26, 2014, 3:33 п.п.)
Review request for Ambari, Andrew Onischuk and Mahadev Konar.
Bugs: AMBARI-7975
https://issues.apache.org/jira/browse/AMBARI-7975
Repository: ambari
Description
-------
Schema upgrade failed
15:33:04,218 WARN [main] DBAccessorImpl:535 - Error executing query: ALTER TABLE clusterconfig MODIFY config_data CLOB
java.sql.SQLException: ORA-22859: invalid modification of columns
Solution:
Upgrade fails because column datatype altering from CLOB to CLOB fails. Since it's CLOB in 1.6.0 and 1.6.1 DB initial scripts, this altering can be skipped for Oracle DB.
Alter statements for config_data were added in order to set same data type for config_data in different tables for Postgres and MySQL
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog170.java c756a29
Diff: https://reviews.apache.org/r/27207/diff/
Testing
-------
[INFO] Ambari Server ..................................... SUCCESS [22:39.687s]
[INFO] Ambari Agent ...................................... SUCCESS [9.434s]
[INFO] Ambari Client ..................................... SUCCESS [0.277s]
[INFO] Ambari Python Client .............................. SUCCESS [0.568s]
[INFO] Ambari Groovy Client .............................. SUCCESS [14.351s]
[INFO] Ambari Shell ...................................... SUCCESS [0.040s]
[INFO] Ambari Python Shell ............................... SUCCESS [0.041s]
[INFO] Ambari Groovy Shell ............................... SUCCESS [10.764s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
+
[root@c6401 ~]# ambari-server upgrade
Using python /usr/bin/python2.6
Upgrading ambari-server
Updating properties in ambari.properties ...
Adjusting ambari-server permissions and ownership...
Ambari Server 'upgrade' completed successfully.
[root@c6401 ~]# ambari-server start
Using python /usr/bin/python2.6
Starting ambari-server
Ambari Server running with 'root' privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server start....a................
Ambari Server 'start' completed successfully.
Thanks,
Dmytro Sen