HiveAccessControlException suggests you are accessing this s3 location through a SQL engine (Hive or Impala perhaps). Check in Ranger, under Hadoop SQL, if the policies are set properly there to access the table you are looking at.   Also, is this a RAZ-enabled environment, by any chance? If it is, please see here for RAZ setup specific to Hive table access: https://docs.cloudera.com/management-console/cloud/fine-grained-access-control-aws/topics/raz-aws-create-ranger-policies.html     Hope this helps, Alex ... View more

Hi @Chhavi , the discussion of HIPPA certification is an intricate one. I would recommend to talk to your Cloudera account representative as there are many details to go through.    Thank you, Alex ... View more

@Chhavi , if you are asking about "Apache NiFi", then the answer is Appache NiFi is not and never will be HIPPA certified or certified for anything similar. This is because it's an Apache project and nobody owns certification for it as such.   With that said, it is likely possible to configure NiFi in a HIPPA compliant way (e.g. repository encryption). You'll need to work with your NiFi vendor for that and Cloudera is happy to help.     Regards, Alex Akulov ... View more

Hi @grlzz ,   CDSW is typically installed/runs on edge nodes, so CM going down does not necessarily preclude you from accessing CDSW. However, if certs expired across the cluster then all services may be inaccessible.   Regarding your question for command line access to CDSW. There is a CLI you can use for that: https://docs.cloudera.com/cdsw/1.9.2/cli-reference/topics/cdsw-cli-reference.html  The first thing you'll need to do to use the CLI is to generate some access keys from CDSW UI, so if you can't access CDSW UI, then you may be stuck until that is resolved.    Have you opened a support case for this?   Kind regards, Alex Akulov ... View more

Could you provide the output of the DESCRIBE command for your table in Kudu. ... View more

Hi @Anyy ,   Your SQL statement seems to be malformed. You have "from" keyword duplicated. Please fix and try running again.   If that helps, please accept as solution.     Regards, Alex ... View more

Strange....    As a test can you replace your hard-coded toppic name with something like ${tableName} or just try a different hardcoded string and see if that gets you further along. Not saying that's a solution, but trying to eliminate causes.   Also, you mentioned you've implemented other flows already. Could it be that the topic name BUBB-MX_ALL_SOFT is already taken in your kafka cluster and thats why goldengate handler can't create the topic (though I would expect it to just write to the existing topic, instead of throwing an error).    I also found this on Oracle site that may have your answer. You'll need an Oracle account to look if there is a solution though. https://support.oracle.com/knowledge/Middleware/2512462_1.html   Could this also be an encoding or trailing character issue in the props file between Unix and AIX?   Overall this sounds like a GoldenGate error that may be better answered by Oracle community.     Regards, Alex ... View more