Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Upgrade to 9i from 8i(8.1.6, 8.1.7)
- Thread starter jpernia
- Start date
SantaMufasa
Technical User
JPernia,
What specific issues are you concerned about relating to "upgrade application from 8i to 9i"? Are you a DBA responsible for reproducing schema objects from 8i to 9i? Or are you an applications developer wondering about version-migration implications for software?
If you are just concerned about your schemas' migrations, then among other options are simply exporting from 8i, then importing into 9i. Oracle is generally very good about ensuring rearward compatibility for applications.
Dave
Sandy, Utah, USA @ 21:53 GMT, 14:53 Mountain Time
[Let's see what a "World Community" Tek-Tips is by adding
location and time-stamp our signatures...¿Sí/No?]
What specific issues are you concerned about relating to "upgrade application from 8i to 9i"? Are you a DBA responsible for reproducing schema objects from 8i to 9i? Or are you an applications developer wondering about version-migration implications for software?
If you are just concerned about your schemas' migrations, then among other options are simply exporting from 8i, then importing into 9i. Oracle is generally very good about ensuring rearward compatibility for applications.
Dave
Sandy, Utah, USA @ 21:53 GMT, 14:53 Mountain Time
[Let's see what a "World Community" Tek-Tips is by adding
location and time-stamp our signatures...¿Sí/No?]
SantaMufasa
Technical User
Dash,
If you are asking strictly about migration, then I simply export schemas from the old database, and import the dump files into the new database.
As far as the tablespaces on the new database are concerned, I create them to AUTOEXTEND and to manage the extents locally (instead of the default of "dictionary managed extents"):
Let us know if this information is what you wanted.
![[santa]](/data/assets/smilies/santa.gif "[santa] [santa]")
Mufasa
(aka Dave of Sandy, Utah, USA)
@ 17:09 (31Jan05) UTC (aka "GMT" and "Zulu"),
@ 10:09 (31Jan05) Mountain Time
Click here to Donate to Tsunami Relief. 100% of your contributions here go to the victims...0% to administration.
They were "The First-Responder" to the disaster, with relief deliveries arriving before Red Cross and U.S. aid.
If you are asking strictly about migration, then I simply export schemas from the old database, and import the dump files into the new database.
As far as the tablespaces on the new database are concerned, I create them to AUTOEXTEND and to manage the extents locally (instead of the default of "dictionary managed extents"):
Code:
CREATE TABLESPACE <ts_name> DATAFILE '<path and files>' SIZE 10M
AUTOEXTEND ON NEXT 10M MAXSIZE 2000M
EXTENT MANAGEMENT LOCAL AUTOALLOCATE;Let us know if this information is what you wanted.
Mufasa(aka Dave of Sandy, Utah, USA)
@ 17:09 (31Jan05) UTC (aka "GMT" and "Zulu"),
@ 10:09 (31Jan05) Mountain Time
Click here to Donate to Tsunami Relief. 100% of your contributions here go to the victims...0% to administration.
They were "The First-Responder" to the disaster, with relief deliveries arriving before Red Cross and U.S. aid.
- Status
Similar threads
