We never drop and recreate tables in production. We do regularly in test. Recently we used the ALTER statement to remove a column in a table. The internal or short name was obviously MAX_P00001 because now we only have a MAX_P00002 and a MAX_P00003(using DSPFFD). In test, the table has MAX_P00001 and MAX_P00002 but no 3. In test, we have a common library for the I/O modules. These modules are used by all test DB2 libraries. If we restore the production version of above mentioned table into a test library, we get a -901 on the select. If we recompile the I/O program into the library with the restored table, then it works. Is there any way of forcing the production table to use MAX_P00001 and MAX_P00002 without dropping and recreating the table?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!