export data getting warning message SQL27981W in a restrictive database?

Harishkumar .Pathangay

export data getting warning message SQL27981W in a restrictive database?

Hi,

I am having a restrictive database db2 11.1.2 Fix Pack 2 ESE.

When a user connects to database it is very restrictive unlike default database.

I had to grant connect on database, execute on CLP packages, usage on default user workloads. All is granted and fine.

I granted select on a table. I try to export data from that table. Got the following errors.

Authorization ID: "HPIN".  Operation: "EXECUTE". Object: "NULLID.SQLUBO05".  SQLSTATE=42501

Authorization ID: "HPIN".  Operation: "EXECUTE". Object: "NULLID.SQLUCO07".  SQLSTATE=42501

Authorization ID: "HPIN".  Operation: "EXECUTE". Object: "NULLID.SQLUPO00".  SQLSTATE=42501
SQL3020N  The user does not have the authority to run the specified EXPORT
command.
I have granted execute on those packages as well. Still I am getting following warning message.
Authorization ID: "HPIN".  Operation: "SELECT". Object: "SYSCAT.FUNCTIONS".  SQLSTATE=42501
SQL27981W  The utility could not verify presence of attached or detached data
partitions in the target table or the source table.
After that, I granted SELECT on SYSCAT.FUNCTIONS too.
But I am still getting following warning message.
SQL27981W  The utility could not verify presence of attached or detached data
partitions in the target table or the source table.
How to run export with getting warning message SQL27981W in a restrictive database.
I do not want to bind and give public access to export packages.
thanks,
harish pathangay 
Edited By:
Harishkumar .Pathangay[Organization Members] @ Jun 28, 2019 - 03:50 PM (Asia/Calcutta)

Harishkumar .Pathangay

RE: export data getting warning message SQL27981W in a restrictive database?
(in response to Harishkumar .Pathangay)

hi,

I tried binding db2cli.lst,db2ubind.lst and db2schema.bnd with grant public option.

still it does not help. Non-Restrictive database does not have that warning message.

how to get rid of that warning message?

thanks,

harish p