tablespace import hangs [message #265974] |
Sat, 08 September 2007 04:57 |
orcl dba
Messages: 68 Registered: August 2005
|
Member |
|
|
Hi all,
I am migrating a 10.2.0.2 database(its an SAP database) from Solaris to Suse Linux SLES10.1. We are migrating the database using brtools as specified by SAP. The following are the steps:
1.Create the the database with the system,sysaux,temp and undo tablespaces.
2.Put the tablespaces in read-only mode on the source system and convert the datafiles using the rman "convert datafile from platform" command.
3.Perform the global import using the following options:
exp system/manager full=y,rows=n,indexes=n,constraints=n,statistics=none,ignore=y,buffer=10485760,file=exp.dmp
4.Once the full import was done on the target, I started the tablespace import using the command
imp \'sys/change_on_install as sysdba\' parfile=imp.par
Follwing are the contents of the parfile
transport_tablespace=y
statistics=none
buffer=10485760
tablespaces=("ts1","ts2","ts3")
datafiles=('/u01/oradata/db1/data1','/u01/oradata/db1/data2',......)
The tablespace import just hangs there forever not doing anything. Any inputs as to what might be wrong?
|
|
|
|
|
|
|
Re: tablespace import hangs [message #265990 is a reply to message #265988] |
Sat, 08 September 2007 09:33 |
orcl dba
Messages: 68 Registered: August 2005
|
Member |
|
|
My alert log file reports the following error: ORA-07445: exception encountered: core dump [__GI_raise()+53] [SIGIOT] [unknown code] [0x3EA00006300] [] []
After going through metalink, I found that its a bug encountered while doing tablespace imp/exp.The doc is 6057615
Can someone throw light on how to go about this issue?
|
|
|
Re: tablespace import hangs [message #265992 is a reply to message #265990] |
Sat, 08 September 2007 10:21 |
|
Michel Cadot
Messages: 68728 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
Did you do what is indicated at the bottom of the Metalink note?
If so, then raise a SR.
Noone can told how to workaround an Oracle bug but Oracle itself.
Regards
Michel
|
|
|