Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
General
cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle 8.0.5 export -> 8.1.6 import

Mike Taylor_3
Occasional Advisor

Oracle 8.0.5 export -> 8.1.6 import

I'm trying to export from a system running Oracle 8.0.5 to import onto a system running Oracle 8.1.6. These are the export/import commands that I used:

exp system/manager full=Y file='/oracle/qts1.exp' log='/oracle/qts1.exp.log'

imp system/manager full=y commit=y ignore=y constraints=n feedback=10 file='/oracle/qts1.exp' log='/oracle/qts1.imp.log'

But I get loads and loads of errors/warnings in the import log file:

Connected to: Oracle8i Enterprise Edition Release 8.1.6.0.0, 64 bit - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production

Export file created by EXPORT:V08.00.05 via conventional path
import done in US7ASCII character set and US7ASCII NCHAR character set
IMP-00017: following statement failed with ORACLE error 2221:
"CREATE ROLLBACK SEGMENT SYSROL STORAGE (INITIAL 106496 NEXT 122880 MINEXTEN"
"TS 2 MAXEXTENTS 2147483645) TABLESPACE "SYSTEM""
IMP-00003: ORACLE error 2221 encountered
ORA-02221: invalid MAXEXTENTS storage option value
IMP-00017: following statement failed with ORACLE error 2221:
"CREATE PUBLIC ROLLBACK SEGMENT RB0 STORAGE (INITIAL 57344 NEXT 57344 MINEXT"
"ENTS 2 MAXEXTENTS 2147483645) TABLESPACE "RBS""
IMP-00003: ORACLE error 2221 encountered
ORA-02221: invalid MAXEXTENTS storage option value
IMP-00017: following statement failed with ORACLE error 2221:
"CREATE PUBLIC ROLLBACK SEGMENT RB1 STORAGE (INITIAL 57344 NEXT 57344 MINEXT"
"ENTS 2 MAXEXTENTS 2147483645) TABLESPACE "RBS""

Any ideas? Many thanks in advance for any help...

Happy holidays,
Mike Taylor
4 REPLIES
John Wimmer
Occasional Visitor

Re: Oracle 8.0.5 export -> 8.1.6 import

What is your db_block_size ?
Mike Taylor_3
Occasional Advisor

Re: Oracle 8.0.5 export -> 8.1.6 import

db_block_size is 8192.

I've gotten a few emails from an Oracle Users Group distribution I am on. They would indicate that I should use the 8.1.6 export utility when I do the export from the 8.0.5 system. I still need to verify that.
CHRIS ANORUO
Honored Contributor

Re: Oracle 8.0.5 export -> 8.1.6 import

Mike,

What you are trying is a difficult thing. The forms for 8.1.6 are different from those of 8.0.5. You cann't do a direct import/export as you have been doing. Get in touch with your DBA and oracle guys to help you sort things out

Happy New Year!
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
John Dixon_1
Advisor

Re: Oracle 8.0.5 export -> 8.1.6 import

Hi Mike,
You might find this article on the oracle maetalink website of interest:
Note:61949.1 - Overview of Import and Export.

To summerise, the procedures to import/export between different versions are as follows:


Source database is newer than the target database:

1. Run the older "CATEXP.SQL" script on the database to be exported.
2. Use the older EXP utility to create the dump file.
3. Use the older IMP utility to import to the target database.
4. Run the newer "CATEXP.SQL" script on the exported database to
restore its export views to the original (correct) version.


It is also possible to have a situation where the source database is older
than the target, but you do not have access to the original Export utility. If
you must use an export executable from one version against an older Oracle
database version, it may be necessary to change the export views.

Source database is older than the target database:

1. Run the newer "CATEXP.SQL" script on the database to be exported.
2. Use the newer EXP utility to create the dump file.
3. Use the newer IMP utility to import to the target database.
4. Run the older "CATEXP.SQL" on the exported database to restore its
export views to the original (correct) version.

cheers,
John