Hi Don,

> -----Original Message-----
> From: Don Gray [mailto:[EMAIL PROTECTED]

> From everything I have read and have been able to determine, RedHat
> Enterprise 3.0 (based on RH 9.0) SHOULD support files greater 
> than 2Gb.
> In fact in some cursory testing that I did I was able to 
> create greater
> than 2.1Gb files using simple system utilities.
> 
> -rw-r--r--    1 root     root     2561325100 Jan 20 08:02 bigfile3
> 
> Is this perhaps some limit imposed by the seeming requirement to run
> with LD_ASSUME_KERNEL=2.2.5?  Or is it some limit imposed by 
> the version
> of C libraries that MaxDB has been compiled against?  Note that I
> installed compat-libstdc++-7.3-2.96.118.i386.rpm in order to allow the
> SDBINST script to complete its install...  I got errors otherwise. 
> 

I don't know whether it's a problem with the compat-libraries or the LD_ASSUME_KERNEL 
option. 
If you are able to create those big files with a shell in which this LD_ASSUME_KERNEL 
option is set maybe trying to build MaxDB from the sources on your machine might help. 
But that I don't really know.

> Being unfamiliar with MaxDB, I have significant concerns 
> regarding this
> work around.  I anticipate that my databases working size 
> will be in the
> 75Gb range.  Is it a performance concern to have 75 1Gb files 
> as opposed
> to 15 5Gb files?  It seems that it would become an 
> administrative issue
> in the least. 
> 

If all those 75 files are located on the same disk then this should degrade I/O 
performance.
As to the administrative problem, creating those volumes can be automated in a script. 
After creation, handling of multiple volumes is transparent and you don't have to care 
about how many volumes are used any more (e.g. during backups). For an example of how 
volumes are created in a script have a look at the create_demo_db.sh script, which 
should be located in dependent_path/misc.
One more thing to take care of before installing all those volumes is to make sure to 
set the database parameter MAXDATAVOLUMES to a sufficiently large value (at least 75 
in your case). When setting this parameter keep in mind that you might want to add 
more data volumes during runtime of your database later on, so it is wise not to set 
it to the minimum value required in your setup.

Hope this helps,

Martin.

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to