OS 명령으로 DATAFILE을 삭제한 경우:ORA-1157, ORA-1110

제품 : ORACLE SERVER
작성날짜 : 2004-03-08
OS 명령으로 DATAFILE을 삭제한 경우 : ORA-1157, ORA-1110
======================================================
[주의] 다음의 경우는 system tablespace에 대해서 적용되지 않는다.
DATABASE RECOVERY에 앞서 ORACLE INSTANCE(즉, ORACLE RDBMS)의 STARTUP
단계를 우선 살펴보기로 하자.
첫번째 단계로 INSTANCE를 START시키며, 여기서는 initORACLE_SID.ora
화일의 파라미터를 참조하여 SGA(SYSTEM GLOBAL AREA)를 할당하고
백그라운드 프로세스를 START 시킨다.
두번째 단계로 DATABASE의 MOUNT이며 파라미터 화일에 명시된 CONTROL
FILE을 오픈한다. CONTROL FILE로부터 DATABASE NAME과 REDO LOG FILE의
이름을 읽는다.
세번째 단계로 CONTROL FILE 내의 정보를 이용하여 모든 데이타 화일을
오픈한다.
SVRMGR> CONNECT INTERNAL;
Connected.
SVRMGR> STARTUP;
ORACLE instance started.
Database mounted.
Database opened.
Total System Global Area 1913196 bytes
Fixed Size 27764 bytes
Variable Size 1787128 bytes
Database Buffers 65536 bytes
Redo Buffers 32768 bytes
RDBMS의 STARTUP 시 문제의 데이타 화일이 CONTROL FILE 정보에서는 존재하지만,
실제로 O/S 상에서는 존재하지 않으므로 DATABASE OPEN 단계에서 삭제된 데이타
화일을 OPEN할 수 없다. 따라서 다음과 같은 데이타 화일 오픈에 관련된 에러가
발생된다 :
SVRMGR> STARTUP;
ORACLE instance started
Database mounted
ORA-01157 : cannot identify data file 11 - file not found
ORA-01110 : data file 11 : '/user1/oracle7/dbs/user2.dbf'
Attempting to dismount database .... Database dismounted
Attempting to shutdown instance .... ORACLE instance shut down
DATABASE OPEN 단계에서 CONTROL FILE에서는 ORA-1157 에러에서 나타난
11번 데이타 화일이 존재하는 것으로 인식하지만, 실제로 O/S 상의 데이타
화일 (ORA-1110 에러에 명시된 '/user1/oracle7/dbs/user2.dbf' 화일)이
삭제된 상태이다.
이러한 경우에는 DATABASE STARTUP 시 STARTUP MOUNT 단계까지 실행한 후,
문제의 데이타 화일을 OFFLINE시킨 다음 데이타베이스를 오픈한다.
단, 데이타베이스 오픈이 정상적으로 수행되면 문제가 발생한 데이타 화일을
포함하고 있는 TABLESPACE를 DROP하지 않을 경우에는 DATABASE STARTUP 시
항상 데이타 화일의 오픈 단계에서 에러가 발생된다.
따라서, 문제의 데이타 화일의 OFFLINE과 TABLESPACE의 DROP 전에 반드시 해당
TABLESPACE를 사용하고 있는 USER의 데이타 백업을 수행해야 한다.
데이타 화일의 OFFLINE과 관련된 명령은 다음과 같다.
먼저 SVRMGR을 Line Mode로 기동시킨다.
$ svrmgrl
SVRMGR> CONNECT INTERNAL;
SVRMGR> STARTUP MOUNT;
ORACLE instance started.
Database mounted.
SVRMGR> ALTER DATABASE DATAFILE '/user1/oracle7/dbs/user2.dbf'
OFFLINE DROP;
Statement processed.
SVRMGR> ALTER DATABASE OPEN;
Statement processed.
SVRMGR> DROP TABLESPACE tablespace_name INCLUDING CONTENTS;
Statement processed.
(이와 같이 offline drop된 datafile을 포함하는 tablespace는 drop하여야 한다.
이 tablespace에 다른 datafile도 포함되어 있다면 export를 받아낸 후
tablespace를 drop하고 재생성 후 import하도록 한다.)
정상적으로 DATABASE가 Open된 후 CONTROL FILE로부터의 데이타베이스
정보를 갖는 DATA DICTIONARY TABLE인 V$DATAFILE(SYS USER에서 액세스
가능)의 내용과 데이타베이스 화일에 관한 정보를 가지고 있는 DATA
DICTIONARY VIEW인 DBA_DATA_FILES(SYSTEM USER)을 조회하면 아래와 같은
내용을 확인할 수 있다 :
(1) SQL> SELECT * FROM V$DATAFILE ;
FILE# STATUS NAME
9 ONLINE /user1/oracle7/dbs/tools.dbf
10 ONLINE /user1/oracle7/dbs/user1.dbf
11 RECOVER /user1/oracle7/dbs/user2.dbf
(2) SQL> SELECT * FROM DBA_DATA_FILES ;
FILE_NAME FILE_ID TABLESPACE_NAME STATUS
/user1/oracle7/dbs/tools.dbf 9 TOOLS AVAILABLE
/user1/oracle7/dbs/user1.dbf 10 TEST AVAILABLE
/user1/oracle7/dbs/user2.dbf 11 TEST AVAILABLE

