<br>I should have posted this to the list. Problem solved. Thanks for the info, though, Jennifer.<br><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Phil Cummins</b> <span dir="ltr"><<a href="mailto:phil.cummins@gmail.com">phil.cummins@gmail.com</a>></span><br>
Date: Mon, Apr 20, 2009 at 10:21 PM<br>Subject: Re: [Antelope] schema compilation(?) problem on 4.9/PowerPC<br>To: "Dr. Kent Lindquist" <<a href="mailto:kent@lindquistconsulting.com">kent@lindquistconsulting.com</a>><br>
<br><br>Hi Ken,<br><br>Thanks! I fixed all the definition files as you suggested and it doesn't report an error now. However, my script still returned an invalid pointer - that turned out to be a different problem. Anyway, many thanks for the advice, dbe no longer reports those annoying error messages. Your Python interface works great, by the way!<br>
<font color="#888888">
<br>- Phil</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Mon, Apr 20, 2009 at 5:02 AM, Dr. Kent Lindquist <span dir="ltr"><<a href="mailto:kent@lindquistconsulting.com" target="_blank">kent@lindquistconsulting.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<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>
% pwd<br>
/opt/antelope/4.10/data/schemas/css3.0.ext<br>
<br>
% grep "Attribute model" *<br>
digitizer:Attribute model<br>
dlcalwf:Attribute model<br>
dlsite:Attribute model<br>
seismometer:Attribute model<br>
%<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<div><div></div><div><br>
<br>
<br>
On Apr 18, 2009, at 7:39 PM, Phil Cummins wrote:<br>
<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div>
Hi,<br>
<br>
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>
<br>
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>
<br>
% dbe smtra_2007<br>
/opt/antelope/4.9/bin/dbe: formats differ: '%-15s' != '%-15'<br>
/opt/antelope/4.9/bin/dbe: conflicting Attribute model in schema css3.0<br>
/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>
/opt/antelope/4.9/bin/dbe: formats differ: '%-15s' != '%-15'<br>
/opt/antelope/4.9/bin/dbe: conflicting Attribute manu in schema css3.0<br>
/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>
/opt/antelope/4.9/bin/dbe: Parsing error in input schema<br>
/opt/antelope/4.9/bin/dbe: failed to compile database extension /opt/antelope/4.9/data/schemas/css3.0.ext/dlsite<br>
/opt/antelope/4.9/bin/dbe: Bad table id -102 in db pointer<br>
** repeated 3 times<br>
/opt/antelope/4.9/bin/dbe: formats differ: '%-25s' != '%-25'<br>
/opt/antelope/4.9/bin/dbe: conflicting Attribute hostname in schema css3.0<br>
/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>
/opt/antelope/4.9/bin/dbe: Parsing error in input schema<br>
/opt/antelope/4.9/bin/dbe: failed to compile database extension /opt/antelope/4.9/data/schemas/css3.0.ext/qctests<br>
<br>
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>
<br>
Any help you can give me would be much appreciated.<br>
<br>
Thanks,<br>
<br>
- Phil<br></div></div>
_______________________________________________<br>
Antelope mailing list<br>
<a href="mailto:Antelope@brtt.net" target="_blank">Antelope@brtt.net</a><br>
<a href="http://brtt.net/mailman/listinfo/antelope_brtt.net" target="_blank">http://brtt.net/mailman/listinfo/antelope_brtt.net</a><br>
</blockquote>
<br>
--<br>
Dr. Kent Lindquist <a href="mailto:kent@lindquistconsulting.com" target="_blank">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" target="_blank">http://www.lindquistconsulting.com</a><br>
<br>
<br>
_______________________________________________<br>
Antelope mailing list<br>
<a href="mailto:Antelope@brtt.net" target="_blank">Antelope@brtt.net</a><br>
<a href="http://brtt.net/mailman/listinfo/antelope_brtt.net" target="_blank">http://brtt.net/mailman/listinfo/antelope_brtt.net</a><br>
</blockquote></div><br>
</div></div></div><br>