.ora-code.com

Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
Q: Filesystem choice for log_archive_dest

Q: Filesystem choice for log_archive_dest

2005-06-23       - By Radoulov, Dimitre
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

It's a very busy critical production system. When we saw the "cannot
allocate new log" messages, we increased the redo logs from 8x256Mb to
16x256Mb and the messages disappeared. But our analysis was: the only thing
changed was the direct IO activation, we've never had this problems before,
the load appeared to be the same(it's hard to measure, it's a mobile phone
company with all those SMS services). So now I'm trying to find the
technical explanation of why one could need a direct IO filesystem for the
archived log files.
And there is another thing, that made me post the question: yesterday we had
to run a report query from sqlplus and guess what: the first person ran the
report spooling under the OFA's filesystem, the result was ORA-01555 (See ORA-01555.ora-code.com) after
3h! And the second, me, ran the same query(same execution plan!) spooling on
the host's local filesystem - successfully in 15min ...
So, we ran another test today with another query, the results: spooling on
the direct IO filesystem: 30min, on the local filesystem: 49s.



Thanks
Dimitre


-- -- Original Message -- --
From: "Kevin Closson" <kevinc@(protected)>
To: <oracle-l@(protected)>
Sent: Thursday, June 23, 2005 6:21 PM
Subject: RE: Q: Filesystem choice for log_archive_dest


>
> >So I was wondering, could the direct IO be beneficial for the
> log_archive_dest filesystem in some cases?
>
> yep...see my last post. This just needs tuning. how many
> online logs do you have and what size are they?
>
> --
> http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l