Search

Are there any actions that I should avoid enabling or disabling on my Oracle B2C Service site during business hours?

Environment:

Site Administration
Oracle B2C Service, All versions

Resolution:

When managing your Oracle B2C Service application, several actions can compromise site performance and cause extra load on your database, or introduce other issues if not implemented, or enacted properly. As a result, it is recommended you review the administrative and maintenance actions listed below that should not be performed during peak business hours.

Note: This is not an all-encompassing list.  If you have questions regarding if an action will adversely affect your site during business hours, please post your question to the General Technical Discussions for Service in Oracle Cloud Customer Connect or Ask Technical Support.

1. Adding and deleting custom fields:  
   
   Introduces significant database load.  When custom fields are added, update statements must be performed against corresponding database tables. While these update statements are running, records in affected tables are inaccessible.
   
   As a result, your staff members will not be able to open or save records associated with the table that is locked. In addition, depending on the type of field being added, your end-users may have difficulty submitting assistance requests through the Ask a Question page.
   
   For example, when adding a contact custom field, the contacts table is locked to allow the custom field to be added to all contact records. As a result, staff are unable to open or save incidents since the contact information is opened along with the incident record.
    
2. Deleting products/categories/dispositions.
   
   a.  These deletions can touch every incident on a site and introduce significant database load
    
3. Changes to cached data:  
   
   This includes, but is not limited to, the following:
   a.  Staff accounts
   b.  Queues
   c.  Products
   d.  Categories
   e.  Dispositions
   
   These changes can introduce problems with agents worked with out-of-date cached data.
    
4. Changes to rules
   
   a.  Changes to both Business rules and Workspace rules should be performed on a clone of a production site, thoroughly tested, and then performed on production site outside business hours.
    
5. Processes that can introduce DB load
   
   a.  Data farming algorithms for the population of data warehouses
   b.  Batch reporting
    
6. Workspaces that are currently being used by logged in agents
   
   a. Making changes to workspaces while they are being used can cause inconsistencies in Agent workflow and cause errors.


7. Adding and Deleting Interfaces
   
   a. A number of functions are performed in the background during these operations (schema modifications, configuration changes etc...). As a result, users could experience intermittent errors navigating the console or logging in.