You can use the admin_copy_schema stored procedure to help you with renaming (it actually copies) the schema. Please refer to the following URLs for more info:
IBM DB2 9.5 Information Center for Linux, UNIX, and Windows
Conveniently create new versions of your database objects
Here is an example of copying schema 'TEST' to TEST2':
test@p6db2serv /home/test > db2 "call SYSPROC.ADMIN_COPY_SCHEMA ('TEST','TEST2','COPY', NULL, NULL, NULL, 'COPYSCHEMA', 'COPYERROR')"
Value of output parameters
--------------------------
Parameter Name : ERRORTABSCHEMA
Parameter Value : COPYSCHEMA
Parameter Name : ERRORTABNAME
Parameter Value : COPYERROR
Return Status = 0
Note: admin_copy_schema needs to use the systoolspace tablespace. If you don't have it, it needs to created prior to using the procedure. Here is an example of creating it in an automatic storage db:
test@p6db2serv /home/test > db2 "CREATE TABLESPACE SYSTOOLSPACE MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 4"
DB20000I The SQL command completed successfully.
The old schema can be removed using the admin_drop_schema stored procedure. Here is an example:
test@p6db2serv /home/test > db2 "CALL SYSPROC.ADMIN_DROP_SCHEMA('TEST', NULL, 'ERRORSCHEMA', 'ERRORTABLE')"
Value of output parameters
--------------------------
Parameter Name : ERRORTABSCHEMA
Parameter Value : ERRORSCHEMA
Parameter Name : ERRORTAB
Parameter Value : ERRORTABLE
Return Status = 0
Please check the restrictions/usage notes in the manual. I'd highly recommend taking a backup prior to copying/dropping the schema if this is an important database (just in case something happens).