Large Core Dumps after DB Backup Control File

Hi All,
Server Specs (it is the test server having no functional modules):
Windows 2003 64bit
Oracle 10.2.0.4 (Patched from 10.2.0.2)
Netweaver 2004s
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
ORA-00279: change 21375038 generated at 09/21/2007 20:12:47 needed for thread 1
ORA-00289: suggestion : /export/pspp/oracle/dbs/xxx_example_xxx.dbf
ORA-00280: change 21375038 for thread 1 is in sequence #4
Specify log: {=suggested | filename | AUTO | CANCEL}
/OraRedo/RedoLogFiles/xxx_example_xxx.dbf
Log applied.
Media recovery complete.
I was facing Control file inconsistence issues against 2 partitions. Issue was resolved by using above commands and Netweaver started successfully. Im now facing another problem, im getting huge tracefiles in SAPTRACE\BACKGROUND folder since its recovery. I deleted those tracefiles which were of approx. 86GB.
Current Tracefiles sizes are:
<drive>:\oracle\TST\saptrace\background\tst_m000_5188.trc (7MB) and it is getting double by each generation.
Here are tracefiles of today (old ones deleted by me coz it was consuming a hell of space, e.g: 86GB as mentioned):
tst_m000_5188.trc (7 MB) Latest
tst_j000_5316.trc (4MB)
Here is Initial info from alert_tst.txt file contained in same folder:
Dump file f:\oracle\tst\saptrace\background\alert_tst.log
Thu Sep 02 13:55:34 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 1
CPU                 : 2 - type 8664, 1 Physical Cores
Process Affinity    : 0x0000000000000000
Memory (Avail/Total): Ph:2886M/4019M, Ph+PgF:19295M/20131M
Thu Sep 02 13:55:34 2010
Starting ORACLE instance (normal)
Thu Sep 02 13:55:35 2010
Specified value of sga_max_size is too small, bumping to 666894336
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 80
  sessions                 = 96
  event                    = 10191 trace name context forever, level 1
  sga_max_size             = 666894336
  shared_pool_size         = 318767104
  shared_pool_reserved_size= 31598837
  filesystemio_options     = setall
  control_files            = E:\ORACLE\TST\ORIGLOGA\CNTRL\CNTLRTST.DBF, E:\ORACLE\TST\ORIGLOGB\CNTRL\CNTRLTST.DBF, F:\ORACLE\TST\SAPDATA1\CNTRL\CNTRLTST.DBF
  control_file_record_keep_time= 30
  db_block_size            = 8192
  db_cache_size            = 318767104
  compatible               = 10.2.0
  log_archive_dest         = E:\oracle\TST\oraarch\TSTarch
  log_buffer               = 2061312
  log_checkpoint_interval  = 0
  db_files                 = 254
  log_checkpoints_to_alert = TRUE
  dml_locks                = 4000
  undo_management          = AUTO
  undo_tablespace          = PSAPUNDO
  undo_retention           = 43200
  recyclebin               = off
  remote_os_authent        = TRUE
  remote_login_passwordfile= EXCLUSIVE
  job_queue_processes      = 1
  background_dump_dest     = F:\ORACLE\TST\SAPTRACE\BACKGROUND
  user_dump_dest           = F:\ORACLE\TST\SAPTRACE\USERTRACE
  core_dump_dest           = F:\ORACLE\TST\SAPTRACE\BACKGROUND
  optimizer_features_enable= 10.2.0.1
  sort_area_size           = 2097152
  sort_area_retained_size  = 0
  db_name                  = TST
  open_cursors             = 800
  _optim_peek_user_binds   = FALSE
  pga_aggregate_target     = 421317836
  workarea_size_policy     = AUTO
  statistics_level         = typical
MMAN started with pid=4, OS id=2760
PMON started with pid=2, OS id=2748
DBW0 started with pid=5, OS id=712
LGWR started with pid=6, OS id=604
CKPT started with pid=7, OS id=1088
SMON started with pid=8, OS id=1164
RECO started with pid=9, OS id=2680
CJQ0 started with pid=10, OS id=2972
MMON started with pid=11, OS id=1816
MMNL started with pid=12, OS id=2904
PSP0 started with pid=3, OS id=2692
Please Review,
Thanks in Advance.
Best Regards.

All dispatchers and shared servers shutdown
Mon Jan 10 15:19:45 2011
ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:19:45 2011
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Jan 10 15:19:46 2011
Shutting down archive processes
Archiving is disabled
Mon Jan 10 15:19:51 2011
ARCH shutting down
ARC1: Archival stopped
Mon Jan 10 15:19:56 2011
ARCH shutting down
ARC0: Archival stopped
Mon Jan 10 15:19:57 2011
Thread 1 closed at log sequence 11
Successful close of redo thread 1
Mon Jan 10 15:19:59 2011
Completed: ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:19:59 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Shutting down Data Guard Broker processes
Mon Jan 10 15:20:00 2011
Completed: Data Guard Broker shutdown
Mon Jan 10 15:20:02 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Jan 10 15:21:43 2011
Starting ORACLE instance (normal)
Mon Jan 10 15:21:43 2011
Specified value of sga_max_size is too small, bumping to 645922816
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 80
  sessions                 = 96
  event                    = 10191 trace name context forever, level 1
  sga_max_size             = 645922816
  shared_pool_size         = 318767104
  __java_pool_size         = 4194304
  java_pool_size           = 4194304
  shared_pool_reserved_size= 31598837
  filesystemio_options     = setall
  control_files            = E:\ORACLE\TST\ORIGLOGA\CNTRL\CNTLRTST.DBF, E:\ORACLE\TST\ORIGLOGB\CNTRL\CNTRLTST.DBF, F:\ORACLE\TST\SAPDATA1\CNTRL\CNTRLTST.DBF
  control_file_record_keep_time= 30
  db_block_size            = 8192
  db_cache_size            = 318767104
  compatible               = 10.2.0
  log_archive_dest         = E:\oracle\TST\oraarch\TSTarch
  log_buffer               = 2061312
  log_checkpoint_interval  = 0
  db_files                 = 254
  log_checkpoints_to_alert = TRUE
  dml_locks                = 4000
  undo_management          = AUTO
  undo_tablespace          = PSAPUNDO
  undo_retention           = 43200
  recyclebin               = off
  remote_os_authent        = TRUE
  remote_login_passwordfile= EXCLUSIVE
  dispatchers              = (PROTOCOL=TCP) (SERVICE=TSTXDB)
  job_queue_processes      = 1
  background_dump_dest     = F:\ORACLE\TST\SAPTRACE\BACKGROUND
  user_dump_dest           = F:\ORACLE\TST\SAPTRACE\USERTRACE
  core_dump_dest           = F:\ORACLE\TST\SAPTRACE\BACKGROUND
  optimizer_features_enable= 10.2.0.1
  sort_area_size           = 2097152
  sort_area_retained_size  = 0
  db_name                  = TST
  open_cursors             = 800
  optimpeek_user_binds   = FALSE
  pga_aggregate_target     = 421317836
  workarea_size_policy     = AUTO
  statistics_level         = typical
  dg_broker_start          = TRUE
