F33-FF00-0006 Error in Recovery

Hello,
I'm attempting to fix a laptop for a friend.  The hard disk in the laptop was gradually failing with quite a number of bad sectors, all seemingly on the OS partition, and it wouldn't boot.  The first partition (WinRE?) and the last (Toshiba recovery?) seemed to be intact.
So, I took an image of the first and last partitions on the disk, got a new hard disk, and restored those partitions to the new disk, making sure to line up the partitions with the same sectors as on the old disk. 
Now, when I boot into the Toshiba Recovery console, I receive the message:
F33-FF00-0006
Failed to get the ID of the specified partition.
I've Googled all around, and the general consensus seems to be "get Toshiba's recovery discs," however, I have the recovery partition and I can boot into it, so it seems like there must be something simple to do to make it boot.
I saw a thread somewhere on this forum that suggested creating the file C:\Windows\System32\winload.exe on the OS partition, which did not work for me.  I even was able to copy that file off the old hard disk and put it on the new disk, which still did not enable Toshiba Recovery to boot.
Any ideas?
OS: Windows Vista
Laptop Model: L505-S5965
Solved!
Go to Solution.

I ended up solving the problem with a rather unusual solution.
On a hunch, I installed Linux Mint 12 on the OS partition - partition #2.  When I did so, Linux Mint installed the GRUB bootloader, which automatically detected the Windows Recovery Environment.  So, when I rebooted, I could select "Windows Recovery Environment" from the GRUB menu.
This took me, obviously, to WinRE.  WinRE asked me which operating system I wanted to repair, and although there were none in the list, it allowed me to click "Next."  This took me to the screen where I could select the Toshiba Recovery environment, and the recovery succeeded.
Thanks Peter, for the suggestions.  Hopefully this solution is helpful for someone else.

