How to resolve "SQL0204N 'TMPBP32K' is an undefined name" during upgrading the MONITOR database
Yan Fang 1200008V6D Visits (18032)
Migrating refers to the process of moving applications and configuration information from an earlier version of a product to a later version of the product, or from one product to a different product. Upgrading refers to the process of installing a new release of the product on top of the previous release and updating the existing installation, configuration, and database in place.
To migrate from WebSphere Business Monitor V6.2.n, you must stop the source environment and upgrade the existing MONITOR and Business Space database schemas. You must also update the MONITOR database data. In this article, we use IBM Business Monitor v8.5.6 as a sample target migration environment but this article is also useful when the target environment is IBM Business Monitor v8.n and the source environment is WebSphere Business Monitor v6.2.n.
In our example, when we perform upgr
DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command.
By checking the upgr
CREATE USER TEMPORARY TABLESPACE UTMPTS32K PAGESIZE 32 K MANAGED BY
The SQL0204N error indicates buffer pool "TMPBP32K" does not exist in Monitor DB. By checking Monitor DB, not only does the buffer pool "TMPBP32K" not exist but also TABLESPACE UTMPTS32K did not exist.
And, the SQL that creates buffer pool "TMPBP32K" is not described in upgr
By checking step 5 as shown below in the Monitor V8.5.6's product documentation upgr
5. In WebSphere® Business Monitor V6.2, you can add the UTMPTS32K table space after you apply the V6.2 Fix Pack. Therefore, if you are upgrading a V6.2 DB2 database, check for the UTMPTS32K table space. If it exists, remove the following lines from the SQL file:
So where is buffer pool "TMPBP32K" created and how can the Monitor database be upgraded?
Below is our solution for your reference:
If you confirm that "TMPBP32K" buffer pool and TABLESPACE UTMPTS32K do not exit, actually it is not a correct status when running Monitor 22.214.171.124 DB since the buffer pool "TMPBP32K" and table space UTMPTS32K should have been created when creating the Monitor 126.96.36.199 DB by crea
Even if you do not have the above buffer pool and TABLESPACE, you still can do migration by following Upgr
------------- bufferpool for temp tablespace
If your crea
After creating buffer pool "TMPBP32K" in Monitor v188.8.131.52 server's DB using the above SQL command, we can perform upgr