Skip to main content
TVR
Silver ⭐️⭐️
July 7, 2021
Question

Unable to set property on handler 'kafkahandler'

ERROR 2021-05-26 15:43:41.000453 [main] - Unable to set property on handler 'kafkahandler' (oracle.goldengate.handler.kafka.KafkaHandler). Failed to set property: Topic
Name:="BUBB-MX_ALL_SOFT" (class: oracle.goldengate.handler.kafka.KafkaHandler).
oracle.goldengate.util.ConfigException: Failed to set property: TopicName:="BUBB-MX_ALL_SOFT" (class: oracle.goldengate.handler.kafka.KafkaHandler).

6 replies

aakulov
Platinum ⭐️
Platinum ⭐️
July 7, 2021

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

Translate
TVR
TVRAuthor
Silver ⭐️⭐️
July 7, 2021

Hi,

 

Kafka Vesion:2.1

Oracle GoldenGate:12.3

 

Please let me know if you need any other inputs.

 

Thanks in advance

 

 

 

 

Translate
aakulov
Platinum ⭐️
Platinum ⭐️
July 8, 2021

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

Translate