on 2017 Mar 16 3:32 PM
Does anyone know how Sybase Central measures what it thinks is enough free disk space?
We have had this screenshot from a customer (cant't upload pictures - get an error about global name send_email_template not defined, tried jpg & png various sizes, so I'll describe it) situation where the where the Overview is generating a warning (red mark against Health & Statistics, yellow triangle with exclamation mark in "Space Remaining" and a message dialog saying
"The device containing Dbspace 'system' is running low on disk space. 94.13 GB out of 185.75 GB are free (50.7%). You can free space on this device by deleting old or unnecessary files.
Caution I approve of, but this seems a little extreme.
v16.0.0.2076 but I've checked the docs for fixes in new ebfs but no mention.
Request clarification before answering.
The size check is a fixed 2 times the size of the database file being checked. It will check this for all dbspaces and transaction logs and the any that are over that limit will be flagged.
The current threshold is too big if you have all your db files on separate physical devices; which I suspect is your point. Many customers will have all of their database files on the same logical drive so in those cases that threshold is not as overzealous as it appears. Breck's example, for example, would have the transaction log flagged on a 3TB logical drive; possible both files.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The more correct answer is that this was set to be twice the size to allow room for a 2nd copy of the database file. This can prove helpful during rebuilds and some other activities (validation for one example).
User | Count |
---|---|
50 | |
10 | |
8 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.