sybase 11.5 的备份文件恢复到15.7 恢复信息如下:
2013-06-06 17:06
260 查看
----------------------------------------------------------
-- gjjmx12_dl 恢复消息
----------------------------------------------------------
Backup Server session id is: 7. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name '12_2011131470E855' section number 1 mounted on disk file 'c:\gjjmx12_2011.dump'
Backup Server: 4.188.1.1: Database gjjmx12_dl: 71686 kilobytes (1%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 157706 kilobytes (2%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 198188 kilobytes (3%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 247488 kilobytes (4%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 311656 kilobytes (5%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 372286 kilobytes (6%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 432618 kilobytes (7%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 517730 kilobytes (8%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 595558 kilobytes (9%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 629608 kilobytes (10%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 707182 kilobytes (11%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 750192 kilobytes (12%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 836212 kilobytes (13%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 879222 kilobytes (14%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 922232 kilobytes (15%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1008252 kilobytes (16%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1051262 kilobytes (17%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1137282 kilobytes (18%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1180292 kilobytes (19%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1266312 kilobytes (20%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1309322 kilobytes (21%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1352332 kilobytes (22%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1438352 kilobytes (23%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1481362 kilobytes (24%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1567382 kilobytes (25%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1610392 kilobytes (26%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1696412 kilobytes (27%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1739422 kilobytes (28%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1781920 kilobytes (29%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1867940 kilobytes (30%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1910950 kilobytes (31%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1996970 kilobytes (32%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 2039980 kilobytes (33%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 2048180 kilobytes (100%) LOADED.
Backup Server: 3.42.1.1: LOAD is complete (database gjjmx12_dl).
All dumped pages have been loaded. ASE is now clearing pages above page 1024000, which were not present in the database just loaded.
Processed 800 allocation unit(s) out of 8000 units (allocation page 2116096). 10% completed.
Processed 1600 allocation unit(s) out of 8000 units (allocation page 2337024). 20% completed.
Processed 2400 allocation unit(s) out of 8000 units (allocation page 1255680). 30% completed.
Processed 3200 allocation unit(s) out of 8000 units (allocation page 2532608). 40% completed.
Processed 4000 allocation unit(s) out of 8000 units (allocation page 2634752). 50% completed.
Processed 4800 allocation unit(s) out of 8000 units (allocation page 2736896). 60% completed.
Processed 5600 allocation unit(s) out of 8000 units (allocation page 2839296). 70% completed.
Processed 6400 allocation unit(s) out of 8000 units (allocation page 2941440). 80% completed.
Processed 7200 allocation unit(s) out of 8000 units (allocation page 3043584). 90% completed.
Processed 8000 allocation unit(s) out of 8000 units (allocation page 2047744). 100% completed.
ASE has finished clearing database pages.
Started estimating recovery log boundaries for database 'gjjmx12_dl'.
Database 'gjjmx12_dl', checkpoint=(880534, 11), first=(880534, 11), last=(880534, 11).
Completed estimating recovery log boundaries for database 'gjjmx12_dl'.
Started ANALYSIS pass for database 'gjjmx12_dl'.
Completed ANALYSIS pass for database 'gjjmx12_dl'.
Started REDO pass for database 'gjjmx12_dl'. The total number of log records to process is 1.
Completed REDO pass for database 'gjjmx12_dl'.
Use the ONLINE DATABASE command to bring this database online; ASE will not bring it online automatically.
已解决!!
恢复后需要 online database 数据库
-- gjjmx12_dl 恢复消息
----------------------------------------------------------
Backup Server session id is: 7. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 6.28.1.1: Dumpfile name '12_2011131470E855' section number 1 mounted on disk file 'c:\gjjmx12_2011.dump'
Backup Server: 4.188.1.1: Database gjjmx12_dl: 71686 kilobytes (1%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 157706 kilobytes (2%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 198188 kilobytes (3%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 247488 kilobytes (4%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 311656 kilobytes (5%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 372286 kilobytes (6%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 432618 kilobytes (7%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 517730 kilobytes (8%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 595558 kilobytes (9%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 629608 kilobytes (10%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 707182 kilobytes (11%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 750192 kilobytes (12%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 836212 kilobytes (13%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 879222 kilobytes (14%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 922232 kilobytes (15%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1008252 kilobytes (16%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1051262 kilobytes (17%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1137282 kilobytes (18%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1180292 kilobytes (19%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1266312 kilobytes (20%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1309322 kilobytes (21%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1352332 kilobytes (22%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1438352 kilobytes (23%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1481362 kilobytes (24%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1567382 kilobytes (25%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1610392 kilobytes (26%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1696412 kilobytes (27%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1739422 kilobytes (28%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1781920 kilobytes (29%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1867940 kilobytes (30%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1910950 kilobytes (31%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 1996970 kilobytes (32%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 2039980 kilobytes (33%) LOADED.
Backup Server: 4.188.1.1: Database gjjmx12_dl: 2048180 kilobytes (100%) LOADED.
Backup Server: 3.42.1.1: LOAD is complete (database gjjmx12_dl).
All dumped pages have been loaded. ASE is now clearing pages above page 1024000, which were not present in the database just loaded.
Processed 800 allocation unit(s) out of 8000 units (allocation page 2116096). 10% completed.
Processed 1600 allocation unit(s) out of 8000 units (allocation page 2337024). 20% completed.
Processed 2400 allocation unit(s) out of 8000 units (allocation page 1255680). 30% completed.
Processed 3200 allocation unit(s) out of 8000 units (allocation page 2532608). 40% completed.
Processed 4000 allocation unit(s) out of 8000 units (allocation page 2634752). 50% completed.
Processed 4800 allocation unit(s) out of 8000 units (allocation page 2736896). 60% completed.
Processed 5600 allocation unit(s) out of 8000 units (allocation page 2839296). 70% completed.
Processed 6400 allocation unit(s) out of 8000 units (allocation page 2941440). 80% completed.
Processed 7200 allocation unit(s) out of 8000 units (allocation page 3043584). 90% completed.
Processed 8000 allocation unit(s) out of 8000 units (allocation page 2047744). 100% completed.
ASE has finished clearing database pages.
Started estimating recovery log boundaries for database 'gjjmx12_dl'.
Database 'gjjmx12_dl', checkpoint=(880534, 11), first=(880534, 11), last=(880534, 11).
Completed estimating recovery log boundaries for database 'gjjmx12_dl'.
Started ANALYSIS pass for database 'gjjmx12_dl'.
Completed ANALYSIS pass for database 'gjjmx12_dl'.
Started REDO pass for database 'gjjmx12_dl'. The total number of log records to process is 1.
Completed REDO pass for database 'gjjmx12_dl'.
Use the ONLINE DATABASE command to bring this database online; ASE will not bring it online automatically.
已解决!!
恢复后需要 online database 数据库
相关文章推荐
- Sybase系统崩溃了,没有备份,但设备文件还存在,如何恢复数据库?
- 在无备份信息和无备份制文件及非catalog下的异机恢复数据库
- DPM2012系列之十七:如何将备份文件恢复到网络共享文件夹 推荐
- RMAN的备份与恢复(5)-数据文件的恢复
- SQL Server 只想对备份的文件恢复数据文件,不恢复日志文件
- BCB ADO 备份 恢复 任何类型 数据库 文件
- 非系统数据文件损坏,rman备份恢复
- mysql怎样利用对所有数据库进行备份的备份文件只恢复某一个数据库
- ★实验 8-1 1. 创建一个守候进程。并为自己创建独立的日志文件。 2. 每隔 1s 向日志文件中写入如下信息: a) 未使用的内存大小(MemFree) 可以从/proc/meminf
- 无备份有完全归档日志情况下恢复数据文件
- 文件服务器权限的备份与半自动恢复
- windows计划任务+批处理文件实现oracle数据库的定时备份与恢复
- oracle无备份丢失数据文件的恢复
- rman实验之归档模式无备份,正常关机丢失当前联机重做日志文件的恢复
- 用备份控制文件做不完全恢复下的完全恢复(全备<老>--备份控制文件<次新>--删除表空间andy--日志文件<新>)
- mysql从只有一个备份文件(多个数据库的备份)中恢复数据到指定数据库
- 用 XML 文件持久化和恢复图片信息
- 【RMAN备份恢复】针对Flash Recovery Area删除文件不回收空间的问题诊断
- MongoDB数据库的文件备份恢复以及文件导入导出
- 备份恢复统计信息