개발자(開發者) a developer

오라클 원격 접속하기

1. 오라클 서버에 리스너(Listener) 를 가동한다.

다른 컴퓨터에서 오라클에 접속하려면 리스너가 동작해야 한다. 오라클 9i라면, 설치시에 기본적으로 리스너를 설치하고, 서비스를 구성한다. Enterprise Edition이나 Standard Edition은 기본으로 구성하는 단계가 있는데, 혹시 구성 중에 취소했다면 안 만들어 졌을 수도 있다.

리스너는 네트워크를 이용하여 클라이언트에서 오라클 서버로 연결하기 위한 오라클 네트워크 관리자 이다. 오라클 서버에서 리스너를 시작시켜 주어야 클라이언트들이 접속 할 수 있다.

리스너 관련 명령어

c:\>lsnrctl start  리스너 시작하기

c:\>lsnrctl stop  리스너 정지하기

c:\>lsnrctl reload  리스너 재시작하기

c:\>lsnrctl status  리스너 상태보기

c:\>lsnrctl help  도움말

리스너 구성 파일은 $ORACLE_HOME/network/admin 아래에 있는 listener.ora 파일이며, 오라클 서버에서 클라이언트의 요청을 듣고 클라이언트와의 통신 환경을 설정한다.

listener.ora 파일이 없다면, cmd 창을 열어서

C:\> lsnrctl start

라고 치면 자동으로 만들어진다.

만들어진 리스너는 서비스로 등록되는데, 서비스 관리자에서 Oracle....TNSListener라는 이름이 바로 리스너 서비스다.

이 서비스의 시작 유형을 "자동" 으로 해 놓는 것이 편리하다.

서비스 관리자에서 이 서비스를 start 시키거나, cmd 창에서

C:\> lsnrctl start

하면 외부에서 접속할 수 있다.

2. 클라이언트에 오라클 클라이언트를 설치 한다.

리눅스용 오라클 클라이언트는 http://www.oracle.com/technology/global/kr/software/products/database/oracle10g/index.html 에서 다운 받을 수 있다. 되도록이면 설치되어 있는 오라클 버전하고 같은 것을 다운 받는다.
주) 리눅스용 오라클 클라이언트는 X 윈도 에서 설치가 가능하다.

3. 리눅스 시스템의 경우 .bash_profile 파일을 수정한다.

SQL PLUS 같은 터미널 접속 이라면 먼저 해당 계정의 .bash_profile 파일을 수정해 주어야 한다.
예를 들면 아래와 같다.

export ORACLE_BASE=/oracle/app/oracle
export ORACLE_HOME=/oracle/app/oracle/product/8.1.7
export ORACLE_OWNER=oracle
export ORACLE_SID=ORCL
export TMPDIR=$ORACLE_BASE/tmp
export PATH=$PATH:$ORACLE_HOME/bin:/usr/local/java/bin
export JAVA_HOME=/usr/local/java
export TNS_ADMIN=$ORACLE_HOME/network/admin
export NLS_LANG=American_America.KO16KSC5601
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH

이 계정으로 접속을 했을 때 아무 곳에서나 오라클의 접속이 가능 하도록 패스 지정을 한 것이다.
 

접속 방법

사용자 이름   : <사용자계정> 암호          : <계정비밀번호> 호스트 스트링 : tnsnames.ora 에 설정된 호스트의 별칭

주) 웹을 이용한 접속 이라면 PHP 의 경우 오라클 클라이언트 설치 경로를 지정해 주어 PHP 를 다시 컴파일 해주어야 하며 JSP 같은 경우 라면 오라클 경로를 다시 잡아 주어야 한다.

4. 클라이언트에서 tnsnames.ora 파일을 수정한다.

tnsnames.ora 파일은 오라클 서버로 접속할 때 필요한 프로토콜 및 포트번호, 서버주소, 인스턴스 등을 설정해 주는 파일로써, C:\oracle\ora92\network\admin 디렉토리에 위치한다.

 

MY_DB =   (DESCRIPTION =     (ADDRESS_LIST =       (ADDRESS = (PROTOCOL = TCP)(HOST = 126.138.95.21)(PORT = 1521))     )     (CONNECT_DATA =       (SERVICE_NAME = oradb)     )   )

오라클 클라이언트는 원격 DB 접속을 위해 위의 파일 내용을 참조하게 된다.

MY_DB 는 원격 데이터베이스의 사용자 정의 명칭이다. 자신의 PC 에서만 유효한 이름이므로 아무렇게나 주어도 된다. HOST = 126.138.95.21 이 부분이 중요한데...실제 원격 DB 가 위치하고 있는 머신의 IP 주소를 입력하면 된다. 포트는 기본 값이 1521 이다.

SERVICE_NAME 이라는 것은 실제 데이터베이스 이름이라고 보면 된다. MY_DB 가 내 PC 에서만 유효한 것이라면 SERVICE_NAME 은 NETWORK 내에서 유일해야 하므로 실제 원격 머신 상에서 오라클 Database 를 Create할 때 결정되어진다. SERVICE_NAME 및 호스트 머신의 IP 주소에 대해서는 원격 Database 를 관리하는 DATABASE 관리자에게 문의하면 된다.

각 오라클의 버전별로 약간의 tnsname.ora 의 내용이 약간씩 다를 수 있으나 위에 설명한 내용은 9i 에서도 그대로 적용된다.

실제 연결을 위해서 tnsname.ora 를 직접 편집하는 것보다 Net Configuration Assistant 라는 프로그램을 이용하길 바란다. 이 프로그램을 이용하여 원격 DB 연결을 설정하면 실제 연결 테스트를 해 볼 수도 있고, 직접 작성으로 인한 tnsname.ora 파일의 버전간 차이 등의 문제를 피할 수 있다. 위의 프로그램은 오라클 클라이언트를 설치하면 프로그램 메뉴에서 찾아볼 수 있다. 해당 프로그램 사용법은 지면 관계상 생략하나 네이버에서 검색하면 쉽게 찾아볼 수가 있을 것이다.

그 후에 다시 로그아웃 하고 로그인을 한후 sqlplus 라고 입력하면 됩니다.

오라클의 설치도 쉽지 않지만 클라이언트의 설치도 간단치 않으므로 차근차근 실수 없이 진행 해야 합니다.

TNSPING으로 접속 TEST하는 방법

Windows 3.1용 SQL*Net을 설치한 경우에 Nettest.exe로써 Server에 접속 여부를 test했었으나, Windows 95용 SQL*Net을 설치하면 tnsping.exe라는 프로그램이 생긴다. 이 프로그램은 일반적인 TCP/IP 프로그램에서 제공하는 Ping Utility와 유사한 방식으로 DB Server에 Login 여부를 확인할 수 있다. SQL*Net 2.2이상에서만 제공이 되며, SQL*Net V1에서는 사용할 수 없다.

C:\oracle\ora92\bin\tnsping.exe

[ 사용 방법 ]

tnsnames.ora file에 tns services name 및 접속에 관련된 내용을 기술한다.　　
예: MY_DB =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 126.138.95.21)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = oradb)
    )
  )

tnsping utility 사용 예
 

c:\>tnsping oradb 5 TNS Ping Utility for 32-bit WINDOWS: Version 9.2.0.1.0 - Production on 18-NOV-2006 09:52:34　　 Copyright (c) Oracle 1997 Corporation. All rights reserved. 사용된 매개변수 파일 C:\oracle\ora92\network\admin\sqlnet.ora 별칭 분석을 위해 TNSNAMES 어댑터 사용 Attempting to contact　(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 126.138.95.21)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = oradb))) 확인 (50 밀리초)　 확인 (30 밀리초)　 확인 (30 밀리초)　 확인 (50 밀리초)　 확인 (30 밀리초)

주) tnsping 은 되는데 오라클 연결이 안될 때는 방화벽을 검사한다. 방화벽은 예외설정을 해도 되지 않고 사용안함 설정을 해야 한다. 또한 tnsnames.ora 파일에 HOST = 126.138.95.21 부분을 ip 주소가 아닌 host 명으로 했을 때 안되는 경우가 있다.

-----------------------------------------------------------------------------------------------------
TNSListener!! 잊지 않겠다 ㅡㅡ+

sqlplus /nolog


sql> conecnt sys/pass as sysdba
sql> startup

sqlplus /nolog

connect sys/패스워드 as sysdba

\uc815\ubcf4: make[1]: Leaving directory `/home/oracle/database/product/11.1.0/db_1/rdbms/lib'

\uc815\ubcf4: make[1]: *** [/home/oracle/database/product/11.1.0/db_1/rdbms/lib/extproc32] \uc624\ub958 1

\uc815\ubcf4: make: *** [extproc32] \uc624\ub958 2

\uc815\ubcf4: \uc0dd\uc131\ub41c \ud504\ub85c\uc138\uc2a4\uc5d0\uc11c \ucd9c\ub825 \ub9c8\uce68.
\uc815\ubcf4: ----------------------------------
\uc815\ubcf4: \uc791\uc5c5\uc5d0\uc11c \ubc1c\uc0dd\ud55c \uc608\uc678 \uc0ac\ud56d: make
\uc608\uc678 \uc0ac\ud56d \uc774\ub984: MakefileException
\uc608\uc678 \uc0ac\ud56d \ubb38\uc790\uc5f4: make \ud30c\uc77c '/home/oracle/database/product/11.1.0/db_1/rdbms/lib/ins_rdbms.mk'\uc758 'all_no_orcl' \ub300\uc0c1\uc744 \ud638\ucd9c\ud558\ub294 \uc911 \uc624\ub958\uac00 \ubc1c\uc0dd\ud588\uc2b5\ub2c8\ub2e4. \uc790\uc138\ud55c \ub0b4\uc6a9\uc740 '/home/oracle/oraInventory/logs/installActions2008-07-17_09-52-57PM.log'\uc744(\ub97c) \ucc38\uc870\ud558\uc2ed\uc2dc\uc624
\uc608\uc678 \uc0ac\ud56d \uc2ec\uac01\ub3c4: 1

-------------------------------------------------------------------------
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.2
This problem can occur on any platform.
After installing any One-off patch in RAC nodes, one of those nodes may fail to start the instance.

NOTE: We did observe the similar problem on 10.2.0.2 RAC installations where certain libraries are not copied from the installing node to other RAC nodes. For such type of problem while performing installation, please refer to the following note.

Note 363840.1 - 10.2.0.2 RAC: ORA-7445 in KKXSYN or KKXCMS ON ALL NODES BUT INSTALL NODE

Symptoms
Oracle Instance does not startup on one of RAC the nodes after installing any One-off Patch.

If you see the alert and trace log files, you may see the following errors:

ORA-00469: CKPT process terminated with error

ORA-07445: exception encountered: core dump [] [] [] [] [] []

Cause
It was noted that the resulting 'Oracle' binaries on different nodes were not the same. Running a cksum on all involved libraries in lib/ and rdbms/lib/, it was evident that libknlopt.a was different across nodes. The object modules that get into libknlopt.a however are identical, so it clearly appears that libknlopt.a isn't relinked on nodes other than the installation one.
Solution
Copy the good library in the faulty node and manually re-link the Oracle again.

Ensure all instances are shut down !

Manually copy good $ORACLE_HOME/rdbms/lib/libknlopt.a from the local node to all remote faulty nodes and relink Oracle again on all faulty nodes.

eg: cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk ioracle

--------------------------------------------------------------------------

[root@smbi-web lib]# make -f ins_rdbms.mk ioracle
chmod 755 /home/oracle/database/product/11.1.0/db_1/bin

 - Linking Oracle
rm -f /home/oracle/database/product/11.1.0/db_1/rdbms/lib/oracle
gcc  -o /home/oracle/database/product/11.1.0/db_1/rdbms/lib/oracle -L/home/oracl
e/database/product/11.1.0/db_1/rdbms/lib/ -L/home/oracle/database/product/11.1.0
/db_1/lib/ -L/home/oracle/database/product/11.1.0/db_1/lib/stubs/   -Wl,-E /home
/oracle/database/product/11.1.0/db_1/rdbms/lib/opimai.o /home/oracle/database/pr
oduct/11.1.0/db_1/rdbms/lib/ssoraed.o /home/oracle/database/product/11.1.0/db_1/
rdbms/lib/ttcsoi.o  -Wl,--whole-archive -lperfsrv11 -Wl,--no-whole-archive /home
/oracle/database/product/11.1.0/db_1/lib/nautab.o /home/oracle/database/product/
11.1.0/db_1/lib/naeet.o /home/oracle/database/product/11.1.0/db_1/lib/naect.o /h
ome/oracle/database/product/11.1.0/db_1/lib/naedhs.o /home/oracle/database/produ
ct/11.1.0/db_1/rdbms/lib/config.o  -lserver11 -lodm11 -lsage11 -lnnet11 -lskgxp1
1 -lsnls11 -lnls11  -lcore11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lxml11
-lcore11 -lunls11 -lsnls11 -lnls11 -lcore11 -lnls11 -lclient11  -lvsn11 -lcommon
11 -lgeneric11 -lknlopt `if /usr/bin/ar tv /home/oracle/database/product/11.1.0/
db_1/rdbms/lib/libknlopt.a | grep xsyeolap.o > /dev/null 2>&1 ; then echo "-lora
olap11" ; fi` -lslax11 -lpls11  -lrt -lplp11 -lserver11 -lclient11  -lvsn11 -lco
mmon11 -lgeneric11 `if [ -f /home/oracle/database/product/11.1.0/db_1/lib/libavs
erver11.a ] ; then echo "-lavserver11" ; else echo "-lavstub11"; fi` `if [ -f /h
ome/oracle/database/product/11.1.0/db_1/lib/libavclient11.a ] ; then echo "-lavc
lient11" ; fi` -lknlopt -lslax11 -lpls11  -lrt -lplp11 -ljavavm11 -lserver11  -l
wwg  `cat /home/oracle/database/product/11.1.0/db_1/lib/ldflags`    -lncrypt11 -
lnsgr11 -lnzjs11 -ln11 -lnl11 -lnro11 `cat /home/oracle/database/product/11.1.0/
db_1/lib/ldflags`    -lncrypt11 -lnsgr11 -lnzjs11 -ln11 -lnl11 -lnnz11 -lzt11 -l
ztkg11 -lmm -lsnls11 -lnls11  -lcore11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls1
1 -lxml11 -lcore11 -lunls11 -lsnls11 -lnls11 -lcore11 -lnls11 -lztkg11 `cat /hom
e/oracle/database/product/11.1.0/db_1/lib/ldflags`    -lncrypt11 -lnsgr11 -lnzjs
11 -ln11 -lnl11 -lnro11 `cat /home/oracle/database/product/11.1.0/db_1/lib/ldfla
gs`    -lncrypt11 -lnsgr11 -lnzjs11 -ln11 -lnl11 -lnnz11 -lzt11 -lztkg11   -lsnl
s11 -lnls11  -lcore11 -lsnls11 -lnls11 -lcore11 -lsnls11 -lnls11 -lxml11 -lcore1
1 -lunls11 -lsnls11 -lnls11 -lcore11 -lnls11 `if /usr/bin/ar tv /home/oracle/dat
abase/product/11.1.0/db_1/rdbms/lib/libknlopt.a | grep "kxmnsd.o" > /dev/null 2>
&1 ; then echo " " ; else echo "-lordsdo11"; fi` -L/home/oracle/database/product
/11.1.0/db_1/ctx/lib/ -lctxc11 -lctx11 -lzx11 -lgx11 -lctx11 -lzx11 -lgx11 -lord
imt11 -lclsra11 -ldbcfg11   -lhasgen11 -lcore11 -lskgxn2 -locr11 -locrb11 -locru
tl11 -lhasgen11 -lcore11 -lskgxn2   -loraz -lsnls11 -lnls11  -lcore11 -lsnls11 -
lnls11 -lcore11 -lsnls11 -lnls11 -lxml11 -lcore11 -lunls11 -lsnls11 -lnls11 -lco
re11 -lnls11 -lsnls11 -lunls11  -lsnls11 -lnls11  -lcore11 -lsnls11 -lnls11 -lco
re11 -lsnls11 -lnls11 -lxml11 -lcore11 -lunls11 -lsnls11 -lnls11 -lcore11 -lnls1
1 -laio    `cat /home/oracle/database/product/11.1.0/db_1/lib/sysliblist` -Wl,-r
path,/home/oracle/database/product/11.1.0/db_1/lib -lm    `cat /home/oracle/data
base/product/11.1.0/db_1/lib/sysliblist` -ldl -lm   -L/home/oracle/database/prod
uct/11.1.0/db_1/lib
test ! -f /home/oracle/database/product/11.1.0/db_1/bin/oracle ||\
           mv -f /home/oracle/database/product/11.1.0/db_1/bin/oracle /home/oracle/databas
e/product/11.1.0/db_1/bin/oracleO
mv /home/oracle/database/product/11.1.0/db_1/rdbms/lib/oracle /home/oracle/database/produc
t/11.1.0/db_1/bin/oracle
chmod 6751 /home/oracle/database/product/11.1.0/db_1/bin/oracle

오라클의 관리자 계정인 system 계정의 기본 패스워드는 'manager' 입니다.

통상 오라클 9i 이상부터는 DBA가 DB를 관리하기 위하여 svrmgrl 을 사용하지 않고

sqlplus "/ as sysdba" 로 접속하게 되어 있습니다.

Linux에서 오라클 삭제하기

1. $ORACLE_HOME 디렉토리에 있는 설치 화일을 전부 삭제.
2. /etc 디렉토리에 있는 oraInst.loc, oratab 파일을 삭제.
3. /usr/local/bin/oraenv 파일을 삭제.
4. /tmp 디렉토리에서 관련된 파일을 삭제.
5. oracle 설치시 생성한 계정의 환경설정 파일(.bash_profile)을 다른 위치에 복사.
6. oracle 설치시 생성한 계정 삭제.
7. oracle 설치시 생성한 계정의 HOME 디렉토리 삭제
8. 끝입니다. 다시 설치하시면 됩니다.

문서는
http://www.oracle.com/technology/pub/articles/smiley_rac10g_install.html
http://www.oracle-base.com/articles/10g/OracleAS10gInstallationOnFedora2.php
참조.

시스템 환경 점검
2.6.9-11 이상의 커널이 필요하다.
# uname -r

필요한 패키지 버전(그 이상도 당연히 가능) -> 대부분 설치되어 있다.
binutils-2.15.92.0.2-10
compat-db-4.1.25-9
control-center-2.8.0-12
gcc-3.4.3-9
gcc-c++-3.4.3-9
glibc-2.3.4-2
glibc-common-2.3.4-2
gnome-libs-1.4.1.2.90-44.1
libstdc++-3.4.3-9
libstdc++-devel-3.4.3-9
make-3.80-5
pdksh-5.2.14-30
sysstat-5.0.5-1
xscreensaver-4.18-5

시스템 요구사항 검증
# grep MemTotal /proc/meminfo
MemTotal :    xxxxxx KB
# grep SwapTotal /proc/meminfo
SwamTotal : xxxxx KB

계정 생성
# groupadd oinstall
# groupadd dba
# useradd -m -g oinstall -G dba oracle
# passwd oracle

디렉토리 생성
# mkdir /oracle
# chown -R oracle.dba /oracle
# chmod -R 755 /oracle

hosts 파일
/etc/hosts 파일이 제대로 설정되어 있는지 확인.
# cat /etc/hosts
<IP-address> <fully-qualified-machine-name> <machine-name>

커널 파라미터 설정
 Oracle 11g? 가 요구하는 커널 매개변수 설정이다. 아래의 수치는 최소값이며 /etc/sysctl.conf에 적혀있는 값이
아래의 값보다 높을 경우에는 변경하지 않아도 된다. 물론 낮을 경우에는 /etc/sysctl.conf 에 추가해준다.

# sysctl -a | grep ... 으로 확인할 수 있다.

#kernel.shmall = 2097152
#kernel.shmmax = 2147483648
#kernel.shmmni = 142
# semaphores: semmsl, semmns, semopm, semmni
#kernel.sem = 250 32000 100 128
#fs.file-max = 131072
net.ipv4.ip_local_port_range = 1024 65000
kernel.msgmni = 2878
#kernel.msgmax = 8192
#kernel.msgmnb = 65535


(#처리는 서버에서 해당값보다 크거나 같은 경우이다. 적다면 주석 풀고 붙여넣는다.)

변경이 완료되면

# /sbin/sysctl -p 로 변경된 설정을 적용한다.


oracle 사용자 계정의 shell limit 설정
Linux 계정 별로 실행되는 프로세스와 열린 파일 수를 제한한다. 이를 위해 /etc/security/limits.conf 를 편집한다.
아래에 추가하자. (간격은 tab으로 조정하던지.. 알아서 )
#<domain>      <type>  <item>         <value>
    oracle            soft     nproc            2047
    oracle            hard    nproc            16384
    oracle            soft     nofile             1024
    oracle            hard    nofile             65536

그리고 /etc/pam.d/login 에 다음을 추가하자.
session    required    /lib/security/pam_limits.so


oracle 계정을 위한 환경변수
DB 서버에서 설정해야하는 환경변수는 다음과 같다.

ORACLE_BASE
ORACLE_HOME
ORACLE_SID
PATH

위의 변수를 추가하기 위해서 oracle 계정의 .bash_profile에 다음을 추가한다.

ORACLE_BASE=/oracle; export ORACLE_BASE
ORACLE_HOME=/oracle/11g; export ORACLE_HOME
ORACLE_SID=orcl; export ORACLE_SID
PATH=$PATH:$ORACLE_HOME/bin

오라클 배포판 다운받기
배포판을 다운받아서 특정 디렉토리에 압축을 풀어놓는다. 물론 디렉토리는 oracle 계정의 소유여야한다.
루트로 작업하고 나중에 chown을 사용해도 상관없다.

# unzip linux.x64_11gR1_database.zip    <물론 zip파일의 이름은 다를 수도 있다 -_->
# chown -R oracle.oinstall ./database

설치 전에..
oracle 계정으로 로그인 해서  설치 파일들을 풀어놓은 디렉토리에서 runInstaller를 실행하기 전에..
# xhost +
(+까지 쳐야한다. 이걸 해줘야 루트로 로그인 한 X윈도에서 터미널로 su - oracle을 이용해서
  oracle 계정을 사용 xwindow 창을 띄울 수 있다. 궁금하다면 man xhost 를 참고할 것)

예전에는 /etc/redhat-release를 수정해주곤 했는데 안해줘도 잘 나온다.

oracle 11g도 한글이 다 깨져서 나온다. runInstaller 전에 다음을 실행한다.
# export LANG=C
그리고 나서 runInstaller를 실행하면 깨지지 않고 나올 것이다. 물론 영어로 -_-;

이제 runInstaller를 실행해보자.

Base Location
Home Location 을 profile과 동일하게 맞춰주고..
Global Database Name 도 SID 와 맞춰준다.
Advanced Installation으로 들어가면 이것저것 만질 수 있는게 많다. 귀찮으므로 패스.

자.. 이제 다음 화면이다.

Inventory Directory와 Group Name을 지정하는데 Inventory는 적당한 곳에 위치시키고..
group name도 dba로 설정해준다.

이제는 설치전 요구사항에 대해서 검사를 하는데.

Warning도 뜨고.. not execute(Network 설정)도 뜬다. 그냥 User Verify 로 선택하고 넘어가자.

11g에서는 다음 화면이 추가로 생겼다. 환경설정 관리자 등록 화면인데.. 등록하면 뭔가 귀찮으니까 -_- 패스

자 이제 Summary 를 볼 수 있다.

Install 버튼을 눌러서 계속 진행한다.

와우. 별일 없이 쭉 넘어갔다. 8i 시절 부터 10g까지 리눅스에 설치시 끈질기게 괴롭히던 Link Error가 사라졌다.
다음은 패스워드 설정이다. 11g 에서는 sys / system / dbsnmp / sysman 을 제외한 모든 계정이 잠겨있다.
여기서 풀어줄 수 있다. scott 정도는 풀어주자.

scott 을 추가해준다.

항상 해오던 루트로 실행해줄 스크립트다. 터미널을 하나 열어서 적혀있는 스크립트를 루트권한으로 실행해준다.

설치가 완료 되었다.

오라클 자동 시작/종료 설정
# vi /etc/oratab
orcl:/oracle/11g:N   <- N을 Y로 수정한다.
orcl:/oracle/11g:Y



에러처리
다음과 같은 에러가 날 것이다.

error while loading shared libraries libnnz11.so: cannot restore segment prot after reloc Permission denied

뭔가 퍼미션이 없다는 얘긴데.. 이건 SELinux를 disable 시켜주면 된다. SELinux disble 시키는 방법은

/etc/selinux/config 파일을 잘 읽어보고 고치면 된다. (모르면 구글에 검색)

또 이런 에러가 날 수도 있다.

$ ./lsnrctl start
 
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 18-FEB-2008 19:14:37
 
Copyright (c) 1991, 2007, Oracle.  All rights reserved.
 
Message 1070 not found; No message file for product=network, facility=TNSTNS-12545: Message 12545 not found; No message file for product=network, facility=TNS
 TNS-12560: Message 12560 not found; No message file for product=network, facility=TNS
  TNS-00515: Message 515 not found; No message file for product=network, facility=TNS
   Linux Error: 2: No such file or directory

이런 경우는 포트가 열려있지 않은 경우니까.. 방화벽에서 1521번 포트를 열어주자.

오라클 실행과 종료
oracle 계정에서
$ lsnrctl start   <리스너 스타트>

리스너 시작 후에..

$ sqlplus /nolog
sqlplus> connect orcl as sysdba
...
sqlplus> startup

서비스 스크립트 작성

# vi /etc/init.d/oracle 
다음의 내용을 파일에 쓴다.

----------------------------------------------------------------------
#!/bin/bash
ORA_HOME="/oracle/11g/"
ORA_OWNER="oracle"
 
if [ ! -f $ORA_HOME/bin/dbstart -o ! -d $ORA_HOME ]
then
        echo "Oracle Startup: failed"
        exit 1
fi
 
case "$1" in
start)
        echo -n "Oracle Start: "
        su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start"
        su - $ORA_OWNER -c $ORA_HOME/bin/dbstart
        touch /var/lock/subsys/oracle
        echo "OK"
        ;;
stop)
        echo -n "ORACLE Shutdown: "
        su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl stop"
        su - $ORA_OWNER -c $ORA_HOME/bin/dbshut
        rm -f /var/lock/subsys/oracle
        echo "OK"
        ;;
restart)
        $0 stop
        $0 start
        ;;
*)
        echo "Usage: $0 start|stop|restart"
        exit 1
esac
exit 0

----------------------------------------------------------------------

사용은 /etc/rc.d/init.d/oracle start | stop | restart ~

*설치전 사전 작업*

1.필수 패키지 설치 및 기본 쉘(bash) 심볼릭 링크 설정.

2.오라클 유저 및 그룹 추가.

3.심볼릭 링크 설정.

4.커널 변수 및 시스템 설정.

5.오라클 환경변수 설정.

6.레드햇 버전 추가.


*설치*

1.시스템 재부팅 후 oracle 유저로 접속.

2.오라클 11g 다운로드 및 압축 해제.

3.인스톨러 실행.

※인스톨러가 구동중 display에러 발생할 경우.
1.DISPLAY 환경변수 확인.

2.확인시 DISPLAY 값이 없을 경우 DISPLAY 환경변수 설정.

※에러화면(디렉토리 및 권한 불충분 에러) : 그냥 OK클릭 후 다음 단계 진행


우분투 오라클 설치 관련 글 : http://kekedie.tistory.com/4

페도라6, 페도라8에서 성공하였습니다..
기본적으로 오라클 홈페이지에 있는 설치 방법을 기반으로 성공하였습니다..

http://www.oracle.com/technology/global/kr/pub/articles/smiley_10gdb_install.html

인터넷에 올라온 경험담들이 다 비슷비슷하지만...필요없는 부분들도 상당히 많았네요(고생한이유;;).

그럼 시작해 보겠습니다.

 

1. 커널 버전의 요구사항을 확인한다.

Oracle Database 10g의 커널 버전 요구사항은 2.6.9-5.Elsmp 사용자는 이것과 동일하거나 이후의 버전이어야 합니다.

#uname -r //명령어로 확인

2. 페도라의 패키지 적용상태를 확인한다.

기본적으로 패키지들은 설치가 되어있지만 저같은 경우 몇개가 없어 설치를 하였습니다.

#rpm -q gcc make binutils setarch compat-db compat-libgcc-296  compat-libstdc++-296 \

compat-libstdc++-33 glibc glibc-common glibc-devel glibc-headers ksh libaio libaio-devel \

libgcc libgcc++ libstdc++-devel openmotif21 libXp // 확인가능하다.

저는 위에서 3갠가 4개정도만 추가로 설치하였는데 openmotif21패키지는 #yum install명령어로 설치가 안됩니다.

http://www.superuser.co.kr/home/search/?select=rpmView&no=14559 // 리눅스포털사이트

에 가셔서 openmotif21-2.1.30-14.i386.rpm으로 컴퓨터환경에 맞는 패키지를 다운 받으시고 설치하세요.(libXp도같이깔리는거같았음..아마도..)

ex)페도라8에서는 setarch, libgcc++이 안깔려요..

3. 시스템 요구사항 확인

최소 메모리 요구사양 512MB, swap 공간의 최소 요구사항 1GB..

이건 거의다 통과할꺼라 생각됨...컴퓨터들이 좋으니..저도 별로 바꾼게 없다는..

4. 오라클 그룹 및 사용자 계정 생성

오라클은 설치하기 위한 사용자 계정을 따로 만들어 두어야 합니다.

#groupadd dba // 그룹생성

#useradd -g dba oracle // 사용자 계정

#passwd oracle // 비번 설정

#id oracle // 확인..

5. Linux커널 매개변수의 설정

커널 매개변수를 변경해 주어야 하는데 시스템이 아래 명시된 것보다 높다면 변경하지 않아도 된다고

했지만..저는 변경을 했습니다..

#vi /etc/sysctl.conf // 를 열어 맨 아래에 다음을 입력합니다.

kernel.shmall = 2097152

kernel.shmmax = 2147483648

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

fs.file-max = 65536

net.ipv4.ip_local_port_range = 1024 65000

6. oracle 사용자 계정의 Shell Limit 설정

오라클은 리눅스 계정 별로 실행되는 프로세스와 열린 파일의 수를 제한한데요...

#vi /etc/security/limits.conf // 열고 맨아래에 입력

oracle    soft    nproc    2047

oracle    hard   nproc    16384

oracle    soft    nofile     1024

oracle    hard   nofile     65536

7. oracle 계정을 위한 환경변수

설정해야되는 환경변수에는 ORACLE_BASE, ORACLE_HOME, ORACLE_SID, PATH임

오라클 계정으로 접속한후에 위에있는 환경변수들을 입력해줍니다.

#su oracle

#vi .bash_profile // 열고 맨 아래에 입력

ORACLE_BASE=/home/oracle; export ORACLE_BASE

ORACLE_HOME=$ORACLE_BASE/product/10.1.0/Db_1; export ORACLE_HOME

ORACLE_SID=ORCL; export ORACLE_SID                    // 데이터베이스이름인건알죠?

PATH=$PATH:$ORACLE_HOME/bin; export PATH

저는 환경변수를 오라클 설치한 후에 설치한 경로를 확인해서 입력했어요. (추천..)

8. 운영체제의 버전 검증

오라클 데이터베이스 10는 10.1.0.3의 Installer는 RHEL4가 지원 가능한 버전임을 인식하지 못합니다.

#vi /etc/redhat-release // 열고 변경한다

Red Hat Enterprise Linux AS release 3 (Taroon)

9. 오라클의 설치

이제 설치를 시작할껀데요..오라클 계정으로 접속한담에 오라클10g를 다운받아야합니다.

http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/linuxsoft.html

위에 오라클 홈피에서 ship.db.cpio.gz를 설치할 폴더에 다운받습니다. 저는 /home/oracle에 바로 다운받았답니다.

#su oracle // 오라클 계정으로 접속합니다. root에서 다운받고 알맞은 폴더로 복사해도되요~

#gunzip ship.db.cpio.gz // 압축품 그럼 ship.db.cpio로 풀림

#cpio -idmv < ship.db.cpio // 또 압축품...그럼 Disk1이란 폴더가 생김

#cd Disk1 // 이동하구

#./runInstaller // 오라클 설치를 시작합니다..

ex) 페도라8에서는 추가적으로 자바어쩌구 에러가 한개나올지도 모르는데요..

그럴때는 페도라 패치를 모두 깔아주셔야 된데요~

여기에서 실행이 안되면 아마 호스트 문제일껍니다.. root로 가셔셔 xhost +한번해주세요~

그런데 오라클 설치화면에서 글씨가 깨져서 보일껍니다...

#export LANG=C // 깨진글씨가 잘보입니다.

자 그럼 설치화면이 잘될겁니다~ 설치방법은 패스~ 설치 중간에 orainstRoot.sh 스크립트를 root로 실행하라고 창이하나 뜰겁니다..무시하지말고 새로운 터미널하나 열어서 root로 실행한담에 넘어가시구요. 설치마지막에도 root.sh를 root로 하라고 창이또뜹니다..그럼 다시 해주시고...워링이나 에러나 창뜨는것들 무시하지 마시고 잘읽어보심 방법을 알겁니다..

sqlplus 사용하려는데 shared_pool_size관련 에러가 생긴다면 에러메시지를 확인하여

요구하는 shared_pool_size를 찾아 오라클이 깔린 디렉토리로 이동하면 dbs라는 폴더가 있습니다.

그폴더에 initORCL.ora파일을 열어서 shared_pool_size를 변경시키면 잘될겁니다~

oracle9i에 bissa_back이라는 user가 없어서 발생하는 문제입니다.
import 하시기 전에
user를 생성하시고 해당 user에 대한 필요한 Role을 주시고
특정 tablespace에 table을 생성하실려면 Quota을 지정하셔야 겠죠.

