Satelitte 5205 wrong machine error on recovery

My 5205 s703 came up with wrong machine after an attemp to recover from a system crash. I recall using the DMI update from toshiba to try and sort out the id problem.( this is the id 5205 changing from 5205 to 5200). Hence the recovery disk does not work because the machine thinks its a 5200. The system board has never been change or altered. The DMI software to fix this from toshiba did not work. (USA web site).
I was left with not being able to access my computer data. I contacted the service agent in Cambridge who suggested i get a caddy and plug my hard drive into another computer to retrive all my crucial files before sending the computer away for repair. Thanks for that. Now i have satellite hard drive in a caddy attached to another computer. The question is, Can i now repair the file that prevented the computer from booting while i have acces to the hard drive. The file was windows\system32\system. Is there a copy of the system file any where else on the hard drive. If i can find that then i can fix it. PS i tried to respond to a previous question i posted but could not witout registering a second time.

hi Garry,
Check for a folder called I386 on your hard drive. This should contain a copy of the system installation files and you may be able to copy your damaged system file from there.
HTH

Similar Messages

Can not use recovery DVD 'Wrong machine' error occurs

My Dealer/Service center replaced the motherboard when I had a start up problem. My recovery DVD which originally comes with the notebook does not work anymore. When I start recovery procedure follow message is shown: 'Wrong machine'.
Is it possible to download new one from the Toshiba website? If yes from where exactly?
My product is registered in October 2004.

Hello
If you use wrong machine as searching term on this forum you will find many similar treads. When motherboard is changed DMI information must be updated. Without this info identification is not possible.
I recommend you to contact service again. They will update DMI info and you will be able to use recovery media again.
Good luck!

Error message "wrong machine" on Qosmio G35-AV650

Hi
please help me with the "wrong machine" message in my notebook .... how can I update DMI ?
Thank you !

Hello,
There is a solution for this problem.
With a DMI update utility (generic) you can modify the DMI information on your Qosmio.
Instructions to modify the DMI information:
1. Once the DMI Utility image is downloaded, with a blank, formatted diskette in the floppy
disk drive, create the DMI Utility disk by clicking on the downloaded file and following the
instructions.
2. Boot from the DMI Utility disk. Ensure that the disk is write-Enabled.
3. Press the 2 key to choose the "Write DMI String" option from the DMI Utility menu.
4. For Manufacturer, type TOSHIBA and press Enter.
5. For "Product Name", enter the product name as given in the information section of the
Issue Alert. Make sure the Product Name is entered exactly as written in the Issue Alert
including spaces / no spaces, caps / lower case, etc. Press Enter to go to the next field.
6. For the "Version Number", enter the complete part number of the computer (i.e.
PT831U-102T97) from the product label on the bottom of the computer and press Enter.
If the computer is a factory-refurbished computer (i.e. PT831U-102T97B), leave off the B
at the end.
7. For "Serial Number", enter the serial number from the product label on the bottom of the
computer and press Enter. Omit the dash and the number after it (i.e. for serial number
12345678A-1, you would enter 12345678).
8. For UUID, press Enter to skip this field. Typically the UUID will not need to be entered,
as it is not cleared when the system boards are repaired. Should this field be blank, enter
the UUID manually. The UUID is typically located on a label affixed to the system board
near the mini-PCI slot.
9. For the OEM Part Number, enter the complete part number of the computer (i.e.
PT831U-102T97) from the product label on the bottom of the computer and press Enter.
If the computer is a factory-refurbished computer (i.e. PT831U-102T97B), leave off the B
at the end.
10. For the OEM SW Number, press Enter to skip this field.
11. If the DMI information is correct, press F2 to confirm the changes; otherwise, press F4 to
ignore the changes and make corrections.
12. Press F2 to save the changes and write the DMI string to the computers EEPROM.
13. Eject the DMI Utility disk and restart the computer.
The computer is now ready to restore the factory pre-installed software using the appropriate
Toshiba recovery media.
if you are interested, I can put the DMI update tool image available for download.
Let me know...
But please... DO IT AT YOUR OWN RISK
Francisco Jr

M35-S359 Wrong Machine Type error message

Well I will try this again!
HDD replaced
Attempted System Restore
Failure - Error message "Wrong Machine type"
Restore Disk is Valid. I have used it before to restore the Original Drive.
Attempted to run Ghost from the Restore Disk. HDD took the Restore but will NOT boot from it.
I have taken all the proper steps in setting up the Laptop.
Others POSTed for this Model Laptop have had the same issue
Im not going to send it in to an ASP.
I am Toshiba Certified but this one has been a real Pain in the Bottomside.
Im about ready to do what one of my former Customers did to his Laptop out of frustration.
He smashed it until nothing was left.
It seems to me Toshiba want us to sell and support their products but we are not getting the support that we need!
Steve Toquinto
[email protected]

I, too, am having this error message. I read somewhere that it is either because of the font Helvetica Nueue, or because the files is being shared between a PC and a Mac. The quickest fix I have found, is to take the pdf and open it in Illustrator and convert all the text to curves. Then it should work correctly.
I don't think anyone has found a definitive answer.
thanks

Wrong Machine message with genuine Toshiba recovery disk

I have a Sat Pro L300 EZ1004X and ordered a recovery disk from Toshiba after giving them the model number and serial number. When I boot from the disk I get a "Wrong Machine" message with an exit button that just powers off the machine, there is no exit to DOS. Booting from recovery partition by holding down 0 does not work either, just some colors at the top of the screen. The laptop was refurbished at a genuine Toshiba service center. The recovery disks are labelled L300 series. The machine was running fine until attacked by the Alureon virus and now hangs at the Microsoft screen on boot. I want to wipe the disk and start again. Net research indicated I may need a DMI reset utility, but the one I found at the Toshiba site does not list the L300 models. Any ideas would be greatly appreciated.

Satellite Pro L300-EZ1004X
"Wrong Machine" message
You're right, Chris. If the recovery disc is the correct one, the DMI string in the machine needs fixing. Since the utility for that computer is not posted, you need to contact Toshiba. It's 800-457-7777 or..
Locate a Toshiba Service Center
-Jerry

Time machine error: doesnt backup due a wrong calculation of space availab

296.4 GB are bigger than 6.8 GB, isnt it?
well, time machine is not doing the backup because detects that 296.4GB are lower than 6.8GB !!!
Time machine error:
This backup is too large for the backup volume. The backup requires 6.8 GB but onlye 296.4 GB are available.
To select a lrger volume, or to make the backup smaller by excluding files, open sustem preferences and chose Time Machine
any idea how to correct this error?
thanks a lot

296.4 GB are bigger than 6.8 GB, isnt it?
well, time machine is not doing the backup because detects that 296.4GB are lower than 6.8GB !!!
Time machine error:
This backup is too large for the backup volume. The backup requires 6.8 GB but onlye 296.4 GB are available.
To select a lrger volume, or to make the backup smaller by excluding files, open sustem preferences and chose Time Machine
any idea how to correct this error?
thanks a lot

P105-S9337 Wrong Machine during recovery

Hello, So I have encountered the ever so common wrong machine message when trying to restore my computer. I understand it has something to do with the DMI in the BIOS or something. I found that Toshiba had a utility to fix this but my model is included in the list of effected computers, but tried to do it anyway. I burned the iso as the instructions say to do using Power ISO and it is indeed a boot cd. I was able to boot from cd but it just comes up and says loading windows 95 in text and then theres a blinking _ a few lines down. It does nothing I left if for an hour. What can I do? I am limited in options being deployed out here in Afghanistan in the middle of nowhere I have nothing but this laptop for another 6 months, any help is greatly appreciated. My System is on bios 4.30, windows vista 32 bit. Thanks! Pat

Satellite P105-S9337
You will need to contact Toshiba's tech support to obtain the DMI-string update utility for that model.
Call them at 800-457-7777.
-Jerry

Portege 2010: message wrong machine appears

On my Portege 2010 message "wrong machine" appears by using recovery CD for Portege 2000
Detais are here.
Portege 2010 > origionaly had chinese version of Win XP home edition >><< i bought it from a person who some how had installed winXP pro and Win 98 on it.
i tried to format HD to use my own copy of XP pro corp.....this is where my problem began.
Portege boots up drpm WIn98 CD and boot disk as well ....... after loading diagnostic tools >> i get message "device driver MSCD001 not found and CD-rom driver not found..........
mY qUESTION :: How can i proceed onward from this Message >>>
>><< i bought Portege 2000 3 Recovery CDs assuming that it will restore Portege but after running first CD ><> i get a big message Wrong Machine
mu Question is is it possible to restore Portege 2000 on Portege 2010 that origionally had chinese version of OS...
what else can i do to Install WinXp on my Portege 2010 ........ and how can i solve the message CD-rom device driver MSCD001 not found

