And another 5 minutes later:
Domino 8.0.1 64-bit with DB/2 9.1.3 64-bit running on Windows 2003 R2 Enterprise 64-bit on IBM System x3650 with Dual Quad Core (=8 cores).
Oh, that reminds me I need to upgrade to DB/2 9.5 Viper next.
|
|
| | Mika
Friday, 22 February 2008 20:55:57 EET |
| | After some quick testing, it seems that Domino 8.0.1 x64 is very buggy.
First it destroyed all Forms and Views in a NSFDB2 database, and when I tried to paste them back from a Local backup, the Forms were pasted OK, but the views went totally nuts: first there appeared no views after the paste, and after a second paste there appeared "number of views pasted"-times the first view in clipboard.
I would be VERY careful using Domino 8.0.1 x64 at the moment, at least with DB/2, something is wrong with it, but I'll investigate more.
On the Notes 8.0.1 side there has been reported some bugs too, like newline seperated multivalue fields not appearing correctly in views.
Also Microsoft XMLHTTP calls seem not to work anymore under Domino 8.0.1 x64: You will get the error message: "msxml6.dll: The parameter is incorrect."
Oh crap, more destruction incoming: Line in log.nsf: DB2OBJ: ERROR WRITING OBJECT: rrv 28310, in D:\NOTES\DATA\...
This is it, I'm going back to Domino 8.0 x32.
After downgrading to Domino 8.0 x32, the Forms and Views are still corrupted in Designer 8.0.1. I see 3 times the same Forms and Views, and when I select one, it selects 2, and I can't select the middle one. Now I need to find out if it's a consequence of the Domino's destruction, or was it a bug in Designer 8.0.1 in first place. Actually I doubt it was a Designer issue, since some databases on the DB/2 server took forever to open, they never opened actually.
The error message: "msxml6.dll: The parameter is incorrect." still keeps appearing in Domino 8.0 x32. It might have been just coincidence that it happened at the same time with the Domino 8.0.1 x64 upgrade, and the actual reason could be that the webservice server is down (it's a chaos between BizTalk 2006 and SAP/R3, I never understood why they need either of those, as they had a fine working IBM System i (AS/400)).
I'm glad this is just technology research server, not even a development, test, stage, or production server.
At this point it was still unclear what caused all these problems:
1) Was it originally bugged in Domino 8.0? I've never seen any problems in 8.0 and DB/2 before today, however they might still have been there as I haven't checked this research server and it's databases for long time.
2) Did Domino 8.0.1 destroy all databases?
3) Did Notes/Designer 8.0.1 destroy all databases?
I didn't know, yet.
Maybe it's a problem with DB/2 itself, or the way how Domino databases are stored into DB/2 databases.
I noticed that a DB/2 enabled database was having very wierd document behaviour. There was a view with only 3 documents, and they randomly appeared either all as the same document, or 1st document OK, 2nd document OK, 3rd document looking like 2nd document. I moved the database to NSF format, and the data was still OK, and now the database works again.
So it is indeed a bug in DB/2 or NSFDB2. And the bug started to occur by the upgrade to Domino 8.0.1, since the same database worked fine a few minutes earlier on Domino 8.0. After the downgrade to Domino 8.0 the bug was still there, so Domino 8.0.1 somehow destroyed the NSFDB2 interface permanently. The mxsml6 error was a consequence of the document corruption in this database, which was also fixed after I moved the database from DB2 to NSF.
And then I found this in the Release Notes (thanks to Roberto from Ed's blog):
Note: Domino 64-bit is not a supported Domino and DB2 configuration.
The DB2 enabled databases were only looking damaged, which means they didn't work when I tried to open them from the Notes Client. Wierd errors came, documents appeared randomly, design elemenents vanished, etc... But then I found out that when I copied the database with a Notes Client to NSF, it worked fine again, all designs and documents were back.
Next I will try what happens if I copy the recovered NSF databases back as DB2 enabled databases.
|
|
|