Deleted.

[anon26949]

Deleted.

[afaust · Accepted solution]

Any caches that Alfresco uses are emptied / cleared when Alfresco is restarted. There is no intended way to clear them at runtime - technically it is possible but you'd be doing this at the risk of breaking your runtime environment (some caches are not meant to be cleared as they hold singletons).

You don't need to do any SQL magic to set an admin password. Simply use either the UI to change it or pre-define it via a configuration in alfresco-global.properties

The only thing you need to undeploy the process definition is the workflow console, correct, But your workflow model will remain active, any nodes / metadata created or set based on a type or aspect in that model will remain in the database.

Generally you should NEVER have to work with the database directly. It is strongly discouraged and not supported by Alfresco in any way.

[anon26949]

Thank you very much for such exhaustive answer!..

[jumamonu]

Hello Axel, after restating Alfresco I see this errors Immediately:

Transactional update cache 'org.alfresco.cache.node.nodesTransactionalCache' is full (126000)

 Transactional update cache 'org.alfresco.cache.node.aspectsTransactionalCache' is full (66000).

If I stop alfresco and restart it, the cache should have been emptied, right?

Thanks

[afaust]

These caches are always empty when a new transaction begins - that is why they are called "transactional update cache". The only reason they are full is when some functionality is loading too much data into them in a single transaction.

[Yeudiel_TECAS]

ok, I understand that it is because it is filled with a single transaction.

So, how can I increase the cache, so that the word full does not appear?
and do not delay in raising the application of alfresco