Skip to main content

Hello,

 

We refreshed SIT with PRD data for FSM application, version 6.22. We updated Scheduling App Params, updated threesixty_dataset_id global code to SIT, updated the monitor schedule that advances the time in PSO, but we are unsure why the scheduling dataset still shows PSO-PRD. 

The resources are not showing up on the schedule workbench. We are getting no other errors when restarting or initializing the dataset in the scheduling manager. 

What do we need to do to get PSO workbench to show the resources, use the correct scheduling dataset and remove the old one?

 



 

 

Hi!

How about the dataset ID? Did you change it after you made the refresh from PROD? If not, you should do that and send a new load to PSO. Also make sure that the all app params, scheduling app params  and integration_monitor-instances are set correctly for SIT. Typically, you should export and re-impot those tables from the destination db after a db refresh. Also, you should set the PROD dataset in PSO to “expired”.

Best regards
Roman

@roklde 

 

Thanks for the response. I wanted to get some clarification. What do you mean by “those tables?” Which tables from which application are you referring to? FSM or PSO tables?

Hi!

the following tables should be exported and re-imported from the target DB when performing a FSM DB refresh from a different environment.

  • metrix_app_params,
  • threesixty_app_params,
  • cust_image,
  • cust_app_params,
  • integration_monitor,
  • cust_int_routing_rule and
  • cust_int_routing_argument

Of course, some of those might no be needed if you don’t have any data in it. However, you should consider the parameters tables as those are typically have environment specific endpoints/configs.

This is a general note on FSM DB Copy / Refresh actions.

 

Best regards
Roman

Reply


Terms & ConditionsCookie settings