2007. 1. 20. 21:13 좋아하는 음악
'분류 전체보기'에 해당되는 글 1016건
- 2007.01.20 jessica simpson " When You Told Me You Loved Me "
- 2007.01.18 최근에 지른 책들. 2
- 2007.01.16 Death Note 를 보고. 1
- 2007.01.15 extreme 의 'midnight express'
- 2007.01.10 내 기타 G250 의 세부모습 1
- 2007.01.07 공각기동대 Solid State Society 1
- 2007.01.04 oracle relink하기 2
- 2007.01.02 controlfile 재생성하기
- 2006.12.29 아! 올 한해도 이렇게 가는구나.
- 2006.12.28 ORA-00257
2007. 1. 18. 20:39 아무거나
최근에 지른 책들.
인터파크에서 모방범만 살려고 했는데 어찌하다 보니 13권이나 지르게 되었다.
모방범은 원래 가격이 12000원인데다가 10% discount 밖에 안되서 10800원.
3권도 만만치 않은 가격이라고 생각하고 있었는데 (책 두꺼운건 마음에 든다), 그후에 갑자기 S-money 때문에 웬지 더 싸게 산다는 느낌 때문인지는 몰라도..
나머지 것들을 계속 클릭질 하고 있었다. -_-;
offline 보다는 거의 1만5천원정도 save 한것 같다. 정확히는 모름 계산하기 귀찮아서.
당분간 2~3개월 정도는 나의 무료함을 이 책들과 함께 달래야 싶을 듯.
2007. 1. 16. 21:45 내가 본 영화
Death Note 를 보고.
이번주에 개봉하는 거 같던데, 호기심 때문에 다운 받아서 봐 버렸다. 근데 1,2편으로 나누어져 나올것 같군. 뭐 영화는 만화책 내용을 얼마나 충실하게 그려냈느냐 하는 정도. 딱 그정도 인거 같다. 만화 내용이 워낙에 방대해서 그걸 짧은 시간에 다 담기에는 역부족인 듯.
만화가 훨씬 나은것 같다. 얼마전에 만화도 13권으로 완결이 되었던데, 해적판으로 나올때 번역해 놓은 글씨가 너무 작아서 읽기 힘들어서 5권까지만 읽고 포기했었는데..시간나면 대여점에서 빌려 읽어야지.
이 만화책은 점점 스토리가 복잡해져서 정말 천천히 읽어야 내용이 들어온다. 아무튼 읽으면서 삶과 죽음에 대해 나름대로 생각을 할수 있는 괜찮은 작품이라고 본다.
2007. 1. 15. 22:32 좋아하는 음악
extreme 의 'midnight express'
Nuno의 엄청한 기타실력이 드러나 있는 곡. 얼마전 여걸 6 인가. 거기 보니깐 지현우 인가? 올드미스 다이어리 영화홍보하러 나왔던데, 이곡을 잠깐 치는 것 같더군. 멋졌음.(얘는 음악활동도 하는걸로 기억남)
" Midnight Express"
2007. 1. 10. 20:24 아무거나
내 기타 G250 의 세부모습
2007. 1. 7. 15:04 내가 본 영화
공각기동대 Solid State Society
2007. 1. 4. 11:08 오라클
oracle relink하기
OS patch를 했거나, oracle engine 을 다른 서버로 통째로 copy 했을 경우 등에
relink 명령을 해주는데 이에 대한 설명이다.
============================================================
Relinking occurs automatically under these circumstances
- An Oracle product has been installed with an Oracle provided installer.
- An Oracle patch set has been applied via an Oracle provided installer.
Relinking Oracle manually is suggested under these circumstances
- An OS upgrade has occurred.
- A change has been made to the OS system libraries. This can occur during the application of an OS patch.
- A new install failed during the relinking phase.
- Individual Oracle executables core dump during initial startup.
- An individual Oracle patch has been applied with explicit relink instructions or the relink is integrated into the patch install script.
Steps to manually relink Oracle
- Logon and set environment variables:
as oracle:source $csetsid
env | grep ORA - Verify and/or Configure the Unix Environment for Proper Relinking:
Sun Solaris Oracle 7.3.x, 8.0.x, 8.1.x or 9.0.x:
- Ensure that /usr/ccs/bin is before /usr/ucb in $PATH:
( should return "/usr/ccs/bin/ld" )which ld - Set LD_LIBRARY_PATH to include $ORACLE_HOME/lib
- If using 64bit Oracle, LD_LIBRARY_PATH should also include $ORACLE_HOME/lib64.
- Ensure that /usr/ccs/bin is before /usr/ucb in $PATH:
- Verify the correct absolute path for $ORACLE_HOME
env | grep ORACLE_HOME
- Before relinking Oracle, shutdown all the databases and the listener.
- Run the OS Commands to Relink Oracle:
- Oracle 7.3.x
- For executables: oracle, exp, imp, sqlldr, tkprof
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk install - For executables: svrmgrl, svrmgrm
cd $ORACLE_HOME/svrmgr/lib
make -f ins_svrmgr.mk linstall minstall
linstall is for svrmgrl, minstall is for svrmgrm - For executables: sqlplus
cd $ORACLE_HOME/sqlplus/lib
make -f ins_sqlplus.mk install - For executables: dbsnmp, oemevent, oratclsh
cd $ORACLE_HOME/network/lib
make -f ins_agent.mk install - For executables: names, namesctl
cd $ORACLE_HOME/network/lib
make -f ins_names.mk install - For executables: tnslsnr, lsnrctl, tnsping, csmnl, trceval, trcroute
cd $ORACLE_HOME/network/lib
make -f ins_network.mk install
- For executables: oracle, exp, imp, sqlldr, tkprof
- Oracle 8.0.x
- For executables: oracle, exp, imp, sqlldr, tkprof, mig, dbv, orapwd, rman, svrmgrl, ogms, ogmsctl
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk install - For executables: sqlplus
cd $ORACLE_HOME/sqlplus/lib
make -f ins_sqlplus.mk install - For executables: dbsnmp, oemevent, oratclsh, libosm.so
cd $ORACLE_HOME/network/lib
make -f ins_oemagent.mk install - For executables: tnslsnr, lsnrctl, namesctl, names, osslogin, trcasst, trcroute
cd $ORACLE_HOME/network/lib
make -f ins_network.mk install
- For executables: oracle, exp, imp, sqlldr, tkprof, mig, dbv, orapwd, rman, svrmgrl, ogms, ogmsctl
- Oracle 8.1.x or 9.0.xA "relink" script ( 8i new feature ) is provided in the $ORACLE_HOME/bin directory:-or-
- For executables: oracle, exp, imp, sqlldr, tkprof, mig, dbv, orapwd, rman, svrmgrl, ogms, ogmsctl
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk install - For executables: sqlplus
cd $ORACLE_HOME/sqlplus/lib
make -f ins_sqlplus.mk install - For executables: dbsnmp, oemevent, oratclsh
cd $ORACLE_HOME/network/lib
make -f ins_oemagent.mk install - For executables: names, namesctl
cd $ORACLE_HOME/network/lib
make -f ins_names.mk install - For executables: osslogin, trcasst, trcroute, onrsd, tnsping
cd $ORACLE_HOME/network/lib
make -f ins_net_client.mk install - For executables: tnslsnr, lsnrctl
cd $ORACLE_HOME/network/lib
make -f ins_net_server.mk install
- For executables: oracle, exp, imp, sqlldr, tkprof, mig, dbv, orapwd, rman, svrmgrl, ogms, ogmsctl
- You still have the option of running the "make" commands independently:
-
cd $ORACLE_HOME/binbug 1337908 : on Solaris with Oracle 8.1.6, also do: relink utilities
relink
usage: relink >parameter<
accepted values for parameter: all, oracle, network, client, client_sharedlib,
interMedia, precomp, utilities, oemagent
i.e. You can relink ALL executables with the following command: relink all
- Oracle 7.3.x
- How to tell if relinking was successful:
If relinking was successful, the make command will eventually return to the OS prompt without an error. There will not be a "Relinking Successful" type message.
If you receive an error message during relinking:
Relinking errors usually terminate the relinking process and contain verbage similar to the following:
Fatal error', 'Ld: fatal', 'Exit Code 1
Fatal error', 'Ld: fatal', 'Exit Code 1
2007. 1. 2. 22:17 오라클
controlfile 재생성하기
controlfile 재생성하기
PURPOSE
This article describes how you can recreate your controlfile.
SCOPE & APPLICATION
For DBAs who need to recreate the controlfile.
WARNING:
--------
You should only need to recreate your control file under very special
circumstances:
- All current copies of the control file have been lost or are corrupted.
- You need to change a "hard" database parameter that was set when the
database was first created, such as MAXDATAFILES, MAXLOGFILES,
MAXLOGHISTORY, etc.
- You are restoring a backup in which the control file is corrupted or
missing.
- Oracle Customer Support advises you to do so.
- If you are moving your database to another machine which is
running the same operating system but the location of the datafiles,
logfiles is not the same.
Instructions:
=============
I. CREATING A NEW CONTROL FILE FROM THE EXISTING CONTROL FILE:
--------------------------------------------------------------
1. If you are running Oracle7 or higher you can get Oracle to generate
a script for you that enables you to recreate the controlfile. Run the
following command while the database is mounted or open and connected
as a user with DBA privileges:
% svrmgrl
SVRMGR> connect internal
SVRMGR> startup mount
SVRMGR> alter database backup controlfile to trace;
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
Oracle6 does not have this feature and therefore you will need to build
the CREATE CONTROLFILE statement yourself. The syntax is discussed in
detail in the Oracle SQL Reference Guide.
2. The trace file will be stored in the USER_DUMP_DEST destination,
which is set to "$ORACLE_HOME/rdbms/log" by default on Unix platforms.
To find out what USER_DUMP_DEST is set to, follow one of the following:
a) Look in the parameter file (init<SID>.ora on UNIX and Windows NT,
<node>_<ora_sid>_init.ora on VMS) for the parameter:
USER_DUMP_DEST = d:/oradata/orcl/trce/udump
b) Using SQL*PLus you can issue the following command:
SQL> SELECT value
2> FROM v$parameter
3> WHERE name = 'user_dump_dest';
VALUE
------------------------------------------------
d:/oradata/orcl/trace/udump
c) Using Server Manager you can issue the following command:
SVRMGR> show parameter <string>
SVRMGR> show parameter user_dump_dest;
The easiest way to locate the correct trace is to look at its date.
A file will exist with the current date and time. The naming
convention for these files is operating system specific.
Example:
--------
% cd $ORACLE_HOME/rdbms/log
% ls -l
-rw-r--r-- 1 osupport dba 2315 Oct 3 16:39 alert_p716.log
-rw-r--r-- 1 osupport dba 1827 Oct3 16:39 p716_ora_26220.trc
In this example, the file "p716_ora_26220.trc" is the trace file
produced that contains a script to create the control file.
NOTE: The trace file is handled a bit differently when issuing this
command from a connection to the database using shared server. The
shared server connection is created by PMON and the connection inherits
its environment, meaning the trace file will be created in the directory
referenced by the initialization parameter BACKGROUND_DUMP_DEST
instead of the USER_DUMP_DEST.
Use similar commands as given above to locate the directory
referenced in the BACKGROUND_DUMP_DEST.
3. Modify the trace file and use it as a script to create the control
file. Copy the trace file to a script file, such as "new_control.sql",
delete the header information prior to the words STARTUP NOMOUNT,
and make any other desired changes, such as increasing MAXDATAFILES,
MAXLOGFILES, etc.
Sample:
-------------------------- <start trace> -----------------------------
Dump file /u01/oracle/7.1.6/rdbms/log/p716_ora_26220.trc
Oracle7 Server Release 7.1.6.2.0 - Production Release
With the distributed and replication options
PL/SQL Release 2.1.6.2.0 - Production
ORACLE_HOME = /u01/oracle/7.1.6
ORACLE_SID = p716
Oracle process number: 9 Unix process id: 26220
System name: SunOS
Node name: tcsun2
Release: 5.4
Version: Generic_101945-27
Machine: sun4m
Tue Oct 3 16:39:13 1995
*** SESSION ID:(6.61)
# The following commands will create a new control file and use it
# to open the database.
# No data other than log history will be lost. Additional logs may
# be required for media recovery of offline data files. Use this
# only if the current version of all online logs are available.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "P716" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 8
MAXLOGHISTORY 800
LOGFILE
GROUP 1 '/u01/oracle/7.1.6/dbs/log1p716.dbf' SIZE 500K,
GROUP 2 '/u01/oracle/7.1.6/dbs/log2p716.dbf' SIZE 500K,
GROUP 3 '/u01/oracle/7.1.6/dbs/log3p716.dbf' SIZE 500K
DATAFILE
'/u01/oracle/7.1.6/dbs/systp716.dbf' SIZE 40M,
'/u01/oracle/7.1.6/dbs/tempp716.dbf' SIZE 550K,
'/u01/oracle/7.1.6/dbs/toolp716.dbf' SIZE 15M
;
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE
# Database can now be opened normally.
ALTER DATABASE OPEN;
---------------------- <end trace> ----------------------------------
4. Shutdown the database (NORMAL, IMMEDIATE, TRANSACTIONAL (Oracle8 only)
but not ABORT).
SVRMGR> shutdown immediate
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
5. Take a full database backup.
6. Rename/move the existing database controlfiles to a backup (The REUSE
option will overwrite the original files). The size of the controlfile
will be increased by increasing the value of MAXDATAFILES,
MAXLOGMEMBERS, etc.
Example:
--------
% cd $ORACLE_HOME/dbs
% mv ctrlV716.ctl ctrlV716.bak
7. Create the controlfile within Server Manager
SVRMGR> connect internal
SVRMGR> @new_control.sql
If you get the "Statement processed" message, the database will
be opened with a brand new control file.
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
8. At the first opportunity, shut the database down (normal, immediate or
transactional oracle8 only) and take a full backup.
II. CREATING A NEW CONTROL FILE WITHOUT AN EXISTING CONTROL FILE:
-----------------------------------------------------------------
CREATE CONTROLFILE SYNTAX:
The following is information on the create control file syntax. This
information is fully documented in the Oracle SQL Reference Manual.
CREATE CONTROLFILE [REUSE]
DATABASE name
[LOGFILE filespec [, filespec] ...]
RESETLOGS | NORESETLOGS
[MAXLOGFILES integer]
[DATAFILE filespec [, filespec] ...]
[MAXDATAFILES integer]
[MAXINSTANCES integer]
[ARCHIVELOG | NOARCHIVELOG]
[SHARED | EXCLUSIVE]
The complete procedure follows:
1. Take a full backup of the database, including all datafiles and redo
log files.
2. Go into SQL*DBA or Server Manager and do a STARTUP NOMOUNT.
3. Issue the CREATE CONTROLFILE statement.
Example:
--------
CREATE CONTROLFILE REUSE DATABASE "P716" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 50
MAXLOGMEMBERS 3
MAXDATAFILES 300
MAXINSTANCES 8
MAXLOGHISTORY 500
LOGFILE
GROUP 1 '/u01/oracle/7.1.6/dbs/log1p716.dbf' SIZE 1M,
GROUP 2 '/u01/oracle/7.1.6/dbs/log2p716.dbf' SIZE 1M,
GROUP 3 '/u01/oracle/7.1.6/dbs/log3p716.dbf' SIZE 1M
DATAFILE
'/u01/oracle/7.1.6/dbs/systp716.dbf' SIZE 40M,
'/u01/oracle/7.1.6/dbs/tempp716.dbf' SIZE 1M,
'/u01/oracle/7.1.6/dbs/toolp716.dbf' SIZE 15M ;
4. Perform media recovery on the database.
SVRMGR> recover database;
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
5. Open the database.
SVRMGR> alter database open;
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
6. At the first opportunity, shut the database down and take a full cold
backup.
Additional Errors:
------------------
ORA-205 ORA-7360 ORA-376 ORA-1110 ORA-1111
PURPOSE
This article describes how you can recreate your controlfile.
SCOPE & APPLICATION
For DBAs who need to recreate the controlfile.
WARNING:
--------
You should only need to recreate your control file under very special
circumstances:
- All current copies of the control file have been lost or are corrupted.
- You need to change a "hard" database parameter that was set when the
database was first created, such as MAXDATAFILES, MAXLOGFILES,
MAXLOGHISTORY, etc.
- You are restoring a backup in which the control file is corrupted or
missing.
- Oracle Customer Support advises you to do so.
- If you are moving your database to another machine which is
running the same operating system but the location of the datafiles,
logfiles is not the same.
Instructions:
=============
I. CREATING A NEW CONTROL FILE FROM THE EXISTING CONTROL FILE:
--------------------------------------------------------------
1. If you are running Oracle7 or higher you can get Oracle to generate
a script for you that enables you to recreate the controlfile. Run the
following command while the database is mounted or open and connected
as a user with DBA privileges:
% svrmgrl
SVRMGR> connect internal
SVRMGR> startup mount
SVRMGR> alter database backup controlfile to trace;
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
Oracle6 does not have this feature and therefore you will need to build
the CREATE CONTROLFILE statement yourself. The syntax is discussed in
detail in the Oracle SQL Reference Guide.
2. The trace file will be stored in the USER_DUMP_DEST destination,
which is set to "$ORACLE_HOME/rdbms/log" by default on Unix platforms.
To find out what USER_DUMP_DEST is set to, follow one of the following:
a) Look in the parameter file (init<SID>.ora on UNIX and Windows NT,
<node>_<ora_sid>_init.ora on VMS) for the parameter:
USER_DUMP_DEST = d:/oradata/orcl/trce/udump
b) Using SQL*PLus you can issue the following command:
SQL> SELECT value
2> FROM v$parameter
3> WHERE name = 'user_dump_dest';
VALUE
------------------------------------------------
d:/oradata/orcl/trace/udump
c) Using Server Manager you can issue the following command:
SVRMGR> show parameter <string>
SVRMGR> show parameter user_dump_dest;
The easiest way to locate the correct trace is to look at its date.
A file will exist with the current date and time. The naming
convention for these files is operating system specific.
Example:
--------
% cd $ORACLE_HOME/rdbms/log
% ls -l
-rw-r--r-- 1 osupport dba 2315 Oct 3 16:39 alert_p716.log
-rw-r--r-- 1 osupport dba 1827 Oct3 16:39 p716_ora_26220.trc
In this example, the file "p716_ora_26220.trc" is the trace file
produced that contains a script to create the control file.
NOTE: The trace file is handled a bit differently when issuing this
command from a connection to the database using shared server. The
shared server connection is created by PMON and the connection inherits
its environment, meaning the trace file will be created in the directory
referenced by the initialization parameter BACKGROUND_DUMP_DEST
instead of the USER_DUMP_DEST.
Use similar commands as given above to locate the directory
referenced in the BACKGROUND_DUMP_DEST.
3. Modify the trace file and use it as a script to create the control
file. Copy the trace file to a script file, such as "new_control.sql",
delete the header information prior to the words STARTUP NOMOUNT,
and make any other desired changes, such as increasing MAXDATAFILES,
MAXLOGFILES, etc.
Sample:
-------------------------- <start trace> -----------------------------
Dump file /u01/oracle/7.1.6/rdbms/log/p716_ora_26220.trc
Oracle7 Server Release 7.1.6.2.0 - Production Release
With the distributed and replication options
PL/SQL Release 2.1.6.2.0 - Production
ORACLE_HOME = /u01/oracle/7.1.6
ORACLE_SID = p716
Oracle process number: 9 Unix process id: 26220
System name: SunOS
Node name: tcsun2
Release: 5.4
Version: Generic_101945-27
Machine: sun4m
Tue Oct 3 16:39:13 1995
*** SESSION ID:(6.61)
# The following commands will create a new control file and use it
# to open the database.
# No data other than log history will be lost. Additional logs may
# be required for media recovery of offline data files. Use this
# only if the current version of all online logs are available.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "P716" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 30
MAXINSTANCES 8
MAXLOGHISTORY 800
LOGFILE
GROUP 1 '/u01/oracle/7.1.6/dbs/log1p716.dbf' SIZE 500K,
GROUP 2 '/u01/oracle/7.1.6/dbs/log2p716.dbf' SIZE 500K,
GROUP 3 '/u01/oracle/7.1.6/dbs/log3p716.dbf' SIZE 500K
DATAFILE
'/u01/oracle/7.1.6/dbs/systp716.dbf' SIZE 40M,
'/u01/oracle/7.1.6/dbs/tempp716.dbf' SIZE 550K,
'/u01/oracle/7.1.6/dbs/toolp716.dbf' SIZE 15M
;
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE
# Database can now be opened normally.
ALTER DATABASE OPEN;
---------------------- <end trace> ----------------------------------
4. Shutdown the database (NORMAL, IMMEDIATE, TRANSACTIONAL (Oracle8 only)
but not ABORT).
SVRMGR> shutdown immediate
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
5. Take a full database backup.
6. Rename/move the existing database controlfiles to a backup (The REUSE
option will overwrite the original files). The size of the controlfile
will be increased by increasing the value of MAXDATAFILES,
MAXLOGMEMBERS, etc.
Example:
--------
% cd $ORACLE_HOME/dbs
% mv ctrlV716.ctl ctrlV716.bak
7. Create the controlfile within Server Manager
SVRMGR> connect internal
SVRMGR> @new_control.sql
If you get the "Statement processed" message, the database will
be opened with a brand new control file.
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
8. At the first opportunity, shut the database down (normal, immediate or
transactional oracle8 only) and take a full backup.
II. CREATING A NEW CONTROL FILE WITHOUT AN EXISTING CONTROL FILE:
-----------------------------------------------------------------
CREATE CONTROLFILE SYNTAX:
The following is information on the create control file syntax. This
information is fully documented in the Oracle SQL Reference Manual.
CREATE CONTROLFILE [REUSE]
DATABASE name
[LOGFILE filespec [, filespec] ...]
RESETLOGS | NORESETLOGS
[MAXLOGFILES integer]
[DATAFILE filespec [, filespec] ...]
[MAXDATAFILES integer]
[MAXINSTANCES integer]
[ARCHIVELOG | NOARCHIVELOG]
[SHARED | EXCLUSIVE]
The complete procedure follows:
1. Take a full backup of the database, including all datafiles and redo
log files.
2. Go into SQL*DBA or Server Manager and do a STARTUP NOMOUNT.
3. Issue the CREATE CONTROLFILE statement.
Example:
--------
CREATE CONTROLFILE REUSE DATABASE "P716" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 50
MAXLOGMEMBERS 3
MAXDATAFILES 300
MAXINSTANCES 8
MAXLOGHISTORY 500
LOGFILE
GROUP 1 '/u01/oracle/7.1.6/dbs/log1p716.dbf' SIZE 1M,
GROUP 2 '/u01/oracle/7.1.6/dbs/log2p716.dbf' SIZE 1M,
GROUP 3 '/u01/oracle/7.1.6/dbs/log3p716.dbf' SIZE 1M
DATAFILE
'/u01/oracle/7.1.6/dbs/systp716.dbf' SIZE 40M,
'/u01/oracle/7.1.6/dbs/tempp716.dbf' SIZE 1M,
'/u01/oracle/7.1.6/dbs/toolp716.dbf' SIZE 15M ;
4. Perform media recovery on the database.
SVRMGR> recover database;
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
5. Open the database.
SVRMGR> alter database open;
If you are running Oracle9i or higher you need to use sqlplus instead of
svrmgrl.
6. At the first opportunity, shut the database down and take a full cold
backup.
Additional Errors:
------------------
ORA-205 ORA-7360 ORA-376 ORA-1110 ORA-1111
2006. 12. 29. 19:34 아무거나
아! 올 한해도 이렇게 가는구나.
Applies to:
Oracle Server - Standard Edition - Version: 10.1.0.0This problem can occur on any platform.
Symptoms
Connections to the database Receive ORA-00257Cause
The max limit for flash recovery area(db_recovery_file_dest_size) is reached.Solution
SOLUTION:
========
1. Check whether the database is in archive log mode and automatic archiving is enabled.
SQL> archive log list;
2. If Archive destination is USE_DB_RECOVERY_FILE_DEST, find the archive destination by :
SQL> show parameter db_recovery_file_dest;
Check what is the value set for db_recovery_file_dest_size
3. Find the space used in flash recovery area by :
SQL> SELECT * FROM V$RECOVERY_FILE_DEST;
4. If SPACE_USED is equal to SPACE_LIMIT, move the archive logs to different destination.
5. Archive all the log files
SQL> alter system archive log all;
NOTE: See Note 315098.1 for pointers on backing up files from the flash recovery area to decrease space usage
6. If ORA-16020: less destinations available than specified by
LOG_ARCHIVE_MIN_SUCCEED_DEST
is received for step 5, then
For each destination give the correct archivelog path and issue:
SQL>alter system set LOG_ARCHIVE_DEST_.. = 'location=/archivelogpath reopen';
NOTE:
If you have configurated Flash Recovery Area (default in 10gR2)--meaning that you have set the two initialization parameters:
-- DB_RECOVERY_FILE_DEST_SIZE
-- DB_RECOVERY_FILE_DEST:
you can not use the LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters any more. You must always use the LOG_ARCHIVE_DEST_n parameters in case you have configured flash recovery area. LOG_ARCHIVE_DEST_10 is implicitly set to USE_DB_RECOVERY_FILE_DEST if you create a recovery area and do not set any other local archiving destinations.
If you try to use LOG_ARCHIVE_DEST with a Flash Recovery Area configured you will receive errors like
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16018: cannot use LOG_ARCHIVE_DEST with LOG_ARCHIVE_DEST_n or
DB_RECOVERY_FILE_DEST
7. Just switch the logs to verify:
SQL> alter system switch logfile;
NOTE:
====
If you want to increase the flash recovery area:
STEPS:
=====
1. Note down the path of flash recovery area.
SQL> show parameter db_recovery_file_dest;
2. Disable the Flash Recovery Area
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST='' SCOPE=BOTH SID='*';
3. Increase the Flash Recovery Area
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 10g SCOPE=BOTH SID='*';
4. Enable the Flash Recovery Area
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = '/dir1' SCOPE=BOTH SID='*';
If the flash recovery area location is an Automatic Storage Management disk group named disk1, for example, then you can do the following:
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = '+disk1' SCOPE=BOTH SID='*';
