Red Hat Bugzilla – Bug 473082
Satellite Installer Always Thinks Database Schema is Populated
Last modified: 2009-01-22 11:48:45 EST
On a clean system installing Satellite 530 always asks: ** Database: Populating database. The Database has schema. Would you like to clear the database [Y]? The database does not yet have any schema. Version-Release number of selected component (if applicable): Discovered in spacewalk-setup-0.4.4 on Satellite 530, but problem may exist in spacewalk as well. Steps to Reproduce: 1. Use install.pl from Satellite. Can also run /usr/share/spacewalk/setup/oracle/remove-db.sh and re-install to repeat the error. Issue results from changes in git commit 56066cb7 to the file satellite/install/Spacewalk-Setup/lib/Spacewalk/Setup.pm. The query was changed to: + WHERE object_name <> 'PLAN_TABLE' + and object_name not like 'BIN$%' + and rownum = 1 Which is now always triggering.
Plan table contains CLOB which was triggering non-empty schema. Fixed in git repo Created commit ee6051d: 473082 - fixed $% expansion 1 files changed, 1 insertions(+), 1 deletions(-) Created commit a09f65b: 473082 - PLAN_TABLE contains CLOB so ignore also LOBs here 1 files changed, 1 insertions(+), 0 deletions(-) Package spacewalk-setup-0.4.5-1.
Moving from Satellite to Spacewalk.