vlt rcp from 6.0 to 6.3

Avatar

Avatar

harishv99010453

Avatar

harishv99010453

harishv99010453

01-05-2018

We are doing a new instance upgrade (6.0 to 6.3) and we are copying content from 6.0 to 6.3 using vlt rcp (3.1.16...we used latest vlt as well 3.1.44), however we are getting below error

[ERROR] Internal error while retrieving NodeInfo.
java.io.IOException: ' ' not allowed in name
at org.apache.jackrabbit.spi2davex.ItemInfoJsonHandler.key(ItemInfoJSONHandler.java:205)
at org.apache.jackrabbit.commons.json.JsonParser.parse(JsonParser.java:108)
at org.apache.jackrabbit.commons.json.JsonParser.parse(JsonParser.java:73)
at org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.getItemInfos(RepositoryServiceImpl.java:365)
at org.apache.jackrabbit.jcr2spi.state.WorkspaceItemStateFactory.createDeepNodeState(WorkspaceItemStateFactory.java:122)
at org.apache.jackrabbit.jcr2spi.state.TransientISFactory.createDeepNodeState(TransientISFactory.java:106)
at org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.loadNodeEntry(NodeEntryImpl.java:1163)
at org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.getDeepNodeEntry(NodeEntryImpl.java:429)
at org.apache.jackrabbit.jcr2spi.hierarchy.HierarchyManagerImpl.getNodeEntry(HierarchyManagerImpl.java:137)
at org.apache.jackrabbit.jcr2spi.ItemManagerImpl.getNode(ItemManagerImpl.java:168)
at org.apache.jackrabbit.jcr2spi.SessionImpl.getNode(SessionImpl.java:513)
at org.apache.jackrabbit.vault.util.RepositoryCopier.copy(RepositoryCopier.java:253)
at org.apache.jackrabbit.vault.util.RepositoryCopier.copy(RepositoryCopier.java:230)
at org.apache.jackrabbit.vault.cli.CmdRcp.doExecute(CmdRcp.java:70)
at org.apache.jackrabbit.vault.cli.AbstractVaultCommand.doExecute(AbstractVaultCommand.java:46)
at org.apache.jackrabbit.vault.cli.AbstractVaultCommand.doExecute(AbstractVaultCommand.java:33)
at org.apache.jackrabbit.vault.util.console.commands.AbstractCommand.execute(AbstractCommand.java:37)
at org.apache.jackrabbit.vault.util.console.ExecutionContext.doExecute(ExecutionContext.java:171)
at org.apache.jackrabbit.vault.util.console.ExecutionContext.execute(ExecutionContext.java:132)
at org.apache.jackrabbit.vault.util.console.AbstractApplication.execute(AbstractApplication.java:302)
at org.apache.jackrabbit.vault.cli.VaultFsApp.execute(VaultFsApp.java:614)
at org.apache.jackrabbit.vault.util.console.AbstractApplication.run(AbstractApplication.java:251)
at org.apache.jackrabbit.vault.cli.VaultFsApp.main(VaultFsApp.java:126)
[ERROR] Error while retrieving src node /content/dam/PROJ/public/sourcelib/photos/product: javax.jcr.RepositoryException: ' ' not allowed in name

However we are not able to identify for which node this RepositoryException is occurring.

We tried to create packages for the node but as packages is having lakhs of dam assets underneath it, packagemanger is also failing with error as:
Error during processing:

java.io.IOException: File too large
at java.io.FileOutputStream.writeBytes(Native Method)

Any thoughts on the above issue ? And do we have any other best approaches other than vlt rcp ?

Replies

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

02-05-2018

When upgrading to AEM 6.3 - best approach is to follow the AEM 6.3 upgrade docs. See - Upgrading to AEM 6.3

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

02-05-2018

If you follow all of these docs and still running into an issue, then there is nothing more the community can do. You need to open a support ticket.

Avatar

Avatar

Kunwar

Employee

Avatar

Kunwar

Employee

Kunwar
Employee

03-05-2018

My cross question would be why are we going the VLT route coz versions won't be migrated for Pages and Assets if you migrate content from one instance to the other. Also, product implementation has changed in accordance to Oak so things like LDAP, SAML might break if you rely on content migration using VLT or crx2oak.

Just use these tools as a means of delta migration when the final cutover happens to new systems else rely on inplace upgrade as directed in Adobe documentation.