The SSH connection is established initially at the beginning of the action and the <command> tag executes the command passed within the tags, but it takes a while(~ around 3 hours) for the command to execute, and in the meantime this action gets updated to COMPLETED and proceeds on to the next subsequent action, whereas former command is still in execution phase.   This exception arises when Oozie starts on the latter SSH action while the prior SSH action is still in execution.   So why does Oozie presumes the prior SSH action as completed yet the command is still in process? ... View more

Have you considered creating a copy of the table as external (in new location you want) and then INSERT into NewTable SELECT * FROM OldTable? ... View more

Thanks Venkat! ... View more

That command worked a treat, I wasn't aware that the configuration xmls varied based on the purpose of the host they are deployed to.    I've got the superuser running now, thanks for the help ... View more

Thanks @venkatsambath. It worked. ... View more

This property is hive specific so it can be either enabled on hiveserver2 server level or in the client session level but is not possible to set on queue level (coz scheduler dont understand hive specific properties). If you set this property in hiveserver2 level - then all hive client will be mandated to use where clause when user run query on partitioned table.   Other property which you can use is hive.metastore.limit.partition.request  https://docs.cloudera.com/documentation/enterprise/5-14-x/topics/admin_hive_tuning.html Quoting from link Set the hive.metastore.limit.partition.request parameter to 1000 to limit the maximum number of partitions accessed from a single table in a query. See the Apache wiki for information about setting this parameter. If this parameter is set, queries that access more than 1000 partitions fail with the following error: MetaException: Number of partitions scanned (=%d) on table '%s' exceeds limit (=%d) Setting this parameter protects against bad workloads and identifies queries that need to be optimized. To resolve the failed queries: Apply the appropriate partition filters. Override the limit on a per-query basis. Increase the cluster-wide limit beyond 1000, if needed, but note that this adds memory pressure to HiveServer2 and the Hive metastore.   ... View more

Thanks @venkatsambath & @EricL  this would certainly help in my hadoop journey.   Regards       ... View more

Thanks @venkatsambath    That helped.    Regards,  Ansar ... View more