Workaround for Using Locally Managed Tablespaces with Risk Manager
Last updated on SEPTEMBER 17, 2016
Applies to:Oracle Risk Manager - Version 4.5 to 4.5.39 [Release 4.5]
Oracle Financial Data Manager - Version 4.5 to 4.5.39 [Release 4.5]
Information in this document applies to any platform.
Oracle Financial Services Applications (OFSA) 4.5
If your Oracle Financial Services Applications (OFSA) 4.5 database has a locally managed SYSTEM tablespace, you will receive an ORA-02219: Invalid NEXT Storage Option error when running a Risk Manager (RM) process because the extent columns in USER_TABLES and USER_INDEXES are NULL.
Is there a way to workaround the ORA-02219 error while still keeping a locally managed SYSTEM tablespace?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms