Schema saving issue in Adobe Campaign Classic
This article outlines the steps to resolve schema saving issues in Adobe Campaign Classic’s development environment, where saving modifications to schemas results in slowness or errors, particularly after version upgrades.
Description description
Environment
Adobe Campaign
Issue/Symptoms
After upgrading to a new version of Adobe Campaign Classic, the following issues may occur when saving schema changes:
- Slowness during the saving process after adding new attributes or modifying existing ones.
The root cause is often linked to a configuration mismatch, particularly with cache invalidation, which prevents schema updates from reflecting across containers without restarting services.
Resolution resolution
- Ensure that the
spareServerconfigurations are correctly set with fully qualified domain names (FQDN). For example: Replaceurl="https://three-mkt-dev1"withurl="http://three-mkt-dev1.campaign.adobe.com". - Perform a clean restart of both nlserver and Apache services to clear any existing cache issues.
- Run post-upgrade commands with the
--forceoption if necessary to address potential conflicts in package management settings. - Although database restoration is not typically required, it may be considered as a last resort if other steps fail to resolve the issue. Before proceeding, ensure you have up-to-date backups to avoid data loss.
- After implementing these solutions, verify by editing and saving various schemas within your instance to confirm resolution of slowness or error messages previously encountered.
By following the outlined steps, you can effectively address schema saving issues in Adobe Campaign Classic’s development environment. This ensures smooth schema modifications and eliminates the need for unnecessary database restoration, except in cases of severe data integrity concerns.