PMON started with pid=2, OS id=5108
PSP0 started with pid=3, OS id=3884
MMAN started with pid=4, OS id=3212
DBW0 started with pid=5, OS id=4508
LGWR started with pid=6, OS id=4124
CKPT started with pid=7, OS id=3684
SMON started with pid=8, OS id=3284
RECO started with pid=9, OS id=4360
CJQ0 started with pid=10, OS id=2128
MMON started with pid=11, OS id=3976
Mon Jan 10 15:21:43 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=3444
Mon Jan 10 15:21:43 2011
starting up 1 shared server(s) ...
DMON started with pid=15, OS id=4136
Mon Jan 10 15:21:43 2011
ALTER DATABASE   MOUNT
Mon Jan 10 15:21:48 2011
Setting recovery target incarnation to 4
Mon Jan 10 15:21:48 2011
Successful mount of redo thread 1, with mount id 1881221383
Mon Jan 10 15:21:48 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Mon Jan 10 15:21:48 2011
ALTER DATABASE OPEN
Mon Jan 10 15:21:51 2011
Starting Data Guard Broker (DMON)
INSV started with pid=16, OS id=4264
Mon Jan 10 15:21:55 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=18, OS id=4768
Mon Jan 10 15:21:55 2011
ARC0: Archival started
Mon Jan 10 15:21:55 2011
ARC1: Archival started
ARC1 started with pid=19, OS id=5288
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 11
  Current log# 3 seq# 11 mem# 0: E:\ORACLE\TST\ORIGLOGA\LOG_G13M1.DBF
  Current log# 3 seq# 11 mem# 1: E:\ORACLE\TST\MIRRLOGA\LOG_G13M2.DBF
Successful open of redo thread 1
Mon Jan 10 15:21:57 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jan 10 15:21:57 2011
SMON: enabling cache recovery
Mon Jan 10 15:21:57 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Jan 10 15:21:57 2011
ARC1: Becoming the heartbeat ARCH
Mon Jan 10 15:21:58 2011
Incremental checkpoint up to RBA [0xb.16b77.0], current log tail at RBA [0xb.16b77.0]
Mon Jan 10 15:21:59 2011
Successfully onlined Undo Tablespace 1.
Mon Jan 10 15:21:59 2011
SMON: enabling tx recovery
Mon Jan 10 15:21:59 2011
Database Characterset is UTF8
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 2
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=20, OS id=4156
Mon Jan 10 15:22:05 2011
Completed: ALTER DATABASE OPEN
Mon Jan 10 15:52:02 2011
Incremental checkpoint up to RBA [0xb.180ee.0], current log tail at RBA [0xb.1830a.0]
Mon Jan 10 15:52:16 2011
Shutting down instance: further logons disabled
Mon Jan 10 15:52:16 2011
Stopping background process CJQ0
Mon Jan 10 15:52:16 2011
Stopping background process QMNC
Mon Jan 10 15:52:17 2011
Background process QMNC not dead after 150 seconds
Mon Jan 10 15:52:17 2011
Stopping background process MMNL
Mon Jan 10 15:52:18 2011
Background process MMNL not dead after 10 seconds
Mon Jan 10 15:52:18 2011
Stopping background process MMON
Mon Jan 10 15:52:19 2011
Background process MMON not dead after 30 seconds
Mon Jan 10 15:52:19 2011
Shutting down instance (immediate)
License high water mark = 12
Mon Jan 10 15:52:19 2011
Stopping Job queue slave processes, flags = 7
Mon Jan 10 15:52:19 2011
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Mon Jan 10 15:52:24 2011
ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:52:24 2011
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Jan 10 15:52:25 2011
Shutting down archive processes
Archiving is disabled
Mon Jan 10 15:52:30 2011
ARCH shutting down
ARC1: Archival stopped
Mon Jan 10 15:52:35 2011
ARCH shutting down
ARC0: Archival stopped
Mon Jan 10 15:52:36 2011
Thread 1 closed at log sequence 11
Successful close of redo thread 1
Mon Jan 10 15:52:37 2011
Completed: ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:52:37 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Shutting down Data Guard Broker processes
Mon Jan 10 15:52:38 2011
Completed: Data Guard Broker shutdown
Mon Jan 10 15:52:40 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Jan 10 15:53:28 2011
Starting ORACLE instance (normal)
Mon Jan 10 15:53:28 2011
Specified value of sga_max_size is too small, bumping to 645922816
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 80
  sessions                 = 96
  event                    = 10191 trace name context forever, level 1
  sga_max_size             = 645922816
  __shared_pool_size       = 318767104
  shared_pool_size         = 318767104
  __java_pool_size         = 4194304
  java_pool_size           = 4194304
  shared_pool_reserved_size= 31598837
  filesystemio_options     = setall
  control_files            = E:\ORACLE\TST\ORIGLOGA\CNTRL\CNTLRTST.DBF, E:\ORACLE\TST\ORIGLOGB\CNTRL\CNTRLTST.DBF, F:\ORACLE\TST\SAPDATA1\CNTRL\CNTRLTST.DBF
  control_file_record_keep_time= 30
  db_block_size            = 8192
  __db_cache_size          = 318767104
  db_cache_size            = 318767104
  compatible               = 10.2.0
  log_archive_dest         = E:\oracle\TST\oraarch\TSTarch
  log_buffer               = 2061312
  log_checkpoint_interval  = 0
  db_files                 = 254
  log_checkpoints_to_alert = TRUE
  dml_locks                = 4000
  undo_management          = AUTO
  undo_tablespace          = PSAPUNDO
  undo_retention           = 43200
  recyclebin               = off
  remote_os_authent        = TRUE
  remote_login_passwordfile= EXCLUSIVE
  dispatchers              = (PROTOCOL=TCP) (SERVICE=TSTXDB)
  job_queue_processes      = 1
  background_dump_dest     = F:\ORACLE\TST\SAPTRACE\BACKGROUND
  user_dump_dest           = F:\ORACLE\TST\SAPTRACE\USERTRACE
  core_dump_dest           = F:\ORACLE\TST\SAPTRACE\BACKGROUND
  optimizer_features_enable= 10.2.0.1
  sort_area_size           = 2097152
  sort_area_retained_size  = 0
  db_name                  = TST
  open_cursors             = 800
  optimpeek_user_binds   = FALSE
  pga_aggregate_target     = 421317836
  workarea_size_policy     = AUTO
  statistics_level         = typical
  dg_broker_start          = TRUE
PMON started with pid=2, OS id=5296
PSP0 started with pid=3, OS id=4804
MMAN started with pid=4, OS id=3480
DBW0 started with pid=5, OS id=4312
LGWR started with pid=6, OS id=4036
CKPT started with pid=7, OS id=3372
SMON started with pid=8, OS id=5816
RECO started with pid=9, OS id=5240
CJQ0 started with pid=10, OS id=4524
MMON started with pid=11, OS id=6140
Mon Jan 10 15:53:28 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=5680
Mon Jan 10 15:53:28 2011
starting up 1 shared server(s) ...
DMON started with pid=15, OS id=5308
Mon Jan 10 15:53:28 2011
ALTER DATABASE   MOUNT
Mon Jan 10 15:53:32 2011
Setting recovery target incarnation to 4
Mon Jan 10 15:53:33 2011
Successful mount of redo thread 1, with mount id 1881229688
Mon Jan 10 15:53:33 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Mon Jan 10 15:53:33 2011
ALTER DATABASE OPEN
Mon Jan 10 15:53:36 2011
Starting Data Guard Broker (DMON)
INSV started with pid=16, OS id=4536
Mon Jan 10 15:53:40 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=18, OS id=5552
Mon Jan 10 15:53:40 2011
ARC0: Archival started
ARC1: Archival started
ARC1 started with pid=19, OS id=5312
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 11
  Current log# 3 seq# 11 mem# 0: E:\ORACLE\TST\ORIGLOGA\LOG_G13M1.DBF
  Current log# 3 seq# 11 mem# 1: E:\ORACLE\TST\MIRRLOGA\LOG_G13M2.DBF
