[Spacewalk-list] Spacewalk upgrade 1.0 to 1.2 failed

Hagberg, Keith Keith.Hagberg at FMR.com
Mon Jan 31 14:08:49 UTC 2011


OK

I reverted everything back and reran the upgrade after setting my temp tablespace in oracle.

My original problem was that the repo data was not being generated. After successfully upgrading to 1.2, I now see a file in /var/cache/rhn/repodata/reponame/noyumrepo.txt in each of my repo dirs. The file has in it No repo will be generated for channel reponame.

Keith

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jan Pazdziora
Sent: Friday, January 28, 2011 1:22 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Spacewalk upgrade 1.0 to 1.2 failed

On Fri, Jan 28, 2011 at 10:47:39AM -0500, Hagberg, Keith wrote:
> OK, the issue was that our temp tablespace is named differently.
> 
> Still having an issue now running the /usr/bin/spacewalk-schema-upgrade
> 
> When I run it now I get Unknown schema name [no rows selected] found.
> 
> Apparently it cannot read the current schema version.
> 
> I went through and manually did all the sql commands for going from 1.0 to 1.1 , still get the same error.

You really should revert to your database backup of the 1.0 schema
and start anew. The spacewalk-schema-upgrade tries hard not to let
you continue / rerun failed schema upgrade because it generally
results in even more troubles.

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list




More information about the Spacewalk-list mailing list