Bug #11270 Database
Submitted: 12 Jun 2005 12:54 Modified: 17 Jul 2005 13:05
Reporter: Munir Tisekar Email Updates:
Status: No Feedback Impact on me:
None 
Category:MaxDB Severity:S2 (Serious)
Version:MAX DB 7.5 OS:Microsoft Windows (Windows 2003)
Assigned to: Assigned Account CPU Architecture:Any

[12 Jun 2005 12:54] Munir Tisekar
Description:
After the restoring backup from diffrent server database is not running. it gives the error "-24895 shutdown of database occured [db_online -f]; -71 connection broken.

How to repeat:
e-mail
[16 Jun 2005 16:21] Ulf Wendel
Munir,

this is very likely not a bug. Please check the KNLDIAG / KNLDIAG.ERR files for detail. The files are contained in the RUNDIRECTORY of the database. The most comfortable way to inspect the files is using the Database Manager GUI. Select Check => Diagnosis Files => Database Messages and Databases Errors for details.

What do they say?

Best regards,
Ulf
[17 Jun 2005 12:55] Munir Tisekar
I reinstall the complete system database version 7.5.00.15 then upgrade to 7.5.00.21 but system still shows the DB version 7.5.00.15 I don't uderstand the reason.

This was the fresh installation without any rovery.

Regards

Munir
[17 Jun 2005 13:05] Ulf Wendel
Munir, 

this is not a support forum. Your request sounds very much like a support request. I don't see how a restore problem is related to installation/upgrade question.

Please provide me with a test case that demonstrate a MaxDB bug. Regarding your restore problem. I'm sorry to say, but I can't help you without the detailed error messages contained in the MaxDB logfiles. Please provide me with the KNLDIAG / Database Messages logfile. Send us the log just after recovery.

Best regards,
Ulf
[17 Jun 2005 13:09] Munir Tisekar
Logfile

Attachment: MaxDBUpdate_install-15.06.2005-18.42.log (application/octet-stream, text), 31.05 KiB.

[17 Jul 2005 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".