Beermann, Albert wrote:

> Hello Everybody
> 
> We migrated a maxdb database from 7.6 32 bit(Linux/9-AMD) to 
> 7.6 64 bit
> (Linux/10-Intel)
> 
> Install new database
> 
> Restore from backup (restore with initialisation)
> 
> First everything seems to be OK, but
> 
>  
> 
> The database is running!
> 
> Connecting via spl-studio OK!
> 
> Tables and tablecontent OK!
> 
> Our application (connecting via odbc) is running!
> 
>  
> 
> BUT this command works only from sql-studio:
> 
> select lohistorie.loarbeitsstellenid,lohistorie.lostammarbkz,
> 
> loarbeitsstellen.loarbeitsstelle,
> 
> loarbeitsstellen.loarbeitsstellenid,
> 
> loarbeitsstellen.stauftragsstammid as stauftragsstammidast,
> 
> loarbeitsstellen.stpersonalstammid as stpersonalstammid 
> 
>  from loarbeitsstellen 
> 
>  left join lohistorie on loarbeitsstellen.loarbeitsstellenid =
> lohistorie.loarbeitsstellenid 
> 
>  and lohistorie.lofuermonat = '2' 
> 
>  and lohistorie.lofuerjahr = '2007'
> 
>  where loarbeitsstellen.stnlstammid = '1046' 
> 
>  
> 
>  
> 
> lohistorie = 1200000 records
> 
> loarbeitsstellen = 100000 records
> 
> result = 1500 records
> 
>  
> 
>  
> 
> When firing the same command from our application via odbc 
> the databases
> seems to hang ??
> 
> CPU 100 % no answer (kernel process)
> 
> We have to kill the process.
> 
> All other sql-commands from our application work fine and quick!
> 
> We droped all indexes and recreate them with no success
> 
> The command above is a "killer"
> 
>  
> 
> After connecting to the new database via Database Manger
> GUI->Information->Activity
> 
> i got an error -24988 sql-execute select description,value from
> monito_load;100;row not found
> 
> When clicking on information->cache
> 
> i got an error -24988 sql-execute select 
> description,numeric_value from
> sysdba.configuration;100;row not found
> 
>  
> 
> The command above works , when fired via odbc against our 
> test database
> (32 bit)  or our old database (32 bit)
> 
>  
> 
> Any help welcomed
> 
> Best regards
> 
> Albert

Hi,

you have to reload system tables after restore.
You can do it with "dbmcli -d ... -u ... load_systab".
I suppose this will be the reason for the DBMGui Problems.

For the outer join problem we need more information about 
the used MaxDB versions on both systems and additionally 
the explain output of the statement.

Kind regards
Holger
 
Holger Becker
MaxDB&liveCache
SAP AG
www.sap.com
Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, 
Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke
Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso 
Plattner 
Registergericht/Commercial Register Mannheim No HRB 350269

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige 
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich 
erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung 
oder Weitergabe der E-Mail ausdrücklich untersagt.
Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen 
Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise 
confidential information. If you have received this e-mail in error, you are 
hereby notified that any review, copying, or distribution of it is strictly 
prohibited. Please inform us immediately and destroy the original transmittal. 
Thank you for your cooperation. 

 

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to