<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Phil,<div><br></div><div>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. </div><div><br></div><div><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>From: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">Jennifer Eakins <<a href="mailto:eakins@epicenter.ucsd.edu">eakins@epicenter.ucsd.edu</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>Date: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">February 17, 2009 4:24:36 PM MST</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; "><font face="Helvetica" size="3" color="#000000" style="font: normal normal normal 12px/normal Helvetica; color: rgb(0, 0, 0); "><b>Subject: </b></font><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; "><b>CVS: contrib: usarray/mk_dbops/: Suite of schema extension changes, </b></font></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div></div><div><br><br>Suite of schema extension changes, conversion utilities, and a program<br>to update these tables as used by the ANF.<br><br>NOTE: If you have used the comm, deployment, or dlsite extension <br>tables prior to January 2009, you will have to convert your pre-existing<br>tables to this updated format. Conversion scripts (convert_comm, <br>convert_deployment, convert_dlsite) are provided to help with this task.<br>Any in-house software that retrieves information from these tables should<br>be checked. The key differences:<br><br><span class="Apple-tab-span" style="white-space: pre; "> </span>- deployment table now uses vnet rather than net. The field<br><span class="Apple-tab-span" style="white-space: pre; "> </span> size is expanded.<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- comm and dlsite table now have extended field size for provider.<br><span class="Apple-tab-span" style="white-space: pre; "> </span>- comm table has additional fields for dutycycle, power, equip_type.<br><br>Also included in this check-in is some additional documentation about the<br>schema extensions.<br><br>Finally, to my great relief as a maintainer of 750+ station that have <br>contributed to the TA, the mk_dbops script will simplify the update of<br>the adoption, comm, dlsite, and deployment tables. Previously, all <br>records had been added/modified by dbe or vi which led to errors of<br>with omission of information, typos, or mismatch between the tables.<br><br>This is a work in progress, and additional updates will likely be <br>occurring in the upcoming weeks (i.e. station based subsetting using<br>not yet checked in features of q330_location).<br><br><br>Added Files:<br>-----------<br> /opt/antelope/cvs/contrib/bin/usarray/mk_dbops:<br> Makefile<br> adoption<br> adoption.5<br> adoption_schema.5<br> comm<br> comm.5<br> comm_schema.5<br> convert_comm.1<br> convert_comm.xpl<br> convert_deployment.1<br> convert_deployment.xpl<br> convert_dlsite.1<br> convert_dlsite.xpl<br> deployment<br> deployment.5<br> deployment_schema.5<br> dlsite<br> mk_dbops.1<br> mk_dbops.pf<br> mk_dbops.xpl<br></div><div><br></div></blockquote></div><div><br></div><div><br><div><div>On Apr 19, 2009, at 1:02 PM, Dr. Kent Lindquist wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>Hello Phil,<br><br>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:<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>% pwd<br><span class="Apple-tab-span" style="white-space:pre"> </span>/opt/antelope/4.10/data/schemas/css3.0.ext<br><span class="Apple-tab-span" style="white-space:pre"> </span><br><span class="Apple-tab-span" style="white-space:pre"> </span>% grep "Attribute model" *<br><span class="Apple-tab-span" style="white-space:pre"> </span>digitizer:Attribute model<br><span class="Apple-tab-span" style="white-space:pre"> </span>dlcalwf:Attribute model<br><span class="Apple-tab-span" style="white-space:pre"> </span>dlsite:Attribute model<br><span class="Apple-tab-span" style="white-space:pre"> </span>seismometer:Attribute model<br><span class="Apple-tab-span" style="white-space:pre"> </span>%<br><br>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).<br><br>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.<br><br>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.<br><br>Best regards,<br>Kent<br><br><br>On Apr 18, 2009, at 7:39 PM, Phil Cummins wrote:<br><br><blockquote type="cite">Hi,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">% dbe smtra_2007<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: formats differ: '%-15s' != '%-15'<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: conflicting Attribute model in schema css3.0<br></blockquote><blockquote type="cite">/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<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: formats differ: '%-15s' != '%-15'<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: conflicting Attribute manu in schema css3.0<br></blockquote><blockquote type="cite">/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<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: Parsing error in input schema<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: failed to compile database extension /opt/antelope/4.9/data/schemas/css3.0.ext/dlsite<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: Bad table id -102 in db pointer<br></blockquote><blockquote type="cite"> ** repeated 3 times<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: formats differ: '%-25s' != '%-25'<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: conflicting Attribute hostname in schema css3.0<br></blockquote><blockquote type="cite">/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<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: Parsing error in input schema<br></blockquote><blockquote type="cite">/opt/antelope/4.9/bin/dbe: failed to compile database extension /opt/antelope/4.9/data/schemas/css3.0.ext/qctests<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Any help you can give me would be much appreciated.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- Phil<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">Antelope mailing list<br></blockquote><blockquote type="cite"><a href="mailto:Antelope@brtt.net">Antelope@brtt.net</a><br></blockquote><blockquote type="cite"><a href="http://brtt.net/mailman/listinfo/antelope_brtt.net">http://brtt.net/mailman/listinfo/antelope_brtt.net</a><br></blockquote><br>--<br>Dr. Kent Lindquist <a href="mailto:kent@lindquistconsulting.com">kent@lindquistconsulting.com</a><br>Lindquist Consulting, Inc.<br>59 College Rd. Suite #7<br>Fairbanks, AK 99701 Phone/FAX 907-457-2374<br><br><a href="http://www.lindquistconsulting.com">http://www.lindquistconsulting.com</a><br><br><br>_______________________________________________<br>Antelope mailing list<br>Antelope@brtt.net<br>http://brtt.net/mailman/listinfo/antelope_brtt.net<br></div></blockquote></div><br></div></body></html>