Database without logs - is it possible?

Hi all!
I have some data in berkeley db database under linux. My application collects some statistical information into database. .db file isn't big (near 100mb), but logs are growed to 15 gb during week of work. Now if i terminated my application with simply killing it, berkeley db engine loads database near 10-20 minutes, which is very long time for such small database.
When i disabled logs, berkeley db simply didn't want to open incorrectly closed database.
Can i make that berkeley db simply kill damaged records from database when i open it, without logs?
Thanks and sorry for my english :)

Hi,
You can not remove the log files just like that. Log files may be removed at any time, as long as:
* the log file is not involved in an active transaction.
* a checkpoint has been written subsequent to the log file's creation.
* the log file is not the only log file in the environment.
You can run the standalone db_archive utility with the -d option, to remove any log files that are no longer needed at the time the command is executed.
Related docs:
Database and log file archival: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/archival.html
Log file removal: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/logfile.html
Bogdan Coman

Similar Messages

  • !!!Urgent !!!!!Cannot recovery database without log files (SQL 2008)

    I only have single mdf file, the transaction log file was corrupted. When I was trying to attatch the mdf file, I received the following error message. Can someone give me a help..... it's really urgent!
    TITLE: Microsoft SQL Server Management Studio
    Attach database failed for Server 'DEV8\sqlexpress2008'.  (Microsoft.SqlServer.Smo)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.1600.22+((SQL_PreRelease).080709-1414+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
    ADDITIONAL INFORMATION:
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
    Could not open new database 'Smartadmin'. CREATE DATABASE is aborted.
    File activation failure. The physical file name "C:\MSSQL\Smartadmin_log.ldf" may be incorrect.
    The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure. (Microsoft SQL Server, Error: 1813)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.1600&EvtSrc=MSSQLServer&EvtID=1813&LinkId=20476
    BUTTONS:
    OK
    Javafun

    I killed a dev db by accident (moved it between folders while it had an open transaction) and out of curiosity attempted to fix it as though it were a super-urgent client db. The above link fixed it, but I'll cut to the chase since it's a lot simpler than
    most of the article:
    1) Set aside the database mdf and ldf you're trying to recover.
    2) Create a database in the location you wanted, of the same name as the problem DB.
    3) Stop the SQL Server service.
    4) Copy the mdf and ldf files in, overwriting the dummy db you created.
    5) Start the SQL Server service.
    Done. Fixed.
    Surely you're doing something SQL Server does not like, but it is unfortunate you have to shut down the entire service to perform this trick. All of the other methods in that linked article and sp_attach_single_file_db failed, but this worked like a charm.
    In my dev database I was left with a db that was good as new - no missing data no problems. It seems odd this works so well and yet all these other approaches get errors about an open transaction. To be fair though, my dev database is essentially a single-user
    file that isn't heavily used, I assume a production DB on a busy server would be more problematic.

  • Physical standby without ALTER DATABASE FORCE LOGGING

    Hi,
    Is it possible to use physical standby database without executing ALTER DATABASE FORCE LOGGING on primary side?
    Can I use alter tablespace force logginng instead?
    I want to have one tablespace with nologging option turned on to reduce redo traffic for some operations.
    I can not check this because I don`t have enough servers to build standby configuration.

    YuriAP wrote:
    Hi,
    Is it possible to use physical standby database without executing ALTER DATABASE FORCE LOGGING on primary side?
    YES
    Can I use alter tablespace force logginng instead?
    YES
    ALTER TABLESPACE <tablespace name> FORCE LOGGING;
    I want to have one tablespace with nologging option turned on to reduce redo traffic for some operations.
    I can not check this because I don`t have enough servers to build standby configuration.http://download.oracle.com/docs/cd/B10500_01/server.920/a96521/create.htm#1022863

  • Is it possible to perform network data encryption between Oracle 11g databases without the advance security option?

    Is it possible to perform network data encryption between Oracle 11g databases without the advance security option?
    We are not licensed for the Oracle Advanced Security Option and I have been tasked to use Oracle Network Data Encryption in order to encryption network traffic between Oracle instances that reside on remote servers. From what I have read and my prior understanding this is not possible without ASO. Can someone confirm or disprove my research, thanks.

    Hi, Srini Chavali-Oracle
    As for http://www.oracle.com/technetwork/database/options/advanced-security/advanced-security-ds-12c-1898873.pdf?ssSourceSiteId… ASO is mentioned as TDE and Redacting Sensitive Data to Display. Network encryption is excluded.
    As for Network Encryption - Oracle FAQ (of course this is not Oracle official) "Since June 2013, Net Encryption is now licensed with Oracle Enterprise Edition and doesn't require Oracle Advanced Security Option." Could you clarify this? Thanks.

  • Recover database without controlfile and redo logs

    Hi guys,
    I am doing a testing with an Oracle Database 11.1.0.7.0, I want recover a database in this scenario without using RMAN:
    -All controlfiles are missing
    -All redo logs are missing
    -I have a Backup Controlfile To Trace Resetlogs (bkp_controlfile.sql)
    -The database is in archivelog mode
    -The database was created with OMF (Oracle Managed Files)
    So I have done this steps:
    1) When the database was opened I rename all controlfiles and all redo logs
    2) Shutdown Abort
    3) I run the bkp_controlfile.sql, here I have a problem...
    The database put in NOMOUNT, the controlfile was created and started the RECOVER DATABASE USING BACKUP CONTROLFILE, but when run ALTER DATABASE OPEN RESETLOGS; appear this:
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1:
    '/u02/app/oracle/oradata/OMF/datafile/o1_mf_system_68hzcb2z_.dbf'I wasn´t expect this because I don´t want recover a datafile, I only want open with resetlogs.
    Any suggestion to help me?
    Thanks a lot.

    Excelent! Thanks for your answers Markus and Hemant.
    In conclusion...
    - If we have all redo logs availables we can recreate the control file and recover the database without any problems using backup controlfile to trace noresetlogs*.
    - if we haven´t all redo logs availables, there are 2 situations:
    1) If the database shutdown properly:_ We will be able to open the database using recover database using backup controlfile until cancel*.
    2) If the database doesn´t shutdown properly:_ We won´t be able to open the database with only a backup controlfile to trace.
    With all this I close this thread. Was very good experience.
    If anyone would add something will be welcome.
    Thanks for all
    I wish add the results of one of my tests: if I did all the steps in only one session of sqlplus I can shutdown properly the database, but if do the shutdown immediate* in a new session I can´t shutdown properly the database. Here I post the output:
    ALL IN ONE SESSION*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    Database opened.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> @/home/oracle/bkp_controlfile.sql
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Control file created.
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
    ORA-00279: change 398764 generated at 09/22/2010 14:09:49 needed for thread 1
    ORA-00289: suggestion :
    /u02/app/oracle/flash_recovery_area/OMF/archivelog/2010_09_22/o1_mf_1_40_%u_.arc
    ORA-00280: change 398764 for thread 1 is in sequence #40
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL> ALTER DATABASE OPEN RESETLOGS;
    Database altered.
    SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u02/app/oracle/oradata/OMF/datafile/o1_mf_temp_69n3z3vv_.tmp' SIZE 50331648  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    Tablespace altered.
    SQL>
    ALL IN DIFERENT SESSIONS*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:55:47 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/home/oracle/bkp_controlfile.sql' RESETLOGS;
    Database altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP MOUNT
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    SQL> ALTER DATABASE ARCHIVELOG;
    Database altered.
    SQL> ALTER DATABASE OPEN;
    Database altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> SHUTDOWN IMMEDIATE
    ORA-00210: cannot open the specified control file
    ORA-00202: control file: '/u02/app/oracle/oradata/OMF/controlfile/o1_mf_69n3x6n5_.ctl'
    ORA-27041: unable to open file
    Linux Error: 2: No such file or directory
    Additional information: 3

  • Urgent help : Need to recover a database without backup and archivelogs

    Hi,
    We are in urgent need to recover a database without backup and archivelogs
    one datafile seems corrupted
    SQL> recover automatic database until cancel using BACKUP CONTROLFILE;
    ORA-00279: change 10527325422479 generated at 07/27/2011 03:13:04 needed for
    thread 1
    ORA-00289: suggestion : /pys/u5/oradata/PYS/PYSarch/arch0001.0000181845.arc
    ORA-00280: change 10527325422479 for thread 1 is in sequence #181845
    ORA-00278: log file '/pys/u5/oradata/PYS/PYSarch/arch0001.0000181845.arc' no
    longer needed for this recovery
    ORA-00308: cannot open archived log
    '/pys/u5/oradata/PYS/PYSarch/arch0001.0000181845.arc'
    ORA-27037: unable to obtain file status
    HP-UX Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/pys/u2/oradata/PYS/pay_system_01.dbf'

    N Gasparotto wrote:
    bsac14 wrote:
    my database is in no archive mode
    can you please tell how to restore
    yes it is a datafile corruptionYou did not say how you defined that's a datafile corruption. You provide minimum to zero information.
    I just need to bring the database up,no need any exact data
    I can refresh from prod laterThen drop and recreate database. Basically and since you are not in archive mode, no recover is possible. Period.
    Nicolas.Hi,
    How did you come to the conclusion that your datafile is corrupted? Can you provide and supported logs?
    Regards .....

  • The database alert log has errors. Please help me

    Hi all
    I have an Oracle 8i Database that seams to be functioning well but when I
    Checked the Database alert Log I realized that something is not fine
    Part of the alert log content is here under. What can be problem and how can I
    Resolve it. Please I need you assistance...
    Thu Feb 07 08:50:37 2008
    Thread 1 advanced to log sequence 266
    Thu Feb 07 08:50:37 2008
    Current log# 11 seq# 266 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
    Thu Feb 07 08:50:38 2008
    ARC0: Beginning to archive log# 10 seq# 265
    Thu Feb 07 08:51:07 2008
    ARC0: Completed archiving log# 10 seq# 265
    Thu Feb 07 09:23:22 2008
    Errors in file E:\Oracle\admin\MUKREC\udump\ORA03976.TRC:
    Thu Feb 07 09:23:23 2008
    Errors in file E:\Oracle\admin\MUKREC\udump\ORA04092.TRC:
    ................................................................................................................

    I'll just throw a shameless copy-paste from Metalink note : 164839.1 , hope you can use it to get further ? :
    Subject: FATAL ERROR IN TWO-TASK SERVER: error = 12571 Found in Alert File
    Doc ID: Note:164839.1 Type: PROBLEM
    Last Revision Date: 17-DEC-2007 Status: PUBLISHED
    fact: Oracle Server - Enterprise Edition
    symptom: Errors appear in alert file
    symptom: FATAL ERROR IN TWO-TASK SERVER:
    symptom: ERROR = 12571
    symptom: trace file generated
    symptom: Database operations continue successfully
    cause: The most common cause for the above error is an ungraceful
    disconnection of a session from the oracle db while the db is currently running
    a dml statement issued by that session. The error is recorded when oracle
    attempts to reply back to the session with the results of the dml and cannot
    access the session. Overall database operations are usually not affected.
    An ungraceful disconnection could cause by but is not limited to any of the
    following:
    - the client machine crashed
    - the network connection crashed
    - the user exited the session improperly (not issuing the 'exit' command)
    - the user application allows the user to exit the application without properly
    terminating the session.
    The above can cause problems with corrupted rollback segments if occurring on a
    regular basis and is not addressed. This would require db recovery and
    possibly a db rebuild (not a light matter)
    PMON will usually rollback most transactions in the rollback segments for a
    session if it finds that the session has been ungracefully disconnected, but
    there is always a chance that it cannot and this will lead to rollback segment
    corruption.
    fix:
    The dml and the user that issued the dml can be determined from the trace file.
    The current dml is in the tracefile header section. The user can be found in
    the process state dump of the trace. The process state shows the machine,
    o/suser, and user for the session.
    The DBA can use this information to determine what the user was doing at the
    time and if there was an ungraceful exit from the session the user was
    utilizing.
    The DBA should then address the cause of the ungraceful exit to reduce the
    possibility of recurrence.

  • SQL - How to attach FileStream enabled db without log file

    I'm trying to attach a FileStream enabled database without a log file. My SQL looks something like this:
    USE master
    CREATE DATABASE MyDB
    ON PRIMARY(NAME = N'MyDB', FILENAME = 'C:\myDB.MDF' ),
    FILEGROUP myFileGroup CONTAINS FILESTREAM ( NAME = myData, FILENAME = 'C:\myFileGroup')      
    For Attach
    Here is the error I'm receiving:
    Msg 5173, Level 16, State 3, Line 2
    One or more files do not match the primary file of the database.
    If you are attempting to attach a database, retry the operation with the correct files.  
    If this is an existing database, the file may be corrupted and should be restored from a backup.
    Does anyone know if it's possible to attach a FileStream enabled database without the original log file?  Thanks!

    Hi cgregory,
    The error might occur if the database is not shutdown cleanly. In this case, log file is required, or, you will have some data lost. Please pay attention to this thread addressing this type of issue:
    attaching DB without .ldf file ???
    For attach a database with FILESTREAM enabled, please refer to this article:
    How to Detach and Attach a SQL Server FILESTREAM Enabled Database.
    Stephanie Lv
    TechNet Community Support

  • Rman backup on physical standby database without cancelling MRP

    Hi all,
    Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
    regarrds,

    Hi,
    On Standby Side:
    SQL> alter database mount;
    Database altered.
    SQL> alter database recover managed standby database using current logfile disconnect from session;
    Database altered.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=390 RECID=391 STAMP=815416638
    input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
    input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
    input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
    input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
    input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
    input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
    input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
    input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
    input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
    input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
    input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
    input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
    input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
    *input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
    *input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> exit
    Recovery Manager complete.
    [oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 2013
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select max(Sequence#) from  v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
    And will not delete this archived log, because it is needed for standby or upstream capture process.
    Updated
    When MRP stoped
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=24 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=405 RECID=406 STAMP=816017455
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> Apply process is stopped and new redo received from primary.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            407
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            405
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=406 RECID=407 STAMP=816018527
    input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> I think, codes is understandable.
    Regard
    Mahir M. Quluzade
    Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

  • How can I access a dormant chat history without logging onto Skype which will delete the data?

    I am posting this question here because many of you will have more technical knowldege about how this works compared to any other thread. I need to access my own Skype IM convos for legal reasons. I have only just realised that I do not have a complete history of chats from the begining of time. It's extremely frustrating that Skype only keeps 6mo worth of chat since Microsoft took over. This happened without any notification from MS that I can recall and it is a major problem for me now. Plan B: I have a Vista machine that I have not used for ages. If I can access the Skype IM chat history on it that will cover at least some of the period I need to access. My problem is, to view the IM chats I need to go online and log into Skype BUT that will wipe the info I need to see when it updates the history and goes back 6mo. It's a catch 22 situation. The info is there but i just don't know how to see it. As an additional complication, I stopped using the machine because there was a strong reason to believe it had a security breach/Trojan on it that antivirus program's could not detect. So I want to avoid going online with that Vista machine but it is possible. How can I view and extract my Skype IM convos without logging onto Skype itself and losing the data I want access? Obviously I know my passwords, so it's not a spying situation that I need to get around. It's very important that I view these old chats and fast. I have Internet access through other machines at the moment and I am not a techie. Can anyone help? You are my last chance.

    Thanks Tamim. I had seen that app but was reluctant to try it. Following your post, I tried it and YES it does work. It is a bit cumbersome and will take a lot of work to sift through the CSV file that has every single chat convo combined into one file and not into separate conversations. There are tens of thousands of lines to search through. I am very grateful that the history is retrievable at all . It's just going to take a long time to sift through the data in an efficient and useable way. Unfortunately, with deadlines looming, I have very little time to do it in. Tamim, or anyone else for that matter, do you know of a way that the information can be viewed as a complete conversation between 2 people only?
    ie filtering out the other irrelevant conversations?  Thnak you, thank you, thank you for your help so far.

  • Why don't we keep Oracle Database ARCH logs in RAW devices

    Hi All,
    Why don't we keep Oracle Database ARCH logs in RAW devices?
    How ARCH process is related to Block Device and Character Device ?
    Thanks,
    Tusar
    Edited by: user11987718 on 26-Jun-2012 09:59

    Why don't we keep Oracle Database ARCH logs in RAW devices? 1.This is because raw devices do not enable sequential writing of consecutive archive log files.
    http://docs.oracle.com/cd/E11882_01/rac.112/e16795/rman.htm#RACAD320
    2.with raw you have to specify the exact size of the file at creation time, in contrast with file system, where you can create file without specifying its size, start writing to it, apending new blocks to it until you are done, and thus creating a file of whatever size it needs to be to hold all information.
    http://www.dbasupport.com/forums/archive/index.php/t-16429.html
    3.raw file systems are difficult to manage because you cannot run normal os commands on them.(as there is no file systems)
    How ARCH process is related to Block Device and Character Device ?A block device would read/write bytes in fixed size blocks, as in disk sectors. Character devices read/write 0 or more bytes, in a stream, such as a TTY or a keyboard.
    For more details about what is block and character device type :
    http://en.wikipedia.org/wiki/Device_file
    And now think, how arch process is related to block and character devices.
    Regards
    Girish Sharma

  • ORA-02231 error when issue ALTER DATABASE FORCE LOGGING

    Hi,
    Does everybody know why I faced ORA-02231 when issue below command in oracle,
    SQL> ALTER DATABASE FORCE LOGGING;
    ALTER DATABASE FORCE LOGGING
    ERROR at line 1:
    ORA-02231: missing or invalid option to ALTER DATABASE
    SQL> ALTER DATABASE FORCE LOGGING ;
    ALTER DATABASE FORCE LOGGING
    ERROR at line 1:
    ORA-02231: missing or invalid option to ALTER DATABASE
    SQL> ALTER DATABASE FORCE LOGGING
    2
    SQL> ALTER TABLESPACE BIIS FORCE LOGGING
    2 ;
    ALTER TABLESPACE BIIS FORCE LOGGING
    ERROR at line 1:
    ORA-02142: missing or invalid ALTER TABLESPACE option
    I use this oracle version:
    Oracle9i Enterprise Edition Release 9.0.1.1.1 - Production
    PL/SQL Release 9.0.1.1.1 - Production
    CORE 9.0.1.1.1 Production
    TNS for 32-bit Windows: Version 9.0.1.1.0 - Production
    NLSRTL Version 9.0.1.1.1 - Production
    Thanks.

    Hi Jaffar,
    After I checked that you are correct.
    I can issue the command without problem in oracle 9i Rel.2.
    Thanks for your information.
    Tarman.

  • Using database without ODBC

    It's possible to use a database without ODBC in Labview??

    IDILIO wrote:
    Hi Rolf,
    At this moment I m using the Microsoft ODBC driver for Oracle and it works ok, but my problem is when i do several reads at the database it reflects in a big delay for the Front Panel.
    As i know that the ODBC driver is a very slow method to access database i m searching for a faster way to do it. Do you have any suggestions?
    It's not ODBC that is necessarily slow. It is usually the way you retrieve data that has a lot more influence on the speed of the data retrieval. In the case of the Microsoft ODBC driver it might be that this driver is not specifically optimized for speed for various reasons.
    First implementing someone elses protocol is always difficult (not sure how well Oracle documents their protocol) and the temptation to stop when it is working rather than when it is working perfect is much bigger. Also it is of course not in Microsofts interest to provide you with a solution for Oracle that outperforms their own SQL Server interface so that is even one more incentive to stop when it is working rather than when it is working perfect.
    Have you tried to use the Oracle ODBC drivers? They might be more optimized so that retrieving data through ADO can be faster.
    Very important is how you retrieve the data however. The classical and simple way of retrieving data element for element is very slow. For this ADO/OLE DB has introduced rowsets which query several rows of a query result at once in one single driver request and then later allow the client to retrieve the elements locally into the native data. This is for remote databases always a huge performance improvement, since the bottle neck here is the network communication and not the memory manager or IO interface.So requesting one whole bunch of rows at once instead of element by element reduces the network traffic substantially and increases the performance at the cost of some extra memory usage for local caching. And the best thing is that the ADO rowsets can be mapped to ODBC cursor sets if the ODBC driver supports cursor sets and the ADO ODBC bridge does that transparently for you. Accessing ODBC directly you could also use cursor sets, but the API for doing that is really not for the faint hearted. ADO rowsets in comparison are very simple to use.
    Try to read a bit about ADO database query optimizations on the web to get an idea of the techniques used and they usually can be quite simply translated to ADO methods as used in the Database Connectivity Toolkit or any of the other ADO based toolkits out there.
    Rolf Kalbermatter
    Message Edited by rolfk on 01-26-2007 04:14 PM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Backup the database without shuting down the database

    Hello All,
    Just want to ask if any one can tell me if it is possible to backup the database without shutting it down
    When can you do so if it is possible?

    A hot (or on-line) backup is a backup performed while the database is open and available for use (read and write activity). Except for Oracle exports, one can only do on-line backups when the database is ARCHIVELOG mode.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/toc.htm

  • ORA-02048: attempt to begin distributed transaction without logging on

    Hello,
    I've got the error:
    ORA-02048: attempt to begin distributed transaction without logging on
    When calling OCITransStart
    (The XID of the transaction to start is:
    formatID = 11101, gtrid = 123, bqual = 1
    I've already run several queries before trying to call
    OCITransStart and the queries are successfull.
    Could anyone help please ?
    I'm running Oracle 10g on Linux.
    Thanks a lot
    Laurent Marzullo

    I believe this is the error you see if the client database name is not set prior to calling OCISessionBegin. To set the client database name, use OCIAttrSet on the server handle with the OCI_ATTR_EXTERNAL_NAME and OCI_ATTR_INTERNAL_NAME attributes.
    These attributes are discussed in chapter 8 of the OCI Programmer's Guide in the section "OCI Support for Transactions".

Maybe you are looking for