----------------------------------------------------
안녕하세요...
전 윈도우에 9i를 설치해서 하고 있습니다..
그런데, 8i에서 엑스포트한 파일을 9i에서 임포트할려고 하는데 되지 않네요..
9i에서는 사용자, 사용자 권한, 테이블 스페이스만 만들었고요..
임포트 실행하면 이런 메세지가 나옵니다..

실행명 :>
C:\>imp userid=system/manager file=d:\oracle\test.dmp fro
muser=bissa touser=bissa_back;

. BISSA 객체를 BISSA_BACK;(으)로 임포트하는 중입니다.
"ALTER SESSION SET CURRENT_SCHEMA= "BISSA_BACK;""
IMP-00003 : ORACLE 오류 1435 가 발생했습니다..
ORA-01435 : 사용자가 존재하지 않습니다.
IMP-00000 : 임포트가 실패로 끝났습니다.

오라클개잘바튜닝가이드

/ $Header: impus.msg 22-aug-2003.14:20:48 bmccarth Exp $ impmtb.msg
/
/ Copyright (c) 1988, 2000 by the Oracle Corporation.  All rights reserved.
/
/ File: v6$knl:[impexp]impmtb.msg
/ Created: 07/12/88
/
/ This file is converted to header/message files using lmsgen.c
/
/ The first column is the Import error number.
/ The second column is reserved and must be (for now) 00000
/ The remainder of the line is the error text
/
/ Adding an error for Import
/    Check out this file, add the error, and check it back in. Error numbers
/    should always be ordered.  The second column should always be 00000.
/
/
/ Range 000 - 099: actual Import errors
/ Range 100 - 199: informative messages
/ Range 200 - 299: prompt messages
/ Range 300 - 399: help messages
/ Range 400 - 499: actual Import errors (exhausted 000 - 099)
/
/ Error messages
/
/
00000, 00000, "Import terminated unsuccessfully\n"
// *Cause:  Import encountered an Oracle error.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual, and take appropriate action.
00001, 00000, "respond with either %s, %s, RETURN or '.' to quit"
// *Cause:  An invalid response was entered.
// *Action: Enter any of the responses shown in the message.
00002, 00000, "failed to open %s for read"
// *Cause:  Import failed to open the export file for reading. This message is
//          usually followed by a device message from the operating system.
// *Action: Take appropriate action to restore the device.
00003, 00000, "ORACLE error %lu encountered"
// *Cause:  Import encountered the referenced Oracle error.
// *Action: Look up the Oracle message in the ORA message chapters of this
//          manual, and take appropriate action.
00004, 00000, "invalid username or password\n"
// *Cause:  An invalid username or password was specified.
// *Action: Retry with a valid username and password.
00005, 00000, "all allowable logon attempts failed"
// *Cause:  An attempt was repeatedly made to log on with an invalid
//          username or password.
// *Action: Retry with valid username and password.
00006, 00000, "failed to allocate memory of size %lu"
// *Cause:  Import failed to allocate the necessary memory.
// *Action: Decrease the import buffer size so that less memory is required,
//          or increase the runtime memory size for Import.
00007, 00000, "must be a DBA to import objects to another user's account"
// *Cause:  The privileges needed to import into another user's account do not
//          exist. Only a database administrator can import into another
//          user's account.
// *Action: Ask the database administrator to do the import.
00008, 00000, "unrecognized statement in the export file: \n  %s"
// *Cause:  Import did not recognize a statement in the export file. Either
//          the export file was corrupted, or an Import internal error has
//          occurred.
// *Action: If the export file was corrupted, retry with a new export file.
//          Otherwise, report this as an Import internal error and submit
//          the export file to customer support.
00009, 00000, "abnormal end of export file"
// *Cause:  The export file is probably from an aborted Export session.
// *Action: If so, retry the export and import. Otherwise, report this as an
//          Import bug and submit the export file that caused this error to
//          customer support.
00010, 00000, "not a valid export file, header failed verification"
// *Cause:  Either the file was not generated by Export or it was corrupted.
// *Action: If the file was indeed generated by Export, report this an
//          Import bug and submit the export file to customer support.
00011, 00000, "formatted table data not currently supported"
// *Cause:  You tried to import an export file that contains formatted table
//          data. Import only supports export files containing binary table
//          data.  wher
// *Action: Retry using an export file that contains only binary table data.
00012, 00000, "invalid export mode (%c) in header"
// *Cause:  The Export mode specified in the export file header is invalid.
// *Action: Check the export file to see if it was corrupted. If it was not,
//          report this as an Import bug and submit the export file to
//          customer support.
00013, 00000, "only a DBA can import a file exported by another DBA"
// *Cause:  The privileges needed to Import an export file generated by a
//          database administrator do not exist. Only a database administrator
//          can import such files.
// *Action: Ask the database administrator to do the import.
00014, 00000, "option \"%s\" is needed, but not present in database"
// *Cause:  The command entered requires the specified option.  Either that
//     option is not installed, or the row describing the option is
//     missing from table V$OPTION
// *Action: Reinstall Oracle with the option specified by the message.
00015, 00000, "following statement failed because the object already exists:"
// *Cause:  Import failed to create an object because it already exists.
// *Action: Specify IGNORE=Y to ignore such errors and import rows even when
//          tables are not created because they already exist.
00016, 00000, "required character set conversion (type %lu to %lu) not supported"
// *Cause:  Import could not convert the character format of the export file
//          into the native character format.
// *Action: Change the user character set by setting the NLS_LANG
//          environment variable to match the character set of the export file.
00017, 00000, "following statement failed with ORACLE error %lu:"
// *Cause:  Import failed to execute the statement from the export file
//          because of an Oracle error.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual and take appropriate action.
00018, 00000, "partial import of previous table completed: %lu rows imported"
// *Cause:  A table was only partially imported because of an Oracle error.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual and take appropriate action.
00019, 00000, "row rejected due to ORACLE error %lu"
// *Cause:  Import encountered the referenced Oracle error while trying to
//          import a row.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual and take appropriate action.
00020, 00000, "long column too large for column buffer size (%lu)"
// *Cause:  The column buffer is too small. This usually occurs when importing
//          LONG data.
// *Action: Increase the insert buffer size 10,000 bytes at a time (for
//          example). Use this step-by-step approach
//          because a buffer size that is too large may cause a similar
//          problem. 
00021, 00000, "INCTYPE parameter is obsolete"
// *Cause:  Import encountered the INCTYPE parameter when parsing Import
//          options.  Incremental Imports are no longer supported.
// *Action: Consult the Oracle Backup and Recovery guide. 
//          Import will attempt to continue.
00022, 00000, "failed to process parameters, type 'IMP HELP=Y' for help"
// *Cause:  Invalid command-line parameters were specified.
// *Action: Check the online help screen for the set of valid parameters, then
//          retry.
00023, 00000, "Import views not installed, please notify your DBA"
// *Cause:  The necessary Import views were not installed.
// *Action: Ask your database administrator to install the required Import
//          views.
00024, 00000, "Only one mode (TABLES, FROMUSER, or FULL) can be specified"
// *Cause:  Parameters were specified that conflict with the import
//          specification FULL=Y.
// *Action: Retry, making sure not to specify FULL=Y.
00025, 00000, "for DBA export files, FROMUSER must be specified with TOUSER option"
// *Cause:  When importing a database administrator export file, you specified
//          the TOUSER parameter but not the FROMUSER parameter.
// *Action: Specify the FROMUSER parameter so that Import knows which user's
//          objects to import.
00027, 00000, "failed to rollback partial import of previous table"
// *Cause: Import encountered an Oracle error while trying to roll back a
//          partial import.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual and take appropriate action. Then, log
//          on to Oracle and check that the partial import was not committed.
00028, 00000, "partial import of previous table rolled back: %lu rows rolled back"
// *Cause:  Import encountered an Oracle error while trying to import a table.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual and take appropriate action. Then, if
//          necessary, re-import the table.
//         
00029, 00000, "cannot qualify table name by owner (%s), use FROMUSER parameter"
// *Cause:  A table name was qualified with the name of its owner, as shown in
//          the following example. This is not allowed. 
//            IMP SYSTEM/MANAGER TABLES=(SCOTT.EMP)
// *Action: Use the FROMUSER parameter to specify the table's owner, as
//          shown in the following example:  
//            IMP SYSTEM/MANAGER FROMUSER=SCOTT TABLES=(EMP, DEPT)
// 
00030, 00000, "failed to create file %s for write"
// *Cause:  Import was unable to create the specified file with write enabled.
// *Action: Check the file name and file system for the source of the error.
//
// 
00031, 00000, "Must specify FULL=Y or provide FROMUSER/TOUSER or TABLES arguments"
// *Cause: The database administrator did not specify full or partial import.
// *Action: The database administrator must specify FROMUSER/TOUSER or table
//          arguments if not a full import.
00032, 00000, "SQL statement exceeded buffer length"
// *Cause:  The buffer was too small for the SQL statement being read.
// *Action: Rerun with a larger buffer. This can also be an indication of a
//          corruption in the import datafile.
00033, 00000, "Warning: Table \"%s\" not found in export file"
// *Cause:  A table name was specified that does not exist in export file.
// *Action: Correct the table specification.
//
00034, 00000, "Warning: FromUser \"%s\" not found in export file"
// *Cause:  The user specified a FROMUSER name that does not exist in export
//          file.
// *Action: Correct the FROMUSER specification.
00035, 00000, "input file %s must be on a disk"
// *Cause:  On some platforms, import can read files from tape.  This message
//     is displayed if the first file in an export file set was on disk
//     and you specified a tape device for a second or subsequent file.
// *Action: Verify that you have specified the correct file name for the import
//     file.  Remember that all input files can be either on disk or all
//     files can be on tape, but not mixed both tape and disk.
00036, 00000, "Could not find environment character set"
// *Cause:  An environment character set was specified that was not recognized
//          by the Import utility.
// *Action: Ensure that the spelling of the character set specified in the
//          command line parameter CHARSET (for Release 6 only)
//          or the environment variable NLS_LANG is correct.
00037, 00000, "Character set marker unknown"
// *Cause:  The export file is corrupted.
// *Action: Try to obtain an uncorrupted version of the export file.
//          If the export file is not corrupted, report this as an Import
//          internal error and submit the export file to customer support.
00038, 00000, "Could not convert to environment character set's handle"
// *Cause:  Internal error.
// *Action: Contact Worldwide Support.
#ifdef EXU_VOLSIZE
00039, 00000, "VOLSIZE does not match the value used for export: %s"
// *Cause:  The value specified for VOLSIZE does not match the value specified
//        during the creation of the export file.
// *Action: If you believe that the specified VOLSIZE value is correct, verify
//   that you specified the correct file for import.  If you specified
//        the correct file but are unsure about the correct value,
//        re-execute the import command but specify VOLSIZE=0.
#endif
00040, 00000, "FILESIZE does not match the value used for export: %s"
// *Cause:  The value specified for FILESIZE does not match the value specified
//        during the creation of the export file.
// *Action: If you believe the specified FILESIZE value is correct, verify
//   that you specified the correct file for import.  If you specified
//        the correct file but are unsure about the correct value,
//        re-execute the import command but specify FILESIZE=0.
00041, 00000, "Warning: object created with compilation warnings"
// *Cause:  The object in the SQL statement following this error was created
//          with compilation errors. If this error occurred for a view, it
//          is possible that the base table of the view was missing.
// *Action: This is a warning. The object may have to be recompiled before
//          being used.
00042, 00000, "CHARSET used, but the export file has specific character set"
// *Cause:  The user requested that a specific character set be used to
//          process an export file that has a specific embedded character
//          set ID. The ID in the export file is accurate and should be used.
// *Action: Remove the CHARSET keyword from the command line.
00043, 00000, "export file character set inconsistent"
// *Cause:  The character set of the export file and the environment character
//          set (or the character set specified with the CHARSET keyword)
//          are inconsistent. One character set is ASCII-based while the other
//          is EBCDIC based.
// *Action: Specify the correct character set with the CHARSET keyword.
00044, 00000, "unable to allocate enough memory for statement"
// *Cause:  Import was unable to allocate sufficient memory to read in the
// specified statement and execute it.
// *Action: Increase the allocation for database buffers, restart the
//          instance, and reexecute the Import command.
#ifdef EXU_VOLSIZE
00045, 00000, "using VOLSIZE value from export file of %s"
// *Cause:  Either you did not specify the VOLSIZE parameter in your
//          IMPORT command, or you specified VOLSIZE=0 and the export was
//          created with a non-zero value for VOLSIZE. Import will use the
//     value specified in the export file.
// *Action: None required.
#endif
00046, 00000, "using FILESIZE value from export file of %s"
// *Cause:  Either you did not specify the FILESIZE parameter in your
//          IMPORT command, or you specified FILESIZE=0 and the export file
//     was created with a non-zero value for FILESIZE. Import will use
//     the value specified in the export file.
// *Action: None required.
00047, 00000, "unexpected file sequence number; expected %u but found %u"
// *Cause:  The header in the export file contains a sequence number that
//        is used to track the order in which multiple export files
//        are written.  The first export file is assigned sequence number 
//        one, the second file is assigned sequence number two and so on.
//        This message is displayed when a number other than the expected 
//        sequence number is found in the file header
// *Action: Execute the import command again, but specify the files in the 
//        order in which Export wrote them.
00048, 00000, "mismatched file header"
// *Cause:  During verification of the 2nd or subsequent file in a multi-file export,
//        Import found header fields in the file that did not match
//        values in the first file.
// *Action: Check the names of the files created by Export and verify that
//        you specified them correctly for the import operation.
00049, 00000, "Unknown language specified in CHARSET"
// *Cause:  An unknown language was listed in the CHARSET option. 
// *Action: Use a known character set.
00050, 00000, "Dump file and log file cannot be identical"
// *Cause:  Identical names were given to the dump file and log file.
// *Action: Specify different names for the dump file and log file and retry
//          the operation.
00051, 00000, "Direct path exported dump file contains illegal column length"
// *Cause:  An invalid column length was encountered while processing column
//          pieces."
// *Action: Check to make sure the export file is not corrupted, or else
//          report this to Oracle Worldwide Support as an Import/Export
//          internal bug and submit the
//          export file.
00052, 00000, "Warning: Unable to set event for freelist communication with server"
// *Cause:  An event could not be set for current the session.
// *Action: If Import fails, give the Import user ALTER SESSION PRIV and retry
//          the operation.
00053, 00000, "Import mode incompatible with Export dump file"
// *Cause:  The specified import option is incompatible with point-in-time-
//          recovery dump file.
// *Action: Generate a proper dump file or use point-in-time-recovery import
//          mode.
00054, 00000, "must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import"
// *Cause:  The user must log in 'as SYSDBA' to perform transportable
//          tablespace imports or Point-In-Time Recovery imports.
// *Action: Ask your database adminstrator to perform the Transportable
//          Tablespace import or the Tablespace Point-in-time Recovery import.
00055, 00000, "Warning: partition or subpartition \"%s\":\"%s\" not found in export file"
// *Cause:  A partition or subpartition name was specified that does not exist in
//          export file.
// *Action: Check to make sure the partition or subpartition name belongs to the table.
#ifdef EXU_VOLSIZE
00056, 0000, "multiple devices specified for tape input"
// *Cause:  You specified multiple file names when doing an import from a tape
//     device.  Import uses the same device for reading all tapes,
//     regardless of the number of tape volumes required.  For this
//     reason, export will accept only one value for the FILE parameter
//     when writing to tape.
// *Action: Reenter the IMPORT command, but specify only one tape device in
//     the FILE parameter.
#endif
00057, 00000, "Warning: Dump file may not contain data of all partitions of this table"
// *Cause:  The dump file used for this Table Import might not contain all
//          of the data belonging to the exported table.
// *Action: Check to see if the export was done as intended, or try performing
//          a Partition Import.
/ do NOT translate or document message 58 - it is never displayed
// NLS_DO_NOT_TRANSLATE [58,58]
00058, 00000, "placeholder for OCI error "
// *Document: NO
// *Cause:  filler
// *Action: filler
00059, 00000, "Failure to initialize parameter manager"
// *Cause:  Parameter manager failed in initialization.
// *Action: Report this to Oracle Worldwide Support as an Import internal bug.
00060, 00000, "Warning: Skipping table \"%s\".\"%s\" because object type \"%s\".\"%s\"  does not exist or has different identifier"
// *Cause:  An object type needed by the table, either does not exist on the
// *        target system or, if it does exist, it has a different object
//          identifier.
// *Action: Create the object type on the target system with a valid
// *        identifier.
00061, 00000, "Warning: Object type \"%s\".\"%s\" already exists with a different identifier"
// *Cause:  An object type cannot be created because it already exists on the
// *        target system, but with a different identifier
// *Action: Drop the object type from the target system and retry the
//          operation.
00062, 00000, "Warning: The identifier on the dump file for object type \"%s\".\"%s\" is invalid"
// *Cause:  The character string representing the object type's identifier
// *        could not be converted to an object identifier.
// *Action: Internal error.
00063, 00000, "Warning: Skipping table \"%s\".\"%s\" because object type \"%s\".\"%s\" cannot be created or has different identifier"
// *Cause:  An error occurred creating an object type that is used by the
// *        table.
// *Action: Examine the import log to determine why the object type could not
// *        be created.  If the object type already existed, with a
// *        different object identifier, then drop the object type and
// *        retry the import.
00064, 00000, "Definition of LOB was truncated by export"
// *Cause:  While producing the dump file, Export was unable to write the
// *     entire contents of a LOB.  Import is therefore unable to
// *        reconstruct the contents of the LOB. The remainder of the
// *     import of the current table will be skipped.
// *Action: Delete the offending row in the exported database and retry the
// *     export.
00065, 00000, "Import is unable to recreate lobs within objects."
// *Cause:  An error occurred recreating a LOB within an imported object.
// *Action: Report this to Oracle Worldwide Support as an Import internal
//          error.
00066, 00000, "Missing NLS_CHARACTERSET  in props$"
// *Cause:  No value for NLS_CHARACTERSET  in props$.
// *Action: Contact Worldwide support.
00067, 00000, "Could not convert to server character set's handle"
// *Cause:  Internal error.
// *Action: Contact Worldwide support.
00068, 00000, "Could not find environment national character set"
// *Cause:  An environment national character set was specified that was
//          not recognized by the Import utility.
// *Action: Ensure that the spelling of the national character set
//          specified in the environment variable NLS_NCHAR is correct.
00069, 00000, "Could not convert to environment national character set's handle"
// *Cause:  Internal error..
// *Action: Contact Worldwide support.
00070, 00000, "Lob definitions in dump file are inconsistent with database."
// *Cause:  The number of LOBS per row in the dump file is different than the
// *     number of LOBS per row in the table being populated.
// *Action: Modify the table being imported so that it matches the column
// *        attribute layout of the table that was exported.
00071, 00000, "Object identifier of imported table mismatches object identifier of existing table"
// *Cause:  An attempt was made to import data into a table that was recreated
//          under a different object identifier than the object identifier
//          used for the exported object table. 
//          Under this situation, REF's to this table that are contained
//          within the dump file will also be invalid.
// *Action: Drop the offending object table prior to import.
00072, 00000, "Warning: The object table's object identifier is invalid."
// *Cause:  The character string representing the table's object identifier
//          could not be converted to an internal object identifier.
// *Action: Internal error.
00073, 00000, "FILE locator \"%.*s\" \"%.*s\" is truncated to \"%.*s\" \"%.*s\" in server character set"
// *Cause:  The conversion of the specified directory and name strings for
//     a file attribute or column from the export server's
//          character set into the import server's character set
//          exceeded the maximum string lengths allowed within
//          FILE descriptors. The strings will be truncated to
//          the maximum supported lengths.
// *Action: Rename the directory aliases and external filenames to match the
//          truncated names in the specified FILE column or attribute.
00074, 00000, "The constraints flagged by ALL_CONSTRAINTS.BAD will break in 2000 A.D."
// *Cause:  Constraints exist in the data base that specify date
//          values without fully specifying the year.  These constraints
//          could break in the year 2000 A.D.
// *Action: Query ALL_CONSTRAINTS and correct those constraints marked as
//          bad.
00075, 00000, "Warning: The nested table may contain partial rows or duplicate rows"
// *Cause:  An error occurred inserting data into an outer or inner nested
//          table.  If the error occurred in the outer table, rows are
//          still inserted into the inner tables.  If the error occurred in
//          an inner table, data is still inserted into the outer table and
//          other inner tables.  This can result in duplicate inner table
//          rows or partial logical rows.
// *Action: Examine the data in the tables.  Delete the incorrect rows or
//          drop the entire table and perform the import again.
00076, 00000, "Missing NLS_NCHAR_CHARACTERSET  in props$"
// *Cause:  No value for NLS_NCHAR_CHARACTERSET  in props$.
// *Action: Contact Worldwide support.
00077, 00000, "Could not convert to server national character set's handle"
// *Cause:  Internal error.
// *Action: Contact Worldwide support.
00078, 00000, "Cannot translate FILE locator to \"%.*s\" \"%.*s\" in server character set"
// *Cause:  (1) The current export dump file was generated using Beta-2 of
//     Oracle8.0  AND (2) there was a File that appeared as an
//     an attribute of an ADT within a table's column AND (3) the
//     character set of the export server's database was different than
//     the character set of the import server's database AND (4) when the
//     filename or the aliasname of the File increased in size when it
//     was translated to the character set of the import server.
//
//     When all of these conditions are true, translation of the strings
//     could yield corruption of the data in the column.  Rather than
//     proceeding with the translation, import will leave the character
//     strings in the File in the old character set.
// *Action: After import completes, rename the directory aliases and external
//     filenames to match the real names used for the target database.
00079, 00000, "Warning: National character set data in this table may be incorrect"
// *Cause:  Due to a problem in 8.0.2 Export, national character data in
//          NCHAR and NVARCHAR2 columns was incorrectly assumed to be in
//          the export server's data base character set and was converted
//          to the export client's data base character set.  This conversion
//          would only be correct if the export server's data base character
//          set was the same as the export server's national character set
//          and the export client's data base character set was the same as
//          the export client's national character set.  All other combinations
//          would likely be incorrect.  This export dump file was generated
//          by 8.0.2 Export and the export client and server characater sets
//          did not fit that criteria.
// *Action: Examine the national character data. If incorrect, update the
//          data with correct data.
00080, 00000, "Error during character conversion of long column or long command"
// *Cause:  During piecewise character conversion of the data in a long
//          column or of a long command, a fatal conversion error
//          occurred.  Either character truncation occurred or an invalid
//          character set handle was used.
// *Action: Retry the import with a different character set.
00081, 00000, "attempt to free unallocated memory"
// *Cause:  An attempt was made to free memory that was not allocated.
// *Action: Contact Oracle Worldwide Support
00082, 00000, "Error during conversion ROWID from string format to internal"
// *Cause:  An error occured while attempting to to convert a ROWID from an
//          export dump file into an internal format.
// *Action: Report this to Oracle Worldwide Support as an Import internal
//          error.
00083, 00000, "dump file does not contain an incremental export"
// *Cause:  An incremental import was requested and the dump file specified
//          for the import command is either a user or table export.
// *Action: Reissue the command import command but specify the name of a dump
//          file containing an incremental export.
00084, 00000, "attempt to mix incremental import with user or table import"
// *Cause:  An incremental import was requested along with the FROMUSER,
//          TOUSER, or TABLE qualifier.  An incremental import cannot be
//          done if any of these other qualifiers are also specified.
// *Action: Determine whether you want to do an incremental import, full
//     import, user import or table import and reissue the import command
//     with the appropriate qualifiers.
00085, 0000, "multiple input files specified for unbounded export file"
// *Cause:  You specified multiple file names for the FILE parameter when
//     doing an import, but the header in the export file indicates that
//     that the export operation could create only one file.  Specifying
//     multiple file names is valid for an import operation only if the
//     export files were created by an export operation in which the user
//     specified a non-zero value for the FILESIZE parameter.
// *Action: If you believe the export contains multiple files, verify that
//     you have specified the correct files.  If you believe the export
//     should be in only one file then try the import operation again,
//     but specify only one value for the FILE parameter.
00086, 00000, "TOID \"%s\" not found in export file"
// *Cause:  Import did not find the type identification specified
//          in the TOID_NOVALIDATE parameter. The specified type
//          identification does not exist in export file.
// *Action: Correct or omit the TOID_NOVALIDATE parameter.
00087, 00000, "Problem with internal hash table of schema/table names"
// *Cause:  Most likely a problem with allocating memory for the hash
//          table entries.
// *Action: Contact Oracle Worldwide Support
00088, 00000, "Problem importing metadata for index %s. Index creation will be skipped"
// *Cause:  Domain indexes import private metadata via anonymous PL/SQL blocks
//   prior to the CREATE INDEX statement. The execution of one of these
//        PL/SQL blocks failed. Because the metadata is considered an integral
//        part of the index, the subsequent CREATE INDEX statement was skipped.
// *Action: Contact the developer of the index's implementation type. If this
//   is an Oracle-supplied index (perhaps via a data cartridge), contact
//   Oracle Worldwide Support.
00089, 00000, "Fine grain policy \"%s\" not recreated on table/view \"%s\" "
// *Cause:  Import user fails to recreate fine grained policies of the
//     table/view being imported. To recreate the policy, the user doing
//          the import needs execute privilege on the package DBMS_RLS for
//          access policies or DBMS_FGA for audit policies.
// *Action:  Ask the database administrator to perform the export/import of
//      this table/view.
00090, 00000, "Unexpected DbmsJava error %d at step %u while creating %s"
// *Cause:  The error was returned from a call to a DbmsJava procedure.
// *Action: Record the accompanying messages and report this as an Import
//          internal error to customer support.
00091, 00000, "Above error occurred on the following function and object: %s. Remaining PL/SQL blocks for this object will be skipped."
// *Cause: An error occurred while executing a PL/SQL block that implements the
// DDL for the named function and procedural object. A procedural object
// is one whose DDL is implemented as stored procedures rather than as
// standard SQL statements.
// *Action: Contact Oracle Worldwide Support so they may determine the
// development group responsible for the package that failed.
00092, 00000, "Java object \"%s\".\"%s\" already exists, cannot be created"
// *Cause:  Import failed to create the Java source, class or resource object
//          because it already exists.
// *Action: Drop the object type from the target system and retry the
//          operation.
00093, 00000, "Inconsistency between dumpfile constraint definition for table %s with columns (%s)"
// *Cause: Import failed to locate a base table for a constraint that was
//    defined in the dump file and statistics were not imported.
// *Action: Check to see if the table and constraint exist. If the table and
//     constraint exist, then report this to Oracle Support Services as
//          an Import internal error.
00094, 00000, "Warning: The identifier on the dump file for object type \"%s\".\"%s\" is invalid"
// *Cause:  The character string representing the object type's identifier
// *        could not be converted.
// *Action: Contact Oracle Worldwide Support.
00095, 00000, "Resumable parameters ignored -- current session not resumable"
// *Cause: Current session is not resumable.
// *Action: Must specify RESUMABLE=Y to enable resumable session in order for
//          the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
00096, 00000, "Warning: Skipping table \"%s\".\"%s\" because type synonym \"%s\".\"%s\" cannot be created"
// *Cause:  An error occurred creating a synonym for a type that is used by the
// *        table.
// *Action: Examine the import log to determine why the type synonym could
// *        not be created. If the synonym already existed, but is not
// *        needed, then drop the synonym and retry the import. If the
// *        synonym is PUBLIC but the importer does not have the
// *        CREATE PUBLIC SYNONYM system privilege, then the import must
// *        be done by someone possessing that privilege, or the importer
// *        must be granted the privilege.
00097, 00000, "\nSTREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y"
// *Cause: STREAMS_CONFIGURATION=Y can only be used
// *       when FULL=Y is present on the command line
// *Action: Remove conflicting command arguments
00098, 00000, "INTERNAL ERROR: %s"
// *Cause:  An INTERNAL error occurred.
// *Action: Contact Oracle Worldwide Support.
00099, 00000, "Warning: The typeid in the dump file for object type \"%s\".\"%s\" is invalid"
// *Cause:  The character string representing the object type's identifier
// *        could not be converted.
// *Action: Contact Oracle Worldwide Support.
/
/ Informative messages
/
/   Do NOT translate message 100
// NLS_DO_NOT_TRANSLATE [100,100]
00100, 00000, "Import"
// UI[101,146]
00101, 00000, "\nConnected to: %s\n"
00102, 00000, "\n. . importing table%*.*s%*.*s"
00103, 00000, "%11lu rows imported"
00109, 00000, "\n\nWarning: the objects were exported by %s, not by you\n"
00110, 00000, "\nImport terminated successfully without warnings.\n"
00111, 00000, "\nColumn %lu %.*s"
00112, 00000, "\n. importing %s's objects into %s"
00113, 00000, "\nExport file created by %s"
00114, 00000, "\n. . skipping table %-35.*s"
00115, 00000, "\n. importing user %-35s"
00116, 00000, "\nSystem error message"
00117, 00000, "\nNote: table contains ROWID column, values may be obsolete"
00118, 00000, "\nImport terminated successfully with warnings.\n"
00119, 00000, "\nWriting all labels to %s\n"
00120, 00000, "\n%61lu rows imported"
00121, 00000, "\nExport file created by %s via conventional path"
00122, 00000, "\nExport file created by %s via direct path"
00123, 00000, "\nColumn : %.*s"
00124, 00000, "\nAbout to import Tablespace Point-in-time Recovery objects..."
00125, 00000, "\n. . importing partition%*.*s%*.*s"
00126, 00000, "\n. . skipping partition %-35.*s"
00127, 00000, "\nAbout to enable constraints..."
00128, 00000, "\nimport done in %s character set and %s NCHAR character set"
00129, 00000, "\nimport server uses %s character set (possible charset conversion)"
00130, 00000, "\nexport client uses %s character set (possible charset conversion)"
00131, 00000, "\nexport server uses %s NCHAR character set (possible ncharset conversion)"
00132, 00000, "first file in the multi-file export is %*s"
00133, 00000, "\n. . skipping TOID validation on type %s.%s"
00134, 00000, "\nAbout to import transportable tablespace(s) metadata..."
00135, 00000, "\n. . importing subpartition%*.*s%*.*s"
00136, 00000, "\n. . skipping subpartition %-35.*s"
/ Message 137 is unused.
00138, 00000, "\nNote: RECORDLENGTH=%lu truncated to %lu\n"
/ The following messages are used by the undocumented METRICS facility.
00139, 00000, "\n\nTotals for tables"
00140, 00000, "\n\nTotals for database"
/ Messages 141 thru 144 should all be the same length and right aligned with respect to other messages in the log.
00141, 00000, "\n        Rows    = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00142, 00000, "\n  Total Rows    = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00143, 00000, "\n        Objects = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00144, 00000, "\n  Total Objects = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00145, 00000, "\n  %10Ld Buffer Reads of %10Ld bytes = %10.3f Kbytes read"
00146, 00000, "\n  Throughput = %10.3f Kbytes/sec"
/ end of METRICS messages
/
/ Prompt messages
/
// UI[200,215]
00200, 00000, "\n%s (%s/%s): %s > "
00201, 00000, "\nImport file: %s > "
00202, 00000, "List contents of import file only"
00203, 00000, "Import entire export file"
00204, 00000, "\nEnter table(T) or partition(T:P) names. Null list means all tables for user"
00205, 00000, "\nEnter table(T) or partition(T:P) name or . if done: "
00206, 00000, "\nEnter insert buffer size (minimum is %lu) %lu> "
00207, 00000, "Username: "
00208, 00000, "Password: "
00209, 00000, "Ignore create error due to object existence"
00210, 00000, "Import grants"
00211, 00000, "Import table data"
00212, 00000, "\nMLS Import mapping file (default is none) "
00213, 00000, "List mapping relations"
00214, 00000, "Abort Import"
00215, 00000, "\nEnter name of the next file in the export file set."
#ifdef EXU_VOLSIZE
/
/ prompt for volsize
/
// UI[298,299]
00298, 00000, "\nVolume size (<ret> for no restriction) > "
00299, 00000, "\nPlease mount the next volume, and hit <ret> when you are done\n"
#endif