Hello
Unfortunately there is nothing to do. The recovery image is created for each notebook model and it can not be used for different notebook models. Can you imagine the situation that you can use every recovery media on every notebook model?
Every notebook has specific hardware configuration and because of that the recovery medias are specific for particular notebook model.
By the way: which CD-Rom device you use?

Time Machine Error - again again..

Hi,
I also get this one...
Time Machine Error
Unable to complete backup. An error occurred while
copying files to the backup volume.
I haven´t tried with Time Machine Buddy - but here is a few facts, that maybe could help me find a solution.
My total backup size is approx. 300GB (on USB connected 1TB external disk)
When i exclude the movie folder in iTunes (113GB) it works fine - when i include it, I get the above error...
Whats wrong - corrupt file in the movie folder?? How do i locate it?? Foldersize to big???
Best regards...

Hello j:
Welcome to Apple discussions.
There is probably a corrupt file in the movie folder. Try TM Buddy. That gives you a log (almost real time) of what is happening when TM does a backup.
Barry

Crti.o: wrong machine class (really need help)

Hi all;
I am trying to build in 64 bit with Forte 6 compiler on Solaris2 8 machine. For the build in 64 bit mode i am using the option -xarch=v9. Also i have set environment variable
LD_OPTIONS=-D files /tools_SunOS/Forte6U1/WS6U1/lib/v9/crti.o
The compiler is located in /tools_SunOS/Forte6U1/WS6U1
my LD_LIBRARY_PATH is set to
/usr/lib/sparcv9:/usr/ccs/lib/sparcv9
The error i get is
debug: file=/tools_SunOS/Forte6U1/WS6U1/lib/v9/crti.o [ ET_REL ]
debug:
debug: file=/tools_SunOS/Forte6U1/WS6U1/lib/crti.o; rejected: ELF class mismatch: 32-bit/64-bit
debug:
ld: fatal: file /tools_SunOS/Forte6U1/WS6U1/lib/crti.o: wrong machine class
Why is the linker picking up the 32 bit crti.o?? Is there an option i need to set in the linker to pick up the 64 bit crti.o???
I have tried to run it with LD_LIBRARY_PATH not set and with the -R option to the following
LIB_LOCATION_PATH=/usr/lib/sparcv9:/vob/tools_SunOS/Forte6U1/WS6U1/lib/v9
LIB_LOCATION_OPTIONS =-norunpath -R $(LIB_LOCATION_PATH)
But still the 32 bit crti.o is been picked up and not the 64 bit!! Any ideas?
Thanks
Terry

I am trying to build in 64 bit with Forte 6 compiler
on Solaris2 8 machine. For the build in 64 bit mode i
am using the option -xarch=v9. Also i have set
environment variable
LD_OPTIONS=-D file /tools_SunOS/Forte6U1/WS6U1/lib/v9/crti.o Don't do that. Never add compiler options that point into the compiler installation area, into /usr/include, or /usr/lib. The compiler knows where to find its own components, and will pick the correct ones if you don't try to "help" it.
my LD_LIBRARY_PATH is set to
/usr/lib/sparcv9:/usr/ccs/lib/sparcv9Do not set LD_LIBRARY_PATH at all.
I have tried to run it with LD_LIBRARY_PATH not set
and with the -R option to the following
LIB_LOCATION_PATH=/usr/lib/sparcv9:/vob/tools_SunOS/Fo
rte6U1/WS6U1/lib/v9
LIB_LOCATION_OPTIONS =-norunpath -R
$(LIB_LOCATION_PATH)If you want to pick up shared libraries from the compiler installation area, you don't need any options. The compiler by default will build the executable with dependencies on those libraries.
To link a 64-bit C++ program that uses shared libraries from the compiler installation area, do something like this:
CC -xarch=v9 -o myprog [ list of files and non-default libraries ]

"Time Machine Error The backup volume is read only"

Lately, every time I try to backup to my Time Capsule using Time Machine it fails and I get a message saying "Time Machine Error The backup volume is read only. To select a different volume, open system preferences and choose Time Machine" So I do that and I see the Time capsule listed. I don't want to select anything but the Time Capsule, cuz what else do I have, right? Am I wrong in assuming the "backup volume" is the Time Capsule? Anyway, I have tried changing the permissions on the time capsule, but when I get the "get info" box for the time capsule, there is not an option to change those settings, they are grayed out. Every thing worked well for about a week and then this started. My backup volume must have been "Read & Write" at first, because I can see what was backed up when I open Time Machine. Anybody have a clue what's going on? How can I make the back up volume "Read & Write" again and why did it change to "Read Only?"

