Process Information retention and TimeTrace

Hello,

I'm having some issues with my history db and need to get my main db down for upgrade to newest version. I plan to create a new history db and the old one will still be available for time trace.

I need to determine what i need to set for keeping the process information on changes history to objects. I know the Common\ProcessState\JobHistory\IsToExport will not be needed for the process information data.

Can someone tell me what is needed for the Process Information to be moved to history db for TimeTrace?

I have the following but are these for the Process Information?

Common\ProcessState\ProgressView\IsToExport
Common\ProcessState\PropertyLog\IsToExport

Thank you,

Top Replies

Parents

+1 Trevor Pike over 3 years ago

Hi Lu,

I'd suggest to review the Configuration Guide for specifics: https://support.oneidentity.com/technical-documents/identity-manager/8.0.5/configuration-guide/80#TOPIC-1447385.

Trevor
Cancel
Up +1 Down

Reply

Verify Answer

Reject Answer

Cancel
0 lrigs over 3 years ago in reply to Trevor Pike

Thank you for the direction.

Can you tell me if I have not turned on JobHistory for Export or Deletion and I have 6 million plus there will it bog down the DB for deletion if I turn it on to 30 days?

Should I make appoint to make it a high number then widdel it down every few days?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 lrigs over 3 years ago in reply to Trevor Pike

Thank you for the direction.

Can you tell me if I have not turned on JobHistory for Export or Deletion and I have 6 million plus there will it bog down the DB for deletion if I turn it on to 30 days?

Should I make appoint to make it a high number then widdel it down every few days?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

+1 xd over 3 years ago in reply to lrigs

To minimize the potential performance impact to the DB, It would be recommended to start with a high number then reduce it eventually.
Cancel
Up +1 Down

Reply

Reject Answer

Cancel
0 lrigs over 3 years ago in reply to xd

XD, Thanks for the advice.

Lu
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 lrigs over 3 years ago in reply to xd

XD,

Do you see any potential impacts if we just truncate JobHistory in the mean time as this will not be needed for the new year.

I do plan to back up the table first but I think just clearing it out to start would help get the database size down.

Thank you, Lu
Cancel
Up 0 Down

Reply

Verify Answer

Cancel