ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleksandr Diachenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-4303) Foreign key constraints name too long - during Oracle schema upgrade
Date Mon, 20 Jan 2014 17:52:19 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleksandr Diachenko updated AMBARI-4303:
----------------------------------------

    Description: 
* Upgrade from 1.4.1/1.3* to 1.4.3*
1) Stop the Ambari Server and all Ambari Agents. From the Ambari Server host: 
{code}ambari-server stop{code}
2) From each Ambari Agent host: 
{code}ambari-agent stop{code}
3) Get the new Ambari bits. Use wget to fetch the repository file and replace the old repo
file with the new repo file on every host.
(For RHEL/CentOS 6/Oracle Linux 6) : 
{code}cd ~/tmp{code}
{code}wget http://s3.amazonaws.com/dev.hortonworks.com/AMBARI.bw-m15-1.x/repos/centos6/ambari.repo{code}
#Replace the old repo file with the new repo file. 
{code}cp ambari.repo /etc/yum.repos.d/ambari.repo{code}

4) Upgrade Ambari Server & check for upgrade success. From the Ambari Server host:
	{code}yum clean all{code}
	{code}yum upgrade ambari-server ambari-log4j -y{code}

6) Upgrade the Ambari Server schema. From the Ambari Server host:
{code}ambari-server upgrade{code}
7) After the process is complete, check each host to make sure the new 1.4.4 files have been
installed:
{code}	rpm -qa | grep ambari{code}
8) Upgrade the Ambari Agent on all hosts. From each Ambari Agent host (RHEL/CentOS): 
{code}yum upgrade ambari-agent ambari-log4j{code}
9) Start the Server and the Agents on all hosts. 
>From the Server host:
{code}ambari-server start{code}
>From each Agent host:
{code}ambari-agent start{code}
10) Open Ambari Web. Point your browser to {noformat}http://{your.ambari.server}:8080{noformat}

  was:
* Upgrade from 1.4.1/1.3* to 1.4.3*
1) Stop the Ambari Server and all Ambari Agents. From the Ambari Server host: 
{code}ambari-server stop{code}
2) From each Ambari Agent host: 
{code}ambari-agent stop{code}
3) Get the new Ambari bits. Use wget to fetch the repository file and replace the old repo
file with the new repo file on every host.
(For RHEL/CentOS 6/Oracle Linux 6) : 
{code}cd ~/tmp{code}
{code}wget http://s3.amazonaws.com/dev.hortonworks.com/AMBARI.bw-m15-1.x/repos/centos6/ambari.repo{code}
#Replace the old repo file with the new repo file. 
{code}cp ambari.repo /etc/yum.repos.d/ambari.repo{code}

4) Upgrade Ambari Server & check for upgrade success. From the Ambari Server host:
	{code}yum clean all{code}
	{code}yum upgrade ambari-server ambari-log4j -y{code}

6) Upgrade the Ambari Server schema. From the Ambari Server host:
{code}ambari-server upgrade{code}
7) After the process is complete, check each host to make sure the new 1.4.4 files have been
installed:
{code}	rpm -qa | grep ambari{code}
8) Upgrade the Ambari Agent on all hosts. From each Ambari Agent host (RHEL/CentOS): 
{code}yum upgrade ambari-agent ambari-log4j{code}
9) Start the Server and the Agents on all hosts. 
>From the Server host:
{code}ambari-server start{code}
>From each Agent host:
{code}ambari-agent start{code}
10) Open Ambari Web. Point your browser to http://{your.ambari.server}:8080


> Foreign key constraints name too long - during Oracle schema upgrade
> --------------------------------------------------------------------
>
>                 Key: AMBARI-4303
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4303
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.4.3
>            Reporter: Oleksandr Diachenko
>            Assignee: Oleksandr Diachenko
>             Fix For: 1.4.4
>
>         Attachments: AMBARI-4303.patch
>
>
> * Upgrade from 1.4.1/1.3* to 1.4.3*
> 1) Stop the Ambari Server and all Ambari Agents. From the Ambari Server host: 
> {code}ambari-server stop{code}
> 2) From each Ambari Agent host: 
> {code}ambari-agent stop{code}
> 3) Get the new Ambari bits. Use wget to fetch the repository file and replace the old
repo file with the new repo file on every host.
> (For RHEL/CentOS 6/Oracle Linux 6) : 
> {code}cd ~/tmp{code}
> {code}wget http://s3.amazonaws.com/dev.hortonworks.com/AMBARI.bw-m15-1.x/repos/centos6/ambari.repo{code}
> #Replace the old repo file with the new repo file. 
> {code}cp ambari.repo /etc/yum.repos.d/ambari.repo{code}
> 4) Upgrade Ambari Server & check for upgrade success. From the Ambari Server host:
> 	{code}yum clean all{code}
> 	{code}yum upgrade ambari-server ambari-log4j -y{code}
> 6) Upgrade the Ambari Server schema. From the Ambari Server host:
> {code}ambari-server upgrade{code}
> 7) After the process is complete, check each host to make sure the new 1.4.4 files have
been installed:
> {code}	rpm -qa | grep ambari{code}
> 8) Upgrade the Ambari Agent on all hosts. From each Ambari Agent host (RHEL/CentOS):

> {code}yum upgrade ambari-agent ambari-log4j{code}
> 9) Start the Server and the Agents on all hosts. 
> From the Server host:
> {code}ambari-server start{code}
> From each Agent host:
> {code}ambari-agent start{code}
> 10) Open Ambari Web. Point your browser to {noformat}http://{your.ambari.server}:8080{noformat}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message