You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sandor Molnar (JIRA)" <ji...@apache.org> on 2018/12/05 13:05:00 UTC

[jira] [Commented] (AMBARI-25001) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate

    [ https://issues.apache.org/jira/browse/AMBARI-25001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710040#comment-16710040 ] 

Sandor Molnar commented on AMBARI-25001:
----------------------------------------

Additional information about the storage requirements for all kind of DBs that are currently supported :
Oracle
 - 12c : 4000 ([https://docs.oracle.com/database/121/SQLRF/sql_elements001.htm#SQLRF0021])
 - 11gr2 : 4000 ([https://docs.oracle.com/cd/E11882_01/server.112/e41084/sql_elements001.htm#SQLRF30020])

Postgres
 - 10.2 : 1 GB ([https://www.postgresql.org/docs/10/datatype-character.html#DATATYPE-CHARACTER-TABLE]); depends on encoding; recommended is to use 'text' as type (see {{clusterconfig.config_data}})
 - 9.6 : 1 GB ([https://www.postgresql.org/docs/9.6/datatype-character.html#DATATYPE-CHARACTER-TABLE]); depends on encoding; recommended is to use 'text' as type (see {{clusterconfig.config_data}})

MySQL (InnoDB only)
 - 5.7 : 65,535 ([https://dev.mysql.com/doc/refman/5.7/en/storage-requirements.html#data-types-storage-reqs-innodb])

MariaDB
 - 10.2 : 65,535 ([https://mariadb.com/kb/en/library/varchar/])

> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate
> --------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-25001
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25001
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 2.8.0
>
>
> During the upgrade process to AMBARI 2.7.0 the upgrade operation is failing on Schema upgrade phase due to the following error:
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO ambari_configuration (property_name, category_name, property_value) VALUES ('ambari.sso.provider.certificate','sso-configuration',<LONG CERTIFICATE VALUE>') was aborted: ERROR: value too long for type character varying(2048)
> {code}
> Ambari is having the following DDL for {{ambari_configuration}}:
> {code:java}
> CREATE TABLE ambari_configuration (
>   category_name VARCHAR(100) NOT NULL,
>   property_name VARCHAR(100) NOT NULL,
>   property_value VARCHAR(2048),
>   CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, property_name));
> {code}
> {{property_value}} is set to maximum of 2048 bytes/chars which is obviously not enough in some cases.
> Checking the currently supported DBs we may set this column to 4000 (except for Postgres where the recommended type is {{text}})



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)