Description of problem: During spacewalk-setup Version-Release number of selected component (if applicable): spacewalk-schema-0.5.9-1, 0.5.8 appears broken as well. Problem does not occurr in 0.5.7. How reproducible: 100% Steps to Reproduce: 1. Install from devel repo. 2. spacewalk-setup --disconnected Actual results: ** Database: Populating database. *** Progress: ################################### Could not populate database. Additional info: Problem surfaces in populate_db.log: SQL_FILE ----------------------------------- rhnsat/tables/rhnRepoRegenQueue.sql Table created. Sequence created. Warning: Trigger created with compilation errors. Errors for TRIGGER RHN_REPO_REGEN_QUEUE_MOD_TRIG: LINE/COL ERROR -------- ----------------------------------------------------------------- 5/1 PLS-00103: Encountered the symbol "SELECT" SQL_FILE -------------------------------------- rhnsat/tables/rhnVirtSubLevel_data.sql SQL_FILE -------------------------------------- rhnsat/tables/rhnVirtSubLevel_data.sql 1 row created. 1 row created. Commit complete. SQL_FILE -------------------------------------------- rhnsat/tables/rhnSGTypeVirtSubLevel_data.sql insert into rhnSGTypeVirtSubLevel * ERROR at line 1: ORA-00942: table or view does not exist Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
weird, rhnSGTypeVirtSubLevel is not a new table. We had this since 5.0+ sats I suspect something did not get picked up when building the schema package.
ran the new rhnreporegenqueue through sqlplus and seems to create the trigger fine. [root@rlx-2-22 ~]# sqlplus rhnsat/rhnsat@rhnsat @rhnRepoRegenQueue.sql SQL*Plus: Release 10.2.0.4.0 - Production on Wed Feb 18 23:30:50 2009 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Table created. Sequence created. Trigger created. SQL>
Problem was missing \ and show errors at end of the new tables, which in turn affected the virt tables. Fixed in spacewalk git: 84c538ea6267017f1a1d839f79e02a6eb8e54023
And another fix in b715621aa747ffec1b15327b58de2b03c7aacc7c for slash going the wrong way. :)