posted 9 years ago
I don't get the error with the statement you've posted. I get it when I increase the cache size to 6, which is consistent with the error message.
I'd say that Oracle simply didn't bother implementing cache size larger than cycle size (you'd have to restart the sequence while filling up the cache, which might - just might - mean that the sequence needs to be updated in the data dictionary; remember that caching is a delicate stuff when concurrency needs to be handled). I believe it is an implementation detail, a decision which doesn't have some deeper meaning behind itself.