Partition managing scripts

The following script should allow a simler managing of the TMCDB partitioned tables. In detail:

1) TmcdbCreatePartTableSpaces.sh USERLIST TABLESPACE_BASE_NAME
	This script will create the needed tablespaces to host the partitions at tables creation time.
	The following parameters are to be specified:
		USERLIST 		-> List of users getting quota on the tablespaces
		TABLESPACE_BASE_NAME 	-> Base name for the tablesspaces. They will be created as TABLESPACE_BASE_NAMEYYYYMMDD starting at the beginning of current month. If possibile use the same name as username.

2) TmcdbCreatePartTables.sh USERNAME PASSWORD TABLENAME TABLESPACE_BASE_NAME PARTITIONING_COLUMN
	This script will create a partitioned TABLENAME table on a certain number of previously created TableSpaces. 
	The script expects to have the clean (no indexes or other objects created in) partition creation script in a directory (defined in a variable, default ./) with the name TABLENAME.sql. 
	Any index (at the moment maximum 1) have to be defined (ad will be created) in a distinct file called TABLENAME_idx.sql. (the infrastructure is ready to create multiple indexes from scripts called: TABLENAME_idx_[1-9].sql)
	The following parameters are to be specified:
		USERNAME		-> User Creating the table
		PASSWORD		-> Password of the user
		TABLENAME		-> Name of the table (will be use to identify the script, too)
		TABLESPACE_BASE_NAME	-> Base name for the tablesspaces, as defined at TmcdbCreatePartTableSpaces.sh run
		PARTITIONING_COLUMN	-> Table column used for partitioning(has to be TIMESTAMP based)

3) TmcdbRotatePart.sh USERNAME PASSWORD TABLENAME TABLESPACE_BASE_NAME
	This script will rotate the partitions based on the definition of a couple of variables at the beginning KEEPBACK, KEEPFORWARD. The script will detect currently available partitions and will add further ones if the last (newer) partition is older than KEEPFORWARD months in the future. 
	In the second phase the script will check if the first (older) partition is older than KEEPBACK months. In this case the partition will be
exchanged with a temporary table and dropped. At this point, if the tablespace hosting the partition is self-contained, it will be removed creating a
transportable tablespace set. If the tablespace is not self contained, it will be extracted only when it will become so.
	Each operation is logged and a snapshot of the table and partitions status saved at the beginning of the operation. The status file will be created in the directory /backup/expdp/ALMA/PARTITIONS_YYYYMMDD (date of the rotation process), the logfile name will be parttable_status_USERNAME_TABLENAME-YYYYMMDD.log (date of the rotation process), the datafile copies (compressed in the background) will be called USERNAMEYYYYMMDD.dbf.bz2 (date of the partition end) and the TTS dumpfile and log TABLENAMEYYYYMMDD.dmp, TABLENAMEYYYYMMDD.log.