/
/ HELP messages, range defined as HELPSTART and HELPEND in impdef.h
/
// UI[300,338]
00300, 00000, "\n\nYou can let Import prompt you for parameters by entering the IMP\n"
00301, 00000, "command followed by your username/password:\n"
00302, 00000, "\n"
00303, 00000, "     Example: IMP SCOTT/TIGER\n"
00304, 00000, "\n"
00305, 00000, "Or, you can control how Import runs by entering the IMP command followed\n"
00306, 00000, "by various arguments. To specify parameters, you use keywords:\n"
00307, 00000, "\n"
00308, 00000, "     Format:  IMP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)\n"
00309, 00000, "     Example: IMP SCOTT/TIGER IGNORE=Y TABLES=(EMP,DEPT) FULL=N\n"
00310, 00000, "               or TABLES=(T1:P1,T1:P2), if T1 is partitioned table\n"
00311, 00000, "\n"
00312, 00000, "USERID must be the first parameter on the command line.\n"
00313, 00000, "\n"
00314, 00000, "Keyword  Description (Default)       Keyword      Description (Default)\n"
00315, 00000, "--------------------------------------------------------------------------\n"
00316, 00000, "USERID   username/password           FULL         import entire file (N)\n"
00317, 00000, "BUFFER   size of data buffer         FROMUSER     list of owner usernames\n"
00318, 00000, "FILE     input files (EXPDAT.DMP)    TOUSER       list of usernames\n"
00319, 00000, "SHOW     just list file contents (N) TABLES       list of table names\n"
00320, 00000, "IGNORE   ignore create errors (N)    RECORDLENGTH length of IO record\n"
00321, 00000, "GRANTS   import grants (Y)           INCTYPE      incremental import type\n"
00322, 00000, "INDEXES  import indexes (Y)          COMMIT       commit array insert (N)\n"
00323, 00000, "ROWS     import data rows (Y)        PARFILE      parameter filename\n"
00324, 00000, "LOG      log file of screen output   CONSTRAINTS  import constraints (Y)\n"
00325, 00000, "DESTROY                overwrite tablespace data file (N)\n"
00326, 00000, "INDEXFILE              write table/index info to specified file\n"
00327, 00000, "CHARSET                character set of export file (NLS_LANG)\n"
00328, 00000, "SKIP_UNUSABLE_INDEXES  skip maintenance of unusable indexes (N)\n"
00329, 00000, "FEEDBACK               display progress every x rows(0)\n"
00330, 00000, "TOID_NOVALIDATE        skip validation of specified type ids \n"
00331, 00000, "FILESIZE               maximum size of each dump file\n"
00332, 00000, "STATISTICS             import precomputed statistics (always)\n"
00333, 00000, "RESUMABLE              suspend when a space related error is encountered(N)\n"
00334, 00000, "RESUMABLE_NAME         text string used to identify resumable statement\n"      
00335, 00000, "RESUMABLE_TIMEOUT      wait time for RESUMABLE \n"
00336, 00000, "COMPILE                compile procedures, packages, and functions (Y)\n"
00337, 00000, "STREAMS_CONFIGURATION  import streams general metadata (Y)\n"
00338, 00000, "STREAMS_INSTANTIATION  import streams instantiation metadata (N)\n"
00339, 00000, "VOLSIZE                number of bytes in file on each volume of a file on tape\n"
// UI[360,364]
00360, 00000, "\nThe following keywords only apply to transportable tablespaces\n"
00361, 00000, "TRANSPORT_TABLESPACE import transportable tablespace metadata (N)\n"
00362, 00000, "TABLESPACES tablespaces to be transported into database\n"
00363, 00000, "DATAFILES datafiles to be transported into database\n"
00364, 00000, "TTS_OWNERS users that own data in the transportable tablespace set\n"
/
/ Error messages (continued from 000 - 099)
/
00400, 00000, "Warning: Object type \"%s\".\"%s\" already exists with a different typeid"
// *Cause:  An object type could not be created because it already existed on the
// *        target system, but with a different typeid
// *Action: Drop the object type from the target system and retry the
//          operation.
00401, 00000, "dump file \"%s\" may be an Data Pump export dump file"
// *Cause:  A dump file was specified for an import operation which appears
//          to have been created using the Data Pump export utility. These
//          dump files cannot be processed by the original import utility.
// *Action: Try using the Data Pump import utility to process this dump file.

