[Antelope] schema compilation(?) problem on 4.9/PowerPC
Jennifer Eakins
jeakins at ucsd.edu
Mon Apr 20 10:02:19 CDT 2009
Hi Phil,
There was a change to the contributed schema extensions dlsite (and
adoption, comm, and deployment) on 2/17/2009. I would make sure you
have the latest versions available from contrib. If you have a dlsite
table, you might check the contributed script convert_dlsite that will
help convert the original version dlsite table into the more recent
version.
> From: Jennifer Eakins <eakins at epicenter.ucsd.edu>
> Date: February 17, 2009 4:24:36 PM MST
> Subject: CVS: contrib: usarray/mk_dbops/: Suite of schema extension
> changes,
>
>
>
> Suite of schema extension changes, conversion utilities, and a program
> to update these tables as used by the ANF.
>
> NOTE: If you have used the comm, deployment, or dlsite extension
> tables prior to January 2009, you will have to convert your pre-
> existing
> tables to this updated format. Conversion scripts (convert_comm,
> convert_deployment, convert_dlsite) are provided to help with this
> task.
> Any in-house software that retrieves information from these tables
> should
> be checked. The key differences:
>
> - deployment table now uses vnet rather than net. The field
> size is expanded.
> - comm and dlsite table now have extended field size for provider.
> - comm table has additional fields for dutycycle, power, equip_type.
>
> Also included in this check-in is some additional documentation
> about the
> schema extensions.
>
> Finally, to my great relief as a maintainer of 750+ station that have
> contributed to the TA, the mk_dbops script will simplify the update of
> the adoption, comm, dlsite, and deployment tables. Previously, all
> records had been added/modified by dbe or vi which led to errors of
> with omission of information, typos, or mismatch between the tables.
>
> This is a work in progress, and additional updates will likely be
> occurring in the upcoming weeks (i.e. station based subsetting using
> not yet checked in features of q330_location).
>
>
> Added Files:
> -----------
> /opt/antelope/cvs/contrib/bin/usarray/mk_dbops:
> Makefile
> adoption
> adoption.5
> adoption_schema.5
> comm
> comm.5
> comm_schema.5
> convert_comm.1
> convert_comm.xpl
> convert_deployment.1
> convert_deployment.xpl
> convert_dlsite.1
> convert_dlsite.xpl
> deployment
> deployment.5
> deployment_schema.5
> dlsite
> mk_dbops.1
> mk_dbops.pf
> mk_dbops.xpl
>
On Apr 19, 2009, at 1:02 PM, Dr. Kent Lindquist wrote:
>
> Hello Phil,
>
> One thing that might cause this is indeed corruption in the schema
> definition files, and that is the first thing to check. However, you
> have to check more than just the definition file for the table in
> which the error crops up (e.g. "dlsite" in your case below). You
> have to check all schema and schema extension files that might use
> this particular attribute. For example, on my copy of Antelope
> (admittedly 4.10 on Intel Mac), the "model" attribute is used in all
> of the dlsite, digitizer, dlcalwf, and seismometer tables:
>
> % pwd
> /opt/antelope/4.10/data/schemas/css3.0.ext
>
> % grep "Attribute model" *
> digitizer:Attribute model
> dlcalwf:Attribute model
> dlsite:Attribute model
> seismometer:Attribute model
> %
>
> The corruption could be in any one of these (in principle it could
> also be in the base schema $ANTELOPE/data/schemas/css3.0, but that
> one doesn't define the "model" attribute).
>
> Antelope allows an attribute that is used in multiple tables to be
> defined in any one of the supporting definition files, and in fact
> the "Attribute" definition block can appear multiple times, once in
> each of the files in which it is used, as long as the repetitious
> definitions are completely consistent with one another. Generally
> this repetition is done, which makes the tables less sensitive to
> load order etc. The first time (during schema parsing) that Antelope
> encounters one of these Attribute blocks, it merely loads in the
> newly defined Attribute. When Antelope sees subsequent definition
> blocks for the same attribute, it double-checks that they are
> consistent with the original. Thus, the comparison you're seeing
> below is presumably of two separate definitions of the "model"
> attribute in two separate extension tables.
>
> For the fields in question that are causing you problems, you should
> hunt down all the extension tables in which they are used, looking
> for errors. Most if not all of the extension tables you list are in
> various places in the Antelope contributed-code repository. The rest
> should be available on the Antelope CD.
>
> Best regards,
> Kent
>
>
> On Apr 18, 2009, at 7:39 PM, Phil Cummins wrote:
>
>> Hi,
>>
>> I am using Antelope 4.9 on a PowerPC Macintosh Powerbook.
>> Antelope_update says that all patches are up-to-date (granted, this
>> isn't saying much).
>>
>> I am developing a script and running it on a test database I
>> created some time ago from an IRIS volume using seed2db. I have
>> used this database many times with no problem. I have also tried
>> recreating the database, again using seed2db. Now I find that,
>> whenever I access the wfdisc table, even using dbe, I get the
>> following error:
>>
>> % dbe smtra_2007
>> /opt/antelope/4.9/bin/dbe: formats differ: '%-15s' != '%-15'
>> /opt/antelope/4.9/bin/dbe: conflicting Attribute model in schema
>> css3.0
>> /opt/antelope/4.9/bin/dbe: db : bad attribute at ';' while
>> compiling attribute 'model' near line #60 of /opt/antelope/4.9/data/
>> schemas/css3.0.ext/dlsite
>> /opt/antelope/4.9/bin/dbe: formats differ: '%-15s' != '%-15'
>> /opt/antelope/4.9/bin/dbe: conflicting Attribute manu in schema
>> css3.0
>> /opt/antelope/4.9/bin/dbe: db : bad attribute at ';' while
>> compiling attribute 'manu' near line #68 of /opt/antelope/4.9/data/
>> schemas/css3.0.ext/dlsite
>> /opt/antelope/4.9/bin/dbe: Parsing error in input schema
>> /opt/antelope/4.9/bin/dbe: failed to compile database extension /
>> opt/antelope/4.9/data/schemas/css3.0.ext/dlsite
>> /opt/antelope/4.9/bin/dbe: Bad table id -102 in db pointer
>> ** repeated 3 times
>> /opt/antelope/4.9/bin/dbe: formats differ: '%-25s' != '%-25'
>> /opt/antelope/4.9/bin/dbe: conflicting Attribute hostname in schema
>> css3.0
>> /opt/antelope/4.9/bin/dbe: db : bad attribute at ';' while
>> compiling attribute 'hostname' near line #72 of /opt/antelope/4.9/
>> data/schemas/css3.0.ext/qctests
>> /opt/antelope/4.9/bin/dbe: Parsing error in input schema
>> /opt/antelope/4.9/bin/dbe: failed to compile database extension /
>> opt/antelope/4.9/data/schemas/css3.0.ext/qctests
>>
>> This is baffling to me. The files in $ANTELOPE/data/schemas/
>> css3.0ext seem to say, e.g., '%-15s', as i think they should. What
>> is antelope comparing to that thinks the format should be '%-15'?
>> Although dbe seems to actually work OK, my script seems to end up
>> with a bad dbpointer when I look up the wfdisc table. And, this is
>> happening with at least one other database that I used to access
>> with no problem. Could one of Antelope's data files been corrupted,
>> and if so, is there any way for me to tell which one?
>>
>> Any help you can give me would be much appreciated.
>>
>> Thanks,
>>
>> - Phil
>> _______________________________________________
>> Antelope mailing list
>> Antelope at brtt.net
>> http://brtt.net/mailman/listinfo/antelope_brtt.net
>
> --
> Dr. Kent Lindquist kent at lindquistconsulting.com
> Lindquist Consulting, Inc.
> 59 College Rd. Suite #7
> Fairbanks, AK 99701 Phone/FAX 907-457-2374
>
> http://www.lindquistconsulting.com
>
>
> _______________________________________________
> Antelope mailing list
> Antelope at brtt.net
> http://brtt.net/mailman/listinfo/antelope_brtt.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brtt.net/pipermail/antelope_brtt.net/attachments/20090420/a33b6d34/attachment-0001.html>
More information about the Antelope
mailing list