哭诉: 数据库为什么会当掉?error 221

本文记录了Oracle数据库从启动到运行过程中的一系列操作及遇到的错误情况,包括错误码ORA-00206、ORA-00202等,并详细展示了数据库启动过程中的配置参数与后台进程初始化步骤。
Tue May 27 03:55:43 2008
Errors in file /opt/oracle/admin/webapp/bdump/webapp_ckpt_1192110.trc:
ORA-00206: Message 206 not found; No message file for product=RDBMS, facility=ORA; arguments: [3] [1]
ORA-00202: Message 202 not found; No message file for product=RDBMS, facility=ORA; arguments: [/data/webapp/control02.ctl]
ORA-27072: Message 27072 not found; No message file for product=RDBMS, facility=ORA
IBM AIX RISC System/6000 Error: 22: Invalid argument
Additional information: 8
Tue May 27 03:55:43 2008
Errors in file /opt/oracle/admin/webapp/bdump/webapp_ckpt_1192110.trc:
ORA-00221: Message 221 not found; No message file for product=RDBMS, facility=ORA
ORA-00206: Message 206 not found; No message file for product=RDBMS, facility=ORA; arguments: [3] [1]
ORA-00202: Message 202 not found; No message file for product=RDBMS, facility=ORA; arguments: [/data/webapp/control02.ctl]
ORA-27072: Message 27072 not found; No message file for product=RDBMS, facility=ORA
IBM AIX RISC System/6000 Error: 22: Invalid argument
Additional information: 8
Tue May 27 03:55:43 2008
CKPT: terminating instance due to error 221
Termination issued to instance processes. Waiting for the processes to exit
Instance terminated by CKPT, pid = 1192110
Tue May 27 08:56:27 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =165
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
  processes                = 1000
  sessions                 = 1500
  sga_max_size             = 3758096384
  lock_sga                 = TRUE
  __shared_pool_size       = 956301312
  shared_pool_size         = 956301312
  __large_pool_size        = 167772160
  large_pool_size          = 167772160
  __java_pool_size         = 50331648
  java_pool_size           = 50331648
  shared_pool_reserved_size= 104857600
  nls_language             = SIMPLIFIED CHINESE
  nls_territory            = CHINA
  control_files            = /data/webapp/control01.ctl, /data/webapp/control02.ctl
  db_block_size            = 8192
  db_cache_size            = 1241513984
  db_writer_processes      = 2
  compatible               = 10.2.0.1.0
  log_buffer               = 14302208
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = /data/dbarch
  db_recovery_file_dest_size= 64424509440
  fast_start_mttr_target   = 1800
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  dispatchers              = (PROTOCOL=TCP) (SERVICE=webappXDB)
  job_queue_processes      = 100
  cursor_sharing           = EXACT
  background_dump_dest     = /opt/oracle/admin/webapp/bdump
  user_dump_dest           = /opt/oracle/admin/webapp/udump
  core_dump_dest           = /opt/oracle/admin/webapp/cdump
  audit_file_dest          = /opt/oracle/admin/webapp/adump
  sort_area_size           = 65536000
  db_name                  = webapp
  open_cursors             = 2500
  optimizer_mode           = CHOOSE
  pga_aggregate_target     = 805306368
PMON started with pid=2, OS id=14242248
PSP0 started with pid=3, OS id=14246344
MMAN started with pid=4, OS id=13889668
DBW0 started with pid=5, OS id=1073238
DBW1 started with pid=6, OS id=13873268
LGWR started with pid=7, OS id=14250442
CKPT started with pid=8, OS id=14254540
SMON started with pid=9, OS id=14258638
RECO started with pid=10, OS id=14262736
CJQ0 started with pid=11, OS id=14266834
MMON started with pid=12, OS id=13848674
Tue May 27 08:56:29 2008
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=13, OS id=14270932
Tue May 27 08:56:29 2008
starting up 1 shared server(s) ...
Tue May 27 08:56:30 2008
ALTER DATABASE   MOUNT
Tue May 27 08:56:34 2008
Setting recovery target incarnation to 2
Tue May 27 08:56:34 2008
Successful mount of redo thread 1, with mount id 2116597886
Tue May 27 08:56:34 2008
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Tue May 27 08:56:34 2008
ALTER DATABASE OPEN
Tue May 27 08:56:34 2008
Beginning crash recovery of 1 threads
parallel recovery started with 15 processes
Tue May 27 08:56:35 2008
Started redo scan
Tue May 27 08:56:35 2008
Completed redo scan
11517 redo blocks read, 22 data blocks need recovery
Tue May 27 08:56:35 2008
Started redo application at
Thread 1: logseq 1909, block 56340
Tue May 27 08:56:35 2008
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1909 Reading mem 0
  Mem# 0 errs 0: /data/webapp/redo01.log
