-
Enable collapse versions within a single editing session set to true.
-
- Document lifecycle with RM has not yet been implemented.
- We only have one extra copy of the document (no backup on tape).
- All our documents are sent to the Archive Server.
- For safety reason, a 93 days retention period has been defined until we implement Record Management.
-
- Givaudan started to deployed Windows 7 client in replacement of Windows XP.
-
- Flag "Delete Documents from Archive" enabled in order to allow content move operations.
- Deployment of Webdav 10.0.0 ActiveX
-
PROVIDERRETRY tables growed from 0 row to 300'000 rows
60% of Windows 7 clients deployed
5500 users reached
Security updates installed on Windows 7 clients
Hotfixes installed on Content Server servers (Windows 2003 SP2)
1.5 millions documents reached. -
- We notice some delete queries consuming a lot of CPU on the database:
DELETE FROM ProviderRetry
WHERE EntryType = :A1 AND ProviderData LIKE :A2 - OpenText support ticket #1510223
- Oracle optimizations were suggested by the support
- We notice some delete queries consuming a lot of CPU on the database:
-
- New index strategy.
- More memory allocated
-
- Uploading 300 documents (total size 200Mb) takes more than 23 hours!
- Uploading a single 10kb document takes 40s
-
Investigations:
- IE parameters
- Firewall on the servers
- IPv6
- Windows 7 updates
- Windows Server 2003 hotfixes
- ... -
- One Cluster down
- less CPU allocated
-
- When you edit a MS Office document, fhe first save is fast, the second is slow (40s) even for a smal document.
-
- When you drag&drop a document, it tries to upload it twice.
- At the end only version 2 remains.
-
- Any attemps to select / insert / delete in this table takes ages.
- There is no index on the PROVIDERDATA column (CLOB).
server: (ds-error='3060: document retention not yet expired: Document
baw5x5wczw1e5aa4kppjsdqkifkyk has a retention period of 87 more days') -
Option 1
- Create an index on PROVIDERDATA (as it's a CLOB column, Oracle TEXT must be installed). Option 2
- Copy PROVIDERRETRY table
- PURGE PROVIDERRETRY table
- Create a new volume on the Archive Server without retention and route all documents on this volume
- In 3 Months, move the rows back into PROVIDERRETRY Option 3
- Option 1 + Option 2 without the purge Option 4
- Create an index on PROVIDERDATA
- Remove the retention period for all new documents
You are not authorized to access this page.