| Bug #27919 | Installation of MaxDB in a cluster fails if another product is clustered | ||
|---|---|---|---|
| Submitted: | 18 Apr 2007 8:38 | Modified: | 30 Sep 2008 16:20 |
| Reporter: | guillaume boullot | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MaxDB | Severity: | S3 (Non-critical) |
| Version: | 7.6.0.34 | OS: | Windows (2003 Enterprise) |
| Assigned to: | CPU Architecture: | Any | |
[11 Sep 2007 15:12]
Burkhard Diesing
Hello, you are right. You found a real bug. I have opened an internal bug fixing request. You can monitore the state with http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1150515 Regards, Burkhard
[4 Oct 2007 17:09]
Valeriy Kravchuk
According to http://www.mysql.com/news-and-events/press-release/release_2007_40.html: "support of the MaxDB database will revert back to SAP"
[30 Sep 2008 16:16]
Konstantin Osipov
MaxDB is no longer under MySQL umbrella.
Description: Installing a MaxDB database in a cluster fails if a cluster resource exists with a name longer than 64 characters. XServer crashes, dbmcli inst_reg crashes, dbmcli db_create crashes. The problem comes from a bug in SAPDBMSCSMan.dll (function tos204_Cluster::os204_Enum, vos204.cpp line 456) How to repeat: Declare a resource in the cluster with a name of 70 characters. Install the MaxDB binaries with sdbinst, then clusterize the installation (with binaries from depend\cluster). Do any operation that tries to add a new resource with SAPDBMSCSMan For instance, register the depend path with dbmcli inst_reg to declare the Service kernel instance. Dbmcli crashes. Suggested fix: in vos204.cpp, function tos204_Cluster::os204_Enum, replace NameLen += sizeof(WCHAR); Name = (LPTSTR)_alloca(NameLen); by NameLen += 1; Name = (LPTSTR)_alloca(NameLen * sizeof(WCHAR));