E-DB2: Why Does Script Fail During Tools Upgrade To 8.53.02 on CREATE TABLE PSYPSMSGEVENTS?
(Doc ID 1561539.1)
Last updated on MARCH 04, 2019
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.52 and later
Information in this document applies to any platform.
*** currency checked Feb 2015 ***
*** currency checked July 2016 ***
*** currency checked March 2018 ***
*** currency checked Feb 2019 ***
During a tools only upgrade from 8.52.xx to 8.53.02
Why Failing on step- Running the Updated peopletools script
CREATE TABLE PSYPSMSGEVENTS (PORTAL_NAME VARGRAPHIC(30) NOT NULL, PORTAL_OBJNAME VARGRAPHIC(30) NOT NULL, EVENT_NAME VARGRAPHIC(30) NOT NULL, HTML_FIELD_NAME VARGRAPHIC(65) NOT NULL, MSG_EVENT_TYPE VARGRAPHIC(1) NOT NULL, MSG_EVENT_DATA VARGRAPHIC(254) NOT NULL, FIELD_EVENT_TYPE VARGRAPHIC(1) NOT NULL, MSG_EVENT_DATALONG DBCLOB(600 M)) IN PTTBL INDEX IN PTTBLIDX LONG IN PTTBLLOB NOT LOGGED INITIALLY
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0204N "PTTBLLOB" is an undefined name. SQLSTATE=42704
Update: The following solution will apply during an Installation using tools 8.53.xx.
The PTDDLUPG script ran in 'Creating Tablespaces' step created 3 new tablespaces - PSIMAGE2, PSIMAGE2IDX, and PSIMAGE2LOB.
During the 'converting DB2 Data Types' section of the change assistant template. Running the PTUPGDB2LOBCONV_ALTERTABLES script results in dozens of tablespaces that did not exist and had to be manually created. Why were the necessary tablespaces not created during the creating tablespaces step?
Also attempting to run the PTUPGDB2LOBCONV_ALTERTABLES it failed creating table PSYFT_CAT_ITEMS. There is a page size issue with creating the table in the PSIMAGE talbespace. None of the previous steps obviously altered or recreated the tablespaces appropriately for DB2.
SQL0670N The row length of the table exceeded a limit of "4005" bytes. (Table
space "PSIMAGE".) SQLSTATE=54010
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document