Troubleshooting
Problem
When upgrading the history database for release 9.1.0 error DB21034E is seen
Symptom
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0104N An unexpected token "," was found following "TEST_START TIMESTAMP".
Expected tokens may include: "<space>". SQLSTATE=42601
Cause
Extra commas included in file upgrade_ANY_ADDCOLS.sql
Diagnosing The Problem
The error message in SYMPTOM above is seen
Resolving The Problem
This command:
ALTER TABLE MDL.JHR_JOB_HISTORY_RUNS
ADD COLUMN JHR_LATEST_START TIMESTAMP,
ADD COLUMN JHR_CRITICAL CHAR ( 1 ),
ADD COLUMN JHR_PROMOTED CHAR ( 1 ) ;
Should not have any commas. You can just remove the commas and rerun the command or install APAR IV55012 from Fix Central (see RELATED INFORMATION below).
upgrade_ANY_ADDCOLS.sql is shipped as part of a zip file- the customer unzips it wherever they choose and then they run an upgrade script that updates the database (dbupgrade). Besides replacing the file, a manual update could be done (followed by running the dbupgrade script) as follows:
.
Find:
ALTER TABLE MDL.JHR_JOB_HISTORY_RUNS
ADD COLUMN JHR_LATEST_START TIMESTAMP,
ADD COLUMN JHR_CRITICAL CHAR ( 1 ),
ADD COLUMN JHR_PROMOTED CHAR ( 1 )
.
and change it to:
ALTER TABLE MDL.JHR_JOB_HISTORY_RUNS
ADD COLUMN JHR_LATEST_START TIMESTAMP
ADD COLUMN JHR_CRITICAL CHAR ( 1 )
ADD COLUMN JHR_PROMOTED CHAR ( 1 ) ;
.
If upgrade_ANY_ADDCOLS.sql was deleted after running the dbupgrade script it would be necessary to unzip the file again, make the change to upgrade_ANY_ADDCOLS.sql and then run the dbupgrade script.
.
To see if this procedure was followed, check in DB2 if table:
MDL.JHR_JOB_HISTORY_RUNS
has the JHR_PROMOTED CHAR column
Related Information
Was this topic helpful?
Document Information
Modified date:
13 September 2019
UID
swg21662469