Hello, dear developers of the installation routine I think you are interested in a feedback about your work. Let me tell you about the experiences I made with the last 2 upgrades (to 7.6.5 and 7.6.10)
I am a windows user and as such always happy if I am not forced to hack too much at the command level. When upgrading to the 7.6 beta, I had the problem that the installation program did not accept the username and password of the Database Administrator (SYSDBA). I tried with the DBM and this worked (!!) but at the end of the installation I got the error that the system tables could not be loaded. I checked everything, but finally I was forced to uninstall everything and to make a clean new installation. Fortunately, having made some bad experiences in the past years ( I use ADABAS since version 10.0), I had a good backup and could restore the database. This time, upgrading to 7.6.10 I was even more cautious, backed up the whole directory containing MaxDB plus a complete backup. I must say that for maximum security, I have exactly the same database running on MS Sqlserver 2000, for other reasons. Starting the nice routine, again I got the error: Unknown username password when indicating the SYSDBA name and password. I knew the data was correct and I began to search. It has cost me some hours to find out the reason: Under ../7600/doc/FirstSteps I found finally a file called sapdbenv.cmd which lead me to the solution of the problem: set SAPDBROOT=$DEP set PATH=%PATH%;$IND/bin;$DEP/bin set CLASSPATH=%CLASSPATH%;%SAPDBROOT%/runtime/jar/sapdbc.jar:. PERL5LIB=%PERL5LIB%;%SAPDBROOT%/misc PYTHONPATH=%PYTHONPATH%;%SAPDBROOT%/misc export SAPDBROOT PATH CLASSPATH PERL5LIB PYTHONPATH I don't know if this file is used during a windows installation, but I think that an error must have occurred during the setting of the environment variables - the classpath was not set in my environment, certainly because of PYTHONPATH which I remember darkly not having installed. After setting the classpath, everything worked fine ! So my tip for you developers: why not check the presence of the classpath. This would avoid such confusing messages like "Username not found" and save a lot of time. The next problem I had, maybe indeed I have not read everything about that new version, was the fact that my applications could no longer connect to the database. Again some hours of research with the following result: Up to the previous versions, a password could be 8 characters or longer, with everything ignored which was longer than 8, correct ? This new version seems not to accept passwords which are longer than 8 chars, even if they are stored as such in the database. I did not notice immediately, because by pure chance, the DBA passwords are exactly 8 characters long and only the special application user had a longer password. Such a changement, in my opinion, is important enough to be mentioned separatly and maybe, if possible, provoking a warning during or after the upgrade process. The third, minor problem: When someone wants to create a new database, it would be very nice if he could see the choice of Unicode or non Unicode without searching the extended parameters...... But otherwise: WHAT A PROGESS ! -- mit freundlichen Grüßen Uwe Haussmann mailto: [EMAIL PROTECTED] PGP/GNUPG Public Key: http://www.somdet.net/pgp/uhaussmann.txt -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
