There is actually a good Oracle Support article on this error. There can be a variety of reasons why one might encounter this issue. Occassionally the values in the Counters table get out of date. Sometimes you’re attempting to check in a new piece of content with the same Content ID as an existing piece of content without knowning it. Oftentimes this happens if you are integrating with Content Server and are attempting to generate a Content ID.
Once you’ve have fixed your core logic issue you may still be left with a “corrupted” piece of content in the system that you need to get rid of before you can make a fresh start with your updated code or process. To take care of this situation:
Step 1 – Open Admin Applets -> Repository Manager
Step 2 – Search/Filter to find the offending Content ID.
Step 3 -Delete this revision in the system.
You should now be able to checkin content normally again without this error occurring.
Running UCM admin applications directly from the server where Content Server is installed is called running them in stand-alone mode. No longer are they called applets, since the term “applet” is usually referred to a program which is included in a web page.
Stand-alone admin applications are located here: CS_INSTALL_DIRECTORY/bin/
Executable applications are listed in this folder. If an application is not listed, it can be entered as a parameter to the IntradocApp application, as in this example: % ./IntradocApp Workflow
In Windows, you can find the applications in your Start Menu: Start, Programs, Content Server, instance, Utilities, utility
In UCM 10g, you could run these stand-alone applications with no additional setup.
In UCM 11g, due to the advent of WebLogic, these applications need some setup. You need to setup a JDBC driver to talk to the database and you will need to login with a local user.
Below are 12 simple steps to get stand-alone admin applications running.
1. Login to UCM as an administrator.
2. Navigate to Administration > Admin Applets > User Admin.
3. Find the local user “sysadmin”.
4. Click “Edit”.
5. Change the password to something secure that you will remember.
6. Click “OK” and exit User Admin.
7. Navigate to MIDDLEWARE_HOME/user_projects/domains/DOMAIN/ucm/bin/
8. Open SystemProperties.
9. Go to the “Database” tab.
10. Select Oracle Thin JDBC Driver.
Note: The user name you connect as should not be “SYS”. You want the user Content Server connects as. If you do not know what user this is, open SQL Developer and connect as “SYS”. Then you can look under “Other Users’ and find a user that looks like it might be Content Server’s user. In my example this is dev_urmserver because it was a dev instance and this was a URM server.
11. Click “OK”.
12. Now when you launch any of the stand-alone applications you will be prompted for a user name and password. Login with sysadmin and click “OK”. The application should now load.
The two stand-alone admin applications that do not need login credentials are SystemProperties and Component Wizard.
Oracle documentation on running UCM 11g stand-alone admin applications can be found here.