Here we are talking of course of “very” badly designed application ! When setting “cursor_sharing= force” you may spot that some part of the application start crashing or generating wrong result. This due to one of the common but not well known side effect of setting cursor sharing to FORCE.
Thomas Kyte already described this side effect a long time ago in his book “Expert Oracle Database Architecture”
So as we can see the column length is suddenly much larger when turning cursor_sharing to force you can take a look here to know why is that. This side effect has caused some badly written application to crash (For example generating CSV file and injecting them into an ETL job) and it took some time to find the root cause of that. So it’s good to now that in any case 😉
That’s it 🙂