October 8, 2004 at 7:59 am
Hello,
After months of debugging, we must assume there is a problem with W2003 Enterprise in combination with SQL2000, when 8Gb RAM is plugged in and /PAE switch enabled. SQL (used for our SAP application) fails to read records from time to time (error message mentions DBIF_RSQL_SQL_ERROR). The database keeps running, SAP has an ABAP dump for that particular user or process, but just goes on with the rest.
When we omit the /PAE switch, and only use the first 4 GB, we have NO problems. Of course, memory modules have been replaced, but it didn't help.
Every possible explanation has been eliminated. We even replaced ALL the hardware (except the disks). A hot fix from MS, recently applied, made things worse : we got blue screens, which we never had before.
Nor SAP, nor HP, nor Microsoft are willing to admit that this is a general problem. They state that only we are experiencing this problem. I don't believe them anymore.
I am sure someone else out there must be having the same problems. Please help us confront Microsoft with this fact. I realize that it probably is not an SQL problem, but one of W2003. But since it only reveils itself when using MS SQL ...
If you need more details, do not hesitate to contact me (rpa@niko.be).
Thanks,
PARIDAENS Robrecht
October 8, 2004 at 9:23 am
I haven't worked with many systems at 8GB and none on W2K3, but I pinged a few people that might have. Which HP system is this?
October 11, 2004 at 12:27 am
Hi,
The system that does not function with 8 Gb RAM under W2003 Enterprise =
HP Proliant DL580R02 / 4 CPU X2800 2MB Cache + MSA1000-storage
October 12, 2004 at 3:42 pm
You might look at KB article 834628
October 13, 2004 at 12:22 am
KB article 834628 is the hotfix I mentioned. We did apply it, as a last desparate measure. Result : 'sponteanous' bluescreen after a couple of hours. We removed the hotfix after we rebooted and got the same errors as before after another couple of hours (DBIF_RSQL_SQL_ERROR).
October 13, 2004 at 1:32 pm
We have an HP Proliant DL560 G1 / 4CPU and 8.5GB RAM, with W2003 Enterprise and SQL2000 Enterprise with SP3.
The system has enabled /3gb and /PAE switches in BOOT.INI.
When we installed we had some issues with W2003 but was because we had an Storage Works and an EVA SAN's together, HP told us that it may exists some conflicts so we disconected the Storage Works and now everything is OK.
Try to put both switches in the BOOT.INI file.
October 14, 2004 at 12:31 am
I didn't mention the /3gb switch : but sure , it is there. It's the only switch that we didn't experiment with : it was always ON.
We did try to enable or disable the /AWE-switch (to use a big SQL-buffer), but finally , we did not need it.
The installation of W2003 and SQL2000 where straightforward, and don't suggest any mistake or problem with the way we installed them. Because that's what HP and SAP now claim : "The problem only occurs in your company, so ... it's NOT a problem." Nice.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply