Repeated error in the c2o.log: Evaluation of [AdaptiveServer Anywhere (ASA)] failed - missing ) in parenthetical (#2) - Evaluation of [thin] failed- ReferenceError: "thin" is not defined. (#2)
search cancel

Repeated error in the c2o.log: Evaluation of [AdaptiveServer Anywhere (ASA)] failed - missing ) in parenthetical (#2) - Evaluation of [thin] failed- ReferenceError: "thin" is not defined. (#2)

book

Article ID: 18531

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Process Automation Base

Issue/Introduction

Description:

The c2o.log contains multiple instances of the following errors:

Evaluation of [AdaptiveServer Anywhere (ASA)] failed - missing ) in parenthetical (#2)

Evaluation of [thin] failed- ReferenceError: "thin" is not defined. (#2)

What do these errors mean and how can I fix them?

Solution:

One or both of these errors is reported when a JDBC operator is in use in a PAM process and the Sybase driver required fields and/or the Oracle driver required fields have not been cleared from the Connection Wizard. To correct this, do the following:

  1. Find your process definition containing the JDBC operator.

    <Please see attached file for image>

    Figure 1

    Select that operator to view the properties

  2. Under properties, click on the Database Server Login tab:

    <Please see attached file for image>

    Figure 2

  3. Select the "Connection Wizard" button

    <Please see attached file for image>

    Figure 3

  4. On the Database Type field at the top, click the drop down and select "Sybase".

    <Please see attached file for image>

    Figure 4

    On the Sybase Server Type field, click the value shown, Adaptive Server Anywhere (ASA), and delete it so that it looks like this:

    <Please see attached file for image>

    Figure 5

  5. Now for Database Type, select Oracle:

    <Please see attached file for image>

    Figure 6

    For Oracle Driver Type, delete the value, thin so that it looks like this:

    <Please see attached file for image>

    Figure 7

  6. And finally switch back to the Database Type you were originally using and click OK.

Save your process definition and that will stop these errors from appearing in the c2o.log.

Environment

Release: ITPASA99000-4.1-Process Automation-Add On License for-CA Server Automation
Component:

Attachments

1558696754618000018531_sktwi1f5rjvs16nk1.gif get_app
1558696752775000018531_sktwi1f5rjvs16nk0.gif get_app
1558696750972000018531_sktwi1f5rjvs16njz.gif get_app
1558696749028000018531_sktwi1f5rjvs16njy.gif get_app
1558696747175000018531_sktwi1f5rjvs16njx.gif get_app
1558696745363000018531_sktwi1f5rjvs16njw.gif get_app
1558696743399000018531_sktwi1f5rjvs16njv.gif get_app