A crucial step after installing a Veridata server is to set up Veridata agents. And, as mentioned in a previous blog post about GoldenGate Veridata installation, Oracle didn’t bother to indicate when an agent is failing. For instance, the following agent named vdt_agent1 starts successfully: And this agent named vdt_agent2 fails to start: Zero difference in the agent.sh output, yet…
At a customer, we are upgrading Control-M Agents running on Windows/Unix from 9.0.00.400 to 9.0.19.200 using Agent Deployment, an upgrade of one agent fails with error talking about communication issue between Control-M/server and Control-M agent: Testing Communication with Control-M/Server using new Control-M/Agent binaries failed, Control-M/Agent Upgrade aborted, please check Log and agent installation requirements On the other hand, the agent…
Introduction I am currently setting up a new “Base Image” virtual machine (Red Hat Enterprise Linux 7.6) which will be used to create 6 brand new Oracle database servers requested by a customer. Besides installing and configuring the OS, I also have to install 3 Oracle Homes and one Cloud Control Agent 13c. An OMS13c server already exists including an…
In order to start index agents, you have several ways, depending on how you need to start them. 1. Use the documentum job dm_FTIndexAgentBoot. If you setup start_index_agents=T in the server.ini, the job will be called when the docbases are started. 2. Use the web interface: Login to http://server:9200/IndexAgent/ with docbase credentials and select “Start in normal mode” 3. Login…
When working with the IDS, you might face some interesting behaviors as mentioned in the last blog I wrote for example. This one will focus on the SSL part of the IDS on the target side. On this blog, I will start with showing the content of our start/stop scripts and how it is working in non-SSL, then switching to SSL…
We had a strange behavior by a customer regarding the indexing queue. We used to have two IA configured and we uninstalled one. I figured out that we still had indexing queue requests for the old index agent while it was totally uninstalled. I checked the following objects to see if the agent was still configured somewhere: dm_fulltext_index, dm_ftengine_config, dm_ftindex_agent_config.…