Similar Messages

Errors-Ora-01157,ORA-01110,ORA-01033

HI all,
i am unable to login into database,i will explain clearly what has happened,please help me out...my /home directory was 100%,so i was unable to login,what i have did is i have not deleted
archive files but i have moved to other directory /ora_bkp,then i was able to login,today i have rebboted the system and later i have started database,started listener,but when i try to login
through sql*plus or toad i am getting this error.....ORA-01033 (ORACLE INITIALIZATION OR SHUTDOWN IN PROGRESS),and when i have tried to check from sql promt ....i am getting this
error....ORA-01157(CANNOT IDENTIFY/LOCK DATAFILE 6 -SEE DBWR TRACE FILE),& ORA-01110(DATA FILE 6: '/SAPDATA/SPO'...
HOW SHOULD I RECTIFY MY PROBLEM...AS I AM VERY NEW IAM TRYING TO EXPLAIN CLEARLY ...PLEASE HELP ME IN SOLVING THIS ISSUE....I HAVE EVEN TRIED ALTER DATABASE OPEN...I AM GETTING ERRORS OF ORA-01157,ORA-01110....WHAT IS MY PROBLEM HOW SHOULD I RECTIFY IT..PLEASE SORT THIS....
THANKS,
MIKE

Well, did you check f.i. your alert.log and other dumps?
They will be on your server in the bdump, udump, cdump directories:
Where to Find Files for Analyzing Errors
Oracle records information about important events that occur in your Oracle RAC environment in trace files. The trace files for Oracle RAC are the same as those in single-instance Oracle databases. As a best practice, monitor and back up trace files regularly for all instances to preserve their content for future troubleshooting.
Information about ORA-600 errors appear in the alert_SID.log file for each instance where SID is the instance identifier. For troubleshooting, you may need to also provide files from the following bdump locations:
* $ORACLE_HOME/admin/db_name/bdump on UNIX-based systems
* %ORACLE_HOME%\admin\db_name\bdump on Windows-based systems
Some files may also be in the udump directory.
In addition, the directory cdmp_timestamp contains in-memory traces of Oracle RAC instance failure information. This directory is located in ORACLE_HOME/admin/db_name/bdump/cdmp_timestamp, where timestamp is the time at which the error occurred.
Trace dump files are stored under the cdmp directory. Oracle creates these files for each process that is connected to the instance. The naming convention for the trace dump files is same as for trace files, but with .trw as the file extension.
(http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/appsupport.htm#RACAD512)

When trying to create new DB ORA-01109 ORA-01092

Hi all,
When I try to create a new database on a two-node clustered machine using dbca and the "General Purpose" template, it returns ORA-01109 ORA-01092 errors.
Following is what I did:
1. Installed Oracle 10 Release 2 on the two Oracle Enterprise Linux 4.5 nodes
2. Installed patch set 3 (upgrade from 10.2.0.1 to 10.2.0.4)
3. Installed Oracle clusterware on both nodes
4. Installed ASM instance
5. when I used the dbca to create a new db, it returns DB ORA-01109 ORA-01092
I guess, the reason is that the seed of the "General Purpose" template was not upgraded by the patch set. If this is the case, my questions are:
*(1) Why the patchset didn't upgrade the template seeds? Is it a bug?*
*(2) How to upgrade the template seeds?*
Oracle 10g R2 (10.2.0.4) on Oracle EL 4.5
Following is a copy of a few last lines in the log generated by the dbca:
[Thread-158] [10:22:57:99] [CloneDBCreationStep.executeImpl:352] createCtl=Create
controlfile reuse set databa se "rac"
MAXINSTANCES 32
MAXLOGHISTORY 1
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
Datafile
'+DG1/rac/datafile/system.277.705320457',
'+DG1/rac/datafile/undotbs1.279.705320475',
'+DG1/rac/datafile/sysaux.278.705320469',
'+DG1/rac/datafile/users.280.705320477',
[Thread-158] [10:22:57:100] [CloneDBCreationStep.executeImpl:359] crtCtl=Create
controlfile reuse set database "rac"
MAXINSTANCES 32
MAXLOGHISTORY 1
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
Datafile
'+DG1/rac/datafile/system.277.705320457',
'+DG1/rac/datafile/undotbs1.279.705320475',
'+DG1/rac/datafile/sysaux.278.705320469',
'+DG1/rac/datafile/users.280.705320477'
[Thread-158] [CloneDBCreationStep.executeImpl:374] Length of OriginalRedoLogsGrNames=2
[Thread-158][CloneDBCreationStep.executeImpl:382] 0th redoLogText = GROUP 1 SIZE 51200K
[Thread-158][CloneDBCreationStep.executeImpl:382] 1th redoLogText = GROUP 2 SIZE 51200K
[Thread-158][CloneDBCreationStep.executeImpl:403] createCTLSql=Create controlfile reuse
set da tabase "rac"
MAXINSTANCES 32
MAXLOGHISTORY 1
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
Datafile
'+DG1/rac/datafile/system.277.705320457',
'+DG1/rac/datafile/undotbs1.279.705320475',
'+DG1/rac/datafile/sysaux.278.705320469',
'+DG1/rac/datafile/users.280.705320477'
LOGFILE GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K RESETLOGS;
[Thread-158] [10:23:22:541] [CloneDBCreationStep.executeImpl:415] calling zerodbid
[Thread-158] [10:23:41:517] [CloneDBCreationStep.executeImpl:425] Shutdown database
[Thread-158] [10:23:41:717] [CloneDBCreationStep.executeImpl:447] Startup ......nomount......
[Thread-158] [10:23:57:523] [CloneDBCreationStep.executeImpl:455] deleting dummy control file from v$controlfi le: +DG1/rac/controlfile/current.281.705320591
[Thread-158] [10:24:1:293] [CloneDBCreationStep.executeImpl:455] deleting dummy control file from v$controlfil e: +DG2/rac/controlfile/current.265.705320595
[Thread-158] [10:24:24:628] [CloneDBCreationStep.executeImpl:466] Enabling restricted session.
[Thread-158] [10:24:29:60] [CloneDBCreationStep.executeImpl:468] alter database "rac" open resetlogs;
[Thread-156] [10:24:58:683] [BasicStep.handleNonIgnorableError:430] oracle.sysman.assistants.util.UIMessageHan dler@1b8099a:messageHandler
[Thread-156] [10:24:58:703] [BasicStep.handleNonIgnorableError:431] ORA-01092: ORACLE instance terminated. Dis connection forced

alertlog tail contents:
SMON: enabling cache recovery
Fri Dec 11 10:24:57 2009
Errors in file /u01/app/oracle/admin/rac/udump/rac1_ora_5482.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Fri Dec 11 10:24:57 2009
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 5482
ORA-1092 signalled during: alter database "rac" open resetlogs...

SQL*LOADER ERROR 비교 (ORA-2359, ORA-1401)

제품 : ORACLE SERVER
작성날짜 : 2002-04-09
SQL*LOADER ERROR 비교 (ORA-2359, ORA-1401)
==========================================
PURPOSE
SQL*LOADER 를 사용하는 경우 ORA-2359 ERROR가 나는 경우와
ORA-1401 ERROR가 나는 경우를 비교한다.
Examples
table 의 desc가 다음과 같다고 가정하자.
SQL> create table test5(a varchar2(1000));
이 경우 delimiter 가 comma 인지 position 으로 구분되는지에 따라 error
message가 달리 나타난다.
1) ORA-2359 : field in datafile exceeded maximum specified length
load data
infile test.dat
replace
into table test5
fields terminated by ','
(a char) 로 실행 시 발생.
---> a char(1000) 으로 하면 error 해결이 가능하다.
2) ORA-1401: inserted value too large for column
load data
infile test.dat
replace
into table test5
fields terminated by ','
(a position(1:2000) char)
---> 이 경우 a position (1:1000) char 로 하면 해결 가능하다 .
* 참고로 + , - 기호와 comma 를 load 하기 위해서는 decimal external을
사용한다. (a position decimal external (10))
Reference Documents
---------------------

