Professional Documents
Culture Documents
Backup xml, env, dbc files and shutdown application services using clone automation scripts.
Step 2:
Step 3:
Step 4:
Dismount the T23 diskgroup (+DSKGRP1) on both aebdbt03 and aebdbt04 servers.
Fire the BCV split sync command from aebdbt03 server as oracle user.
$ sudo /scripts/acs/mkcct23bcv
Step 5:
After the spilt copied to T23 servers mount the disk group on all ASM instances (aebdbt03 & aebdbt04
servers).
$ asmcmd
ASMCMD> cd DSKGRP1
ASMCMD> ls -lt
ASMCMD> cd TKP29
ASMCMD> ls -lt
Make sure all datafiles, controlfile, tempfile and onlinelog exists.
Step 2:
Check the db_name, it should be 'TKP29', but instance name will be cct231.
If the above commands shows no recover, then Open the database otherwise we may need to recover
the database.
Now the database will open as 'TKP29', but instance name will be cct231.
Step 3:
Remove the extra log groups (from 30 to 47) which are pointing to ‘+DSKGRP1/tkp29’.
$ asmcmd
ASMCMD> cd DSKGRP1
ASMCMD> rm spfiletkp29.ora
Step 6:
Bring up the database in cluster mode, the listeners will automatically come up once the DB is started.
BCV Split process completed, CCT23 is up in cluster mode, now you continue with the post clone steps
with automation process.....have a nice day...