Tue May 27 08:56:35 2008
Completed redo application
Tue May 27 08:56:35 2008
Completed crash recovery at
Thread 1: logseq 1909, block 67857, scn 62588965
22 data blocks read, 21 data blocks written, 11517 redo blocks read
Tue May 27 08:56:35 2008
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=32, OS id=14324206
ARC1 started with pid=33, OS id=14328304
Tue May 27 08:56:35 2008
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 advanced to log sequence 1910
Thread 1 opened at log sequence 1910
  Current log# 3 seq# 1910 mem# 0: /data/webapp/redo03.log
Successful open of redo thread 1
Tue May 27 08:56:36 2008
ARC1: STARTING ARCH PROCESSES
Tue May 27 08:56:36 2008
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Tue May 27 08:56:36 2008
SMON: enabling cache recovery
Tue May 27 08:56:36 2008
db_recovery_file_dest_size of 61440 MB is 47.70% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue May 27 08:56:36 2008
ARC2: Archival started
ARC1: STARTING ARCH PROCESSES COMPLETE
ARC1: Becoming the heartbeat ARCH
ARC2 started with pid=34, OS id=14332402
Tue May 27 08:56:37 2008
Successfully onlined Undo Tablespace 1.
Tue May 27 08:56:37 2008
SMON: enabling tx recovery
Tue May 27 08:56:37 2008
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=35, OS id=14291208
Tue May 27 08:56:40 2008
Completed: ALTER DATABASE OPEN
Tue May 27 09:02:36 2008
Shutting down archive processes
Tue May 27 09:02:41 2008
ARCH shutting down
ARC2: Archival stopped
Tue May 27 10:24:20 2008
Memory Notification: Library Cache Object loaded into SGA
Heap size 3595K exceeds notification threshold (2048K)
KGL object name :XDB.XDbD/PLZ01TcHgNAgAIIegtw==
Tue May 27 10:24:21 2008
Memory Notification: Library Cache Object loaded into SGA
Heap size 3774K exceeds notification threshold (2048K)
Details in trace file /opt/oracle/admin/webapp/udump/webapp_ora_13967468.trc
KGL object name :XDB.XDJ7JY/ksrgOzgQ8CoEgGA7A==

