948024 wrote:No. Once you opened that second database, it started life with it's own set of archive sequences, it's own set of scn's. You can't just graft in an archivelog from some other database, no matter how closely you think those databases are related. As far as oracle is concerned, they have zero relationship to each other.
great thanks guys it really helped,
i recoverd the database completely i cross checked the rows which i inserted after taking the backup and they are in the new database
guys just one more thing.
now both the databses hav same data......
again if i want to insert rows in primary database and do
alter system archive log current;
then cn i directly paste that archive log into second database archvive folder and do shutdown immediate
948024 wrote:If that's what you want, you need to look at DataGuard. There are variations on a theme, but the basic idea is that the secondary database stays in 'recovery mode', and all redo from the primary is shipped to the secondary and applied. But both databases have to be specifically configured for it, not simply you grabbing the archives from one database and trying to force them onto another.
thanks alot buddy, i was in a wrong perception tht if i keep adding archvie log from main database to this clone database it will keep updating.