Export from 8.1.7.4 and Import to 8.0.5

[Adrian Sobers2]

Here is the situation. We need to do some testing for part of our application that was rewritten. We will test on INLAND3 (running 8.0.5 database engine) but will need the information from inland8 (running 8.1.7.4 database engine).

Follow and let me know if I am on the right track. We will need to backup the schema on INLAND3. Then execute the DROP USER ABC CASCADE statement for that user to get rid of the schema, good.

Now the question is, how do I use the 8.0.5 export utility (do I have to do it across Net8?) to export the 8.1.7.4 ABC schema? If so, how do I go about this?

Urgent help required, thanks in advance.

[Patti Johnson · Accepted solution]

Take a look at Metalink article 132904.1 it will give you more details.
Basically you export from 8i using the 8.0 export utility, then import into 8.0 with the 8.0 import. As long as sqlnet is configured between your servers you should be able to run the following from your 8.0 server - using the 8.0 ORACLE_HOME

exp user/passwd@8i_database

[Yogeeraj_1]

hi,

this should not be a problem as long as you are using the 8.0.5 EXP/IMP to export/import the 8.1.7.4 database objects and you have the appropriate tns entry in your tnsnames.ora.

If both the databases are on the same server, you may consider using SQLCOPY.

regards
Yogeeraj

[Adrian Sobers2]

I see two export utilities under:

$ORACLE_HOME/bin

They are, exp and expO

When I run both with help=Y option, they both say the utility version is 8.1.7.4. Where is the 8.0 export utility and how do I use it to export from 8i?

I need detailed help, thanks.

[Jean-Luc Oudart]

"exp" is current version whereas "exp0" is previous version (before patch installation)

This is typical if you went from oracl8i 8.1.7.0 to 8.1.7.4

Youc an also check in $ORACLE_HOME/bin you probably have oracle and oracle0. Checj timestamp for these binary pgms.

Regards
Jean-Luc

[Adrian Sobers2]

Yes we did in fact go from 8.1.7.0 to 8.1.7.4 so I guess that explains it.

The timestamps are:

-rwxr-x--x 1 oracle dba 1286144 Sep 23 18:34 exp
-rwxr-x--x 1 oracle dba 1286144 Sep 1 19:28 expO

But this still does not help me with the 8.0.5 export utility? How do I use that on this 8.1.7.4 machine?

[Jean-Luc Oudart]

Patti gave you the answers

1) use the export of the lower version
that is exp 8.0.5

2) use import of the target database
that is again imp 8.0.5

3) setup your tnsname entry on the target server and test SQLNET connect say with sqlplus

then run export over SQLNET

Regards
Jean-Luc

[Hein van den Heuvel]

Adrian,

I think Yogeeraj is suggestion to simply use EXP as client with a 8.0 Oracle home, possibly on a different box, and have it connect "@" through TNSnames to the 8.1.7 DB.

Also... had you already tried an export under 8.1.7 and import 8.0? Did it complain bitterly or just wine a little :-).

Hein.

[Adrian Sobers2]

So I have to log onto 8.0.5 server and use export from there over SQLNET to connect to 8.1.7.4 database via a database link right?

[Patti Johnson]

That is correct.
As long as your 8i database is accessable from you 8.0 server it will work. If sqlplus works - exp will work.

[Adrian Sobers2]

ok thanks

[Adrian Sobers2]

I was running the export by putting an entry in my tnsnames.ora. I strarted the export but I got an error about end of oracle communication channel. I tried to start the export again between the servers now I get the error, no listener. I've checked both listeners and they are running. Do you have any suggestions on what else I should look at?

[Patti Johnson]

Verify your sqlnet configuration.
From the 8i server - tnsping the service name of your 8i database. Take note of the port and host name. Then run the tnsping on the 8.0 server. Make sure these are the same and the 8.0 server can resolve the service name for the 8i database.
No Listener often means that the tnsnames.ora entry is not correct - if the port or host name are different it will fail.
Did the export start and then fail with ora-3113? Were you able to export any data?
Also look in the udump directory for any trace files that were created at the time of the export on the 8i database.

