From: Angel P. <an...@pc...> - 2004-01-08 19:55:28
|
Hey Matthew, Thanks for finding all of the bugs in the schema code for me. I will update them and commit to CVS. Angel Matthew Hobbs wrote: >Thanks Angel - this made things much clearer to me. > > >On Wed, 7 Jan 2004 02:17 am, you wrote: > > >>schmea.prop does indeed get read by the build process, and not by >>create-db.sh >>The build process should read schema.prop and do macro replacements on >>all of the SQL files that create a GUS instance. >> >>For example, the "@oracle_rad@" macro should have been replaced by the >>value in schema.prop for oracle_rad, but I just checked and there is not >>one there. There is a "oracle_rad3=RAD3", so this is my mistake as a >>result of dumping GUS 3.1 and trying to get rid of a historic version >>number from the RAD schema's name. So when you are runnning the $GUSHOME >>SQL files, that particular macro was (erroneously) not replaced. Sorry >>about that. The simple thing to do is to replace "rad3" with "rad" in >>the schema.prop file wherever you find it. Including the uppercase. (I >>just did so in my local copy and will commit it to CVS shortly) >> >> > > >I ended up making these changes to schema.prop: > >i) replaced these lines: > >oracle_rad3=RAD3 >oracle_rad3Password=password5 >oracle_rad3ver=RAD3Ver >oracle_rad3verPassword=password5 > >with these: > >oracle_rad=RAD >oracle_radPassword=password5 >oracle_radver=RADVer >oracle_radverPassword=password5 > >ii) added lines something like this (but with nice passwords): > >oracle_app=app >oracle_appPassword=password6 >oracle_appTablespace=tablespace6 >oracle_appIndexTablespace=tablespace6 > >oracle_appver=appVer >oracle_appverPassword=password6 >oracle_appverTablespace=tablespace6 > > >Does this look sensible? > > >Also I note that these lines don't seem to be necessary as the variables are >not used in any SQL statements: > >oracle_coreverIndexTablespace=indextablespace1 >oracle_sresverIndexTablespace=indextablespace2 >oracle_tessverIndexTablespace=tablespace4 >oracle_rad3verIndexTablespace=tablespace5 > >because dotsver is the only 'ver' database (whatever that is ) to be indexed. >Does that sound correct? > > >I also made some changes to view-creating SQL files where 'RAD3' was >inappropriately used instead of 'RAD'. > >in rad3-views.sql changed these lines: > >from RAD3.ANALYSISRESULTIMP >FROM RAD3.CompositeElementResultImp > >to: > >from RAD.ANALYSISRESULTIMP >FROM RAD.CompositeElementResultImp > > >and in rad3ver-views.sql changed these lines: > >FROM RAD3ver.ANALYSISRESULTIMPver >FROM rad3ver.AnalysisResultImpver; >FROM RAD3Ver.CompositeElementResultImpVer; > >to: > >FROM RADver.ANALYSISRESULTIMPver >FROM radver.AnalysisResultImpver; >FROM RADVer.CompositeElementResultImpVer; > > >After these edits I was able to run create-db.sh without any errors! > >Now on with the installation.... > > >Matthew > > > |