Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: export error for duh Gurus

RE: export error for duh Gurus

From: Spears, Brian <>
Date: Tue, 13 Dec 2005 17:13:51 -0500
Message-ID: <>

It's highly sensitive production db...  

I cannot implement new datapump right now..It's just the nature of the environment here. Yes the conventional exports with direct=y ... If it wakes me up again, I will try the direct=N  

Note: a rerun of the export usually is successful! So I am thinking some resource contention or something.  


From: [] On Behalf Of Powell, Mark D
Sent: Tuesday, December 13, 2005 4:41 PM To: oracle-l
Subject: RE: export error for duh Gurus

Brian, do you get the error on conventional exports? And to be clear I take it you are using the traditional exp utility and not the new expdp utility that is the preferred utility with 10g to use for exports.  

[] On Behalf Of Spears, Brian

	Sent: Tuesday, December 13, 2005 4:23 PM
	To: oracle-l
	Subject: export error for duh Gurus
	Has anyone got ideas or run across this intermittent export error?
	Randomly getting this error in the export full.
	Metalink does not show anything related at our version so a tar
	. . exporting table                  CARTON_STATUS
	EXP-00008: ORACLE error 8103 encountered
	ORA-08103: object no longer exists
	. . exporting table           CLASS_IMPLEMENTATION         33 rows

        Brian Spears         

[] On Behalf Of Yongping Yao

	Sent: Tuesday, December 13, 2005 1:22 AM
	Cc: oracle-l
	Subject: Re: pga_aggregate_target
	I think Expert Oracle: Database Arichitecture Chapter 3 (or 4 I
don't have it in hand) will help you.                           

        On 12/13/05, The Human Fly <> wrote:

                Hello List,                 

                I was little confused about the settings of pga_aggregate_target

                parameter. I was in a assumption that when we set this parameter to a

                certain value, the usage of pga wont go beond this value. I have set

                pga as 3gb to one of my business critical database. Recently, I have

                found that max pga allocation was 4+ Gb. My boss askmed me, why the

                hell it takes more than what we have defined. I explained him saying

                that oracle might taken it from the OS to finish the necessary

                request. His immediately counter question was, then what is the use of

                setting pga_aggregate_target parameter? When oracle allocates and

		de-allocated the memory (pga) as per requirements.
		Is it expected behaviour that oracle takes sometime more
that the 
		value defined for pga? If so, what is the benift of setting
value for
		Thanks for your time.
		Best Regards,
		Syed Jaffar Hussain
		OCP 8i & 9i DBA,
		Banque Saudi Fransi,
		Saudi Arabia 
		"Winners don't do different things. They do things

	Yao Yongping
	Learning Oracle, UNIX/Linux...
	Love Reading, Classical Music, Philosophy, Economics etc.

Received on Tue Dec 13 2005 - 16:14:05 CST

Original text of this message