Skip to content

log

Retrieving GoldenGate logs, reports, and diagnostics with the REST API

I often need to retrieve report files or logs from GoldenGate deployments, and I wanted to find ways of automating this. Hence this blog, about retrieving all available logs with GoldenGate REST API. I previously wrote about the GoldenGate log files. Some of them (extract.log, replicat.log and others) are in fact just filters of other logs (ggserr.log or restapi.log). These… 

Increase GoldenGate 26ai log retention

GoldenGate logs are a powerful source of information when debugging or analyzing your deployments. However, some of these logs have a rather low retention period in active deployments. They might then not even be useful for debugging if you send them to your dbi consultants or the Oracle support for analysis. So how can you increase GoldenGate log retention ?… 

GoldenGate 26ai logs explained

GoldenGate logs are a powerful source of information when troubleshooting or analyzing your deployments. However, there is at least one log file per service in the Microservices Architecture. This means that for a GoldenGate setup with multiple deployments, you can quickly have tens of log files to search for information. In that context, knowing where to look is important, especially… 

Querying GoldenGate REST API log efficiently

In this blog post, I will guide you on how to query the restapi.log file of your GoldenGate deployments more efficiently. These logs are a valuable source of information for GoldenGate administrators but are unfortunately not easy to analyze. In fact, their format is not really suited for a complex analysis. With what I present here, you could improve the… 

MongoDB log analysis : a comprehensive guide

Contrary to other DBMS, MongoDB self-managed deployments generate logs in a JSON format, which can be quite intimidating at first. But instead of hoping to never have to look at the logs, you can use some tools and tips to navigate them more easily and not waste time finding the information you’re looking for. Log format overview Inside /var/log/mongodb/mongod.log (or… 

HowTo – Enable & Disable traces on Documentum

If you are here, I assume you are looking for some ways to enable traces on Documentum. There are already a few blog posts here and there showing some information but Documentum being what it is, i.e., a quite complex machinery, there are just way too many places/configurations that you can have traces/debug information on. Therefore, I also wanted to… 

Logs from Filebeat to Logstash to Elasticsearch – 2

As promised in the previous blog, I will show how to configure Filebeat to push logs to Logstash, then to Elasticsearch. This for sure will not cover all use cases, but will give you an idea on how it works. Configure Filebeat First of all, let’s understand how Filebeat works. We have to configure inputs and outputs, once Filebeat starts… 

ELK Stack – Filebeat vs Logstash

Filebeat and Logstash are both comprised in ELK Stack, in this blog we will compare both with some use cases. So, you can then take the most appropriate to your case. Introduction Are you using ELK for logging? In fact, both Filebeat and Logstash can be used to send logs from a file-based data source to a supported output destination.… 

Documentum CS 7.* – 777 permission on jobs log

A few weeks ago at a customer, our team was involved in a security control. We tracked files with 777 permission and we detected that logs generated by Documentum jobs have 777 permissions. Security before anything else, that’s why this topic was my top priority! First of all, I checked the logs on some Content Servers, and I had the… 

ODA : Free up space on local filesystems

Introduction When you work on ODA you sometimes get struggled with local filesystem free space. ODA has terabytes of space on data disks, but local disks are still limited to a raid-1 array of 2x 480GB disks. And only few GB are dedicated to / and /u01 filesystems. You do not need hundreds of GB on these filesystems, but I… 

Documentum – How to really configure the D2 JMS logs starting with JBoss/WildFly

If you are working with Documentum for quite some time, you are probably familiar with the logback.xml file that can be used to configure the D2 logs. In this blog, I will be talking only about the Content Server side of this configuration. As you probably know, Documentum upgraded the JMS to use JBoss 7.1.1 “recently” (several years already) and even WildFly9.0.1…