IdentifiantMot de passe
Loading...
Mot de passe oublié ?Je m'inscris ! (gratuit)
Navigation

Inscrivez-vous gratuitement
pour pouvoir participer, suivre les réponses en temps réel, voter pour les messages, poser vos propres questions et recevoir la newsletter

Administration Oracle Discussion :

[9.2] Probleme suite Supression REDO03.log


Sujet :

Administration Oracle

  1. #41
    Membre régulier
    Profil pro
    Inscrit en
    Décembre 2003
    Messages
    198
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Décembre 2003
    Messages : 198
    Points : 87
    Points
    87
    Par défaut
    Puisque vous êtes dure au mal !

    je vous inflige mon alert :

    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75
    76
    77
    78
    79
    80
    81
    82
    83
    84
    85
    86
    87
    88
    89
    90
    91
    92
    93
    94
    95
    96
    97
    98
    99
    100
    101
    102
    103
    104
    105
    106
    107
    108
    109
    110
    111
    112
    113
    114
    115
    116
    117
    118
    119
    120
    121
    122
    123
    124
    125
    126
    127
    128
    129
    130
    131
    132
    133
    134
    135
    136
    137
    138
    139
    140
    141
    142
    143
    Fri Aug 17 18:01:00 2007
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.7.0.
    System parameters with non-default values:
      processes                = 150
      timed_statistics         = TRUE
      shared_pool_size         = 159383552
      large_pool_size          = 8388608
      java_pool_size           = 159383552
      control_files            = C:\oracle\ora92\orcl\control01.ctl, C:\oracle\ora92\orcl\control02.ctl, C:\oracle\ora92\orcl\control03.ctl
      db_block_size            = 8192
      db_cache_size            = 25165824
      compatible               = 9.2.0.0.0
      db_file_multiblock_read_count= 16
      fast_start_mttr_target   = 300
      _allow_resetlogs_corruption= TRUE
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      undo_retention           = 10800
      remote_login_passwordfile= EXCLUSIVE
      db_domain                = 
      global_names             = FALSE
      instance_name            = orcl
      dispatchers              = (PROTOCOL=TCP) (SERVICE=orclXDB)
      job_queue_processes      = 10
      hash_join_enabled        = TRUE
      background_dump_dest     = C:\oracle\admin\orcl\bdump
      user_dump_dest           = C:\oracle\admin\orcl\udump
      core_dump_dest           = C:\oracle\admin\orcl\cdump
      audit_trail              = DB
      sort_area_size           = 524288
      db_name                  = orcl
      open_cursors             = 300
      star_transformation_enabled= FALSE
      query_rewrite_enabled    = FALSE
      pga_aggregate_target     = 25165824
      aq_tm_processes          = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Fri Aug 17 18:01:03 2007
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Fri Aug 17 18:01:04 2007
    ALTER DATABASE   MOUNT
    Fri Aug 17 18:01:08 2007
    Successful mount of redo thread 1, with mount id 865779488
    Fri Aug 17 18:01:08 2007
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Fri Aug 17 18:01:34 2007
    ALTER DATABASE RECOVER  database using backup controlfile  
    Fri Aug 17 18:01:34 2007
    Media Recovery Start
    WARNING! Recovering data file 1 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 2 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 3 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 4 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 5 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 6 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 7 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 8 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 9 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 10 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 11 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 13 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 14 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 15 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    ORA-279 signalled during: ALTER DATABASE RECOVER  database using backup cont...
    Fri Aug 17 18:01:35 2007
    ALTER DATABASE RECOVER    LOGFILE 'OEM_sqlplus_input_finished'  
    Fri Aug 17 18:01:35 2007
    Media Recovery Log OEM_sqlplus_input_finished
    Errors with log OEM_sqlplus_input_finished
    ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE 'OEM_sqlplus_inp...
    Fri Aug 17 18:01:41 2007
    ALTER DATABASE RECOVER    CANCEL  
    Fri Aug 17 18:01:42 2007
    Media Recovery Cancelled
    Completed: ALTER DATABASE RECOVER    CANCEL  
    Fri Aug 17 18:02:16 2007
    alter database open resetlogs
    Fri Aug 17 18:02:16 2007
    RESETLOGS is being done without consistancy checks. This may result
    in a corrupted database. The database should be recreated.
    RESETLOGS after incomplete recovery UNTIL CHANGE 3891487272613
    Resetting resetlogs activation ID 865774401 (0x339aab41)
    Online log 1 of thread 1 was previously cleared
    Online log 2 of thread 1 was previously cleared
    Fri Aug 17 18:02:22 2007
    Assigning activation ID 865779488 (0x339abf20)
    Thread 1 opened at log sequence 1
      Current log# 3 seq# 1 mem# 0: C:\ORACLE\ORA92\orcl\REDO03.LOG
    Successful open of redo thread 1
    Fri Aug 17 18:02:22 2007
    SMON: enabling cache recovery
    Fri Aug 17 18:02:22 2007
    Errors in file c:\oracle\admin\orcl\udump\orcl_ora_2288.trc:
    ORA-00600: internal error code, arguments: [2662], [906], [246902441], [906], [276153425], [4194721], [], []
     
    Fri Aug 17 18:02:24 2007
    Errors in file c:\oracle\admin\orcl\udump\orcl_ora_2288.trc:
    ORA-00704: bootstrap process failure
    ORA-00600: internal error code, arguments: [2662], [906], [246902441], [906], [276153425], [4194721], [], []
     
    Fri Aug 17 18:02:24 2007
    Error 704 happened during db open, shutting down database
    USER: terminating instance due to error 704
    Fri Aug 17 18:02:24 2007
    Errors in file c:\oracle\admin\orcl\bdump\orcl_smon_2736.trc:
    ORA-00704: bootstrap process failure
     
    Fri Aug 17 18:02:25 2007
    Errors in file c:\oracle\admin\orcl\bdump\orcl_pmon_2728.trc:
    ORA-00704: bootstrap process failure
     
    Instance terminated by USER, pid = 2288
    ORA-1092 signalled during: alter database open resetlogs...

  2. #42
    Expert éminent sénior
    Avatar de orafrance
    Profil pro
    Inscrit en
    Janvier 2004
    Messages
    15 967
    Détails du profil
    Informations personnelles :
    Âge : 46
    Localisation : France

    Informations forums :
    Inscription : Janvier 2004
    Messages : 15 967
    Points : 19 073
    Points
    19 073
    Par défaut
    apparemment c'est un problème de SCN

    ERROR:
    ORA-600 [2662] [a] [b] [c] [d] [e]

    VERSIONS:
    versions 6.0 to 10.1

    DESCRIPTION:

    A data block SCN is ahead of the current SCN.

    The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN
    stored in a UGA variable.

    If the SCN is less than the dependent SCN then we signal the ORA-600 [2662]
    internal error.

    ARGUMENTS:
    Arg [a] Current SCN WRAP
    Arg [b] Current SCN BASE
    Arg [c] dependent SCN WRAP
    Arg [d] dependent SCN BASE
    Arg [e] Where present this is the DBA where the dependent SCN came from.

    FUNCTIONALITY:
    File and IO buffer management for redo logs

    IMPACT:
    INSTANCE FAILURE
    POSSIBLE PHYSICAL CORRUPTION

    SUGGESTIONS:

    There are different situations where ORA-600 [2662] can be raised.

    It can be raised on startup or duing database operation.

    If not using Parallel Server, check that 2 instances have not mounted
    the same database.

    Check for SMON traces and have the alert.log and trace files ready
    to send to support.

    Check the SCN difference [argument d]-[argument b].

    If the SCNs in the error are very close, then try to shutdown and startup
    the instance several times.

    In some situations, the SCN increment during startup may permit the
    database to open. Keep track of the number of times you attempted a
    startup.
    je pense qu'on peut annoncer l'heure de la mort de ta base

  3. #43
    Membre régulier
    Profil pro
    Inscrit en
    Décembre 2003
    Messages
    198
    Détails du profil
    Informations personnelles :
    Localisation : France

    Informations forums :
    Inscription : Décembre 2003
    Messages : 198
    Points : 87
    Points
    87
    Par défaut
    Dégouté de la vie (en info seulement) je suis parti en vacances !!!

    et je reviens et on repart à 0

    aussi merci à vous tous pour vos conseils, patience et énergie

    Bonne semaine

    Luna

Discussions similaires

  1. [NETBEANS 5.5] BUILD AND CLEAN probleme de supression
    Par liquideshark dans le forum NetBeans
    Réponses: 10
    Dernier message: 07/05/2009, 11h02
  2. Probleme de supression des controles sur formulaire
    Par tribaleur dans le forum VBA Access
    Réponses: 6
    Dernier message: 14/02/2008, 13h09
  3. [select]serveur TCP : probleme suite a un accept!
    Par phraides dans le forum Développement
    Réponses: 8
    Dernier message: 27/05/2007, 20h55
  4. Réponses: 4
    Dernier message: 09/05/2006, 09h55

Partager

Partager
  • Envoyer la discussion sur Viadeo
  • Envoyer la discussion sur Twitter
  • Envoyer la discussion sur Google
  • Envoyer la discussion sur Facebook
  • Envoyer la discussion sur Digg
  • Envoyer la discussion sur Delicious
  • Envoyer la discussion sur MySpace
  • Envoyer la discussion sur Yahoo