/ $Header: expus.msg 26-aug-2004.10:07:30 jgalanes Exp $ exumtb.msg
/ Copyright (c) 1988, 2001 by the Oracle Corporation.  All rights reserved.
/
/ File: v6$knl:[impexp]exumtb.msg
/ Created: 07/12/88
/
/
/ This file is converted to header/message files using lmsgen.c
/
/ The first column is the Export error number.
/ The second column is reserved and must be (for now) 00000
/ The remainder of the line is the error text
/
/ Adding an error for Export:
/    Check out this file, add the error, and check it back in. Error numbers
/    should always be ordered.  The second column should always be 00000.
/
/
/ Range 000 - 199: actual Export errors
/ Range 200 - 299: informative messages
/ Range 300 - 399: prompt messages
/ Range 400 - 499: help messages
/
00000, 00000, "Export terminated unsuccessfully\n"
// *Cause:  Export encountered an Oracle error.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual, and take appropriate action.
00001, 00000, "data field truncation - column length=%lu, buffer size=%lu actual size=%lu"
// *Cause:  Export could not fit a column in the data buffer.
// *Action: Record the given size parameters and the accompanying messages and
//          report this as an Export internal error to customer support. (Part
//          of the table has been exported. Export will continue with the next
//          table.)
00002, 00000, "error in writing to export file"
// *Cause:  Export could not write to the export file, probably because of a
//          device error. This message is usually followed by a device message
//          from the operating system.
// *Action: Take appropriate action to restore the device.
00003, 00000, "no storage definition found for segment(%lu, %lu)"
// *Cause:  Export could not find the storage definitions for a cluster,
//          index, or table.
// *Action: Record the accompanying messages and report this as an Export
//          internal error to customer support.
00004, 00000, "invalid username or password"
// *Cause:  An invalid username or password was specified.
// *Action: Retry with a valid username and password.
00005, 00000, "all allowable logon attempts failed"
// *Cause:  Attempts were repeatedly made to log on with an invalid username
//          or password.
// *Action: Shut down the utility, then restart and retry with a valid
//          username and password.
00006, 00000, "internal inconsistency error"
// *Cause:  Export's data structure was corrupted.
// *Action: Record the accompanying messages and report this as an Export
//          internal error to customer support.
00007, 00000, "dictionary shows no columns for %s.%s"
// *Cause:  Export failed to gather column information from the data
//          dictionary. The table may have been dropped.
// *Action: Retry the export and, if this error recurs, report it as an Export
//          internal error to customer support.
00008, 00000, "ORACLE error %lu encountered"
// *Cause:  Export encountered the referenced Oracle error.
// *Action: Look up the Oracle message in the ORA message chapters of this
//          manual and take appropriate action.
00009, 00000, "no privilege to export %s's table %s"
// *Cause:  An attempt was made to export another user's table. Only a
//          database administrator can export another user's tables.
// *Action: Ask your database administrator to do the export.
00010, 00000, "%s is not a valid username"
// *Cause:  An invalid username was specified.
// *Action: Shut down the utility, then restart and retry with a valid
//          username.
00011, 00000, "%s.%s does not exist"
// *Cause:  Export could not find the specified table.
// *Action: Retry with the correct table name.
00012, 00000, "%s is not a valid export mode"
// *Cause:  An invalid export mode was specified.
// *Action: Retry with a valid export mode.
00013, 00000, "respond with either 'Y', 'N', RETURN or '.' to quit"
// *Cause:  An invalid response was entered.
// *Action: Enter any of the responses shown in the message.
00014, 00000, "error on row %lu of table %s\n"
// *Cause:  Export encountered an Oracle error while fetching rows.
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual and take appropriate action.
00015, 00000, "error on row %lu of table %s, column %s, datatype %lu"
// *Cause:  Export encountered an error while fetching or writing the
//          column. An accompanying message gives more information.
// *Action: Correct the error and try again.
00016, 00000, "ORACLE error encountered while reading default auditing options"
// *Cause:  Export encountered an Oracle error while reading the default
//          auditing options (those for updates, deletes, and so on).
// *Action: Look up the accompanying Oracle message in the ORA message
//          chapters of this manual and take appropriate action.
00017, 00000, "feature \"%s\" is needed, but not present in database"
// *Cause:  The command entered requires the specified feature.  Either that
//     feature is not installed, or the row describing the feature is
//     missing from table V$OPTION
// *Action: Reinstall Oracle with the feature specified in the message.
00018, 00000, "datatype (%lu) for column %s, table %s.%s is not supported"
// *Cause:  Export does not support the referenced datatype.
// *Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE,
//          LONG, or RAW).
00019, 00000, "failed to process parameters, type 'EXP HELP=Y' for help"
// *Cause:  Invalid command-line parameters were specified.
// *Action: Check the online help screen for the set of valid parameters, then
//          retry.
00020, 00000, "failed to allocate memory of size %lu"
// *Cause:  Export failed to allocate the necessary memory.
// *Action: Decrease the export buffer size so that less memory is required,
//          or increase the runtime memory size for Export.
00021, 00000, "can only perform incremental export in Full Database mode"
// *Cause:  USER or TABLE mode was specified when doing an incremental export.
// *Action: Specify FULL database mode (FULL=Y) and retry.
00022, 00000, "must be SYS or SYSTEM to do incremental export"
// *Cause:  The privileges needed to do an incremental export do not exist.
//          Only a data base administrator can do incremental exports.
// *Action: Ask the database administrator to do the incremental export.
00023, 00000, "must be a DBA to do Full Database or Tablespace export"
// *Cause:  The privileges needed to do a FULL database export do not exist.
//          Only a database administrator can do a FULL database export.
// *Action: Ask the database administrator to do the FULL database export.
00024, 00000, "Export views not installed, please notify your DBA"
// *Cause:  The necessary Export views were not installed.
// *Action: Ask the database administrator to install the required Export
//          views.
00025, 00000, "dictionary shows no column for constraint %s.%lu"
// *Cause:  Export failed to gather column information about the referenced
//          constraint from the data dictionary. The constraint may have
//          been altered.
// *Action: Retry the export and, if this error recurs, report it as an Export
//          internal error to customer support.
00026, 00000, "conflicting modes specified"
// *Cause:  Conflicting export modes were specified.
// *Action: Specify only one parameter and retry.
00027, 00000, "failed to calculate ORACLE block size"
// *Cause:  Export failed to calculate the Oracle block size.
// *Action: Report this as an Export internal error to customer support.
00028, 00000, "failed to open %s for write"
// *Cause:  Export failed to open the export file for writing. This message is
//          usually followed by device messages from the operating system.
// *Action: Take appropriate action to restore the device.
00029, 00000, "Incremental export mode and consistent mode are not compatible"
// *Cause:  Both consistent and incremental exports were specified.
// *Action: None. Consistent mode is turned off.
00030, 00000, "Unexpected End-Of-File encountered while reading input"
// *Cause:  Encountered an End-Of-File while reading the user input.
// *Action: If input to export is being redirected, check the file for errors.
00031, 00000, "Arraysize not in valid range. Using arraysize=%u"
// *Cause:  The arraysize value specified is not in the valid range.
// *Action: None
00032, 00000, "Non-DBAs may not export other users"
// *Cause:  Only database administrators can export to other users. A non-
//          database administrator attempted to specify owner=user where
//          exporter is not the user.
// *Action: Request that this operation be performed by the database
//          administrator.
00033, 00000, "Could not find environment character set"
// *Cause:  The environment character set is missing or incorrectly specified.
// *Action: Ensure that the environment character set is correctly specified
//          and is present.
00034, 00000, "error on rowid: file# %lu block# %lu slot# %lu"
// *Cause:  Identifies the rowid on which an error occurred.
// *Action: This is an information message. No action is required.
00035, 00000, "QUERY parameter valid only for table mode exports" 
// *Cause:  You specified the QUERY parameter in an export command, but you 
//     are not performing a table mode export.  The QUERY parameter cannot
//     be used for a user mode export, a full export, nor 
//     a point in time recovery export. 
// *Action: If you want to select a subset of rows for a table, you must export
//     the table independently with a table mode export.  Issue a table 
//     mode export command that specifies the table name and the query you
//     want to execute during export.
00036, 00000, "Object %lu non-existent in dictionary"
// *Cause:  The specified object could not be found in the dictionary.
//          The object might have been dropped during the export
// *Action: The object no longer exists; no action is needed.
00037, 00000, "Export views not compatible with database version"
// *Cause:  The Export utility is at a higher version than the database
//          version and is thereby incompatible.
// *Action: Use the same version of Export utility as the database.
00038, 00000, "Bad Hash cluster id in clu$"
// *Cause:  The function id in clu$ is not a legal number. Clu$ has become
//          corrupted.
// *Action: Contact Worldwide Support
00039, 00000, "export file %s must be on a disk"
// *Cause:  On some platforms, export can read files from tape.  This message
//     is displayed if the first file in an export file set was on disk
//     and you specified a tape device for a second or subsequent file.
// *Action: Verify that you have specified the correct file name for the export
//     file.  Remember that all export files can be either on disk or all
//     files can be on tape, but not mixed both tape and disk.
00040, 00000, "Dump file and log file must be different"
// *Cause:  The dump file and log file cannot be the same file.
// *Action: Specify different file names for the dump file and the log file,
//          then retry the operation.
00041, 00000, "INCTYPE parameter is obsolete"
// *Cause:  Export encountered the INCTYPE parameter when parsing Export
//          options.  Incremental Exports are no longer supported.
// *Action: Consult the Oracle Backup and Recovery guide. 
//          Export will attempt to continue.
00042, 00000, "Missing NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET in props$"
// *Cause:  A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was not
//          entered in the props$ table"
// *Action: internal error.
00043, 00000, "Invalid data dictionary information in the row where column \"%s\" is \"%s\" in table %s"
// *Cause:  The export utility retrieved invalid data from the data
//     dictionary.
// *Action: Contact Oracle Worldwide Suport.
00044, 00000, "must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import"
// *Cause:  The user must log in 'as SYSDBA' to perform transportable
//          tablespace imports or Point-In-Time Recovery imports.
// *Action: Ask your database adminstrator to perform the Transportable
//          Tablespace import or the Tablespace Point-in-time Recovery import.
00045, 00000, "Cannot export SYSTEM Tablespace for Point-in-time Recovery or Transportable Tablespace"
// *Cause:  SYSTEM tablespace cannot be part of recovery set or transportable tablespace set.
// *Action: Contact Oracle Wordwide Support.
00046, 00000, "Tablespace named %s does not exist"
// *Cause:  The specified tablespace does not exist in dictionary.
// *Action: Contact Oracle Wordwide Support.
00047, 00000, "Missing tablespace name(s)"
// *Cause:  Tablespace name(s) were not supplied
// *Action: Provide tablespace name(s)
00048, 00000, "Cannot export SYSAUX Tablespace for Point-in-time Recovery or Transportable Tablespace"
// *Cause:  SYSAUX tablespace cannot be part of recovery set or transportable tablespace set.
// *Action: Contact Oracle Wordwide Support.
00049, 00000, "%s option is not compatible with Point-in-time Recovery or Transportable Tablespace Export"
// *Cause:  An option was specified incompatible with Point-in-time
//          Recovery or Transportable Tablespace Export.
// *Action: Retry the Export without the displayed option.
00050, 00000, "Cannot perform Partition Export \"%s\" on non-partitioned table \"%s\""
// *Cause:  The table specified in this Partition Export is not a
//          partitioned table.
// *Action: Use Table mode, or specify a non-partitioned table.
00051, 00000, "\"%s\" - given partition or subpartition name is not part of \"%s\" table"
// *Cause:  The specified partition or subpartition name is not in the specified table.
// *Action: Check if the correct table, partition or subpartition name was specified.
00052, 00000, "error on row %lu of partition %s\n"
// *Cause:  Export encountered the referenced Oracle error while fetching
//          rows.
// *Action: Look up the Oracle message in the ORA message chapters of this
//          manual and take appropriate action.
00053, 00000, "unable to execute QUERY on table %s because the table has inner nested tables" 
// *Cause:  You specified the QUERY parameter on a table that has one or more
//     inner nested tables.  The QUERY parameter cannot be specified on  
//     tables that have inner nested tables. 
// *Action: Export the entire table by omitting the QUERY parameter.
00054, 00000, "error on row %lu of subpartition %s\n"
// *Cause:  Export encountered the referenced Oracle error while fetching rows.
// *Action: Look up the Oracle message in the ORA message chapters of this
//          manual and take appropriate action. 
00055, 00000, "%s.%s is marked not exportable"
// *Cause:  An object was marked as non-exportable in the NOEXP$ table.
// *Action: Consult your database administrator.
/ do NOT translate or document message 56 - it is never displayed
// NLS_DO_NOT_TRANSLATE [56,56]
00056, 00000, "placeholder for OCI error "
// *Document: NO
// *Cause:  filler
// *Action: filler
00057, 00000, "Failure to initialize parameter manager"
// *Cause:  The parameter manager failed in intialization.
// *Action: Record the messages that follow and report this to Oracle Wordwide
//          Support as an Export internal bug.
00058, 00000, "Password Verify Function for %s profile does not exist"
// *Cause:  Cannot find the function for the profile.
// *Action: Check if the profile was created properly.
00059, 00000, "error converting an object type's identifier to characters"
// *Cause:  An invalid length of an object type identifier prevented
//          its conversion.
// *Action: Contact Oracle Worldwide Support
00060, 00000, "an object type had multiple TYPE BODYs"
// *Cause:  More than one TYPE BODY was found for an object type.
// *Action: Try dropping the TYPE BODY, if that is not successful, contact 
//          Oracle Worldwide Support
00061, 00000, "unable to find the outer table name of a nested table "
// *Cause:  While exporting a bitmap index or posttable action
//          on an inner nested table, the name of the outer
//          table could not be located, using the NTAB$ table.
// *Action: Verify the table is properly defined.
00062, 00000, "invalid source statements for an object type"
// *Cause:  TYPE was not found in the statements in SOURCE$ for an
//          Object Type
// *Action: Contact Oracle Worldwide Support.
00063, 00000, "error in changing language handle"
// *Cause:  Unable to change language handle.
// *Action: Contact Oracle Worldwide Support.
00064, 00000, "%s is an inner nested table and cannot be exported."
// *Cause:  An attempt was made to export an inner nested table without its
//          parent table.
// *Action: Export the parent of the inner nested table.
00065, 00000, "Error writing lob to the dump file."
// *Cause:  The current LOB could not be written to the dump file.
// *Action: Identify the cause of the write failure and fix it.
00066, 00000, "Object table %s is missing its object identifier index"
// *Cause:  All object tables must have an object identifier index, but
//          the specified table was missing an index on its object
//     identifier column.
// *Action: Recreate the type table and retry the operation.
00068, 00000, "tablespace %s is offline"
// *Cause:  Export failed to export tablespace (tablespace being offline).
// *Action: Make tablespace online and re export.
/ do NOT translate or document message 69 - it is never displayed
// NLS_DO_NOT_TRANSLATE [69,69]
00069, 00000, "placeholder for column level ORA error "
// *Document: NO
// *Cause:  filler
// *Action: filler
00070, 00000, "attempt to free unallocated memory"
// *Cause:  An attempt was made to free memory that was not allocated.
// *Action: Contact Oracle Worldwide Support
00071, 00000, "QUERY parameter not compatible with Direct Path export"
// *Cause:  You specified a value for the QUERY parameter for a direct path
//     export. The QUERY parameter cannot be used with a direct path
//     export.
// *Action: Re-issue the export command with DIRECT=N or omit the DIRECT 
//     parameter from the command line.
00072, 00000, "error closing export file %s"
// *Cause:  An error occurred while trying to close the export file.
// *Action: Contact Oracle Worldwide Support.
00073, 00000, "dump file size too small"
// *Cause:  You specified either the FILESIZE parameter or the VOLSIZE
//        parameter (if your platform supports it), and the value of the
//        parameter is too small to hold the header information for the 
//        export file, plus any data. 
// *Action: Increase the value of the FILESIZE or VOLSIZE parameter.
#ifdef EXU_VOLSIZE
00074, 0000, "rounding VOLSIZE down, new value is %s"
// *Cause:  The VOLSIZE parameter must be a multiple of the RECORDLENGTH,
//        but the value you specified for VOLSIZE does not meet this
//        requirement.  The value of VOLSIZE has been rounded down to
//        be a multiple of the RECORDLENGTH used for the dump file.
// *Action: No action is required.  You can adjust the VOLSIZE or RECORDLENGTH
//        parameter to avoid this message.  When importing
//        this file, you must specify the VOLSIZE value reported by this
//        message.
#endif
00075, 0000, "rounding FILESIZE down, new value is %s"
// *Cause:  The FILESIZE parameter must be a multiple of the RECORDLENGTH,
//        but the value you specified for FILESIZE does not meet this
//        requirement.  The value of FILESIZE has been rounded down to
//        be a multiple of the RECORDLENGTH used for the dump file.
// *Action: No action is required.  You can adjust the FILESIZE or RECORDLENGTH
//        parameter to avoid this message.  When importing
//        this file, you must specify the FILESIZE value reported by this
//        message.
#ifdef EXU_VOLSIZE
00076, 0000, "multiple devices specified for tape output"
// *Cause:  You specified multiple file names when doing an export to a tape
//   device.  EXPORT uses the same device for writing all files, of the
//   number of tape volumes required.  For this reason, export will
//   accept only one value for the FILE parameter when writing to tape.
// *Action: Reenter the EXPORT command, but specify only one tape device in
//   the FILE parameter.
#endif
00077, 0000, "multiple output files specified for unbounded export file"
// *Cause:  You specified multiple file names when doing an export and you also
//   specified a value of 0 for the FILESIZE parameter.  Note that 0 is
//   the value used if FILESIZE is not specified on the command line.
//   Since a value of 0 for FILESIZE means that only one file will be
//   written and there is no size limit for that file, the other files
//   you specified in the FILE parameter can never be used.
// *Action:  If you intended to write multiple files, respecify the command
//   but use the FILESIZE to specify the maximum number of bytes that
//   EXPORT should write to each file.  If you intended to write only
//   one file with no limits on it's size, reissue the EXPORT command
//   but specify only one file name for the FILE parameter.
00078, 0000, "Error exporting metadata for index %s. Index creation will be skipped"
// *Cause:  Domain indexes export private metadata via anonymous PL/SQL blocks
//   prior to the CREATE INDEX statement. Export does this by calling
//   the ODCIIndexGetMetadata method on the implementation type
//   associated with the index. A problem occurred inside this routine.
//   Because the metadata is considered an integral part of the index,
//   the CREATE INDEX statement was not written to the dump file.
// *Action: Contact the developer of the index's implementation type. If this
//   is an Oracle-supplied index (perhaps via a data cartridge), contact
//   Oracle Worldwide Support.
00079, 0000, "Data in table \"%s\" is protected. Conventional path may only be exporting partial table."
// *Cause:  User without the execute privilege on DBMS_RLS, the access control
//        package, tries to export a table that has access control. Since table
//        owner is also subjected to access control, the owner may not be able
//        to export all rows in the table, but only the ones he can see.  Also,
//        to preserve integrity of the table, user exporting the table should
//        have enough privilege to recreate the table with the security
//        policies at import time. Therefore, it is strongly recommended
//        the database administrator should be handling exporting of this
//        table. Granting the table owner execute privilege would also
//        satisfy this security check, though it might have other security
//        implications. If the table does not have objects, can use direct mode.
// *Action: Ask the database administrator to export/import this table/view.
00080, 0000, "Data in table \"%s\" is protected. Using conventional mode."
// *Cause:  User without the execute privilege on DBMS_RLS, the access control
//        package, tries to direct export a table that has access control
//        enabled. Using conventional export mode instead. Note that
//        because of access control, only a partial table may be exported.
// *Action: Ask the database administrator to export/import this table/view.
00081, 0000, "Exporting access control for table/view \"%s\" as non-DBA."
// *Cause:  A non-DBA user tries to export table/view and the associated
//        fine grain access control policies.  The user may not have enough
//        privilege to recreate the access control policies when importing
//        the table/view. And such an event may cause inconsistency
//        in the security model of the table/view.
// *Action: Ask the database administrator to export/import this table/view.
00082, 00000, "Invalid function name passed to procedural object support: %s"
// *Cause:  Internal inconsistency error: The listed function is not a method
//          on export's procedural object interface specification.
// *Action: Contact Oracle Worldwide Support
00083, 00000, "The previous problem occurred when calling %s.%s.%s"
// *Cause:  The listed package provides export/import support for procedural
// actions. The previously listed error occurred while calling the
// specified function.
// *Action: Contact Oracle Worldwide Support. Most packages are supplied by
// Oracle internal cartridge or server development groups. The package
// name will help Support determine the correct owner of the problem.
00084, 00000, "Unexpected DbmsJava error %d at step %u"
// *Cause:  The error was returned from a call to a DbmsJava procedure.
// *Action: Record the accompanying messages and report this as an Export
//          internal error to customer support.
00085, 00000, "The previous problem occurred when calling %s.%s.%s for object %lu"
// *Cause:  The listed package provides export/import support for procedural
// objects, i.e, those whose DDL is supplied by stored procedures. The
// previously listed error occurred while calling the specified function.
// *Action: Contact Oracle Worldwide Support. Most packages are supplied by
// Oracle internal cartridge or server development groups. The package
// name will help Support determine the correct owner of the problem.
00086, 00000, "Primary key REFs in table \"%s\"may not be valid on import"
// *Cause:  The specified table contains primary key REFs which may
//          not be valid in the import database.
// *Action: Do not use Export/Import to move Primary key REFs between
//          databases having differing character sets.
00087, 00000, "Problem with internal hash table of schema/table names"
// *Cause:  Most likely a problem with allocating memory for the hash
//          table entries.
// *Action: Contact Oracle Worldwide Support
// NLS_DO_NOT_TRANSLATE [88,88]
00088, 00000, "null error message, just signal error "
// *Document: NO
// *Cause:  filler
// *Action: filler
00089, 00000, "invalid FILE_FORMAT specification"
// *Cause:  The FILE_FORMAT specification did not contain an
//          instance of "%s".  This wildcard string must be present.
// *Action: Correct the error and reenter the EXPORT command.
00090, 00000, "cannot pin type \"%s\".\"%s\""
// *Cause:  Export was unable to pin the specified type in the object cache.
//          This is typically caused because a type could not be made valid
//          (for example because of authorization violations in accessing
//          subtypes).
// *Action: Fix the problem with the offending type until the type can be
//          successfully compiled.
00091, 00000, "Exporting questionable statistics."
// *Cause:  Export was able export statistics, but the statistics may not be
//          usuable. The statistics are questionable because one or more of
//     the following happened during export: a row error occurred, client
//     character set or NCHARSET does not match with the server, a query
//     clause was specified on export, only certain partitions or
//     subpartitions were exported, or a fatal error occurred while
//     processing a table.
// *Action: To export non-questionable statistics, change the client character
//     set or NCHARSET to match the server, export with no query clause,
//     export complete tables. If desired, import parameters can be
//     supplied so that only non-questionable statistics will be imported,
//     and all questionable statistics will be recalculated.
00092, 00000, "Unable to set NLS_NUMERIC_CHARACTERS to required defaults."
// *Cause:  Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'
// *Action: Record the accompanying messages and report this as an Export
//          internal error to customer support.
00093, 00000, "Could not convert to server character set's handle"
// *Cause:  Internal error.
// *Action: Contact Worldwide support.
00094, 00000, "Could not convert to server national character set's handle"
// *Cause:  Internal error.
// *Action: Contact Worldwide support.
00095, 00000, "Flashback_time and Flashback_scn are not compatible"
// *Cause:  Both flashback_time and flashback_scn paramerers were specified.
// *Action: Reissue command with only one flashback parameter.
00096, 00000, "The template name specified can not be found."
// *Action: The template name specified does not exist. Verify template name
//          by looking up view %_ias_template.
00097, 00000, "Object type \"%s\".\"%s\" is not in a valid state, type will not be exported"
// *Cause:  The object type's status is invalid which may be caused by
//          a dependant type's modification (or removal) without cascading
//          the change.
// *Action: The type must be recompiled using ALTER TYPE COMPILE.
00098, 00000, "Data in table has not been upgraded, table will not be exported"
// *Cause:  Export is attempting to process a table containing references
//          to a type which has evolved.  In order for Export to process the
//          table successfully, all data within each table must be upgraded
//          to the latest revision of each referenced type.
// *Action: The table must be updated using ALTER TABLE UPGRADE DATA.
00099, 00000, "Table \"%s\".\"%s\" is not in a valid state, table will not be exported"
// *Cause:  A table or one of its dependant types has modified without
//          cascading the change.  This left the table in an INVALID state.
// *Action: The table must be updated using ALTER TABLE UPDATE.
00100, 00000, "error converting an object type's hashcode to characters"
// *Cause:  An invalid length of an object type identifier prevented
//          its conversion.
// *Action: Contact Oracle Worldwide Support
00101, 00000, "Version 1 extensible index \"%s\".\"%s\" can not be included in Transportable Tablespace Export"
// *Cause:  Transporable Tablespace extensible indexes must be at least version
//          2.
// *Action: Upgrade extensibile index implementation to version 2
//          specifications.
00102, 00000, "Resumable parameters ignored -- current session not resumable"
// *Cause:  Current session is not resumable.
// *Action: Must specify RESUMABLE=Y to enable resumable session in order for
//          the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
00103, 00000, "The FLASHBACK_TIME parameter was invalid"
// *Cause:  FLASHBACK_TIME did not contain a valid timestamp or an expression
//          that yields a valid timestamp.
// *Action: Specify a timestamp value in the format of YYYY-MM-DD HH24:MI:SS or
//          an expression that evaluates to a valid timestamp.
00104, 00000, "datatype (%s) of column %s in table %s.%s is not supported, table will not be exported"
// *Cause:  The column is of a datatype which does not contain the required
//          support.  The table will not be exported.
// *Action: Use the Data Pump version of Export to export this table.
00105, 00000, "parameter %s is not supported for this user"
// *Cause:  The user attempted to specify either CONSISTENT or OBJECT_CONSISTENT
//          when connected as sysdba.
// *Action: If a consistent export is needed, then connect as another user.
/
00106, 00000, "Invalid Database Link Passwords"
// *Cause:  Invalid Encoded Password for Database Link
// *Action: Please drop the Database Link and recreate it after import.
00107, 00000, "Feature (%s) of column %s in table %s.%s is not supported. The table will not be exported."
// *Cause:  Export does not contain the required support for this feature.
//          The table will not be exported.
// *Action: Use the Data Pump version of Export to export this table.
/
/ Informative messages
/
// UI[200,205]
00200, 00000, "\nExport terminated successfully without warnings.\n"
00201, 00000, "\n\nAbout to export specified tables "
00203, 00000, "\nCurrent user changed to %s"
00204, 00000, "\n\nAbout to export specified users ..."
00205, 00000, "%11lu rows exported"
/ do NOT translate message 206
// NLS_DO_NOT_TRANSLATE [206,206]
00206, 00000, "Export"
// UI[207,285]
00207, 00000, "\nConnected to: %s"
00208, 00000, "\n\nAbout to export the entire database ..."
00209, 00000, "\n. exporting user definitions"
00210, 00000, "\n. exporting cluster definitions"
00211, 00000, "\n. exporting tablespace definitions"
00212, 00000, "\n. exporting synonyms"
00213, 00000, "\n. exporting default and system auditing options"
00214, 00000, "\n. . exporting table%*.*s%*.*s"
00215, 00000, "\nAbout to export %s's objects ..."
00216, 00000, "\n. about to export %s's tables "
00217, 00000, "\n. exporting database links"
00218, 00000, "\n. exporting rollback segment definitions"
00219, 00000, "\n. exporting sequence numbers"
00220, 00000, "\n. exporting referential integrity constraints"
00221, 00000, "\n. exporting information about dropped objects"
00222, 00000, "\n. exporting PUBLIC type synonyms"
00223, 00000, "\nNote: grants on tables/views/sequences/roles will not be exported"
00224, 00000, "\nNote: indexes on tables will not be exported"
00225, 00000, "\nNote: constraints on tables will not be exported"
00226, 00000, "\nNote: table data (rows) will not be exported"
00227, 00000, "\n. exporting roles"
00228, 00000, "\n. exporting views"
00229, 00000, "\n. exporting triggers"
00230, 00000, "\n. exporting profiles"
00231, 00000, "\n. exporting stored procedures"
00232, 00000, "\n. exporting materialized views"
00233, 00000, "\n. exporting snapshot logs"
00234, 00000, "          Rows not exported"
00235, 00000, "\nWarning: Object %s.%s is invalid"
00236, 00000, "\nExport terminated successfully with warnings.\n"
00237, 00000, "\n. exporting resource costs"
00238, 00000, "\n. exporting job queues"
00239, 00000, "\n. exporting refresh groups and children"
00240, 00000, "\n. exporting posttables actions"
00241, 00000, "\n%61lu rows exported"
00242, 00000, "via Conventional Path ..."
00243, 00000, "via Direct Path ..."
00244, 00000, "\nExport done in %s character set and %s NCHAR character set"
00245, 00000, "\n\nAbout to export Tablespace Point-in-time Recovery objects..."
00246, 00000, "\nFor tablespace %s ..."
00247, 00000, "\n. exporting table definitions"
00248, 00000, "\nWarning: %s option incompatible with Tablespace point-in-time Recovery"
00249, 00000, "\n. . exporting partition%*.*s%*.*s"
00250, 00000, "\n. end point-in-time recovery"
00251, 00000, "\n. exporting user history table"
00252, 00000, "\n. exporting foreign function library names for user %s "
00253, 00000, "\n. exporting object type definitions"
00254, 00000, "\n. exporting object type definitions for user %s "
00255, 00000, "\nNote: Table depends on an object type from a different schema %s.%s"
00256, 00000, "\n. exporting directory aliases"
00257, 00000, "\n. exporting foreign function library names"
00258, 00000, "\nserver uses %s character set (possible charset conversion)"
00259, 00000, "\ncontinuing export into file %s\n"
00260, 00000, "\n. exporting context namespaces"
00261, 00000, "\nAbout to export transportable tablespace metadata..."
00262, 00000, "\n. end transportable tablespace metadata export"
00263, 00000, "\n. exporting operators"
00264, 00000, "\n. exporting indextypes"
00265, 00000, "\n. exporting dimensions"
00266, 00000, "\n. exporting system procedural objects and actions"
00267, 00000, "\n. exporting pre-schema procedural objects and actions"
00268, 00000, "\n. exporting post-schema procedural objects and actions"
00269, 00000, "\n. exporting bitmap, functional and extensible indexes"
00270, 00000, "\n. . exporting composite partition%*.*s%*.*s"
00271, 00000, "\n. . exporting subpartition%*.*s%*.*s"
00272, 00000, "\n. exporting statistics"
00273, 00000, "\nNote: RECORDLENGTH=%lu truncated to %lu\n"
00274, 00000, "\n\nAbout to export selected tablespaces ..."
00275, 00000, "\n. exporting iAS generated DDL statements"
00276, 00000, "\nTable %s will be exported in conventional path."
00277, 00000, "\n. exporting private type synonyms"
/ The following messages are used by the undocumented METRICS facility.
00278, 00000, "\n\nTotals for tables"
00279, 00000, "\n\nTotals for database"
/ Messages 280 thru 283 should all be the same length and right aligned with respect to other messages in the log.
00280, 00000, "\n        Rows    = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00281, 00000, "\n  Total Rows    = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00282, 00000, "\n        Objects = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00283, 00000, "\n  Total Objects = %10Ld Elapsed Time = %02ld:%02ld:%02ld:%02ld  CPU Time = %02ld:%02ld:%02ld:%02ld"
00284, 00000, "\n  %10Ld Buffer Writes of %10Ld bytes = %10.3f Kbytes written"
00285, 00000, "\n  Throughput = %10.3f Kbytes/sec"
/ end of METRICS messages

