Joords Oracle DBA blog

The Oracle Database Listener is the database server software component that manages the network traffic between the Oracle Database and the client. The Oracle Database Listener listens on a specific network port (default 1521) and forwards network connections to the Database. One of the most misunderstood security issues with the Oracle Database is the security of the Listener. The listener is one of the most critical components to database operations; It is responsible for the ability to have a client/server communication In dedicated mode it is responsible for creating a new process (or thread on Windows) on behalf of the client and setting up the communications On Windows each such server process actually speaks on a new tcpip port and the listener redirects the client to this port On Unix streaming continues on the original port The listener forks a new process The listener then closes its own fd-s; the new process continues to speak on the fd-s ...

Summary of the presentation  "Oracle Enterprise Manager Cloud Control 12c" by Rob Zoeteweij Result of 3 years development More than 500 enhancement requests included Code rewrite Enhanced user interface Management Oracle products via plug-ins New credentials model Personalisation support Customizable page layout Add / remove regions in page Specify data displayed in region Pre-defined homepage layouts Click on the link  Oracle Enterprise Manager Cloud Control 12c  to get the presentation.

OracleRemExecService is a service which is only used temporarily by the OUI It gets removed when OUI is finished with it, therefore, it will have a value of 'DISABLED' until a reboot - then it will simply be gone, ignore and leave this service untouched. The Oracle Windows service "OracleRemExecService" to execute various commands from Oracle applications like DBCA and GUI. The service itself relies on a named pipe to receive the commands.

Instance caging is another small but useful feature of Oracle Database 11g Release 2. Thanks to it the database resource manager is able, to limit the number of CPUs that can be used by a given instance simultaneously. This feature allows Oracle DBAs to easily manage Oracle Instance CPU consumption. There are two typical approaches to instance caging for a server: Over-provisioning: In this approach, the sum of the CPU limits for each instance exceeds the actual number of CPUs on the system. Partitioning:In this approach, the sum of allocate CPUs for each instance is equal to the number of CPUs on the server

Setting init.oraparameter ASM instance Use default values sesettings. Only processes parameter may need modification. Processes parameter setting is dependent on the number of databases that connect to ASM processes= 25 + 15n, where n = # databases connected to ASM . If max processes is reache on ASM, this indicaties offten on hanging processes of cluster agents or RMAN processes

The Oracle's strategic solution for real time data integration. Oracle GoldenGate provides low-impact capture, routing, transformation, and delivery of transactional data across heterogeneous environments in real time

RACcheck RACcheck is a RAC Configuration Audit tool designed to audit various important configuration settings within a Real Application Clusters (RAC), Oracle Clusterware (CRS), Automatic Storage Management (ASM) and Grid Infrastructure environment.