Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Database Upgrade Guide for DB2 UDB for z/OS > Preparing a Development Environment for a Siebel Upgrade > About Moving TablesEnvironments: Development environment only. This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade. Some of the Siebel tables will have columns added to them as part of the upgrade. When this happens, the length of the record will increase causing it to require a larger table space or bufferpool. Moving the identified tables to a new, larger and differently named table space allows you to maintain the model of multiple tables in each table space which is present for all pre-7.7 schemas. Before you move the tables, you need to remove any standard or custom views using an SQL DROP command. Complete the following procedure to find the views that are defined on a table. NOTE: The example used in the procedure assumes that you are creating a new 16K table space within the same database as the older, smaller table space. To find views that are defined on a table This SQL statement produces the drop statements into a sequential dataset:
To process these drop statements on the z/OS host, you need to create a PDS member with the output from the preceding statement. Then submit this member through DSNTEP2 using JCL. You can also list these tables in the override.inp file. This will cause the tables to be recreated in a new database with one table space and one table. If you are using the preconfigured storage control file, you do not need to move any tables as a preupgrade task. This is because the existing schema is not being preserved and all tables will be recreated in the 1:1:1 model. |
![]() |
![]() ![]() |
Siebel Database Upgrade Guide for DB2 UDB for z/OS | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |