Unfortunately I cannot reproduce this issue. From service or from UI, everything is ok right now.
But I can tell this only happened when deleting the content via service since I never use the UI (only for "debug" or investigation purpose).
My concern now is to "restore" the data to be able to check-in again those documents.
So I wonder if there is some kind of tool which could analyse the table content and clean-up irrelevant rows?
You could launch a database check with the IdcAnalyze applet.
This tool will check the tables and detect the inconsistencies.
You'll find it in $DOMAIN_HOME/ucm/cs/bin
If there is something wrong, it will be detected and IdcAnalyze will generate some scripts to correct the inconsistencies.
Hi Romain and thank you for your answer.
I wish I could reply earlier but the forum seems to be in trouble as I could not log in sooner (no responses from the login page).
I think this is what I need. Unfortunately, I cannot run the IdcAnalyze. I got a ClassNotFoundException on JpsTomcatPlatformFactory when I try to launch the utility, and another error stating JdbcConnectionString cannot be found. (both with the link in the start menu and command line)
And I cannot find any clue on how to properly launch the IdcAnalyze. Is there some kind of environment to set?
Any advice would be greatly appreciated.
Little update : I ran the SystemProperties.exe applet to set the jdbc parameters. So now the IdcAnalyze starts but I get stuck since it asks me a user name and password, but none of those I enter seem correct (I tried weblogic admin users and database users....).
What user should I use? I am lost with those stand-alone applets...
It's really painful to post something on the forum !
Since 11G, the database connection is handled by a weblogic connection pool.
You need to set the connection string in System Properties for the applets : Batch Loader, IdcAnalyze, etc.
To connect to an applet, you have to use a local user (admin) : sysadmin
Hi Luke ,
Run these 2 sql queries on UCM DB schema :
update users set dpasswordencoding='' where dname like 'sysadmin';
update users set dpassword='idc' where dname like 'sysadmin';
Then login with this user id / pwd .
If it still shows a problem then go to User Admin Applet from UI and put in the same password as above sql .