精华内容
下载资源
问答
  • ORACLE startup过程

    2021-05-02 06:45:49
    Starting Up an Oracle Database Instance: NOMOUNTWhen starting the database instance, select the state in which it starts. The following scenarios describe different stages of starting up an instance.A...

    Starting Up an Oracle Database Instance: NOMOUNT

    When starting the database instance, select the state in which it starts. The following scenarios describe different stages of starting up an instance.

    An instance is typically started only in NOMOUNT mode during database creation,

    during re-creation of control files, or during certain backup and recovery scenarios.

    Starting an instance includes the following tasks:

    •Searching /database for a file of a particular name in this order:

    -spfile.ora

    -If not found, spfile.ora

    -If not found, init.ora

    This is the file that contains initialization parameters for the instance. Specifying the PFILE parameter with STARTUP overrides the default behavior.

    •Allocating the SGA

    •Starting the background processes

    •Opening the alert.log file and the trace files

    Note:SID is the system ID, which identifies the instance (for example, ORCL).

    Starting Up an Oracle Database Instance: MOUNT

    Mounting a database includes the following tasks:

    •Associating a database with a previously started instance

    •Locating and opening the control files specified in the parameter file

    •Reading the control files to obtain the names and statuses of the data files and online redo log files. However, no checks are performed to verify the existence of the data files and online redo log files at this time.

    To perform. specific maintenance operations, start an instance and mount a database, but do not open the database.

    For example, the database must be mounted but must not be opened during the following tasks:

    •Renaming data files (Data files for an offline tablespace can be renamed when the database is open.)

    •Enabling and disabling online redo log file archiving options

    •Performing full database recovery

    Note:A database may be left in MOUNT mode even though an OPEN request has been made. This may be because the database needs to be recovered in some way.

    Starting Up an Oracle Database Instance: OPEN

    A normal database operation means that an instance is started and the database is mounted and opened. With a normal database operation, any valid user can connect to the database and perform. typical data access operations.

    Opening the database includes the following tasks:

    •Opening the online data files

    •Opening the online redo log files

    If any of the data files or online redo log files are not present when you attempt to open the database, then the Oracle server returns an error.

    During this final stage, the Oracle server verifies that all the data files and online redo log files can be opened and checks the consistency of the database. If necessary, the System Monitor (SMON) background process initiates instance recovery.

    You can start up a database instance in restricted mode so that it is available to users with administrative privileges only. To start an instance in restricted mode, select the “Restrict access to database” option on the Advanced Startup Options page.

    展开全文
  • oracle startup的选项

    2021-05-06 09:03:47
    每当一个Oracle数据库启动时,它都经历一系列步骤来保证数据库一致性。当一个数据库启动时,它经历三个模式:NOMOUNT、MOUNT和OPEN。STARTUP NOMOUNT选项:(读初始化参数文件,启动实例)STARTUP NOMOUNT选项启动实例...

    每当一个Oracle数据库启动时,它都经历一系列步骤来保证数据库一致性。

    当一个数据库启动时,它经历三个模式:NOMOUNT、MOUNT和OPEN。

    STARTUP NOMOUNT选项:(读初始化参数文件,启动实例)

    STARTUP NOMOUNT选项启动实例,但不安装数据库。当数据库以这个模式启动时,参数文件被读取;后台进程和内存结构被启动;但它们不被附加或与数据库的磁盘结构进行通信。当实例处于这个状态时,数据库是不可使用的。

    STARTUP MOUNT选项:(打开控制文件)

    STARTUP MOUNT选项执行STARTUP NOMOUNT选项的所有工作,但另外附加数据库结构并与这些结构进行交互。这时Oracle从它用来查找和附加到主要数据库结构的控制文件中获得信息。当处于这个模式时,可以执行一些管理型任务,比如恢复。

    STARTUP OPEN选项:(打开数据文件,日志文件)

    如果STARTUP命令行上没有指定任何模式,STARTUP OPEN选项就是默认的启动模式。STARTUP OPEN选项执行STARTUP NOMOUNT和STARTUP MOUNT选项的所有步骤。这个选项把数据库变成对所有用户都时可用的。

    STARTUP FORCE选项:

    如果在用正常方式启动数据库时遇到了困难,可以使用STARTUP FORCE选项。STARTUP FORCE选项首先异常关闭数据库,然后重新启动它。

    STARTUP RESTRICT选项:

    STARTUP RESTRICT选项启动数据库并把它置入OPEN模式,但只给拥有RESTRICTED SESSION权限的用户赋予访问权。

    alter system enable restricted session;(限制会话权限)

    alter system disable restricted session;(禁止限制会话权限)

    只读模式:

    startup mount;

    alter database open read only;(只读模式,切换只读模式需要重启数据库)

    最后,可以在多个地方启动数据库,像命令行、sqlplus和EM Database Control。这全凭读者的个人喜好。

    展开全文
  • 每当一个Oracle数据库启动时,它都经历一系列步骤来保证数据库一致性。当一个数据库启动时,它经历三个模式:NOMOUNT、MOUNT和OPEN。STARTUP NOMOUNT选项:(读初始化参数文件,启动实例)STARTUP NOMOUNT选项启动实例...

    每当一个Oracle数据库启动时,它都经历一系列步骤来保证数据库一致性。

    当一个数据库启动时,它经历三个模式:NOMOUNT、MOUNT和OPEN。

    STARTUP NOMOUNT选项:(读初始化参数文件,启动实例)

    STARTUP NOMOUNT选项启动实例,但不安装数据库。当数据库以这个模式启动时,参数文件被读取;后台进程和内存结构被启动;但它们不被附加或与数据库的磁盘结构进行通信。当实例处于这个状态时,数据库是不可使用的。

    STARTUP MOUNT选项:(打开控制文件)

    STARTUP MOUNT选项执行STARTUP NOMOUNT选项的所有工作,但另外附加数据库结构并与这些结构进行交互。这时Oracle从它用来查找和附加到主要数据库结构的控制文件中获得信息。当处于这个模式时,可以执行一些管理型任务,比如恢复。

    STARTUP OPEN选项:(打开数据文件,日志文件)

    如果STARTUP命令行上没有指定任何模式,STARTUP OPEN选项就是默认的启动模式。STARTUP OPEN选项执行STARTUP NOMOUNT和STARTUP MOUNT选项的所有步骤。这个选项把数据库变成对所有用户都时可用的。

    STARTUP FORCE选项:

    如果在用正常方式启动数据库时遇到了困难,可以使用STARTUP FORCE选项。STARTUP FORCE选项首先异常关闭数据库,然后重新启动它。

    STARTUP RESTRICT选项:

    STARTUP RESTRICT选项启动数据库并把它置入OPEN模式,但只给拥有RESTRICTED SESSION权限的用户赋予访问权。

    alter system enable restricted session;(限制会话权限)

    alter system disable restricted session;(禁止限制会话权限)

    只读模式:

    startup mount;

    alter database open read only;(只读模式,切换只读模式需要重启数据库)

    最后,可以在多个地方启动数据库,像命令行、sqlplus和EM Database Control。这全凭读者的个人喜好。

    本文出自 “飞舞的菜刀” 博客

    展开全文
  • 再进入系统的时候,启动ORACLE服务失败。发现是startup就失败了操作如下:SQL> startupORACLE 例程已经启动。Total System Global Area218103808 bytesFixed Size 788188 bytesVariable S...

    服务器操作系统windows 2003,用户在数据库使用的情况下重新启动了。再进入系统的时候,启动ORACLE服务失败。发现是startup就失败了操作如下:

    SQL> startup

    ORACLE 例程已经启动。

    Total System Global Area  218103808 bytes

    Fixed Size                   788188 bytes

    Variable Size             146012452 bytes

    Database Buffers           67108864 bytes

    Redo Buffers                4194304 bytes

    数据库装载完毕。

    ORA-01092: ORACLE 例程终止。强制断开连接

    然后查找altersid.log文件,搞不清是什么问题,请教各位如何解决。altersid.log文件内容如下:

    Starting ORACLE instance (force)

    LICENSE_MAX_SESSION = 0

    LICENSE_SESSIONS_WARNING = 0

    Picked latch-free SCN scheme 2

    KCCDEBUG_LEVEL = 0

    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST

    Autotune of undo retention is turned on.

    Dynamic strands is set to TRUE

    Running with 2 shared and 18 private strand(s). Zero-copy redo is FALSE

    IMODE=BR

    ILAT =18

    LICENSE_MAX_USERS = 0

    SYS auditing is disabled

    Starting up ORACLE RDBMS Version: 10.1.0.2.0.

    System parameters with non-default values:

    processes                = 150

    shared_pool_size         = 83886080

    large_pool_size          = 8388608

    java_pool_size           = 50331648

    control_files            = D:ORACLEPRODUCT10.1.0ORADATAEXPRESSCONTROL01.CTL, D:ORACLEPRODUCT10.1.0ORADATAEXPRESSCONTROL02.CTL, D:ORACLEPRODUCT10.1.0ORADATAEXPRESSCONTROL03.CTL

    db_block_size            = 8192

    db_cache_size            = 67108864

    _db_handles_cached       = 0

    compatible               = 10.1.0.2.0

    db_file_multiblock_read_count= 16

    db_recovery_file_dest    = D

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0flash_recovery_area

    db_recovery_file_dest_size= 2147483648

    undo_management          = AUTO

    undo_tablespace          = UNDOTBS1

    remote_login_passwordfile= EXCLUSIVE

    db_domain                =

    dispatchers              = (PROTOCOL=TCP) (SERVICE=expressXDB)

    job_queue_processes      = 10

    background_dump_dest     = D:ORACLEPRODUCT10.1.0ADMINEXPRESSBDUMP

    user_dump_dest           = D:ORACLEPRODUCT10.1.0ADMINEXPRESSUDUMP

    core_dump_dest           = D:ORACLEPRODUCT10.1.0ADMINEXPRESSCDUMP

    sort_area_size           = 65536

    db_name                  = express

    open_cursors             = 300

    pga_aggregate_target     = 25165824

    PMON started with pid=2, OS id=2760

    MMAN started with pid=3, OS id=2764

    DBW0 started with pid=4, OS id=2724

    DBW1 started with pid=5, OS id=2728

    LGWR started with pid=6, OS id=2732

    CKPT started with pid=7, OS id=2736

    SMON started with pid=8, OS id=1140

    RECO started with pid=9, OS id=2784

    CJQ0 started with pid=10, OS id=1504

    Wed Jun 11 17:12:56 2008

    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...

    starting up 1 shared server(s) ...

    Wed Jun 11 17:12:56 2008

    ALTER DATABASE   MOUNT

    Wed Jun 11 17:12:56 2008

    Controlfile identified with block size 16384

    Wed Jun 11 17:13:00 2008

    Setting recovery target incarnation to 2

    Wed Jun 11 17:13:00 2008

    Successful mount of redo thread 1, with mount id 2918455896

    Wed Jun 11 17:13:00 2008

    Database mounted in Exclusive Mode.

    Completed: ALTER DATABASE   MOUNT

    Wed Jun 11 17:13:00 2008

    ALTER DATABASE OPEN

    Wed Jun 11 17:13:00 2008

    Beginning crash recovery of 1 threads

    attempting to start a parallel recovery with 15 processes

    parallel recovery started with 15 processes

    Wed Jun 11 17:13:01 2008

    Started first pass scan

    Wed Jun 11 17:13:01 2008

    Completed first pass scan

    1 redo blocks read, 0 data blocks need recovery

    Wed Jun 11 17:13:01 2008

    Started redo application at

    Thread 1: logseq 1325, block 2, scn 0.6145417

    Recovery of Online Redo Log: Thread 1 Group 1 Seq 1325 Reading mem 0

    Mem# 0 errs 0: D:ORACLEPRODUCT10.1.0ORADATAEXPRESSREDO01.LOG

    Wed Jun 11 17:13:01 2008

    Completed redo application

    Wed Jun 11 17:13:01 2008

    Completed crash recovery at

    Thread 1: logseq 1325, block 3, scn 0.6165419

    0 data blocks read, 0 data blocks written, 1 redo blocks read

    Wed Jun 11 17:13:01 2008

    Thread 1 advanced to log sequence 1326

    Maximum redo generation record size = 120832 bytes

    Maximum redo generation change vector size = 116476 bytes

    Private_strands 4 at log switch

    Thread 1 opened at log sequence 1326

    Current log# 2 seq# 1326 mem# 0: D:ORACLEPRODUCT10.1.0ORADATAEXPRESSREDO02.LOG

    Successful open of redo thread 1

    Wed Jun 11 17:13:01 2008

    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

    Wed Jun 11 17:13:01 2008

    SMON: enabling cache recovery

    Wed Jun 11 17:13:01 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressudumpexpress_ora_2848.trc:

    ORA-00704: 引导程序进程失败

    ORA-00604: 递归 SQL 级别 1 出现错误

    ORA-04031: 无法分配 4096 字节的共享内存 ("shared pool","create table bootstrap$ ( li...","Typecheck heap","kgghteInit&quot

    9f7588d3b12cd5d674b5f81c0b8fc6cb.gif

    Wed Jun 11 17:13:01 2008

    Error 704 happened during db open, shutting down database

    USER: terminating instance due to error 704

    Wed Jun 11 17:13:02 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_dbw0_2724.trc:

    ORA-00704: bootstrap process failure

    Wed Jun 11 17:13:02 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_lgwr_2732.trc:

    ORA-00704: bootstrap process failure

    Wed Jun 11 17:13:02 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_dbw1_2728.trc:

    ORA-00704: bootstrap process failure

    Wed Jun 11 17:13:02 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_ckpt_2736.trc:

    ORA-00704: bootstrap process failure

    Wed Jun 11 17:13:03 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_reco_2784.trc:

    ORA-00704: bootstrap process failure

    Wed Jun 11 17:13:03 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_pmon_2760.trc:

    ORA-00704: bootstrap process failure

    Wed Jun 11 17:13:03 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_smon_1140.trc:

    ORA-00704: bootstrap process failure

    Wed Jun 11 17:13:03 2008

    Errors in file d

    5b24fae4cde99750994428c024162093.gifracleproduct10.1.0adminexpressdumpexpress_mman_2764.trc:

    ORA-00704: bootstrap process failure

    Instance terminated by USER, pid = 2848

    ORA-1092 signalled during: ALTER DATABASE OPEN...

    文件express_ora_2848.trc见附件express_ora_2848.txt

    267abf8789d6bad6eaf3c8c87b18d9ed.gif

    2008-6-11 17:23 上传

    点击文件名下载附件

    104.2 KB, 下载次数: 18

    展开全文
  • oracle9 startup时 报错ORA-00600: 内部错误代码,参数: [kcratr1_lostwrt], [], [], [], [], [], [], []原因可能是非法关机或掉电造成,以下是出现的问题及解决方法:C:\Documents and Settings\Administrator>...
  • 今天为了修改一个数据库的属性,需要将数据库修改到挂载(mount)状态,却出现了‘继续执行将不安全 ORA-03114: 未连接到ORACLE’的问题。这里分享一下解决的方案:本机安装两个数据库,分别为orac和orcl121,默认连接...
  • 当你访问Oracle数据库是若出现ORA-01033‘Oracle startup or shutdown in progress’错误,则说明连接到的Oracle实例正在处于一个startup或shutdown的过程中,且该过程尚未结束。对于此种问题首先要查看alert.log即...
  • oracle startup shutdown命令写些基础的! 对自己还是有好处的.shutdown有四个参数:normal、transactional、immediate、abort。缺省不带任何参数时表示是normal一:shutdown normal:不断开现在连接的用户,阻止任何...
  • Oracle启动失败startup - 闪回空间满登录失败sqlplus / as sysdb登录后:startup失败,ORA-03113: end-of-file on communication channel查看日志:SQL> show parameter db_recovery_file_dest_size;NAME TYPE ...
  • startup,startup mount,startup nomount之间的区别startup nomount选项:(读初始化参数文件,启动实例)startup nomount选项启动实例,但不安装数据库。当数据库以这个模式启动时,参数文件被读取;后台进程和内存...
  • 天萃荷净分享一篇Oracle数据库在打完补丁后startup migrate、startup upgrade区别分析1、为什么要使用Startup MigrateSTARTUP MIGRATE was introduced in 9.2 as a mechanism to be sure that most everything that ...
  • 问题: 首先我搞错了控制文件 然后我执行shutdown immediate再startup就出错了 后面退出执行也是ORA-00205: ???, ???, ??? 解决办法:
  • oracle入门书,其中一句话说,使用startupnomount命令启动例程,不可以和mountopen和exclusive一起使用,这个命令适用于建立数据库或是维护数据库时使用。于是查了一下,为什么不能同时使用,以及他们之间的区别。...
  • ORA-1578 on Oracle Startup

    2021-05-04 02:55:14
    An ORA-1578 on startup is usually bad news and relates to either a corruptrollback segment header, or a corrupt block being referenced duringbootstraping of the instance.eg:Database mounted.ORA-01578:...
  • oracle9 startup时 报错ORA-00600: 内部错误代码,参数: [kcratr1_lostwrt], [], [], [], [], [], [], []原因可能是非法关机或掉电造成,以下是出现的问题及解决方法:C:\Documents and Settings\Administrator>...
  • 在使用sysdba登录Oracle后,显示用的空闲例程就感觉不对劲,果然。 这证明数据库没有正常启动! 解决办法 这种方式每次电脑重启以后,都需要用sysdba的身份启动数据库;优点:能够加深基本的sql密令的印象;缺点:...
  • oracle入门书,其中一句话说,使用startup nomount 命令启动例程,不可以和mount open和exclusive一起使用,这个命令适用于建立数据库或是维护数据库时使用。于是查了一下,为什么不能同时使用,以及他们之间的...
  • 一、摘要Oracle数据库的完整启动过程是分步骤完成的,包含以下3个步骤:启动实例-->加载数据库-->打开数据库因为Oracle数据库启动过程中不同的阶段可以对数据库进行不同的维护操作,对应我们不同的需求,所以...
  • 今天,一实施同事求助,说一地市oracle数据库无法通过远程连接,连接报错如图:操作系统:windows server2008 R2数据库版本:oracle 11.2.0.1初看报错貌似数据库正处在打开或关闭的过程中。查看告警日志,最近的一次...
  • oracle升级操作步骤

    2021-05-05 02:30:36
    --*********************************-- Oracle 10.2.0.1 升级到 10.2.0.4--*********************************数据库升级并不难,只要遵循其步骤,一般问题不大。但是升级失败的情况也是屡见不鲜,尤其是生产数据库...
  • 启动数据库 SYS@PROD1> startup ORACLE instance started. Total System Global Area 521936896 bytes Fixed Size 2254824 bytes Variable Size 373295128 bytes Database Buffers 138412032 bytes Redo Buffers ...
  • 该楼层疑似违规已被系统折叠 隐藏此楼查看此...$ umount /dev/shm [oracle@oracle11g ~]$ mount /dev/shm 查看shm大小 [oracle@oracle11g ~]$ df -h |grep shm none 1.0G 308M 200M 30% /dev/shm 重新启动oracle,OK!
  • Oracle下启动与关闭大致都是由3个步骤完成,在启动时分别是:启动实例、加载数据库、打开数据库;关闭时分别是:关闭数据库、卸载数据库、关闭Oracle实例。所以在Oracle因为这种严谨的风格下,使得在平时可以根据...
  • ************************************************************************ ARCH: Error 19809 Creating archive log file to 'D:\ORACLE\ER1\ORAFLASH\ER1\ARCHIVELOG\2012_07_18\O1_MF_1_1626_%U_.ARC' Errors ...
  • oracle 多个例程,启动具体例程 startup pfile如果环境是AIX系统,安装了oracle,具有多个例程(实例instance),有一个默认的实例,启动其他实例怎么办?如果说存在orcl1,orcl2,orcl3,单个例程,默认的为orcl1,...
  • 在linux下装了一个oracle 10g,登录sqlplus 后,显示SQL> startupORACLE ???????Total System Global Area 167772160 bytesFixed Size 1218316 bytesVariable Size 67111156 bytesDatabase Buf...
  • Oracle启动时ORA 00600错误处理方法oracle startup时 报错ORA-00600: 内部错误代码,参数: [kcratr1_lostwrt], [], [], [], [], [], [], []原因可能是非法关机或掉电造成,以下是出现的问题及解决方法:C:\Documents ...
  • 不小心删除掉了备份文件导致oracle挂掉,报了控制文件丢失的问题 1.停止oracle shutdown abort 2.nomount 启动oracle startupnomount 3.修改控制文件的位置 ...alter system set control_files=$...startupmount ...
  • startup 后报错ORA-03113: end-of-file on communication channel二、查找原因查看alter日志tail -500 /oracle/database/oracle/diag/rdbms/udb/udb1/trace/alter_UDB1.logUnable to create archi...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 122,456
精华内容 48,982
关键字:

oraclestartup