Java Mailing List Archive

http://www.dba.5341.com/

Home » Home (12/2007) » oracle l »

RE: ORA-04031

Powell, Mark D

2004-07-14


>> It is currently set at 4400 - how much lower would I need to go???? <<

From experience I think the answer depends on how large the requests that
are failing happen to be. If you routinely get errors trying to find small
chunks then your shared pool then it is badly fragmented and you should look
at large pl/sql and cursors that have reloads. Pinning one or two large
objects can have a very beneficial effect when you suffer from 04031 errors.
If the errors normally occur on chunks larger than 4400 then you need more
reserved pool and/or again to pin large pl/sql packages.

We have worked a half-dozen 04031 related iTARs that support acknowledge
trace to Oracle memory management bugs . Pinning packages, reducing the
size of objects considered large, and increasing the space reserved for
large objects is the best you can do if your application follows the code
paths that hit these bugs.

Then you have poor application design in relation to how Oracle works,
namely, failure to use reusage SQL. The cursor_sharing = similar might be
an option. Force produced unacceptable side effects for us on 8.1.7+ so we
have not tried it on 9.2. If you have SQL reuse issues then 9+ option might
be available to you.

IMHO -- Mark D Powell --


-----Original Message-----
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)
Paula_Stankus@(protected)
Sent: Wednesday, July 14, 2004 10:28 AM
To: oracle-l@(protected)
Subject: RE: ORA-04031



Platform:

Oracle 9.2.0.5
Solaris 2.9
ArcSDE 8.3

I am running a DSS - geodatabase with 30 concurrent users. I am getting =
ORA-04031 errors.

I have verified that last_failure_size > shared_pool_reserved_min_alloc. =
According to Note: 146599.1 it states that I should increase the =
hidden parameter "_shared_pool_reserved_min_alloc" to lower the number =
of objects being cached. =20

It is currently set at 4400 - how much lower would I need to go????

It also states I should consider increasing the =
shared_pool_reserved_size and shared_pool_size but these parameters seem =
adequate to me:

40M for shared_pool_size
4M for shared_pool_reserved_size

I have gone through NOTE: 1012046.6 "Calculating Shared Pool size" and =
based on that my shared_pool_size is more than adequate.

How can I more specifically size the shared pool, shared reserved pool =
as I know that if I size too large then I can start incurring overhead.


-----Original Message-----
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)
Sent: Wednesday, July 14, 2004 8:41 AM
To: oracle-l@(protected)
Subject: RE: rman nocatalog - point in time recovery


Sometimes I find it is just expedient to use sqlplus to open the =
database.
Sometimes, there is no other way. Rman is still a work in progress and =
it
has been seriously improved since the 8.0.5... days but when you are =
doing
incomplete recovery and it seems to want a redo log instead of an =
archived
log, then I have found, sqlplus recover the way you did it is the =
easiest
way. Even Oracle support has told me this.

HTH,
Ruth

-----Original Message-----
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)
Sent: Tuesday, July 13, 2004 4:44 PM
To: oracle-l@(protected)
Subject: RE: rman nocatalog - point in time recovery


This may not be the cleanest solution, but it worked:

rman
run {
set until logseq=3D1235 thread =3D1;
allocate channel ch1 type disk;
allocate channel ch2 type disk;
allocate channel ch3 type disk;
restore database;
}
exit;

sqlplus internal
sqlplus> recover database until cancel using backup controlfile;
sqlplus> alter database open resetlogs;
sqlplus> exit;

Is there a better way to do this?

thanks,
Peter Schauss

-----Original Message-----
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)
Sent: Tuesday, July 13, 2004 4:12 PM
To: Oracle-L (E-mail)
Subject: rman nocatalog - point in time recovery


Enviroment: Oracle 8.1.7.4 / AIX 5.2

Scenario:

- I have an rman backup (nocatalog) and a separate control file backup
done at 11:00 pm.

- The database is in archivelog mode.

- At 11:00 am the next morning I have a failure which causes
loss of the entire database.

- Archivelogs through 10:45 are intact. The last archive log is =
sequence
1234.

- I have the backup files created from the 11:00 pm rman backup in the
directory
to which they were backed up.

- I want to restore the database to the state it was in at 10:45 am by
applying
the redo logs through number 1234.

I restore my control files by copying them to the appropriate =
directories on
the disk (e.g. /ora1/oradata/sid/control01.ctl ... /ora2/... =
/ora3/...).

I run the following commands in rman

run {
set until logseq=3D1234 thread=3D1;
allocate channel ch1 type disk;
allocate channel ch2 type disk;
allocate channel ch3 type disk;
restore database;
recover database;
alter database open resetlogs;
}

Oracle says:

RMAN-03002: failure during compilation of command
RMAN-03013: command type: set
RMAN-06003: ORACLE error from target database: RMAN-20206: log sequence =
not
found in the recovery catalog

What am I missing here?

Thanks,
Peter Schauss
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------


BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 4586007) is spam:
Spam:     =
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Ds&i=3D4586007&m=3Ddd09e=
d4dec9a
Not spam:   =
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Dn&i=3D4586007&m=3Ddd09e=
d4dec9a
Forget vote: =
https://dohsmsi01.doh.state.fl.us/canit/b.php?c=3Df&i=3D4586007&m=3Ddd09e=
d4dec9a
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
©2008 dba.5341.com - Jax Systems, LLC, U.S.A.