Skip to Content

~system~ version folder not clean after persistance change from dbfs -fsdb

I configure a repository manager DBFS and I create some content in it. Then I delete the content and also the repository configuration. I re-create the repository with FSDB persistance with the same name than before. But if I watch in the /fsdb/system/Versions/ folder I found many folder and documents such as 0... 1... 2... and so on. If I try to delete it the following message appear:

System error (com.sapportals.wcm.repository.IncompleteOperationException): null System error (com.sapportals.wcm.repository.IncompleteOperationException): null System error (com.sapportals.wcm.repository.IncompleteOperationException): null System error (com.sapportals.wcm.repository.IncompleteOperationException): null

I think that the information on DB is not correct and versions of documents that do not exist is diplayed. How can I clean the content of /system /Versions?

Any idea.

Thank in advance.

Regards,

Fabio Sambugaro

Calpeda S.p.A.

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 07, 2008 at 02:21 PM

    Hi Fabio,

    Try changing the Root Directory for Versions path for your FSDB Repository.

    After changing shutdown server and delete the version files manually from file system from:

    /usr/sap/J00/SYS/global/config/cm/

    Start your server and check if this work fine.

    Regards,

    Praveen Gudapati

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 07, 2008 at 03:36 PM

    Hi Praveen Gudapati,

    I create a new versions folder in /fsdb/Versions_rep and in the CM repository configuration I set the

    - Root Directory for Versions: /fsdb/Versions_rep (before it was /fsdb/Versions)

    - I stopped the instance.

    - In filesystem /fsdb/Versions/versiones/* I found all the folder and object I delete them with rm command.

    - I restart the instance, but when I go to Content administration - KM Content - fsdb - .system - versions I found o... 1... 2... ecc. again.

    It seems that the filesystem and the db doesn't syncronized.

    Thanks.

    Regards,

    Fabio Sambugaro

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 08, 2008 at 03:16 PM

    Hi,

    I found the solution. Under /fsdb/.system/version/ in KM Content see a list of folders. In the filesystem I don't see anything. If I try to delete the folders I receive an error. So I create the first level of folders under /fsdb/.system/version/... with a bash script at filesystem level (the server is SuSE Linux Enterprise Server) I recreate the same folders as in the KM Content. So in the KM Content I select the folders and delete them. Now the CM repository work fine.

    Thanks.

    Fabio Sambugaro

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.