Similar Messages

  • Toshiba NB205 Error message F3-FF00-0006, Please Help!

    I need help. My toshiba NB205 is not working. When I turn it on it goes to a black screen that give me two options Launch start up repair or start normally. If I choose the startup normally it brings me back to the the same screen. If I choose Launch start up repair it goes to a black screen and only my cursor is on there. I tried going into safe mode and doing the recovery but nothing works. It always brings me back to this black screen. I even tried pressing Alt-Ctrl-Del and after trying a bunch of other things it brought me to a black screen and then weird codes came up on the screen like "Realtek RTL8101E etc. PXE-E61: Media test failure, check cable PXE-M0F: Exiting PXE ROM. This product is covered by one or more of the following patents, etc." and it says a bunch of other stuff and it keeps repeating it. I read in other forums that Im supposed to get into the BIO but I need step by step directions on how to do that cause when I went into the start up (by pressing F2) I didnt know what to do. Well, after pressing Launch star up repair and I left it for several minutes at the black screen to see if anything will happen and then after a long time a pop up message came and it said Error: F3-FF00-0006. Failed to get the ID of the specified partition. Press ok to turn off the computer. When I pressed ok, it turned off the computer and when I turned it on again i took me to the black screen with the two options Launch start up repair or start normally. Ahhh it's so frustrating and all my school work is on this laptop. Please if you can help me.. please let me know what to do..thanks. Oh, and I don't know what could have caused this problem. Yesterday the computer kept freezing up and it was really slow and once it even shut down for no reason but I could start it up after. But today it's not working properly.

    do you have same model computer?  Are all the same things occuring with your computer as the op's?  If not, then start your own thread and start from the beginning.  If much of the OP's issue(s) are the same as your you can always link to this thread if there is a reason to do so. 

  • 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.

  • Error in recovery media creation

    I bought  a new HP laptop recently.Its a HP PAVILION G6 2320TX.I ran the Recovery Media  Creation .After the initial setup and burning of files onto my first dvd,when it comes to verify, i am getting an error that states "We are experiencing errors in recovery media creation. Please try again.” ,and the disk ejects out.
    I use SONY DVD-R media so,i guess there shouldn't be any problem with the brand.I tried doing this a couple of time and each time i got the same error.
    Has anyone else experienced this? Any help/suggestions would be greatly appreciated!
    Thanks,
    Akash.

    Hello Akash_Sanu,
    I see that you are having problems with the recovery discs creation on your computer.
    I would suggest trying a different brand of disc, here is a link that explains the recovery discs process. If you continue to have problems with the disc creation I would suggest contacting HP support for a set of recovery discs.
    Here is a link to the contact options for HP support.
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

  • Error Handling/Recovery Mechanism in ODI

    can u ps provide sum infor related to Error handling/recovery mechanism in ODI?
    say for instance a link breaks down while moving data from source to staging or/and staging to target..what will happen?? is it like that the processed records will be dumped into the target table, or no record will be moved into the target table?
    Is it like "ZERO or ALL" kindaa stuff that ODI works on?
    I really need help on this?

    There is an option - Restart in the Operator. When you right click and click on restart .ODI will start from the steps failed.
    I beleive if the database is down then restart can help you but if the agent is down , then you might need to start the session completely ,reason being when agent send the SQL process to database it wait till the Database process and send the record back to it.During that interval if the agent goes down the database would have processed the records but agent wouldn't be ready to read those record and by the time you bring the agent up ,the session would have died and so you would need to start the session again.
    You can test and see if the Restart option helps you .

  • 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. 

  • Error on recovery 0xe0ef000d

    keep geting the same error on recovery hdd ok and memory
    this is using the 3 recovery discs i created and no longer have recovery on hdd
    pavilion dv7-3112sa

    It could be a bad disc.
    You can call HP and order a recovery disc set for a nominal fee.
    Yes you can use the COA product key to install W7 from a regular installation disc, but then you need to download and install all sorts of drivers from HP.
    HP support page for your model
    http://h10025.www1.hp.com/ewfrf/wc/product?product=4100032&cc=us&dlc=en&lc=en&query=dv7-3112sa&tool=

  • HT4848 Error creating recovery disk in Disk Assist

    I've carefully followed all instruction in this post: http://support.apple.com/kb/ht4848, but I am having an error when creating the recovery disk.
    The recovery Disk Assist starts creating it, but stops early on. The message I get is titled "Conclusion," and it says "The recovery drive wasn't created. There was an error creating recovery disk."
    Can anyone help me with this? I followed all the steps in the post above and I also created the partition on the external drive.
    I really need to wipe out my computer and make it appear "as new" because I am selling it. Any help would be great!
    Thanks!

    Same happened to me.  This makes absolutely no sense, but I just kept trying and trying then it finally worked.  For me, it hasn't been worth the bother.  These restore DVDs don't work like the ones I made for an Acer laptop, for example.  On my Acer, I repartitioned, reformatted my drive and was easily able to restore my computer before I sold it.  I've been going nuts trying to restore my computer after a clean install of Windows 7.  Still can't get it to work.

  • DB_PAGE_NOTFOUND error after recovery on a CDS database

    I am getting a DB_PAGE_NOTFOUND error after recovery, with a database that is configured in CDS mode. The error occurs after I insert several rows, bring down the process, remove the environment files and start the process which attempts to insert additional rows - gets a DB_PAGE_NOTFOUND error. The error persists ie. terminating and starting a new oprocess does not resolve the problem.
    Amy help will be appreciated.

    Assuming, that the db is corrupted and that CDS db's can get corrupted - is there any way, I can reduce the frequency of these errors by increasing Cache, page size etc.?
    Following is my DB configuration:
                   dbEnv_->open(envHome_.c_str(), envFlags_, 0);
                    dbEnv_->set_errpfx(envHome_.c_str());
                    dbEnv_->set_thread_count(16);
                    dbEnv_->set_cachesize(0,(100*1024*1024),2);
                    envFlags_ =   DB_INIT_CDB | DB_THREAD | DB_INIT_MPOOL ;
                    envFlags_ |=  DB_CREATE ;
                    dbEnv_->open(envHome_.c_str(), envFlags_, 0);
    db->set_pagesize((32*1024));
                db->open(NULL, temp.c_str(), tableName.c_str(),\
                    DB_BTREE, DB_CREATE | DB_THREAD , S_IRUSR | S_IWUSR);
                    dbEnv_->open(envHome_.c_str(), envFlags_, 0);
    The platform is HPUX. The problems occurs periodically - i.e. not every time.
    Thanks for your help.

  • Error installing recovery catalog

    Hi,
    Inorder to implement RMAN in oracle 10g in windows environment I created a separate table space for rman and created a user as rman1;
    then I issued the following commands :
    GRANT connect, resource, recovery_catalog_owner TO rman1
    grant create session to rman1;
    grant create type to rman1;
    then i entered into rman from dos prompt,
    rman catalog=rman1/rman1@tc
    from rman prompt I issued the command,
    create catalog tablespace RMAN1;
    then the following error occurs,
    RMAN> create catalog tablespace RMAN1;
    ORACLE error from recovery catalog database: ORA-01031: insufficient privileges
    RMAN-00571: ====================
    RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS ===========
    RMAN-00571: ====================================
    RMAN-06433: error installing recovery catalog
    Due to this error I am unable to proceed further and let me know the solution.
    Thanks in advance.
    Regards,
    A.Mohammed Rafi.

    Hi,
    Thanks for the help and the problem is solved.
    Now I am facing another problem,
    RMAN-03009: failure of catalog command on default channel
    ORA-19657: cannot inspect current datafile D:\ORACLE\PRODUCT\10.1.0\DB_2\TC\EXAMPLE01.DBF
    Could you please help me in this regard.

  • I want to backup my Mac to iCloud, but receive an error message recovery partition required.  Is this an easy fix?

    I want to backup my MacBook Pro to iCloud, but receive the error message "recovery partition required".  Is this easy to fix? 
    Thanks for your time.

    Sounds like your missing the partition. I have seen this before when I friend had a bad drive and took it in. Apple store replaced the driveamd installed lion but no partition. I had to reinstall lion from a full install DVD to build the recovery partition. Looks like you need to do the same. No data will be lost if you don't re-partition with the disk util. Just run the lion install from within lion and use the default. It will build the partition for you. Then re-run the apple updates for the 10.7.2 update which embeds the find my Mac part of iCloud in the recovery partition.
    Good luck.

  • Boot error: "F3-FF00-0006" "Failed to get the ID of the specified partition"

    Windows won't boot even in safe mode.  Can't access command prompt either.  I've looked around for solutions.  Other than ordering Toshiba recovery disks, one solution suggests installing the HDD Recovery Update Tool.  How do I run this if Windows won't start?  I tried burning it to a CD and booting the broken laptop from CD, but this doesn't work.
    Model is A505-S6980

    I see the HDD Recovery Update Tool on Toshiba of Canada's site but not here on our site that I can find. I honestly don't know how they indended that to be used.
    Have you tried booting while holding '0' to load from the recovery partition? It should allow you to return the notebook to factory conditions. Note that this will delete all your data.
    - Peter

  • Unknown Error during Recovery - iPad no longer Recognized by iTunes

    I have a 3rd Generation iPad which I was attempting to perform a factory reset.  I received an "Unknown Error" during the process and from that point on I have been unable to get iTunes to recognize my iPad in recovery mode (or otherwise).
    I have tried every thread on the subject, but I found one interesting thing.  If I connect the iPad with the same cable, etc. to another computer it immediately recognizes it in recovery mode and offers to restore the iPad.
    It seems like my computer is not recognizing the iPad because it was in the process of restoring the device when the error occurred.  Does anyone know if there is a way to reset or fix this issue.  I would prefer not to update iTunes and download both the new iTunes and iPad software again and use another computer if it is not necessary.
    Any help would be appreciated.
    Thanks

    Hey KSHItunes,
    That was a good test to try your iPad on another computer.  It does seem to isolate the issue to something with your computer setup.
    Although you would prefer not to update iTunes, there may be steps in this article which can help.
    iPhone, iPad, or iPod not recognized in iTunes for Windows - Apple Support
    Please check it out.
    Regards,
    Nubz

  • Equium A100-549: Blue Screen error during Recovery CD installation

    Hey,
    I recently purchased a Toshiba laptop, everything worked perfectly until my laptop was attacked. I got rid of the virus and went to reformat due to lots of problems occurring. The main one being a error has accursed and "Blah Blah" program needs to close. Also i kept getting loads of errors.
    http://aumha.org/win5/kbestop.htm
    Them types.
    Now then the Toshiba reformatting disk said simply put the disk into the CD drive and turn off. I did this, great. The toshiba disk said press F12 upon starting and click run the CD. The CD fires up and gets half way thro reformatting.
    I suddenly get a blue screen error. I thought oh well ill reboot and carry on. This is where the problem started. Because i was half way thro deleting/reinstalling windows i was missing some files. I go to reinstall or try to use the Toshiba CD I get a blue screen error.
    0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
    (Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1548.)
    Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).
    Any ideas what i can do? I don't want to send the laptop back to Toshiba to fix however im thinking this is the only way out.
    Please if repplying try to keep technical lanuage to a minnium. Many thanks, Dan.

    Hi
    Its very strange because the installation from the Toshiba recovery CD should works properly and without any Blue screen messages.
    Usually if the BSOD appears if there is a serious software problem or something wrong with the hardware.
    I dont think that the software on the recovery CD could be corrupt.
    Did you try to install the OS from original Microsoft Windows CD? It would be very interesting to know if the blue screen will also appear.
    However, I think your notebook is new and the warranty is valid. In my opinion you should ask the Toshiba service partner for the help because the guys could start the diagnostic test and could locate the fault.

  • Windows 7 Install error after Recovery

    I recently had a HD crash on my SL410.  I received a new hard drive and recovery disks from support.  All appear to install OK until Windows 7 tries to start.  I get to "Setting up for first use " and then get an error message that says the install did not work correctly and I need to start over.  Requested new disks from support but had the same error.  Any ideas on what is wrong?

    performing clean windows installation may solve your issue.
    also, when you see lenovo logo, press f8 , then select "las good configuration" or "fix start-up issue" from the menu.

Maybe you are looking for

  • I have connected via VPN but can't see lion server .private

    when I am in my local network at home I simply go to finder and click on my server and connect to it. When I VPN form the net into my servers local network I dont see it in my finder? I know I am in the next work being I did a IP Check but am I am mi

  • Norton anti virus won't allow installation of flash player (vista-IE)

    Flash player has been on my computer for several years. Somehow it got deleted after installing a windows update today. An error mesage comes in the lower left of screen saying that this is unsafe and won't allow the download. I attempted several tim

  • Can we remove timestamp which is added infront of the file name, in archive

    Can we remove timestamp which is added infront of the file name of datafile which was imported succesfully , in archive folder, i have a requriment to move file from archive folder  to another folder, but programmer is finding diffficulty in moving t

  • Service Pack availability

    Hi Hopefully a very easy question! We purchased an upgrade from an old version of Zenworks to ZENworks Configuration Management 11 SP1. Can I confirm (I don't know how Novell do this now) if we are entitled/able to download and install SP3 for Zenwor

  • Executing a function when application loads and Automatically refreshing

    Hello, I am new to JSF and would like to load an application by calling a function in 1 of my java classes. I am currently doing that, successfully, on a click of a button but would like the function to run onLoad, without the button click. In additi