You hit Bug 3531336
Run the script catcio.sql from $ORACLE_HOME/rdbms/admin directory.
Run this in sys schema.
And then load the data with sqlloader.

DataGuard Continuing to Fail - ORA-16766, ORA-01237 - OPSCODE 17.4

DataGuard Broker failing every few hours ... have to stop and restart. ORA-16766, ORA-01237. I cannot find any information on the failure apply recovery marker (opscode 17.4).
The thought would be from the errors that the volume is out of space, we are running NETAPP and the volumes do auto expand but when I looked the volume it was only at 44% full at 1600 yesterday when I restarted and today I it is at 28%.
These are BIGFILE tablespace. I have restarted multiple times and keep getting the same errors daily and I just end up restarting and everything works again w/o intervention.
I don't want to daily have to check dataguard. If I don't run dg and just run "recover standby database until cancel auto" ... it just keeps going w/o issue, any ideas on the problem?
Please advise:
OS: Solaris 5.10
RDBMS:Oracle 11.2.0.2 64 bit
OMF
BIGFILE Tablespaces
VLDB - Standby DG Database
Created via RMAN Duplicate Database
Dataguard Alert shows the original startup information, does some health check ... becomes quite for a few hours and then I start seeing the Redo Apply is stopped.
2011-09-28 18:45:20.824 00000000 24342 Operation HEALTH_CHECK canceled during phase 1, error = ORA-16766
2011-09-28 18:46:20.929 DMON: HEALTH CHECK ERROR: ORA-16766: Redo Apply is stopped
Alert Log showing 1237 on the extend but volume is not out of space ... bigfile tablespace. I cannot find any information on the failure apply recovery marker (opscode 17.4):
Errors in file /u02/d002/oracle/bdump/diag/rdbms/DBUNIQNAME/DBNAME/trace/DBNAME_pr00_6331.trc:
ORA-01237: cannot extend datafile 670
ORA-01110: data file 670: '/u07/d101/oracle/DBUNIQNAME/datafile/o1_mf_ftk_31_c_784ql3gh_.dbf'
Managed Standby Recovery not using Real Time Apply
Wed Sep 28 18:43:57 2011
Recovery interrupted!
Wed Sep 28 18:44:29 2011
Archived Log entry 2805 added for thread 1 sequence 135638 ID 0x249d4159 dest 1:
Wed Sep 28 18:44:41 2011
Recovery stopped due to failure in applying recovery marker (opcode 17.4).
Datafiles are recovered to a consistent state at change 22941677700 but controlfile could be ahead of datafiles.
Wed Sep 28 18:44:42 2011
MRP0: Background Media Recovery process shutdown (DBNAME)
Wed Sep 28 18:46:04 2011
Trace FIle showing the same problem as the alert ...
Started Parallel Media Recovery
*** 2011-09-28 16:14:52.074 4265 krsh.c
Managed Standby Recovery starting Real Time Apply
*** 2011-09-28 18:43:08.759 4265 krsh.c
MRP0: Background Media Recovery terminated with error 1237
ORA-01237: cannot extend datafile 670
ORA-01110: data file 670: '/u07/d101/oracle/DBUNIQUNAME/datafile/o1_mf_ftk_31_c_784ql3gh_.dbf'
*** 2011-09-28 18:43:08.779 4265 krsh.c
Managed Standby Recovery not using Real Time Apply----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 54581570Kb in 8888.95s => 6.00 Mb/sec
Total redo bytes: 54636866Kb Longest record: 81Kb, moves: 49633/139704932 moved: 130Mb (0%)
Longest LWN: 118127Kb, reads: 45176
Last redo scn: 0x0005.576e3884 (22941677700)
Change vector header moves = 18603031/273716057 (6%)
*** 2011-09-28 18:43:08.816
Media Recovery drop redo thread 1
*** 2011-09-28 18:43:56.660
Completed Media Recovery
*** 2011-09-28 18:44:00.869
Checking to start in-flux buffer recovery from SCN 5.1465762230 to SCN (non-inclusive) 5.1466841220
Influx recovery found in-flux buffers
*** 2011-09-28 18:44:00.874
Influx Media Recovery add redo thread 1
*** 2011-09-28 18:44:36.493
Resized overflow buffer to 52335K (for 52335K LWN)
*** 2011-09-28 18:44:38.887
Resized overflow buffer to 63165K (for 63165K LWN)
*** 2011-09-28 18:44:41.686
Managed Recovery: Not Active posted.

