DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: Packages are not current

  1. #1
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322

    Packages are not current

    while starting RMAN session, I encounter the following issue.
    Is it an erroneous situation?
    The packages are not current. How can I make them current?

    C:\>rman target 'sys/sys@wip as sysdba'

    Recovery Manager: Release 10.2.0.2.0 - Production on Thu Jul 30 13:55:00 2009

    Copyright (c) 1982, 2005, Oracle. All rights reserved.

    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: WIPRO (DBID=1774606815)
    lucky

  2. #2
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,555
    named package in target database is an older version.
    rman would run anyway but in backwards compatible mode.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  3. #3
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322
    nope RMAN commands return error. There are some issues with Oracle Home in this case. I figured out from metalink. I have set my intended oracle home in system variables but still it didn't work. For the time being, I have uninstalled certain other Oracle components that were not of any need since I encountered this problem on my test machine. Though I know that this is not the right solution but I immediately required my test machine for some RMAN practice.

    So rightly setting the Oracle_Home and then followed by some other OS procedures could have resolved the issue.
    lucky

Posting Permissions

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


Click Here to Expand Forum to Full Width