clone preserve: System Properties and dealing with System Property versions

stevemac
Tera Guru

3 weeks ago - last edited 3 weeks ago

Like many customers we have environment specific settings stored in System Properties.  These properties are included in Clone Data Preserver rules.

 

Last week we had a problem in one of our non-prods.  Turns out it was a result of an intentional change to one of these properties and then shortly after reverting to the most recent prior version.   We found out the hard way that the System Property version records [in sys_update_version] are not preserved in the clone and therefore are a copy of the clone source.  The most recent version had the value for another instance

 

How do you deal with this?   Is a clone data preserver record safe to use in this case?  Something like

  • Table is Update Versions [sys_update_versions]
  • Type is System Property
  • Record Name starts with {what ever the matching string is}

Not sure the index on sys_update_versions is sufficient and generally concerned about unknown ramifications.

 

Appreciate your input,

 

Steve

 

0 Helpfuls
  • 947 Views
8 REPLIES 8

stevemac
Tera Guru

3 weeks ago

And obviously Clone Data Preserver is insufficient as also need to exclude the records and cannot set a condition on that

0 Helpfuls

stevemac
Tera Guru

3 weeks ago

Looked at this further & believe the following is required

  • Clone Data Preserver to preserve the required records
  • Clone Cleanup Script
    • Deletes the version records for the system properties preserved during clone
    • Saves the current version of the system property to generate a record in the versions [sys_update_versions] table
0 Helpfuls

Bert_c1
Kilo Patron

3 weeks ago

I believe a Data Preserver as you describe above will work to save those local update version records of records updated on the target since the last clone. I don't understand your next post, and Seems a Cleanup script as you post contradicts the desire to preserver update versions of records updated on the target instance.

0 Helpfuls

stevemac
Tera Guru
In response to Bert_c1

3 weeks ago

thanks @Bert_c1 

 

to clarify - I do not believe I can do clone exclusion for the versions table.  With just a data preserver, post clone the versions would be those from clone source and what was preserved on the clone target (assuming different version records in clone source).

 

Looking for a way to remove the records that may have come in from clone source.  I do not know how to identify them.

 

You are correct - no benefit in doing clone preserver on the version records if going to delete them.   Suggests the option is

  • leave existing Clone data preserver on the sys_properties records
  • new Clone cleanup script to get rid of the versions related to preserved system properties and create new version records based on the current system property
0 Helpfuls