Posted by Marcelo Lopes on Jan 12, 2011
For this blog I have compiled the main information specifically considering 11gR2 platform, but the concepts and idea also apply for older platforms as well.
Oracle provides the following JDBC drivers:
Oracle Call Interface (OCI) driver: For client-side use with an Oracle client installation.
Thin driver: A pure Java driver for client-side use, particularly with applets. It does not require an Oracle client installation.
Server-side Thin driver: Is functionally the same as the client-side Thin driver, but is for code that runs inside Oracle Database instance and needs to access a remote server.
Server-side internal driver: For code that runs inside the target server, that is, inside Oracle Database instance that it must access.
Read the rest of this entry . . .
Posted by Marcelo Lopes on Jan 21, 2009
If you don’t want to deal with missteps, I recommend that you test your standby database to facilitate the failover or switchover process.
This procedure is very useful when you have physical standby databases for testing and other purposes that require read-write access to the standby database. Also, it improves your checklist in the event of an error or disaster.
By using Snapshot standby databases, redo data is not applied until you convert the snapshot standby database back into a physical standby database, and after all local updates to the snapshot standby database are discarded.
Requirements
The following requirements need to be met in order to create a snapshot standby.
Read the rest of this entry . . .
Posted by Marcelo Lopes on Dec 3, 2008
Sometimes you find yourself facing some little problem. You don’t believe it’s a bug or software deficiency, and you spend some time trying to find out what is the silly thing you’ve missed. Here are a handful of issues in Grid Control that cause this sort of little problem.
Issue One
The overall status of a multi-task job is shown as succeeded even though some of the steps within the job have failed.
This is expected behavior. The various tasks (such as T1, T2, T3) of the multi-task job are part of a serial step-set. The status of a serial step-set is considered to have succeeded if the last step has succeeded. This happens if the “Condition” and “Depends On” are not used while creating the task.
To avoid this default behavior use “Condition” and “Depends On” while creating the task.
Read the rest of this entry . . .
