- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: upgrade from oracle 8.1.7 to oracle 9i
Operating System - HP-UX
1753797
Members
7645
Online
108804
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2006 01:07 PM
05-16-2006 01:07 PM
Re: upgrade from oracle 8.1.7 to oracle 9i
Hi Dartan,
From 8.1.7.4 to 9.2.0.7 ---- Full database export with the 8.1.7.4 export utility, and full database import with the 9.2.0.7 import utility is a supported migration method.
Refer to Note:227332.1 in metalink for details of "NLS considerations in Import/Export"
As Brian mentioned, upgrade using export/import will take a long time, and will depend on how much database down time can you afford.
You could speed-up the export import process, by exporting schema by schema and scheduling more than one import process simultaneously. This will require you to pre-create the tablespaces, users and roles. You can select from dba_users, dba_roles, dba_tablespaces, v$datafile views for the tablespaces, users and roles details. This will actually give you a change to create them with proper sizes with the current which suites the current data volume + future data growth forcaste. Make sure to assign the default tablespaces to the users and grant quotas on the tablespaces to the users.
Then export from the source database using exp username/password owner= file=file_name.........etc
Then import using imp user/password fromuser= touser= ignore=y commit=y file=file_name......etc,
This will create the tables and import the data, and grant privileges to the users / roles.
To further speed-up the import, you can say indexes=n in the import and then re-create the indexes later on.
If you prefer to pre-create the tables before the data import, you can export using the rows=n and this will export the table structure and import this dump file will create the tables in the target database. Then export the data and import.
You can also export few tables and import those tables. So You can schedule several imports simulatnously for different sets of tables.
IA
From 8.1.7.4 to 9.2.0.7 ---- Full database export with the 8.1.7.4 export utility, and full database import with the 9.2.0.7 import utility is a supported migration method.
Refer to Note:227332.1 in metalink for details of "NLS considerations in Import/Export"
As Brian mentioned, upgrade using export/import will take a long time, and will depend on how much database down time can you afford.
You could speed-up the export import process, by exporting schema by schema and scheduling more than one import process simultaneously. This will require you to pre-create the tablespaces, users and roles. You can select from dba_users, dba_roles, dba_tablespaces, v$datafile views for the tablespaces, users and roles details. This will actually give you a change to create them with proper sizes with the current which suites the current data volume + future data growth forcaste. Make sure to assign the default tablespaces to the users and grant quotas on the tablespaces to the users.
Then export from the source database using exp username/password owner=
Then import using imp user/password fromuser=
This will create the tables and import the data, and grant privileges to the users / roles.
To further speed-up the import, you can say indexes=n in the import and then re-create the indexes later on.
If you prefer to pre-create the tables before the data import, you can export using the rows=n and this will export the table structure and import this dump file will create the tables in the target database. Then export the data and import.
You can also export few tables and import those tables. So You can schedule several imports simulatnously for different sets of tables.
IA
Never give up, Keep Trying
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP