IdcAnalyze Tool does not work with External Search Collection

(Doc ID 2314506.1)

Last updated on OCTOBER 09, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.6.0 to 12.2.1.3.0 [Release 11g to 12c]
Information in this document applies to any platform.

Symptoms

On : 11.1.1.8.0 version, Content Server

When attempting to run IdcAnalyze the following error occurs.

ERROR
-----------------------

./IdcAnalyze -doall
>system/6 10.04 08:58:06.159 main Configuring tracing verbose: true; sections: system, analyzer, requestaudit
>system/6 10.04 08:58:06.160 main Configuring tracing verbose: true; Services: *
>system/6 10.04 08:58:06.160 main Configuring tracing verbose: true; Threads: *
>(internal)/3 10.04 08:58:15.586 main !csProviderConfigError,ExternalSearchProvider
(internal)/3 10.04 08:58:15.586 main at intradoc.common.DefaultTraceImplementor.appendStackTrace(DefaultTraceImplementor.java:348)
(internal)/3 10.04 08:58:15.586 main at intradoc.common.DefaultTraceImplementor.traceDumpException(DefaultTraceImplementor.java:467)
(internal)/3 10.04 08:58:15.586 main at intradoc.common.DefaultReportHandler.message(DefaultReportHandler.java:510)
(internal)/3 10.04 08:58:15.586 main at intradoc.common.DefaultReportDelegator.message(DefaultReportDelegator.java:140)
(internal)/3 10.04 08:58:15.586 main at intradoc.common.Report.messageInternal(Report.java:172)
(internal)/3 10.04 08:58:15.586 main at intradoc.common.Report.message(Report.java:145)
(internal)/3 10.04 08:58:15.586 main at intradoc.common.Report.error(Report.java:408)
(internal)/3 10.04 08:58:15.586 main at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2593)
(internal)/3 10.04 08:58:15.586 main at intradoc.server.IdcSystemLoader.initProviders(IdcSystemLoader.java:2277)
(internal)/3 10.04 08:58:15.586 main at intradoc.server.IdcSystemLoader.finishInit(IdcSystemLoader.java:408)
(internal)/3 10.04 08:58:15.586 main at IdcAnalyze.doBackgroundProcess(IdcAnalyze.java:88)
(internal)/3 10.04 08:58:15.586 main at IdcAnalyze.main(IdcAnalyze.java:63)
(internal)/3 10.04 08:58:15.586 main at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
(internal)/3 10.04 08:58:15.586 main at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
(internal)/3 10.04 08:58:15.586 main at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
(internal)/3 10.04 08:58:15.586 main at java.lang.reflect.Method.invoke(Method.java:606)
(internal)/3 10.04 08:58:15.586 main at intradoc.loader.IdcClassLoader.invokeMain(IdcClassLoader.java:392)
(internal)/3 10.04 08:58:15.586 main at intradoc.loader.IdcClassLoader.startMain(IdcClassLoader.java:187)
(internal)/3 10.04 08:58:15.586 main at intradoc.loader.IdcClassLoader.main(IdcClassLoader.java:152)
(internal)/3 10.04 08:58:15.586 main Caused by: intradoc.data.DataException: !csJdbcUnableToCreateConnection,ExternalSearchProvider,
(internal)/3 10.04 08:58:15.586 main at intradoc.jdbc.JdbcConnectionUtils.getConnection(JdbcConnectionUtils.java:126)
(internal)/3 10.04 08:58:15.586 main at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:85)
(internal)/3 10.04 08:58:15.586 main at intradoc.provider.Provider.init(Provider.java:72)
(internal)/3 10.04 08:58:15.586 main at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2577)
(internal)/3 10.04 08:58:15.586 main ... 11 more
(internal)/3 10.04 08:58:15.586 main Caused by: java.sql.SQLException: No suitable driver found for
(internal)/3 10.04 08:58:15.586 main at java.sql.DriverManager.getConnection(DriverManager.java:596)
(internal)/3 10.04 08:58:15.586 main at java.sql.DriverManager.getConnection(DriverManager.java:187)
(internal)/3 10.04 08:58:15.586 main at intradoc.jdbc.JdbcConnectionUtils.getConnection(JdbcConnectionUtils.java:107)
(internal)/3 10.04 08:58:15.586 main ... 14 more
FileSystemFileStore:1.0.0.0 started.
Content Management System Server. Version 11.1.1.8.0PSU-2015-10-08 10:52:37Z-r135627
Copyright (C) 1996-2013, Oracle and/or its affiliates. All rights reserved.

Analyzing tables...
-------------------------------
........WARNING: Checking dRevClassIDdDocName consistency can take several minutes on large repositories!


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In a command prompt run the tool from the bin directory:   IdcAnalyze -doall

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, IdcAnalyze can not check the search collection.

Changes

The following KM note was followed to create an external search collection: <Document 1444813.1> Setting up External Search Collection in WCC 11g
The config.cfg has the configuration entry: IndexerDatabaseProviderName=ExternalSearchProvider

There is a provider configured in the content server to use an external search collection.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms