Common OracleJob-Related Errors

This topic lists typical errors that are due to misconfiguration.

ORA-20800: JCS-02006: user <user> does not exist within database <database>

Symptoms

The OracleJob job reaches status Error and the job has a Remote ID.

Specific Error Message

ORA-20800: JCS-02006: user example does not exist within database example
ORA-06512: at  "CRIMSON.JCS_INTERNAL", ligne 1528
ORA-06512: at  "CRIMSON.JCS_INTERNAL", ligne 600
ORA-06512: at  "CRIMSON.JCS_EMU_MSG", ligne 643
ORA-06512: at  "CRIMSON.JCS_EMU_MSG", ligne 209
ORA-06512: at  "CRIMSON.JCS_EMU_MSG", ligne 113
ORA-06512: at  "CRIMSON.JCS_INTERNAL", ligne 465
ORA-06512: at  "CRIMSON.JCS", ligne 117
ORA-06512: at  line 2

at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
 at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
 at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
 at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
 at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
 at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
 at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
 at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
 at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3857)
 at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
 at com.redwood.scheduler.oraclejob.service.OracleJob.finalizeJob(OracleJob.java:500)
 at com.redwood.scheduler.oraclejob.service.OracleJob.execute(OracleJob.java:391)
 at com.redwood.scheduler.systemjobservice.impl.JobWorker.doWork(JobWorker.java:245)
 at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)
 at java.lang.Thread.run(Thread.java:662)

Resolution

Add a Redwood Server user matching the name of the Oracle user specified in the Run As User field, grant that user the scheduler-user or redwood-login role, and import the user. Note that the name must match the Oracle user (case-sensitive).

ORA-01017: invalid username/password; logon denied

Symptoms

The OracleJob job reaches status Error and the job has no Remote ID.

Platform

This error can occur in Redwood Server version 8 or higher.

Specific Error Message

-- JOB RUN STACK TRACE --
java.sql.SQLException: ORA-01017: invalid username/password; logon denied

 at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
 at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:406)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
 at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:799)
 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:368)
 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508)
 at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:203)
 at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510)
 at com.redwood.scheduler.oraclejob.impl.OracleJobHelper.getConnection(OracleJobHelper.java:488)
 at com.redwood.scheduler.oraclejob.service.OracleJob.getConnection(OracleJob.java:547)
 at com.redwood.scheduler.oraclejob.service.OracleJob.execute(OracleJob.java:378)
 at com.redwood.scheduler.systemjobservice.impl.JobWorker.doWork(JobWorker.java:245)
 at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)
 at java.lang.Thread.run(Thread.java:662)

Resolution

The process definition does not have a Run As User set; this should be set to the credential. Note that the name must match the Oracle user (case-sensitive).

JCS-132004: JDBC credential for user <user>@System_Oracle not found.

Symptoms

The OracleJob job reaches status Error and the job has no Remote ID.

Platform

This error can occur in Redwood Server version 8 or higher.

Specific Error Message

-- JOB RUN STACK TRACE --
JCS-132004: JDBC credential for user EXAMPLE@System_Oracle not found.
 at com.redwood.scheduler.jdbc.service.impl.JDBCCredentialHelper.getCredential(JDBCCredentialHelper.java:604)
 at com.redwood.scheduler.jdbc.service.impl.JDBCCredentialHelper.determineRunAsUserCredentials(JDBCCredentialHelper.java:460)
 at com.redwood.scheduler.oraclejob.service.OracleJob.execute(OracleJob.java:366)
 at com.redwood.scheduler.systemjobservice.impl.JobWorker.doWork(JobWorker.java:245)
 at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)
 at java.lang.Thread.run(Thread.java:662)

Resolution

Create a credential that matches the user in the Oracle database with the EndPoint System_Oracle.

onsiteTopic