Re: Drop table error after update from 7.5.0.19 to 7.5.0.23

Am Freitag, 21. Januar 2005 16:40 schrieb Edson Carlos Ericksson Richter:
> After update, have you run "Update system tables"?
No, I did not. 
But your hint lead me to tho:
MySQL MaxDB Library; Tools; DatabaseManager CLI;
Working with the Database Manager CLI;
Installation and Registration Management;
Configuring Database Instances; Functions for Database Operation;
Loading the System Tables,
where it states: 
"You have to reload the system tables after a change of database software 
version."

Thank you verry much!

Hermann-Josef Krings
> I just updated my linux box from 7.5.0.19 to 7.5.0.23 and don't get this
> errors (I have executed your sample).
>
> Best regards,
>
> Edson Richter
>
> Hermann-Josef Krings escreveu:
> >Hello,
> >
> >we use MaxDB 7.5.0.19 successfully, but after update using SDBINST to
> > 7.5.0.23 we get errors while dropping a table which has just been
> > created. The operating system we used, is SuSE 8.1 and SuSE 9.2.
> >
> >Example:
> >create table test (id integer,text varchar(24))
> >drop table test
> >
> >Generates the Following message:
> >General error; -28534 POS(1) Package must be recreated: ?
> >
> >In the Log we find:
> >
> >2005-01-21 16:12:35 17632 ERR 11262 DCOM     dispGetClassObject - HRESULT:
> >-2147220711, Context: INPROC
> >
> >2005-01-21 16:12:35 17632 ERR 11263 DCOM     COCLSID:
> >{A435CDA8-A24E-11D3-A996-00A0C94311A5}
> >
> >2005-01-21 16:12:35 17632 ERR 51260 HRESULT  80040319 package_out_of_dat
> >
> >After the first update we found that  Owner and Group are changed to a non
> >existing owner and group.
> >User sdb and sdbadmin, as well as group sdba existed before and did work
> > in 7.5.0.19.
> >We changed owner and group back to sdb.sdba
> >We also noticed that the location of directory sql has been changed
> >from /var/spool/sql to /usr/spool/sql
> >and created a link to solve problems starting WebSQL.
> >
> >A restart of the Update Process reports all OK, nothing gets replaced.
> >
> >Which file is causing the problem and how can we solve it?
> >
> >Best regards
> >
> >Hermann-Josef Krings

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx