Sounds like an I/O issue at the OS level.
Did someone drop the disk while it was out ?
Obviously, something changed.
Good luck with that.
Andre
-----Original Message-----
From: Brian Mays
[mailto:oracledba-ezmlmshield-x78382188.[Email address protected]
Sent: Wednesday, January 31, 2007 3:43 PM
To: LazyDBA Discussion
Subject: Database Sluggish after remount of storage device.
Hi Guys:
I am having a strange problem,and was hoping someone could point me in the
right direction:
Our SA's attempted to move from an old storage device to a new EMC. All
Oracle instances, listeners, etc., were down at the time. They couldn't get
the server to recognize the new storage device when they were done, so they
reconnected the old storage. The oracle binaries are on the server; all
data files are on the storage device.
I started the instances, but instead of taking 30 seconds or so to start
up, they took 5-10 minutes. Same thing when I brought them back down.
Now they are up, but performance is horrible. The SA's swear nothing has
changed; they put everything back the way it was before they tried to switch
over.
I see the following types of errors in the trace files:
*** SESSION ID:(102.305) 2007-01-31 12:27:08.593
*** 2007-01-31 12:27:08.593
ORA-12012: error on auto execute of job 4367
ORA-20000: SQLERRM: ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 449
ORA-29283: invalid file operation SQLCODE: -29283
ORA-06512: at "CCR.MGMT_DB_LL_METRICS", line 1009
ORA-06512: at line 1
During Startup, these messages appeared in the alert log:
FAST_START_MTTR_TARGET 300 is out of the valid MTTR range, use 384
instead.
Wed Jan 31 09:06:11 2007
Thread 1 opened at log sequence 32
Current log# 1 seq# 32 mem# 0: /PRODdg/u01/oradata/QA/redo1A.log
Successful open of redo thread 1 Wed Jan 31 09:06:11 2007
LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
Wed Jan 31 09:06:19 2007
SMON: enabling cache recovery
Wed Jan 31 09:06:22 2007
FAST_START_MTTR_TARGET 300 is out of the valid MTTR range, use 370 instead.
Wed Jan 31 09:10:09 2007
Successfully onlined Undo Tablespace 1.
Wed Jan 31 09:10:09 2007
SMON: enabling tx recovery
Wed Jan 31 09:10:24 2007
Database Characterset is AL32UTF8
Wed Jan 31 09:12:35 2007
replication_dependency_tracking turned off (no async multimaster replication
found) Wed Jan 31 09:13:05 2007
Completed: ALTER DATABASE OPEN
Wed Jan 31 09:14:59 2007
FAST_START_MTTR_TARGET 300 is out of the valid MTTR range, use 486 instead.
Wed Jan 31 09:15:06 2007
Errors in file /oracle/product/admin/QA/bdump/qa_j000_2238.trc:
ORA-12012: error on auto execute of job 4367
ORA-20000: SQLERRM: ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 449
ORA-29283: invalid file operation SQLCODE: -29283
ORA-06512: at "CCR.MGMT_DB_LL_METRICS", line 1009
ORA-06512: at line 1
Wed Jan 31 09:15:31 2007
Errors in file /oracle/product/admin/QA/bdump/qa_j000_2238.trc:
ORA-12012: error on auto execute of job 4368
ORA-20000: SQLERRM: ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 449
ORA-29283: invalid file operation SQLCODE: -29283
ORA-06512: at "CCR.MGMT_DB_LL_METRICS", line 1009
ORA-06512: at line 1
Any idea what could be wrong?
Thanks in advance,
Brian
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a dba
job: http://jobs.lazydba.com To Subscribe : http://www.LazyDBA.com To
unsubscribe: http://www.lazydba.com/unsubscribe.html
Oracle LazyDBA home page