This is a known issue and it was resolved today. The problem is caused by adapting the feature "Isolated-database configuration". To learn more about isolated more see:
It's easy to fix, you just have to add new property to JCR workspace configuration for some workspaces:
If the "db-tablename-suffix" property is not specified the indentifier names are based on the workspace name. If the workspace name is too long, you got the ORA-00972 error. If the "db-tablename-suffix" property is set (to some shorter variant), the value from property is used in oracle identifier names.
Hope this helps,
Your solution works.