Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.13.9
-
None
-
None
Description
Current Situation
- when Oracle is used for the JobScheduler database and a custom field (CLOB) was added to the history data model, the JobScheduler returns an unknown exception when executing the <show_history> command and logs the SCHEDULER-360/SOS-1343 exceptions.
- Command: <show_history job="/my_job" />
- JobScheduler response:
<?xml version="1.0" encoding="ISO-8859-1"?> <spooler> <answer time="2021-10-04T13:17:52.210Z"> <ERROR code="std::exception" text="Unknown exception" time="2021-10-04T13:17:52Z"/> </answer> </spooler>
- JobScheduler log:
{scheduler} Execute <show_history job="/my_job"/> ...Exception SOS-1343 Datensatz wird mit dem Feld zu groß ...[xc.insert "TRANSFER_HISTORY String0(2147483647) offset=(ohne Offset?)"] ...[xc.insert "Record_type(16 Felder)"] .Exception SCHEDULER-360 Error when accessing database table SCHEDULER_HISTORY [SOS-1343 Datensatz Record_type(16 Felder) wird mit dem Feld TRANSFER_HISTORY String0(2147483647) offset=(ohne Offset?) zu groß]
How to reproduce
- use the Oracle database
- add a custom CLOB column to the SCHEDULER_HISTORY table
- execute the <show_history job="/my_job" /> command
- my_job - is any existing job
Desired Behavior
- <show_history> command should support the character large objects (CLOBs).
Attachments
Issue Links
- is related to
-
JS-1926 custom history fields - increasing the maximum allowed size
- Released