Nope, I am using the same passwords as ever, both users have the same password, BTW. The password I gave to the Time Capsule is different, tho, but that password is for the wireless aspect of the Time Capsule, so that wouldn't have anything to do with it, would it?
I also get a message box that says "Disk Repair The disk "Backup of XXX's Computer" was not repairable by this computer, it is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible." This box appears in conjunction with the appearance of the Norton's virus scan box scanning the time capsule.

Wrong Machine Class

We receive the following error when trying to compile on 64 bit Solaris 7 using SunWorkshop 5:
ld: fatal: file cdemo6.o: wrong machine class
Has anyone seen this message before and if so were they able to resolve the problem.
Thanks in advance

Hi,
I found following technote on related subject.
Technote suggests the method to diagnose this problem.
Thanks
Kalpesh
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SYNOPSIS: Compilation error message "ld: fatal: wrong machine class"
OS: Solaris/SunOS
PLATFORM: Generic
OS VERSION: 7
TECH AREA: OS
PRODUCT: Utilities
KEYWORDS: ld wrong machine class cc LD_OPTIONS
DESCRIPTION: What to do when the compiler emits the error message "ld: fatal: wrong
machine class"
SOLUTION: This error message can be printed when the user attempts to link binaries
compiled for different architecture. Here is an example compilation which
can cause problems.
An application is built using two C files (foo.c foo1.c).
cc -c foo1.c
cc -c foo.c -xarch=v9
cc -o foo foo.o foo1.old: fatal: file foo.o: wrong machine class
ld: fatal: File processing errors. No output written to foo
A quick check with the "file" command will show the problem:
file *.ofoo.o: ELF 64-bit MSB relocatable SPARCV9 Version 1
foo1.o: ELF 32-bit MSB relocatable SPARC Version 1
Note that foo.o was built as a Sparc V9 binary.
That was a very simple example. With more complex link phases, the problems
could be far more obscure. In that case, there is a linker variable
which may help. The "-D files" flag will print the files which the
linker is opening. A simple way to set the flag is to set "LD_OPTIONS='-D
files'" in the environment.
export LD_OPTIONS="-D files"
cc -D files -o foo foo.o foo1.odebug: file=/opt/SUNWspro/SC5.0/lib/crti.o [ ET_REL ]
debug: file=/opt/SUNWspro/SC5.0/lib/crt1.o [ ET_REL ]
debug: file=/opt/SUNWspro/SC5.0/lib/values-xa.o [ ET_REL ]
debug:
debug: file=foo.o rejected: ELF class mismatch: 32-bit/64-bit
debug:
ld: fatal: file foo.o: wrong machine class
ld: fatal: File processing errors. No output written to foo
This output could help track down the miscompiled binary.

I'm having trouble backing up my second macbook to a new time capsule. continue to get an error message -- "Time Machine Error. The backup disk image could not be created." Is there something I need to change in my time capsule or time machine?

I just set up a new time capsule. it worked fine on my first macbook. But now I cannot backup my second macbook. Getting "Time Machine Error" "The backup disk image could not be created." Do I need to change settings on my time capsule to allow the second computer, or do I need to change something on the computer to allow time machine to work right?

Try #C9 in Pondini's Time Machine Troublshooting
http://pondini.org/TM/Troubleshooting.html

How to resolve this issue in windows 7 ?? "An Internal Virtual Machine error (3) has occurred. The virtual machine will reset now."

Dear Friends,
Do kindly help me out on this issues. I have installed Microsoft Virtual PC 2007 in my PC and i am trying to create an new virtual machine for several testing. I have a clean ISO image of windows 7 . I import through Captured ISO option. The system tries
to configure the OS . But during the configuration i am getting this error.
*Your PC needs to Restart.
Please hold the power button.
Error Code: 0X0000005D
Parameters:
0x03063A09
0x756E6547
0x49656E69
0x6C65746E
An Internal Virtual Machine error (3) has occured.
The virtual machine will reset now.
I have Enabled the virtualization settings in BIOS.
Kindly help me out to resolve this issue.
Base Machine Platform : Windows 7 - 32 Bit and Windows 7 - 64 Bit.
ISO Image : windows 7 - 32 bit.

Error Code: 0x0000005D: Your
CPU is not compatible.
Ref : http://www.winvistatips.com/internal-virtual-machine-error-3-has-occurred-t520964.html
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

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.

Satelitte 5205 wrong machine error on recovery

Similar Messages

Maybe you are looking for