[Yogeeraj_1]

hi,

can you post the switches that you are using for your export?

are you using DIRECT=Y?

is the network connection between the two servers reliable?

regards
Yogeeraj

[Adrian Sobers2]

Patti,

From the old server I can tnsping the local database on that server as well as the remote database (production server)

From the production server I can tnsping the local database on that server but not the remote database (test server)

I'm sure the tnsnames.ora files are correct, help!

[Jean-Luc Oudart]

Hi

could you check entries in the sqlnet.ora file ?

Regards
Jean-Luc

[Adrian Sobers2]

attached are two text files with output from the netstat -rn commands. I think it might be a routing (networking) issue. Does anyone know how I can/should modify my routing tables so that the servers can see each other? Thanks...

attachement is route.zip which contains

- old.txt > routing table for old server

- new.txt > routing table for new server

[Jean-Luc Oudart]

Can you just ping the server or is this just tnsping the issue ?

Regards
Jean-Luc

[Adrian Sobers2]

I cannot ping or tnsping the oldserver from the newserver.

I can ping and tnsping the newserver from the oldserver.

[Jean-Luc Oudart]

try traceroute

should be in /usr/contrib/bin

what output are you getting ?

Regards
Jean-Luc

[Patti Johnson]

You said "From the production server I can tnsping the local database on that server but not the remote database (test server)."

If the tnsnames.ora entry is the same for the test database on both servers - then it sounds like the production server can not resolve the name of the test server. Do you have the host= set to the ip address of the server or the hostname. If you are using the hostname and you can not do a ping of the test host from the production server that could be your problem.
Try changing the host entry to the ip address of the test server. Also verify the environment variable TNS_ADMIN, if set, points to the correct location of the tnsnames.ora. If it is not set the default is $ORACLE_HOME/network/admin

If this does not work please post the results of these commands from your production server
1. tnsping
2. echo $TNS_ADMIN
3. and the tnsnames.ora entry from the production server for the test instance.
Also from the test server
4. tnsping

Patti

[Adrian Sobers2]

Patti,

From Production Server:

1) oracle:INLAND8>tnsping TESTDB

TNS Ping Utility for HPUX: Version 8.1.7.4.0 - Production on 23-NOV-2004 14:25:04

(c) Copyright 1997 Oracle Corporation. All rights reserved.

Attempting to contact (ADDRESS=(PROTOCOL=TCP)(HOST=INLAND3)(PORT=1521))
TNS-12535: TNS:operation timed out
oracle:INLAND8>


2) oracle:INLAND8>echo $TNS_ADMIN
sh: TNS_ADMIN: Parameter not set.


3) TESTDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = INLAND3)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = IRDS)
)
)


From Test Server

1) TESTDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = INLAND3)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = IRDS)
)
)

[Adrian Sobers2]

Patti,

Ooops, from Test Server should read:

oracle:INLAND3>tnsping IRDS

TNS Ping Utility for HPUX: Version 8.0.5.0.0 - Production on 23-NOV-04 13:28:24

(c) Copyright 1997 Oracle Corporation. All rights reserved.

Attempting to contact (ADDRESS=(PROTOCOL=TCP)(Host=INLAND3)(Port=1521))
OK (80 msec)
oracle:INLAND3>

[Patti Johnson]

tnsnames.ora looks correct.
From production can you
ping INLAND3
Does it work? How long does it take.
If you can ping the test server from production, but the delay is long then check the listener.ora file for the connection_timeout parameter. If this value is set low increasing it or setting a value of 0 will make the wait indefinite.
If the problem is a slow network this may help you around it until you can resolve the newwork issue.
Metalink note 119706.1 has more information on the TNS-12535 error.
If you cannot ping the hostname try the ip address.

[Adrian Sobers2]

Patti,

I cannot ping test server from production server.

I have already set the CONNECT_TIMEOUT value to 0 in my listener.ora but it still does not work

I think it has to do with routing information. What about you?