![]() | ![]() | ![]() | ![]() | ![]() |
When the indexing process occurs for external entities from Oracle data stores, and the entities in turn have child entities, the process might fail with the following error message in the index logs:
In the datahub log, you can see errors and exceptions like the following, followed by a full stack trace:
2020-02-07 16:27:52.891 ERROR 18318 --- [titionExecutor1] c.s.f.d.s.d.l.j.s.i.d.DocumentCompleter : service [9823d62f73a7615f] Document completer failed with an exception
2020-02-07 16:27:52.892 ERROR 18318 --- [titionExecutor1] c.s.f.d.s.d.l.j.s.i.d.DocumentCompleter : service [9823d62f73a7615f] java.util.concurrent.ExecutionException: org.apache.metamodel.jdbc.UncheckedSQLException: java.sql.SQLException: [SAS][Oracle JDBC Driver][Oracle]ORA-01795: maximum number of expressions in a list is 1000
2020-02-07 16:27:58.346 ERROR 18318 --- [oaderExecutor10] org.apache.metamodel.jdbc.JdbcUtils : service [9823d62f73a7615f] Could not execute compiled query: [SAS][Oracle JDBC Driver][Oracle]ORA-01795: maximum number of expressions in a list is 1000, Error code=1795, SQL state=HY000
java.sql.SQLException: [SAS][Oracle JDBC Driver][Oracle]ORA-01795: maximum number of expressions in a list is 1000
This issue can occur when the configured chunk-size value for indexing is 1000 or greater.
A fix for this issue is planned for a future software release.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Visual Investigator | Linux for x64 | 10.6 | 10.6 | Viya | Viya |