Problem during schema-upgrade on satellite 5.3 to 5.4 upgrade
Issue
- I'm in the middle of upgrading our satellite from 5.3 to 5.4. The OS has been updated and I was running the spacewalk-schema-upgrade command when it failed, apparently due to lack of space in the external oracle db. It had run for 70 minutes before this happened (and the estimate script says it should take 3 hours to run). Is it possible to extend the db and continue from where we are or do we need to completely restore the db (a cold backup was done before we started) and re-run the schema upgrade from the beginning.
Environment
- Red Hat Enterprise Linux 5.4
- Satellite 5.4 (during Upgrade Process)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.