HADR ROS for Db2 Purescale Merged

Right now, Db2 Purescale primary operational databases are delivering transactional data services in a primary location. Meantime in a secondary location, owning the same Purescale configuration and computing capability is running the HADR secondary role for high availability. Resource utilization of secondary site in less than 20% of the potential and it's the best platform to execute complex Read Only query and large offload of data generated by Warehousing ETL, now targeted toward the primary database. We mitigate the impact of this non-transactional workload adding Uncommitted Read isolation level in most of involved queries. Anyway it is really a waste of resources to keep empty more than 80% of allocated processors and I/O HBA and RAM of the secondary location, except in a potential Disaster Recovery. In production primary database are executing more than 3.000 parallel SQL transactions by more than 1 million users on +20TB compressed and 15.000 tables. INAIL owns 8 purescale simila clusters in the two locations. HADR ROS on purescale will be the best solution to rebalance the workload among the different location because, due to the integration of Primary DB2 with multiple components, as Appl. Server, Security, Oracle database and so on, it's not possible to split the production in the two different locations, although Db2 itself allow this option. About Db2 Shadow Table, number of tables, kind of data, volume of transactions and CDC efforts and consume to replicate do not suggest this solution.