DATABASE SHUTDOWN 후 STARTUP시 ORA-7445가 발생하면서 OS PROMPT로 빠짐
제품 : ORACLE SERVER
작성날짜 : 2002-04-10
DATABASE SHUTDOWN 후 STARTUP시 ORA-7445가 발생하면서 OS PROMPT로 빠짐
=====================================================================
Server Platform : Sparc Sunw Ultra Enterprise 10000
(CPU 44개, Main Memory 9 Megabytes)
ORACLE RDBMS 7.3.3.4
ORACLE PARALLEL SERVER 환경
Sun Cluster Volume Manager 2.0
DB size : 약 1.2 Terabytes (=1200 Gigabytes)
관련 TAR : 9168089.7
조치 내역 :
1. init.ora에 다음의 event와 hidden parameter를 설정
1) event="10210 trace name context forever, level 10"
(Data Block Integrity를 check, Refer to Note 21184.1)
2) event="10211 trace name context forever, level 10"
(Data Block Integrity를 check, Refer to Note 21185.1
3) dbblock_cache_protect = true (Refer to note18144.1)
corrupt된 block이 memory에 load되는 것을 방지
2. Startup mount 후 recover database를 실행
ORA-600[6593] [26]발생 - Detection of block corruption
3. alter database open 실행
ORA-1578 file#88 block #172628 발생 하였으나
ORA-7445 없이 open됨
(문제가 되는 특정 테이블과 데이타 블럭 발견)
4. 위의 file block에 data를 확인하기 위하여 block dump를 함
"Alter session set events 'immediate trace name
blockdump level xxxxx"
( xxxxx는 Data Block Address 값의 decimal 값)
- Block dump에 있는 hexa값을 ascii로 변환
5. corrupt된 block을 제외한 data를 recover하기 위하여 새로운
tablespace를 생성 후 다음 실행.
"Insert into (TABLEA) select * from (TABLEB)
where index_column > ' '
and rowid not like 'corrupt된 row의 rowid들';"
(TABLEA는 corrupt되지 않은 row들을 제외한 나머지 row들을
포함할 새로운 테이블이고, TABLEB는 corrupt된 row들을 갖고
있었던 기존의 테이블)
6. 새로 생성한 테이블의 데이타 확인한 후 기존의 corrupt된
테이블 drop시킴
7. 새 테이블을 rename하여 기존의 테이블 이름과 같게 함.
Similar Messages
-
Dear all,
10.2.0.3 on Solaris 10.
When shutting down the database, shutdown hangs after database mounted as you can see below
SQL> startup
ORACLE instance started.
Total System Global Area 1073741824 bytes
Fixed Size 2133800 bytes
Variable Size 435843288 bytes
Database Buffers 624951296 bytes
Redo Buffers 10813440 bytes
Database mounted.In one more session, I checked the alert log
Fri Jan 7 10:13:16 2011
Incremental checkpoint up to RBA [0x417a.3.0], current log tail at RBA [0x417a.87.0]
Fri Jan 7 10:13:16 2011
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=36, OS id=15146
Fri Jan 7 10:13:19 2011
Completed: ALTER DATABASE OPEN
^C
bash-3.00$
bash-3.00$
bash-3.00$
bash-3.00$
bash-3.00$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Fri Jan 7 10:16:28 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
SQL> select open_mode from v$database;
OPEN_MODE
READ WRITEAny idea ?.
KaiThere is no error message . Anyway alert log
Fri Jan 7 10:13:08 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =88
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.3.0.
System parameters with non-default values:
_trace_files_public = TRUE
processes = 400
sessions = 800
timed_statistics = TRUE
shared_pool_size = 419430400
shared_pool_reserved_size= 41943040
sga_target = 1073741824
control_files = /erp/u01/medh/db/apps_st/data/cntrl01.dbf, /erp/u01/medh/db/apps_st/data/cntrl02.dbf, /erp/u01/medh/db/apps_st/data/cnt
rl03.dbf
db_block_checksum = TRUE
log_archive_dest = /oracle/arch/medh_ARCH
log_archive_format = medh%t_%s_%r.arc
log_buffer = 10485760
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1200
db_files = 512
db_file_multiblock_read_count= 8
log_checkpoints_to_alert = TRUE
dml_locks = 10000
undo_management = AUTO
undo_tablespace = APPS_UNDOTS1
db_block_checking = FALSE
session_cached_cursors = 500
utl_file_dir = /usr/tmp, /usr/tmp, /erp/u01/medh/db/tech_st/10.2.0/appsutil/outbound/medh_sed04, /usr/tmp
plsql_native_library_dir = /erp/u01/medh/db/tech_st/10.2.0/plsql/nativelib
plsql_native_library_subdir_count= 149
plsql_code_type = INTERPRETED
plsql_optimize_level = 2
job_queue_processes = 2
cursor_sharing = EXACT
parallel_min_servers = 0
parallel_max_servers = 8
background_dump_dest = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/bdump
user_dump_dest = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/udump
max_dump_file_size = 20480
core_dump_dest = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/cdump
db_name = medh
open_cursors = 600
ifile = /erp/u01/medh/db/tech_st/10.2.0/dbs/medh_sed04_ifile.ora
_sort_elimination_cost_ratio= 5
_b_tree_bitmap_plans = FALSE
_fast_full_scan_enabled = FALSE
_sqlexec_progression_cost= 2147483647
_like_with_bind_as_equality= TRUE
pga_aggregate_target = 1073741824
workarea_size_policy = AUTO
optimizer_secure_view_merging= FALSE
aq_tm_processes = 1
olap_page_pool_size = 4194304
PMON started with pid=2, OS id=12494
PSP0 started with pid=4, OS id=12496
MMAN started with pid=6, OS id=12499
DBW0 started with pid=8, OS id=12511
DBW1 started with pid=3, OS id=12544
DBW2 started with pid=10, OS id=12574
LGWR started with pid=5, OS id=12604
CKPT started with pid=12, OS id=12628
SMON started with pid=14, OS id=12653
RECO started with pid=16, OS id=12680
CJQ0 started with pid=18, OS id=12712
MMON started with pid=20, OS id=12738
MMNL started with pid=22, OS id=12761
Fri Jan 7 10:13:10 2011
ALTER DATABASE MOUNT
Fri Jan 7 10:13:14 2011
Setting recovery target incarnation to 2
Fri Jan 7 10:13:14 2011
Successful mount of redo thread 1, with mount id 3947812854
Fri Jan 7 10:13:14 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri Jan 7 10:13:15 2011
ALTER DATABASE OPEN
Fri Jan 7 10:13:15 2011
Beginning crash recovery of 1 threads
parallel recovery started with 8 processes
Fri Jan 7 10:13:15 2011
Started redo scan
Fri Jan 7 10:13:15 2011
Completed redo scan
0 redo blocks read, 0 data blocks need recovery
Fri Jan 7 10:13:15 2011
Started redo application at
Thread 1: logseq 16761, block 30591, scn 30945234899
Fri Jan 7 10:13:15 2011
Recovery of Online Redo Log: Thread 1 Group 2 Seq 16761 Reading mem 0
Mem# 0: /erp/u01/medh/db/apps_st/data/log02b.rdo
Mem# 1: /erp/u01/medh/db/apps_st/data/log02a.rdo
Fri Jan 7 10:13:15 2011
Completed redo application
Fri Jan 7 10:13:15 2011
Completed crash recovery at
Thread 1: logseq 16761, block 30591, scn 30945254900
0 data blocks read, 0 data blocks written, 0 redo blocks read
Fri Jan 7 10:13:15 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=34, OS id=14889
Fri Jan 7 10:13:15 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=15, OS id=14921
Fri Jan 7 10:13:15 2011
Thread 1 advanced to log sequence 16762
Thread 1 opened at log sequence 16762
Current log# 3 seq# 16762 mem# 0: /erp/u01/medh/db/apps_st/data/log03b.rdo
Current log# 3 seq# 16762 mem# 1: /erp/u01/medh/db/apps_st/data/log03a.rdo
Successful open of redo thread 1
Fri Jan 7 10:13:15 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Jan 7 10:13:15 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Fri Jan 7 10:13:15 2011
ARC1: Becoming the heartbeat ARCH
Fri Jan 7 10:13:15 2011
SMON: enabling cache recovery
Fri Jan 7 10:13:16 2011
Successfully onlined Undo Tablespace 1.
Fri Jan 7 10:13:16 2011
SMON: enabling tx recovery
Fri Jan 7 10:13:16 2011
Database Characterset is AR8MSWIN1256
Fri Jan 7 10:13:16 2011
Incremental checkpoint up to RBA [0x417a.3.0], current log tail at RBA [0x417a.87.0]
Fri Jan 7 10:13:16 2011
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=36, OS id=15146
Fri Jan 7 10:13:19 2011
Completed: ALTER DATABASE OPEN -
ORACLE DATABASE의 AUTOMATIC STARTUP/SHUTDOWN
제품 : ORACLE SERVER
작성날짜 : 1995-11-21
오라클 database의 AUTOMATIC STARTUP/SHUTDOWN
============================================
시스템이 startup 하면서 오라클도 함께 startup하거나 시스템을 shutdown
할 때 오라클도 같이 shutdown 하는 것이 가능하다. 그 방법은 OS마다 차이가
있는데 여기서는 UNIX 에 기반한 여러 플랫폼에 대해서 알아보기로 한다.
본 내용에서 가장 많이 사용되는 화일은 다음과 같다.
$ORACLE_HOME/bin/dbstart
$ORACLE_HOME/bin/dbshut
/etc/oratab 또는 /var/opt/oracle/oratab
dbstart 와 dbshut 은 오라클을 startup/shutdown 시키는 스크립트인데
이것은 automatic startup/shutdown 시에만 사용하도록 하고 평상 시의
경우에는 사용하지 않도록 한다.
oratab 화일은 일반 텍스트 화일로서 시스템에 설치된 오라클 인스턴스에
대한 정보를 가지고 있는데 보통 3개의 필드로 이루어져 있으며 첫번재
필드는 ORACLE_SID, 두번째 필드는 ORACLE_HOME, 세번째 필드는 Y 또는 N
으로 구성되어 있다. 해당 인스턴스를 autostartup 시키려면 꼭 Y로
세팅되어 있어야 한다.
SYSTEM V
System V 에 기반한 시스템은 /etc/rc<n>.d 디렉토리에 초기화 스크립트를
가지고 있다. 여기서 <n> 은 해당 스크립트의 run-level 을 의미한다.
일반적으로 run-level 0은 power shutdown mode 이고 run-level 2는 multi-user
mode 이다. 각각의 디렉토리에 들어있는 초기화 스크립트는 다음과 같은 형태의
이름을 갖고 있다.
K{two-digit number][descriptive filename]
예를 들면 S75cron, K30tcp 등이 있을 수 있다.
S로 시작되는 스크립트는 startup 시에 실행되는 것이고 K 로 시작하는 것은
shutdown 시에 실행된다.
two-digit number가 의미하는 것은 스크립트가 실행되는 순서인데 숫자가 작은
것부터 먼저 실행된다. 따라서 오라클 스크립트는 보통 다음과 같은 이름을 갖게 된다.
S99oracle, K01oracle
이와 같이 설정하면 시스템이 startup 될 때 모든 초기화가 끝난 후 마지막으로
오라클이 startup 되며 시스템을 shutdown 할 때에는 오라클을 가장 먼저 shutdown
하게 된다.
BSD UNIX
BSD 에 기반한 시스템은 시스템이 startup 될 때 초기화 화일로
/etc/rc*(예를 들면, /etc/rc, /etc/rc.local) 를 사용한다.
시스템을 shutdown 할 때에는 보통은 /etc/shutdown 만 실행하게 되므로
특별히 실행되는 스크립트가 없지만 /etc/rc.shutdown 이 실행되는
플랫폼도 있다.
이제 각 플랫폼별로 자세히 알아보기로 한다.
주의 : <oracle_owner> 는 oracle owner id 로 대체
<$ORACLE_HOME> 은 oracle home directory 명으로 대체
(1)SunOS 4.1.3
SunOS 4.1.3 에서는 /etc/rc.local 을 startup 스크립트로 사용한다. 즉
시스템이 startup 되면서 /etc/rc.local 이 실행된다. 따라서 이 화일의 끝에
다음과 같은 라인을 추가하면 된다.
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
예를 들어 oracle owner 가 oracle7 이고 $ORACLE_HOME 이 /home/oracle
이라면 다음과 같이 해주면 된다.
su oracle7 -c /home/oracle/bin/dbstart
여기서 /home/oracle 대신에 $ORACLE_HOME 과 같은 환경변수를 이용하여
세팅하면 안된다.
SunOS 에서는 시스템이 shutdown 될 때 실행되는 스크립트는 따로 없다.
따라서 dbshut 을 실행시키는 방법은 다음과 같은 스크립트를 만들어서
시스템을 shutdown 시킬 때 /etc/shutdown 을 실행시키지 말고 대신
이것을 실행시켜야 한다.
#!/bin/csh
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
/etc/shutdown $*
만약 오라클을 shutdown 하지 않고 시스템을 shutdown 하면 다음에
오라클을 startup 하려고 할 때 startup이 되지 않는다. 이 경우에는
$ORACLE_HOME/dbs/sgadef<SID>.dbf 화일을 지우고 startup 시키면 된다.
(2)OSF/1(DIGITAL UNIX)
/etc/inittab : 초기화 과정을 콘트롤
/sbin/rc3 : run-level 3 에서 사용되는 script
/sbin/rc0 : run-level 0 에서 사용되는 script
/sbin/rc3.d/S99oracle : /sbin/init.d/oracle 로 link
/sbin/rc0.d/K01oracle : /sbin/init.d/oracle 로 link
/etc/initab 화일에는 초기화 과정에 대한 정보가 들어 있다.
예를 들면 다음과 같다.
s3:3:wait:/sbin/rc3 < /dev/console > /dev/console 2>&1
이렇게 설정하면 run-level 3 일 경우 /sbin/rc3 스크립트가 실행된다.
/sbin/rc3 은 /sbin/rc3.d 디렉토리에 들어있는 스크립트를 실행한다. 만약
스크립트 이름이 K 로 시작하면 이것은 stop 파라미터를 갖고 실행되어서 이
스크립트에 지정된 프로세스를 정지시킨다. 한편, 스크립트가 S 로 시작하면
/sbin/rc3 는 이 스크립트에 startup 파라미터를 부여하고 여기서 지정된
프로세스를 실행시킨다. 따라서 /sbin/rc3.d/S99oracle 을 사용하여
dbstart를 실행한다.
shutdown 과정도 거의 비슷하다. /etc/inittab 에 다음과 같은 라인을 추가
한다.
s0:0:wait:/sbin/rc0 off < /dev/console > /dev/console 2>&1
이것은 /sbin/rc0 를 실행시키는데 /sbin/rc0 는 /sbin/rc0.d 디렉토리에
들어있는 스크립트를 실행시킨다. 스크립트의 이름이 S 로 시작하면 run
time parameter 로 start 를 사용하게 되고 K 로 시작하면 stop 을
사용한다.
따라서 /sbin/rc0.d/K01oracle 스크립트는 stop 파라미터를 갖고
실행되며 이 스크립트는 $ORACLE_HOME/bin/dbshut 스크립트를 실행시켜서
오라클을 shutdown 시킨다.
/sbin/rc3.d/S99oracle과 /sbin/rc0.d/K01oracle은 모두 /sbin/init.d/oracle
에 대한 symbolic link 이다. /sbin/init.d/oracle 에 대한 symbolic link 는
이들 외에 더 있을 수 있다.
(3)Solaris 2.3 & SCO UNIX
/etc/inittab : 초기화 과정을 콘트롤
/etc/rc2 : run-level 2 에서 사용되는 스크립트
/etc/rc0 : run-level 0 에서 사용되는 스크립트
/etc/rc2.d/S99dbstart : /etc/init.d/dbstart 에 대한 link
/etc/rc0.d/K01dbshut : /etc/init.d/dbshut 에 대한 link
/var/opt/oracle/oratab
Solaris 의 경우는 OSF/1 과 매우 유사하다. 차이점이라고 한다면 /sbin
디렉토리 대신에 /etc 디렉토리에 필요한 스크립트가 들어있다는 것이다.
rc0.d, rc2.d 같은 디렉토리는 실제로 /etc 디렉토리에 위치하고 있으며
rc0, rc2 와 같은 스크립트는 /etc/init.d 에 존재하는 같은 이름의 스크립트에
대한 symbolic link이다.
/etc/init.d/dbstart 와 /etc/init.d/dbshut 스크립트의 내용은 각각 다음과
같이 한줄로 구성되어 있다.
su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
Solaris 에서는 start, stop 같은 파라미터는 /etc/init.d/dbstart,
/etc/init.d/dbshut 에서는 무시된다.
/etc/init.d/dbstart, /etc/init.d/dbshut 화일은 owner가 oracle owner id
이여야 한다.
/etc/init.d/README 를 읽어보면 좀 더 자세한 내용이 설명되어 있으니 참조하기
바란다.
(4)AIX
/etc/inittab : 시스템 초기화 화일
/etc/rc : 시스템 초기화 스크립트
/etc/mkitab : /etc/inittab 을 수정하는 유틸리티
/etc/shutdown : 시스템 shutdown 스크립트
AIX 에서는 오라클 autostartup 방법은 여러가지가 가능하지만 shutdown 은
한가지만 가능하다. 우선 autostartup 은 다음과 같은 방법 가운데 하나를
사용하면 된다.
a)/etc/mkitab 를 사용하여 /etc/inittab 에 entry 를 추가한다. 즉,
/etc/mkitab "<oracle_owner>:2:wait:/bin/su <oracle_owner> -c
<$ORACLE_HOME>/bin/dbstart > /dev/console 2>&1"
이렇게 하면 /etc/inittab 화일에 dbstart 기능이 추가된다. 이렇게 하면
시스템이 뜨면서 run-level 2일 경우 오라클이 자동으로 startup 된다.
b)다음과 같은 방법도 가능하다.
/etc/mkitab "rcoracle:2:wait:/etc/rc.oracle > /dev/console 2>&1"
그리고, root 소유의 /etc/rc.oracle 스크립트를 다음과 같이 작성한다.
su <oracle_owner> <<EOF
<$ORACLE_HOME>/bin/dbstart
EOF
c)/etc/rc 스크립트의 마지막에 다음을 추가한다.
/bin/su <oracle_owner> - c <$ORACLE_HOME>/bin/dbstart
AIX 에서 시스템 shutdown 은 /etc/shutdown 에 의한다. 시스템을 내릴 때
오라클을 shutdown 하려면 별도의 시스템 shutdown 스크립트(root 소유로)를
다음과 같이 만들어서 /etc/shutdown 을 사용하지 말고 이것을 사용해야 한다.
#!/bin/sh
/bin/su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
/etc/shutdown $*
(5)HP/UX
/etc/rc : 시스템 startup 화일
/etc/shutdown : 시스템 shutdown 실행 화일
/etc/shutdown.d : 시스템 shutdown 디렉토리
HP/UX 에서는 시스템 startup 시에 /etc/rc 가 실행된다. 따라서 다음 라인을
/etc/rc 스크립트의 마지막에 추가하면 auto startup 이 가능해진다.
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
시스템의 shutdown 은 /etc/shutdown 화일을 실행하여 수행된다. 이 프로그램은
/etc/shutdown.d 디렉토리에 들어있는 스크립트를 실행시키는데 다음과 같은
세 가지 방법 가운데 하나로 auto shutdown 을 세팅할 수 있다.
a)$ORACLE_HOME/bin/dbshut 화일을 /etc/shutdown.d 디렉토리 아래에 copy
b)/etc/shutdown.d/dbshut 을 $ORACLE_HOME/bin/dbshut 으로 symbolic link 지정
c)다음과 같은 스크립트 작성
#!/bin/sh
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
단,이 스크립트는 root의 소유이고 root에 의해서만 실행 가능해야 한다.
만약 V6 와 V7 을 동시에 사용하는 경우라면 V7 에서 제공하는 dbshut을
사용하도록 한다.Dear Alexdelarg,
First launch the "Services" applet from the Windows NT Control Panel. Double-click on the "OracleService<SID>" service and verify that "Startup Type" is set to "Automatic", "Log On As" is set to "System Account", and that the "Allow Service to Interact with Desktop" check box is disabled.
Then launch REGEDIT and check that the Value String ORA_<SID>AUTOSTART within the key My Computer\HKEYLOCAL_MACHINE\SOFTWARE\ORACLE is set to "TRUE".
If the above does not rectify your startup problem, try issuing the following command from the Command Prompt:
<ORACLE_HOME>\bin\oradim -edit -sid <SID> -startmode auto
where <ORACLE_HOME> is the full path of your Oracle8i Server software and <SID> is the Service Identifier of your database.
Hope this helps! -
Shutdown/Startup database from java
Hi,
I need to execute shutdown/ startup database commands from a java application. I have tried wrapping these in sql / sh file using Runtime.getRuntime().exec("z:\\sql\\shut.sql"), but keep getting:
java.io.IOException: CreateProcess
any ideas ?
thanks,
DaphnaHi,
I don't see why the 11g Drivers won't work for earlier releases of the DB as long as you follow the steps in the documentation. Have you tried it? -
Reg : Script for shutdown startup in oracle9i
Hi,
I need shutdown and startup sqlfiles script while taking Coldbackup in oracle9i.U need to perform a cold backup using a script? this one will create a backup from SQL*Plus connected as SYSDBA.
Rem Set SQL*Plus variables to manipulate output
set feedback off heading off verify off
set pagesize 0 linesize 200
Rem Set SQL*Plus user variables used in script
Rem Linux User variables
define dir = '/backup'
define fil = '/tmp/closed_backup_commands.sql'
prompt *** Spooling to &fil
spool &fil
select 'host cp '|| name ||' &dir' from v$datafile order by 1;
select 'host cp '|| member ||' &dir' from v$logfile order by 1;
select 'host cp '|| name ||' &dir' from v$controlfile order by 1;
select 'host cp '|| name ||' &dir' from v$tempfile order by 1;
spool off;
Rem Shutdown the database cleanly
shutdown immediate;
Rem Run the copy file commands
@&fil
Rem Start the database again
startup;
On Linux, connect to SQL*Plus as SYSDBA and run this script like this:
LINUX> sqlplus /nolog
SQL> connect system/manager as sysdba
SQL> @closed_backup.sql -
DB STARTUP 시 ORA-312, ORA-313(ONLINE REDO LOG CRASH)
제품 : ORACLE SERVER
작성날짜 : 2002-10-31
=====================================================
DB STARTUP 시 ORA-312, ORA-313(ONLINE REDO LOG CRASH)
=====================================================
PURPOSE
[ ONLINE REDO LOG가 손상되었을 때 DB에 OPERATION 이 없었던 경우는 다음과 같은 절차로 DB 을 OPEN 할 수 있다. - 확률 70% ]
Explanation & Example
1. CONTROLFILE 생성
-. 손상된 online log 는 포함시키지 않는다.
-. resetlogs option 으로 생성한다.
-. reuse option 은 생략하고 기존 controlfile 은 다른 이름으로 move 시킴.
<V7 에서 CONTROLFILE 생성하는 방법 >
sqldba> startup mount
sqldba> alter database backup controlfile to trace;
위와 같이 명령을 입력하면 ORACLE_HOME/rdbms/log 디렉토리에 trace 화일이
생긴다. 그 trace 화일에서 create controlfile 명령 부분을 남기고 삭제
한다.
(7.3 이상에서는 cd $ORACLE_HOME
cd ../../admin/SID dir/udump 에 있습니다.)
콘트롤 화일 생성 문장 예 - <cnt.sql> : GROUP 1 이 ONLINE LOG 라고 가정
CREATE CONTROLFILE DATABASE "RC722" RESETLOGS NOARCHIVELOG
MAXLOGFILES 32 ********
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 8
MAXLOGHISTORY 800
LOGFILE
GROUP 2 '/oracle/oracle/dbs/log2RC722.dbf' SIZE 5M,
GROUP 3 '/oracle/oracle/dbs/log3RC722.dbf' SIZE 5M
DATAFILE
'/oracle/oracle/dbs/systRC722.dbf',
'/oracle/oracle/dbs/rbsRC722.dbf',
'/oracle/oracle/dbs/toolRC722.dbf',
'/oracle/oracle/dbs/usrRC722.dbf',
'/oracle/oracle/dbs/tempRC722.dbf',
'/oracle/oracle/rcdata.dbf'
2.절차
$ sqldba lmode=y
SQLDBA> connect internal
SQLDBA> shutdown abort
SQLDBA> startup nomount
statement processed
SQLDBA> @cnt
SQLDBA> recover database using backup controlfile until cancel;
CANCEL (Return)
Recovery canceled
SQLDBA> alter database open resetlogs;
: 만일 정상적으로 open 되면 log file 추가
SQLDBA> alter database add logfile '?/dbs/log1ORA722.dbf' size 1M;
Reference Documents
noneYou could check if the recovery was complete by (re)creating the controlfile with the resetlogs option.
<CREATE CONTROLFILE REUSE DATABASE define_db_name RESETLOGS NOARCHIVELOG
...>Thanks for the hint. If possible, could you only check if the steps I'm going to perform are ok.
I did an "alter database backup controlfile to trace;" and then extracted the create controlfile definition part. So in essence I should run the following statements:
CREATE CONTROLFILE REUSE DATABASE "TESTDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 'C:\ORADATA\TESTDB\REDO01.LOG' SIZE 20M,
GROUP 2 'C:\ORADATA\TESTDB\REDO02.LOG' SIZE 20M,
GROUP 3 'C:\ORADATA\TESTDB\REDO03.LOG' SIZE 20M
-- STANDBY LOGFILE
DATAFILE
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF',
'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF'
CHARACTER SET EE8MSWIN1250
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\TEMP01.DBF' REUSE;Is that correct?
About the RMAN backups: Wouldn't a 'CATALOG RECOVERY AREA' populate the controlfile with backup information again (I'm not using a recovery catalog in this case)?
Thanks for the help!
Regards,
Jure -
Urgent help needed; Database shutdown issues.
Urgent help needed; Database shutdown issues.
Hi all,
I am trying to shutdown my SAP database and am facing the issues below, can someone please suggest how I can go about resolving this issue and restart the database?
SQL> shutdown immediate
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01089: immediate shutdown in progress - no operations are permitted
SQL> shutdown abort
ORA-01031: insufficient privileges
Thanks and regards,
IqbalHi,
check SAP Note 700548 - FAQ: Oracle authorizations
also check Note 834917 - Oracle Database 10g: New database role SAPCONN
regards,
kaushal -
Hi,
I have a specific problem on one notebook. It's a windows 2000 SP4. The installation log does not contain an obvious error message. But after installation, the database homepage doesn't start.
When looking in the alert file I find those ORA 7445 and ORA 472 errors. When starting up the database using sqlplus and stepping through nomount , mount, open, it seems that the database is running for a short period and then again ends up with the above errors.
Any ideas?Hi
ORA 7445 indicates that oracle has detected a core dump when attempting a particular operation. To identify a bug you need to look at the first argument after the 7445 error as this identifies the module where the exception was raised. Use this together with the stack produced to identify a bug if possible. The ORA-600/ORA-7445 Troubleshooter will help identify bugs known to core dump in the identified module. https://metalink.oracle.com/metalink/plsql/f?p=130:14:1905955764385093414::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,153788.1,1,0,1,helvetica
Also look into the Customer Introduction to ORA-7445 Errors at https://metalink.oracle.com/metalink/plsql/f?p=130:14:1905955764385093414::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,211909.1,1,0,1,helvetica
-Priya -
ORA-7445[qkarid()+872] error
Hi,
I am using Binary XML DB .
Here is the DB banner info.
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
"CORE 11.2.0.1.0 Production"
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
I am getting ORA-7445[qkarid()+872] error while executing a query
SELECT XMLCast(XMLQuery('$p/PurchaseOrder/Reference' PASSING OBJECT_VALUE AS "p"
RETURNING CONTENT)
AS VARCHAR2(30)) "Reference"
FROM purchaseorder
WHERE XMLExists('$p/PurchaseOrder[User="SBELL"]' PASSING OBJECT_VALUE AS "p") for update wait 60;
Please advise
ThanksUpdate to 11.2.0.3.0 and see if it goes away. If that is not poissble open a tar with Oracle Support
c:\xdb\examples\SXI_Generator>sqlplus SXIGEN/SXIGEN
SQL*Plus: Release 11.2.0.3.0 Production on Mon Mar 5 12:48:17 2012
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> desc PURCHASEORDER
Name Null? Type
TABLE of SYS.XMLTYPE STORAGE BINARY
SQL> SELECT XMLCast(XMLQuery('$p/PurchaseOrder/Reference' PASSING OBJECT_VALUE AS "p"
2 RETURNING CONTENT)
3 AS VARCHAR2(30)) "Reference"
4 FROM purchaseorder
5 WHERE XMLExists('$p/PurchaseOrder[User="SBELL"]' PASSING OBJECT_VALUE AS "p") for update wait 60;
Reference
SBELL-20100408134226318PDT
SBELL-20100419204001680PDT
SBELL-20100420220510663PDT
SBELL-20100422220520735PDT
SBELL-20100427173413101PDT
...Edited by: mdrake on Mar 5, 2012 12:48 PM -
Ora 600 and ora 7445 error in oracle 10g r2
hi all,
we are using Oracle 10g r2.
os is windows 2003 server,
ram is 4 gb.
front end is java .
we got a below mentioned errors.
i got the RA-00600: internal error code, arguments: [qerghFetch:inc], [], [], [], [], [], [], [],
and ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x61F04AC9] [ADDR:0xC] [UNABLE_TO_READ] []
and Error 0 in kwqmnpartition(), aborting txn errors.
for aug 3 11.42.47 we got a ora 600 error after that through front end (java) users can't able to connect the database.the not able to executed the query session disconnected error.
what is reason for theis error . how it will rectifiy.?
pls advice.Below i attached the alret log message .
Sun Aug 02 04:04:24 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 05:48:10 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 05:49:10 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 07:38:49 2009
Thread 1 advanced to log sequence 1732
Current log# 3 seq# 1732 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Sun Aug 02 07:44:14 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 07:45:14 2009
Error 0 in kwqmnpartition(), aborting txn
Sun Aug 02 22:00:26 2009
Thread 1 advanced to log sequence 1733
Current log# 1 seq# 1733 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG
Mon Aug 03 07:08:15 2009
Thread 1 advanced to log sequence 1734
Current log# 2 seq# 1734 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
Mon Aug 03 09:28:23 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 09:30:27 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 11:42:47 2009
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6012.trc:
ORA-00600: internal error code, arguments: [qerghFetch:inc], [], [], [], [], [], [], []
Mon Aug 03 13:20:00 2009
Thread 1 advanced to log sequence 1735
Current log# 3 seq# 1735 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Mon Aug 03 16:07:07 2009
Errors in file e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_4756.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x61F04AC9] [ADDR:0xC] [UNABLE_TO_READ] []
Mon Aug 03 16:07:11 2009
Process m000 died, see its trace file
Mon Aug 03 16:07:11 2009
ksvcreate: Process(m000) creation failed
Mon Aug 03 16:08:37 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 16:10:40 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:25:05 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:27:11 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:32:19 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 17:33:24 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 18:52:08 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 18:54:09 2009
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 19:05:33 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Mon Aug 03 19:09:02 2009
Errors in file e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_5132.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C34126B] [ADDR:0x0] [UNABLE_TO_WRITE] []
Mon Aug 03 19:10:27 2009
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txn
Error 0 in kwqmnpartition(), aborting txnHi reshumakur
As this is your PRODUCTION system THEN_ The best help to offer in case of ORA-600, and ORA-7445 is to open SR with metalink. Submit with the SR the following
1- Alert log
2- Trace files (in ur case e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6012.trc: and e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_4756.trc:)
3- Describe what was happening when you had these errors.
Try to avoid free help when you have ORA-600 and ORA-07445. This errors could be becuase of BUGS. Oracle Support will know this from the call stack in the trace file.
Then Do your best to patch 10.2.0.4 and the latest CPU patch.
Good Luck -
Hi,
My database takes quite a lot of time in shutting down, when I do normal shutdown.
Pls help
vipHi Aman,
F. Munoz Alvarez wrote:
This is because Oracle terminates all sessions and does a rollback on all.Francisco,
What does it mean by rollback here? So if I would kick in really big transaction and Oracle is shutting down, it will be rolling back my transcton? I don't think so. > My transaction info would be cleared immediately. Is there any way that I can see this happening ?
Aman....Take a look in the Oracle Docs:
- http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/start.htm#sthref589
Immediate database shutdown proceeds with the following conditions:
- No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
- Any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)
- Oracle Database does not wait for users currently connected to the database to disconnect. The database implicitly rolls back active transactions and disconnects all connected users.
The next startup of the database will not require any instance recovery procedures.
Transactional database shutdown proceeds with the following conditions:
- No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
- After all transactions have completed, any client still connected to the instance is disconnected.
- At this point, the instance shuts down just as it would when a SHUTDOWN IMMEDIATE statement is submitted.
The next startup of the database will not require any instance recovery procedures.
A transactional shutdown prevents clients from losing work, and at the same time, does not require all users to log off.
Cheers,
Francisco Munoz Alvarez
http://www.oraclenz.com
Sorry by the delay to answer, I'm having some issues with my internet connection :( -
Error on starting up database...ORA-01589: must use RESETLOGS
I just installed Oracle9i and when trying to start up the db I get the following:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\>sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Wed Jun 11 11:02:50 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect / as sysdba
Connected.
SQL> startup
ORACLE instance started.
Total System Global Area 135338868 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL>
Any ideas what I should do?
Thanks.Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the file consistent. The named file was not closed cleanly when it was last opened by the database. The most likely cause of this message is forgetting to restore the file from a backup before doing incomplete recovery.
Action: The file must be recovered to a time when it was not being updated. Either apply more redo logs until the file is consistent or restore the file from an older backup and repeat recovery. -
Ora 7445 error happend on 11g r1
I found many ora 07445 error on my database:
Details ID Description Data Dumped Active Status Timestamp [Sorted in descending order]
[Select to show information] Show
111129 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 4:42:27 PM CST
[Select to show information] Show
111369 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 4:38:05 PM CST
[Select to show information] Show
111330 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 4:37:58 PM CST
[Select to show information] Show
111081 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 4:26:51 PM CST
[Select to show information] Show
111025 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 4:19:36 PM CST
[Select to show information] Show
111282 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 3:37:35 PM CST
[Select to show information] Show
111393 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 2:50:21 PM CST
[Select to show information] Show
111497 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 2:02:42 PM CST
[Select to show information] Show
111217 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 1:15:24 PM CST
[Select to show information] Show
111113 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 12:28:06 PM CST
[Select to show information] Show
111281 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 11:41:20 AM CST
[Select to show information] Show
111593 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 11:08:03 AM CST
[Select to show information] Show
111569 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 10:57:24 AM CST
[Select to show information] Show
111329 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 10:50:01 AM CST
[Select to show information] Show
111121 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 10:36:48 AM CST
[Select to show information] Show
110777 ORA 7445 [ttci2u()+3660] [ttci2u()+3660] [SIGSEGV] [ADDR:0x0] [PC:0x105698A0C] [Address not mapped to object] [] [] [] Yes Yes Ready February 2, 2010 3:52:08 AM CST
How to resolve?
Edited by: user3799828 on Feb 2, 2010 1:14 AM
Edited by: user3799828 on Feb 2, 2010 1:15 AMLookup MOS document 310737.1 for this. You are better off raising an SR with Oracle support as others have indicated.
-
Oracle database shutdown unexpectedly
Hi,
My oracle database shutdown unexpectedly several times this week and the alert log shows the below errors
database shutdown unexpectedly with the folloing messge in alert
Fatal NI connect error 12560, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Time: 29-JUL-2012 06:24:48
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (3948_1704)
Sun Jul 29 06:26:54 2012
Please any help ???
Thanks943086 wrote:
Thanks
both links descriping the same oracle metalink docs, witch its not applicable
thanksyou are not help us to help you , both metalink that i have been posted talking about windows environment , OTN thread talking about windows environment and seems to me in all links that i have been posted its same alertlog error . -
We have a Oracle9i database on RHEL ver.4.
After installed new storage, our disk partition was broken and database was shutdown.
Question 1.
When File system was broken cause of media failure, we want know how startup database by force even though we lost our data.
Purpose of Our system is temporarily to manage data.
We want startup database emergency at either event that tablespace and data files exist or not.
Question 2.
In above situation, we acknowledge status of our database in nomount but control file was broken cause of media failure.
So we don't startup our database immediately.
I wonder if we create new control file, whether we startup database or not.
Please, be hurry.
We are in very emergency situation.
Thanks.
Message was edited by:
user636366Hi,
Database shutdown was unexpected.
It was not clean shutdown.
We had not control file backup.(Actually, We had not any backup; COLD & HOT.)
So you don't have any backups in hand at the moment?Well prayers may help then.I shall suggest that you contact support for the issue.Its a prod db and you don't have a backup,I wont suggest you play around with it for any trial-see methodology.Let support take over the charge.
Aman....
Maybe you are looking for
-
EDUCATION: Updated to new iPad iOS - can no longer sync with computer
I recently updated all of my class iPads (36) to the new iOS. Now I can no longer sync them with the ONLY computer they have ever been sync'd with. I get a message that the iPad is "now associated" with another device (which it is NOT). I have neve
-
Swipe no longer works in Firefox since upgrading to Lion.
I can no longer use the swipe gesture to move between pages on Firefox since upgrading to Lion. I have tried it on both the Magic trackpad and the magic mouse. Anyone else haviong this issue?
-
Photoshop Elements 11 editor no longer working
All of a sudden, when I try to open Photoshop Elements 11 Editor either through Aperture 3, from the Organizer or from the dock, just get the spinning color wheel. Have to force close. Editor used to work fine. Organizer still works fine. Using Apple
-
Can't edit photos in my MobileMe gallery in iPhoto '11
Hi, I have all my photos in my MobileMe gallery. Everything sync very well with iPhoto '11. But I'm surprised by the fact that I can't edit those photos. It keeps saying that the element I selected can't be modified in iPhoto '11. Is this because I d
-
Hi Experts, I'm new @ QM & was wanting to understand the reasons/needs for a business to carry out QM inpection during Shipment?? Most of the goods produced for shipments are inspected either during production (in-process) or @ GR. That being the cas