<think>嗯,用户问的是关于DAT文件无法打开的问题。这确实是个常见困扰,因为DAT文件本身就像个"黑盒子"——它可以是任何数据的容器。用户点击后没反应时的焦虑我很理解,就像拿到个没标签的罐头却找不到开罐器。 让我拆解下核心痛点:首先用户需要判断这个DAT的"真身",是邮件附件里的winmail.dat?还是监控录像的专用格式?或者是游戏存档?不同场景解法完全不同。用户可能已经尝试过双击失败,才会来寻求帮助。 注意到用户没提具体场景,所以得覆盖所有可能性。先从最温和的解决方案开始:用记事本暴力试探。虽然大概率看到乱码,但万一发现"PK"头就能立刻锁定是zip文件。这个操作零成本,值得优先推荐。 考虑到普通用户的技术水平,专业工具要谨慎推荐。比如提到WinHex时得强调"十六进制查看",避免用户误以为是普通软件。对于视频类的DAT,必须提醒VLC这个万能播放器——毕竟它连损坏的视频都能勉强解析。 特别要警示注册表操作的风险。上次有用户按网上教程乱改.dat关联,结果系统崩溃来哭诉。所以这部分必须用⚠️强化警告,甚至考虑要不要删掉这段...但为了完整性还是保留吧。 最后想到个隐藏陷阱:某些恶意软件会伪装成.dat。得提醒用户注意来源可信度,上次有用户中招就是因为强行打开了"发票.dat"。 (翻查技术手册补充)噢对,Win10的默认程序关联设置藏得深,在"选择按文件类型指定的应用"里能找到.dat项。这个路径必须写清楚,毕竟微软总爱改设置入口...</think>DAT文件无法直接打开通常是因为系统没有关联的默认程序,或者文件本身并非可执行文件。以下是系统级分析和解决方案: ### 一、原因解析 1. **无关联程序** DAT是通用数据容器(Data File),系统无法自动识别其内容类型。需根据实际内容选择打开方式。 *例如:邮件附件中的`winmail.dat`是TNEF格式,需专用解码器;监控录像的DAT文件需配套播放器* 2. **文件内容类型** - 📁 **文本数据**:日志、配置信息(可用文本编辑器打开) - 📹 **媒体文件**:部分视频/音频的封装格式(如VCD的`AVSEQ01.DAT`) - 🔐 **加密数据**:程序专用格式(如游戏存档、数据库文件) - 🧩 **混合类型**:包含二进制+文本的复合结构 3. **文件损坏风险** 错误修改扩展名可能导致文件头损坏(如将`.exe`重命名为`.dat`后无法执行) ### 二、打开方法(逐步操作) #### ▶ 基础方案:文本编辑器探测 ```powershell # Windows快速验证文件类型: certutil -hashfile "文件路径.dat" MD5 # 生成校验码比对已知类型 notepad "C:\path\to\file.dat" # 强制用记事本打开 ``` - **乱码判断**:若显示`ÿ&Oslash;ÿà`等特殊字符,可能是图片/视频;出现`PK`开头可能是ZIP压缩包 #### ▶ 进阶方案:按来源推断 | **文件来源** | **推荐工具** | **操作提示** | |---------------------|-------------------------------|----------------------------------| | 电子邮件附件 | Winmail.dat Viewer | 解码Outlook专属格式 | | 监控录像 | 厂商播放器(如海康威视iVMS) | 需同步下载.index索引文件 | | 游戏存档 | Save Editor在线工具 | 搜索特定游戏名+save editor | | VCD视频 | VLC Media Player | 直接拖入播放 | #### ▶ 专业工具链 1. **十六进制分析**(检测真实类型) - 工具:HxD(Windows)、Bless(Linux) - 关键操作:查看文件头签名(首2-8字节) *常见签名对照:* - `FF D8 FF` → JPEG图片 - `47 40 00` → MPEG-TS视频 2. **格式转换**(以视频DAT为例) ```bash ffmpeg -i input.dat -c:v libx264 output.mp4 # 转码为通用MP4 ``` ### 三、特殊场景处理 - **注册表关联错误**: Win+R输入`regedit` → 定位`计算机\HKEY_CLASSES_ROOT\.dat` → 删除错误关联项 - **伪装的恶意文件**: 用7-Zip右键检查,若内含`.exe`或`.vbs`需立即扫描病毒 ### ⚠️ 重要警示 1. **修改扩展名风险** ```mermaid graph LR A[原文件file.exe] -->|重命名为.dat| B[file.dat] B -->|双击尝试打开| C{系统行为} C -->|关联文本工具| D[显示乱码] C -->|关联错误程序| E[执行失败] ``` 此时需**还原正确扩展名**:命令行执行`ren "file.dat" "file.exe"` 2. **数据恢复预案** 操作前复制备份:`copy /y "source.dat" "backup.dat"` ### 四、自动化推荐方案 ```python # Python自动检测文件类型(需安装python-magic) import magic def detect_file_type(file_path): mime = magic.Magic(mime=True) file_type = mime.from_file(file_path) print(f"真实类型: {file_type}") return "视频" if "video" in file_type else "文本" if "text" in file_type else "二进制" ``` > 执行示例:`detect_file_type("unknown.dat")` → 输出`video/mp2t` ---
评论 1
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值