Results 1 to 8 of 8
  1. #1
    Join Date
    Oct 2003
    Posts
    71

    Unanswered: Backup not working in Oracle 8.1.7.4

    We recently applied Oracle patchset 8.1.7.4. Everything works fine except for backup. It is giving these errors:

    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: backup
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 21:
    PLS-00302: component 'LOCKFORCKPT' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    RMAN-06097: text of failing SQL statement: begin dbms_rcvcat . lockForckpt ; end ;
    RMAN-06099: error occurred in source file: krmk.pc, line: 2121



    Also note that the rman is on a seperate oracle server which is still on 8.1.7

    Is this the cause of the problem.

    Any help is appreciated

    Thanks
    Reema

  2. #2
    Join Date
    Apr 2003
    Location
    Minneapolis, MN
    Posts
    273
    Hi Reema, I am not sure but I guess the old backup will not work for the Upgraded DB (after applying New patchset) because the current controlfile is having entry for this new version of DB. Youd old backup datafiles have old db version. So You cannot apply old baclup.

    You can still use the same RMAN because it is nothing but simply the tools to perform backup and recovery tasks.

    HTH
    Bhavin

    MS Computer Science
    OCP DBA 9i/8i

  3. #3
    Join Date
    Oct 2003
    Posts
    71
    Bhavin,

    Thanks for your reply.
    Then how do run the backup script. Do i need to upgrade RMAN database before taking the backup.

    Thanks
    Reema


    Originally posted by Hings
    Hi Reema, I am not sure but I guess the old backup will not work for the Upgraded DB (after applying New patchset) because the current controlfile is having entry for this new version of DB. Youd old backup datafiles have old db version. So You cannot apply old baclup.

    You can still use the same RMAN because it is nothing but simply the tools to perform backup and recovery tasks.

    HTH

  4. #4
    Join Date
    Jul 2003
    Posts
    2,296
    you should verify/validate all your RMAN backups, also do it logically

    connect to target and catalog through RMAN then run:
    select version from rcver;

    PHP Code:
    RMAN Compatibility Matrix
    In general
    the rules of RMAN compatibility are as follows:


    The versions of the RMAN executable and the target database should be the same 
    (refer to Table B-for other legal combinations). 
    Code:
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96565/compat.htm#631670
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  5. #5
    Join Date
    Apr 2003
    Location
    Minneapolis, MN
    Posts
    273
    Originally posted by The_Duck
    you should verify/validate all your RMAN backups, also do it logically

    connect to target and catalog through RMAN then run:
    select version from rcver;

    PHP Code:
    RMAN Compatibility Matrix
    In general
    the rules of RMAN compatibility are as follows:


    The versions of the RMAN executable and the target database should be the same 
    (refer to Table B-for other legal combinations). 
    Code:
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96565/compat.htm#631670
    Thanks Duck,

    But here, I guess there is no question of compatibility as the RMAN and recovery catalog and Target DB version is same 8.1.7. They are compatible even after applying patchset.
    Bhavin

    MS Computer Science
    OCP DBA 9i/8i

  6. #6
    Join Date
    Jul 2003
    Posts
    2,296
    Good point.
    For some reason I thought the db being backed up was 9i.

    Anyways,
    looks like something is wrong with the catalog db.
    Maybe a manual resync is in order?
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  7. #7
    Join Date
    Oct 2003
    Posts
    71
    Thanks You both for your response.

    Duck,

    How do I do manual resynch??

    The patch has been applied to the target database (so it is 8.1.7.4) but the rman database is 8.1.7.0, will that make a difference.

    Also there is no recovery catalog (uses controlfile)

    Thanks
    Originally posted by The_Duck
    Good point.
    For some reason I thought the db being backed up was 9i.

    Anyways,
    looks like something is wrong with the catalog db.
    Maybe a manual resync is in order?

  8. #8
    Join Date
    Apr 2003
    Location
    Minneapolis, MN
    Posts
    273
    Originally posted by reemagupta

    Also there is no recovery catalog (uses controlfile)

    Thanks
    hi Reema,
    That is the problem I guess. As I mentioned earlier in the same post that the database version in the current controlfile is different than the same in the old backup set. So New (Current ) controlfile does not recognize any old backup. I guess it is no more usefull. You have to take a fresh backup (cold or online) after applying the Patchset.

    HTH
    Bhavin

    MS Computer Science
    OCP DBA 9i/8i

Posting Permissions

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