If you're currently using Derby as a content store in your production TCR environment, then I'm afraid this is not a supported configuration.

IBM have issued a flash about this, the details of which can be found here - http://www-01.ibm.com/support/docview.wss?uid=swg21609287

Derby is recommended for demonstration/testing purposes only, it's just not designed to be used in a production or enterprise level environment. If you are using Derby at present, we would strongly advise you to change away from this to one of the supported databases as quickly as you can.