数据库ORA-03113排查
提示ORA-03113:通信通道的文件结尾解决
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@CP07_NV1_DB ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Mon Dec 12 13:48:35 2016
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size 2235208 bytes
Variable Size 822084792 bytes
Database Buffers 3439329280 bytes
Redo Buffers 12132352 bytes
Database mounted.
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES BLOCKSIZE MEMBERS ARC
---------- ---------- ---------- ---------- ---------- ---------- ---
STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
---------------- ------------- --------- ------------ ---------
1 1 88281 52428800 512 1 NO
INACTIVE 1179936249 12-DEC-16 1179945253 12-DEC-16
4 1 88283 57671680 512 1 NO
CURRENT 1179952814 12-DEC-16 2.8147E+14
3 1 88280 52428800 512 1 NO
INACTIVE 1179929281 12-DEC-16 1179936249 12-DEC-16
GROUP# THREAD# SEQUENCE# BYTES BLOCKSIZE MEMBERS ARC
---------- ---------- ---------- ---------- ---------- ---------- ---
STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
---------------- ------------- --------- ------------ ---------
2 1 88282 52428800 512 1 NO
INACTIVE 1179945253 12-DEC-16 1179952814 12-DEC-16
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> recover database until time '2016-12-11';
Media recovery complete.
SQL> alter database open resetlogs;
Database altered.
SQL> select open_mode from $database;
select open_mode from $database
*
ERROR at line 1:
ORA-00911: invalid character
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES BLOCKSIZE MEMBERS ARC
---------- ---------- ---------- ---------- ---------- ---------- ---
STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
---------------- ------------- --------- ------------ ---------
1 1 1 52428800 512 1 NO
CURRENT 1179956666 12-DEC-16 2.8147E+14
2 1 0 52428800 512 1 YES
UNUSED 0 0
3 1 0 52428800 512 1 YES
UNUSED 0 0
GROUP# THREAD# SEQUENCE# BYTES BLOCKSIZE MEMBERS ARC
---------- ---------- ---------- ---------- ---------- ---------- ---
STATUS FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
---------------- ------------- --------- ------------ ---------
4 1 0 57671680 512 1 YES
UNUSED 0 0
重置日志的序列号
SQL> select member from v$logfile;
MEMBER
--------------------------------------------------------------------------------
/u01/app/oracle/oradata/CP07NV1D/redo03.log
/u01/app/oracle/oradata/CP07NV1D/redo02.log
/u01/app/oracle/oradata/CP07NV1D/redo01.log
/u01/app/oracle/oradata/CP07NV1D/redo04.log
[oracle@CP07_NV1_DB ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Mon Dec 12 14:07:10 2016
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select status from v$instance;
STATUS
------------
OPEN
SQL> select * from scott.emp;
EMPNO ENAME JOB MGR HIREDATE SAL COMM
---------- ---------- --------- ---------- --------- ---------- ----------
DEPTNO
----------
7369 SMITH CLERK 7902 17-DEC-80 800
20
7499 ALLEN SALESMAN 7698 20-FEB-81 1600 300
30
7521 WARD SALESMAN 7698 22-FEB-81 1250 500
SQL> select group#,sequence#,bytes,members,status from v$log;
GROUP# SEQUENCE# BYTES MEMBERS STATUS
---------- ---------- ---------- ---------- ----------------
1 1 52428800 1 INACTIVE
2 2 52428800 1 CURRENT
3 0 52428800 1 UNUSED
4 0 57671680 1 UNUSED
SQL> alter system switch logfile;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> SQL> select open_mode from v$database;
OPEN_MODE
--------------------
READ WRITE
SQL> select open_mode from v$database;
OPEN_MODE
--------------------
READ WRITE
SQL> select group#,sequence#,bytes,members,status from v$log;
GROUP# SEQUENCE# BYTES MEMBERS STATUS
---------- ---------- ---------- ---------- ----------------
1 5 52428800 1 INACTIVE
2 6 52428800 1 INACTIVE
3 7 52428800 1 CURRENT
4 4 57671680 1 INACTIVE
SQL> select member from v$logfile;
MEMBER
--------------------------------------------------------------------------------
/u01/app/oracle/oradata/CP07NV1D/redo03.log
/u01/app/oracle/oradata/CP07NV1D/redo02.log
/u01/app/oracle/oradata/CP07NV1D/redo01.log
/u01/app/oracle/oradata/CP07NV1D/redo04.log
SQL> select file#,checkpoint_change# from v$datafile;
FILE# CHECKPOINT_CHANGE#
---------- ------------------
1 1180436432
2 1180436432
3 1180436432
4 1180436432
5 1180436432
6 1180436432
6 rows selected.
SQL> select file#,checkpoint_change# from v$datafile_header;
FILE# CHECKPOINT_CHANGE#
---------- ------------------
1 1180452436
2 1180452436
3 1180452436
4 1180452436
5 1180452436
6 1180452436
6 rows selected.
SQL>
第二步:
免责声明:
① 本站未注明“稿件来源”的信息均来自网络整理。其文字、图片和音视频稿件的所属权归原作者所有。本站收集整理出于非商业性的教育和科研之目的,并不意味着本站赞同其观点或证实其内容的真实性。仅作为临时的测试数据,供内部测试之用。本站并未授权任何人以任何方式主动获取本站任何信息。
② 本站未注明“稿件来源”的临时测试数据将在测试完成后最终做删除处理。有问题或投稿请发送至: 邮箱/279061341@qq.com QQ/279061341
数据库ORA-03113排查
下载Word文档到电脑,方便收藏和打印~
下载Word文档猜你喜欢2024-04-022023-09-06MySQL INSERT锁与数据库故障排查
在MySQL中,当执行INSERT操作时,会自动对被插入的行进行加锁以确保数据的一致性。INSERT操作会在执行时对被插入的行进行加锁,以防止其他事务对同一行进行修改或删除。这种锁称为INSERT锁。如果在执行INSERT操作时出现数据库2024-08-19数据库死锁排查及处理方法
1.查询是否锁表 show OPEN TABLES where In_use > 0; 2.查询进程(如果您有SUPER权限,您可以看到所有线程。否则,您只能看到您自己的线程) show processlist 3.杀死进程id(就是上面命令的id列) kil2015-10-31数据库连接池满了如何排查
当数据库连接池满了,可能会导致应用程序无法获取数据库连接,从而无法进行数据库操作。以下是一些排查问题的步骤:检查数据库连接池的配置参数:检查数据库连接池的配置文件,确认最大连接数和空闲连接数是否合理。如果最大连接数设置过小,可能会导致连接池2023-10-272024-04-02php如何查询数据库并正序排列
今天小编给大家分享一下php如何查询数据库并正序排列的相关知识点,内容详细,逻辑清晰,相信大部分人都还太了解这方面的知识,所以分享这篇文章给大家参考一下,希望大家阅读完这篇文章后有所收获,下面我们一起来了解一下吧。一、什么是数据库查询正序排2023-07-05Oracle数据库ODBC连接故障排查流程
Oracle数据库ODBC连接故障排查流程如下:检查ODBC数据源配置:首先确保ODBC数据源配置正确,包括数据库实例名、用户名、密码等信息。测试连接:使用ODBC数据源配置工具测试连接是否正常,若连接失败可能说明配置有误。检查网络连接:检2024-07-15MySQL INSERT锁与数据库故障排查流程
MySQL INSERT锁是指在执行INSERT语句时,MySQL会为新插入的数据行加锁,以确保数据的一致性和完整性。当有其他会话尝试读取或修改被锁定的数据行时,会话将被阻塞,直到INSERT语句执行完成并释放锁。数据库故障排查流程如下:2024-08-132024-04-022023-05-142023-08-312024-04-02怎么使用ThinkPHP5进行数据库查询排序
这篇文章主要讲解了“怎么使用ThinkPHP5进行数据库查询排序”,文中的讲解内容简单清晰,易于学习与理解,下面请大家跟着小编的思路慢慢深入,一起来研究和学习“怎么使用ThinkPHP5进行数据库查询排序”吧!在进行数据库查询时,排序是一个2023-07-052024-04-022024-04-022024-04-02如何在oracle数据库中查看ora报错
在Oracle数据库中,可以通过查看数据库日志文件和使用SQL语句来查看ORA错误。查看数据库日志文件:在Oracle数据库的安装目录下,有一个名为alert_数据库实例名.log的日志文件。可以使用文本编辑器(如Notepad++)打开2024-04-092024-04-022023-10-11热门标签
编程热搜[mysql]mysql8修改root密码
use mysqlselect * from user where user="root";update user set password=password("mysql@2020") where user="root";ERROR 1064 (42000)MySQL专题3之MySQL管理
1、启动以及关闭MySQL服务器- 首先,我们需要通过以下命令来检查MySQL服务器是否已经启动:ps -ef | grep mysqld- 如果MySQL已经启动,以上命令将输出mysql进程列表,如果mysql未启动,你可以使用以下
编程资源站- 资料下载
- 历年试题
目录反馈
我要
反馈