Migrating to Oracle ASMLIB from AFD

Migrating to Oracle ASMLIB from AFD

Migrating to Oracle ASMLIB from AFD

Why if you do not like to use AFD? You could follow instructions below to come back to our old love, ASMLIB. Although it is possible to migrate to Oracle ASMLIB from AFD, as I mentioned in the Introducing Oracle AFD, Oracle AFD is the superset of the ASMLIB, and it is better to use Oracle AFD. Configuring Oracle AFD after Installation could reverse this migration.

Let me show you how to migrate Oracle ASMLIB from AFD within a scenario:

Existing setup:

Before starting migrating to Oracle ASMLIB from AFD we check existing setup:

In the above review, we saw Oracle AFD has been started and ASM Disk string refers to Oracle AFD disk string path. The first step in practice is to set ASM Disk string so that it also refers to ASMLIB path.

In the following steps, we are going to remove Oracle AFD Configuration and start ASMLIB. As I mentioned in the Introducing Oracle AFD one of the limitations is that AFD and ASMLIB are mutually exclusive. The root user must do this configuration and this setting requires the Oracle Clusterware stack to be down on the local node.

You could find more information about Oracle AFD in MOS.

Unlike Oracle AFD, whose installation exists in the Grid Home, the ASMLIB has to be installed by OS tools like yum.

It is time to start Clusterware stack on the local node.

Let me do some verification:

There is an optional step for clearing configuration, which is to remove Oracle AFD path

I hope you’ve enjoyed reading this post.

 

Leave a reply:

Your email address will not be published.

Captcha loading...