Transferring archive log from Oracle 9i to Oracle 10g

I got a situation where I need to transfer archived Oracle 9i logs to an Oracle 10g database, from where they will be mined with a log miner and then used by Oracle thread capture / apply processes.

(Oracle 9 archived logs can be read by Oracle 10 logarithm - I can manually copy archived logs, manually log them and mine, grab and apply).

The difficulty is that the way the Oracle log archive is archived has changed slightly between 9i and 10g and the 9i database set up to transfer to the remote machine as follows:

log_archive_dest_state_2 = enable
log_archive_dest_2 = "service=OTHERMACHINE arch optional"

      

does not work any more.

I get this in 9i logs:

*** 2009-05-22 04:03:44.149
RFS network connection lost at host 'OTHERMACHINE'
Error 3113 attaching RFS server to standby instance at host 'OTHERMACHINE'
Error 3113 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'OTHERMACHINE'
Heartbeat failed to connect to standby 'OTHERMACHINE'. Error is 3113.
*** 2009-05-22 04:03:44.150
kcrrfail: dest:2 err:3113 force:0
ORA-03113: end-of-file on communication channel

      

And in 10g log I get:

Fri May 22 04:07:42 2009
WARNING: inbound connection timed out (ORA-3136)

      

My question is:

Does anyone know how I can set up my 9i or 10g server so that the 10g server accepts the 9i connection in such a way that I can transfer the archived 9i logs to the 10g server. It would be a bonus if the archived logs are automatically logged to the 10g server.

Note. I have not installed the full DataGuard config here, and the 10g database is not a secondary server.

Thanks for any suggestions.

Edit

Please note that I can login to the 10g server from the 9i server via sqlplus, so the connection is not a problem

Edit 2

After a lot of time to resolve, I finally decided that such a mechanism did not work and that a method to migrate archived logs using non-Oracle 9i to 10g (eg Rsync) should be used.

+1


a source to share


1 answer


Are your patched databases up to date?

Also, generally, do your connections usually take a while to authenticate? After V10.1, by default SQLNET.INBOUND_CONNECT_TIMEOUT is set to 60 seconds. Prior to this version, it is undefined by default.



Ref Metalink 345197.1: Connections that are used to run in Oracle 10.1 are now broken with ORA-3113, ORA-3106, or ORA-3136 in 10.2

0


a source







All Articles