unable to delete metadata associated with the expired content from the docbase/rdbms

Hi,

We have observed that when we expire the content in production server,it gets deleted from the file folder system in the webserver but corresponding metadata is not getting deleted from the database.

This behaviour is present in both WIP as well as LIVE. In database its version is shown as WIP and Active with respect to WIP and Active server.

We have come across two such incidents where file is deleted from the server and metadata is still there in the database.Because of this behaviour it still shows in the webpage and customers are raising the incidents.

We have raised a ticket with the Database team to delete the metadata from the back-end Oracle Database.

Could you let us know any steps to be done from Documentum side meanwhile.

Kindly do the needful.

Kind regards,

sowmya melanathur.

Find more posts tagged with

Comments

kcrkarthik

IDS or IDSx? What version?

The removal of entry from published database should happen by default.

Does the removal of entry from DB happen when you forcefully expire a file or delete it? In what all scenarios the entry is getting removed and NOT removed?

-karthik

yamangoyal

It occurs some times when you expired the content or delete the content.

Try to run the Full content refresh from the DA, it will resolve your problem.

kcrkarthik

Some steps for analyzing the issue: https://solutions.emc.com/emcsolutionview.asp?id=esg90290

sowmya.melanathur

Hi karthik,

The file content is deleted but the metadata associated is not getting deleted,.We r using IDSX 6.7 version.We would like to know any DQL query to delete the expired content metadata from the database or is there any other way to fix this issue.?

Please let me know your sugegstions on this asap.

regards,

sowmya.

kcrkarthik

Quick fix would be to manually run publishing from DA. First try without full refresh publishing. That should take care of removing the entries of expired ones from the DB.

If that doesn't happen, then try with full-content refresh.

My question repeats again, does the entry get removed when you manually expire the content?

-karthik

yamangoyal

Finally you have to do full-content refresh.

sowmyaanantha

hi karthik

I have few more queries to figure out which files are getting expired from the wip and active sites in prod env and whether there is any particular way to find out how the files are getting expired and the particular files which are getting expired ?

forexample either through DQL query or api command to find them out ? and if so how the expired files are getting deleted from the file system / web server and how the metadata is getting deleted from the database( wip and active version) and is there any stored procedure involved in connection with the database to delete the expired content metadata from the DB and how the database knows it or any job runs at the back end or through DFC program the DB knows and gets called to delete the expired content metadata ?

Is there any particular way to handle this issue.Please post your comments on this with steps and the DQL query /DFC program to know/ trace which files are expired and how the expired files content is getting deleted and how to delete the metadata associated with them from DB through DQL.

regards

sowmya melanathur.

sowmyaanantha

Hi Karthik

Could you guide me how this full content refreshing / manually running publishing is done through DA?

regards,

sowmya melanathur.

kcrkarthik

Navigate to the SCS node in DA. Right click on the appropriate publishing config and select Publish, in the screen that appears, choose the appropriate check boxes and click OK.

-karthik

kcrkarthik

Find my answeres here:

1) The content files have a attribute "a_expiration_date", when set to a value, the monitor lifecycle job checks from the value. if the current time has reached or exceded that value, it moves the content to Expired. During the next pulishing cycle run, these files are makred to be removed from the published locations.

2) did you check the support solution link i mentioned. it has the details of how to find the query SCS uses. No stored procs are used. everything is thru DQL's read through the SCS user guide also. it tells you the publishing process. there are certain key items (like Properties.XML) involved in the publishing process. So, to identify the root cause, you have to dig into those files. and to do that, you need to understand what they are used for.

3) mentioned already. try running publishing through DA (first without full-refresh). in my experience this step takes care of clearing the unnecessary ones. only if this doesn't work, try full-refresh.

Help me with few more details:

a) is the metadata published only to 1 db or multiple DBs?

b) you still haven't answered this one, Does the removal of entry from DB happen when you forcefully expire a file or delete it?

c) Do you have auto publish enabled in the WebPublisher's WcmApplicationConfig.properties?

BTW, i dont have any environment (with IDSx) in hand to check exact details.

-karthik