Hi,
Have u tried using the log_archive_dest_n parameter? Plz check the following info in the SMO 3.0.2 IAG:
http://now.netapp.com/NOW/knowledge/docs/SnapManager/relsmoracle301/html/software/install/cloning/task/t_sm_clon_creating-smo-smsap-db-clone-specs.htm...
Specify any Oracle parameters that should be set to a different value in the cloned database than in the source database. If you are using Oracle 9 or 10, you must specify the first three parameters.
- Background dump
- Core dump
- User dump
- (Optional) Archive logs
If you do not specify archive logs for the destination, SnapManager creates the clone in NOARCHIVELOG mode. SnapManager copies this parameter information into the clone’s init.ora file.
Note: If a parameter entered conflicts with a parameter that SnapManager for Oracle must change to create the clone, the clone operation is aborted and you receive an error message.
Example
The following example displays the parameter syntax to use in the clone specification.
<parameters>
<parameter>
<name>log_archive_dest_1</name>
<value>LOCATION=/mnt/path/clonename/archive</value>
</parameter>
</parameters>
Also are u using the enterprise edition of Oracle in which case the LOG_ARCHIVE_DEST param might be deprecated. Check the following link:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams099.htm