Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: HELP - Oracle Schema Import problem

Re: HELP - Oracle Schema Import problem

From: Steve Howard <stevedhoward_at_gmail.com>
Date: Fri, 27 Jul 2007 16:37:22 -0000
Message-ID: <1185554242.051130.256960@e16g2000pri.googlegroups.com>


On Jul 27, 9:57 am, Johne_uk <edg..._at_tiscali.co.uk> wrote:
> On 27 Jul, 08:15, DA Morgan <damor..._at_psoug.org> wrote:
>
>
>
> > Johne_uk wrote:
> > > Hi,
>
> > > I have 2 identical Solaris servers (freshly installed v490 - dual CPU
> > > 8GB RAM). The OS (Solaris 10) were both installed to an agreed spec by
> > > 2 diff consultants (all disk mirrored and striped).
>
> > > I created identical 9208 DB instances on both servers (using identical
> > > scripts with only diff being SID names).
>
> > > I then imported a schema dump (from another db server) on server 1.
> > > This took about 3 hrs.
>
> > > However, despite an idential setup the second server took up to 3
> > > times longer than the first to import the same export dump (except
> > > this dump was sourced from a Linux db whereas the first was from
> > > another solaris instance)
>
> > > Im not an expert DBA and in the morning need to start troublesheeting
> > > this performance bottleneck. Could the linux sourced export be the
> > > reason for it being being slower on server 2. No logs etc were
> > > generated whilst importing.
>
> > > If I rule out using a linux derived export dump AND verify there are
> > > no i/o issues with the Solaris server how would you suggest I proceed
> > > to identify the bottelneck on server 2.
>
> > > Apologies for the simplistic explanation (there are reasons for using
> > > the Linux export) but I'd appreciate any pointers on how to start
> > > solving this as I'm currently stuck in a hotel room and cant get my
> > > hands on the system until the morning.
>
> > > Thanks in advance
> > > John
>
> > Check endian values.
> > --
>
> Hi,
>
> I've since repeated importing using the same export dump derived from
> a solaris instance (still very slow in fact still running). My unix
> admin says that endian values should not be an issue as all Solaris
> boxes uses the same.
>
> regards

You may try sql tracing for each, as that will at least show you how much cpu each uses, and what waits it generates. You can then compare the two traces to see what drops out.

HTH, Steve Received on Fri Jul 27 2007 - 11:37:22 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US