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

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

@TVR ,  in the link you shared, Step 11/12 shows how to setup .props file. Note that the property gg.handler.kafkaconnect.topicMappingTemplate is used, instead of TopicName. Check your .props file and see what is set there.  ... View more

Hi @TVR ,   Next time please provide more details on what you have tried, what versions of Kafka and Oracle you are using, and what you are trying to achieve. In the meantime, it looks like TopicName is not a supported parameter since some version of Oracle GoldenGate. The alternative parameter is topicMappingTemplate. Please see Oracle documentation here: https://docs.oracle.com/goldengate/bd123110/gg-bd/GADBD/using-kafka-handler.htm#GADBD458     Hope that helps, Alex ... View more

Hi @roshanbi,   There is no equivalent of oracle's EXTRACTVALUE in Kudu or Impala SQL. XML is not one of the supported formats.    I think your approach of running the SQL with EXTRACTVALUE as part of the sqoop job is a good one. That way you are writing the fields you need into target Hive table and from there insert into Kudu. This would be the fastest path and would work if you are not planning to get more fields from your source XML table in the future.   An alternative approach is to use Hive with a 3rd party SerDe for XML. Then let Hive do the conversion from XML format to something like Avro, and then create your Impala table based on that Avro data. This way is more involved, but gives you flexibility in terms of the schema.    Hope that helps, Alex ... View more

The broken pipe character seems to be a special hex character that is longer than a single byte. The workaround here could be doing a ReplaceText processor on your Excel file first, replacing broken pipe character with something simple like a comma (,) and then doing conversion to CSV.       ... View more