RMAN-00554: initialization of internal recovery manager package failed

Hi Folks,
I am getting the below mentioned error........
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04004: error for recovery catalog database:ORA_28000: The account is locked.
I have also tried unlocking the account & now its UNLOCKED but again i am getting the same message....
Please assist..!
Thanks in advance..!

ORA-28000: the account is locked
Cause: The user has entered wrong password consequently for maximum number of times specified by the user"s profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account
Action: Wait for PASSWORD_LOCK_TIME or contact DBA
I think you have specified a profile to the user for recovery manager where failed_login_attempts was set. Because of wrong password attempts the account got locked.
Unlocking of account should work.. Check whether you can login to sql*plus ?
Change the profile's FAILED_LOGIN_ATTEMPTS value and try once again.

Similar Messages

  • Rman command fails with "RMAN-00554: initialization of internal RMAN"

    Hi
    I am at cross roads with no direction. 2 things and most like cause for the issue is same
    1)rman target rman1/rman1@ppmqa
    Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 10:34:46 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-01031: insufficient privileges
    2) sqlnet userid/passwd@db1 "/as sysdba" works some times and fails with insufficient privileges" some times
    ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
    SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:55 2010
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    ERROR:
    ORA-01031: insufficient privileges
    ppmqa1 10:24 AM sqrac202a:/oracle/base/diag/tnslsnr/sqrac202a/listener/trace > sqlplus rman1/rman1@ppmqa1 "as sysdba"
    SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 16 10:24:57 2010
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
    Data Mining and Real Application Testing options
    SQL>
    Information on environment and let me know if you need or know any more details... thanks in advance.
    CRS Version 11201 and so DB
    current parameters:
    SQL> show parameter remote
    NAME TYPE VALUE
    remote_dependencies_mode string TIMESTAMP
    remote_listener string sqrac202-scan.frxntnyc.frx2.co
    m:1521
    remote_login_passwordfile string EXCLUSIVE
    remote_os_authent boolean FALSE
    remote_os_roles boolean FALSE
    result_cache_remote_expiration integer 0
    SQL> select * from v$pwfile_users
    USERNAME SYSDB SYSOP SYSAS
    SYS TRUE TRUE FALSE
    RMAN1 TRUE TRUE FALSE
    sqlnet.ora from GRID Home
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    ADR_BASE = /oracle/base
    #################################

    I found solution just now, this is very simple i was not aware this but this is how it working
    Hope this helps
    I granted sysdba from node A but not from node B, thinking that if you grant any privilege at instance level that is applicable to db level but that is not the case with sysdba privs
    so i need to grant it from both nodes A and B.
    here is the output
    test case
    initially no entry for instance 2
    1) select * from gv$pwfile_users;
    INST_ID USERNAME SYSDB SYSOP SYSAS
    2 SYS TRUE TRUE FALSE
    1 SYS TRUE TRUE FALSE
    1 RMAN1 TRUE TRUE FALSE
    2) grant sysdba to rman1 -- this I did at NODE B or instance 2
    3) SQL> select * from gv$pwfile_users;
    INST_ID USERNAME SYSDB SYSOP SYSAS
    2 SYS TRUE TRUE FALSE
    2 RMAN1 TRUE FALSE FALSE
    1 SYS TRUE TRUE FALSE
    1 RMAN1 TRUE TRUE FALSE
    4) I am able to connect remotely
    C:\Documents and Settings\kthoka> sqlplus rman1/rman1@ppmqa "as sysdba"
    SQL*Plus: Release 10.2.0.3.0 - Production on Thu Dec 16 13:59:20 2010
    Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management
    OLAP,
    Data Mining and Real Application Testing options
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    ppmqa2
    5) rman also working fine
    ppmqa 03:00 PM sqrac202a:/oracle/NSQ/112_64/dbs > rman target rman1/rman1@ppmqa
    Recovery Manager: Release 11.2.0.1.0 - Production on Thu Dec 16 15:00:32 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: PPMQA (DBID=774170541)
    RMAN> exit
    Recovery Manager complete.

  • Recovery Manager Failure: Failed to create EFI partition

    Envy 15-1055SE
    Windows 7 Home Premium 64 bit
    The original HD failed (500GB) and it was replaced it with a working unit of the same size (500GB). Since the hard drive was completely dead and I no longer had access to the recovery partition we installed Windows 7 Home Premium 64bit on the new hard drive, assuming we could use my Windows Key and then just download all the applicable drivers from the HP site. Windows did install and was running, but since my key was not compatible and trying to get all the correct drivers for my specific notebook was essentially impossible I rush ordered the recovery discs form HP. Once received, we then attempted to restore the system using recovery media supplied by HP (590684-003 , WINDOWS 7 PREMIUM 64B + SUPP 2 RECOVERY).
    Multiple attempts were made with the replacement HD raw, formatted or untouched from the last failure. I have also downloaded and used the Cyberlink Recover Discs Utility from the HP site that supposed to resolve Recovery Discs issues, but all attempts ended exactly the same way.  After using and ejecting all three recovery discs Recovery Manager terminated with the same error:
    Recovery Manager
    The Recovery Attempt has Failed.
    Select one of the following buttons
    [Savelog]   [Details]   [Retry]
    Pressing [Details] results in this message:
    CTO ERRORFLG
    Fail to Create EFI Partition...
    Diskpart return error level [-2147024809]...
    Retrying ultimately loops to the same error.
    So, what now???

    So I took your advice and called HP support. As you stated, they recommended new recovery discs, which they sent me and I recieved today. So I went through the whole process again and got the same error.
    When I was on the phone with support they mentioned that I could have purchased a replacement drive from them for 2.5 times the price i paid for mine. And they didn't confirm if that would fix my problem or come with everything already installed.
    At this point I'm at a loss, I don't have the money to pay that much for a "possible" solution, when I have a perfectly fine working new hard drive already.
    There has to be a solution out there, as everyone I talked doesn't understand why the recovery disc/process isn't working. Can someone please provide some useful advise/suggestions?

  • Recovery Manager is failing to read backup files from disc

    Product Name:
    HP G56-129WM
    Operating System:
    Windows 7
    I used the HP Recovery Manager (F11) to backup my files instead of using the Windows backup. The HP Recovery Manager back uped my files on 2 dvd discs. I then restored my laptop to factory settings. When I go to restore my files, it will only go to 40% and then ask me to insert backup DISC 2. When I insert the disc, it fails to read it. The disc pops out and I keep getting a request to insert DISC 2. What is going on?
    This question was solved.
    View Solution.

    I have a related but different issue with file back-up using HP recovery manager.
    I have a Pavilion g7-1070us laptop that failed to start and simply displays a blue-screen with a blinking cursor (no error message). I could NOT get into safe-mode by hitting F8, but was able to activate the “HP recovery manager” by hitting F11. I was trying to back-up my files before triggering the system restore. It asked me what types of files to back-up, then scanned the computer for these files and was finalizing the files for back-up; then suddenly an error message showed up saying something like "No storage device detected. Make sure the removable disc drive is connected to computer". But I have both a DVD sitting in the optical drive and a USB drive attached!!!!!! Apparently the recovery manager doesn’t see them?
    Can someone throw me a life-saver here? If I cannot recover my files, I cannot proceed with the system restore and I am forever stuck here!!!!!!
    Please help!!!! Much appreciated!!

  • 0xc000025 - Trying Recovery System via Recovery Manager: Windows failed to start.

    Name: Pavilion dv4-2161nr
    Prod. Number: WA691UA#ABA
    Windows 7  64-bit
      I splitted original Hard Disk Partition in three partitions.  I formatted those two not containing O.S.  Now I want to format the partition containing the O.S.
      1)  If I choose "Recovery System", will it format all three partitions?  Or will it format the partition I choose to?
      2)  I tryed "Recovery System", but it failed.  What can I do?
         2.1)  I made Recovery DVDs when first used the PC.  It loads but it never runs.  It's like theres no AutoRun, and there's no ".exe" to execute when I open the first DVD Recovery via Windows Explorer.  What am I missing?
         2.2)  I tryed Recovery System via Recovery Manager.  System shuts down and starts reiniciating but it gives the following message "Windows Boot Manger: Windows failed to start.  A recent hardware of software change might be the problem.  Status: 0xc000025.  The boot selection failed because a required device is inacessible".  What can I do?
         Regards,
         Rafael.

    I tested the Hard Drive and it passed 100% ok.
    I tested the Memory and it passed 100% ok.
    My PC runs a Win 7 Home Premium.
    I've just run a Win 7 Ultimate CD Installation.  It formatted the System Partition, but I couldn't get Win 7 installed because when I filled in my Product Key it said the Product Key wasn't right.  Is it because Product Key for Win 7 Home Premium wouldn't work on a Win 7 Ultimate installation?
    I hoped the Hard Drive would be ok after it had been formatted while I tryed Win 7 Ultimate installation.  So I tryed once again to boot with HP Recovery Disc.  It stopped at 23% once again.  Until 23% there are all noises that get me thinking PC is running ok.  When it get up to 23% all noises just stop.
    Any ideias?
    And thanks once again.
    Rafael.

  • RMAN-00554...How to resolve

    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-04063: package body "SYS.DBMS_BACKUP_RESTORE" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_BACKUP_RESTORE"
    ORA-06512: at line 1
    RMAN-04015: error setting target database character set to WE8MSWIN1252
    Hi,
    i am getting this error ,when access a particular database through RMAN.
    while checking NLS_characterset in props$ it shows WE8MSWIN1252 only,
    How to resolve this errors...?
    null

    Version-10.2.0.1.0
    Hi pavan,
    while compiling the DBMS_BACKUP_RESTORE
    by giving the command
    ALTER PACKAGE DBMS_BACKUP_RESTORE COMPILE body;
    it giving compliation error ,
    DBMS_BACKUP_RESTORE must be declared & DBMS_SYS_ERROR must be declared.
    Dynamic view (props$) will reflect the character set.. is there any other method to see the character set...?

  • RMAN-00554 with ORA-12638

    Hi,
    I'm receiving the following error when I try to start RMAN from a command prompt. I can connect to the database from the Enterprise Manager and from SQLPlus without any problems. I've read about removing the sqlnet.authentication_services line from sqlnet.ora, but I don't know if I should since the database connects fine outside of RMAN:
    C:\>rman target sys/password@DB1
    Recovery Manager: Release 10.2.0.1.0 - Production on Mon May 15 10:01:40 2006
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-12638: Credential retrieval failed
    Thanks,
    Nora

    Hi,
    In 'C:\oracle\product\10.2.0\db_1\NETWORK\ADMIN', my files look like this (the line in sqlnet.ora is still present-- i haven't removed or changed it yet):
    TNSNAMES.ORA
    # Generated by Oracle configuration tools.
    DB1 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = host1)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = db1)
    SQLNET.ORA:
    # This file is actually generated by netca. But if customers choose to
    # install "Software Only", this file wont exist and without the native
    # authentication, they will not be able to connect to the database on NT.
    SQLNET.AUTHENTICATION_SERVICES = (NTS)
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    LISTENER.ORA:
    # listener.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = DB1)
    (ORACLE_HOME = C:\oracle\product\10.2.0\Db_1)
    (GLOBAL_DBNAME = DB1)
    LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = host1)(PORT = 1521))
    I don't get ORA-01031 in RMAN with this configuration, but I do get ORA-12638.
    Otherwise, I can connect fine to my database if I don't use 'connect / as sysdba'.
    Thanks again,
    Nora

  • RMAN-00554, RMAN-04005, ORA-12154: TNS:could not resolve the connect identifier specified

    Hi Gurus,
    I need your help!
    I am implementing dataguard through RMAN, where my primary database is mydb and my standby database is orcl. I am pasting step by step process and atlast the error message which I am getting. Please do help me to resolve it.
    [oracle@localhost ~]$ . oraenv
    ORACLE_SID = [orcl] ? mydb
    The Oracle base for ORACLE_HOME=/u01/home/oracle/product/11.2.0/db_1 is /u01/app/oracle
    [oracle@localhost ~]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.1.0 Production on Sun Jan 5 09:24:56 2014
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select db_unique_name, database_role, open_mode from v$database;
    DB_UNIQUE_NAME                 DATABASE_ROLE    OPEN_MODE
    mydb_un                        PRIMARY          READ WRITE
    SQL> show parameter instance_name
    NAME                                 TYPE        VALUE
    instance_name                        string      mydb
    SQL> show parameter service_names
    NAME                                 TYPE        VALUE
    service_names                        string      mydb_un
    SQL> !
    [oracle@localhost ~]$ . oraenv
    ORACLE_SID = [oracle] ? orcl
    ORACLE_HOME = [/home/oracle] ? /u01/app/oracle/product/11.2.0/dbhome_1
    The Oracle base for ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1 is /u01/app/oracle
    [oracle@localhost ~]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.1.0 Production on Sun Jan 5 09:20:04 2014
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select host_name, status from v$instance;
    HOST_NAME                                                        STATUS
    localhost.localdomain                                            STARTED
    SQL> show parameter instance_name
    NAME                                 TYPE        VALUE
    instance_name                        string      orcl
    SQL> show parameter service_names
    NAME                                 TYPE        VALUE
    service_names                        string      orcl_un
    SQL> !
    [oracle@localhost ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 05-JAN-2014 09:27:44
    Copyright (c) 1991, 2009, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
      TNS-00511: No listener
       Linux Error: 2: No such file or directory
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date                05-JAN-2014 08:17:31
    Uptime                    0 days 1 hr. 10 min. 15 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Log File         /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
    Services Summary...
    Service "mydbXDB" has 1 instance(s).
      Instance "mydb", status READY, has 1 handler(s) for this service...
    Service "mydb_un" has 1 instance(s).
      Instance "mydb", status READY, has 1 handler(s) for this service...
    Service "orcl_un" has 1 instance(s).
      Instance "orcl", status BLOCKED, has 1 handler(s) for this service...
    The command completed successfully
    [oracle@localhost ~]$ tnsping mydb
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 05-JAN-2014 09:27:54
    Copyright (c) 1997, 2009, Oracle.  All rights reserved.
    Used parameter files:
    /u01/home/oracle/product/11.2.0/db_1/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = mydb_un)))
    OK (0 msec)
    [oracle@localhost ~]$ tnsping orcl
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 05-JAN-2014 09:28:03
    Copyright (c) 1997, 2009, Oracle.  All rights reserved.
    Used parameter files:
    /u01/home/oracle/product/11.2.0/db_1/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl_un)))
    OK (0 msec)
    [oracle@localhost admin]$ more listener.ora
    # listener.ora Network Configuration File: /u01/home/oracle/product/11.2.0/db_1/network/admin/listener.ora
    # Generated by Oracle configuration tools.
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
          (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = mydb_un)
          (ORACLE_HOME = /u01/home/oracle/product/11.2.0/db_1)
          (SID_NAME=mydb)
        (SID_DESC =
          (GLOBAL_DBNAME = orcl_un)
          (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
          (SID_NAME = orcl)
    ADR_BASE_LISTENER = /u01/app/oracle
    [oracle@localhost admin]$ more tnsnames.ora
    # tnsnames.ora Network Configuration File: /u01/home/oracle/product/11.2.0/db_1/network/admin/tnsnames.ora
    # Generated by Oracle configuration tools.
    MYDB =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = mydb_un)
    ORCL =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = orcl_un)
    [oracle@localhost ~]$ rman target sys/engineer@mydb auxiliary sys/engineer@orcl
    Recovery Manager: Release 11.2.0.1.0 - Production on Sun Jan 5 09:30:59 2014
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-12154: TNS:could not resolve the connect identifier specified
    [oracle@localhost ~]$
    Please let me know why I am getting this error if everything is fine above.
    Regards,
    Michel

    Here's your issue
    (HOST=localhost.localdomain)
    If you are going to use "localhost" at least fake it by adding an entry in your /etc/hosts files
    Example ( add to both servers so they can see each other )
    192.168.0.20               primary.localdomain   primary
    192.168.0.21               standby.localdomain   standby
    Does the "hostname" return localhost.localdomain? Setup something so RMAN has something to connect to.
    The "/etc/hosts" file must contain a fully qualified name for the server.
    <IP-address> <fully-qualified-machine-name> <machine-name>
    localhost.localdomain is 127.0.0.1, you don't want that.
    Best Regards
    mseberg

  • Fatal error in recovery manager

    Hi,
    I am trying to restore my DB for disaster recovery, I have taken a backup earlier in flash_recovery_area with controlfile autobackup on.
    I have successfully restored spfile and controlfiles, but when I am running restore database, rman is crashing:
    RMAN> startup force mount;
    RMAN> restore database;
    Starting restore at 17-JUL-13
    Starting implicit crosscheck backup at 17-JUL-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=170 device type=DISK
    Crosschecked 4 objects
    Finished implicit crosscheck backup at 17-JUL-13
    Starting implicit crosscheck copy at 17-JUL-13
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 17-JUL-13
    searching for all files in the recovery area
    cataloging files...
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    ORA-01092: ORACLE instance terminated. Disconnection forced
    RMAN-03002: failure of restore command at 07/17/2013 23:44:08
    ORA-03113: end-of-file on communication channel
    Process ID: 10307
    Session ID: 162 Serial number: 9
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    please help me out identifying the issue.
    thanks,

    this directory is actually empty : /scratch/oradba/db/apps_st/zDB/dat/
    It had all data files earlier, but to try disaster recovery I manually removed all of them to bring them back from backup.
    I am following all these steps: Hemant's Oracle DBA Blog: RMAN Backup and Recovery for Loss of ALL files
    but at restore database, its crashing out. 

  • Hp recovery manager pavilion dv7 windows 7 64bit not installed correctly

    I'm trying to reinstall Recovery Manager after a hard disk replacement. I have a HP Pavilion dv7 4060si running Windows 7 Home Premium 64 bit. I've downloaded sp45602 and installed it. It did not install properly. When I went to the SwSetup/sp45602 folder and clicked RecoveryMgr.exe I got a message that a DZIP32.dll file was missing. I downloaded it and dragged it into the SwSetup/sp45602 folder. Then I got a message that HardDisk.dll was missing. I downloaded it and dragged it into the SwSetup/sp45602 folder. Then I got a message that PRRC.dll was missing. I downloaded it and dragged it into the SwSetup/sp45602 folder. Now I get a message in Turkish that translated by Google reads: Recovery Manager driver failed to start. To apply you will need to reinstall.
    I've deleted the SwSetup/sp45602 folder, downloaded the sp45602.exe again and gone through the same process to get the same result. What is missing from my software?

    Did you resolve this?
    I'm getting the same issues!

  • ORACLE8: RECOVERY MANAGER 사용 방법(RMAN)

    제품 : ORACLE SERVER
    작성날짜 : 1997-11-17
    Oracle 8 NEW : Recovery manager 란 ?
    ====================================
    - 소개
    Oracle 8 은 새로운 backup와 recovery 방법인 Recovery manager 를 제공한다.
    Recovery manager(이하 RMAN) 는 backup,restore,recover process를 관리하는
    tool 이다. Oracle Enterprise Manager 를 통해 GUI mode 로 가능하고,
    rman 이라는 command line interface 를 함께 제공한다.
    특히, OS device control 기능이 보완 되었기 때문에, 현재 backup catalog 를
    유지하고, 이 정보를 이용해 OS level 에서 file 을 auto-restore 해 주기
    때문에, database recovery 전에 file 을 manual 하게 restore 할 필요가
    없어졌다.
    Incremental backup 을 제공하고, backup 이나 restore 중에 current block
    detection 을 해 주며(v$backup_corruption, v$copy_corruption 또는 alert
    log 에 report), Rman 작업시에 parallelization 을 제공하며, open database
    backup 동안 특별한 redo 를 발생하지 않는다.
    - 구조
    Recovery               
    manager in OEM(oracle          
              enterprise      ---> Database
              manager) <---     (catalog)          
    or RMAN
         /| |
         | |/
    DATABASE     ---> OS
    (target to backup) <--- Device
    - 구성 요소 설명
    1) recovery manager
    Command 를 해석하고, backup, restore, recover 를 실행하기 위해 target
    database 로 command 를 전달한다. recovery catalog 를 update 한다. 실행
    과정을 조정, 모니터링 한다.
    2) Target database
    backup,restore,recovery action 이 수행될 데이타베이스
    3) Recovery Catalog
    Information 저장장소. 즉, target database 의 물리적 스키마, datafile 과
    archivelog 의 backup sets 과 pieces, backup script 등을 포함하고 있음.
    rman 작업시 recovery catalog 정보를 이용한다.
    4) channel
    allocation channel 은 target database 의 backup,restore,recover 에 대한
    server process 초기화를 한다. 즉, 이 channel 은 disk 를 포함 기타 OS
    device 를 지정하게 되며, 이 갯수에 따라 parallelization 의 degree 가 결정
    된다.
    - recovery catalog 를 사용할 것인지를 결정하기
    catalog 없이 RMAN 을 사용할 때의 단점은 recovery catalog 의 overhead 가
    없는 대신, Point-In-Time recovery 를 쉽게 할 수 없다. 또한, control file
    손상시에 recovery 할 수 없고, stored script 를 사용할 수 없다.
    (datafile 이 20개 이상일 경우에는 recovery catalog 사용을 권장한다.)
    - Setup
    가. Recovery catalog 생성
    1. Backup(target) db 외의 별도의 db 생성 (8.0.3 이상)
    2. catalog DB 에 분리된 tablespace 생성
    create tablespace rcvcat datafile '/oracle/rcvcat/rcvcat01.dbf'
    size 20 M;
    3. catalog 의 owner 생성과 권한부여
         create user rman identified by rman
         temporary tablespace temp
         default tablespace rcvcat;
         grant dba,connect,resource,recovery_catalog_owner to rman;
    4. catalog 저장에 필요한 object 생성
         cd $ORACLE_HOME/rdbms/admin
         sqlplus rman/rman
         @catrman
    나. Recovery manager 기동
    1. recovery catalog DB 를 사용하는 경우
    rman target \"system/manager\" rcvcat \"rman/rman@orabeta1\"
    (orabeta1 은 catalog DB 로 접속하는 tnsname 입니다.
    즉, sqlplus rman/rman@orabeta1 하면, catalog db 와 접속되어야 합니다.)
    2. recovery catalog DB 를 사용하지 않는 경우
    rman target system/manager@target nocatalog
    위 경우 모두, target database 를 catalog 에 등록해야 한다.
    RMAN> register database;
    다. Backup 시작
    - Backup 은 database 가 open 또는 close(close 후에는 반드시 mount
    상태이어야 한다)
    - Backup 의 단위
         full database
         tablespace
         datafile
         control file
         archived logs
    - Backup 의 예
    --full database
    run { 
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    backup full filesperset 2
    (database format '/user7/ora8/backup.%n_%p') ;
    release channel dev1;
    release channel dev2;
    -- tablespace
    run {
    allocate channel dev_1 type disk ;
    backup incremental level 0
    filesperset 1
    (tablespace system channel dev_1 format '/vol312/net8%d_%u');
    release channel dev_1;
    -- datafile
    run{ 
    allocate channel dev1 type disk;
    copy datafile "/vo3/orabeta6/backup/copy_tools.dbf"
    to "/vo3/orabeta6/oradata/orabeta6/tools01.dbf"
    tag "org_tools";
    release channel dev1;
    -- archived logs
    create script beta_arch_full { 
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    backup full filesperset 10
    (archivelog all delete input
    format '/vo3/orabeta6/backup/beta_arch.%s_%p') ;
    release channel dev1;
    release channel dev2;
    -- backup to tape
    run {
    allocate channel t1 type 'sbt_tape';
    backup
    format 'dbfull_sunday_s%s_t%t'
    tag 'Sunday full backup'
    (database);
    라. Restore
    - Backup 으로 부터 원래 위치로 복원
    - Archive log file 은 manual 하게 restore 할 수도 있고, 필요하다면
    recovery 시 자동으로 restore 된다.
    restore (archivelog all| like <filename | <archivelog range>);
    - restore 명령
    database : restore (database);
    tablespace : restore (tablespace <name>,...,<name>);
    datafile : restore (datafile <name>,...,<name>);
    control file : restore control file to location;
    - recovery 시에 database 는 어떤 상태에 있어야 하는가 ?
    1) control file restore - not mount
         SVRMGRL> startup nomount
    2) whole database, or system tablespace - not open
         SVRMGRL> startup mount
    3) tablespace or datafile - open but tablespace or datafile offline
         SVRMGRL> alter tablespace user_data offline temporary;
         SVRMGRL> alter database datafile '/oracle/file/user_data1.dbf'           offline;
    마, Recovery
    - Recoervy 는 file restore 후의 과정이다.
    1) Archive log mode : complete recovery, incomplete recovery 가 가능하다     
    2) No archive log mode : consistent whole database backup 으로 부터
    restore 하는 것이 유일한 option 이다.
    - whole database recovery 의 예
    svrmgrl
    connect internal
    shutdown abort
    startup mount
    rman target \"system/manager\" rcvcat \"rman/rman@orabeta1\"
    run {
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    restore database;
    recover database;
    release channel dev1;
    release channel dev2;
    or
    run {
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    restore tablespace 'SYSTEM';
    restore tablespace 'USERS';
    recover tablespace 'SYSTEM';
    recover tablespace 'USERS';
    sql "alter database open ";
    release channel dev1;
    release channel dev2;
    - datafile 하나가 사용할 수 없을 경우의 recovery
    가정) full backup set 이 있을 경우
    ORA-01157: cannot identify data file 3 - file not found
    ORA-01110: data file 3: '/user7/ora8/oradata/ORA8/temp01.dbf'
    SVRMGR> startup mount
    rman target \"system/manager\" rcvcat \"rman/rman@orabeta1\"
    RMAN> run {
    allocate channel dev1 type disk;
    restore database;
    recover database;
    release channel dev1;
    };

    Check the TSM logs for errors, the error stack here doesn't show any useful information (only informational messages and an undefined exit code). This is an 8i problem, later releases transfer much better messages from the media management software.

  • Recovery Manager not present and cannot install it

    I am working on a friend's computer as a favor as he knows nothing about computers.  I know some, but not much/enough about HP's.  Windows failed so I entered Recovery Manager (f11) and made a backup image ( it had never been done on this computer) to a USB, Sony 32 gb.   When I tried to boot from the USB during system recovery it would not boot.  I tried changing BIOS settings removing protected boot and switching to legacy boot device, but it still would not boot.  So I had downloaded a Win 8 install ios, burnt it to a DVD.  It installed Win 8.1 fine, but it did not allow me back into Recovery Manager.  I tired to use the Restore System but it still did not boot from the USB.  Recovery Manager does not run. The restore partition is intact on the hard drive, so I have been trying to reinstall Recovery Manager with Windows running from RM/Tools/Rita-Tools/HPRecovery.exe. It will not finish installing RM.  So I tried to install it from SW setup/RM4Win/installer.msi, but gives me "a script for this install to complete could not run. Contact your support or package vendor." Another time I tried it said the path was incorrect.   I even tried copying the recovery image from the USB to the RM folder on the recovery partition but that gives me an incorrect path message too. I tried to find a file suggested on C;\Program files (x86)/Hewlett-Packard/HPRecovery Manager/Rebecca.exe but it is not there. I read that some USB's are not compatable but it did not giv e a compete list, only a few examples.  Don't know where to find that list so I can buy another USB and copy the image over to it. Please, anyone, who actually with some indepth experience, would you help? I don't have much hair left from pulling it out. 

    WHen you get trouble with msi files you usually need the Microsoft Installer cleanup utility.
    Here is a method for removal of iTunes and related programs with clean up and reinstall.
    Download a fresh copy of iTunes and the stand alone version of Quicktime (the one without iTunes)
    http://www.apple.com/quicktime/download/win.html
    http://www.apple.com/itunes/download/
    Download and install Microsoft Installer cleanup utility, there are instructions on the page as well as the download. Note that what you download is the installer not the program – you have to run it to install the program. The installer doesn't give any message to confirm the installation.
    http://support.microsoft.com/kb/290301/
    (To run the program – All Programs>>Windows Install)
    Now use the following method to remove iTunes and its components:
    XP
    http://support.apple.com/kb/HT1925
    Vista
    http://support.apple.com/kb/HT1923
    *If you hit a problem with one of the uninstalls don't worry*, carry on with the deleting of files and folders as directed in the method.
    When you get to deleting Quicktime files in the system32 folder as advised in the method, you can delete any file or folder with Quicktime in the name.
    Restart your PC.
    Run the Microsoft Installer Cleanup Utility. (Start > All Programs > Windows Install Clean Up)
    Remove any references you find to the programs you removed - strictly speaking you only need to worry about those programs where the uninstall failed.
    If you don’t see an entry for one of the programs that did not uninstall, look out for blank entries or numeric entries that look like version numbers e.g. 7.x for Quicktime or 1.x for Bonjour.
    restart your PC
    Install the stand alone Quicktime and check that it works.
    If it does, install iTunes.

  • Error in Execution of Data Manager Package

    Hi Folks,
    We are facing the following error while executing the Data Manager Package for Clear/Import..
    Error Details:
    [Admin-ProcessPartition]Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_tblFactFinance, Column: ENTITY, Value: CONEUROPE.
    Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
    Errors in the OLAP storage engine: An error occurred while processing the 'FAC2Finance_INCR_UPDATE_TEMP_kmj3h_' partition of the 'Finance' measure group for the 'Finance' cube from the YASH6 database.
    Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
    Internal error: The operation terminated unsuccessfully.
    Please Look into it.....

    Hello,
       It looks like you have an inconsistency on the OLAP level. Please try to reprocess Entity dimension choosing full process for your application. This should solve the issue.
    Best regards,
    Mihaela

  • RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

    Good Morning All,
    One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
    ==================================================================================================
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

    This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
    ====================================================================================================
    Recovery Manager: Release 9.2.0.6.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN>
    connected to recovery catalog database
    RMAN>
    connected to target database: CUSTPR (DBID=525071053)
    RMAN>
    RMAN> #########################################################################
    2> # LEVEL 0 BACKUP #
    3> #########################################################################
    4>
    5> # Configure backups to be written to disk.
    6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    old RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
    2> # RMAN retains all backups needed to recover the database to any point in time
    3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
    4> # backups that are no longer required by the retention policy. To exclude a
    5> # backup from consideration by the policy, you can use KEEP option with the
    6> # BACKUP command.
    7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
    2> # maintenance operations.
    3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write disk backups to the /backup directory.
    2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
    3> # backup set number, and %p with the backup piece number.
    4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to back up the control file after each backup.
    2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
    2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
    2> # RMAN won't backup an archivelog or datafile if there already exists a backup
    3> # of that file. The FORCE option can be used to override optimization on a
    4> # specific BACKUP command.
    5> CONFIGURE BACKUP OPTIMIZATION ON;
    old RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Use the SHOW ALL command to see the current configuration settings.
    2> SHOW ALL ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
    RMAN>
    RMAN> # The following commands are run each day to start the backup cycle.
    2> # The steps are:
    3> # - Take an incremental level 0 backup of the database. A level 0 backup is
    4> # a complete backup of the entire file which can be used as the basis
    5> # for a subsequent incremental backup.
    6> # - Backup all archivelogs that have not already been backed up.
    7> # - Delete on-disk archivelogs older than seven days.
    8>
    9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
    10> DATABASE maxsetsize 33G
    11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
    12> delete all input;
    Starting backup at 12/30/2008 22:01:40
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=11 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
    input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
    input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
    input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
    input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
    input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
    input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
    channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
    channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
    piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
    archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
    archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
    archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
    archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
    archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
    archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
    Finished backup at 12/30/2008 22:03:47
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Recovery Manager complete.

  • NOT SHOWING FACTORY INSTALLED SOFTWARES IN " RECOVERY MANAGER "

    I'VE TRIED TO REINSTALL SOME SOFTWARE PROGMS BY USING  " RECOVERY MANAGER ".
    BUT I DIDNT FIND ANY FACTORY INSTALLED SOFTWARE PROGRAMS. 
    PLZ ASSIST ME.
    I WILL BE WAITING FOR UR KIND REPLY.
    THANK U SO MUCH.

    That is odd - that is, as long as the integrity of the Recovery Manager is intact, I would expect it to work.
    For example,
    If you have reinstalled the system using other than the Recovery Manager,
    or if you have upgraded the Operating System,
    or added / Removed data from the Recovery Partition,
    OR if the Recovery Manager is corrupted in some way,
    then
    the Recovery Manager will either not work at all, or may at least show inconsistancies.
    ======================================================================================
    You might try using a Restore Point to "go back in time" and see if the setting can recover.
    Using Microsoft System Restore (Windows 8)
    HP PCs - Restoring Files that were Backed Up Using HP Recovery Manager (Windows 8)
    You can go to your system's website for the current Drivers and Software that are available for your computer.
    First, create a place to which you can return in case things do not work as you hope:
    Create a restore point
    Install Software and Drivers from HP Website
    Go to the top of the HP forum page to Support and Drivers
    If prompted, Enter your Country or Region and
    Enter your Computer Model information,
    Go to Software and Drivers...
    Enter your Operating System in the Drop-down menu...  Scroll down
    Select desired Category Software – Solutions >> Driver - Keyboard, Mouse and Input Devices
    NOTE:  Download ONLY the relevant drivers and software for YOUR hardware - note that in the website you might find more than one kind of driver for more than one model of computer -- this is normal, but it does not mean YOUR computer uses all the software offered.
    Expand and decide if you need to install that package.
    Assure that you download and install only the most recent versions of each driver or program.
    Save the appropriate *.exe installation package on your computer
    NOTE the name and the location - the *.exe file will likely save to "Downloads “
    Install the Software / Driver installation package:  If you have ‘Admin’ control, you may highlight the package(s) and “double-click” to install, else Right-Click, Select ‘run as Administrator’ and install.
    NOTE:  There is sometimes a lot of information at the computer’s website.  Take a look at what’s available and bookmark the page for later reference.
    ======================================================================================
    Kind Regards,
    Dragon-Fur

Maybe you are looking for