03-14-2017 04:12 AM - edited 03-14-2017 04:13 AM
Hello all,
I am having a problem with DDGC, every time I run it ends with an error, below I attach the log. (dedupeserver.log at C:\Program Files\Symantec\Symantec DLO\Dedupe\Tomcat\logs)
In addition, I ran Data Integrity Scanner twice with the 4 options selected and nothing appears solve it. Any idea?
DLO is 7.6
Thanks !!!
Alex
[14/03/2017], [08:01:22:481], [DEDUPE_TRACE], [Thread-12], [10.130.1.76], GarbageCollectionDAO::getChunkFileInfoForGC: Found chunk file with free space between hashId 334335 and 335335 = \#ECF#FJA-F38664\#ECF#RT109\1\01\01\CF02
[14/03/2017], [08:01:37:582], [ERROR], [catalina-exec-20], [10.114.15.25], SessionInMemoryDAO::isChannelValid: com.result.Result: (20133) Could not validate the channel.
[14/03/2017], [08:01:37:582], [ERROR], [catalina-exec-20], [10.114.15.25], DedupeServer::getRootResource: (20045) Could not validate the session. (20133) Could not validate the channel. (20133) Could not validate the channel.
[14/03/2017], [08:01:54:446], [ERROR], [Thread-12], [10.130.1.76], DBAccess::updateChunkFileOffsets: (20105) Could not update cri to hash table.
[14/03/2017], [08:01:54:477], [ERROR], [Thread-12], [10.130.1.76], DBAccess::deleteCleanUpTable: (20109) Could not delete file from cleanup table.
[14/03/2017], [08:01:54:976], [ERROR], [Thread-12], [10.130.1.76], GarbageCollectionDAO::doGarbageCollection: (20105) Could not update cri to hash table.
[14/03/2017], [08:01:54:992], [ERROR], [Thread-12], [10.130.1.76], GarbageCollectionDAO::run: (20083) Error occurred during garbage collection. (20105) Could not update cri to hash table.
[14/03/2017], [08:01:54:992], [ERROR], [catalina-exec-4], [10.130.1.76], DedupeManager::performGarbageCollection: (20121) Error occurred during garbage collection with error number 105.
[14/03/2017], [08:01:56:396], [ERROR], [catalina-exec-13], [10.190.1.226], SessionInMemoryDAO::isChannelValid: com.result.Result: (20133) Could not validate the channel.
[14/03/2017], [08:01:56:396], [ERROR], [catalina-exec-13], [10.190.1.226], DedupeServer::getRootResource: (20045) Could not validate the session. (20133) Could not validate the channel. (20133) Could not validate the channel.
[14/03/2017], [08:02:02:542], [ERROR], [catalina-exec-4], [10.114.16.43], SessionInMemoryDAO::isChannelValid: com.result.Result: (20133) Could not validate the channel.
[14/03/2017], [08:02:02:542], [ERROR], [catalina-exec-4], [10.114.16.43], DedupeServer::getRootResource: (20045) Could not validate the session. (20133) Could not validate the channel. (20133) Could not validate the channel.
[14/03/2017], [08:02:12:433], [ERROR], [catalina-exec-22], [10.114.15.57], SessionInMemoryDAO::isChannelValid: com.result.Result: (20133) Could not validate the channel.
[14/03/2017], [08:02:12:433], [ERROR], [catalina-exec-22], [10.114.15.57], DedupeServer::getRootResource: (20045) Could not validate the session. (20133) Could not validate the channel. (20133) Could not validate the channel.
[14/03/2017], [08:02:37:783], [ERROR], [catalina-exec-9], [10.113.15.19], SessionInMemoryDAO::isChannelValid: com.result.Result: (20133) Could not validate the channel.
[14/03/2017], [08:02:37:783], [ERROR], [catalina-exec-9], [10.113.15.19], DedupeServer::getRootResource: (20045) Could not validate the session. (20133) Could not validate the channel. (20133) Could not validate the channel.
03-15-2017 12:58 PM
Hi All, any idea? I'd better open a case, right ?
Thanks !!!
Alex
03-15-2017 09:07 PM - edited 03-15-2017 09:10 PM
Hi,
Not get DLO answers in forum, I dont know why.Might be this product is not so widely used.
I also log case for any help. You please log a case and answer it here once it resolved for help others.
If you have a license upgrade option, try upgrade to newer version 9.0. I am using 9.0
03-16-2017 11:20 AM
Hi Shiju,
Thanks for your help ans comments.
The version 9 does not convince me yet, I found variuos problems to update the DLO agents and I do not use the external connection. Also the dlo agent icon does not show if there are errors or warnings ... etc.
woefully, I'll open a case on veritas.
Thanks,
Alex