It appears to be a problem that occurs every time an OMF file wants to extend that it kills the dataguard process irrelvant of what volume the file is on.

ORA-00283:,ORA-19909:,ORA-19909:

Hi,
I am doing recovery with hot backup (whiout using RMAN) in my stand by database dupdb but getting below error.
SQL> select name, open_mode from v$database;
NAME      OPEN_MODE
DUPDB     MOUNTED
SQL> set logsource 'D:\app1\Archivelocation';
SQL> recover database using backup controlfile until cancel;
ORA-00283: recovery session canceled due to errors
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: 'D:\APP1\APP\HIMANSHU\ORADATA\DUPDB\SYSTEM01.DBF'
Please let me know What wrong I am doing here.
Thanks,
Michel

HI, welcome to OTN form,
fb767351-a660-4b18-9a9f-73bc141f6a0c wrote:
Hi,
I am doing recovery with hot backup (whiout using RMAN) in my stand by database dupdb but getting below error.
SQL> select name, open_mode from v$database;
NAME      OPEN_MODE
DUPDB     MOUNTED
SQL> set logsource 'D:\app1\Archivelocation';
SQL> recover database using backup controlfile until cancel;
ORA-00283: recovery session canceled due to errors
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: 'D:\APP1\APP\HIMANSHU\ORADATA\DUPDB\SYSTEM01.DBF'
From Metalink: (Oracle Support)
From Metaclick
Error:     ORA-19909 (ORA-19909)
Text:     datafile %s belongs to an orphan incarnation
Cause:     Either the specified datafile was restored from a backup that was
     taken during a period of time that has already been discarded by a
     resetlogs operation, or Oracle cannot identify which database
     incarnation the file belongs to. The alert log contains more
     information.
Action:     Restore a backup of this file that belongs to either the current
     or a prior incarnation of the database. If you are using RMAN to
     restore, RMAN will automatically select a correct backup.
Thank you

ORA-01503 ORA-01115 ORA-01110 ORA-27091ORA-27067