/
/ Prompt messages
/
// UI[300,311]
00300, 00000, "\nEnter array fetch buffer size: %lu > "
00301, 00000, "\nUsername: "
00302, 00000, "Password: "
00303, 00000, "\nTable(T) or Partition(T:P) to be exported: (RETURN to quit) > "
00304, 00000, "\nUser to be exported: (RETURN to quit) > "
00305, 00000, "Compress extents"
/
/ These messages used to accept only the first letter of the mode.
/ Now they also accept the number indicated in parentheses so they
/ are language-independent.
00306, 00000, "\n(1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U > "
00307, 00000, "\n(2)U(sers), or (3)T(ables): (2)U > "
/
00308, 00000, "\n%s (%s/%s): %s > "
00309, 00000, "\nExport file: %s > "
00310, 00000, "Export grants"
00311, 00000, "Export table data"
#ifdef EXU_VOLSIZE
/
/ prompt for volsize
/
// UI[398,399]
00398, 00000, "\nVolume size (<ret> for no restriction) > "
00399, 00000, "\nPlease mount the next volume and hit <ret> when you are done.\n"
#endif /* EXU_VOLSIZE */

/
/ HELP messages, range defined as EXUSHLP and EXUEHLP in exudef.h
/
// UI[400,436]
00400, 00000, "\n\nYou can let Export prompt you for parameters by entering the EXP\n"
00401, 00000, "command followed by your username/password:\n"
00402, 00000, "\n"
00403, 00000, "     Example: EXP SCOTT/TIGER\n"
00404, 00000, "\n"
00405, 00000, "Or, you can control how Export runs by entering the EXP command followed\n"
00406, 00000, "by various arguments. To specify parameters, you use keywords:\n"
00407, 00000, "\n"
00408, 00000, "     Format:  EXP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)\n"
00409, 00000, "     Example: EXP SCOTT/TIGER GRANTS=Y TABLES=(EMP,DEPT,MGR)\n"
00410, 00000, "               or TABLES=(T1:P1,T1:P2), if T1 is partitioned table\n"
00411, 00000, "\n"
00412, 00000, "USERID must be the first parameter on the command line.\n"
00413, 00000, "\n"
00414, 00000, "Keyword    Description (Default)      Keyword      Description (Default)\n"
00415, 00000, "--------------------------------------------------------------------------\n"
00416, 00000, "USERID     username/password          FULL         export entire file (N)\n"
00417, 00000, "BUFFER     size of data buffer        OWNER        list of owner usernames\n"
00418, 00000, "FILE       output files (EXPDAT.DMP)  TABLES       list of table names\n"
00419, 00000, "COMPRESS   import into one extent (Y) RECORDLENGTH length of IO record\n"
00420, 00000, "GRANTS     export grants (Y)          INCTYPE      incremental export type\n"
00421, 00000, "INDEXES    export indexes (Y)         RECORD       track incr. export (Y)\n"
00422, 00000, "DIRECT     direct path (N)            TRIGGERS     export triggers (Y)\n"
00423, 00000, "LOG        log file of screen output  STATISTICS   analyze objects (ESTIMATE)\n"
00424, 00000, "ROWS       export data rows (Y)       PARFILE      parameter filename\n"
00425, 00000, "CONSISTENT cross-table consistency(N) CONSTRAINTS  export constraints (Y)\n\n"
00426, 00000, "OBJECT_CONSISTENT    transaction set to read only during object export (N)\n"
00427, 00000, "FEEDBACK             display progress every x rows (0)\n"
00428, 00000, "FILESIZE             maximum size of each dump file\n"
00429, 00000, "FLASHBACK_SCN        SCN used to set session snapshot back to\n"
00430, 00000, "FLASHBACK_TIME       time used to get the SCN closest to the specified time\n"
00431, 00000, "QUERY                select clause used to export a subset of a table\n"
00432, 00000, "RESUMABLE            suspend when a space related error is encountered(N)\n"
00433, 00000, "RESUMABLE_NAME       text string used to identify resumable statement\n"
00434, 00000, "RESUMABLE_TIMEOUT    wait time for RESUMABLE \n"
00435, 00000, "TTS_FULL_CHECK       perform full or partial dependency check for TTS\n"
00436, 00000, "VOLSIZE              number of bytes to write to each tape volume\n"
/
/ HELP messages for transportable tablespace, range defined as EXUTSHLP and
/ EXUTEHLP in exudef.h
/
// UI[461,463]
00461, 00000, "TABLESPACES          list of tablespaces to export\n"
00462, 00000, "TRANSPORT_TABLESPACE export transportable tablespace metadata (N)\n"
/
/ HELP message for iAS mode export.
00463, 00000, "TEMPLATE             template name which invokes iAS mode export\n"

