Joords Oracle DBA blog

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

Static service name is an  important part in the failover and snapshot mechanisme by the Standby database for using as a HA and test enviroment. Oracle Net Service uses the TNSNAME to resolve the path to the database and initiates a connection to the listener at the target system using the service name in the TNSNAME entry. Command to change the snapshot database to physical standby database: DGMRL> CONVERT DATABASE "JOORDS_DR0" TO PHYSICAL STANDBY; During these operations the the snapshot database needs a restart of the database. When the database is down, the service that is specified by TNSNAME is not registerd so an Oracle Net Service connection cannot be made to the database.Result is a failed operation of the convert database to physical standby. Monitoring the listener.log will give you the information of the error. and what the request is ORA-12514: listener does not currently know of the service request in the connect descriptor