标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2131 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (103)
- 数据库 (1,727)
- DB2 (22)
- MySQL (74)
- Oracle (1,581)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (160)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (68)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (579)
- Oracle安装升级 (94)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (81)
- PostgreSQL (24)
- PostgreSQL恢复 (11)
- SQL Server (28)
- SQL Server恢复 (9)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- 当前主流数据库版本服务支持周期-202503
- pg启动报invalid checkpoint record处理
- 删除redo导致ORA-00313 ORA-00312故障处理
- Navicat连接postgresql时出现column “datlastsysoid” does not exist错误解决
- aix磁盘损坏oracle数据库恢复
- pg误删除数据恢复(PostgreSQL delete数据恢复)
- PostgreSQL表文件损坏恢复—pdu恢复损坏的表文件
- linux rm -rf 删除数据文件恢复
- PostgreSQL恢复工具—pdu恢复单个表文件
- PostgreSQL恢复工具—pdu工具介绍
- 近1万个数据文件的恢复case
- 不当使用_allow_resetlogs_corruption参数引起ORA-600 2662错误
- CSSD signal 11 in thread clssnmRcfgMgrThread故障处理
- 使用sid方式直接访问pdb(USE_SID_AS_SERVICE_LISTENER)
- ORA-00069: cannot acquire lock — table locks disabled for xxxx
- ORA-600 [4000] [a]相关bug
- sql server数据库“正在恢复”故障处理
- 如何判断数据文件是否处于begin backup状态
- CDM备份缺少归档打开数据库报ORA-600 kcbzib_kcrsds_1故障处理
- ORA-07445: exception encountered: core dump [expgod()+43] [IN_PAGE_ERROR]
标签归档:pg启动异常处理
pg启动报invalid checkpoint record处理
pg库启动报PANIC: could not locate a valid checkpoint record错误
2025-03-09 10:59:10.365 EDT [73013] LOG: starting PostgreSQL 16.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5), 64-bit 2025-03-09 10:59:10.365 EDT [73013] LOG: listening on IPv4 address "0.0.0.0", port 5432 2025-03-09 10:59:10.365 EDT [73013] LOG: listening on IPv6 address "::", port 5432 2025-03-09 10:59:10.367 EDT [73013] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" 2025-03-09 10:59:10.401 EDT [73018] LOG: database system was interrupted; last known up at 2025-03-09 10:54:43 EDT 2025-03-09 10:59:11.506 EDT [73018] LOG: invalid checkpoint record 2025-03-09 10:59:11.508 EDT [73018] PANIC: could not locate a valid checkpoint record 2025-03-09 10:59:12.004 EDT [73013] LOG: startup process (PID 73018) was terminated by signal 6: Aborted 2025-03-09 10:59:12.004 EDT [73013] LOG: aborting startup due to startup process failure 2025-03-09 10:59:12.006 EDT [73013] LOG: database system is shut down
从报错信息中看,是有无法读取到有效的checkpoint记录导致,初步怀疑是wal异常,检查pg_wal目录,发现wal日志为空
[root@localhost pg_wal]# ls -ltr total 16388 drwx------ 2 postgres postgres 6 Mar 6 08:10 archive_status [root@localhost pg_wal]#
进一步检查系统操作命令rm删除wal日志命令
cd pg_wal rm -rf 0000000*
初步确认是由于wal日志被意外删除导致pg库无法启动,尝试重置wal,由于库不是干净关闭,无法直接重置成功
[postgres@localhost log]$ pg_resetwal $PGDATA The database server was not shut down cleanly. Resetting the write-ahead log might cause data to be lost. If you want to proceed anyway, use -f to force reset.
使用pg_resetwal -f强制重置
[postgres@localhost log]$ pg_resetwal -f $PGDATA Write-ahead log reset
尝试启动pg库成功
[postgres@localhost log]$ pg_ctl start waiting for server to start....2025-03-09 11:02:02.609 EDT [73088] LOG: redirecting log output to logging collector process 2025-03-09 11:02:02.609 EDT [73088] HINT: Future log output will appear in directory "log". done server started
2025-03-09 11:02:02.609 EDT [73088] LOG: starting PostgreSQL 16.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5), 64-bit 2025-03-09 11:02:02.609 EDT [73088] LOG: listening on IPv4 address "0.0.0.0", port 5432 2025-03-09 11:02:02.609 EDT [73088] LOG: listening on IPv6 address "::", port 5432 2025-03-09 11:02:02.610 EDT [73088] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" 2025-03-09 11:02:02.645 EDT [73092] LOG: database system was shut down at 2025-03-09 11:01:53 EDT 2025-03-09 11:02:02.650 EDT [73088] LOG: database system is ready to accept connections