| |
Results |
|
Dim10: Rebuilding database indexes fails if schema has a non default password
|
Dim10: Rebuilding database indexes fails if schema has a non default password
|
|
|
|
KM-Dim9: Rebuilding Indexes, get: ORA-01630: max # extents (121) reached in temp segment in tablespace PCMS_TEMP
|
KM-Dim9: Rebuilding Indexes , get: ORA-01630: max # extents (121) reached in temp segment in tablespace PCMS_TEMP
|
|
|
|
VM File Server-based PDB with missing pvcsid.ser file gives "Array Index Out of Bounds" error when adding an entity or trying to rebuild the pvcsid.ser file using PCLI ScanPDB
|
VM File Server-based PDB with missing pvcsid.ser file gives "Array Index Out of Bounds" error when adding an entity or trying to rebuild the pvcsid.ser file using PCLI ScanPDB
|
|
|
|
SBM and index fragmentation
|
Our DBA is rebuilding indexes twice a week due to a large amount of fragmentation. What can we do to improve this?
|
|
|
|
How to pre-index an SBM database before an upgrade
|
The Work Center search index is automatically rebuilt when Tomcat is started for the first time after the upgrade. Depending on the size of the database, the re-index can take a considerable amount of time. During the re-index, SBM will be available for use; however, Work Center or SRC search my not return all expected results.
|
|
|
|
MCLG: Suggested rebuild maintenance to improve performance with Oracle projects
|
The following Oracle rebuild activities should be performed regularly to ensure that performance is not degraded uncertainly. Perform daily a rebuild of all the indexes and computing tables and index statistics, preferably before any nightly batch jobs (deploys)
|
|
|
|
KM-Dim8: How to change storage parameters on tables or indexes?
|
For indexes , it's recommended that user rebuild them using the DMDBA recreateindexes utility. However, to modify next extent on an index, similar to the that on a table, user would need to run the following:
|
|
|
|
KM-Dim7: Moving Database Indexes to a separate Tablespace
|
Sometimes this is desirable as a minor performance improvement if the corresponding datafiles are located on different physical disk drives.Separating the data from the indexes also provides an aid in keeping fragmentation down. When the indexes are periodically rebuilt , their entire tablespace can be taken offline, dropped and recreated. This avoids leaving behind the fragmentation that would otherwise occur by simply dropping an index and recreating it.
|
|
|
|
Dim10: How to run the Dimensions Re-indexing script
|
where <basedb> is the schema whose index(es) are to be recreated. The recreateIndexes.sql script will rebuild and resize all the indexes in the specified schema. Please refer to Page 135 of the Dimensions Administrator's Guide, dmcm_admin.pdf, for additional details.
|
|
|
|
SBM 10.1.5+: Disable Returning Attachments in Work Center Search Results (How to turn off Smart Search indexing for attachments)
|
You are planning an upgrade and expect the re-index to take too long. After an upgrade, the indices are rebuilt automatically when JBoss/Tomcat is started. It could take a considerable amount of time for the re-index to complete and performance will be very slow until it finishes.
|
|
|
