Infrastructure at your Service
By Franck Pachot . Usually, cursor invalidations do not interrupt the current execution of the cursor. You can even drop a table while a query on it is running and the query may end successfully. However some invalidations will throw internal errors that are catch and the cursor execution restarts transparently. I’ve reproduced one here to show the symptoms: it’s a different EXEC_SQL_ID so the restarts are not accounted within the same SQL Monitoring.
On a customer site, one of the users complained about being kicked out each time he wanted to create new documents in D2. This issue is happening in a default deployment of D2 and D2Config in a WebLogic Domain.We found out that the user sessions for D2Config and D2 are conflicting together. This issue occurs if D2Config and D2 applications are opened in the same browser using different TABs and if the user is navigating…
What is the relation between dfc.date_format and dm_LogPurge? This is the question we had to answer as we hit an issue. An issue with the dm_LogPurge job. As usual once a repository has been created we are configuring several Documentum jobs for the housekeeping. One of them is the dm_LogPurge. It is configured to run once a day with a cutoff_days of 90 days. So all ran fine until we did another change. On request of…
Maybe you had some issues with UCF in DA as me. I had this for no reason since few days at a customer. The problem was that we use SSL with DA and the Unified Content Facilities (UCF) wasn’t happy about it. Thus, in this short blog I’ll speak about troubleshooting UCF. The error I got happened when trying to edit, view or create documents; I had a popup saying an error occured with UCF….
By Franck Pachot . 12c SQL Plan Directives, a side effect, a bad application design, a bug… and the occasion to show how to quickly troubleshoot. An application has long response time since 12c migration. No blind guesses, no reason to compare with previous version, let’s just troubleshoot performance with methodical approach.
I discover a strange error with a customer about the default trace. As you know, SQL Server has a default trace with a lot of events like the data and log file growth. This trace is enabled by default and you have five .trc files located in the installation directory of SQL Server.
I post a little tips for orphan database-users that we cannot drop so easily in the SSISDB… I discovered this by a customer and it was very tricky to find the explanation and the solution. This is the reason why I will share it with you…
In all blogs that I read, the solution is just to change the retention period to a reasonable value. Yes, it is true but in some case you need to go deeper in the analysis… Like you, I changed the retention period, ran the cleanup but finally, I had always a big database… Why, Why, Why? My first step for this analysis, is to see in the SSISDB, the Disk Usage by Table Reports from…
In a recent project I faced the following situation: One the one hand I had to execute scripts on a customer’s workstation while on the other hand I had to integrate the results of these scripts into a report on my own workstation. The question was how to efficiently do this without sending dozens of mails to myself. One solution would be to create one script which produces all output and send the results by…
Recently, I have installed an Oracle 11.2.0.4 RDBMS on a server, and I wanted to install the latest Patch Set Update (PSU) 11.2.0.4.4 from October 2014. During the execution, I fell on the error “Archive not applied” and the job failed. This is how to quickly fix this issue. While installing the PSU 11.2.0.4.4 from October 2014 on my Oracle 11.2.0.4 database server, I experienced the following error: The following actions have failed: Archive not…
