Results 1 to 5 of 5
  1. #1
    Join Date
    May 2009
    Location
    Manila, Philippines
    Posts
    16

    Unanswered: Failed verification check

    Hello, I need help with this. One of our developers reported that when he accessed a certain database it returns an error:

    ORA-01033: ORACLE initialization or shutdown in progress

    I tried bouncing the oracle database but it returned an error:

    ERROR at line 1:
    ORA-01122: database file 1 failed verification check
    ORA-01110: data file 1: '/ccb_oradata_01/CD22ARCH/system01.dbf'
    ORA-01251: Unknown File Header Version read for file number 1


    So tried restoring and recovering the datafile/tablespace but it also returned the same error above that the datafile failed the verification check. Researched on the net and I've encountered a solution that would require a back up to trace and get the sql from the trace file and ran it in nomount state. Below is the sql statement:

    CREATE CONTROLFILE REUSE DATABASE "CD22ARCH" NORESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 2540
    LOGFILE
    GROUP 1 '/ccb_oradata_01/CD22ARCH/redo02.log' SIZE 10M,
    GROUP 2 '/ccb_oradata_01/CD22ARCH/redo01.log' SIZE 10M,
    GROUP 3 '/ccb_oradata_01/CD22ARCH/redo03.log' SIZE 10M
    DATAFILE
    '/ccb_oradata_01/CD22ARCH/system01.dbf' SIZE 301000K,
    '/ccb_oradata_01/CD22ARCH/SYSTEM.dbf' SIZE 307200K,
    '/ccb_oradata_01/CD22ARCH/UNDOTBS1.dbf' SIZE 122736K,
    '/ccb_oradata_01/CD22ARCH/SYSAUX.dbf' SIZE 132968K,
    '/ccb_oradata_01/CD22ARCH/CISTS_01.dbf' SIZE 307205K,
    '/ccb_oradata_01/CD22ARCH/TEMP.dbf' SIZE 50000K ,
    '/ccb_oradata_01/CD22ARCH/temp01.dbf SIZE 50000K'
    CHARACTER SET WE8ISO8859P15
    /


    However somethings weird about this line >>>> '/ccb_oradata_01/CD22ARCH/CISTS_01.dbf' SIZE 307205K it keeps on saying that i have computed the incorrect number of blocks but I have used the correct parameters for the formula (e.g. 8192 bytes for the blocks) but it kept saying that I have computed wrong number of blocks.

    Is there any other way to work around this problem? Or since it is a system datafile do I need to just recreate a database? Thanks for the help.

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >Or since it is a system datafile do I need to just recreate a database?
    Yes, or follow documented & tested Restoration Procedure to restored DB from prior backup.

    Who whacked the system01.dbf file?

    Why does the folder seem to involve archiving (CD22ARCH)?
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    May 2009
    Location
    Manila, Philippines
    Posts
    16
    Actually CD22ARCH is the database SID/Name. This database is where we tested archive log mode. I think what caused the system01.dbf file was whacked because the automated backup procedure for this database stop improperly that is why it became unverified. Will just recreate the database.

  4. #4
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >I think what caused the system01.dbf file was whacked because the automated backup procedure for this database stop improperly that is why it became unverified.
    I always thought that back up operation only read data in the database.
    How can reading data corrupt the file?
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  5. #5
    Join Date
    May 2009
    Location
    Manila, Philippines
    Posts
    16
    I really have no idea what happened since I'm not really handling this DB server and this was used by our developers. Anyway thanks I'll just have to re-create this database.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •