Script redo migration to asm win2003 10.2.0

Question

I am trying this script for online log migartion to ASM(found on the internet)
my databse name is orcl, asm instance is +ASM using 10.2.0 on win 2003
also i already done the previous steps correctly when i am firing this sql script its show me error:
can somebody tell me where i am wrong.
SQL> @C:\a.sql;
39 /
declare
ERROR at line 1:
ORA-00349: failure obtaining block size for '+TESTDB_DATA1'
ORA-06512: at line 26
here is the script:
set serveroutput on
declare
cursor rlc is
select group# grp, thread# thr, bytes/1024 bytes_k, 'NO' srl
from v$log
union
select group# grp, thread# thr, bytes/1024 bytes_k, 'YES' srl
from v$standby_log
order by 1;
stmt varchar2(2048);
swtstmt varchar2(1024) := 'alter system switch logfile';
ckpstmt varchar2(1024) := 'alter system checkpoint global';
begin
for rlcRec in rlc loop
if (rlcRec.srl = 'YES') then
stmt := 'alter database add standby logfile thread ' ||
rlcRec.thr || ' ''+TEST'' size ' ||
rlcRec.bytes_k || 'K';
execute immediate stmt;
stmt := 'alter database drop standby logfile group ' || rlcRec.grp;
execute immediate stmt;
else
stmt := 'alter database add logfile thread ' ||
rlcRec.thr || ' ''+TEST'' size ' ||
rlcRec.bytes_k || 'K';
execute immediate stmt;
begin
stmt := 'alter database drop logfile group ' || rlcRec.grp;
dbms_output.put_line(stmt);
execute immediate stmt;
exception
when others then
execute immediate swtstmt;
execute immediate ckpstmt;
execute immediate stmt;
end; end if;
end loop;
end;

Answer 1

I can't debug your script, but I can tell you that it is much easier to "migrate" your logfiles to ASM.
You point your DB_CREATE_FILE_DEST parameter to the database area diskgroup (if not already set)
You point your DB_RECOVERY_FILE_DEST parameter to the recovery area (if not already set)
You look at the old logfiles and remember their number
Then you say
alter database add logfile;
as many times as you want to have new loggroups to be on ASM
Then you drop all the old loggroups.
That is done interactively (in about 5 minutes), though.
But you could script that with a .sql script also quiet easily, instead of "breaking your fingers" with PL/SQL, couldn't you? :-)
Kind regards
Uwe
http://uhesse.wordpress.com