Successful open of redo thread 1
Mon Jan 10 15:53:41 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jan 10 15:53:41 2011
SMON: enabling cache recovery
Mon Jan 10 15:53:42 2011
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Jan 10 15:53:42 2011
ARC0: Becoming the heartbeat ARCH
Mon Jan 10 15:53:43 2011
Incremental checkpoint up to RBA [0xb.18403.0], current log tail at RBA [0xb.18403.0]
Mon Jan 10 15:53:44 2011
Successfully onlined Undo Tablespace 1.
Mon Jan 10 15:53:44 2011
SMON: enabling tx recovery
Mon Jan 10 15:53:44 2011
Database Characterset is UTF8
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 2
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=20, OS id=5776
Mon Jan 10 15:53:50 2011
Completed: ALTER DATABASE OPEN
Mon Jan 10 15:55:46 2011
Starting ORACLE instance (normal)
Mon Jan 10 16:00:56 2011
Errors in file f:\oracle\tst\saptrace\background\tst_j000_3228.trc:
Mon Jan 10 16:01:26 2011
Beginning log switch checkpoint up to RBA [0xc.2.10], SCN: 16865686
Mon Jan 10 16:01:26 2011
Thread 1 advanced to log sequence 12 (LGWR switch)
  Current log# 4 seq# 12 mem# 0: E:\ORACLE\TST\ORIGLOGB\LOG_G14M1.DBF
  Current log# 4 seq# 12 mem# 1: E:\ORACLE\TST\MIRRLOGB\LOG_G14M2.DBF
Mon Jan 10 16:03:54 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_5396.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 16:04:01 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_5396.trc:
ORA-00600: internal error code, arguments: [kcbgcur_3], [61846], [9], [4], [0], [], [], []
Mon Jan 10 16:04:07 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_5396.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 16:06:30 2011
Completed checkpoint up to RBA [0xc.2.10], SCN: 16865686
Mon Jan 10 16:23:50 2011
Incremental checkpoint up to RBA [0xc.4e3a.0], current log tail at RBA [0xc.4f1f.0]
Mon Jan 10 16:53:57 2011
Incremental checkpoint up to RBA [0xc.55b9.0], current log tail at RBA [0xc.5726.0]
Mon Jan 10 17:00:01 2011
Errors in file f:\oracle\tst\saptrace\background\tst_j000_2516.trc:
Mon Jan 10 17:00:29 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_6048.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 17:00:33 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_6048.trc:
ORA-00600: internal error code, arguments: [kcbgcur_3], [61846], [9], [4], [0], [], [], []
Mon Jan 10 17:00:37 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_6048.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 17:24:02 2011
Incremental checkpoint up to RBA [0xc.6125.0], current log tail at RBA [0xc.62ae.0]

