Article - CS408736
Unable to extract WTDocument ContentMetadata with message "No wt.doc.WTDocument|CONTENT objects to extract" when using Windchill Bulk Migrator
Modified: 11-Jan-2024
Applies To
- Windchill Bulk Migrator 12.0.2.5
Description
- Unable to extract WTDocument ContentMetadata with message "No wt.doc.WTDocument|CONTENT objects to extract"
- Extraction Report shows that there are some WTDocument FILECONTENT present in Source Windchill environment
- Below message is observed in Extraction Server log :
[RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO util.WBMMigrationSourceSitHelper - Migration source site information already exist. [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO wbmutil.CommonConnectionPool - Total Connections with Staging database are: 10 [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO session.WBMSessionCache - Initialized WBM session cache [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO session.WBMSessionServerHelper - ### ENTER: Registering session:637828 for type:wt.doc.WTDocument|CONTENT [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO session.WBMSessionServerHelper - Entry not Found for type:wt.doc.WTDocument|CONTENT [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO session.WBMSessionServerHelper - ### EXIT: Registering session:637828 for type:wt.doc.WTDocument|CONTENT [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO session.WBMSessionServerHelper - ### ENTER: Unregistering session:637828 from cache for type:wt.doc.WTDocument|CONTENT [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO session.WBMSessionServerHelper - Removing the entry, threadcount is 0 [RMI TCP Connection(17)-xxx.xx.xxx.xx] INFO session.WBMSessionServerHelper - ### Exit: Unregistered session:637828 for type:wt.doc.WTDocument|CONTENT
- Below message is observed in Extraction Client log :
[main] INFO client.Extractor - *******************No wt.doc.WTDocument|CONTENT objects to extract**************************
[main] INFO wbmutil.CommonConnectionPool - Total Connections with Staging database are: 10
[main] INFO wbmutil.CommonConnectionPool - Total Connections with Staging database are: 10
[main] INFO wbmutil.CommonConnectionPool - Total Connections with Staging database are: 10
[main] INFO wbmutil.CommonConnectionPool - Total Connections with Windchill database are: 10
[main] INFO sql.ExtractionFailureSqlHelper - creating failure lower boundary timestamp to list of failure ids map
[main] INFO wbmutil.CommonConnectionPool - Total Connections with Staging database are: 10
[main] INFO extractor.ExtractedClassStatistics -
******************************************************************************************************************************
Extraction Statistics for the Object Type:wt.doc.WTDocument(FILECONTENT)
Processed Items Count :0
Staged Items count :0
Filtered Items count :0
Failed object count :0
Finished extraction. You can see more details by running reports.
******************************************************************************************************************************
- Below is the Extraction query captured from client log :
WITH cont as ( select con.idA2A2 idA2A2, con.namecontainerInfo CONTAINER_NAME, con.classnameA2A2 CONTAINER_TYPE, wtorg.name CONTAINER_ORGANIZATION_NAME from dbuser.PDMLinkProduct con join WTOrganization wtorg on con.idA3organizationReference=wtorg.idA2A2 union all select con.idA2A2 idA2A2
This is a printer-friendly version of Article 408736 and may be out of date. For the latest version click CS408736