현재 export 받을려고 하는 DB1 의 기본 charset 은 KO16KSC5601 입니다.

그런데 TESTMALL 유저는 US7ASCII 의 DB2 를 export 받아서 import 한 유저입니다.

테이블및 기타오브젝트는 exp 와 imp 를 이용하여 import 했고

data는 한글이 깨지는 관계로 스크립트를 만들어서 import 했습니다.

이 유저를 다시 KO16KSC5601 의 또다른 DB3 에 import 하기 위해서

export 하려고 하니 다음과 같은 에러가 발생을 하네요.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses KO16KSC5601 character set (possible charset conversion)
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user TESTMALL
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user TESTMALL
About to export TESTMALL's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
EXP-00056: ORACLE error 1652 encountered
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
EXP-00000: Export terminated unsuccessfully

기존 방식처럼 export/import 하면 되겠지만 시간도 많이 걸리고 새로운 데이타가 몇개 있어서요.

DB1(KO16KSC5601) -> DB3(KO16KSC5601) 로 export/import 할 수 있는 방법이 없을까요?

select * from sb???? as of timestamp(systimestamp - interval '120' minute) where pername='홍길동';

insert into sb????
select * from sb???? as of timestamp(systimestamp - interval '120' minute) where perid='660729';

------------------------------

오라클에서 지원하는 Flashback 이라는 기능입니다.


※select

select * from item

 where orgid ='HANSALIM'  and itemnum like 'R %' ;

※delete
 

 delete from item

 where orgid ='HANSALIM'  and  itemnum like 'R %';

※commit

commit;

 

※delete 한것을 다시 조회해 온다 (10분 전내용으로)

 SELECT * FROM item

 as of timestamp ( systimestamp - interval '10' minute)

where orgid ='HANSALIM'  and  itemnum like 'R %';

※원래 table로 다시 인서트 한다.
 

insert into item

 SELECT * FROM item

 as of timestamp ( systimestamp - interval '10' minute)

where orgid ='HANSALIM'  and  itemnum like 'R %';

※ update 잘못친경우도 10분전(interval '10' minute) 여기 시간을 조정해서 읽어온 후 처리 할수도 있습니다.

참고문서

http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_flashback.htm#sthref1460 

 

imp user/pass

file=xxxx.dmp                                       // 파일명 적으시오

full=y                                                    // 없어두 됨

ignore=y                                                // 없어두 됨

commit=y                                                // 없어두 됨

fromuser=(dmp파일 만든 장본인 계정)

touser=(import 받을 계정)

tables=tbl1,tbl2                                    // 뽑아내고 싶은 테이블이 있다면...

 

ex) $imp system/manager file=source.dmp fromuser=batman touser=robin tables=list

===================================================================

1. jakarta 홈피에서 dbcp 관련 jar 를 다운 받는다.

여기 - > http://ftp.apache-kr.org/jakarta/commons

commons-collections-3.1.jar

commons-dbcp-1.2.1.jar

commons-pool-1.2.jar

===================================================================

2. ${WAS_HOME}/common/lib 에 위치 시키고 classespath 를 확인한다.

===================================================================

3. Init ( DBCPInit.java ) 파일 생성

    package com.zzang.db;

    import javax.servlet.http.HttpServlet;
    import javax.servlet.ServletConfig;
    import javax.servlet.ServletException;
    import java.util.StringTokenizer;

    public class DBCPInit extends HttpServlet {

        public void init(ServletConfig config) throws ServletException {
            try {
                String drivers = config.getInitParameter("jdbcdriver");
                StringTokenizer st = new StringTokenizer(drivers, ",");
                while (st.hasMoreTokens()) {
                    String jdbcDriver = st.nextToken();
                    Class.forName(jdbcDriver);
                }

                Class.forName("org.apache.commons.dbcp.PoolingDriver");

                System.setProperty("org.xml.sax.drvier",
                       "org.apache.crimson.parser.XMLReaderImpl");
            } catch(Exception ex) {
                throw new ServletException(ex);
            }
        }
    }

===================================================================

4. web.xml 설정 하기

${WAS_HOME}/webapps/ROOT/WEB-INF/web.xml

<!-- DBCP config  start -->
  <servlet>
     <servlet-name>DBCPInit</servlet-name>
     <servlet-class>com.zzang.db.DBCPInit</servlet-class>
     <load-on-startup>1</load-on-startup>
     <init-param>
        <param-name>jdbcdriver</param-name>
        <param-value>oracle.jdbc.driver.OracleDriver</param-value>
     </init-param>
  </servlet>

<!-- DBCP config  end -->

===================================================================

5. config 파일 생성

${WAS_HOME}/webapps/ROOT/WEB-INF/classes/pool.jocl

<object class="org.apache.commons.dbcp.PoolableConnectionFactory" xmlns="http://apache.org/xml/xmlns/jakarta/commons/jocl">

        <object class="org.apache.commons.dbcp.DriverManagerConnectionFactory">
        <string value="jdbc:oracle:thin:@localhost:1521:ora92" />
        <string value="userid" />
        <string value="userpw" />
        </object>

      <object class="org.apache.commons.pool.impl.GenericObjectPool">
        <object class="org.apache.commons.pool.PoolableObjectFactory" null="true" />
        <int value="10" />  <!-- maxActive -->
        <byte value="1" />  <!-- whenExhaustedAction -->
        <long value="20000" /> <!-- maxWait -->
        <int value="100" /> <!-- maxIdle -->
        <int value="10" /> <!-- minIdle -->
        <boolean value="true" /> <!-- testOnBorrow -->
        <boolean value="true" /> <!-- testOnReturn -->
        <long value="5000" /> <!-- timeBetweenEvctionRunsMillis -->
        <int value="5" /> <!-- numTestsPerEvictionRun -->
        <long value="5000" /> <!-- minEvictableIdleTimeMillis -->
        <boolean value="true" /> <!-- testWhileIdle -->
      </object>

      <object class="org.apache.commons.pool.impl.GenericKeyedObjectPoolFactory" null="true" />

      <string null="true" />

      <boolean value="false" />

      <boolean value="true" />

</object>

===================================================================

6. WAS 재구동 & 테스트

        //initial
        Connection conn = null;
        Statement stmt = null;
        ResultSet rs = null;

        try {

                //get Connnection
                conn = DriverManager.getConnection("jdbc:apache:commons:dbcp:/pool");
                conn.setAutoCommit(false);
                stmt = conn.createStatement();

                .................

        } catch(Exception ex) {
                conn.rollback();
                ex.printStackTrace();
                out.println(ex.toString());
        } finally {
                if ( rs != null ) try { rs.close(); } catch( Exception exf ){}
                if ( stmt != null ) try { stmt.close(); } catch( Exception exf ){}
                if ( conn != null ) try { conn.close(); } catch( Exception exf ){}
        }

===================================================================

7. Tip

 - 5번의 pool.jocl 파일을 여러개 생성하면, DB개정을 여러개 가져갈 수 있쥐요~

 - 5번의 maxWait 값이 작으면 에러가 발생할 수 있다.( 정확한 에럼 메세지가 기억 안남 ^^;;;)

===================================================================

50만건이 넘는 데이타를 읽어서 insert 할 일이 생겼는데 보통의 방법으로 하니 톰켓이 계속 죽어 버리는 일이 생겼습니다.

자바 API를 보니 이러한 방법이 있더군요...

 

try {
            StringBuffer query = new StringBuffer();
            query.append("INSERT INTO ABT231 ");
            query.append("(customer_no, item_cd, occur_amt, reason_cd, register_ymd, register_no) ");
            query.append(" VALUES (?, ?, ?, '9', ?, ?) ");

            conn = getConnection();
            conn.setAutoCommit(false);

            pstmt = conn.prepareStatement(query.toString());
            Iterator iter = m_abt231InsertList.iterator();
            int count = 0;

            while( iter.hasNext() ) {
                m_abt231 = (Abt231) iter.next();
                pstmt.setInt(1, m_abt231.getCustomerNo());
                pstmt.setString(2, m_abt231.getItemCd());
                pstmt.setLong(3, m_abt231.getOccurAmt());
                pstmt.setString(4, s_magamCurrentTime);
                pstmt.setInt(5, Integer.parseInt(s_workCd));
                pstmt.addBatch();
                count++;
                if( (count % 10000) == 0){
                    System.out.println(count + "건 처리중");
                    pstmt.executeBatch();
                }
            }

            pstmt.executeBatch();
            conn.commit();
}

여기서는 full=y를 사용했을 경우만 생각해본다.
이는 DBA권한을 가진 사람이 모든 데이터베이스에 대해 백업을 실시할 때 사용한다.
full옵션을 사용할 수 있으려면 정확히 EXP_FULL_DATABASE 권한을 가져야한다.
export유틸리티를 사용하기 위해 catexp.sql이라는 유틸리티스크립트를 실행해야 하는데
이것은 catalog.sql이 실행되면서 부수적으로 실행되므로 그리 신경쓸 필요는 없다.

export는 논리적인 백업으로 완벽한 복구에 사용되기에는 무리이다.
많은(아주 많은 것 같다.) 사이트들이 백업수단으로 export를 사용하는 것 같다.
사용하기 쉬운 것과 짧은 시간에 할 수 있다는 것이 그 이유가 아닌가 생각된다.
개인적인 생각에는 export의 경우, 각 schema에 대한 백업수단(export시 owner옵션을 사용한 백업)으로서만
사용하는 것이 좋을것 같다.

full=y를 사용할 경우 inctype으로 complete, cumulative, incremental 3가지가 사용될 수 있다.
complete는 무조건 전체 데이터베이스를 백업.
cumulative는 complete이후 변경된 데이블에 대해서만 백업
incremental는 위 2가지 백업뒤 변경된 놈들에 대해 백업

cumulative는 incremental로 생성되는 파일수를 줄여주는 역활을 한다.
즉, 이전에 incremental백업을 2번한 상황에서 comulative백업을 하면 이전의 2개의 incremental백업은
cumulative백업으로 커버가 된다. 즉, 이전 2개의 incremental백업은 복구시 필요치 않고, cumulative백업
하나만 있으면 되는 것이다.

2주일간의 백업정책을 세운다면,
처음 complete백업을 받는다.
일별로 incremental백업을 받는다.
하지만, 수요일, 일요일은 incremental백업대신 cumulative백업을 한다.
2주가 되는 일요일에 complete백업을 한다.

복구의 순서는,
가장 최근의 complete백업한 것을 resotre한다.
가장 최근의 complete백업후에 발생한 cumulative백업들을 restore한다.
(cumulative백업이 없다면 incremental백업으로 대체)
위에서 행한 cumulative백업들중 가장 최근의 cumulative백업후의 incremental백업들을
가장 오래된 것부터 차례로 restore한다.

정리하면,
complete의 경우 주말에 한번 정도
incremental의 경우 날마다
cumulative의 경우 주중에 한번(수요일정도)

오라클이 complete백업후의 변동된 사항을 어떻게 알수 있을까?
당연히 내부적인 테이블에 이런 정보를 저장하고 있다.
언제 complete, cumulative백업들이 발생했는가등등.. 문서하단에 자세히 설명하겠다.

