[AMBARI-4303] Foreign key constraints name too long - during Oracle schema upgrade

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.3
• Fix Version/s: 1.4.4
• Component/s: ambari-server
• Assignee: Papirkovskyy Myroslav
• Reporter: Oleksandr Diachenko
• Created: 15/Jan/14 16:28
• Updated: 27/Jan/14 20:34
• Resolved: 27/Jan/14 20:34

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:

  ambari-server stop

  2) From each Ambari Agent host:

  ambari-agent stop

  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) :

  cd ~/tmp

  wget http://s3.amazonaws.com/dev.hortonworks.com/AMBARI.bw-m15-1.x/repos/centos6/ambari.repo

  #Replace the old repo file with the new repo file.

  cp ambari.repo /etc/yum.repos.d/ambari.repo

4) Upgrade Ambari Server & check for upgrade success. From the Ambari Server host:

yum clean all

yum upgrade ambari-server ambari-log4j -y

6) Upgrade the Ambari Server schema. From the Ambari Server host:

ambari-server upgrade

7) After the process is complete, check each host to make sure the new 1.4.4 files have been installed:

	rpm -qa | grep ambari

8) Upgrade the Ambari Agent on all hosts. From each Ambari Agent host (RHEL/CentOS):

yum upgrade ambari-agent ambari-log4j

9) Start the Server and the Agents on all hosts.
From the Server host:

ambari-server start

From each Agent host:

ambari-agent start

10) Open Ambari Web. Point your browser to

http://{your.ambari.server}:8080

Issue Links

• links to: ReviewBoard