Why my alert log file is not updated

Dear all,

Please find below my workplace

OS - Windows server 2012

version - 11.2.0.1.0

Server: production server

I checked my alert log file, there is no entry in recent day. He finally stopped on August 31. Please find entry line last two in the alert log file

Mon Aug 31 10:30:23 2015

Archived journal 72088 extra for each sequence 1 79292 0x38b3fdf6 dest ID thread entry 1:

Why it is not updated after August 31.

Please help me on the rest of my points

(1) is there a way to know why he is not up-to-date.

(2) If an order wrongly manually to alert the log entry, so how can I take to update as usual.

Please make sure that you review the correct alerts log by using the following query:

SELECT THE VALUE

V $ diag_info

WHERE name = "Diag Trace"

If this is the right place, then perhaps there is no activity that should be recorded in the log of alert since August 31.

You can manually print something for journal alerts to check this using:

Exec DBMS_System.ksdwrt(2, 'TEST');

Alternatively, you can manually run the command of journal and see if new lines are written to the log of alerts using the following command:

alter system switch logfile;

Tags: Database

Similar Questions

  • Why my index.html file is not changing on the server when I download it using the option at the level of the site to synchronize.

    DW CS6 using, Windows and sometimes try DW CC. I say just put the files on the server.   All, I repeat all, times, I download, the file index.html and sometimes other files, does not update.  I use iPage as my host, but others have tried with the same results.  If I go to iPage file manager and look at the file on the server, this is the old version, before the updates to the file.  Physically, I delete the files from any problem and put the file on the server individually.  Because the way it happened with different hosts, I'm on #4, I think it's a problem of DW.  Any ideas?

    As a un travail work around download, tell him rather than the button synchronize and see if the results are different...

    1 right-click the root directory of local site in the files window

    2. choose the selection command > recently changed

    3. set ' files created or modified in the last: ' for 1 day

    Which will highlight everything that has received a change in any of the site for the last day. Then, you click on the button Put standard to place these files on the server.

    If it doesn't, check your FTP logs (access the Site > advanced > FTP Log) and see if there is anything that is mentioned on the index page.

  • Alerts log files...

    Hello

    It is really very difficult to go through the alerts log files.

    Y at - it no tool or any method is there to play the the alerts in a simple way log files.

    do not read the whole alert log all the time...
    Use the tail command, it will give you the last line as...

    alert_database.log tail - 50 (for the last 50 lines...)

    A new ADRCI command is also there, but I think first of all learn the basics...

    Use Enterprise manager, which helps you easily get an alert.

    Published by: Christel Kumar on October 18, 2012 21:16

  • alert log file notification e-mail

    Hi all

    A DBA, you should check the alert log file again and again for troubleshoting,
    Is there a method to make self as each time that no matter what error / warning encountered in file alert log a mailbox on my Inbox? No matter what script that I put with cron which monitor log file and I would like to know if the log file is good or not...



    Please suggest is possible to do?

    Hello
    You can do this in

    (1) ORACLE ENTERPRISE MANAGER GRID CONTROL OR
    (2) IN WRITING SCRIPTS

    Described by the links below:

    http://download.Oracle.com/docs/CD/B19306_01/server.102/b25159/monitor.htm
    http://www.my-Whiteboard.com/Perl-script-Oracle-database-alert-log-parser-send-email-notification-if-error-is-found/

    Best regards

    Rafi.
    http://rafioracledba.blogspot.com/

  • shell script for oracle alert.log file

    Hi gurus,

    I want to write the shell script to know the last timing 10 stop of the database of the alerts log file. I'm working on oracle 9i.

    Could someone please advice on that.

    Thanks in advance

    Kind regards
    Shaan

    Published by: Shaan_dmp on January 5, 2009 13:27

    Published by: Shaan_dmp on January 5, 2009 13:28

    Use awk. I have not at hand a 9i but here is a very simple version for 10g XE

    My awk file (line numbers for the notes below - don't include them):

    01:BEGIN { prevline = "";} 02:03:/Completed: alter database close/ {print prevline,FS,$0;}04:05:{prevline = $0;}

    The command line and the results (from my alert log 300 k)

    $ awk -f alert.awk.txt alert_xe.logFri Apr 11 18:08:40 2008   Completed: alter database close normalFri May 16 18:53:21 2008   Completed: alter database close normalTue May 20 17:28:23 2008   Completed: alter database close normalThu Jul 17 19:08:52 2008   Completed: alter database close normalFri Aug 15 15:12:48 2008   Completed: alter database close normalWed Nov 05 08:52:59 2008   Completed: alter database close normalFri Nov 14 16:36:03 2008   Completed: alter database close normalTue Dec 09 10:46:23 2008   Completed: alter database close normalMon Jan 05 11:12:22 2009   Completed: alter database close normal

    What it means:

    (1) section START line 01 defines the variable to contain the previous line
    (2) the /search chain / line 03 search marker in the file for a stop, and then performs the requested action (print the time that was in the previous line and then this line; use FS (the field to the awk - space normally separator) as a separator
    (3) on line 05 is a statement that we do on each line - is remembered in case it is the timestamp for the closure.

    Now, you can include several cases corner for closures by adding several models of research etc. For more information, google for examples of awk.

    AWK is really good at this sort of thing!

    HTH

    Nigel cordially

  • When I try to open my file saved PREL - Adobe Premier elements 11, it starts as usual and then "the project appears to be damaged, it cannot be opened. But when I try to open the same file (but not update) of 'Adobe Premiere éléments Auto-Save' it opens

    When I try to open my file saved PREL - Adobe Premier elements 11, it starts as usual and then "the project appears to be damaged, it cannot be opened. But when I try to open the same file (but not update) of 'Adobe Premiere éléments Auto-Save' it opens as usual.  What can I do to be able to open it?

    Good luck to the project is corrupted.

    Be happy, you have an auto save, even if you've lost some work.

  • Deleted alerts log file

    What happens if alert log file is deleted?

    What happens if alert log file is deleted?

    It will be recreated again. See below

    sys@11GDEMO > show parameter background

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    background_core_dump partial string
    / oracle/11 g/diag/rdbms/11gdemo string background_dump_dest
    + / 11gdemo / trace +.
    sys@11GDEMO >! ls - ltr/oracle 11 g/diag/rdbms/11gdemo/11gdemo/trace/al *.
    -rw - r - 1 oracle oinstall 199294 16 Jul 03:11 /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log

    sys@11GDEMO >! RM /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log

    sys@11GDEMO >! ls /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log
    + ls: /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log: no such file or directory.

    sys@11GDEMO > alter system switch logfile;

    Modified system.

    sys@11GDEMO >! ls /oracle/11g/diag/rdbms/11gdemo/11gdemo/trace/alert_11gdemo.log
    */Oracle/11g/diag/RDBMS/11gdemo/11gdemo/trace/alert_11gdemo.log*

    sys@11GDEMO >

  • the log files are not purged

    Hi all

    I have a data store of TT, with layout LogPurge = 1. There are a lot of transactions, manipulating the data store. If I'm not mistaken, the log files, which are older, then the old checkpoint file is deleted automatically by TT, is there is no operation holding them. In my case, the log files are not deleted, so the ls - ltr command prints:

    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 10:49 appdbtt.res1
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 10:49 appdbtt.res0
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 10:49 appdbtt.res2
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:02 appdbtt.log0
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:03 appdbtt.log1
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:03 appdbtt.log2
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:04 appdbtt.log3
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:04 appdbtt.log4
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:04 appdbtt.log5
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:05 appdbtt.log6
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:05 appdbtt.log7
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:06 appdbtt.log8
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:06 appdbtt.log9
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:07 appdbtt.log10
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:07 appdbtt.log11
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:08 appdbtt.log12
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:08 appdbtt.log13
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:09 appdbtt.log14
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:09 appdbtt.log15
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:09 appdbtt.log16
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:10 appdbtt.log17
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:10 appdbtt.log18
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:11 appdbtt.log19
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:11 appdbtt.log20
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:12 appdbtt.log21
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:12 appdbtt.log22
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:13 appdbtt.log23
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:13 appdbtt.log24
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:14 appdbtt.log25
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:14 appdbtt.log26
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:15 appdbtt.log27
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:15 appdbtt.log28
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:16 appdbtt.log29
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:16 appdbtt.log30
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:16 appdbtt.log31
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:17 appdbtt.log32
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:17 appdbtt.log33
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:18 appdbtt.log34
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:18 appdbtt.log35
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:19 appdbtt.log36
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:19 appdbtt.log37
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:20 appdbtt.log38
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:20 appdbtt.log39
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:21 appdbtt.log40
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:21 appdbtt.log41
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:22 appdbtt.log42
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:22 appdbtt.log43
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:22 appdbtt.log44
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:23 appdbtt.log45
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:23 appdbtt.log46
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:24 appdbtt.log47
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:25 appdbtt.log48
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:25 appdbtt.log49
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:25 appdbtt.log50
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:26 appdbtt.log51
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:26 appdbtt.log52
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:27 appdbtt.log53
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:27 appdbtt.log54
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:28 appdbtt.log55
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:28 appdbtt.log56
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:29 appdbtt.log57
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:29 appdbtt.log58
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:30 appdbtt.log59
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:30 appdbtt.log60
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:31 appdbtt.log61
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:31 appdbtt.log62
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:32 appdbtt.log63
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:32 appdbtt.log64
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:33 appdbtt.log65
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:33 appdbtt.log66
    -rw-rw-rw-1 timesten, timesten 487444480 dec 07 11:33 appdbtt.ds0
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:34 appdbtt.log67
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:34 appdbtt.log68
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:35 appdbtt.log69
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:35 appdbtt.log70
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:35 appdbtt.log71
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:36 appdbtt.log72
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:36 appdbtt.log73
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:37 appdbtt.log74
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:37 appdbtt.log75
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:38 appdbtt.log76
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:38 appdbtt.log77
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:39 appdbtt.log78
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:39 appdbtt.log79
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:40 appdbtt.log80
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:40 appdbtt.log81
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:41 appdbtt.log82
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:41 appdbtt.log83
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:42 appdbtt.log84
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:42 appdbtt.log85
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:43 appdbtt.log86
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:43 appdbtt.log87
    -rw-rw-rw-1 timesten, timesten 632098816 dec 07 11:43 appdbtt.ds1
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:44 appdbtt.log88
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:45 appdbtt.log89
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:45 appdbtt.log90
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:46 appdbtt.log91
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:46 appdbtt.log92
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:46 appdbtt.log93
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:47 appdbtt.log94
    -rw-rw-rw-1 timesten, timesten 67108864 dec 07 11:47 appdbtt.log95
    -rw-rw-rw-1 timesten, timesten 4767744 dec 07 11:47 appdbtt.log96

    As you can see, I have 67 log files older than the old checkpoint file. Now, if I enter the DS in ttIsql and call ttLogHolds I get:
    Command > call ttLogHolds();
    < 0, 38034792, replication, APPDBTT:_ORACLE >
    67 44319520, checkpoint, < appdbtt.ds0 >
    88 45855168, checkpoint, < appdbtt.ds1 >
    3 lines found.

    What can be the problem?

    Thanks in advance:
    Dave

    This bookmark

    < 0,="" 38034792,="" replication="" ,="" appdbtt:_oracle="">

    indicates that the bookmark AWT has not moved since 0 log file. Since the AWT is performed by the replication agent, it retains a bookmark to follow where its has reached in reading through files looking for operations against any cachegroups AWT transaction logs. It seems that somehow an operation against a cachegroup AWT was not committed, which means that he cannot be sent to Oracle, recognized and settled the bookmark. Once the bookmark moves into a new transaction log file, all the old log files can then be purged.

    You might be able to identify any transaction cease using ttXactAdmin and looking for the locks held against AWT cachegroups.

  • Vista service pack 2 error code 80092004__run updated stand-alone responsible package__down ServicePack 2__run stand-alone service pack 2___ error code not found crypt_E_ (0 x 80092004) __could the log file is not open

    Service pack 2 80092004 Vista error code
    Run the stand-alone update package
    Load service pack 2
    run stand-alone service pack 2
    error code not found crypt_E_ (0 x 80092004)
    could not open log file

    https://support.Microsoft.com/OAS/default.aspx?PRID=13014&Gprid=582034&St=1

    Free unlimited installation and compatibility support is available for Windows Vista, but only for Service Pack 2 (SP2). This support for SP2 is valid until February 26, 2010.

    Microsoft free support for Vista SP2 at the link above.

    See you soon.

    Mick Murphy - Microsoft partner

  • Cannot publish get error message - log file is not being created

    When you try to publish a project of FlashHelp, I get an error message window that says "Publishing has been cancelled. "Cannot create the file: (name of the project) .log"

    When I click OK in the message window, the publish process will stop. However, if I look in the SSL folder, I see the log file. It is a text file.

    I had this problem in January 09, but it seemed to be a problem with the password and the access path in the command FTP window. I fixed it, and it worked fine. However, I have not published since the end of January. Now, when I try to publish, it gives me the same error message. I checked and examined the window FTP fields, and they are very good. But I still get the error message and cannot publish.

    Why?

    I need to get this problem fixed as soon as POSSIBLE and make sure it won't happen again. What is strange, is that I have 3 other projects and it is the only 1 who receives this error message.

    Colum
    Thanks for the memory jog, that was the problem. They had to move the server, so the ftp info was wrong. It is probably the same problem last time, but I couldn't remember because I tried so many things before we had solved it.

  • Archive the log files are not register with oracle 10g are

    Hello

    I have oracle 10.2.0 Linux redhat 4. my database is archivelog since that sequence mode no 30

    but when I backup all the files in the archives to help newspapers.

    rman> backup archivelog all delete input.

it backups up from sequence 67 

because.

SQL> select sequence# from v$archived_log;

 SEQUENCE#
----------
        67
        68
        69
        70
        71
        72
        73
        74
        75
        76
        77

 SEQUENCE#
----------
        78
        79
        80
        81
        82
        83
        84
        85
        86
        87
        88

 SEQUENCE#
----------
        89
        90
        91
        92
        93
        94
        95
        96
        97
        98
        99

 SEQUENCE#
----------
       100
       101
       102
       103
       104
       105
       106
       107
       108
       109
       110

 SEQUENCE#
----------
       111
       112
       113
       114
       115
       116
       117
       118
       119
       120
       121

 SEQUENCE#
----------
       122

56 rows selected.

while i left with

[oracle@Oracledatabas ArchiveDest]$ ls
1_30_694492901.dbf  1_40_694492901.dbf  1_50_694492901.dbf  1_60_694492901.dbf
1_31_694492901.dbf  1_41_694492901.dbf  1_51_694492901.dbf  1_61_694492901.dbf
1_32_694492901.dbf  1_42_694492901.dbf  1_52_694492901.dbf  1_62_694492901.dbf
1_33_694492901.dbf  1_43_694492901.dbf  1_53_694492901.dbf  1_63_694492901.dbf
1_34_694492901.dbf  1_44_694492901.dbf  1_54_694492901.dbf  1_64_694492901.dbf
1_35_694492901.dbf  1_45_694492901.dbf  1_55_694492901.dbf  1_65_694492901.dbf
1_36_694492901.dbf  1_46_694492901.dbf  1_56_694492901.dbf  1_66_694492901.dbf
1_37_694492901.dbf  1_47_694492901.dbf  1_57_694492901.dbf
1_38_694492901.dbf  1_48_694492901.dbf  1_58_694492901.dbf
1_39_694492901.dbf  1_49_694492901.dbf  1_59_694492901.dbf
[oracle@Oracledatabas ArchiveDest]$

i have backup of archive log as 

RMAN> list backup of archivelog all;


List of Backup Sets
===================

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
3       136.49M    DISK        00:00:08     27-AUG-09
        BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: TAG20090827T061019
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_27/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp

  List of Archived Logs in backup set 3
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    37      1530188    18-AUG-09 1549890    19-AUG-09
  1    38      1549890    19-AUG-09 1584124    19-AUG-09
  1    39      1584124    19-AUG-09 1628757    19-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
7       181.96M    DISK        00:00:12     27-AUG-09
        BP Key: 7   Status: AVAILABLE  Compressed: NO  Tag: TAG20090827T222915
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_27/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp

  List of Archived Logs in backup set 7
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    63      2413676    26-AUG-09 2435738    26-AUG-09
  1    64      2435738    26-AUG-09 2472234    27-AUG-09
  1    65      2472234    27-AUG-09 2515317    27-AUG-09
  1    66      2515317    27-AUG-09 2546805    27-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
9       15.94M     DISK        00:00:02     28-AUG-09
        BP Key: 9   Status: AVAILABLE  Compressed: NO  Tag: TAG20090828T001745
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_28/o1_mf_annnn_TAG20090828T001745_59gpmc0s_.bkp

  List of Archived Logs in backup set 9
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    30      1328116    17-AUG-09 1330698    17-AUG-09
  1    31      1330698    17-AUG-09 1343639    17-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
11      104.87M    DISK        00:00:07     28-AUG-09
        BP Key: 11   Status: AVAILABLE  Compressed: NO  Tag: TAG20090828T012913
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_28/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp

  List of Archived Logs in backup set 11
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    31      1330698    17-AUG-09 1343639    17-AUG-09
  1    32      1343639    17-AUG-09 1386340    17-AUG-09
  1    33      1386340    17-AUG-09 1418708    17-AUG-09

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
18      2.44G      DISK        00:03:18     17-SEP-09
        BP Key: 18   Status: AVAILABLE  Compressed: NO  Tag: TAG20090917T002120
        Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_09_17/o1_mf_annnn_TAG20090917T002120_5c3gb2m2_.bkp

  List of Archived Logs in backup set 18
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    67      2546805    27-AUG-09 2571963    28-AUG-09
  1    68      2571963    28-AUG-09 2610800    28-AUG-09
  1    69      2610800    28-AUG-09 2647832    28-AUG-09
  1    70      2647832    28-AUG-09 2668839    28-AUG-09
  1    71      2668839    28-AUG-09 2705408    29-AUG-09
  1    72      2705408    29-AUG-09 2749633    29-AUG-09
  1    73      2749633    29-AUG-09 2783675    30-AUG-09
  1    74      2783675    30-AUG-09 2826464    30-AUG-09
  1    75      2826464    30-AUG-09 2860499    30-AUG-09
  1    76      2860499    30-AUG-09 2903504    31-AUG-09
  1    77      2903504    31-AUG-09 2943108    31-AUG-09
  1    78      2943108    31-AUG-09 2977859    31-AUG-09
  1    79      2977859    31-AUG-09 2998785    01-SEP-09
  1    80      2998785    01-SEP-09 3042779    01-SEP-09
  1    81      3042779    01-SEP-09 3086898    01-SEP-09
  1    82      3086898    01-SEP-09 3103245    02-SEP-09
  1    83      3103245    02-SEP-09 3147628    02-SEP-09
  1    84      3147628    02-SEP-09 3192216    02-SEP-09
  1    85      3192216    02-SEP-09 3208480    02-SEP-09
  1    86      3208480    02-SEP-09 3248106    03-SEP-09
  1    87      3248106    03-SEP-09 3294064    03-SEP-09
  1    88      3294064    03-SEP-09 3323611    03-SEP-09
  1    89      3323611    03-SEP-09 3352060    04-SEP-09
  1    90      3352060    04-SEP-09 3399516    04-SEP-09
  1    91      3399516    04-SEP-09 3440740    04-SEP-09
  1    92      3440740    04-SEP-09 3457884    05-SEP-09
  1    93      3457884    05-SEP-09 3485157    05-SEP-09
  1    94      3485157    05-SEP-09 3523208    05-SEP-09
  1    95      3523208    05-SEP-09 3558325    05-SEP-09
  1    96      3558325    05-SEP-09 3600414    06-SEP-09
  1    97      3600414    06-SEP-09 3642729    06-SEP-09
  1    98      3642729    06-SEP-09 3678479    07-SEP-09
  1    99      3678479    07-SEP-09 3720642    07-SEP-09
  1    100     3720642    07-SEP-09 3748794    07-SEP-09
  1    101     3748794    07-SEP-09 3777963    08-SEP-09
  1    102     3777963    08-SEP-09 3823393    08-SEP-09
  1    103     3823393    08-SEP-09 3865230    08-SEP-09
  1    104     3865230    08-SEP-09 3880510    09-SEP-09
  1    105     3880510    09-SEP-09 3906888    09-SEP-09
  1    106     3906888    09-SEP-09 3961086    09-SEP-09
  1    107     3961086    09-SEP-09 3982103    10-SEP-09
  1    108     3982103    10-SEP-09 4034528    10-SEP-09
  1    109     4034528    10-SEP-09 4055556    11-SEP-09
  1    110     4055556    11-SEP-09 4115268    11-SEP-09
  1    111     4115268    11-SEP-09 4128557    12-SEP-09
  1    112     4128557    12-SEP-09 4165104    12-SEP-09
  1    113     4165104    12-SEP-09 4202850    12-SEP-09
  1    114     4202850    12-SEP-09 4258353    13-SEP-09
  1    115     4258353    13-SEP-09 4298900    14-SEP-09
  1    116     4298900    14-SEP-09 4341046    14-SEP-09
  1    117     4341046    14-SEP-09 4365180    15-SEP-09
  1    118     4365180    15-SEP-09 4424992    15-SEP-09
  1    119     4424992    15-SEP-09 4439538    15-SEP-09
  1    120     4439538    15-SEP-09 4489259    16-SEP-09
  1    121     4489259    16-SEP-09 4532807    16-SEP-09
  1    122     4532807    16-SEP-09 4548893    17-SEP-09



and when i try

RMAN> backup archivelog from sequence 30 until sequence 66;

Starting backup at 17-SEP-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 09/17/2009 04:01:25
RMAN-20242: specification does not match any archive log in the recovery catalog


when i try to restore database on testing server it ask me for



MAN> recover database until sequence 121;

Starting recover at 17-SEP-09
using channel ORA_DISK_1

starting media recovery

channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=37
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=38
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=39
channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp tag=TAG20090827T061019
channel ORA_DISK_1: restore complete, elapsed time: 00:00:17
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=63
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=64
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=65
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=66
channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp tag=TAG20090827T222915
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=31
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=32
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=33
channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp tag=TAG20090828T012913
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_31_694492901.dbf thread=1 sequence=31
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_32_694492901.dbf thread=1 sequence=32
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_33_694492901.dbf thread=1 sequence=33
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf thread=1 sequence=34
archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf thread=1 sequence=35
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/17/2009 03:01:31
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf'
ORA-00310: archived log contains sequence 34; sequence 35 required
ORA-00334: archived log: '/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf'
    My question is why my 30 to 66 sequence archivelog file are not saved with the database in v$ archived_log and how to solve this problem.

    Thank you
    Umesh

    You may need to increase the CONTROL_FILE_RECORD_KEEP_TIME value.

    If the archivelogs are still on the disk, you can try to catalog them with:

    RMAN> catalog start with '/home/oracle/DataBaseBackups/ArchiveDest/;

    or if you don't need the file you can simply remove the o/s and run the following:

    RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;

  • Recent files list not updated in Photoshop CC 2015

    After the update, the new window opening do not display the last open files but only the ones I used before the update.

    Hi joseebelanger,

    Click file > open recent item > clear recent files list.

    Restart Photoshop and then try and open the pictures and see if they show under recent files or not.

    Kind regards

    Tanuj

  • "Recent files" are not updated.

    I'm on the latest version of Photoshop CC 2015, and my list of recent files simply don't is not updated at all.

    I have Photoshop installed on 2 computers and it works fine on one but not the other...

    Is anyone else having the same problem?

    Hi NextGenEnglish,

    I'm sorry for the inconvenience caused to you.

    Click file > open recent item > clear recent files list.

    Let me know if it helps.

    ~ UL

  • export photoshop file is not updated

    Hello

    Recently, I noticed that when I export to photoshop and save the file isn't updated in the develop module. It does not update in the library module, but when I go to develop it, it comes back.

    Lightroom cc 2015.1.1

    Mac Yosemite 10.10.5

    This bug has been reported in Adobe official feedback forum: Lightroom CC 2015.1.1: develop module does not detect external changes to the original file.  Adobe said that they were able to reproduce the problem and are working.  Please add your vote and notice to this bug report, because even if Adobe has acknowledged the bug does not mean they will implement a solution in the next version.  A bit more likely that they will give priority, your vote will make the fix.

  • Who writes the alert log file?

    Hi guys,.

    I tried to answer this question...

    What process (process backgroud) written in newspaper alert?

    Is not "one" but all background processes can / write for her.

    The archiver written for her. LogWriter can write (if you have log_checkpoints_to_alert).
    When a background process detects that another died, the former written to the alert log in before you panic the instance and kill him.

    An ALTER SYSTEM command issued by the server process for your database session will also write to the alert.log

    (Alternatively, you can call a specific procedure of data to write in it - but it is not documented).

    Hemant K Collette

Maybe you are looking for