-
Upgrading 9.2.0.4 to 10.2.0.3
Hi All,
I am facing some real problem in upgrading my 9204 database tp 10.2.0.3.
The scenario is : I have my production db running on 9.2.0.6 and i have been asked to clone the db using RMAN to a new host and upgrade it to 10.2.0.3. I have tried but the new host has got 9.2.0.4 binaries. Management does not allow me to patch the binariy at this point.
So alternatively what i have done is
1) I have created one 10g database in the new host.
2) Taken a full database export of source prod db(9206)
3) Trying to import but here i am facing one problem.
/home/oracle/wrkspc>$ imp parfile=/home/oracle/wrkspc/importpar
Import: Release 10.2.0.3.0 - Production on Mon Jun 9 17:01:28 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: sys/sys as sysdba
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V09.02.00 via conventional path
Warning: the objects were exported by SYSTEM, not by you
import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses US7ASCII character set (possible charset conversion)
export server uses UTF8 NCHAR character set (possible ncharset conversion)
IMP-00040: FILESIZE does not match the value used for export: 0
IMP-00000: Import terminated unsuccessfully
My Parfile is:
file=/stage/bhakti/fulldb.dmp
filesize=4096MB
log=/stage/bhakti/fullbobd2_imp.log
fromUser=('OUTLN','READONLY','DBSNMP','TRACESVR','TRANS','BACKUP_ADMIN','BOMANAGER_COPY','BOMANAGER' ,'STSC','TOAD','FOCUSX','PLEX','DBABOBP')
toUser=('OUTLN','READONLY','DBSNMP','TRACESVR','TRANS','BACKUP_ADMIN','BOMANAGER_COPY','BOMANAGER',' STSC','TOAD','FOCUSX','PLEX','DBABOBP')
indexes=Y
constraints=Y
indexfile=/stage/bhakti/create_index.sql
This is a critical issue for me now. Can anyone has ever faced this sort of issue help me in this? I will really appreciate the help. My advance regards and thanks.
Regards,
Bhakti
-
take the filesize parameter out
also dont import outln or dbsmmp
might be wise to find a dba to help you out as well
-
Also, you may have characterset conversion issues, set your NLS_LANG environment variable compatible for both export and import.
import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses US7ASCII character set (possible charset conversion)
export server uses UTF8 NCHAR character set (possible ncharset conversion)
"The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|