ORA-01092 ORACLE instance terminated. Disconnection forcedCause: The instance connected to was terminated abnormally, probably due to a SHUTDOWN ABORT. The current process was forced to disconnect from the instance.Action: Examine the alert log for more details. Contact the database administrator to determine when the instance is restarted. Attempt to reconnect after the instance is running again.
解决方案 »
- oracle不同的用户可以看到不同的数据库么?
- oracle正在初始化或在关闭,请稍后再试。
- 执行以下命令的时候报错,请帮忙看一下,谢谢
- 将一个表中的数据插入到另一个表中,两个表的结构一样,问sql文怎么写?谢谢!
- dblink连接后查询大表无响应
- 哪儿能下载到LogMiner??
- 菜鸟写触发器和存储过程的问题,急,在线等!!!
- update ..... (比较更新)!
- 请教高手:怎么对oracle数据库进行自动备份!
- 初学ORACLE,有使用SQL SERVER的基础,请帮忙介绍基本学习ORACLE的书籍
- ★★★★各位高手帮忙看看,为什么新建的快照不能执行?●●●●
- pb中如何调用oracle存储过程
svrmgrl>connect internal
svrmgrl>startup mount
svrmgrl>alter database open;
SQL>
这时候,我们可以退出SQLPLUS,然后重新进来:
SQL> exit
E:\>sqlplus internal
进来后,shutdown abort数据库,然后,再startup mount:
SQL> shutdown abort
SQL> startup mount
可以看到,数据库没有CRASH。现在我们CLEAR GROUP4,先用alter database clear logfile group 4;(如果不行就用alter database clear unarchived logfile group 4;):
SQL> alter database clear logfile group 4;
数据库已更改。
SQL> alter database open;
数据库已更改。
SQL>
好了,数据库已经恢复了
如果正在写入当前组的所有成员时,LGWR 突然无法访问这些成员,则该数据库例程关闭,在这种情况下,数据库可能需要从联机日志文件残留物进行介质恢复。
Problem:
Your Oracle Server database on OpenVMS crashes. The following errors are reported: Background process DBWR unexpectedly terminated with error 1092
ORA-1092 Oracle instance terminated
ORA-313 open failed for members of log group 'n' of thread 'n'
ORA-600 [3228] reported from a PL/SQL script.
Explanation:
The most significant error reported here is the ORA-313 error. This error indicates a failure to open a file which indicates a problem with OpenVMS resources. When either CHANNELCNT and/or FILLM are too small, these errors can result.
Solution:
Increase the SYSGEN parameter CHANNELCNT. This should be done by an OpenVMS system manager and requires a reboot of your OpenVMS node. For more information on SYSGEN, please review the OpenVMS documentation.
If the CHANNELCNT parameter is already large enough to allow the expected number of files to be opened, check the FILLM quota. Review two areas when you check FILLM:
1) The Oracle background processes (PMON, DBWR, LGWR etc.)
2) The SERVER side (or SHADOW) process created when you use SVRMGRL to start the database. To get an idea of the quota available, use the command: $ SHOW PROCESS /QUOTA /ID=<pid> Where <pid> is the OpenVMS pid of the process to be reviewed. This command displays the remaining 'Open file quota' (FILLM) for the process, as well as other available quotas.
Example:
You have 226 data files, eight REDO log files and three control files for a total of 237 files. The SYSGEN setting for CHANNELCNT is at the default of 256. During normal operation, Oracle periodically needs to open additional files. These include the INIT parameter files, the ALERT log, various DCL scripts, trace files, etc. Under these conditions, a CHANNELCNT value of 256 is too small to accommodate the number of files that Oracle/OpenVMS needs open at the same time.
For most systems the default quotas should be adequate.
If not, please describe the infor u've encountered