Hi ,
I am making a copy of our production database which is on a linux server to my
testserver on windows server 2003
1. copy the datafiles from a coldbackup to my testserver
2. run the scricpt ad@sql
STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE "ADWTEST1" RESETLOGS ARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 226
LOGFILE
GROUP 1 'C:\DATABASE\REDO1\REDO01.LOG' SIZE 100M,
GROUP 2 'C:\DATABASE\REDO2\REDO02.LOG' SIZE 100M
-- STANDBY LOGFILE
DATAFILE
'C:\ORACLE\ORADATA\ADWTEST\ADW1SYSTEM01.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01A.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01B.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01C.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01D.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01E.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01F.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01G.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1DATA01H.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1INDEX01A.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1INDEX01B.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1INDEX01C.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1INDEX01D.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1INDEX01E.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1INDEX01F.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1INDEX01G.DBF',
'C:\ORACLE\ORADATA\ADWTEST\ADW1UNDO01.DBF',
'C:\ORACLE\ORADATA\ADWTEST\REPOSITORY1A.DBF'
CHARACTER SET WE8MSWIN1252
Than i got the following message
CREATE CONTROLFILE SET DATABASE "ADWTEST1" RESETLOGS ARCHIVELOG
FEHLER in Zeile 1:
ORA-01503: CREATE CONTROLFILE nicht erfolgreich
ORA-01115: EA-Fehler beim Lesen von Block aus Datei (Block Nr. 1)
ORA-01110: Datendatei : 'C:\ORACLE\ORADATA\ADWTEST\ADW1SYSTEM01.DBF'
ORA-27091: skgfqio: E/A kann nicht in Queue gestellt werden
ORA-27067: skgfdisp: Puffergro?e ungultig
OSD-04026: Ung+ltiger Parameter +bergeben.

Please review Oracle Metalink Document: ORA-01503 ORA-01160 ORA-01110 while creating controlfile: Doc ID: Note:265265.1
https://metalink.oracle.com/metalink/plsql/f?p=130:14:6577327622142824597::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,265265.1,1,0,1,helvetica
and
Oracle Metalink Document: ORA-01503 And (ORA-01160 ORA-01110) Or (ORA-01565 ORA-27406) Doc ID: Note:1077033.6.
https://metalink.oracle.com/metalink/plsql/f?p=130:14:6577327622142824597::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,1077033.6,1,0,1,helvetica
Please also mention your database version (4 digits).
Adith

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
none

You 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

ORA-00376,ORA-01110 의 조치 방법

제품 : ORACLE SERVER
작성날짜 : 2003-01-15
ORA-00376,ORA-01110 의 조치 방법
================================
Purpose
ORA-00376: file 29 cannot be read at this time
ORA-01110: data file 29: '/db/GICORP_4/axix01.dbf'
Problem Description
datafile의 size가 os에서 허용하는 filesize를 초과해서
발생하는 에러입니다.
Solution Description:
unix의 ulimit filesize를 확인해 보시기 바랍니다.
그리고 datafile size 보다 크도록 수정해 주어야 합니다.
1. unix ulimit filesize를 증가 시킨다
C shell인 경우
% limit filesize <number>
Bourne 이나 Korn shell 인 경우
$ ulimit -f <number>
2. archivelog mode인지 확인합니다
SVRMGR> select * from v$database;
NAME CREATED LOG_MODE CHECKPOINT ARCHIVE_CH
GICORP 05/17/00 13:44:56 ARCHIVELOG 36290290 36284249
1 row selected.
3. media recovery가 필요한 datafiles를 찾습니다
SVRMGR> select * from v$recover_file;
FILE# ONLINE ERROR CHANGE# TIME
9 OFFLINE 36287415 12/20/00 23:30:55
23 OFFLINE 36289350 12/21/00 08:40:54
28 OFFLINE 36287415 12/20/00 23:30:55
29 OFFLINE 36287415 12/20/00 23:30:55
37 OFFLINE 36287415 12/20/00 23:30:55
5 rows selected.
4. 각각의 datafile에 대해서 다음을 실행해 줍니다
SVRMGR> recover datafile '/db/GICORP_4/axix01.dbf';
Media recovery complete.
SVRMGR> alter database datafile '/db/GICORP_4/axix01.dbf' ONLINE;
Statement processed.
5. database를 restart합니다
SVRMGR> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 54578916 bytes
Fixed Size 69348 bytes
Variable Size 20783104 bytes
Database Buffers 33554432 bytes
Redo Buffers 172032 bytes
Database mounted.
Database opened.
SVRMGR>
Reference Ducumment
---------------------

Hi,
You have deleted the data files then how can you expect to query the data :). You need to recover from a valid backup to get the database back. You CAN NOT open database if current undo tablespace data file is gone
Salman

ORA-00704: 引导程序进程失败 ORA-00600: 内部错误代码,参数: [4000], [14], [], [], [], [], [],

KSTDUMP: End of in-memory trace dump
ORA-00704: 引导程序进程失败
ORA-00704: 引导程序进程失败
ORA-00600: 内部错误代码，参数: [4000], [14], [], [], [], [], [], []
数据库无法启动，启动时提示：ORA-01092: ORACLE 例程终止。强行断开连接

9.2.0.1.0 + Win 2000， 9.2.0.1 是一个极不稳定的版本，没有任何理由继续使用该版本。
allowresetlogs_corruption= TRUE
corruptedrollback_segments= SYSSMU1$, SYSSMU2$, SYSSMU3$, SYSSMU4$, SYSSMU5$, SYSSMU6$, SYSSMU7$, SYSSMU8$, SYSSMU9$, SYSSMU10$
你已经使用了非正常手段的 allowresetlogs_corruption 和 corruptedrollback_segments ，这可能导致数据字典和 segment都存在大量讹误
Sat Oct 27 13:17:43 2012
SMON: enabling cache recovery
Sat Oct 27 13:17:43 2012
Errors in file d:\oracle\admin\nmgecid\udump\nmgecid_ora_808.trc:
ORA-00600: 内部错误代码，参数: [4000], [14], [], [], [], [], [], []
Sat Oct 27 13:17:44 2012
Errors in file d:\oracle\admin\nmgecid\udump\nmgecid_ora_808.trc:
ORA-00704: 引导程序进程失败
ORA-00704: 引导程序进程失败
ORA-00600: 内部错误代码，参数: [4000], [14], [], [], [], [], [], []
Sat Oct 27 13:17:44 2012
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 808
ORA-1092 signalled during: alter database open resetlogs...
ORA-704 bootstrap fatal error + ORA-600[4000]
*** SESSION ID:(9.3) 2012-10-27 13:17:39.000
*** 2012-10-27 13:17:39.000
*** 2012-10-27 13:17:43.000
ksedmp: internal or fatal error
ORA-00600: 内部错误代码，参数: [4000], [14], [], [], [], [], [], []
Current SQL statement for this session:
select ctime, mtime, stime from obj$ where obj# = :1引发错误的对象是 OBJ$对象，可能引发该ORA-600[4000]的块，分别是 DATAFILE 1的 380块和122块：
BH (0x6C3FEAC8) file#: 1 rdba: 0x0040017c (1/380) class 1 ba: 0x6C3DC000
set: 6 dbwrid: 0 obj: 56 objn: 56
hash: [6bbf58a4,67e920f4] lru: [6c3fec88,6c3fe998]
ckptq: [NULL] fileq: [NULL]
st: XCURRENT md: NULL rsop: 0x00000000 tch: 0
flags: only_sequential_access
LRBA: [0x0.0.0] HSCN: [0xffff.ffffffff] HSUB: [255] RRBA: [0x0.0.0]
buffer tsn: 0 rdba: 0x0040017c (1/380)
scn: 0x0000.000000db seq: 0x01 flg: 0x06 tail: 0x00db0601
frmt: 0x02 chkval: 0x9441 type: 0x06=trans data
Block header dump: 0x0040017c
Object id on Block? Y
seg/obj: 0x38 csc: 0x00.d1 itc: 1 flg: O typ: 1 - DATA
     fsl: 0 fnx: 0x0 ver: 0x01
Itl           Xid                  Uba         Flag Lck        Scn/Fsc
0x01   0x0000.022.00000002 0x00400195.0004.17 --U-    9 fsc 0x0000.000000db
data_block_dump,data header at 0x6c3dc044
===============
buffer with tsn: 0 rdba: 0x0040017c (1/380) has already been dumped
BH (0x6C3FE894) file#: 1 rdba: 0x0040007a (1/122) class 1 ba: 0x6C3D6000
set: 5 dbwrid: 0 obj: 18 objn: 18
hash: [6bbe9b2c,67e80ed4] lru: [6c3fea54,67ea4868]
ckptq: [NULL] fileq: [NULL]
use: [67e3c450,67e3c450] wait: [NULL]
st: XCURRENT md: SHR rsop: 0x00000000 tch: 0
LRBA: [0x0.0.0] HSCN: [0xffff.ffffffff] HSUB: [255] RRBA: [0x0.0.0]
buffer tsn: 0 rdba: 0x0040007a (1/122)
scn: 0x0bcf.c733503a seq: 0x01 flg: 0x06 tail: 0x503a0601
frmt: 0x02 chkval: 0x4ff3 type: 0x06=trans data
Block header dump: 0x0040007a
Object id on Block? Y
seg/obj: 0x12 csc: 0xbcf.c7335039 itc: 1 flg: - typ: 1 - DATA
     fsl: 0 fnx: 0x0 ver: 0x01
Itl           Xid                  Uba         Flag Lck        Scn/Fsc
0x01   0x000e.00f.000001b1 0x008010cf.0074.07 --U-    1 fsc 0x0000.c733503a

Cannot create ctxsys.context type index : ORA-29855 ORA-20000 DRG-11206 ...