[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=complete

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:35:28 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Export done in UTF8 character set and KO16KSC5601 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. . exporting table                    DEF$_AQCALL          0 rows exported
. . exporting table                   DEF$_AQERROR          0 rows exported
. . exporting table                  DEF$_CALLDEST          0 rows exported
. . exporting table               DEF$_DEFAULTDEST          0 rows exported
. . exporting table               DEF$_DESTINATION          0 rows exported
. . exporting table                     DEF$_ERROR          0 rows exported
. . exporting table                       DEF$_LOB          0 rows exported
. . exporting table                    DEF$_ORIGIN          0 rows exported
. . exporting table                DEF$_PROPAGATOR          0 rows exported
. . exporting table       DEF$_PUSHED_TRANSACTIONS          0 rows exported
. . exporting table                  DEF$_TEMP$LOB          0 rows exported
. . exporting table                           HELP        816 rows exported
. . exporting table        SQLPLUS_PRODUCT_PROFILE          0 rows exported
. about to export OUTLN's tables via Conventional Path ...
. . exporting table                            OL$          0 rows exported
. . exporting table                       OL$HINTS          0 rows exported
. about to export DBSNMP's tables via Conventional Path ...
. about to export TRACESVR's tables via Conventional Path ...
. about to export KANG's tables via Conventional Path ...
. . exporting table                           TEST          1 rows exported
. exporting referential integrity constraints
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting triggers
. exporting snapshots
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting user history table
. exporting default and system auditing options
. exporting statistics
Export terminated successfully without warnings.

[kang@piruks kang]$ ls -l
total 155
-rw-rw-r--    1 kang     kang       155648 11월  2 15:37 expdat.dmp
drwxrwxr-x    4 kang     kang         1024 10월 27 13:02 public_html/
drwxrwxr-x    2 kang     kang         1024 10월 15 12:54 test/

complete로 백업후 바로 cumulative로 다시 실행해 봤다.
역시 변경사항이 없으니 .. 별 일은 하지 않는것 같다.
백업받을 파일을 지정하지 않으면 complete로 백업받은 파일을 덮어쓰니까
다른 곳으로 미리 옮겨놓는 것이 좋을 것 같다.
[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=cumulative

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:39:22 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Export done in UTF8 character set and KO16KSC5601 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. about to export OUTLN's tables via Conventional Path ...
. about to export DBSNMP's tables via Conventional Path ...
. about to export TRACESVR's tables via Conventional Path ...
. about to export KANG's tables via Conventional Path ...
. exporting referential integrity constraints
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting triggers
. exporting snapshots
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting user history table
. exporting default and system auditing options
. exporting information about dropped objects
. exporting statistics
Export terminated successfully without warnings.

파일의 크기가 줄었다.
[kang@piruks kang]$ ls -l                                              
total 27
-rw-rw-r--    1 kang     kang        24576 11월  2 15:42 expdat.dmp
drwxrwxr-x    4 kang     kang         1024 10월 27 13:02 public_html/
drwxrwxr-x    2 kang     kang         1024 10월 15 12:54 test/

역시 아무런 변경없이 incremental로 다시 실행해봤다.
생각한대로 별 일은 하지 않는다. 파일크기도 cumulative와 같았다.
[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=incremental

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:40:29 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Export done in UTF8 character set and KO16KSC5601 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. about to export OUTLN's tables via Conventional Path ...
. about to export DBSNMP's tables via Conventional Path ...
. about to export TRACESVR's tables via Conventional Path ...
. about to export KANG's tables via Conventional Path ...
. exporting referential integrity constraints
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting triggers
. exporting snapshots
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting user history table
. exporting default and system auditing options
. exporting information about dropped objects
. exporting statistics
Export terminated successfully without warnings.

[kang@piruks kang]$ ls -l                                               
total 27
-rw-rw-r--    1 kang     kang        24576 11월  2 15:43 expdat.dmp
drwxrwxr-x    4 kang     kang         1024 10월 27 13:02 public_html/
drwxrwxr-x    2 kang     kang         1024 10월 15 12:54 test/


음.. 데이터를 하나 넣어보고 다시 해보자
[kang@piruks kang]$ sqlplus kang/xxxxxx                             

SQL*Plus: Release 8.1.6.0.0 - Production on Thu Nov 2 15:46:34 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to:
Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production

SQL> insert into test values ('하하하', 29);

1 row created.

SQL> exit
Disconnected from Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production

incremental로 다시 백업
물론 변경사항이 있으니 뭔가 할 거다.
test테이블에 대해 2개의 row를 백업받았다.
export는 row단위로 백업하는 것이 아니기때문에 이는 test라는 테이블전체를 백업받은 것이다.
다시 한번 말하는데 export는 변경된 테이블에 대해 백업을 실시한다.
[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=incremental

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:48:11 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Export done in UTF8 character set and KO16KSC5601 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. about to export OUTLN's tables via Conventional Path ...
. about to export DBSNMP's tables via Conventional Path ...
. about to export TRACESVR's tables via Conventional Path ...
. about to export KANG's tables via Conventional Path ...
. . exporting table                           TEST          2 rows exported
. exporting referential integrity constraints
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting triggers
. exporting snapshots
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting user history table
. exporting default and system auditing options
. exporting information about dropped objects
. exporting statistics
Export terminated successfully without warnings.
[kang@piruks kang]$ ls -l
total 27
-rw-rw-r--    1 kang     kang        24576 11월  2 15:48 expdat.dmp
drwxrwxr-x    4 kang     kang         1024 10월 27 13:02 public_html/
drwxrwxr-x    2 kang     kang         1024 10월 15 12:54 test/

이번에는 좀더 데이터를 많이 집어넣어 보자
[kang@piruks kang]$ sqlplus kang/xxxxxx

SQL*Plus: Release 8.1.6.0.0 - Production on Thu Nov 2 15:49:16 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to:
Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production

SQL> insert into test values ('&a', 30);
Enter value for a: 슈퍼맨
old   1: insert into test values ('&a', 30)
new   1: insert into test values ('슈퍼?, 30)

1 row created.

SQL> /
Enter value for a: 배트맨
old   1: insert into test values ('&a', 30)
new   1: insert into test values ('배트?, 30)

1 row created.

SQL> /
Enter value for a: vicman
old   1: insert into test values ('&a', 30)
new   1: insert into test values ('vicman', 30)

1 row created.

SQL> quit
Disconnected from Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=incremental

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:50:24 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Export done in UTF8 character set and KO16KSC5601 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. about to export OUTLN's tables via Conventional Path ...
. about to export DBSNMP's tables via Conventional Path ...
. about to export TRACESVR's tables via Conventional Path ...
. about to export KANG's tables via Conventional Path ...
. . exporting table                           TEST          5 rows exported
. exporting referential integrity constraints
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting triggers
. exporting snapshots
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting user history table
. exporting default and system auditing options
. exporting information about dropped objects
. exporting statistics
Export terminated successfully without warnings.

입력한 데이터가 별로 되지 않아 백업파일의 크기에 영향이 없다. 쩝..
[kang@piruks kang]$ ls -l
total 28
-rw-r--r--    1 kang     kang            5 11월  2 15:51 HantermLog.GDPo9B
-rw-rw-r--    1 kang     kang        24576 11월  2 15:50 expdat.dmp
drwxrwxr-x    4 kang     kang         1024 10월 27 13:02 public_html/
drwxrwxr-x    2 kang     kang         1024 10월 15 12:54 test/

incremental과 cumulative의 차이점이라고 발견할 수 있는 것은 한가지다.
cumulative가 incremental로 백업받은 것을 다시 백업할 수 있지만,
incremental백업은 cumulative로 백업받은 것을 다시 백업할 수 없다는 것이다.
음.. 중요한 사실인가? 밑에 cumulative와 incremental의 예를 보면 알 수 있을 것이다.
[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=cumulative

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:51:48 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Export done in UTF8 character set and KO16KSC5601 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. about to export OUTLN's tables via Conventional Path ...
. about to export DBSNMP's tables via Conventional Path ...
. about to export TRACESVR's tables via Conventional Path ...
. about to export KANG's tables via Conventional Path ...
. . exporting table                           TEST          5 rows exported
. exporting referential integrity constraints
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting triggers
. exporting snapshots
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting user history table
. exporting default and system auditing options
. exporting information about dropped objects
. exporting statistics
Export terminated successfully without warnings.

cumulative백업후 데이터베이스에 아무런 변경없는 상태에서 incremental백업은 무의미하다.
즉 cumulative가 받은 백업데이터를 백업하지 못한다.
[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=incremental

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:52:05 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Export done in UTF8 character set and KO16KSC5601 NCHAR character set

About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
. about to export SYSTEM's tables via Conventional Path ...
. about to export OUTLN's tables via Conventional Path ...
. about to export DBSNMP's tables via Conventional Path ...
. about to export TRACESVR's tables via Conventional Path ...
. about to export KANG's tables via Conventional Path ...
. exporting referential integrity constraints
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting triggers
. exporting snapshots
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting user history table
. exporting default and system auditing options
. exporting information about dropped objects
. exporting statistics
Export terminated successfully without warnings.




일반사용자는 데이터베이스 full백업이 불가능하다.
[kang@piruks kang]$ exp userid=kang/xxxxxx full=y inctype=incremental

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:43:53 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
EXP-00023: must be a DBA to do Full Database export
(2)U(sers), or (3)T(ables): (2)U >

EXP-00022: must be SYS or SYSTEM to do incremental export
EXP-00000: Export terminated unsuccessfully
[kang@piruks kang]$


full패러미터사용시 tables와 owner패러미터는 사용하지 못한다.
[kang@piruks kang]$ exp userid=system/xxxxxx full=y inctype=complete tables=kang.test

Export: Release 8.1.6.1.0 - Production on Thu Nov 2 15:45:55 2000

(c) Copyright 1999 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
EXP-00026: conflicting modes specified
EXP-00000: Export terminated unsuccessfully
[kang@piruks kang]$


incexp, incfil, incvid
sys계정에 보면, incexp, incfil, incvid테이블이 있다.
보통의 owner, table백업으로는 이 테이블들이 채워지지 않는다.
cumulative, incremental을 해야 이 놈들의  테이블이 채워진다.
백업을 하면 백업기록을 남겨야 incremental backup을 할 수 있는데 이 놈들이다.

incexp: export된 스키마들의 정보를 가짐(보통 무지하게 row가 많다)
incfil: incremental backup이 된 export파일들
incvid: 다음 export id를 가짐(즉, 지금 한게 id가 1이라면 다음은 2가 된다.)

exp userid=system/xxxx file=fullexp.dmp full=y inctype=complete
exp userid=system/xxxx file=cumexp.dmp full=y inctype=cumulative
exp userid=sys/xxxx file=incexp.dmp full=y inctype=incremental

이렇게 2번을 하고, DB 에서 조회

SQL> select * from incfil;

     EXPID EXPTYPE  EXPFILE                        EXPDATE   EXPUSER
---------- -------- ------------------------------ --------- ------------------------------
         1 X        fullexp.dmp                    12-JAN-01 SYSTEM
         2 C        cumexp.dmp                     12-JAN-01 SYSTEM
         3 I        incexp.dmp                     12-JAN-01 SYS

SQL> select * from incvid;

     EXPID
----------
         3


SQL> select * from incexp where rownum<5;

    OWNER# NAME                      TYPE# CTIME     ITIME          EXPID
---------- -------------------- ---------- --------- --------- ----------
         5 DEF$_AQCALL                   2 12-JAN-01 12-JAN-01          1
         5 DEF$_AQERROR                  2 12-JAN-01 12-JAN-01          1
         5 DEF$_CALLDEST                 2 12-JAN-01 12-JAN-01          1
         5 DEF$_DEFAULTDEST              2 12-JAN-01 12-JAN-01          1



------------------------------------------------------------------------------------------------

[엑스포트(Export)]

 

Export 유틸리티의 명령행 모드를 사용하여 데이터베이스 데이터를 운영 체제 파일로 복사할 수 있습니다. 이 파일은 Import 유틸리티에서만 읽을 수 있습니다.

예제

행을 포함하여 scott의 스키마에 속한 emp 및 dept 테이블을 포함하는 expincr1.dmp 엑스포트 파일을 생성합니다.

$ exp scott/tiger tables=(emp,dept) rows=y file=expincr1.dmp

행을 포함하여 scott의 스키마에 속한 모든 객체를 포함하도록 expdat.dmp라는 빠른 엑스포트 파일을 생성합니다.

$ exp system/manager owner=SCOTT DIRECT=Y

ts_emp 테이블스페이스에 속한 모든 객체의 정의를 포함하는 expdat.dmp 엑스포트 파일을 생성하고 ts_emp.log 로그 파일을 생성합니다.

$ exp system/manager TRANSPORT_TABLESPACE=y TABLESPACES=(ts_emp) LOG=ts_emp.log

마지막 누적 또는 완전 엑스포트 이후 데이터베이스에서 수정된 모든 정의 및 데이터를 포함하는 expcum1.dmp 엑스포트 파일을 생성합니다.

$ exp system/manager FULL=y INCTYPE=cumulative FILE=expcum1.dmp

참고: 명령행 모드 옵션은 대화식 모드 옵션과 유사합니다.

 

엑스포트 매개변수

매개변수	설명
USERID	엑스포트할 스키마 객체의 사용자 이름/암호
FILE	출력 파일 이름
ROWS	엑스포트 파일에 테이블 행을 포함시킬 것인지 여부: (Y)es/(N)o
FULL	전체 데이터베이스를 엑스포트할 것인지 여부: (Y)es/(N)o
OWNER	엑스포트할 사용자: 사용자 이름
TABLES	엑스포트할 테이블: 테이블 목록
INDEXES	인덱스를 엑스포트할 것인지 여부: (Y)es/(N)o
DIRECT	직접 모드 엑스포트 지정 여부: (Y)es/(N)o
INCTYPE	엑스포트 레벨 유형
PARFILE	매개변수가 지정된 파일 이름
HELP	대화식 모드에서 엑스포트 매개변수 표시(Y)
LOG	정보 및 오류 메시지용 파일 이름
CONSISTENT	엑스포트 중에 데이터가 갱신될 경우 데이터베이스의 읽기 일관성 뷰를 제공할 것인지 여부: (Y)es/(N)o
BUFFER	데이터 버퍼 크기(바이트): (정수)
TRANSPORT_TABLESPACE	이동 가능한 테이블스페이스 메타 데이터의 엑스포트 설정(릴리스 8.1 전용)
TABLESPACES	이동할 테이블스페이스(릴리스 8.1 전용)
POINT_IN_TIME_RECOVER	Export 유틸리티가 Oracle 데이터베이스에 있는 하나 이상의 테이블스페이스를 엑스포트할지 여부 표시(릴리스 8.0 전용)
RECOVERY_TABLESPACES	포인트 인 타임 복구를 사용하여 복구할 테이블스페이스 지정(릴리스 8.0 전용) Oracle Server Readme, Release 8.0.4 참조
COMPRESS	하나의 확장 영역에 모든 데이터를 포함시킬지 여부 지정: (Y)es/(N)o

참고: 위에 나열한 매개변수는 모든 Export 유틸리티 매개변수의 전체 목록이 아니며 DBA가 복원을 위해 자주 사용하는 매개변수입니다

 

 

[임포트(import)]

 

expincr1.dmp 엑스포트 파일을 사용하여 행을 포함해 emp 및 dept 테이블을 scott 스키마로 임포트합니다.

$ imp scott/tiger tables=(emp,dept) rows=y file=expincr1.dmp

expincr1.dmp 엑스포트 파일을 사용하여 행을 포함해 Scott 스키마에 속한 모든 객체를 임포트합니다.

$ imp system/manager FROMUSER=scott file=expincr1.dmp

expdat.dmp 엑스포트 파일을 사용하여 ts_emp 테이블스페이스에 속한 모든 객체의 정의를 임포트합니다.

$ imp system/manager TRANSPORT_TABLESPACE=y TABLESPACES=ts_emp

참고: 명령행 모드 옵션은 대화식 모드 옵션과 유사합니다.

 

임포트 매개변수

매개변수	설명
USERID	임포트할 스키마 객체의 사용자 이름/암호
FILE	입력 파일의 이름. 유효한 Export 유틸리티 파일이어야 합니다.
ROWS	임포트 파일에 테이블 행을 포함시킬지 여부
IGNORE	해당 객체가 존재할 경우 생성 오류 무시
FULL	전체 파일 임포트
TABLES	임포트할 테이블
INDEXES	인덱스를 임포트할 것인지 여부
INCTYPE	증분 임포트 유형 지정. SYSTEM 및 RESTORE 옵션이 있습니다.
PARFILE	매개변수 사양 파일
HELP	대화식 모드에서 엑스포트 매개변수 표시
LOG	정보 및 오류 메시지용 파일
DESTROY	데이터베이스를 구성하는 기존 데이터 파일을 재사용해야 할지 여부 지정
FROMUSER	임포트할 객체를 포함하는 스키마 목록
TOUSER	임포트할 스키마를 소유한 사용자 이름 목록 지정
INDEXFILE	인덱스 생성 명령을 받을 파일 지정
TRANSPORT_TABLESPACE	엑스포트 파일에 있는 이동 가능한 테이블스페이스 메타 데이터를 Import 유틸리티가 임포트하도록 명령
TABLESPACES	데이터베이스로 이동할 테이블스페이스 목록
DATAFILES	데이터베이스로 이동할 데이터 파일 목록
TTS_OWNERS	이동 가능한 테이블스페이스 집합에 있는 데이터를 소유한 사용자 목록
POINT_IN_TIME_RECOVER	Import 유틸리티가 나머지 데이터베이스에 영향을 주지 않고 Oracle 데이터베이스에 있는 하나 이상의 테이블스페이스를 이전 시점으로 복구할지 여부 표시(릴리스 8.0 전용)

참고: 위에 나열한 매개변수는 모든 Import 유틸리티 매개변수의 전체 목록이 아니며 DBA가 복원 작업을 위해 자주 사용하는 매개변수입니다.