Last updated on MARCH 28, 2016
Applies to:Oracle Demantra Demand Management - Version 7.2 and later
Information in this document applies to any platform.
This problem can occur on any platform.
On 7.2.0 in Production:
When Installing Demantra, the installer asks the user to specify which table spaces you would like key tables and indexes to be placed. However, after the install completes you find that the a separately created table space (ex. TS_SALES_DATA) for the SALES_DATA table does contain the latter table.
Expect key tables and indexes to be imported to their own table spaces as designated during the installer since this will impact performance
The issue can be reproduced at will with the following steps:
1. Run Demantra base version install
2 Specify a table space that exists as the site for the SALES_DATA table.
3.Check the table space to see if the table is associated with it after the Installation Completes (it will still be in the schema default table space)
Due to this issue, users have to go in after the install and create key tables and indexes in their preferred table spaces.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms