| Model cannot be deployed after dropping and re-creating a partition [message #741986] |
Thu, 20 October 2011 04:16  |
 Srinivasan Iyer
Messages: 36
Registered: October 2011 |
Member |
|
|
An existing partition was dropped via the command-line and created again with the same ID. Afterwards a model deployment fails with this exception:
Operation could not be performed: AUTHx00545 - Failed to initially synchronize external user 'motu'. Exceeded maximum number of retries.: ag.carnot.error.ObjectNotFoundException: ATDB02103 - User realm 'carnot' for partition with oid '44' not found.
[Updated on: Thu, 20 October 2011 10:41] Report message to a moderator |
|
|
| Re: Model cannot be deployed after dropping and re-creating a partition [message #741987 is a reply to message #741986] |
Thu, 20 October 2011 04:17  |
Srinivasan Iyer
Messages: 36
Registered: October 2011 |
Member |
|
|
The problem is that the caches in the Stardust engine are not aware of the changes made via the command line, so they were using stale AuditTrail information (non-existing OID).
Stardust is currently working on a design for a distributed cache that would be aware of these changes.
But for now please flush and rebuild the caches after such changes to the AuditTrail via command line. Flushing the caches can be accomplished in two ways:
- Restart the application or the server
- Call "console -user <admin> -password <admin> engine -init" from the command line
[Updated on: Thu, 20 October 2011 10:34] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02806 seconds
] 
Search
Help
Register
Login
Home
