  | | | Problem after migration! SQL-command via seems to kill the database ?? | Problem after migration! SQL-command via seems to kill the database ?? 2007-03-02 - By Beermann, Albert
Back 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
|
|
 |