Hello sir, Not sure if it is tee's problem. Tee works well in my workstation, but it will take a long time on cluster. See the example below. Could you if possible show me the reason why tee spends so long time while it is working on cluster?
This simple tests below illustrate how rep_age can take 30 times longer than necessary: 1. Without tee @3 seconds /home/sqdev16> time echo ' > SET TRANSACTION ISOLATION LEVEL READ COMMITTED, READ WRITE, NO ROLLBACK OFF, > MULTI COMMIT ON; > DELETE WITH MULTI COMMIT FROM > manageability.instance_repository.problem_instance_table > WHERE (gen_ts_lct) < ((CURRENT_TIMESTAMP) - CAST(CAST(0 AS INTEGER) AS > INTERVAL HOUR(2))); ' | sqlci >>>> --- SQL operation complete. >>+> --- 0 row(s) deleted. >> End of MXCI Session real 0m3.354s user 0m0.184s sys 0m0.099s 2. With tee @ 1 minute 46 seconds: /home/sqdev16> time echo ' > SET TRANSACTION ISOLATION LEVEL READ COMMITTED, READ WRITE, NO ROLLBACK OFF, > MULTI COMMIT ON; > DELETE WITH MULTI COMMIT FROM > manageability.instance_repository.problem_instance_table > WHERE (gen_ts_lct) < ((CURRENT_TIMESTAMP) - CAST(CAST(0 AS INTEGER) AS > INTERVAL HOUR(2))); ' | sqlci | tee -a junk >>>> --- SQL operation complete. >>+> --- 0 row(s) deleted. >> End of MXCI Session real 1m45.969s user 0m0.180s sys 0m0.093s Thanks, Jie Gao, Jie (Kyrie) BIP, DS CDC, HPIT *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- Email: jie....@hp.com
