10g RMAN-2001 error because of new DBID after cloning.

Hello all,

My first post!! :D After cloning our 10g dev instance from production my RMAN backup is now failing with the error: "RMAN-20001: target database not found in recovery catalog" because the clone gets a new DBID.

My question: is it possible to tell/update the 10g RMAN catalog of the new DBID without having to register the database again? This way I don't have to perform a 'register database' and configure the channels again and again after each clone.

Thanks,

SteveV