Cannot Execute Batchloader From Command Line - LAUNCHER_SOURCE_EXECUTABLE undefined (Doc ID 1329319.1)

Last updated on MAY 18, 2017

Applies to:

Oracle WebCenter Content - Version 7.5.1 to 11.1.1.4.0 [Release Stellent to 11g]
Information in this document applies to any platform.

Symptoms

Unable to run batchloader from command line.  Content Server runs normally. 

Errors in logs: 

launcher updating skipped because LAUNCHER_SOURCE_EXECUTABLE undefined

system 06.09 16:37:50.408 main Configuring tracing verbose: true; sections: systemdatabase
systemdatabase 06.09 16:37:52.858 main Database type: Oracle
systemdatabase 06.09 16:37:52.859 main Database version: Oracle Database 11g Release 11.1.0.0.0 - Production
systemdatabase 06.09 16:37:52.859 main Database driver name: Oracle JDBC driver
systemdatabase 06.09 16:37:52.859 main Database driver version: 11.1.0.6.0-Production+
systemdatabase 06.09 16:37:52.860 main DB supports column change: true
systemdatabase 06.09 16:37:52.860 main DB supports column delete: true
(internal) 06.09 16:37:55.216 main The InboundRefinery Support Component is enabled, but no IBR providers are enabled
systemdatabase 06.09 16:37:55.457 main Unable to set transaction isolation level. READ_COMMITTED and SERIALIZABLE are the only valid transaction levels
systemdatabase 06.09 16:37:55.461 main Initializing Connection. Executing query: ALTER SESSION SET optimizer_mode = 'FIRST_ROWS_100'
systemdatabase 06.09 16:37:55.462 main Initializing Connection. Executing query: ALTER SESSION SET NLS_LENGTH_SEMANTICS = 'CHAR'
systemdatabase 06.09 16:37:55.464 main Initializing Connection. Executing query: ALTER SESSION SET NLS_SORT = 'BINARY'
systemdatabase 06.09 16:37:55.465 main Initializing Connection. Executing query: ALTER SESSION SET NLS_COMP = 'BINARY'
systemdatabase 06.09 16:37:55.467 main Initializing Connection. Executing query: ALTER SESSION SET CURSOR_SHARING = 'FORCE'
systemdatabase 06.09 16:37:55.468 main Initializing Connection. Executing query: alter session set events '30579 trace name context forever, level 2'
systemdatabase 06.09 16:37:55.521 main Unable to set transaction isolation level. READ_COMMITTED and SERIALIZABLE are the only valid transaction levels

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