In an Oracle Database we can mention following auditing types:
Mandatory Auditing causes database start-up/shut-down and SYSDBA-SYSOPER login logout information to be written into AUDIT_FILE_DEST. This auditing cannot be turned off and it's always written into operating system directory specified with
Let us take a look at the process of configuring Goldengate 12c to work in an Oracle 12c Grid Infrastructure RAC or Exadata environment using DBFS on Linux x86-64.
Simply put the Oracle Database File System (DBFS) is a standard file system interface on top of files and directories that are stored in database tables as LOBs.
In one of my earlier posts we had seen how we can configure Goldengate in an Oracle 11gR2 RAC environment using ACFS as the shared location.
One use for the 188.8.131.52 addition of PL/SQL functions in the WITH clause is to get the HIGH_VALUE of a partition in a usable column format.
FUNCTION char2000(i_tab in varchar2, i_part in varchar2)
RETURN VARCHAR2 IS
Can you use the Execution Plan of an INSERT statement to identify if the INSERT was executed in Parallel ?
Here's a brief demonstration :
SQL*Plus: Release 184.108.40.206.0 Production on Sat May 16 22:27:49 2015
Earlier this week preparations have been started to add the Goldengate software to the Grid infrastructure of 220.127.116.11.3 on the Billing environment on production. As part of that scenario I also had to add a Vip address that is to be used by the Goldengate Software as part of high(er) availability. In my concept Goldengate Daemons are running on on Node only by default.
"Oracle Fusion Middleware is the leading business innovation platform for the enterprise and the cloud. It enables enterprises to create and run agile, intelligent business applications while maximizing IT efficiency through full utilization of modern hardware and software architectures. Solutions and products include Exalogic Elastic Cloud, data integration, business process management, business intelligence, identity management, Cloud application foundation, service-oriented architecture, WebCenter, and development tools."
Wouldn’t be nice to get regularly informed how (in)compliant you are with Oracle licenses in an easy – centralized – way, and therefore not have to worry about visits of Oracle’s LMS – License Management Services? I think that would be nice for the most of us. Running LMS-scripts on the target databases, hosts and middleware is for now the most thorough way to get informed about possible incompliancy. Or in some cased, using some clever – but informal and mostly incomplete – scripting on the OEM-repository.
Tweaking LLVM Obfuscator + quick look into some of LLVM internals.