You are correct Edson, english is not everyone's first language. I later found that Stephen actually *pays* for support so he has every right to be upset. With those additional facts in hand I apologize to everyone (especially Stephen) for my remarks, they were short-sighted.
-----Original Message----- From: Edson Carlos Ericksson Richter [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 5:45 AM To: [EMAIL PROTECTED] Subject: Re: MaxDB 7.5.0.8 - xserver on Windows - DNS blocking all clients - SERIOUS! I don't see anything rude in the post... I think you should remeber that english is not the first language to vast number of people in the list, and some times we have diffuculty to express ourselfs, and sometime we appear being rude - but isn't our intention. So keep cool and try to understand the problem the user is facing, not blaming him by the words it self. Don't forget that, looking in the past, under beautyfull words was executed atrocities. Stephen, I faced the problem sometime ago, and found no solution, neither response from Sap guys. I think they are too busy developing and fixing a large number of bugs in SapDB and are not getting time to response complex problems. I'm sure they are storing this complains, and will eventually fix all of them. About the posts about a year ago, I have about 5 questions without response in the list too, all valid and reproducible. The question about the DNS dependencie is already discussed largelly in the past. Unfortunatelly, SapDB need either DNS server or a hosts files with IP/names mapping. In real, SapDB appear be dependent on a service name resolution. A solution you can use is configure a hosts file in %WINDIR%\system\drivers\etc with mappings for all IP will be accessing the server (not need be the real workstation names: is just a way to lie to SapDB), like this: 127.0.0.1 localhost 192.168.0.1 server 192.168.0.2 workstation2 192.168.0.3 workstation3 192.168.0.4 workstation4 and so on to the 192.168.0.254 (no map for 192.168.0.255, because it's broadcast address, and 192.168.0.0 is the network address). This is make SapDB think that is a resolution service active and working (look, I supposing that your subnet is 192.168.0). The problem is that if you need communication over the internet. Then, or you map all IP you need, or you should configure a caching DNS (look for Bind for Windows - if much better than MS Dns). In some of our clients, using WINS in a NT Domain local network environment guarantee that a service name resolution is avaliable, and we had no problems. Best regards, Edson Richter . PcgScrapAddy wrote: >Don't run it on Windows then or figure out a way to keep your DNS servers >up. If you want a super Windows friendly DB then buy MS-SQL. Your attitude >is very rude especially since they are doing *us* the favor by >producing/maintaining sapdb. > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Monday, March 29, 2004 5:10 PM >To: [EMAIL PROTECTED] >Subject: MaxDB 7.5.0.8 - xserver on Windows - DNS blocking all clients - >SERIOUS! > > > > >We were again hit with a production outage due to DNS dependence within >MaxDB. This time we spent 1 day setting up two test servers with >Win2K and a third running Linux. All running latest 7.5.0.8. > >I reported this problem over a year ago, and no response to my two posts on >the topic. http://lists.mysql.com/maxdb/19709 - in reply to my >first March 14 2003 posting. > > >Windows >===================== >We used Windows 2000 Server with latest service pack and Windows Update. >Also tested on Windows XP SP1. > >-- Win32 version of MaxDB xserver does NOT support the -F parameter! If you >run it you get: > >C:\Program Files\sdb\programs>serv -F >No valid option! Use -h to get help. > >If the remote DNS servers are down (stopped / blocked)... MaxDB will do two >nasty things: >1. take 35 seconds to respond to the first SQL from the first client. >2. serialize all other SQL requests... so they won't even START their 35 >seconds until the first one completes. Just a matter of time until the >server is so backlogged that > >Extra info: > >3. Even on the server itself, "DBMCLI -n localhost" will fail to respond >when DNS is unavailable. >4. As soon as DNS is restored, all returns to normal resuming right where it >halted. > > >Linux >====== >So we setup a Redhat 9 system and installed MaxDB. We found if the DNS >server is down (stopped / blocked); > >1. maxDB takes 20 seconds to respond >2. Adding the -F parameter to XServer fixes this! > > >So where is the -F parameter for Windows?! > >Stephen Gutknecht >full time traveler, home on wheels >currently in Grand Prairie, Texas USA > > > > >-- >MaxDB Discussion Mailing List >For list archives: http://lists.mysql.com/maxdb >To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > > > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
