Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Dimensions RM Slow Performance in RM 10.1.0, 10.1.1, 10.1.2, 10.1.3, and 10.1.4 caused by missing Oracle Indexes in Blank Project
Dimensions RM Slow Performance in RM 10.1.0, 10.1.1, 10.1.2, 10.1.3, and 10.1.4 caused by missing Oracle Indexes in Blank Project
CMS-XML KM-Dim7: 1019-DBIO: oracle error occured SQL-0904 3531 ORA-08102: index key not found, obj# 5669, dba 67170180 '2' 9505- failed to delete from table 'table name'
KM-Dim7: 1019-DBIO: oracle error occured SQL-0904 3531 ORA -08102: index key not found, obj# 5669, dba 67170180 '2' 9505- failed to delete from table 'table name'
CMS-XML Adding Indexes to SQL Server and Oracle.
Outlined below are suggested indexes for Oracle and SQL Server databases. Adding indexes will help improve response time of the database and remain balanced as more issues are added to your database.
CMS-XML "sqlerrm = ORA-20000: Unable to set values for index [index name]" errors during Data Pump import.
When users import Dimensions CM data into an Oracle 19 database via IMPDP, it may return the following messages: Processing object type DATABASE_EXPORT/STATISTICS/MARKER [index name] : sqlerrm = ORA-20000: Unable to set values for index [index name]: does not exist or insufficient privileges
CMS-XML Dim: ORA-01502: index "index_name" or partition of such index is in unusable state COR0004731E Error: failed to query details for build targets
This is caused by a problem with the Oracle index . To fix it, you can run this : sqlplus basedbname/password@<sid >
CMS-XML Dim10: When performing an upgrade, an error of SQL-1404(1007efb20) ORA-01404: ALTER COLUMN will make an index too large occurs
This error occurs if the db_block parameter size is too small within the Oracle instance. It is recommended that a new Oracle instance be created using the create_ora_inst script and using the relevant template file, either dim10Oracle10g.dbt or dim10Oracle9i.dbt, as referenced in our Installation Guide starting on Page 337.
CMS-XML KM-Dim7: Error: ORA-01632: max # extents (99) reached in index
By default, Dimensions indexes have a total of 99 extents. Oracle allows maxextents up to 121,so by increasing this from 99 to 121 it is possible to "hold back" the filling of the index . Thevalue of maxextents is increased as follows:
CMS-XML KM-Dim9: Rebuilding Indexes, get: ORA-01630: max # extents (121) reached in temp segment in tablespace PCMS_TEMP
To calculate the best set of storage parameters, I usually divide the total space available in the temp tablespace by 100 and use that as my initial and next sizes. The reason for this is that Oracle will be able to use all of the TEMP tablespace for one object containing approximately 100 extents. In this way, we are sure that the temp tablespace can be used efficiently.
CMS-XML Dim10: Error SQL-1408(1105daef0) ORA-01408: such column list already indexed occurs running the upgrade command
This error occurs during the creation of the index of WS_FILES4 as the index already exists. To fix: 1. Through Oracle delete the index mentioned.
CMS-XML KM-Dim9: During the upgrade process, the error SQL-1536-15(00C737F8) ORA-02429: cannot drop index used for enforcement of unique/primary key occurs (FILE_OS_DETAILS1)
Or SYSTEM> upgrade <basedatabasename> Note: The above can also be done directly on the table within Oracle Enterprise Manager. Disable the constraints, perform the upgrade and then reset.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs