Posts by Yury Velikanov

EBS DBA: WF Mailer Override Address and Cloning: How to

I just recently faced an issue on how to automate the Workflow Mailer override address for development and testing environments during the EBS cloning process. The problem is that the only official way to set the override address in the latest ATG releases is to go through the OAM portal and change the override email via the GUI interface. I came to this solution.

EBS DBA: R12.1.2 Another Step for Automated Vanilla EBS Cloning

If you have tried to automate EBS cloning then you definitely know that you can’t get through without hacking and customizing the Oracle-provided Rapid Clone utility. One of the areas we should “hack” the code to make it running in batch scripts is the services startup bit. The problem is that by default straight after Rapid Clone is completed Oracle starts all the services on the Apps node and until now there wasn’t a way to change it.

Emergency Recovery or RMAN DUPLICATE Rerun Just Works!

One of the tasks that I was involved in was 700GB database emergency cloning for an important functional issue troubleshooting. It was 10.2.0.5 (10GR2) 64 Bit database on Linux. To make a long story short I gave the DUPLICATE command a try. I used the comand in this post to start the process. After 4h of the restore process I was horrified (you know how it is to work under time and management pressure) at seeing the following errors

EBS DBAs Be Warned! NOLOGGING Can Hit You Badly …

I’ve just come across an old known issue again today. Was working in the greatest and latest 12.1.2 Oracle e-Business Suite environment. Surprisingly, I face the old issue when WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES objects (among other objects) are set to NOLOGGING mode. The easiest solution is to switch the whole database to FORCE_LOGGING mode:

Oracle Setting High Naming Standards

As part of my preparation for the Exadata OCP Exam, I was reading through the “Oracle® Exadata Storage Server Software User’s Guide”. I found the two famous events in the Exadata world, “db file scattered read” and “db file sequential read” that cause so much confusion, have been renamed to “cell multiblock physical read” and “cell single block physical read” accordingly. Hopefully Oracle will port those events’ names to the RDBMS world as well in version 12c.

How to GNS process log level for diagnostic purposes?

I was troubleshooting a new GNS (Grid Name Services) functionality and noticed a-trace-level parameter in the GNS process string. Unfortunately there is no description in the documentation or MOS on how to change it to generate invaluable diagnostic information. NOTE: I am sure the documentation will be updated in Database 12c version (c for Cloud. For the time being the following should work for you.

Page 8 of 8« First...45678