RE:Undo_management=MANUAL

Hi all!
I'm trying to create the rollback segment below but get the error shown. Even when i set undo_management=MANUAL & restart my PC or stop/start Oracle services, it remains AUTO. What else need i do plz.
Thnx!
SQL> create rollback segment test tablespace ts_vas_hr;
create rollback segment test tablespace ts_vas_hr
ERROR at line 1:
ORA-30019: Illegal rollback Segment operation in Automatic Undo mode
SQL>
SQL> show parameter undo_management
NAME TYPE VALUE
undo_management string AUTO

You are probably using spfile. So if you have changed the parameter undo_management in pfile,it wont be into effect.
Do this
1)Check that you are using spfle or not.Issue
sql>show parameter spfileThis would give sme value.If it does than you are using spfile
2)
alter system set undo_management=mnanual scope=spfile3{code{
startup forceOr shut immediate and than startup.
4show parameter undo
If its shows manual as the setting than retry uour operation.
HTH
Aman....                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • Undo_management=Manual

    Hi
    We are performing system refresh from PRD system to another TST system.
    Our PRD system currently running on oracle 9i ECC 5.0 and HP-UX platform..we have installed
    new ECC 5.0 system with oracle 9i as TST system.
    But our PRD system is having UNDO_MANAGEMENT=MANUAL and ROLLBACK_SEGMENTS=PRS_1 to PRS_15
    and tablespace used is PSAPROLL.
    Our newly created TST system is having UNDO_MANAGEMENT=AUTO AND UNDO_TABLESPACE=PSAPUNDO.
    When we are trying to restore database and create controlfile ( Create controlfile SET database ...and so on) perform recovery ( recover datasabse using backu...until cancel)
    ...But when we give Alter database open resetlogs ... it terminate the Oracle instance and
    reason in alertlog is unable to find PSAPUNDO tablespace.
    currently We do not want to make any changes in PRD system ... do we need to switch to
    manual Undomanagement on TST system first and then perform system copy..
    Or simply change parameters UNDO_MANAGEMENT=MANUAL AND UNDO_TABLESPACE=PSAPROLL will
    do the trick.
    Please let me know at earliest currently my TST system is down and oracle instance terminated.
    Edited by: ganesh rr on Oct 2, 2008 6:21 AM
    Edited by: ganesh rr on Oct 2, 2008 6:30 AM
    Subject modified by moderator
    Read the "Rules of Engagement"
    Edited by: Juan Reyes on Oct 3, 2008 10:59 AM

    Thanks to all,
    I have done changes as per note 600141 and my target DB is up and running now.

  • Advantage for use undo_management MANUAL oracle 9i DWH

    Hi,
    I have a questions,
    What is the advantage for use undo_management MANUAL oracle 9i in DWH vs undo_management AUTO?
    I need to obtain the UNDO_BLOCK_PER_SEC, but when I try to obtain the information in the view v$undostat, appear "no rows selected", exist any form to obtain this information?
    Thanks for your help!!
    Regards!!

    To add to what SB said, do not tune what does not need tuning. That is, do not make changes till you have developed a case to support the change.
    In order to learn how to work with rollback segments look in your DBA Administration manual. Since Oracle now puts the emphasis on automatic undo management I would look for an earlier version of the documentation set and reference it since there is probably more information in the manual where manual RBS management was the only method.
    If you are a warehouse I would expect the number of users performing DML to be low and the update jobs to be large so I would expect a low number of large RBS segments to be allocated.
    HTH -- Mark D Powell --

  • Switching forn AUTO undo_management to MANUAL

    hi,
    1) after AUTO undo_management installation, i will use RBS MANUAL. But when i set the undo_management to MANUAL the database don't start.
    What's problem?
    2)Where will us use the AUTO or the MANUAL method?
    Regards.
    Tark.

    Hi
    You are right... I did a test... here the statement that I used for the switch:
    connect / as sysdba
    alter system set undo_management = manual scope = spfile;
    shutdown
    startup
    create public rollback segment rbs0 tablespace system;
    shutdown
    startup
    create tablespace rbs datafile '/tmp/rbs.dbf' size 10m;
    create public rollback segment rbs1 tablespace rbs;
    create public rollback segment rbs2 tablespace rbs;
    create public rollback segment rbs3 tablespace rbs;
    create public rollback segment rbs4 tablespace rbs;
    alter rollback segment rbs1 online;
    alter rollback segment rbs2 online;
    alter rollback segment rbs3 online;
    alter rollback segment rbs4 online;
    alter rollback segment rbs0 offline;
    Chris

  • EM 10g - Listener does not show up on DB home, but is running. Why??

    Oracle Version          10.2.0.1.0
    Microsoft Windows Server 2003 R2 Server 5.2 Service Pack 2 (32-bit)
    LSNRCTL> start LISTENER
    Starting tnslsnr: please wait...
    TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
    System parameter file is D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Log messages written to D:\oracle\product\10.2.0\db_1\network\log\listener.log
    Trace information written to D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
    Start Date 22-OCT-2007 11:42:18
    Uptime 0 days 0 hr. 0 min. 5 sec
    Trace Level user
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Listener Log File D:\oracle\product\10.2.0\db_1\network\log\listener.log
    Listener Trace File D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
    Services Summary...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    ========================================================
    LSNRCTL> status LISTENER
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
    Start Date 22-OCT-2007 11:42:18
    Uptime 0 days 0 hr. 14 min. 8 sec
    Trace Level user
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Listener Log File D:\oracle\product\10.2.0\db_1\network\log\listener.log
    Listener Trace File D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
    Services Summary...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "orcl.us-as1.nti2.org" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "orclXDB.us-as1.nti2.org" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "orcl_XPT.us-as1.nti2.org" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    The command completed successfully
    ======================================================
    C:\Documents and Settings\pierrel>netstat -a
    Active Connections
    Proto Local Address Foreign Address State
    TCP us-as1:smtp us-as1.nti2.org:0 LISTENING
    TCP us-as1:http us-as1.nti2.org:0 LISTENING
    TCP us-as1:nntp us-as1.nti2.org:0 LISTENING
    TCP us-as1:epmap us-as1.nti2.org:0 LISTENING
    TCP us-as1:microsoft-ds us-as1.nti2.org:0 LISTENING
    TCP us-as1:nntps us-as1.nti2.org:0 LISTENING
    TCP us-as1:kpop us-as1.nti2.org:0 LISTENING
    TCP us-as1:1110 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1111 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1117 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1119 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1158 us-as1.nti2.org:0 LISTENING
    TCP us-as1:1521 us-as1.nti2.org:0 LISTENING
    ==================================================
    init.ora
    # $Header: init.ora 25-jul-01.18:03:38 rajayar Exp $
    # Copyright (c) 1991, 2001, Oracle Corporation. All rights reserved. */
    # Example INIT.ORA file
    # This file is provided by Oracle Corporation to help you customize
    # your RDBMS installation for your site. Important system parameters
    # are discussed, and example settings given.
    # Some parameter settings are generic to any size installation.
    # For parameters that require different values in different size
    # installations, three scenarios have been provided: SMALL, MEDIUM
    # and LARGE. Any parameter that needs to be tuned according to
    # installation size will have three settings, each one commented
    # according to installation size.
    # Use the following table to approximate the SGA size needed for the
    # three scenarious provided in this file:
    # -------Installation/Database Size------
    # SMALL MEDIUM LARGE
    # Block 2K 4500K 6800K 17000K
    # Size 4K 5500K 8800K 21000K
    # To set up a database that multiple instances will be using, use the
    # same file for all instance. Place all instance-specific parameters
    # at the end of the file using the <sid>.<parameter_name> = <value> syntax.
    # This way, when you change a public
    # parameter, it will automatically change on all instances. This is
    # necessary, since all instances must run with the same value for many
    # parameters. For example, if you choose to use private rollback segments,
    # these must be specified differently for each instance, but since all gc_*
    # parameters must be the same on all instances, they should be in one file.
    # INSTRUCTIONS: Edit this file and the other INIT files it calls for
    # your site, either by using the values provided here or by providing
    # your own.
    # replace "clustdb" with your database name
    db_name = clustdb
    compatible=9.0.0
    db_files = 1024 # INITIAL
    #INITIAL
    #db_files=80
    #SMALL
    #DB_files=400
    #MEDIUM
    #db_files=1000
    #LARGE
    control_files = ("\\.\clustdb_control1", "\\.\clustdb_control2")
    db_file_multiblock_read_count = 8 # INITIAL
    # db_file_multiblock_read_count = 8
    #SMALL
    #db_file_multiblock_read_count = 16
    #MEDIUM
    #db_file_multiblock_read_count = 32
    #LARGE
    #Datawarehouse
    db_block_size=8192
    # Transaction processing
    # db_block_size=4096
    open_cursors=300
    #Transaction processing
    #sort_area_size=524288
    #Datawarehouse
    sort_area_size=1048576
    large_pool_size=1048576 #Transaction processing, Datawarehouse
    db_cache_size=50331648 #Datawarehouse, Transaction processing
    java_pool_size=67108864 #Datawarehouse, Transaction processing
    # db_block_buffers = 200 # INITIAL
    # db_block_buffers=100 #SMALL
    # db_block_buffers =550 # MEDIUM
    # db_block_buffers=3200 #LARGE
    #shared_pool_size = 52428800 # INITIAL
    shared_pool_size = 67108864 # datewarehouse, transaction processing
    log_checkpoint_interval = 10000
    processes = 59 # INITIAL
    # processes = 50
    #SMALL
    #processes = 100
    #MEDIUM
    #processes = 200
    #LARGE
    parallel_max_servers = 5
    #SMALL
    # parallel_max_servers = 4 x (number of CPUs)
    #MEDIUM
    # parallel_max_servers = 4 x (number of CPUs)
    # LARGE
    log_buffer = 8192 # INITIAL
    #log_buffer = 8192
    #SMALL
    #log_buffer = 32768
    #MEDIUM
    #log_buffer = 163840
    #LARGE
    # audit_trail = true # if you want auditing
    # timed_statistics = true # if you want timed statistics
    max_dump_file_size = 10240 # limit trace file size to 10 K each
    # Uncommenting the line below will cause automatic archiving if archiving has
    # been enabled using ALTER DATABASE ARCHIVELOG.
    # log_archive_start = true
    # log_archive_dest = %ORACLE_HOME%/admin/clustdb/arch
    # log_archive_format = "%%ORACLE_SID%%T%TS%S.ARC"
    # If using private rollback segments, place lines of the following
    # form at the end of this file:
    # <sid>.rollback_segments = (name1, name2)
    # If using public rollback segments, define how many
    # rollback segments each instance will pick up, using the formula
    # # of rollback segments = transactions / transactions_per_rollback_segment
    # In this example each instance will grab 40/10 = 4:
    # transactions = 40
    # transactions_per_rollback_segment = 10
    # Global Naming -- enforce that a dblink has same name as the db it connects to
    global_names = TRUE
    # Edit and uncomment the following line to provide the suffix that will be
    # appended to the db_name parameter (separated with a dot) and stored as the
    # global database name when a database is created. If your site uses
    # Internet Domain names for e-mail, then the part of your e-mail address after
    # the '@' is a good candidate for this parameter value.
    # db_domain = us.acme.com # global database name is db_name.db_domain
    # Uncomment the following line if you wish to enable the Oracle Trace product
    # to trace server activity. This enables scheduling of server collections
    # from the Oracle Enterprise Manager Console.
    # Also, if the oracle_trace_collection_name parameter is non-null,
    # every session will write to the named collection, as well as enabling you
    # to schedule future collections from the console.
    # oracle_trace_enable = TRUE
    # define directories to store trace and alert files
    background_dump_dest=%ORACLE_HOME%/admin/clustdb/bdump
    user_dump_dest=%ORACLE_HOME%/admin/clustdb/
    db_block_size = 4096
    remote_login_passwordfile = exclusive
    # text_enable = TRUE
    # The following parameters are needed for the Advanced Replication Option
    job_queue_processes = 2
    # job_queue_processes = 4 #datawarehouse
    # job_queue_interval = 10
    # job_queue_keep_connections = false
    distributed_transactions = 5
    open_links = 4
    # The following parameters are instance-specific parameters that are
    # specified for two instances named clustdb1 and clustdb2
    undo_management=AUTO # For automatic undo management
    # = MANUAL For manual/RBS undo management
    cluster_database= true
    cluster_database_instances=2
    remote_listener=LISTENERS_CLUSTDB
    # First instance specific parameters
    clustdb1.thread=1
    clustdb1.instance_name=clustdb1
    clustdb1.instance_number=1
    clustdb1.local_listener=listener_clustdb1
    clustdb1.remote_login_passwordfile = exclusive
    # Comment out clustdb1.undo_tablespace and uncomment clustdb1.rollback_segments
    # when undo_management=MANUAL
    clustdb1.undo_tablespace = UNDOTBS1
    # clustdb1.rollback_segments = (rbs1_1,rbs1_2)
    # Second instance specific parameters
    clustdb2.thread=2
    clustdb2.instance_name = clustdb2
    clustdb2.instance_number = 2
    clustdb2.local_listener = listener_clustdb2
    clustdb2.remote_login_passwordfile = exclusive
    # Comment out clustdb2.undo_tablespace and uncomment clustdb2.rollback_segments
    # when undo_management=MANUAL
    clustdb2.undo_tablespace = UNDOTBS2
    # clustdb2.rollback_segments = (rbs2_1,rbs2_2)
    ===========================================
    listener.ora
    # listener.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    (PROGRAM = extproc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = us-as1.nti2.org)(PORT = 1521))
    TRACE_LEVEL_LISTENER = USER
    ===============================================
    sqlnet.ora
    # sqlnet.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    # Generated by Oracle configuration tools.
    # This file is actually generated by netca. But if customers choose to
    # install "Software Only", this file wont exist and without the native
    # authentication, they will not be able to connect to the database on NT.
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    =================================================
    tnsnames.ora
    # tnsnames.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    ORCL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = us-as1.nti2.org)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = orcl.us-as1.nti2.org)
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    ============================================================

    Enterprise manager still requires a static service definition in listener.ora and does not rely on dynamic registration.
    From documentation:
    The SID_LIST is required for backward compatibility with Oracle8 or Oracle7 databases, as well as external procedures and heterogeneous services, and some management tools, including Oracle Enterprise Manager.
    Werner

  • Restore using TSPITR Results  Dead lock error

    This is the step is followed but i am getting deadlock error .please give your valuable suggestion .
    Product Used:oracle 11g in linux environmnet
    1)Before taking backup get SCN number for restore.
    Command applied: Select current_scn from v$database;
    2)running Full backup of database
    Command applied:
    configure controlfile autobackup on;
    backup database;
    CROSSCHECK BACKUP;
    exit;
    3)Running level 0 incremental backup
    Command applied:
    BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
    exit;
    3) Running level 1 incremental backup
    Command applied:
    BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
    4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
    Command applied:
    SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
    5)TSPITR Restore command
    Command applied:
    run
    SQL 'ALTER TABLESPACE TEST OFFLINE'
    RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
    SQL 'ALTER TABLESPACE TEST ONLINE';
    and i tried with this option also(the same error i was getting)
    Command applied:
    run
    SQL 'ALTER TABLESPACE TEST OFFLINE';
    SET UNTIL SCN 1912813;
    RESTORE TABLESPACE TEST ;
    RECOVER TABLESPACE TEST UNTIL SCN 1912813 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
    SQL 'ALTER TABLESPACE TEST ONLINE';
    The follwing error i get for above mentioned restore command
    Recovery Manager: Release 11.2.0.1.0 - Production on Tue Aug 17 18:11:18 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: NEW10 (DBID=2860680927)
    RMAN> run
    2> {
    3> SQL 'ALTER TABLESPACE TEST OFFLINE';
    4> RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
    5> SQL 'ALTER TABLESPACE TEST ONLINE';
    6> }
    7>
    using target database control file instead of recovery catalog
    sql statement: ALTER TABLESPACE TEST OFFLINE
    Starting recover at 17-AUG-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=404 device type=DISK
    RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
    List of tablespaces expected to have UNDO segments
    Tablespace SYSTEM
    Tablespace UNDOTBS1
    Creating automatic instance, with SID='BkAq'
    initialization parameters used for automatic instance:
    db_name=NEW10
    db_unique_name=BkAq_tspitr_NEW10
    compatible=11.2.0.0.0
    db_block_size=8192
    db_files=200
    sga_target=280M
    processes=50
    db_create_file_dest=/opt/oracle/base/flash_recovery_area
    log_archive_dest_1='location=/opt/oracle/base/flash_recovery_area'
    #No auxiliary parameter file used
    starting up automatic instance NEW10
    Oracle instance started
    Total System Global Area 292933632 bytes
    Fixed Size 1336092 bytes
    Variable Size 100666596 bytes
    Database Buffers 184549376 bytes
    Redo Buffers 6381568 bytes
    Automatic instance created
    Running TRANSPORT_SET_CHECK on recovery set tablespaces
    TRANSPORT_SET_CHECK completed successfully
    contents of Memory Script:
    # set requested point in time
    set until scn 1791053;
    # restore the controlfile
    restore clone controlfile;
    # mount the controlfile
    sql clone 'alter database mount clone database';
    # archive current online log
    sql 'alter system archive log current';
    # avoid unnecessary autobackups for structural changes during TSPITR
    sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 17-AUG-10
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=59 device type=DISK
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp tag=TAG20100817T142607
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    output file name=/opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl
    Finished restore at 17-AUG-10
    sql statement: alter database mount clone database
    sql statement: alter system archive log current
    sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
    contents of Memory Script:
    # set requested point in time
    set until scn 1791053;
    # set destinations for recovery set and auxiliary set datafiles
    set newname for clone datafile 1 to new;
    set newname for clone datafile 8 to new;
    set newname for clone datafile 3 to new;
    set newname for clone datafile 2 to new;
    set newname for clone datafile 9 to new;
    set newname for clone tempfile 1 to new;
    set newname for datafile 7 to
    "/opt/oracle/base/oradata/NEW10/test01.dbf";
    # switch all tempfiles
    switch clone tempfile all;
    # restore the tablespaces in the recovery set and the auxiliary set
    restore clone datafile 1, 8, 3, 2, 9, 7;
    switch clone datafile all;
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    renamed tempfile 1 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_%u_.tmp in control file
    Starting restore at 17-AUG-10
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00001 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00008 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00003 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00002 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00009 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp tag=TAG20100817T140128
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:02:45
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00007 to /opt/oracle/base/oradata/NEW10/test01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp tag=WEEKLY
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:06:55
    Finished restore at 17-AUG-10
    datafile 1 switched to datafile copy
    input datafile copy RECID=6 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf
    datafile 8 switched to datafile copy
    input datafile copy RECID=7 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf
    datafile 3 switched to datafile copy
    input datafile copy RECID=8 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=9 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=10 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf
    contents of Memory Script:
    # set requested point in time
    set until scn 1791053;
    # online the datafiles restored or switched
    sql clone "alter database datafile 1 online";
    sql clone "alter database datafile 8 online";
    sql clone "alter database datafile 3 online";
    sql clone "alter database datafile 2 online";
    sql clone "alter database datafile 9 online";
    sql clone "alter database datafile 7 online";
    # recover and open resetlogs
    recover clone database tablespace "TEST", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
    alter clone database open resetlogs;
    executing Memory Script
    executing command: SET until clause
    sql statement: alter database datafile 1 online
    sql statement: alter database datafile 8 online
    sql statement: alter database datafile 3 online
    sql statement: alter database datafile 2 online
    sql statement: alter database datafile 9 online
    sql statement: alter database datafile 7 online
    Starting recover at 17-AUG-10
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00007: /opt/oracle/base/oradata/NEW10/test01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp tag=DAILY
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    starting media recovery
    archived log for thread 1 with sequence 39 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc
    archived log for thread 1 with sequence 40 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc
    archived log for thread 1 with sequence 41 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc
    archived log for thread 1 with sequence 42 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc
    archived log for thread 1 with sequence 43 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc thread=1 sequence=39
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc thread=1 sequence=40
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc thread=1 sequence=41
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc thread=1 sequence=42
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc thread=1 sequence=43
    media recovery complete, elapsed time: 00:00:50
    Finished recover at 17-AUG-10
    database opened
    contents of Memory Script:
    # make read only the tablespace that will be exported
    sql clone 'alter tablespace TEST read only';
    # create directory for datapump import
    sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
    /opt/oracle/base/flash_recovery_area''";
    # create directory for datapump export
    sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
    /opt/oracle/base/flash_recovery_area''";
    executing Memory Script
    sql statement: alter tablespace TEST read only
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
    Performing export of metadata...
    EXPDP> Starting "SYS"."TSPITR_EXP_BkAq":
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/GRANT/OWNER_GRANT/OBJECT_GRANT
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/TRIGGER
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
    EXPDP> Master table "SYS"."TSPITR_EXP_BkAq" successfully loaded/unloaded
    EXPDP> ******************************************************************************
    EXPDP> Dump file set for SYS.TSPITR_EXP_BkAq is:
    EXPDP> /opt/oracle/base/flash_recovery_area/tspitr_BkAq_82690.dmp
    EXPDP> ******************************************************************************
    EXPDP> Datafiles required for transportable tablespace TEST:
    EXPDP> /opt/oracle/base/oradata/NEW10/test01.dbf
    EXPDP> Job "SYS"."TSPITR_EXP_BkAq" successfully completed at 18:25:02
    Export completed
    contents of Memory Script:
    # shutdown clone before import
    shutdown clone immediate
    # drop target tablespaces before importing them back
    sql 'drop tablespace TEST including contents keep datafiles';
    executing Memory Script
    database closed
    database dismounted
    Oracle instance shut down
    sql statement: drop tablespace TEST including contents keep datafiles
    Removing automatic instance
    shutting down automatic instance
    target database instance not started
    Automatic instance removed
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_66o1k480_.tmp deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_3_66o1k0mg_.log deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_2_66o1jyt4_.log deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_1_66o1jx3w_.log deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl deleted
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/17/2010 18:25:36
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of sql command on default channel at 08/17/2010 18:25:25
    RMAN-11003: failure during parse/execution of SQL statement: drop tablespace TEST including contents keep datafiles
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00060: deadlock detected while waiting for resource
    Recovery Manager complete.
    please give your valuable suggestion .It should be more helpful for us.
    Edited by: user10750009 on Aug 20, 2010 1:07 AM
    Edited by: user10750009 on Aug 20, 2010 1:15 AM

    I want TSPITR ,during this operation i faced this deadlock error.
    Before that we faced roll backsegment error for that we applied follwing workaround .
    If i applied follwing workaround before every backup and restore .i didn't get any error .all things went successful.
    spool /tmp/Createtest.log
    connect / as sysdba
    REM Perform startup in case we are still down
    ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE;
    SHUT IMMEDIATE;
    STARTUP MOUNT EXCLUSIVE;
    ALTER DATABASE ARCHIVELOG;
    ARCHIVE LOG START;
    ALTER DATABASE OPEN;
    connECT / as sysdba;
    alter system set undo_management = MANUAL scope=spfile;
    shutdown immediate;
    startup;
    Connect / as sysdba;
    DROP TABLE TEST123;
    create table test123 (t1 number, t2 varchar2(10));
    begin
    for i in 1.. 300000 loop
    insert into test values (i,'AAAAAAAAAA');
    end loop;
    end;
    delete test123;
    commit;
    alter system set undo_management = auto scope=spfile;
    shutdown immediate ;
    startup ;
    The above workaround we applied before creating tablespace and datafile ,after that we face some dead lock error while restore TSPITR .Did you need any more information
    Edited by: user10750009 on Aug 20, 2010 1:12 AM

  • PMON (ospid: 8143): terminating the instance due to error 472

    Hi Friends,
    My Environment_
    OS : oel4u5
    Apps Version : R12.1.1
    DB Version : *11.1.0.7*
    When i am trying to start my ebiz 11g database the db started and its automatically going down because of PMON termination.  When am looking in to the alert log files its showing the below ora-600 errors,
    Resuming block recovery (PMON) for file 4 block 180627
    Block recovery from logseq 125, block 70 to scn 10132192035480
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 125 Reading mem 0
    Mem# 0: /ebiz/oracle/db/apps_st/data/log2.dbf
    Block recovery completed at rba 125.281.16, scn 2359.364184220
    Errors in file /ebiz/oracle/db/tech_st/11.1.0/admin/TEST05_erptest05/diag/rdbms/test05/TEST05/trace/TEST05_pmon_8143.trc (incident=49647):
    ORA-00600: internal error code, arguments: [4194], [41], [37], [], [], [], [], [], [], [], [], []
    Errors in file /ebiz/oracle/db/tech_st/11.1.0/admin/TEST05_erptest05/diag/rdbms/test05/TEST05/trace/TEST05_pmon_8143.trc:
    ORA-00600: internal error code, arguments: [4194], [41], [37], [], [], [], [], [], [], [], [], []
    PMON (ospid: 8143): terminating the instance due to error 472
    Instance terminated by PMON, pid = 8143
    Following error which i found in the trace file /ebiz/oracle/db/tech_st/11.1.0/admin/TEST05_erptest05/diag/rdbms/test05/TEST05/trace/TEST05_pmon_8143.trc
    (call) sess: cur 5f1efd10, rec 5f1e5ff0, usr 5f1efd10; depth: 0
    ksudlc FALSE at location: 6
    (k2g table)
    error 472 detected in background process
    ORA-00600: internal error code, arguments: [4194], [41], [37], [], [], [], [], [], [], [], [], []
    *** 2011-11-27 20:19:33.113
    PMON (ospid: 8143): terminating the instance due to error 472
    Kindly Suggest me,
    Thanks
    Athish

    Hi Helios,
    We identified that the error was in undo corruption and We followed the below steps to over come above mention error.
    Steps as followed,
    Step 1:
    SQL> SELECT name,value FROM v$parameter WHERE name IN ('undo_management','undo_tablespace');
    NAME VALUE
    undo_management MANUAL
    undo_tablespace UNDO_TBS
    Step2:
    SQL> select FILE_NAME, TABLESPACE_NAME from dba_data_files where TABLESPACE_NAME like 'UNDO%';
    FILE_NAME                         TABLESPACE_NAME
    /ebiz/oracle/db/apps_st/data/undotbs_02.dbf     UNDO_TBS
    /ebiz/oracle/db/apps_st/data/undotbs_01.dbf     UNDO_TBS
    Step 3: Create a new undo tablespace
    SQL> create UNDO tablespace UNDOTBS datafile '/ebiz/oracle/db/apps_st/data/undotbs01.dbf' size 1024m REUSE AUTOEXTEND ON NEXT 4096K MAXSIZE 1024M;
    Tablespace created.
    Step 4:
    SQL> ALTER SYSTEM SET undo_tablespace = 'UNDOTBS' scope=spfile;
    System altered.
    Step 5: set old undo tablespace offine mode and drop
    SQL> ALTER TABLESPACE UNDO_TBS offline;
    Tablespace altered.
    SQL> drop tablespace UNDO_TBS including contents and datafiles;
    Tablespace dropped.
    Step 6:
    Rebounced the db services
    Step 7: Changed the undo management parameter to AUTO
    SQL> alter system set undo_management='AUTO' scope=spfile;
    System altered.
    SQL> SELECT name,value FROM v$parameter WHERE name IN ('undo_management','undo_tablespace');
    NAME VALUE
    undo_management AUTO
    undo_tablespace UNDOTBS
    Now the database is up and running with no issue and we cant find any ora error in the alert log file,
    ThaNks
    Athish

  • Oracle 9i - Database closed while normal use

    Hi all,
    I have big problem with my 9i database. One of my sid get closed (sort of shutdown) while we're using it. I have no trace in alert, and no trace dumped.
    I don't what to do ? I have tried new allocation of space memory... Dont' work.
    It shutdown (no trace of this shutdown ot any error in alert) and I just restart it and it go ok for a while. When it get closed, there's no special things running on it, just normal activity.
    Do you have any idea on what I must do to know a little bit more from where the problem is ?
    Thanks

    Nothing interesting on the events on the server. That's my problem.
    It's a local storage. No bay. just raid 0 + 1
    Here is a part of my alert
    ARC1: Evaluating archive log 2 thread 1 sequence 16918
    ARC1: Beginning to archive log 2 thread 1 sequence 16918
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16918.ARC'
    Tue Dec 12 09:58:53 2006
    ARC1: Completed archiving log 2 thread 1 sequence 16918
    Tue Dec 12 10:16:20 2006
    Thread 1 advanced to log sequence 16920
    Tue Dec 12 10:16:20 2006
    Current log# 1 seq# 16920 mem# 0: E:\ANTI\REDO\REDO01.LOG
    Tue Dec 12 10:16:21 2006
    ARC0: Evaluating archive log 4 thread 1 sequence 16919
    Tue Dec 12 10:16:21 2006
    ARC0: Beginning to archive log 4 thread 1 sequence 16919
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16919.ARC'
    Tue Dec 12 10:16:31 2006
    ARC0: Completed archiving log 4 thread 1 sequence 16919
    Tue Dec 12 10:17:12 2006
    Thread 1 advanced to log sequence 16921
    Current log# 3 seq# 16921 mem# 0: E:\ANTI\REDO\REDO03.LOG
    Tue Dec 12 10:17:12 2006
    ARC1: Evaluating archive log 1 thread 1 sequence 16920
    ARC1: Beginning to archive log 1 thread 1 sequence 16920
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16920.ARC'
    ARC1: Completed archiving log 1 thread 1 sequence 16920
    Tue Dec 12 10:18:10 2006
    Thread 1 advanced to log sequence 16922
    Current log# 2 seq# 16922 mem# 0: E:\ANTI\REDO\REDO02.LOG
    Tue Dec 12 10:18:10 2006
    ARC0: Evaluating archive log 3 thread 1 sequence 16921
    ARC0: Beginning to archive log 3 thread 1 sequence 16921
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16921.ARC'
    ARC0: Completed archiving log 3 thread 1 sequence 16921
    Tue Dec 12 10:33:38 2006
    Thread 1 advanced to log sequence 16923
    Tue Dec 12 10:33:38 2006
    Current log# 4 seq# 16923 mem# 0: E:\ANTI\REDO\REDO04.LOG
    Tue Dec 12 10:33:39 2006
    ARC1: Evaluating archive log 2 thread 1 sequence 16922
    Tue Dec 12 10:33:39 2006
    ARC1: Beginning to archive log 2 thread 1 sequence 16922
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16922.ARC'
    ARC1: Completed archiving log 2 thread 1 sequence 16922
    Tue Dec 12 10:46:37 2006
    Thread 1 advanced to log sequence 16924
    Current log# 1 seq# 16924 mem# 0: E:\ANTI\REDO\REDO01.LOG
    Tue Dec 12 10:46:37 2006
    ARC0: Evaluating archive log 4 thread 1 sequence 16923
    ARC0: Beginning to archive log 4 thread 1 sequence 16923
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16923.ARC'
    Tue Dec 12 10:46:47 2006
    ARC0: Completed archiving log 4 thread 1 sequence 16923
    Tue Dec 12 10:47:40 2006
    Thread 1 advanced to log sequence 16925
    Current log# 3 seq# 16925 mem# 0: E:\ANTI\REDO\REDO03.LOG
    Tue Dec 12 10:47:40 2006
    ARC1: Evaluating archive log 1 thread 1 sequence 16924
    ARC1: Beginning to archive log 1 thread 1 sequence 16924
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16924.ARC'
    Tue Dec 12 10:47:50 2006
    ARC1: Completed archiving log 1 thread 1 sequence 16924
    Tue Dec 12 10:48:23 2006
    Thread 1 advanced to log sequence 16926
    Current log# 2 seq# 16926 mem# 0: E:\ANTI\REDO\REDO02.LOG
    Tue Dec 12 10:48:23 2006
    ARC0: Evaluating archive log 3 thread 1 sequence 16925
    ARC0: Beginning to archive log 3 thread 1 sequence 16925
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16925.ARC'
    Tue Dec 12 10:48:33 2006
    ARC0: Completed archiving log 3 thread 1 sequence 16925
    Tue Dec 12 10:48:42 2006
    Thread 1 advanced to log sequence 16927
    Current log# 4 seq# 16927 mem# 0: E:\ANTI\REDO\REDO04.LOG
    Tue Dec 12 10:48:42 2006
    ARC1: Evaluating archive log 2 thread 1 sequence 16926
    ARC1: Beginning to archive log 2 thread 1 sequence 16926
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16926.ARC'
    Tue Dec 12 10:48:52 2006
    ARC1: Completed archiving log 2 thread 1 sequence 16926
    Tue Dec 12 10:49:00 2006
    Thread 1 advanced to log sequence 16928
    Current log# 1 seq# 16928 mem# 0: E:\ANTI\REDO\REDO01.LOG
    Tue Dec 12 10:49:00 2006
    ARC0: Evaluating archive log 4 thread 1 sequence 16927
    ARC0: Beginning to archive log 4 thread 1 sequence 16927
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16927.ARC'
    Tue Dec 12 10:49:11 2006
    ARC0: Completed archiving log 4 thread 1 sequence 16927
    Tue Dec 12 10:49:21 2006
    Thread 1 advanced to log sequence 16929
    Current log# 3 seq# 16929 mem# 0: E:\ANTI\REDO\REDO03.LOG
    Tue Dec 12 10:49:21 2006
    ARC1: Evaluating archive log 1 thread 1 sequence 16928
    ARC1: Beginning to archive log 1 thread 1 sequence 16928
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16928.ARC'
    Tue Dec 12 10:49:32 2006
    ARC1: Completed archiving log 1 thread 1 sequence 16928
    Tue Dec 12 10:49:51 2006
    Thread 1 advanced to log sequence 16930
    Current log# 2 seq# 16930 mem# 0: E:\ANTI\REDO\REDO02.LOG
    Tue Dec 12 10:49:51 2006
    ARC0: Evaluating archive log 3 thread 1 sequence 16929
    ARC0: Beginning to archive log 3 thread 1 sequence 16929
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16929.ARC'
    Tue Dec 12 10:50:01 2006
    ARC0: Completed archiving log 3 thread 1 sequence 16929
    Tue Dec 12 10:56:17 2006
    Thread 1 advanced to log sequence 16931
    Current log# 4 seq# 16931 mem# 0: E:\ANTI\REDO\REDO04.LOG
    Tue Dec 12 10:56:17 2006
    ARC1: Evaluating archive log 2 thread 1 sequence 16930
    ARC1: Beginning to archive log 2 thread 1 sequence 16930
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16930.ARC'
    Tue Dec 12 10:56:27 2006
    ARC1: Completed archiving log 2 thread 1 sequence 16930
    Tue Dec 12 10:56:36 2006
    Thread 1 advanced to log sequence 16932
    Current log# 1 seq# 16932 mem# 0: E:\ANTI\REDO\REDO01.LOG
    Tue Dec 12 10:56:36 2006
    ARC0: Evaluating archive log 4 thread 1 sequence 16931
    ARC0: Beginning to archive log 4 thread 1 sequence 16931
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16931.ARC'
    Tue Dec 12 10:56:46 2006
    ARC0: Completed archiving log 4 thread 1 sequence 16931
    Tue Dec 12 10:56:51 2006
    Thread 1 advanced to log sequence 16933
    Current log# 3 seq# 16933 mem# 0: E:\ANTI\REDO\REDO03.LOG
    Tue Dec 12 10:56:51 2006
    ARC1: Evaluating archive log 1 thread 1 sequence 16932
    ARC1: Beginning to archive log 1 thread 1 sequence 16932
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16932.ARC'
    Tue Dec 12 10:57:01 2006
    ARC1: Completed archiving log 1 thread 1 sequence 16932
    Tue Dec 12 11:11:02 2006
    Thread 1 advanced to log sequence 16934
    Tue Dec 12 11:11:02 2006
    Current log# 2 seq# 16934 mem# 0: E:\ANTI\REDO\REDO02.LOG
    Tue Dec 12 11:11:03 2006
    ARC0: Evaluating archive log 3 thread 1 sequence 16933
    Tue Dec 12 11:11:03 2006
    ARC0: Beginning to archive log 3 thread 1 sequence 16933
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16933.ARC'
    ARC0: Completed archiving log 3 thread 1 sequence 16933
    Tue Dec 12 11:47:35 2006
    Thread 1 advanced to log sequence 16935
    Tue Dec 12 11:47:35 2006
    Current log# 4 seq# 16935 mem# 0: E:\ANTI\REDO\REDO04.LOG
    Tue Dec 12 11:47:36 2006
    ARC1: Evaluating archive log 2 thread 1 sequence 16934
    Tue Dec 12 11:47:36 2006
    ARC1: Beginning to archive log 2 thread 1 sequence 16934
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16934.ARC'
    Tue Dec 12 11:47:46 2006
    ARC1: Completed archiving log 2 thread 1 sequence 16934
    Tue Dec 12 12:34:33 2006
    Thread 1 advanced to log sequence 16936
    Current log# 1 seq# 16936 mem# 0: E:\ANTI\REDO\REDO01.LOG
    Tue Dec 12 12:34:33 2006
    ARC0: Evaluating archive log 4 thread 1 sequence 16935
    ARC0: Beginning to archive log 4 thread 1 sequence 16935
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16935.ARC'
    Tue Dec 12 12:34:43 2006
    ARC0: Completed archiving log 4 thread 1 sequence 16935
    Tue Dec 12 13:33:55 2006
    Thread 1 advanced to log sequence 16937
    Tue Dec 12 13:33:55 2006
    Current log# 3 seq# 16937 mem# 0: E:\ANTI\REDO\REDO03.LOG
    Tue Dec 12 13:33:56 2006
    ARC1: Evaluating archive log 1 thread 1 sequence 16936
    Tue Dec 12 13:33:56 2006
    ARC1: Beginning to archive log 1 thread 1 sequence 16936
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16936.ARC'
    Tue Dec 12 13:34:06 2006
    ARC1: Completed archiving log 1 thread 1 sequence 16936
    Tue Dec 12 14:23:58 2006
    Thread 1 advanced to log sequence 16938
    Tue Dec 12 14:23:58 2006
    Current log# 2 seq# 16938 mem# 0: E:\ANTI\REDO\REDO02.LOG
    Tue Dec 12 14:23:59 2006
    ARC0: Evaluating archive log 3 thread 1 sequence 16937
    Tue Dec 12 14:23:59 2006
    ARC0: Beginning to archive log 3 thread 1 sequence 16937
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16937.ARC'
    ARC0: Completed archiving log 3 thread 1 sequence 16937
    Tue Dec 12 15:01:00 2006
    Thread 1 advanced to log sequence 16939
    Tue Dec 12 15:01:00 2006
    Current log# 4 seq# 16939 mem# 0: E:\ANTI\REDO\REDO04.LOG
    Tue Dec 12 15:01:01 2006
    ARC1: Evaluating archive log 2 thread 1 sequence 16938
    Tue Dec 12 15:01:01 2006
    ARC1: Beginning to archive log 2 thread 1 sequence 16938
    Creating archive destination LOG_ARCHIVE_DEST_1: 'G:\ANTI\ARCHIVE\A16938.ARC'
    Tue Dec 12 15:01:11 2006
    ARC1: Completed archiving log 2 thread 1 sequence 16938
    Dump file d:\oracle\admin\anti\bdump\alert_anti.log
    Tue Dec 12 15:09:43 2006
    ORACLE V9.2.0.4.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.2 Service Pack 1, CPU type 586
    Tue Dec 12 15:09:43 2006
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.4.0.
    System parameters with non-default values:
    processes = 300
    timed_statistics = FALSE
    shared_pool_size = 402653184
    sga_max_size = 1418275328
    shared_pool_reserved_size= 20132659
    large_pool_size = 134217728
    java_pool_size = 0
    pre_page_sga = FALSE
    trace_enabled = FALSE
    nls_date_format = DD/MON/RR
    control_files = D:\ORACLE\ORADATA\ANTI\control01.ctl, D:\ORACLE\ORADATA\ANTI\control02.ctl, D:\ORACLE\ORADATA\ANTI\control03.ctl, I:\ORACLE\ORADATA\ANTI\control04.ctl, I:\ORACLE\ORADATA\ANTI\control05.ctl, I:\ORACLE\ORADATA\ANTI\control06.ctl
    db_block_size = 8192
    db_cache_size = 822083584
    compatible = 9.2.0.0.0
    log_archive_start = TRUE
    log_archive_dest_1 = location=G:\anti\archive
    log_archive_dest_2 =
    log_archive_dest_state_2 = defer
    log_archive_format = A%S.ARC
    log_buffer = 32768
    db_file_multiblock_read_count= 16
    fast_start_mttr_target = 300
    undo_management = MANUAL
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    instance_name = anti
    cursor_space_for_time = TRUE
    session_cached_cursors = 50
    utl_file_dir = *
    job_queue_processes = 10
    hash_join_enabled = TRUE
    hash_area_size = 1048576
    background_dump_dest = D:\Oracle\admin\anti\bdump
    user_dump_dest = D:\Oracle\admin\anti\udump
    core_dump_dest = D:\Oracle\admin\anti\cdump
    sort_area_size = 524288
    db_name = anti
    open_cursors = 300
    star_transformation_enabled= FALSE
    query_rewrite_enabled = FALSE
    pga_aggregate_target = 209715200
    statistics_level = TYPICAL
    aq_tm_processes = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Tue Dec 12 15:09:46 2006

  • Managing Undo tablespace & roll back segments

    Hi,
    I have oracle 9.1 version and have created 5g undo tablespace apart from 20m rbs tablespace for 15 rollback segments. But it is seen that whenever i give UNDO_MANAGEMENT=AUTO then rollback segments are created using undo tablespace and not allowing rollback segment in rbs tablespace ONLINE. In the reverse happens whenever I give UNDO_MANAGEMENT=MANUAL , the rollback segments in the rbs tablespace gets focus and roll back segments in the Undo tablespace goes offline. Is there anything that I can do so that both undo tablespace and redo segments in the rbs tablespace gets working together so as to minimize the undo contention. Moreover, any query given takes long time when select query given with || in the subquery.
    Please suggest the tuning need to do?

    brain_heart wrote:
    Hi,
    I have oracle 9.1 version and have created 5g undo tablespace apart from 20m rbs tablespace for 15 rollback segments. But it is seen that whenever i give UNDO_MANAGEMENT=AUTO then rollback segments are created using undo tablespace and not allowing rollback segment in rbs tablespace ONLINE. In the reverse happens whenever I give UNDO_MANAGEMENT=MANUAL , the rollback segments in the rbs tablespace gets focus and roll back segments in the Undo tablespace goes offline. Is there anything that I can do so that both undo tablespace and redo segments in the rbs tablespace gets working together so as to minimize the undo contention.No that's the way it would work, you can either use the automatic undo or the manual one.not both. And its better to stick with the automatic one IMHO. Have a read of this link to understand more about undo.
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96521/undo.htm#8888
    HTH
    Aman....

  • To change manul to auto undo management in 9i

    Hi
    My production database on manul undo management means (RBS) . I want to change this on auto mode Please Help me what steps i follow to do this
    DB 9.2 and OS AIX 5.2
    Thanks

    SQL> alter system set undo_management=manual scope=spfile;
    System altered.
    SQL> shutdown immediate;
    SQL> startup
    SQL> show parameter undo
    NAME TYPE VALUE
    undo_management string MANUAL
    undo_retention integer 1800
    undo_tablespace string UNDONEW
    SQL>
    do this same for auto....
    regards

  • Ora 01078 error

    Hello Experts,
    I am getting the following error while try to start database. In the respective directory I am not able to find initorrcl.ora file.
    Please help. Its urgent fro my project/job.
    Error:
    startup nomount
    ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file \APP\US31998\PRODUCT\11.1.0\DB_1\DATABASE\INITORCL.ORA'

    The init.ora file actullay located in the *\app\US31998\product\11.1.0\db_1\srvm\admin* directory.
    I copied the same file and putting into the *\app\US31998\product\11.1.0\db_1\database* directory
    After I copied its saying the following errer while runnning the startup nomount command
    startup nomount
    ORA-01078: failure in processing system parameters
    ORA-00439: feature not enabled: Real Application Clusters
    -----------------------------------init.ora file---------------------------------------------------------------------------------------
    # $Header: init.ora 25-jul-01.18:03:38 rajayar Exp $
    # Copyright (c) 1991, 2001, Oracle Corporation. All rights reserved. */
    # Example INIT.ORA file
    # This file is provided by Oracle Corporation to help you customize
    # your RDBMS installation for your site. Important system parameters
    # are discussed, and example settings given.
    # Some parameter settings are generic to any size installation.
    # For parameters that require different values in different size
    # installations, three scenarios have been provided: SMALL, MEDIUM
    # and LARGE. Any parameter that needs to be tuned according to
    # installation size will have three settings, each one commented
    # according to installation size.
    # Use the following table to approximate the SGA size needed for the
    # three scenarious provided in this file:
    # -------Installation/Database Size------
    # SMALL MEDIUM LARGE
    # Block 2K 4500K 6800K 17000K
    # Size 4K 5500K 8800K 21000K
    # To set up a database that multiple instances will be using, use the
    # same file for all instance. Place all instance-specific parameters
    # at the end of the file using the <sid>.<parameter_name> = <value> syntax.
    # This way, when you change a public
    # parameter, it will automatically change on all instances. This is
    # necessary, since all instances must run with the same value for many
    # parameters. For example, if you choose to use private rollback segments,
    # these must be specified differently for each instance, but since all gc_*
    # parameters must be the same on all instances, they should be in one file.
    # INSTRUCTIONS: Edit this file and the other INIT files it calls for
    # your site, either by using the values provided here or by providing
    # your own.
    # replace "clustdb" with your database name
    db_name = clustdb
    compatible=9.0.0
    db_files = 1024 # INITIAL
    #INITIAL
    #db_files=80
    #SMALL
    #DB_files=400
    #MEDIUM
    #db_files=1000
    #LARGE
    control_files = ("\\.\clustdb_control1", "\\.\clustdb_control2")
    db_file_multiblock_read_count = 8 # INITIAL
    # db_file_multiblock_read_count = 8
    #SMALL
    #db_file_multiblock_read_count = 16
    #MEDIUM
    #db_file_multiblock_read_count = 32
    #LARGE
    #Datawarehouse
    db_block_size=8192
    # Transaction processing
    # db_block_size=4096
    open_cursors=300
    #Transaction processing
    #sort_area_size=524288
    #Datawarehouse
    sort_area_size=1048576
    large_pool_size=1048576 #Transaction processing, Datawarehouse
    db_cache_size=50331648 #Datawarehouse, Transaction processing
    java_pool_size=67108864 #Datawarehouse, Transaction processing
    # db_block_buffers = 200 # INITIAL
    # db_block_buffers=100 #SMALL
    # db_block_buffers =550 # MEDIUM
    # db_block_buffers=3200 #LARGE
    #shared_pool_size = 52428800 # INITIAL
    shared_pool_size = 67108864 # datewarehouse, transaction processing
    log_checkpoint_interval = 10000
    processes = 59 # INITIAL
    # processes = 50
    #SMALL
    #processes = 100
    #MEDIUM
    #processes = 200
    #LARGE
    parallel_max_servers = 5
    #SMALL
    # parallel_max_servers = 4 x (number of CPUs)
    #MEDIUM
    # parallel_max_servers = 4 x (number of CPUs)
    # LARGE
    log_buffer = 8192 # INITIAL
    #log_buffer = 8192
    #SMALL
    #log_buffer = 32768
    #MEDIUM
    #log_buffer = 163840
    #LARGE
    # audit_trail = true # if you want auditing
    # timed_statistics = true # if you want timed statistics
    max_dump_file_size = 10240 # limit trace file size to 10 K each
    # Uncommenting the line below will cause automatic archiving if archiving has
    # been enabled using ALTER DATABASE ARCHIVELOG.
    # log_archive_start = true
    # log_archive_dest = %ORACLE_HOME%/admin/clustdb/arch
    # log_archive_format = "%%ORACLE_SID%%T%TS%S.ARC"
    # If using private rollback segments, place lines of the following
    # form at the end of this file:
    # <sid>.rollback_segments = (name1, name2)
    # If using public rollback segments, define how many
    # rollback segments each instance will pick up, using the formula
    # # of rollback segments = transactions / transactions_per_rollback_segment
    # In this example each instance will grab 40/10 = 4:
    # transactions = 40
    # transactions_per_rollback_segment = 10
    # Global Naming -- enforce that a dblink has same name as the db it connects to
    global_names = TRUE
    # Edit and uncomment the following line to provide the suffix that will be
    # appended to the db_name parameter (separated with a dot) and stored as the
    # global database name when a database is created. If your site uses
    # Internet Domain names for e-mail, then the part of your e-mail address after
    # the '@' is a good candidate for this parameter value.
    # db_domain = us.acme.com # global database name is db_name.db_domain
    # Uncomment the following line if you wish to enable the Oracle Trace product
    # to trace server activity. This enables scheduling of server collections
    # from the Oracle Enterprise Manager Console.
    # Also, if the oracle_trace_collection_name parameter is non-null,
    # every session will write to the named collection, as well as enabling you
    # to schedule future collections from the console.
    # oracle_trace_enable = TRUE
    # define directories to store trace and alert files
    background_dump_dest=%ORACLE_HOME%/admin/clustdb/bdump
    user_dump_dest=%ORACLE_HOME%/admin/clustdb/
    db_block_size = 4096
    remote_login_passwordfile = exclusive
    # text_enable = TRUE
    # The following parameters are needed for the Advanced Replication Option
    job_queue_processes = 2
    # job_queue_processes = 4 #datawarehouse
    # job_queue_interval = 10
    # job_queue_keep_connections = false
    distributed_transactions = 5
    open_links = 4
    # The following parameters are instance-specific parameters that are
    # specified for two instances named clustdb1 and clustdb2
    undo_management=AUTO # For automatic undo management
    # = MANUAL For manual/RBS undo management
    cluster_database= true
    cluster_database_instances=2
    remote_listener=LISTENERS_CLUSTDB
    # First instance specific parameters
    clustdb1.thread=1
    clustdb1.instance_name=clustdb1
    clustdb1.instance_number=1
    clustdb1.local_listener=listener_clustdb1
    clustdb1.remote_login_passwordfile = exclusive
    # Comment out clustdb1.undo_tablespace and uncomment clustdb1.rollback_segments
    # when undo_management=MANUAL
    clustdb1.undo_tablespace = UNDOTBS1
    # clustdb1.rollback_segments = (rbs1_1,rbs1_2)
    # Second instance specific parameters
    clustdb2.thread=2
    clustdb2.instance_name = clustdb2
    clustdb2.instance_number = 2
    clustdb2.local_listener = listener_clustdb2
    clustdb2.remote_login_passwordfile = exclusive
    # Comment out clustdb2.undo_tablespace and uncomment clustdb2.rollback_segments
    # when undo_management=MANUAL
    clustdb2.undo_tablespace = UNDOTBS2
    # clustdb2.rollback_segments = (rbs2_1,rbs2_2)
    -----------------------------------init.ora file---------------------------------------------------------------------------------------

  • Recovery lost  undo tablespace and Redo log

    Recovery undo tablespace
    [email protected]> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.e
    [email protected]> exit
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    [ora920@tkyte-pc-isdn ora920]$ ls
    control01.ctl cwmlite01.dbf indx01.dbf redo02.log redo0B.log temp01.dbf
    users01.dbf
    control02.ctl drsys01.dbf odm01.dbf redo03.log redo0C.log tools01.dbf
    xdb01.dbf
    control03.ctl example01.dbf redo01.log redo0A.log system01.dbf undotbs01.dbf
    [ora920@tkyte-pc-isdn ora920]$ mv undotbs01.dbf undotbs01.dbf.xxx
    [ora920@tkyte-pc-isdn ora920]$ sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Sat Sep 28 08:33:29 2002
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    idle> connect / as sysdba
    Connected to an idle instance.
    idle> startup
    ORACLE instance started.
    Total System Global Area 143725064 bytes
    Fixed Size 451080 bytes
    Variable Size 109051904 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf'
    idle> show parameter undo
    NAME TYPE VALUE
    undo_management string AUTO
    undo_retention integer 10800
    undo_suppress_errors boolean FALSE
    undo_tablespace string UNDOTBS1
    idle> alter system set undo_management = manual scope=spfile;
    System altered.
    Note: disabling the undo tablespace here, this'll let us go back to "rollback segments"
    and we'll use the system RBS to get back on our feet
    idle> shutdown
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    idle> exit
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    [ora920@tkyte-pc-isdn ora920]$ !sql
    sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Sat Sep 28 08:35:34 2002
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    idle> connect / as sysdba;
    Connected to an idle instance.
    idle> startup
    ORACLE instance started.
    Total System Global Area 143725064 bytes
    Fixed Size 451080 bytes
    Variable Size 109051904 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf'
    Note: we still have to get rid of that thing..
    idle> alter database datafile '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf'
    2 offline drop;
    Database altered.
    idle> alter database open;
    Database altered.
    idle> drop tablespace undotbs1;
    Tablespace dropped.
    idle> create UNDO tablespace undotbs1
    2 datafile '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf' size 25m
    3 autoextend on next 1m maxsize 1024m;
    Tablespace created.
    idle> alter system set undo_management = auto scope=spfile;
    System altered.
    Now, we've put the undo tablespace "back" by creating a new one. Just bounce...
    idle> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    idle> exit
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    [ora920@tkyte-pc-isdn ora920]$ !sql
    sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Sat Sep 28 08:40:51 2002
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    idle> connect / as sysdba;
    Connected to an idle instance.
    idle> startup
    ORACLE instance started.
    Total System Global Area 143725064 bytes
    Fixed Size 451080 bytes
    Variable Size 109051904 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    Database opened.
    idle> show parameter undo
    NAME TYPE VALUE
    undo_management string AUTO
    undo_retention integer 10800
    undo_suppress_errors boolean FALSE
    undo_tablespace string UNDOTBS1
    idle>
    and we are right back where we started from
    RECOVERY REDO TABLESPACE
    STARTUP MOUNT;
    RESTORE DATABASE;
    RECOVER DATABASE UNTIL SEQUENCE $v_seq THREAD 1;
    ALTER DATABASE OPEN RESETLOGS;

    [email protected] wrote:
    just ignore first one like title
    Alter database open resetlog is not necessary to open database ?
    Regards
    kmphttp://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/osrecov.htm#i1007426
    About Opening with the RESETLOGS Option
    The RESETLOGS option is always required after incomplete media recovery or recovery using a backup control file.
    You did not do an incomplete media recovery nor a recovery using a backup control file.

  • Data Guard parameter

    HI There
    I have recently configure Data guard with Database 10g (10.2.0.4-64 bits) on Windows 2007 server.
    My Data Gurad Configuration show Success status with 2 databases on same (or local) location.
    My questions are
    1-When I query SHOW PARAMETER LOG ARCH
    DG_CONFIG(PRMDB)
    ONLY 1 (PRIMARY DATABASE IS DISPLAYED ONLY NOT 2 DTATABASES
    e.g. DG_CONFIG(PRMDB, STLDB)
    2- How to check the log applied interval or time (either transaction by transaction, timing etc)
    Kind Regards
    Thunder2777

    THANKS FOR REPLY
    BOTH TNSNAMES.ORA AND LISTENER.ORA IN SAME DIRECTORY
    C:\oracle\product\10.2.0\db_1\NETWORK\ADMIN
    TNSNAMES.ORA
    # tnsnames.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    PRMDB =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = CV-SERVER)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = PRMDB)
    STLDB =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = CV-SERVER)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = STLDB)
    LISTENER.ORA
    # listener.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = STLDB)
    (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
    # PRIMARY DATABASE SPFILE
    SPFILEPRMDB.ORA
    prmdb.__db_cache_size=922746880
    prmdb.__java_pool_size=16777216
    prmdb.__large_pool_size=16777216
    prmdb.__shared_pool_size=285212672
    prmdb.__streams_pool_size=0
    *.archive_lag_target=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\PRMDB\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\PRMDB\bdump'
    *.compatible='10.2.0.3.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\PRMDB\control01.ctl','C:\oracle\product\10.2.0\oradata\PRMDB\control02.ctl','C:\oracle\product\10.2.0\oradata\PRMDB\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\PRMDB\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='PRMDB'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dg_broker_start=TRUE
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=PRMDBXDB)'
    *.job_queue_processes=10
    *.log_archive_config='dg_config=(stldb)'
    *.log_archive_dest_1='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=CV-SERVER)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=stldb_XPT)(INSTANCE_NAME=stldb)(SERVER=dedicated)))"',' LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="stldb" register net_timeout=180 valid_for=(online_logfile,primary_role)'
    *.log_archive_dest_state_1='ENABLE'
    prmdb.log_archive_format='ARC%S_%R.%T'
    *.log_archive_max_processes=2
    *.log_archive_min_succeed_dest=1
    prmdb.log_archive_trace=0
    *.open_cursors=300
    *.pga_aggregate_target=417333248
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=1253048320
    prmdb.standby_archive_dest=''
    *.standby_file_management='MANUAL'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\PRMDB\udump'
    # STANDBY DATABASE INITSTLDB
    INITSTLDB.ORA
    STLDB.__db_cache_size=922746880
    STLDB.__java_pool_size=16777216
    STLDB.__large_pool_size=16777216
    STLDB.__shared_pool_size=285212672
    STLDB.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\STLDB\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\STLDB\bdump'
    *.compatible='10.2.0.3.0'
    *.control_files='D:\ORACLE\ORADATA\STLDB\CONTROLFILE\control01.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\STLDB\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='PRMDB'
    *.db_unique_name='STLDB'
    *.db_recovery_file_dest='D:\oracle\FRA'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=STLDBXDB)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=STLDB'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=417333248
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=1253048320
    *.undo_management='MANUAL'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\STLDB\udump'
    THANKS

  • 9i in 10g

    I'm attempting to make a 9i database from scratch running within 10g, has anyone ever tried this before. I played with the compatibility mode however the database creation wizard always gives me the error "must be 10.0 or above". Any hints.
    Thanks in advance...

    I take it you are trying to create a 9i-compatible database with a 10g software installation.
    Nothing like making life difficult for yourself, is there?!
    Anyway, it's perfectly do-able. You just have to be aware that the SYSAUX tablespace is a 10g invention, as is the Flash Recovery Area and the Enterprise Manager DB Console. So, you'd better be prepared to unselect all those things (which means doing a custom database creation in DBCA), because if you ask for any of them to be included, then it will certainly demand that the compatible parameter be set to 10.0.0.0+
    A simpler alternative might be as follows.
    Create a text file init.ora in ORACLE_HOME/dbs or ORACLE_HOME\database depending on your OS, containing the following parameters:
    control_files=c:\control01.ctl
    db_block_size=8192
    compatible=9.2.0.1
    undo_management=manual
    shared_pool_size=64M
    db_cache_size=64M
    db_name=test9
    db_create_file_dest=c:\Obviously, you adjust paths and sizes to suit. I called mine INITTEST9.ORA. You need to call it INITXXXX.ora, where XXXX is what you want your eventual database name to be.
    Next, create a password file:
    orapwd file=C:\oracle\product\10.2.0\db_1\database\pwdtest9.ora entries=5 password=pwordAgain, that's for Windows (it really helps to know your OS when you ask for help, you know!) and if you're not using Windows, you'll have to adjust paths and file names to suit. The thing needs to be created in ORACLE_HOME/dbs with a default name of orapwXXXX.ora, where XXXX is your ORACLE_SID (in my case, test9)
    If you're Windows, you'll also need a service:
    oradim -NEW -SID test9 -STARTMODE autoSkip that bit completely if you're not on Windows
    Now you simply do:
    set ORACLE_SID=TEST9 (on Linux, export ORACLE_SID=test9)
    sqlplus sys/pword as sysdba
    startup nomount
    create database;And at that point, you have a very basic 9i database created with 10g software (so anyone saying it can't be done needs to re-consider!)
    You'll need to add temporary tablespace and undo tablespace, but those are just details. The main point is to get a prior-compatible, fully-functioning database.

  • Undo tablespace currupt and no clean backup

    Hello,
    We are facing critical problem with database. We have not any clean backup and database in no archive log mode. Suddenly database is shutdown and when we are trying to open database it is giving error:-
    ORA-01172: recovery of thread 1 stuck at block 350230 of file 3
    ORA-01151: use media recovery to recover block, restore backup if needed
    File 3 is Undo file.
    Is there any way to open database?
    Thanks in advance and please reply us ASAP.

    1) First, follow Howardjr recomendations and allways do a backup first.
    2) Open a SR with Metalink to help with your problem
    3) If you want to try something here are some options, but never skip the point 1 previously explained.
    Well, you have two possible scenarios, one supported other unsupported.
    This is an inconsistency issue..
    Solution
    ============
    *1]Supported Solution:*
    Restore-Incomplete recovery the DB from backup or rebuild the DB using an export dump.
    *2]Internal (Not-supported) Solution:*
    Update undo$ to change the status$ = 1 (undo segment is dropped) for the corrupted undo segment.
    Caution:
    This is NOT a supported solution. Therefore ensure that a full database cold backup is taken bbefore doing this data-dictionary patching.
    Steps to do the patching:
    1) First ensure that a full database backup is taken.
    2) Modify/add the following parameters in initSID.ora:
    undo_management=manual
    job_queue_processes =0
    aq_tm_processes=0
    systemtrig_enabled=false
    3) Shutdown
    4) Startup restrict pfile
    5) set transaction use rollback segment system;
    if set transaction above fails, then not to proceed further.
    6) Update undo$ to change the status$ = 1 (undo segment is dropped) for
    the corrupt undo segment.
    update undo$ set status$ = 1
    where us# = <'undo segment id'>
    and ts#=<'tablespace id'>
    and file#=<'file id'>
    and block# = <'block id'>
    and status$=2;
    or
    update undo$ set status$ = 1
    where name = <'corrupt undo segment name'>
    and status$=2;
    This will update only 1 row. Rollback the update if more than 1 row is updated.
    7) Commit;
    8) Shutdown abort
    9) Set back in init.ora parameters modified in Step 2.
    Startup restrict
    10) Drop the corrupt undo tablespace using command:
    drop tablespace <corrupt undo tablespace name> including contents;
    11) Create new undo tablespace.
    In initSID.ora, set undo_management=auto, undo_tablespace=<'new undo tablespace name'>
    Restart the instance.
    12) Take a backup.
    *Parameter offlinerollback_segments is not useful:*
    Trying to drop the corrupt undo segment or the undo tablespace by setting parameters undo management=manual and offline_rollback_segments in initSID.ora will fails with error: ORA-00600 [ktssdrp1].
    To see the information about the corrupt block use this query:
    select us#, name, ts#, file#, block#,status$ from undo$
    where (ts#, file#, block#) not in
    (select ts#, file#, block# from seg$ where type# in (1,10)) and status$ > 1;I had the same problem some time ago, and the unsupported solution works great, but never try it without a full backup first.
    Cheers,
    Francisco Munoz Alvarez
    http://oraclenz.wordpress.com
    Edited by: F.Munoz Alvarez on Nov 30, 2012 11:03 AM

Maybe you are looking for