Similar Messages

  • Need a help: how to recover using backup control file?

    Please a help:
    First computer
    1. I create a database
    2. put it in archive mode,
    3. shutdown and made a cold backup
    4. Created backup control file (alter database backup control file to trace)
    5. I started up and created some archived log files.
    Second Computer
    1. I copied all files created in the step 3 above except the control file
    2. I create all the same map directory on the 2nd computer as in the 1st computer
    3. I recreate the control file from the script got in the step 4 above
    4. I Copy archived log files generated at the step 5 in the local directory in the second computer
    5. I set the logsource and set the autorecovery to on
    6. I recover the database: RECOVER DATABASE USING BACKUP CONTROL FILE UNTIL CANCEL
    Error got:
    the archived log file applied do not go beyond the first one?,How could I do to applied all archived log files copied from the first computer to the second computer to have the same data?
    Thank you very much

    archived log sequeces in the first computerSQL> select sequence#,first_change#,next_change# from v$log_history;
    SEQUENCE# FIRST_CHANGE# NEXT_CHANGE#
    1 553723 555484
    2 555484 557345
    Actions I did in the second Computer(after copied the former two archived log files from the 1st computer)
    SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG
    2 MAXLOGFILES 16
    3 MAXLOGMEMBERS 3
    4 MAXDATAFILES 100
    5 MAXINSTANCES 8
    6 MAXLOGHISTORY 292
    7 LOGFILE
    8 GROUP 1 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG' SIZE 50M,
    9 GROUP 2 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG' SIZE 50M,
    10 GROUP 3 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG' SIZE 50M
    11 -- STANDBY LOGFILE
    12 DATAFILE
    13 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF',
    14 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF',
    15 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF',
    16 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF'
    17 CHARACTER SET WE8ISO8859P1
    18 ;
    Control file created.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Disabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 0
    Next log sequence to archive 0
    Current log sequence 0
    SQL> alter database archivelog;
    Database altered.
    SQL> set logsource C:\local_destination1_orcl
    SQL> set autorecovery on;
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 555611 generated at 01/18/2007 14:14:14 needed for thread 1
    ORA-00289: suggestion :
    C:\LOCAL_DESTINATION1_ORCL\ARCH.1_1_612194518_43F17CF5.ARC
    ORA-00280: change 555611 for thread 1 is in sequence #1
    ORA-00328: archived log ends at change 555483, need later change 555611
    ORA-00334: archived log:
    'C:\LOCAL_DESTINATION1_ORCL\ARCH.1_1_612194518_43F17CF5.ARC'
    Idon't know where the change 555611 is coming from?

  • Recovery using backup control file

    Hello friends,
    I have a scenario where i am unable to recover by database by using backup control file option can u pls give ur expert advice.
    1) Database is working in ARCHIVE MODE.
    2) One of my file was READ ONLY when i take my closed backup. At this time
    v$log file output is :
    group# thread# sequence# bytes member arc status first_change#
    1 1 8 8192 2 yes inactive 4697463
    2 1 9 8192 2 yes active 4717493
    3 1 10 8192 2 no current 4717738
    3) After 2-3 log switches i have made it READ WRITE.
    4) After making it READ WRITE i have taken controlfile backup by using
    ALTER SYSTEM BACKUP CONTROLFILE TO 'E:\ORACLE\CONTROL01.CTL';.
    5) Again i have make some log switches.
    6) Shutdown my database using SHUTDOWN option.
    7) Copy my SYSTEM,UNDO,USER,INDEX datafiles from my backup (taken at
    step 2) and CONTROL file (taken at step 4).
    8) I have not copied my old redo log files so those are new.
    9) I mount database & then use this command to recover database :
    RECOVER DATABASE USING BACKUP CONTROLFILE AUTO;
    10) My recovery process starts applying archived log files and applied upto
    sequence no 9. When it starts applying last one 10 which is online redo log
    and not yet archived my recovery process fails by giving this error:
    ORA-00308: cannot open archived log 'd:\oracle\oradata\practice\archive\1_10.dbf'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    11) I try to open database using :
    ALTER DATABASE OPEN RESETLOGS;
    it gives following warning:
    Error at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: datafile 1: 'D:\ORACLE\ORADATA\PRACTICE\SYSTEM01.DBF'
    Please guide me why it is so ?
    Whether in BACKUP CONTROL FILE CASES system didn't recognise ONLINE REDO LOG FILES or it is anything else.
    Regards
    Sethi

    Hi,
    >>I am not using RMAN. I am taking user managed backups. Moreover i have tried what u said that make checkpoints also but again i came to the same result when it try to apply last archived log which was current redo log when database was started to shutdown it says unable to find the specified file & then when i open database using resetlogs it says system file needs media recovery.
    it show error because you are using wrong approach of Recovery.
    Alter database open Resetlog command is used only in incomplete recovery.
    but your are giving
    Recover database command,it means ur performing full recovery (means you have apply online redo logfile.) and after applying it you should open the database with Alter database Open command.
    No need to give resetlog option.
    Again Restore all backup;
    Issue Recover database;
    and open the database with
    Alter database open;
    Thanks
    Kuljeet Pal Singh

  • Can I recover the database to the current time using a backup control file?

    Can I recover the database to the current time using a backup control file? How far can I recover this database?
    I have an Oracle 10g(10.2.3) database on RHEL4.3 system.
    I have lost all the current control files and all the online redo logs, archived redo logs and all other files are OK.
    Now I have to recovery this database using a backup control file.
    Can I recover the database without any data lost?

    If
    a) it was a Shutdown Abort or an Instance Crash (i.e. backgrounds died on detecting loss of redo logs),
    b) redo logs are lost
    c) data files are intact
    You'd have to
    a) Restore datafiles
    b) Do an Incomplete Recovery to the last available ArchiveLog
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

  • Restore Backup control file doubt ?

    when restoring backup control file why we need to set the DBID first?
    Thankx..

    When using a recovery catalog and attempting to restore a lost control file, you encounter an error if there are other databases are registered in the recovery catalog with the same name as your target database. To resolve this error, you must uniquely identify the database by DBID for the restore operation. This requires determining the correct DBID for your database, and then using the SET DBID command to identify the target database before the RESTORE CONTROLFILE.

  • System Core Dumped after Oracle patch upgrade 9.2.0.6 to 9.2.0.8

    Hi,
    We are continously getting dumps on our BW Central instance server after we did an Oracle patch upgrade from 9.2.0.6 to 9.2.0.8.
    Following is our system environment
    SAP Release.............. "640"
    Application server....... "abci"
    Operating system......... "SunOS"
    Release.................. "5.10"
    Hardware type............ "sun4v"
    Database server.......... "abdb"
    Database type............ "ORACLE"
    Database name............ "ABP"
    Database owner........... "SAPABP"
    SAP kernel............... "640"
    Database version......... "OCI_920 "
    Patch level.............. "175"
    Following below is the Core Dump that is generated for any process chains that we schedule on our BW server
    Runtime Errors         SYSTEM_CORE_DUMPED
    Date and Time          14.04.2008 09:26:17
    ShrtText
         Process terminated by signal 11.
    What happened?
        The current ABAP program had to be terminated because the
        ABAP processor detected an internal system error.
        The current ABAP program "SAPMSSY2" had to be terminated because the ABAP
        processor discovered an invalid system state.
    What can you do?
        Make a note of the actions and input which caused the error.
        To resolve the problem, contact your SAP system administrator.
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer
        termination messages, especially those beyond their normal deletion
        date.
    Error analysis
        An SAP System process was terminated by an operating system signal.
        Possible reasons for this are:
        1. Internal SAP System error.
        2. Process was terminated externally (by the system administrator).
                   Last error logged in SAP kernel
        Component............ "Taskhandler"
        Place................ "SAP-Server awci_ABP_00 on host awci (wp 5)"
        Version.............. 1
        Error code........... 11
        Error text........... "ThSigHandler: signal"
        Description.......... " "
        System call.......... " "
        Module............... "thxxhead.c"
        Line................. 9780
    How to correct the error
        The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
        contains a file called 'core'.
        Save this file under another name.
        If you cannot solve the problem yourself and you wish to send
        an error message to SAP, include the following documents:
        1. A printout of the problem description (short dump)
           To obtain this, select in the current display "System->List->
           Save->Local File (unconverted)".
        2. A suitable printout of the system log
           To obtain this, call the system log through transaction SM21.
           Limit the time interval to 10 minutes before and 5 minutes
           after the short dump. In the display, then select the function
           "System->List->Save->Local File (unconverted)".
        3. If the programs are your own programs or modified SAP programs,
           supply the source code.
           To do this, select the Editor function "Further Utilities->
           Upload/Download->Download".
        4. Details regarding the conditions under which the error occurred
           or which actions and input led to the error.
    Kindly help.
    Regards
    Sachin
    Edited by: Sachin N on Apr 14, 2008 12:26 PM

    No. If the environment would be wrong the system wouldn´t start up.
    Core dumps are in 99 % of the cases program errors (in the SAP kernel or in an interface (libdbora*)), misaligend accesses of data etc.
    If you encounter such an error have a look in the C-Stack. If you can´t see where the error is happening opening an OSS call. Most of those errors are fixed by installing the latest patches for the kernel and the database interface.
    Markus

  • A question about restoring from cold backup(control file backup not clear)

    Hi,
    I had another question about restoring the cold backup. My database is in noarchivelog mode and after taking a consistent cold backup, all I need to do is to restore the backup right? -Why I got this question is because: when I backup my control file to trace, I see statements like this:-----
    -- Commands to re-create incarnation table
    -- Below log names MUST be changed to existing filenames on
    -- disk. Any one log file from each branch can be used to
    -- re-create incarnation records.
    -- ALTER DATABASE REGISTER LOGFILE '/uo1/app1/arch1_1_647102958.dbf';
    -- Recovery is required if any of the datafiles are restored backups,
    -- or if the last shutdown was not normal or immediate.
    RECOVER DATABASE
    -- Database can now be opened normally.
    ALTER DATABASE OPEN;
    My database is in noarchivelog mode now so don't know why these statements (of register the logfile) is there in the backup of control file? so when I restore the cold backup of this database, it will still work correct? (there is no logfile I have only CRD files in cold backup -no archive log files.)
    thanks
    Nirav

    Thanks for your inputs! It is most useful to me.
    Regards
    Nirav

  • Memoy fault, core dump after import

    Hi,
    db is 9.2.0.7, os is hp-ux itanium 11.23
    i have done schema level import, after import, i got the memory fault core dump at end of the import log file as last entry. I have seen core dump file created.
    I did not see any errors in alert log file.
    But Import has been done successfuly and can check that all objects are imported successfully.
    why this memory cored dump error logged in import log file.

    Please post full error message what You got.

  • Sshd core dump after logout

    I've noticed that sshd has been producing core dumps. The core dumps aren't affecting anything and appear to be produced after the ssh session ends.
    /var/adm/messages shows:
    Jun 30 09:59:59 www1 sshd[15453]: [ID 800047 auth.info] Accepted publickey for webstats from 123.123.123.123 port 4935 ssh2
    Jun 30 10:00:01 www1 genunix: [ID 603404 kern.notice] NOTICE: core_log: sshd[15453] core dumped: /var/core/core_www1_sshd_0_0_1151625600_15453
    A core dump isn't produced every time but only appears to happen after ssh connections from windows systems running cygwin.
    Running adb on a core dump shows:
    core file = core_www1_sshd_0_0_1151390790_3514 -- program ``/usr/lib/ssh/sshd
    '' on platform i86pc
    SIGSYS: Bad System Call
    Like I said, it doesn't appear to be causing any problems. Any ideas on how to stop it?

    Forgot to mention. We are calling OCISessionEnd before rolling through OCIServerDetach.
    /* STATIC */
    static void logout()
    printf ("\n\nFreeing statement handles..\n");
    if(stmthp) OCIHandleFree ((dvoid *) stmthp, (ub4) OCI_HTYPE_STMT);
    printf ("Logging off...\n");
    if(authp) OCISessionEnd (svchp, errhp, authp, (ub4) 0);

  • After Restoring/Backup of File System XI Java Instances are not up!

    Hello all,
    We are facing problem in restoring the SAP XI System, after taking backup of the system the <b>java instances</b> in SAP XI System are not starting again. ABAP connections are fine.
    Can anyone provide suggestions/solutions in order to restore the XI System back.
    The system information is as follows.
    System Component:     SAP NetWeaver 2004s, <b>PI 7.0</b>
    Operating System:     SunOS 5.9, SunOS 5.10
    Database:          ORACLE 9.2.0.
    Regards,
    Ketan Patel

    If it´s REALLY a PI 7.0 (SAP_BASIS 700 and WebAS Java 7.00) then it´s not compatible. WebAS 7.00 needs Oracle 10g (http://service.sap.com/pam)
    Also see
    http://service.sap.com/nw2004s
    --> Availibility
    --> SAP NetWeaver 7.0 (2004s) PAM
    If you open the Powerpoint, you will see that Oracle 9 is not listed. I wonder, how you got that installed.
    Neverless, if you recover a Java instance, both filesystem and database content (of the Java schema) must be in sync, means, you need to restore both, database (schema) and filesystem, that have been backed up at the same time.
    Check Java Backup and Restore :
    Restoring the System
           1.      Shut down the system.
           2.      Install a new AS Java system using SAPInst, or restore the file system from the offline backups that you created.
           3.      Import the database backup using the relevant tools provided by the database vendor.
           4.      Overwrite the SAP system directory /usr/sap/.
           5.      Start the system (see Starting and Stopping SAP NetWeaver ABAP and Java.)
    The J2EE Engine is restored with the last backup.
    Markus

  • BACKUP CONTROL FILE

    Hi all,
    11.2.0.1
    Aix 6.1
    I want to backup my control file to text as in
    SQL> alter system backup controlfile to '/u01/a.txt';
    But  the output is not readable
    Why is that if the command is
    SQL> alter system backup controlfile to trace;
    The output is readable but it is very hard to find
    Please help...
    Thanks ,
    zxy

    Saran, you should actually take care of what the OP is saying. He/she certainly even did not tried the command he/she tells us because it's not an option of "alter system".
    SQL> alter system backup controlfile to trace as '/u01/a.sql';
    alter system backup controlfile to trace as '/u01/a.sql'
    ERROR at line 1:
    ORA-02065: illegal option for ALTER SYSTEM
    SQL>
    Please see Hemant's post instead.
    Mod. action: your "correct" response is unmarked.
    Nicolas.

  • Rman backup control file

    hii i am working on oracle 10g 10.2.0.4.0 on solaris 10 have asm and rac setup(2 node rac).
    i have only one control file--+DATA_DG1/ftssdb/controlfile/current.270.664476369
    i am backing up these control file with rman
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/rman_node1/%F';
    c-31850833-20100909-00 is a backed up piece of control file.
    now suddenly one system admin deleted that control file...how can i recover my database using rman backup??

    You can found these entries like :
    CREATE CONTROLFILE REUSE DATABASE "DBNAME" NORESETLOGS NOARCHIVELOG ==depends what is your db log mode
    MAXLOGFILES 32
    MAXLOGMEMBERS 2
    MAXDATAFILES 30
    MAXINSTANCES 8
    MAXLOGHISTORY 800
    LOGFILE
    GROUP 1 '/u01/oracle/7.1.6/dbs/log1p716.dbf' SIZE 500K,
    GROUP 2 '/u01/oracle/7.1.6/dbs/log2p716.dbf' SIZE 500K,
    GROUP 3 '/u01/oracle/7.1.6/dbs/log3p716.dbf' SIZE 500K
    DATAFILE
    '/u01/oracle/7.1.6/dbs/systp716.dbf' SIZE 40M,
    '/u01/oracle/7.1.6/dbs/tempp716.dbf' SIZE 550K,
    '/u01/oracle/7.1.6/dbs/toolp716.dbf' SIZE 15M
    # Recovery is required if any of the datafiles are restored backups,
    # or if the last shutdown was not normal or immediate.
    RECOVER DATABASE
    # Database can now be opened normally.
    ALTER DATABASE OPEN;
    Edited by: user00726 on Sep 9, 2010 4:42 AM

  • BDB core dumps after addition of 30MB data

    Hi,
    BDB dumps core after adding about 100000 items at regular intervals on HP-UX 64 bit environment.
    Stack trace :
    Program terminated with signal 6, Aborted.
    #0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
    (gdb) bt
    #0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
    #1 0xc000000000260cf0:0 in raise+0x30 () from /usr/lib/hpux64/libc.so.1
    #2 0xc0000000002fe710:0 in abort+0x190 () from /usr/lib/hpux64/libc.so.1
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_err.o.
    If NOT specified will behave as a non -g compiled binary.
    #3 0xc000000038deb0f0:0 in __db_panic+0xc0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile log_put.o.
    If NOT specified will behave as a non -g compiled binary.
    #4 0xc000000038e70ab0:0 in __log_flush_int+0x7e0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    #5 0xc000000038e72d80:0 in __log_flush+0xa0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile mp_bh.o.
    If NOT specified will behave as a non -g compiled binary.
    #6 0xc000000038e77fe0:0 in __memp_pgwrite+0x5f0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    #7 0xc000000038e77460:0 in __memp_bhwrite+0x6a0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile mp_alloc.o.
    If NOT specified will behave as a non -g compiled binary.
    #8 0xc000000038e76560:0 in __memp_alloc+0xb20 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile mp_fget.o.
    If NOT specified will behave as a non -g compiled binary.
    #9 0xc000000038e7a600:0 in __memp_fget+0xc60 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so---Type <return> to continue, or q <return> to quit---
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile bt_search.o.
    If NOT specified will behave as a non -g compiled binary.
    #10 0xc000000038d13720:0 in __bam_search+0x8d0 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile bt_cursor.o.
    If NOT specified will behave as a non -g compiled binary.
    #11 0xc000000038cf4e30:0 in __bam_c_search+0x590 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    #12 0xc000000038cf02c0:0 in __bam_c_get+0x640 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_cam.o.
    If NOT specified will behave as a non -g compiled binary.
    #13 0xc000000038de03d0:0 in __db_c_get+0x530 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_am.o.
    If NOT specified will behave as a non -g compiled binary.
    #14 0xc000000038dccf60:0 in __db_put+0x320 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile db_iface.o.
    If NOT specified will behave as a non -g compiled binary.
    #15 0xc000000038df37a0:0 in __db_put_pp+0x240 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    warning:
    ERROR: Use the "objectdir" command to specify the search
    path for objectfile cxx_db.o.
    If NOT specified will behave as a non -g compiled binary.
    #16 0xc000000038cbbc90:0 in Db::put(DbTxn*,Dbt*,Dbt*,unsigned int)+0x120 ()
    from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
    If some body as an idea about the cause for dump, pls reply.
    Thanks,
    Sandhya

    Hi Sandhya,
    This issue is already handled on your other thread:
    BDB dumps core after adding approx 19MB of data
    Please follow the suggestions provided there and try keeping one issue per thread when posting. The stack trace posted here is almost identical to the previous one you posted, and contains in addition only a couple of calls for memory pool file allocation and writing.
    Thanks, regards,
    Andrei

  • Backup control file to trace failing with ORAORA-01116

    Hi,
    backup failing on 10.2 version as includes a backup controlfile command. This falls over with
    unable to open file /u10/oradata/TISD/temp101.dbf
    Now, there is a tempfile there, temp01.dbf.
    Why is the temp101.dbf being looked for?
    How can I proceed from this ?
    As it doenst exist, I am tempted to create it; but why is it temp101? (and not something like temp02)
    Thanks,
    DA
    Edited by: Dan A on Jul 16, 2009 4:31 AM

    This turned out to be a case of a user playing around with the temp tablespace and not dropping original correctly. In teh end I dropped the tablasepace with everyting in it.
    Thanks to all.
    DA

  • Zfs core dumps in Solaris Zones after patchcluster installation

    Hi
    I've installed the recommended patch cluster for Solaris 10 (SPARC) on my T2000 Server.
    Now after the reboot all the Solaris Zones (got about 10 of them) instantly do zfs core dumps when their booted.
    Some Output:
    Dec 15 15:34:43 XXXXX genunix: NOTICE: core_log: zfs[1711] core dumped: /var/core/core_XXXXXX_zfs_0_0_1292423682_1711
    bash-3.00# svcs
    STATE STIME FMRI
    online 13:58:50 svc:/system/svc/restarter:default
    online 13:58:51 svc:/system/filesystem/root:default
    online 13:58:51 svc:/network/loopback:default
    online 13:58:53 svc:/network/pfil:default
    online 13:58:54 svc:/system/installupdates:default
    online 13:58:55 svc:/system/boot-archive:default
    online 13:58:56 svc:/network/physical:default
    online 13:58:57 svc:/system/filesystem/usr:default
    online 13:58:57 svc:/system/identity:node
    online 13:58:58 svc:/system/device/local:default
    online 13:58:58 svc:/system/keymap:default
    online 13:58:58 svc:/milestone/devices:default
    online 13:58:58 svc:/system/filesystem/minimal:default
    online 13:58:58 svc:/system/rmtmpfiles:default
    online 13:58:58 svc:/system/cryptosvc:default
    online 13:58:59 svc:/system/identity:domain
    online 13:58:59 svc:/system/name-service-cache:default
    online 13:58:59 svc:/system/coreadm:default
    online 13:58:59 svc:/network/ipsec/ipsecalgs:default
    online 13:58:59 svc:/application/print/ppd-cache-update:default
    online 13:58:59 svc:/network/ipsec/policy:default
    online 13:59:00 svc:/milestone/network:default
    online 13:59:00 svc:/network/initial:default
    online 13:59:00 svc:/system/manifest-import:default
    online 13:59:00 svc:/network/service:default
    online 13:59:00 svc:/milestone/single-user:default
    online 13:59:00 svc:/network/dns/client:default
    online 13:59:00 svc:/network/routing-setup:default
    online 13:59:00 svc:/milestone/name-services:default
    online 13:59:03 svc:/milestone/sysconfig:default
    online 13:59:03 svc:/system/utmp:default
    online 13:59:03 svc:/system/console-login:default
    offline 13:58:51 svc:/system/sysidtool:net
    offline 13:58:51 svc:/network/rpc/bind:default
    offline 13:58:51 svc:/system/sysidtool:system
    offline 13:58:52 svc:/network/nfs/status:default
    offline 13:58:52 svc:/network/nfs/nlockmgr:default
    offline 13:58:52 svc:/network/nfs/cbd:default
    offline 13:58:52 svc:/network/nfs/mapid:default
    offline 13:58:52 svc:/network/inetd:default
    offline 13:58:52 svc:/network/nfs/client:default
    offline 13:58:52 svc:/system/filesystem/autofs:default
    offline 13:58:53 svc:/system/system-log:default
    offline 13:58:53 svc:/network/smtp:sendmail
    offline 13:58:53 svc:/system/cron:default
    offline 13:58:53 svc:/milestone/multi-user:default
    offline 13:58:54 svc:/application/management/snmpdx:default
    offline 13:58:54 svc:/application/management/dmi:default
    offline 13:58:54 svc:/application/management/seaport:default
    offline 13:58:54 svc:/network/ssh:default
    offline 13:58:54 svc:/milestone/multi-user-server:default
    offline 13:58:54 svc:/application/font/fc-cache:default
    offline 13:58:55 svc:/application/management/sma:default
    offline 13:58:58 svc:/system/sac:default
    offline 13:59:00 svc:/network/shares/group:default
    offline 13:59:00 svc:/system/boot-archive-update:default
    maintenance 15:34:43 svc:/system/filesystem/local:default
    uninitialized 13:58:52 svc:/network/rpc/gss:default
    uninitialized 13:58:54 svc:/application/font/stfsloader:default
    uninitialized 13:58:55 svc:/network/rpc/rstat:default
    uninitialized 13:58:55 svc:/application/print/rfc1179:default
    uninitialized 13:58:55 svc:/application/x11/xfs:default
    uninitialized 13:58:55 svc:/network/finger:default
    uninitialized 13:58:55 svc:/network/ftp:default
    uninitialized 13:58:56 svc:/network/login:rlogin
    uninitialized 13:58:56 svc:/network/nfs/rquota:default
    uninitialized 13:58:56 svc:/network/rpc/rusers:default
    uninitialized 13:58:56 svc:/network/rpc/smserver:default
    uninitialized 13:58:57 svc:/network/security/ktkt_warn:default
    uninitialized 13:58:57 svc:/network/shell:default
    uninitialized 13:58:57 svc:/network/telnet:default
    uninitialized 13:58:58 svc:/network/rpc-100235_1/rpc_ticotsord:default
    uninitialized 13:58:58 svc:/network/rpc/cde-calendar-manager:default
    uninitialized 13:58:59 svc:/network/rpc/cde-ttdbserver:tcp
    bash-3.00# svcs -x
    svc:/system/filesystem/local:default (local file system mounts)
    State: maintenance since Wed Dec 15 15:34:43 2010
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/system-filesystem-local:default.log
    Impact: 24 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/gss:default (Generic Security Service)
    State: uninitialized since Wed Dec 15 13:58:52 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: gssd(1M)
    Impact: 11 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/rstat:default (kernel statistics server)
    State: uninitialized since Wed Dec 15 13:58:55 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: rpc.rstatd(1M)
    See: rstatd(1M)
    Impact: 1 dependent service is not running. (Use -v for list.)
    bash-3.00# cat /var/svc/log/system-filesystem-local:default.log
    [ Jul 10 03:41:35 Enabled. ]
    [ Jul 10 03:43:45 Rereading configuration. ]
    [ Jul 10 03:44:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 03:44:18 Method "start" exited with status 0 ]
    [ Jul 10 12:44:36 Enabled. ]
    [ Jul 10 12:44:45 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:44:45 Method "start" exited with status 0 ]
    [ Jul 10 12:45:03 Enabled. ]
    [ Jul 10 12:45:09 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:45:09 Method "start" exited with status 0 ]
    [ Jul 10 13:54:39 Enabled. ]
    [ Jul 10 13:54:46 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 13:54:46 Method "start" exited with status 0 ]
    [ Jul 18 12:34:19 Enabled. ]
    [ Jul 18 12:34:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 12:34:27 Method "start" exited with status 0 ]
    [ Jul 18 17:29:08 Enabled. ]
    [ Jul 18 17:29:15 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 17:29:15 Method "start" exited with status 0 ]
    [ Jul 19 11:13:34 Enabled. ]
    [ Jul 19 11:13:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:13:42 Method "start" exited with status 0 ]
    [ Jul 19 11:32:23 Enabled. ]
    [ Jul 19 11:32:30 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:32:31 Method "start" exited with status 0 ]
    [ Jul 19 11:57:06 Enabled. ]
    [ Jul 19 11:57:13 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:57:13 Method "start" exited with status 0 ]
    [ Jul 19 12:40:05 Enabled. ]
    [ Jul 19 12:40:12 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 12:40:12 Method "start" exited with status 0 ]
    [ Jul 20 15:51:46 Enabled. ]
    [ Jul 20 15:51:54 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 20 15:51:54 Method "start" exited with status 0 ]
    [ Jul 24 11:42:17 Enabled. ]
    [ Jul 24 11:42:25 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 24 11:42:25 Method "start" exited with status 0 ]
    [ Jul 27 12:05:06 Stopping because service disabled. ]
    [ Jul 27 12:05:07 Executing stop method (null) ]
    [ Jul 27 12:13:10 Enabled. ]
    [ Jul 27 12:13:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 12:13:17 Method "start" exited with status 0 ]
    [ Jul 27 13:10:26 Stopping because service disabled. ]
    [ Jul 27 13:10:26 Executing stop method (null) ]
    [ Jul 27 13:18:19 Enabled. ]
    [ Jul 27 13:18:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 13:18:26 Method "start" exited with status 0 ]
    [ Jul 31 10:12:31 Enabled. ]
    [ Jul 31 10:12:38 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 31 10:12:39 Method "start" exited with status 0 ]
    [ Aug  7 10:08:52 Stopping because service disabled. ]
    [ Aug  7 10:08:52 Executing stop method (null) ]
    [ Aug  7 10:34:50 Enabled. ]
    [ Aug  7 10:34:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  7 10:34:58 Method "start" exited with status 0 ]
    [ Aug  9 09:14:50 Stopping because service disabled. ]
    [ Aug  9 09:14:50 Executing stop method (null) ]
    [ Aug  9 09:55:03 Enabled. ]
    [ Aug  9 09:55:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  9 09:55:11 Method "start" exited with status 0 ]
    [ Aug 16 10:46:43 Enabled. ]
    [ Aug 16 10:46:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 10:46:50 Method "start" exited with status 0 ]
    [ Aug 16 12:06:56 Enabled. ]
    [ Aug 16 12:07:02 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 12:07:02 Method "start" exited with status 0 ]
    [ Aug 16 13:45:10 Enabled. ]
    [ Aug 16 13:45:16 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 13:45:16 Method "start" exited with status 0 ]
    [ Aug 16 14:36:59 Enabled. ]
    [ Aug 16 14:37:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 14:37:07 Method "start" exited with status 0 ]
    [ Aug 16 15:00:40 Enabled. ]
    [ Aug 16 15:00:47 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 15:00:47 Method "start" exited with status 0 ]
    [ Aug 22 16:00:13 Enabled. ]
    [ Aug 22 16:00:21 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 22 16:00:21 Method "start" exited with status 0 ]
    [ Aug 23 09:49:04 Enabled. ]
    [ Aug 23 09:49:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 09:49:11 Method "start" exited with status 0 ]
    [ Aug 23 09:49:23 Stopping because service disabled. ]
    [ Aug 23 09:49:23 Executing stop method (null) ]
    [ Aug 23 10:04:13 Enabled. ]
    [ Aug 23 10:04:20 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:04:20 Method "start" exited with status 0 ]
    [ Aug 23 10:06:57 Enabled. ]
    [ Aug 23 10:07:04 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:07:05 Method "start" exited with status 0 ]
    [ Oct 23 08:43:05 Enabled. ]
    [ Oct 23 08:43:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 23 08:43:14 Method "start" exited with status 0 ]
    [ Nov 21 14:51:50 Enabled. ]
    [ Nov 21 14:51:58 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 21 14:51:59 Method "start" exited with status 0 ]
    [ Nov 29 15:33:19 Enabled. ]
    [ Nov 29 15:33:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 29 15:33:27 Method "start" exited with status 0 ]
    [ Dec 18 13:37:35 Enabled. ]
    [ Dec 18 13:37:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 18 13:37:42 Method "start" exited with status 0 ]
    [ Dec 19 08:48:07 Enabled. ]
    [ Dec 19 08:48:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:48:14 Method "start" exited with status 0 ]
    [ Dec 19 08:56:07 Enabled. ]
    [ Dec 19 08:56:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:56:14 Method "start" exited with status 0 ]
    [ Dec 19 08:57:41 Enabled. ]
    [ Dec 19 08:57:48 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:57:48 Method "start" exited with status 0 ]
    [ Feb  1 10:39:48 Enabled. ]
    [ Feb  1 10:39:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  1 10:39:56 Method "start" exited with status 0 ]
    [ Feb  8 11:12:50 Enabled. ]
    [ Feb  8 11:12:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  8 11:12:57 Method "start" exited with status 0 ]
    [ Jun  6 10:08:34 Enabled. ]
    [ Jun  6 10:08:44 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jun  6 10:08:46 Method "start" exited with status 0 ]
    [ Aug  8 09:45:48 Enabled. ]
    [ Aug  8 09:46:35 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  8 09:46:36 Method "start" exited with status 0 ]
    [ Aug 14 17:53:59 Enabled. ]
    [ Aug 14 17:54:06 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:54:06 Method "start" exited with status 0 ]
    [ Aug 14 17:55:20 Enabled. ]
    [ Aug 14 17:55:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:55:27 Method "start" exited with status 0 ]
    [ Aug 18 15:19:17 Enabled. ]
    [ Aug 18 15:19:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 18 15:19:24 Method "start" exited with status 0 ]
    [ Aug 29 12:56:48 Enabled. ]
    [ Aug 29 12:56:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 29 12:56:55 Method "start" exited with status 0 ]
    [ Oct 13 11:59:43 Enabled. ]
    [ Oct 13 11:59:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 13 11:59:51 Method "start" exited with status 0 ]
    [ Feb 26 16:47:00 Enabled. ]
    [ Feb 26 16:47:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb 26 16:47:07 Method "start" exited with status 0 ]
    [ Apr 14 15:54:17 Enabled. ]
    [ Apr 14 15:54:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Apr 14 15:54:25 Method "start" exited with status 0 ]
    [ Aug 28 08:49:58 Stopping because service disabled. ]
    [ Aug 28 08:49:58 Executing stop method (null) ]
    [ Aug 28 08:52:54 Enabled. ]
    [ Aug 28 08:53:01 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 28 08:53:01 Method "start" exited with status 0 ]
    [ Aug 28 09:08:20 Stopping because service disabled. ]
    [ Aug 28 09:08:20 Executing stop method (null) ]
    [ Sep  1 16:05:36 Enabled. ]
    [ Sep  1 16:06:05 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 16:06:05 Method "start" exited with status 0 ]
    [ Sep  1 19:29:19 Enabled. ]
    [ Sep  1 19:29:27 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 19:29:27 Method "start" exited with status 0 ]
    [ Sep  1 23:04:00 Enabled. ]
    [ Sep  1 23:04:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 23:04:08 Method "start" exited with status 0 ]
    [ Sep  2 00:23:41 Stopping because service disabled. ]
    [ Sep  2 00:23:42 Executing stop method (null) ]
    [ Sep  2 00:46:46 Enabled. ]
    [ Sep  2 00:46:53 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  2 00:46:54 Method "start" exited with status 0 ]
    [ Sep 26 12:04:34 Enabled. ]
    [ Sep 26 12:04:41 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep 26 12:04:42 Method "start" exited with status 0 ]
    [ Oct 20 13:05:09 Stopping because service disabled. ]
    [ Oct 20 13:05:10 Executing stop method (null) ]
    [ Oct 20 13:24:01 Enabled. ]
    [ Oct 20 13:24:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 20 13:24:09 Method "start" exited with status 0 ]
    [ Oct 21 16:30:59 Enabled. ]
    [ Oct 21 16:31:09 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:31:09 Method "start" exited with status 0 ]
    [ Oct 21 16:32:42 Stopping because service disabled. ]
    [ Oct 21 16:32:42 Executing stop method (null) ]
    [ Oct 21 16:42:05 Enabled. ]
    [ Oct 21 16:42:15 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:42:15 Method "start" exited with status 0 ]
    [ Oct 21 17:27:37 Enabled. ]
    [ Oct 21 17:27:47 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 17:27:47 Method "start" exited with status 0 ]
    [ Oct 22 11:08:34 Enabled. ]
    [ Oct 22 11:08:43 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 22 11:08:43 Method "start" exited with status 0 ]
    [ Dec  9 09:17:33 Stopping because service disabled. ]
    [ Dec  9 09:17:33 Executing stop method (null) ]
    [ Dec 10 11:47:14 Enabled. ]
    [ Dec 10 11:47:24 Executing start method ("/lib/svc/method/fs-local") ]
    [ Dec 10 11:47:25 Method "start" exited with status 0 ]
    [ Dec 15 10:52:25 Stopping because service disabled. ]
    [ Dec 15 10:52:25 Executing stop method (null) ]
    [ Dec 15 12:42:16 Enabled. ]
    [ Dec 15 12:42:26 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 12:42:28 Method "start" exited with status 95 ]
    [ Dec 15 13:13:19 Enabled. ]
    [ Dec 15 13:13:28 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:13:30 Method "start" exited with status 95 ]
    [ Dec 15 13:58:51 Enabled. ]
    [ Dec 15 13:59:00 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:59:03 Method "start" exited with status 95 ]
    [ Dec 15 15:34:41 Leaving maintenance because clear requested. ]
    [ Dec 15 15:34:41 Enabled. ]
    [ Dec 15 15:34:41 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 15:34:43 Method "start" exited with status 95 ]
    bash-3.00# /usr/sbin/zfs mount -a
    internal error: Unknown error
    Abort (core dumped)
    Before that I've installed the patch cluster with halted solaris zones which produced following output:
    Application of patches finished : 2010.12.15 12:08:43
    Following patches were applied :
    119254-77 119812-10 125719-31 140159-03 142911-01
    141588-04 119900-11 125731-05 142292-01 142933-02
    142251-02 119906-16 126206-05 141444-09 142909-17
    118666-28 120460-17 126363-08 141500-07 143140-04
    118667-28 121012-03 126365-16 141502-02 143502-01
    118777-16 121308-20 126868-04 141506-09 143506-01
    140860-02 122212-40 127724-02 141514-02 143615-02
    119059-56 122261-03 136998-09 141518-12 143731-01
    119213-23 122675-05 137000-07 141552-03 143733-01
    124628-10 123003-04 137080-05 141558-01 143977-01
    119252-29 123590-12 137147-06 141586-01 144053-04
    119280-23 123893-22 138195-04 141590-02 144106-01
    124188-03 124393-11 138822-07 141874-09 144254-01
    120199-15 124457-02 138826-07 141876-07 144488-04
    119534-19 124630-42 138880-02 142084-04 144492-01
    120272-28 125215-03 139099-04 142397-01 145124-01
    119757-18 125388-03 139620-01 142529-01 145796-01
    119783-15 125555-07
    Following patches were skipped :
    Patches already applied
    120900-04 119063-01 119810-05 123005-07 137093-01
    121133-02 119081-25 119986-03 124444-01 138866-03
    119317-01 119130-33 120061-02 124939-03 137137-09
    121296-01 123611-04 120201-05 124943-01 137871-02
    138215-01 140899-01 120292-02 124997-01 138181-01
    127884-01 122640-05 120329-02 125279-05 138361-01
    118712-23 126897-02 121975-01 125539-06 138373-02
    118918-24 127755-01 120719-02 125891-01 138647-01
    138217-01 125503-02 120830-06 126440-01 141016-01
    119578-30 125547-02 121095-02 126540-02 139555-08
    121453-02 140796-01 121606-04 127127-11 139967-01
    121453-02 120011-14 124171-07 136882-02 140455-01
    121118-16 139520-02 123630-03 137032-01 140563-01
    118833-36 119764-06
    Patches obsoleted by one or more patches already applied
    118731-01 124204-04 122660-10
    Patches not applicable to packages on the system
    121181-03 120410-33 121211-02 125533-15 143317-03
    119115-35 120412-11 122259-03 125541-06 143510-01
    119117-52 120414-27 122470-03 125952-20 143725-01
    119315-19 120543-21 122911-24 137004-08 143727-01
    119548-14 120739-06 122958-06 138387-01 143739-01
    119903-02 120811-09 123938-02 138824-07 144325-01
    120094-30 120849-04 125136-24 138876-01 145006-02
    120185-21 121104-11 125137-24 139986-01 145080-01
    119368-04 121136-02 125332-14 142244-02 145200-01
    120286-03
    Installation of patch set complete. PLEASE REBOOT THE SYSTEM.
    when i tried to reboot the system by init 6 the service iscsi hanged and produced syslog errors about a unkown iocall -> killed the process. System rebooted w/o errors.
    Does anyone have got an idea how to find out which patch or whatever do produce these errors?

    Hi,
    I'm having the same issue of diskmon core dumps after upgrading grid and database from 11.2.0.1 to 11.2.0.2 on Solaris 10 x86-64. Following this thread, I'm trying to deinstall the Oracle 11.2.0.1 grid home.
    I answered the following questions asked by the grid deinstall tool:
    1. ASM configuration was not detected in this Oracle home. Was ASM configured in this Oracle home (y|n): y
    2. Specify the ASM Diagnostic Destination: /db01/app/oracle/diag/asm/+ASM
    3. Specify the diskgroups that are managed by this ASM instance: DATA FRA
    4. De-configuring ASM will drop all the diskgroups at cleanup time. Do you want deconfig tool to drop the diskgroups:
    If I answer no to question 1, the tool exits with error.
    How do I answer question #4? (confused about this question of dropping diskgroups, it's already been upgraded)
    Deinstall of Oracle db Home 11.2.0.1 was successful.
    The +ASM instance has been upgraded and is running fine under 11.2.0.2 except for the excessive diskmon core dumps.
    Thanks,
    Lisa
    Edited by: user12018917 on Apr 19, 2011 10:21 AM

Maybe you are looking for

  • Removing modules to help with boot, not sure which modules to remove

    ok i have a dell studio 1555, 320gb hdd, i use ext4 for home and / and ext2 for boot and swap is swap i use kernel26-pae as i have 4gb ram i have an ati graphics card if you need anything else please tell me would really appreciate help with  improvi

  • 1 End-2-End Life Cycle Implementation

    Hi, Provide me with the detailed information about 1 End-2-End Life Cycle Implementation. How it is done?

  • Getting ripped episodes of LOST on my iPod Touch

    I own season 1 of LOST and Season 3 of Rescue Me. I've recently ripped some of the files to MP4 format to place on my Touch with handbrake. I cannot get the ripped versions of these episodes to load to my Touch. They are loading fine into my iTunes l

  • Proxy issues

    I am having some problem with the web publishing tool in a proxy network. I have kept a VI online using the web publishing tool, when in an open network it works perfectly fine. By working fine I mean when i try to open up the front panel from the li

  • Install AMS Centos6, libcap required

    ./installAMS ERROR: A required package, libcap, was not found on your Linux x86_64 RedHat.        Please install required package and run Adobe Media Server installer again. [root@ip-10-254-24-40 AMS_5_0_1_r1076]# yum install libcap Loaded plugins: f