Hello everybody,
I have from time to time to create Intermedia or Oracle text indexes in Oracle databes, most 10g ones.
Today I did it in a Oracle 10g under Linux RHEL 5, with this few usual commands:
1) connect SYS/**** as SYSDBA;
2) CREATE TABLESPACE "DRSYS" LOGGING DATAFILE '/path_to_index_files/drsys.ora' SIZE 25M REUSE AUTOEXTEND ON NEXT 1280K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO;
3) @$ORACLE_HOME/ctx/admin/catctx.sql ctxsys DRSYS TEMP NOLOCK
4) connect ctxsys/ctxsys;
5) @$ORACLE_HOME/ctx/admin/defaults/drdeff.sql;
6) connect sa/*****;
7) CREATE INDEX pj_index ON sa.tpiecejointe(pjcontenu) INDEXTYPE IS ctxsys.context parameters ('sync (every "SYSDATE+12/24")');
My issue occured at the 7th step:
CREATE INDEX pj_index ON sa.tpiecejointe(pjcontenu) INDEXTYPE IS ctxsys.context parameters ('sync (every "SYSDATE+12/24")')
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-11206: user filter command /dk2/app/oracle/ctx/bin/ctxhx could not be
executed
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 364
/dk2/app/oracle/ctx/bin/ctxhx is ok and may be executed by anyone.
I found no reason for this problem on the Web.
If somebody can help, thanks a lot...
Thomas

Hi,
for using the sync parameter, the user needs to be granted to execute a job. Oracle makes a job to do the sync. So issue:
GRANT CREATE JOB TO SMADMIN;
from SYS/SYSTEM.
Herald ten Dam
superconsult.nl

(ORA-1653, ORA-1658)TABLESPACE 크기를 확장하는 방법

제품 : ORACLE SERVER
작성날짜 : 1995-11-21
(ora-1653, ora-1658)Tablespace를 확장하는 방법
=============================================
오라클 7.1 이하에서는 tablespace를 확장하려면 해당 tablespace에
데이타 화일을 추가하는 방법을 사용한다. 이 때 추가하는 데이타 화일의
이름은 기존의 화일과 동일한 이름이 아니기만 하면 되지만, 편의상 기존의
화일에 일련 번호를 붙여서 사용하는 것이 일반적이다.
예를 들어 tablespace TOOLS 를 확장한다고 가정하면
$sqlplus system/manager
SQL>select file_name, bytes
from dba_data_files
where tablespace_name = 'TOOLS';
이와 같이 하면 현재 TOOLS tablespace를 구성하고 있는 화일 이름과 크기
(bytes)가 출력된다. 여기서 출력된 file_name 이 /oracle/dbs/toolsORA.dbf
라고 한다면 다음과 같이 하여 tablespace를 확장한다.
SQL>alter tablespace tools
add datafile '/oracle/dbs/tools2ORA.dbf' size 50M;
여기서는 화일의 크기를 50M 로 주었는데 이것은 디스크의 FREE SPACE 와
기존의 데이타 화일의 크기 및 앞으로 들어갈 데이타의 크기 등을 고려하여
적절한 값으로 결정하도록 한다.
오라클 7.2 에서는 위의 방법 외에도 기존의 데이타화일의 크기를 변경시켜서
확장시킬 수 있다.
예를 들어 TOOLS tablespace가 현재 50M 크기의 /oracle/dbs/toolsORA.dbf
화일로 구성되어 있다면 다음과 같이 해서 이 화일의 크기를 100M 로 늘릴 수
있다.
SQL>alter database datafile
'/oracle/dbs/toolsORA.dbf' resize 100M;
RESIZE 옵션은 V7.2 에서 추가된 것으로 기존의 데이타 화일을 확장 또는
축소할 수 있다. 축소하는 경우는 데이타가 들어 있는 경우 하한선 이하로
내려가지는 않는다.
한편, 데이타가 계속 들어가서 tablespace를 꽉 채우게 되면 다음과 같은 명령을
이용하여 자동적으로 tablespace를 확장할 수도 있다.
SQL>alter database datafile
'/oracle/dbs/toolsORA.dbf'
autoextend on
next 10M
maxsize 200M;
이렇게 하면 데이타가 늘어나면서 자동적으로 10M 씩 데이타화일의 크기가
늘어나게 된다. 여기서는 최대 200M 까지 늘어날 수 있도록 설정하였다.

the error is because you can't create the table because your tablespace does not have a free extent large enough to hold the table referenced
So - you might have enough space if you just look at total free space, but the space is fragmented, and so it can't get enough space to create the table.
It references the tablespace in the error message. You can try to coalese the tablespace - I think the syntax is 'alter tablespace xxx coalesce'. If that doesn't work, you can add a datafile or extend an existing datafile, that will give you a big chunk of unfragmented space to work with.
One other thing - when you did the export, by default it changes the storage parameters so that the initial extent will hold the whole table, even if in the source table it spanned several extents
You can re-export with 'COMPRESS=N', then it will not change the space parameters, then try to re-import and it might work.
If none of those work, then it gets ugly - you can do a "import indexfile=xxx.sql" - that will give you a script that has the create table in it, but REMed out. You can change the storage parameters and create the table.
Then you re-import just that table with 'ignore=y', that will load the table even though it already exists.
I say it gets messy because then you have to make sure all the permissions got granted, all the constraints got created, etc, since you created the table manually.
A lot of this advice is 'old-school' - with the new locally managed and system managed tablespaces, this stuff is not needed any more. Is your tablespace dictionary-managed?

SQL Loader and Error ORA-01847/ORA-01839

Hi,
While using the direct loading in SQL-LOADER when we get the ORA-01847/ORA-01839 all the other records are getting errorred out. It goes fine with the conventional loading.
Should I use some parameters or anything to make sure that all the other records are not rejected when we get the ORA-01847/ORA-01839 error while going with the DIRECT loading.
Thanks
Jibin

In internet I found this short message:
“AL32UTF8 is a multi-byte characterset,that means some characters are stored in more than 1 character, that's true for these special characters.
If you have same table definitions in both databases you likely face error ORA-12899.
This metalink note discusses this problem, it's also applicable to sqlloader:
Import reports "ORA-12899: Value too large for column" when using BYTE semantic
Doc ID: Note:563893.1”
By metalink, I can see the Note linked to a one Oracle Internal Bug for Oracle 11g.....
I'm waiting you suggestion... thanks very much in advance.
Regards.
Giovanni

ORA-20006: ORA-01722: invalid number ORA-06512: at "APPS.WF_NOTIFICATION"

Hi,
I am having a wft program, which checks a function activity and depending on the value returned sends difference notifications.
The package body completed successfully from backend and while running the workflow program it sends a notification also. But while opening the notification it gives the following error,
ORA-20006: ORA-01722: invalid number ORA-06512: at "APPS.WF_NOTIFICATION", line 5328 ORA-06512: at line 5
I have 3 procedures in my package body and all the 3 procedures have exceptions defined as follows, if they are using any workflow activities.
==========================================================
EXCEPTION
     WHEN OTHERS THEN
          WF_CORE.context (
          'WFCustCheck',
          'MisCustDataFromTableDoc',
          document_id,
          display_type,
          document,
          document_type,
          SQLERRM
RAISE_APPLICATION_ERROR (-20006, SQLERRM);
==========================================================
But I am not able to figure out what is causing this error. What does this "line 5328 ORA-06512: at line 5" in the error message indicate?. My package body has only 600 lines. And why is the error message not displaying the procedure name? though I have defined the procedure name in the exception.
What is the best way to get the procedure name in the error message? So that it becomes easier for identifying which procedure is causing the erro?
Please let me know.
Thanks

Hi,
Instead of the RAISE_APPLICATION_ERROR command, just replace that with RAISE;
The error is coming out of the package that is sending the notification (WF_NOTIFICATION), which is invoked when you open the notification. I'm guessing that line 5 is the line in your code though.
Are you using documents to send the notification, or are they purely defined in the .wft file?
Matt
Alpha review chapters from my book "Developing With Oracle Workflow" are available on my website:
http://www.workflowfaq.com
http://forum.workflowfaq.com
NEW! - WorkflowFAQ Blog at http://thoughts.workflowfaq.com

Difference between ORA-00018 & ORA-00020

Hi experts,
I am confused about ORA-00018 & ORA-00020, it easier to understand how number of session increased [ora-18],
but what are the special causes that increase number of oracle processes [ora-20] ?
Thanks in advance.

There is a relationship between sessions on a database and the
number of
processes. What happens if we increase the number of sessions without
increasing the number of processes???
The parameters SESSIONS and PROCESSES determine the
size of two arrays in the SGA.
If you try to create more sessions on an instance than specified
by the SESSIONS parameter, you will get an ORA-00018: maximum
number of sessions exceeded.
If you try to create more processes on an instances than specified
by the PROCESSES prameter, you wil get an ORA-00020: maximum
number of processes exceeded.
The number of sessions and processes on your instance can been
seen using a COUNT(*) against V$PROCESS and V$SESSION.
Your job is to determine resonable values, so your users can continue
to work without getting neither ORA-18 nor ORA-20 during normal
conditions. (A run away job, that keeps starting new sessions is not
a normal condition, and it should be stopped by ORA-18 or ORA-20
whichever happens first).
You can join the two V$-views using the columns V$SESSION.PADDR
and V$PROCESS.ADDR.
It is quite normal to see a 1:1 relationship between processes
and sessions. However one OCI-program can create multiple
sessions belonging to one process. Users of Oracle Portal
will experience this behaviour.
The default value for SESSIONS is 1.1*PROCESSES + 5.
It is appropriate for some databases and inappropriate for
others (e.g. Oracle Portal).
Also, I remember a limit on the OS regarding the number of processes
allowed per Oracle user - also I know there is a semaphore
relationship.
On HP-UX there is a kernel parameter called NPROC. Like
PROCESSES and SESSIONS it should have a reasonable
value.
answered by
Jesper Haure Norrevangsource:-http://ora-00020.ora-code.com/msg/40800.html

OS 명령으로 DATAFILE을 삭제한 경우:ORA-1157, ORA-1110

Similar Messages

Maybe you are looking for