• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 1364 views
  • Users 0 members are here
Options
Related

Removing Custom Schema Extension in PRD

prueegg
over 2 years ago

I know that removing custom schema extension in production level isn't supported out of the box:
https://support.oneidentity.com/technical-documents/identity-manager/8.1.3/configuration-guide/89#TOPIC-1250792

Now I like to get rid of one of this columns and I wondering why it isn't supported. The risk could be quite high, but is it worth to keep the garbage forever?

I could force it, if I change the ProductionLevel temporary to a non production level. Is there any reason, why I shouldn't do that?

Patrick

PS: We are on 8.1.3

Parents
  • +1 over 2 years ago

    Hello,

    In our case, we have switched to "Stagging" configuration for deleting some custom schema.

    It's not powerfull because it will slowdown all the platform but didn't find any other solutions. (My case was to delete and create again a custom view which has not been transported successfully)

    I suggest to do it in a cold time of your users and to do the operation quickly to back in Production more faster.

Reply
  • +1 over 2 years ago

    Hello,

    In our case, we have switched to "Stagging" configuration for deleting some custom schema.

    It's not powerfull because it will slowdown all the platform but didn't find any other solutions. (My case was to delete and create again a custom view which has not been transported successfully)

    I suggest to do it in a cold time of your users and to do the operation quickly to back in Production more faster.

Children
No Data