Database is in which mode

Hi,
give me query to check the database is in which mode?.archivelog mode or not.
Thanks

user9121291 wrote:
Hi,
give me query to check the database is in which mode?.archivelog mode or not.
Thanks
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     291
Next log sequence to archive   293
Current log sequence           293
SQL>HTH
Aman....

Similar Messages

  • How to open a "manual" Physical standby database in read/write mode

    Hi,
    I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
    I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
    The standby database is started this way :
    startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
    alter database mount standby database;
    Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
    The thing is, if I shutdown immediate the database, then do just startup :
    shutdown immediate;
    startup;
    The database opens with no error messages, but is still in read-only mode...
    I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
    Thanks,
    Mat

    Hello,
    There're features which allows you to open a Standby database in Read/Write mode but for all I know
    it needs Entreprise Edition.
    In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
    a way by using flashback database so as to rolling backward the database and avoiding to recreate
    the Standby.
    In Standard Edition I'm afraid that you'll have to recreate your Standby database.
    Best regards,
    Jean-Valentin

  • Need to create a Database in Shared Serve Mode

    Hi,
    Please help me in Creating a Manual Database in Shared Server Mode. (I am a Student and It is a Learning Process).
    I am able to Create Database (Without DBCA) in Dedicated Mode and I have no doubts in that.
    What are the parameters i need to specify
    Please post me Helpful Links

    Poorna Prakash wrote:
    Hi,
    Please help me in Creating a Manual Database in Shared Server Mode. (I am a Student and It is a Learning Process).
    I am able to Create Database (Without DBCA) in Dedicated Mode and I have no doubts in that.
    What are the parameters i need to specify
    Please post me Helpful LinksYOu need to understand that ... as far as the database is concerned ... it's not an either/or situation between dedicated and shared server. Setting shared server parameter like DISPATCHERS simply allows the database to handle shared server connections. But it is up to the client to specify which method it wants, and the database will always allow dedicated server connections.

  • Database recovery in Inconsistent mode

    Hi,
    We have mirroring at 24:00 on one of the mount point in Solaris which copy all oracle datafiles,redo files and control files and create a replica of all these files in a separate folder. But my database is running in NOARCHIVELOG mode.I am assuming it would be an inconsistent backup.
    I am wondering if in case of any failure can we recover with these replica files created on 24:00.
    My query is if the database is in NOARCHIVELOG mode, Can we use the command "recover database until time" and recover database till 23:55.
    Thanks,
    Vaibhav

    user10624526 wrote:
    Hi,
    We have mirroring at 24:00 on one of the mount point in Solaris which copy all oracle datafiles,redo files and control files and create a replica of all these files in a separate folder. But my database is running in NOARCHIVELOG mode.I am assuming it would be an inconsistent backup.
    I am wondering if in case of any failure can we recover with these replica files created on 24:00.
    My query is if the database is in NOARCHIVELOG mode, Can we use the command "recover database until time" and recover database till 23:55.
    Thanks,
    Vaibhavno & no
    For you to obtain a consistent backup, the DB must first be cleanly shutdown.
    Consider changing into ARCHIVE MODE

  • Sharepoint Crawler database went to emergency mode

    Hi,
    My SharePoint Crawl Database went on Suspect mode suddenly & now i need to bring on Online mode.
    For solving this issue, i Google on several sites & came across following steps,
    Steps:
    EXEC sp_resetstatus 'DBName';
    ALTER DATABASE DBName SET EMERGENCY
    DBCC checkdb('DBName')
    ALTER DATABASE DBName SET SINGLE_USER WITH ROLLBACK IMMEDIATE
    DBCC CheckDB ('DBName', REPAIR_ALLOW_DATA_LOSS)
    ALTER DATABASE DBName SET MULTI_USER
    DBCC CheckDB ('DBName')
    Now the problem is Step 1 & 2 completed successfully, but when i tried step 3 it is throwing me below error,
    Msg 945, Level 14, State 2, Line 1
    Database 'DBName' cannot be opened
    due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
    I am using the service account which has full rights on the server & through which the SQL Server 2012 was configured.
    Current status Database is in Emergency mode & I am stuck over there.
    Please help.
    Regards,
    Purvish Shah

    Hi Alberto,
    Thank for the reply.
    I updated the Database with the below query ,
    ALTER DATABASE [YourDB] SET SINGLE_USER;
    GO
    It completed successfully, but the database is still in the
    "Emergency mode".When i checked in the logs it says 
    Message
    Setting database option SINGLE_USER to ON for database 'DBName'.
    Regards,
    Purvish Shah

  • How to put database in single user mode?

    hi
    how to put database in single user mode?and what could be the impact of this to EBS R12 RUP 6.DB 10.2.0.0
    rgrds

    hsawwan wrote:
    Hi,
    Are you referring to restricted mode? If yes, please see these links/docs.
    Restricting Access to an Open Database
    http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/start002.htm#ADMIN11155
    Note: 1059291.6 - How to Put a Database into Restricted Mode and Verify Restricted Mode
    The impact is none of the users will be able to connect to the database/application (except for the sys user which can connect to the database). Usually, you would need to put the database in restricted mode when doing upgrade/migrate (i.e. you do not want to have active user sessions in the database during that time).
    Thanks,
    HusseinHi
    i want to mean:
    ALTER SYSTEM QUIESCE RESTRICTEDThe ALTER SYSTEM QUIESCE RESTRICTED statement may wait a long time for active sessions to become inactive. You can determine the sessions that are blocking the quiesce operation by querying the V$BLOCKING_QUIESCE view. This view returns only a single column: SID (Session ID). You can join it with V$SESSION to get more information about the session, as shown in the following example:
    select bl.sid, user, osuser, type, program
    from v$blocking_quiesce bl, v$session se
    where bl.sid = se.sid;I suspect all apps user can.t login to db?
    Edited by: new2appsdba on Aug 19, 2010 1:54 AM

  • Would you use scripts to take database out of archivelog mode?

    Background: we do not use RMAN for this production database and we do cold backups each night.
    I've been asked to take one of our databases out of archivelog mode for a few days and then to put it back into archivelog mode.
    Being somewhat neurotic about these things - I've only ever done it manually - so that I can make sure nothing goes wrong and to check that there was a last successful cold backup prior to the switch.
    However, management have asked that it be done automatically by scripts after the backup.
    Whilst I can create a script that will do this - the question I'd like to ask the forum is - have you and would you?

    I do not agree with taking any Oracle database out of archivelog mode and I do not approve of management's decision and have told them why and all the risks they run.
    This is not a test database - it IS a production database and other users do make changes daily.
    What I did not reveal until now is that I have also been asked to take this database out of archivelog mode for 5 days and suspend all cold back-ups for the whole server (with 3 other instances on the server - also impacted) - and have warned them accordingly.
    However, management have been swayed by someone who feels they know better - who claims to be a qualified Oracle DBA - I'm OCP but seems to have little sway since this person has convinced management that my 6 years experience and qualification is less than his application experience in GIS.
    They want to run an upload which will take around 5 days to do - I'm somewhat miffed that an upload can take that length of time and question whether a GIS system should need such an upload for such a length of time.
    Let's no go into the problem with tablespaces and space within the tablespaces - the upload will fail because they do not understand that if the tablespace fills up - the upload will fail - but despite asking - I've been told that there is no problem - there will be a problem - since I refuse to allow autoextend on this database - because of the potential to run out of disk space.
    I've explained until I'm blue in the face - never mind that even if the upload is successful - the cold backup tape won't be able to backup the data because it'll be potentially over the limit.
    I've even warned of my past experience x 3 - when a RAID controller failed - literally died in front of my eyes - I just happened to be standing next to one of the servers talking to someone - and the whole server was lost - but because we had the archivelogs - and the previous day's backup - we got it up and running after Dell replaced the RAID controller - within 1 hour.
    That's the joy of Oracle - nothing is lost other than the last archivelog - depending on the time you set the switch.
    I love this system - it's so recoverable - it such a joy to work with.
    But then when I get told to suspend cold backups and then at the same time suspend archivelog mode - I go mad.
    Don't get me started - I've gone down the usual path of why hire an OCP when you won't listen to what I say, etc.
    Management are demanding I switch it automatically out of archivelog mode etc.
    I can do it - but my question is still - have you guys?
    And why did you do it?
    All I can say is that I hope that the server has a RAID contoller failure and finally they listen to me - the chances of that are minimal - so management are saying - do it or else.
    Oh and by the way - the GIS team have asked for this to be bi-monthly - automated.
    And have said that:
    "You can not rollback or recover the loading process using the log files because it involves a far more complex operation that would most likely not be successful."
    Nice phrase that to an OCP.
    I welcome your comments - as I really am in a hole here.
    Thanks.

  • Error: 1013231 Unable to update database while in readonly mode for backup

    Hi all,
    Wen im deleting the members for dimendsion , its giving error (hyperion 11.1 aso)
    Error: 1013231 Unable to update database while in readonly mode for backup , how can i solve this problem ,plz can any one help on this
    Thanks

    Has somebody set the database ready for archiving, maybe some maxl has been run and the db has not been returned from read only mode.
    Try running the following Maxl (change app.db to match your app/db)
    alter database app.db end archive;
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Database Started In Restricted Mode...

    Dear Exports,
    We are using Oracle 10gR2 on Windows server 2008. My database size is approximately 2tb. Now we are going to setup Dataguard for our primary. We started the database with the changer parameters for dataguard and create spfile from pfile. And started the database with Spfile. But after some time i noticed that the database started automatically in Restricted mode. As in our database Previously dataguard was configured, due to the some problem that setup is not working and the logs are not applied in Standby server. I thought may be for this reason database going to restricted mode automatically so i set the log_archive_dest_state_2='DEFFER' and Now I scanned the whore alert.log file and found the same situation of restricted is happening from Jan 2010. Please Suggest some solution how i can over come the problem.
    The alertlog when i started the database recently...
    ALTER DATABASE CLOSE NORMAL
    ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Fri Apr 12 19:12:39 2013
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =97
    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 = 800
    sessions = 885
    sga_max_size = 10737418240
    __shared_pool_size = 1325400064
    __large_pool_size = 16777216
    __java_pool_size = 16777216
    __streams_pool_size = 0
    sga_target = 8589934592
    control_files = G:\ORADATA\CONTROL01.CTL, G:\ORADATA\CONTROL02.CTL, G:\ORADATA\CONTROL03.CTL
    db_block_size = 8192
    __db_cache_size = 7214202880
    compatible = 10.2.0.3.0
    log_archive_config = DG_CONFIG=(orcl,stdby)
    log_archive_dest_1 = LOCATION=I:\archive_log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl
    log_archive_dest_2 = SERVICE=stdby NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stdby
    log_archive_dest_state_1 = enable
    log_archive_max_processes= 30
    log_archive_format = ARC%D_%s_%R.%T
    fal_client = orcl
    fal_server = stdby
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    standby_file_management = AUTO
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    undo_retention = 5400
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
    local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.168.12.86)(PORT=1521))
    job_queue_processes = 10
    audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
    background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
    user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
    core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
    db_name = orcl
    open_cursors = 500
    pga_aggregate_target = 10737418240
    PMON started with pid=2, OS id=14328
    PSP0 started with pid=3, OS id=15420
    MMAN started with pid=4, OS id=9092
    DBW0 started with pid=5, OS id=12360
    DBW1 started with pid=6, OS id=18112
    LGWR started with pid=7, OS id=18360
    CKPT started with pid=8, OS id=18448
    SMON started with pid=9, OS id=17160
    RECO started with pid=10, OS id=18512
    CJQ0 started with pid=11, OS id=19324
    MMON started with pid=12, OS id=14380
    Fri Apr 12 19:12:40 2013
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=13, OS id=2996
    Fri Apr 12 19:12:40 2013
    starting up 1 shared server(s) ...
    Fri Apr 12 19:12:41 2013
    ALTER DATABASE MOUNT
    Fri Apr 12 19:12:45 2013
    Setting recovery target incarnation to 2
    Fri Apr 12 19:12:45 2013
    Successful mount of redo thread 1, with mount id 1340307369
    Fri Apr 12 19:12:45 2013
    Allocated 15937344 bytes in shared pool for flashback generation buffer
    Starting background process RVWR
    RVWR started with pid=17, OS id=5524
    Fri Apr 12 19:12:45 2013
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Fri Apr 12 19:12:46 2013
    ALTER DATABASE OPEN
    Fri Apr 12 19:12:46 2013
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=18, OS id=11964
    ARC1 started with pid=19, OS id=13472
    ARC2 started with pid=20, OS id=17960
    ARC3 started with pid=21, OS id=18548
    ARC4 started with pid=22, OS id=15660
    ARC5 started with pid=23, OS id=15548
    ARC6 started with pid=24, OS id=14720
    ARC7 started with pid=25, OS id=15780
    ARC8 started with pid=26, OS id=17992
    ARC9 started with pid=27, OS id=17988
    ARCa started with pid=28, OS id=19436
    ARCb started with pid=29, OS id=16104
    ARCc started with pid=30, OS id=6656
    ARCd started with pid=31, OS id=6900
    ARCe started with pid=32, OS id=10568
    ARCf started with pid=33, OS id=16992
    ARCg started with pid=34, OS id=14372
    ARCh started with pid=35, OS id=18084
    ARCi started with pid=36, OS id=5788
    ARCj started with pid=37, OS id=4940
    ARCk started with pid=38, OS id=18816
    ARCl started with pid=39, OS id=14588
    ARCm started with pid=40, OS id=16820
    ARCn started with pid=41, OS id=8068
    ARCo started with pid=42, OS id=18736
    ARCp started with pid=43, OS id=8316
    ARCq started with pid=44, OS id=5952
    ARCr started with pid=45, OS id=16304
    ARCs started with pid=46, OS id=14884
    Fri Apr 12 19:12:46 2013
    ARC0: Archival started
    ARCt started with pid=47, OS id=19408
    Fri Apr 12 19:12:46 2013
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    Thread 1 opened at log sequence 117446
    Current log# 10 seq# 117446 mem# 0: G:\ORADATA\REDO10A.LOG
    Current log# 10 seq# 117446 mem# 1: H:\ORADATA\REDO10B.LOG
    Fri Apr 12 19:12:46 2013
    ARC0: Becoming the 'no FAL' ARCH
    Fri Apr 12 19:12:46 2013
    ARC0: Becoming the 'no SRL' ARCH
    Fri Apr 12 19:12:46 2013
    ARC8: Becoming the heartbeat ARCH
    Fri Apr 12 19:12:47 2013
    Successful open of redo thread 1
    Fri Apr 12 19:12:47 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Apr 12 19:12:47 2013
    SMON: enabling cache recovery
    Fri Apr 12 19:12:48 2013
    Successfully onlined Undo Tablespace 1.
    Fri Apr 12 19:12:48 2013
    SMON: enabling tx recovery
    Fri Apr 12 19:12:48 2013
    Database Characterset is WE8MSWIN1252
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 16
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=48, OS id=10048
    Fri Apr 12 19:12:51 2013
    Completed: ALTER DATABASE OPEN
    Fri Apr 12 19:12:51 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mmon_14380.trc:
    ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 99.56% used, and has 9486336 remaining bytes available.
    Fri Apr 12 19:12:51 2013
    You have following choices to free up space from flash recovery area:
    1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
    then consider changing RMAN ARCHIVELOG DELETION POLICY.
    2. Back up files to tertiary device such as tape using RMAN
    BACKUP RECOVERY AREA command.
    3. Add disk space and increase db_recovery_file_dest_size parameter to
    reflect the new space.
    4. Delete unnecessary files using RMAN DELETE command. If an operating
    system command was used to delete files, then use RMAN CROSSCHECK and
    DELETE EXPIRED commands.
    Dump file d:\oracle\product\10.2.0\admin\orcl\bdump\alert_orcl.log
    Fri Apr 12 19:13:26 2013
    ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Windows NT Version V6.0 Service Pack 1
    CPU : 16 - type 8664, 16 Physical Cores
    Process Affinity : 0x0000000000000000
    Memory (Avail/Total): Ph:55999M/65533M, Ph+PgF:183151M/193356M
    Fri Apr 12 19:13:26 2013
    Starting ORACLE instance (restrict)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =97
    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 = 800
    sessions = 885
    sga_max_size = 10737418240
    __shared_pool_size = 1325400064
    __large_pool_size = 16777216
    __java_pool_size = 16777216
    __streams_pool_size = 0
    sga_target = 8589934592
    control_files = G:\ORADATA\CONTROL01.CTL, G:\ORADATA\CONTROL02.CTL, G:\ORADATA\CONTROL03.CTL
    db_block_size = 8192
    __db_cache_size = 7214202880
    compatible = 10.2.0.3.0
    log_archive_config = DG_CONFIG=(orcl,stdby)
    log_archive_dest_1 = LOCATION=I:\archive_log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl
    log_archive_dest_2 = SERVICE=stdby NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stdby
    log_archive_dest_state_1 = enable
    log_archive_max_processes= 30
    log_archive_format = ARC%D_%s_%R.%T
    fal_client = orcl
    fal_server = stdby
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    standby_file_management = AUTO
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    undo_retention = 5400
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
    local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=192.168.12.86)(PORT=1521))
    job_queue_processes = 10
    audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
    background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
    user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
    core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
    db_name = orcl
    open_cursors = 500
    pga_aggregate_target = 10737418240
    PMON started with pid=2, OS id=18668
    PSP0 started with pid=3, OS id=17668
    MMAN started with pid=4, OS id=16896
    DBW0 started with pid=5, OS id=18204
    DBW1 started with pid=6, OS id=16976
    LGWR started with pid=7, OS id=14552
    CKPT started with pid=8, OS id=4480
    SMON started with pid=9, OS id=10236
    RECO started with pid=10, OS id=11832
    CJQ0 started with pid=11, OS id=18844
    MMON started with pid=12, OS id=15320
    Fri Apr 12 19:13:27 2013
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=13, OS id=14944
    Fri Apr 12 19:13:27 2013
    starting up 1 shared server(s) ...
    Fri Apr 12 19:13:27 2013
    alter database orcl mount exclusive
    Fri Apr 12 19:13:31 2013
    Setting recovery target incarnation to 2
    Fri Apr 12 19:13:31 2013
    Successful mount of redo thread 1, with mount id 1340305111
    Fri Apr 12 19:13:31 2013
    Allocated 15937344 bytes in shared pool for flashback generation buffer
    Starting background process RVWR
    RVWR started with pid=17, OS id=12880
    Fri Apr 12 19:13:31 2013
    Database mounted in Exclusive Mode
    Completed: alter database orcl mount exclusive
    Fri Apr 12 19:13:31 2013
    alter database open
    Fri Apr 12 19:13:31 2013
    Beginning crash recovery of 1 threads
    parallel recovery started with 15 processes
    Fri Apr 12 19:13:31 2013
    Started redo scan
    Fri Apr 12 19:13:31 2013
    Completed redo scan
    735 redo blocks read, 211 data blocks need recovery
    Fri Apr 12 19:13:31 2013
    Started redo application at
    Thread 1: logseq 117446, block 97761
    Fri Apr 12 19:13:31 2013
    Recovery of Online Redo Log: Thread 1 Group 10 Seq 117446 Reading mem 0
    Mem# 0: G:\ORADATA\REDO10A.LOG
    Mem# 1: H:\ORADATA\REDO10B.LOG
    Fri Apr 12 19:13:31 2013
    Completed redo application
    Fri Apr 12 19:13:32 2013
    Completed crash recovery at
    Thread 1: logseq 117446, block 98496, scn 7310601900
    211 data blocks read, 211 data blocks written, 735 redo blocks read
    Fri Apr 12 19:13:33 2013
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=33, OS id=18508
    ARC1 started with pid=34, OS id=14692
    ARC2 started with pid=35, OS id=17728
    ARC3 started with pid=36, OS id=12476
    ARC4 started with pid=37, OS id=19228
    ARC5 started with pid=38, OS id=11552
    ARC6 started with pid=39, OS id=7576
    ARC7 started with pid=40, OS id=6244
    ARC8 started with pid=41, OS id=18468
    ARC9 started with pid=42, OS id=18492
    ARCa started with pid=43, OS id=10352
    ARCb started with pid=44, OS id=15516
    ARCc started with pid=45, OS id=18216
    ARCd started with pid=46, OS id=5660
    ARCe started with pid=47, OS id=18756
    ARCf started with pid=48, OS id=17828
    ARCg started with pid=49, OS id=8696
    ARCh started with pid=50, OS id=17736
    ARCi started with pid=51, OS id=16736
    ARCj started with pid=52, OS id=13208
    ARCk started with pid=53, OS id=12012
    ARCl started with pid=54, OS id=19180
    ARCm started with pid=55, OS id=16632
    ARCn started with pid=56, OS id=17588
    ARCo started with pid=57, OS id=11948
    ARCp started with pid=58, OS id=18416
    ARCq started with pid=59, OS id=17888
    ARCr started with pid=60, OS id=2144
    ARCs started with pid=61, OS id=14392
    Fri Apr 12 19:13:33 2013
    ARC0: Archival started
    ARCt started with pid=62, OS id=19264
    Fri Apr 12 19:13:33 2013
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    Fri Apr 12 19:13:33 2013
    Thread 1 advanced to log sequence 117447 (thread open)
    Thread 1 opened at log sequence 117447
    Current log# 8 seq# 117447 mem# 0: G:\ORADATA\REDO08A.LOG
    Current log# 8 seq# 117447 mem# 1: H:\ORADATA\REDO08B.LOG
    Successful open of redo thread 1
    Fri Apr 12 19:13:33 2013
    ARC3: Becoming the 'no FAL' ARCH
    Fri Apr 12 19:13:33 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Apr 12 19:13:33 2013
    ARC3: Becoming the 'no SRL' ARCH
    Fri Apr 12 19:13:33 2013
    ARCr: Becoming the heartbeat ARCH
    Fri Apr 12 19:13:33 2013
    SMON: enabling cache recovery
    Fri Apr 12 19:13:33 2013
    Successfully onlined Undo Tablespace 1.
    Fri Apr 12 19:13:33 2013
    SMON: enabling tx recovery
    Fri Apr 12 19:13:33 2013
    Database Characterset is WE8MSWIN1252
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 16
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=63, OS id=14896
    Fri Apr 12 19:13:34 2013
    Completed: alter database open
    Fri Apr 12 19:13:34 2013
    ALTER SYSTEM disable restricted session;
    Fri Apr 12 19:13:35 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_mmon_15320.trc:
    ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 99.56% used, and has 9486336 remaining bytes available.
    Fri Apr 12 19:13:35 2013
    You have following choices to free up space from flash recovery area:
    1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
    then consider changing RMAN ARCHIVELOG DELETION POLICY.
    2. Back up files to tertiary device such as tape using RMAN
    BACKUP RECOVERY AREA command.
    3. Add disk space and increase db_recovery_file_dest_size parameter to
    reflect the new space.
    4. Delete unnecessary files using RMAN DELETE command. If an operating
    system command was used to delete files, then use RMAN CROSSCHECK and
    DELETE EXPIRED commands.
    Fri Apr 12 19:13:36 2013
    Error 12514 received logging on to the standby
    Fri Apr 12 19:13:36 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc0_18508.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    FAL[server, ARC0]: Error 12514 creating remote archivelog file 'stdby'
    FAL[server, ARC0]: FAL archive failed, see trace file.
    Fri Apr 12 19:13:36 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc0_18508.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Fri Apr 12 19:19:33 2013
    Error 12514 received logging on to the standby
    Fri Apr 12 19:19:33 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Fri Apr 12 19:22:52 2013
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Fri Apr 12 20:09:34 2013
    Error 12514 received logging on to the standby
    Fri Apr 12 20:09:34 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Fri Apr 12 20:13:50 2013
    Sat Apr 13 01:54:52 2013
    Error 12514 received logging on to the standby
    Sat Apr 13 01:54:52 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Sat Apr 13 12:35:12 2013
    Error 12514 received logging on to the standby
    Sat Apr 13 12:35:12 2013
    Errors in file d:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcr_2144.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARCr]: Heartbeat failed to connect to standby 'stdby'. Error is 12514.
    Sat Apr 13 12:37:01 2013
    ALTER SYSTEM SET log_archive_dest_state_2='DEFER' SCOPE=MEMORY;
    Sat Apr 13 12:38:23 2013
    Unable to allocate flashback log of 1946 blocks from
    current recovery area of size 2147483648 bytes.
    Current Flashback database retention is less than target
    because of insufficient space in the flash recovery area.
    Flashback will continue to use available space, but the
    size of the flash recovery area must be increased to meet
    the Flashback database retention target
    Use ALTER SYSTEM SET db_recovery_file_dest_size command
    to add space. DO NOT manually remove flashback log files
    to create space.
    Sat Apr 13 12:38:41 2013
    ALTER SYSTEM SET db_recovery_file_dest_size='5G' SCOPE=MEMORY;
    Sat Apr 13 12:38:41 2013
    db_recovery_file_dest_size of 5120 MB is 39.82% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Sat Apr 13 15:42:21 2013
    ORA-01555 caused by SQL statement below (SQL ID: 2zb70pwz9p06q, Query Duration=1365847941 sec, SCN: 0x0001.b3c0f735):
    Sat Apr 13 15:42:21 2013
    SELECT * FROM RELATIONAL("ORISSA_TRANSACTION"."SELLER_BIOMETRICS_TBL")
    Sat Apr 13 15:48:37 2013
    Thread 1 advanced to log sequence 117452 (LGWR switch)
    Current log# 10 seq# 117452 mem# 0: G:\ORADATA\REDO10A.LOG
    Current log# 10 seq# 117452 mem# 1: H:\ORADATA\REDO10B.LOG
    Sat Apr 13 20:31:00 2013
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM00 started with pid=31, OS id=16196
    to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_30', 'ORISSA_TRANSACTION', 'KUPC$C_1_20130413203100', 'KUPC$S_1_20130413203100', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=66, OS id=16200
    to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_30', 'ORISSA_TRANSACTION');
    Sun Apr 14 00:00:11 2013
    Thread 1 advanced to log sequence 117453 (LGWR switch)
    Current log# 8 seq# 117453 mem# 0: G:\ORADATA\REDO08A.LOG
    Current log# 8 seq# 117453 mem# 1: H:\ORADATA\REDO08B.LOG
    Sun Apr 14 00:00:52 2013
    Thread 1 advanced to log sequence 117454 (LGWR switch)
    Current log# 9 seq# 117454 mem# 0: G:\ORADATA\REDO09A.LOG
    Current log# 9 seq# 117454 mem# 1: H:\ORADATA\REDO09B.LOG

    like you show in the alert.log:
    PROBLEM
    Unable to allocate flashback log of 1946 blocks from
    current recovery area of size 2147483648 bytes.
    Current Flashback database retention is less than target
    because of insufficient space in the flash recovery area.
    Flashback will continue to use available space, but the
    size of the flash recovery area must be increased to meet
    the Flashback database retention target
    Use ALTER SYSTEM SET db_recovery_file_dest_size command
    to add space. DO NOT manually remove flashback log files
    to create space.
    SOLUTION
    Fri Apr 12 19:12:51 2013
    You have following choices to free up space from flash recovery area:
    1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
    then consider changing RMAN ARCHIVELOG DELETION POLICY.
    2. Back up files to tertiary device such as tape using RMAN
    BACKUP RECOVERY AREA command.
    3. Add disk space and increase db_recovery_file_dest_size parameter to
    reflect the new space.
    4. Delete unnecessary files using RMAN DELETE command. If an operating
    system command was used to delete files, then use RMAN CROSSCHECK and
    DELETE EXPIRED commands.
    ************************************************************************choose one and try again. Post if you have more issues.

  • Cannot open the database, stuck in mount mode

    Someone please shed some lights on this problem.
    I ran into some media failure, and ended up restoring the database from the offline whole backup.
    The database is in the nonarchivelog mode (I know, it is not good), so there is no archive log files and
    restore database is the only solution.
    . startup mount
    . restore database <== ran ok
    . ALTER DATABASE CLEAR LOGFILE GROUP 1 <== ran ok
    . ALTER DATABASE CLEAR LOGFILE GROUP 2 <== alter failed
    ORA-01624: log 2 needed for crash recovery of instance orcl (thread 1)
    Alter failed with group 2 and 3 because one was CURRENT,
    and one was ACTIVE.
    SQL> select group#, sequence#, members, status from v$log;
    GROUP# SEQUENCE# MEMBERS STATUS
    1 0 2 UNUSED
    3 189 2 CURRENT
    2 188 2 ACTIVE
    I also tried 'alter database open resetlogs', and got:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    I don't think I can recover the datafile since there is no archive log file here.
    Besides, if the restore database ran fine, why did I get SYSTEM01.DBF datafile needs media recovery message?
    Right now, the database is in mount mode, and I cannot open it. How do I solve the problem with
    ALTER DATABASE CLEAR LOGFILE GROUP for group 2 and 3?
    Any suggestion? Thank you for the input.
    The database is 11G running on Window.

    I would think the cold backup ran successfully. Here is the backup record:
    RMAN> run {
    2> shutdown immediate;
    3> startup mount;
    4> allocate channel c1 type disk;
    5> backup as backupset database;
    6> alter database open;
    7> }
    8>
    using target database control file instead of recovery catalog
    database closed
    database dismounted
    Oracle instance shut down
    connected to target database (not started)
    Oracle instance started
    database mounted
    Total System Global Area 535662592 bytes
    Fixed Size 1348508 bytes
    Variable Size 331353188 bytes
    Database Buffers 197132288 bytes
    Redo Buffers 5828608 bytes
    allocated channel: c1
    channel c1: SID=156 device type=DISK
    Starting backup at 29-NOV-09
    channel c1: starting full datafile backup set
    channel c1: specifying datafile(s) in backup set
    input datafile file number=00002 name=C:\APP\DAVECW\ORADATA\ORCL\SYSAUX01.DBF
    input datafile file number=00001 name=C:\APP\DAVECW\ORADATA\ORCL\SYSTEM01.DBF
    input datafile file number=00003 name=C:\APP\DAVECW\ORADATA\ORCL\UNDOTBS01.DBF
    input datafile file number=00005 name=C:\APP\DAVECW\ORADATA\ORCL\EXAMPLE01.DBF
    input datafile file number=00006 name=C:\APP\DAVECW\ORADATA\ORCL\INVENTORY01.DBF
    input datafile file number=00004 name=C:\APP\DAVECW\ORADATA\ORCL\USERS01.DBF
    channel c1: starting piece 1 at 29-NOV-09
    channel c1: finished piece 1 at 29-NOV-09
    piece handle=C:\APP\DAVECW\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_11_29\O1_MF_NNNDF_TAG20091129T230
    632_5K6VQY0W_.BKP tag=TAG20091129T230632 comment=NONE
    channel c1: backup set complete, elapsed time: 00:01:55
    channel c1: starting full datafile backup set
    channel c1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel c1: starting piece 1 at 29-NOV-09
    channel c1: finished piece 1 at 29-NOV-09
    piece handle=C:\APP\DAVECW\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_11_29\O1_MF_NCSNF_TAG20091129T230
    632_5K6VVNJR_.BKP tag=TAG20091129T230632 comment=NONE
    channel c1: backup set complete, elapsed time: 00:00:03
    Finished backup at 29-NOV-09
    database opened
    released channel: c1
    Recovery Manager complete.

  • Database Recovery in NOARCHIVELOG Mode

    Hi All,
    I was trying to 'startup' my database & encountered the following error in the alert.log
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 469 failed verification check
    ORA-01110: data file 469: '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf'
    ORA-01209: data file is from before the last RESETLOGS
    I then looked up on the internet and since the error was related to the UNDO TABLESPACE, i did the following:
    sql>startup mount
    sql>alter database datafile '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf' offline drop;
    sql>alter database open
    Thereafter the database kept on erroring on all the datafiles belonging to the undo tablespaces and i dropped all the datafiles belonging to the undo tablespace using the above command. (alter database datafile ....offline drop).
    Next, i tried to open the database and got the following error from the alert log:
    Tue May 12 18:15:24 2009
    alter database open
    Tue May 12 18:15:33 2009
    Beginning crash recovery of 1 threads
    Tue May 12 18:15:33 2009
    Started redo scan
    Tue May 12 18:15:33 2009
    Completed redo scan
    21 redo blocks read, 3 data blocks need recovery
    Tue May 12 18:15:33 2009
    Started recovery at
    Thread 1: logseq 252, block 2, scn 1917.14626262
    Tue May 12 18:15:33 2009
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 252 Reading mem 0
    Mem# 0 errs 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo03a.dbf
    Tue May 12 18:15:33 2009
    Completed redo application
    Tue May 12 18:15:33 2009
    Ended recovery at
    Thread 1: logseq 252, block 23, scn 1917.14646284
    3 data blocks read, 3 data blocks written, 21 redo blocks read
    Crash recovery completed successfully
    Tue May 12 18:15:35 2009
    Thread 1 advanced to log sequence 253
    Thread 1 opened at log sequence 253
    Current log# 4 seq# 253 mem# 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo04a.dbf
    Successful open of redo thread 1
    Tue May 12 18:15:38 2009
    LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
    Tue May 12 18:15:38 2009
    SMON: enabling cache recovery
    Tue May 12 18:15:38 2009
    Successfully onlined Undo Tablespace 1.
    Tue May 12 18:15:39 2009
    SMON: enabling tx recovery
    Tue May 12 18:15:39 2009
    Database Characterset is US7ASCII
    Tue May 12 18:15:39 2009
    SMON: about to recover undo segment 1
    Can someone please help me on this issue? Thanks and Regards

    Hi ERROR,
    I think i figured out the hidden parameter that you were referring to.
    (1) I set the allowresetlogs_corruption=TRUE and commented undo_management. Then opened the database using--> alter database open resetlogs;
    But still was not able to start the database. The alert log entries are as below:
    ALTER DATABASE   MOUNT
    Thu May 14 18:11:56 2009
    Successful mount of redo thread 1, with mount id 4113112614
    Thu May 14 18:11:56 2009
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Shutting down instance: further logons disabled
    Shutting down instance (immediate)
    License high water mark = 2
    Thu May 14 18:12:05 2009
    ALTER DATABASE CLOSE NORMAL
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    Thu May 14 18:12:05 2009
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archiving is disabled
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archiving is disabled
    Would be great if you can help me further on this.
    Regards,
    Fuzzy

  • Regarding database tables in which i can write directly

    hi experts,
                      i have to create a database table in which i can write directly in to the table with out using update statement,what sud i do for this plz help me......

    Hi Ravi,
    If you mean you need to directly update values on the screen, SE11 has a menu for the table maintenance generator. In there you can generate screens and everything needed for your table to allow entry with or without transports. You then capture the data through transaction SM30 or SM31.
    Cheers
    Wayne

  • Unable to open database in READ ONLY mode

    When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
    1) Startup mount
    2) SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-16005: database requires recovery
    But database opens succesfully when opened in READ WRITE mode.

    user12038051 wrote:
    When trying to open database in READ ONLY MODE it says needs recovery. How ever database opens succesfully in READ WRITE MODE.
    1) Startup mount
    2) SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-16005: database requires recovery
    But database opens succesfully when opened in READ WRITE mode.
    sqlplus '/as sysdba'
    shutdown imediate;
    startup;
    shutdown imediate;
    startup mount;
    recover database;
    alter database open read only;

  • Putting apps database in Read-Only mode

    Hi,
    I want to put the apps database in read-only mode to that user will be able to login into the applications and see data but will not be able to update it.
    What is the best way to do this?
    Thanks

    I am still looking at how to do this because if users
    update the UAT/test database, when the prod upgrade
    is completed, they will think that their updates will
    be available and this will cause some issues.This is a training/expectation-setting issue, not a technical one. You need to make sure that your users understand the difference between a test system and production, and that changes made in testing will not be present in production. They also need to understand that this situation is actually to their benefit: it enables them to really work with the test system to uncover potential problems and learn new features, without fear of making changes that could negatively impact their day-to-day work in production.
    Please note that I'm not trying to be a jerk here. I very respectfully submit that attempting to make an instance read-only for training purposes, even if possible, will involve a great deal of technical work for very little (and perhaps even negative) overall benefit to the users.
    Regards,
    John P.

  • How to trigger an interface from a database(COBOL) in online mode?

    Hi everybody,
    Can you please tell me how to trigger an interface from a database(COBOL) in online mode?
    thanks a lot,
    Ramya Shenoy

    If you can make a HTTP call from you DB platform -
    HTTP -> BPM (Receive -> Send Step (execute an SP or your select statement here in the JDBC receiver channel) -> send (to target) )-> end.
    VJ

Maybe you are looking for