pat98's always & forever

* Goal
-----------------------------------------------------------------------------------------------------
Your production database has bi-annual or annual purging programs which generate huge redo. Due to this requirement, your undo tablespace grows rapidly and occupies most of the space on file system.
The purging process is run only few times a year. So would not like to keep the huge undo datafile in your database throughout the year. You don't want to buy additional disks unnecessarily.

You have created an undo tablespace with datafiles as AUTOEXTEND ON MAXSIZE UNLIMITED to avoid Error: ORA 1651 : unable to extend save undo segment by <num> in tablespace <name>.

You have tried "alter database datafile .. resize" which always fails with Error: ORA 3297 : file contains <num> blocks of data beyond requested RESIZE value.

You want to shrink the datafile to utilize the disk space for other tablespaces or other purposes.
* Solution
-----------------------------------------------------------------------------------------------------
-- Create new undo tablespace with smaller size.
SQL> create undo tablespace UNDO_RBS1 datafile 'undorbs1.dbf' size 100m;

-- Set new tablespace as undo_tablespace
SQL> alter system set undo_tablespace=undo_rbs1;

-- Drop the old tablespace.
SQL> drop tablespace undo_rbs0 including contents.

NOTE: Dropping the old tablespace may give ORA-30013 : undo tablespace '%s' is currently in use. This error indicates you must wait for the undo tablespace to become unavailable. In other words, you must wait for existing transaction to commit or rollback.

Points to Consider:

-  The value for undo_retention also has a role in growth of undo tablespace. If there is no way to get the undo space for a new transaction, then the undo space (retention) will be reused. But, if the datafiles for undo tablespace are set to auto extensible, it will not reuse the space. In such scenarios new transaction will allocate a space and your undo tablespace will start growing.

-  Is big really bad?  Overhead on larger file/tablespaces can theoretically impact the database and the OS.  With a small file, the OS would have to do minimal I/O.  Oracle would be able to cache the whole file and there would be less segments to manage.  With AUM you get bitmapped files and all its (space management) performance benefits-- (number of) undo segments are automatically managed and are not related to the size of the tablespace.  With the bigger file/tablespace you will have other overhead--e.g. backup will take longer--but as far as the undo management there should be no performance impact just because the file/tbs is bigger.  That said, it is important to monitor systems (e.g. with statspack) and watch for environment-specific issues.

ReferencesNote 135090.1 - Managing Rollback/Undo Segments in AUM (Automatic Undo Management)
ErrorsORA-30013 undo tablespace '%s' is currently in use

Oracle 10g 의 archive mode

10g에서는 약간 parameter 값이 틀린데요.
ORA-32006,ORA-19905 이 에러 뜨면 8i, 9i 쓰시던 분들이 약간 당황하는 문제인데 알고 나면 별거 없지요.
==============================================================================================

1. 일단  LOG_ARCHIVE_START parameter 가 없어졌구요.
2. LOG_ARCHIVE_FORMAT 은 %s,%t,%r  형태가 되어야 합니다.
3. LOG_ARCHIVE_DEST 은 당연히 있어야 겠죠? 10개까지 지정할수 있습니다.
ex) *.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle10GDB\database\archive1'
     *.LOG_ARCHIVE_DEST_2='LOCATION=C:\oracle10GDB\database\archive2'

여기서 s,t, r의 의미는  %s log sequence number
                               %t thread number,
                               %r resetlogs 

Oracle 10g에서 vip 를 바꾸어보자.

vip 변경
=================================================================
ex)
srvctl stop database -d promise
srvctl stop nodeapps -n promise1
srvctl stop nodeapps -n promise2
crsctl stop crs (root user)

srvctl modify nodeapps -n mynode1 -A 138.2.166.152/255.255.255.0/lan1  (root user)

crsctl start crs (root user)
srvctl start nodeapps -n promise1
srvctl start nodeapps -n promise2
srvctl start database -d promise

================================================================
vip 이중화
================================================================
srvctl modify nodeapps -n mynode1 -A 138.2.166.152/255.255.255.0/lan1/lan2  (root user로) <- 요기 파란색부분이 중요함..(첫번째 놈,두번째 놈 순서대로)

MC/SG lancard failover 구성해 놓고 oracle에서 lancard failover 셋팅해 놓지 않으면 무용지물이라고 함.

ex)
srvctl stop database -d promise
srvctl stop nodeapps -n promise1
srvctl stop nodeapps -n promise2
crsctl stop crs (root user)

srvctl modify nodeapps -n mynode1 -A 138.2.166.152/255.255.255.0/lan1\lan2  (root user)
srvctl modify nodeapps -n mynode1 -A 138.2.166.153/255.255.255.0/lan1\lan2  (root user)

crsctl start crs (root user)
srvctl start nodeapps -n promise1
srvctl start nodeapps -n promise2
srvctl start database -d promise

Unix 에서는 rm 으로 삭제하면 simple 하게 없어지지만, windows 는 지워도 registry에 정보가 남아서 Uninstaller로 지운후 다시 설치 해도 설치가 안되는 경우가 종종 있죠? 이렇게 하면 99% 깨끗하게 지워짐니다. windows 에서 재설치 때문에 고민하시는 분들 이렇게 한번 해 보세요.
=====================================================================================================

WIndows NT, 2003 의 경우
1. 시작-> 실행-> regedit을 기동하여
  HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE 폴더 전체를 삭제한다.
2. HKEY_LOCAL_MACHINE\SOFTWARE\odbc 를 삭제한다.
3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ 에서 oracle로
  시작되는 폴더들을 삭제한다.
4. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
  Application\ 에서 oracle로 시작되는 폴더들을 삭제한다.
5. regedit을 종료한다.
6. 설정-> 제어판 -> 시스템을 실행하여 환경 tab에서
7. autoexec.bat 화일에서 %ORACLE_HOME%\bin과 JRE path를 remove한다.
8. <system_drive>: \Winnt\Profiles\All Users\시작메뉴\Programs\Oracle
  폴더를 삭제한다.
9. <system_drive>: \Program Files\Oracle 폴더를 삭제한다.
10. 시스템을 재기동시킨다.
11. Oracle Home directory를 삭제한다.
    (HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ORACLE_HOME 에서 확인 가능).

* CWI32.DLL 파일 삭제가 안될경우에는 재부팅시 F8 누르고 안전모드로 부팅해서 삭제하면 된다.

오라클 export & import 를 할때, 어떤 버전끼리 되는지 고민되는 때가 있는데, 이에 대한 문서를 보면 도움이 된다..

[Metalink 문서번호 132904.1]

PURPOSE
-------
This article describes several issues related with the compatibility of the
different versions of the Oracle EXPORT and IMPORT utilities.

SCOPE & APPLICATION
-------------------
The article is intended for users of the Oracle7, Oracle8, Oracle8i,
Oracle9i, and Oracle10g databases who wish to use the EXPORT and IMPORT
utilities to export data from an Oracle database release x and import
this data into an Oracle database release y.  The article gives information
which version of the utility to use when performing the export and import,
and how to prepare the Oracle data dictionary before exporting the data.
For the transportable tablespaces export/import, see:
Note 291024.1 "Compatibility and New Features when Transporting Tablespaces
with Export and Import"

SUMMARY
-------
1. Export the data with the Export utility of the lowest database version
  involved.

2. Import the data with the Import utility of the target database.

3. Running an Oracle7 Export utility against an Oracle9i database is not
  supported.

COMPATIBILITY MATRIX FOR EXPORT & IMPORT BETWEEN DIFFERENT ORACLE VERSIONS
--------------------------------------------------------------------------

Introduction.
-------------

With the Oracle EXPORT and IMPORT utilities you can transfer data objects
between Oracle databases, even if they reside on platforms with different
hardware and software configurations.

The Oracle EXPORT utility extracts the object definitions and table data
from an Oracle database and stores them in an Oracle binary-format export
dump file located typically on disk or tape.  The files can then be
transferred using FTP or physically transported (in the case of tape)
to a different site.  When transferring the export dump file over a network,
the file has to be transmitted in binary mode.  Transmitting export files in
character mode (ASCII) causes errors when the file is imported, resulting
most likely in: IMP-9 or IMP-10, followed by IMP-0.

The Oracle IMPORT utility reads the object definitions and table data
from the export dump file and then inserts the information into the Oracle
database.

Starting with Oracle10g Release 1 (10.1.0.x) we have introduced the new
Export DataPump (expdp) and Import DataPump (impdp) utilities.  Export
dumpfiles created with Export DataPump can only be read by Import DataPump.
And export dumpfiles created with the original Export utility cannot be read
by the Import DataPump client.

Data Dictionary Views.
----------------------

Before using the EXPORT or IMPORT utility, the Data Dictionary has to be
prepared with the views that are needed by these utilities.  This can be done
by running the script:

  UNIX   : SQL> @$ORACLE_HOME/rdbms/admin/catexp.sql

  Windows: SQL> @%ORACLE_HOME%\rdbms\admin\catexp.sql

This script CATEXP.SQL has to be run by the user SYS.  The script is called
automatically by the CATALOG.SQL script.  Both scripts CATEXP.SQL and
CATALOG.SQL need to be run only once on a database.  Normally, you never
need to run it again before you perform an export or import (the errors
EXP-24 or IMP-23 indicate that the views are not correct anymore).

The script CATEXP.SQL performs the following tasks to prepare the database
for an export and/or import:

- create the required export and import views in the data dictionary;
- create the EXP_FULL_DATABASE role and the IMP_FULL_DATABASE role;
- assign all necessary privileges to the EXP_FULL_DATABASE role and the
  IMP_FULL_DATABASE role;
- assign EXP_FULL_DATABASE and IMP_FULL_DATABASE to the DBA role;
- update table sys.props$ with the version of the export and import views
  (see the notes at the end of the article).

When creating an Oracle7 export file from an Oracle8/8i database by running
the Oracle7 EXPORT utility against the Oracle8/8i server (see details below),
the user SYS must have run the CATEXP7.SQL script on the Oracle8/8i database:

  UNIX   : SQL> @$ORACLE_HOME/rdbms/admin/catexp7.sql

  Windows: SQL> @%ORACLE_HOME%\rdbms\admin\catexp7.sql

This script creates the export views that make the database look, to EXPORT,
like an Oracle7 release database.  This means that the views will not see any
new Oracle8/8i specific objects, so the export file can be imported
without problems in the Oracle7 database.

Keep in mind that both the scripts CATEXP.SQL and CATEXP7.SQL only need to
be run once: CATEXP.SQL creates the exu8% views which are used by the
Oracle8/8i/9i/10g EXPORT utilities, and CATEXP7.SQL creates the exu7% views
which are used by the Oracle7 EXPORT utilities.
So if both scripts have been run by SYS, you do not need to run them again.

The procedure mentioned above, also applies for creating an Oracle6 export
dump file from an Oracle7 database.  In this case the user SYS must have run
the CATEXP6.SQL script on the Oracle7 database.

Note that running an Oracle7 Export utility against Oracle9i database is not
supported: in a downgrade scenario, we only support one functional release
back. This also means that running an Oracle8 Export utility against an
Oracle10g database is not supported (currently, it is only supported to run
the Oracle8i 8.1.7 export utility or higher against the Oracle10g database).

Database Migration to Oracle9i / Oracle10g with a full database export/import.
------------------------------------------------------------------------------

If the database is migrated to Oracle9i or Oracle10g, there is a limitation
regarding a direct upgrade with a full database export and a full database
import.  This *only* applies to the FULL mode (FULL=Y) of the database
import from an export dump file created in FULL mode.
It remains possible to:
- import data in USER mode (FROMUSER=... TOUSER=...)
- import data in TABLE mode (FROMUSER=... TABLES=...)
- export and import data in TABLESPACE mode (TRANSPORT_TABLESPACE=Y)
Note that an import client is technically capable to read export dump files
created by EXPORT release 5.1.22 and higher (up to same version).
This migration limitation is related to the available upgrade paths
as described in the Migration manual. The main reason for only supporting
a direct migration from the terminal release of a major version (like 8.1.7
for Oracle8i), to a new major version (like 9.2.0 for Oracle9i) is the fact
that this terminal release was the latest release. I.e.:
- for Oracle7, the release 7.3.4. is the latest released version,
- for Oracle8, the release 8.0.6. is the latest released version,
- for Oracle8i, the release 8.1.7. is the latest released version.
Any known problems (and in particular data dictionary related issues)
that were identified in the earlier versions of the major release
(like 8.1.5 and 8.1.6) are very likely fixed in the latest release (8.1.7)
or with the latest patchset for that release (8.1.7.4.0).
See also sections 'Basic Compatibility' and 'Limitations' below for details.

1. Migration to Oracle9i release 2 - 9.2.0.x :
  -------------------------------------------
  Direct migration with a full database export and full database import
  is only supported if the source database is:
  - Oracle7 : 7.3.4
  - Oracle8 : 8.0.6
  - Oracle8i: 8.1.7
  - Oracle9i: 9.0.1

2. Migration to Oracle10g release 1 - 10.1.0.x :
  ---------------------------------------------
  Direct migration with a full database export and full database import
  is only supported if the source database is:
  - Oracle8 : 8.0.6
  - Oracle8i: 8.1.7
  - Oracle9i: 9.0.1 or 9.2.0

3. Migration to Oracle10g release 2 - 10.2.0.x :
  ---------------------------------------------
  Note that you must first apply the specified minimum patch release
  (or any higher patch release) !
  Direct migration with a full database export and full database import
  is only supported if the source database is:
  - Oracle8i :  8.1.7.4
  - Oracle9i :  9.0.1.4 (or higher) or 9.2.0.4 (or higher)
  - Oracle10g: 10.1.0.2 (or higher)

Examples:
1. From 8.1.7.4 to 9.2.0.7: Full database export with the 8.1.7.4 export
  utility, and full database import with the 9.2.0.7 import utility is
  a supported migration method.

2. From 8.0.5.0 to 10.1.0.2: Full database export with the 8.0.5.0 export
  utility, and full database import with the 10.1.0.2 import utility is
  *NOT* a supported migration method.
  Possible alternatives:
  a. First upgrade the 8.0.5.0 database to 8.0.6.0, apply latest patchset
     8.0.6.3 and afterwards you can migrate with a full database export
     with the 8.0.6.3 export utility, and a full database import with the
     10.1.0.2 import utility.
  b. Or do a full database export with the 8.0.5.0 export utility,
     pre-create the users in the Oracle10g datatabase, and do a schema level
     import with the 10.1.0.2 import utility.

3. From 9.2.0.1 to 10.2.0.1: First apply the 9.2.0.4 patchset (or any higher
  patchset release, such as 9.2.0.7). Full database export with the 9.2.0.4
  export utility (resp. 9.2.0.7), and full database import with the 10.2.0.1
  import utility is a supported migration method.

Basic Compatibility.
--------------------

Definition Source database = the database where the data is exported from.
Definition Target database = the database where the data is imported into.

1) Always use a version of the EXPORT utility that is equal to the
  lowest version of either the source or the target database.
  This means:
  a) When creating an export dump file for an import into a higher release
     database (e.g.: from Oracle8i to Oracle9i), use a version of the
     EXPORT utility that is equal to the version of the source database
     (= lowest version = Oracle8i in this case).
     The export fails if you use a higher release export version.
     For example, if you use the export 9.0.1 utility the export data
     from an 8.1.7 database, you will get the errors:
        EXP-56 Oracle error 942 encountered
        ORA-942 table or view does not exist
        EXP-0 Export terminated unsuccessfully
     Solution: use the lowest release export utility (8.1.7 in this case).
  b) When creating an export dump file for an import into a lower release
     database (e.g.: from Oracle9i to Oracle8i), use a version of
     the EXPORT utility that is equal to the version of the target database
     (= lowest version = Oracle8i in this case).
     (1) When creating an Oracle6 export file from an Oracle7 database by
         running the Oracle6 EXPORT utility against the Oracle7 server,
         the user SYS must first run the CATEXP6.SQL script on the Oracle7
         database. This script creates the export views that make the
         database look, to EXPORT, like an Oracle6 release database.
     (2) When creating an Oracle7 export file from an Oracle8/8i database
         by running the Oracle7 EXPORT utility against the Oracle8/8i
         server, the user SYS must first run the CATEXP7.SQL script on the
         Oracle8/8i database. This script creates the export views that
         make the database look, to EXPORT, like an Oracle7 release
         database.
     (3) When creating an Oracle8/8i export file from an Oracle9i database
         by running the Oracle8/8i EXPORT utility against the Oracle9i
         server, you do not have to take any special steps. I.e., you do
         not need to run the 8i version of catexp.sql against the 9i database.
         You only need to run the 8i exp executable against the 9i database.
         Be aware that several Oracle9i specific features are not
         supported/exported (e.g. no LOBs and objects are exported when
         using DIRECT=YES).  See the "Oracle9i Database Utilities" manual
         for a complete list of these restrictions).
2) With some patchsets the data dictionary export views are also changed.
  As a result it will not be possible to run this patched Export utility
  against an unpatched database. Therefore the same basic rule also applies
  to the patchset release: Export the data with the Export utility of the
  lowest database version involved.
  Example: an export with 9.2.0.5 export client from a 9.2.0.1 database can
  give the errors:
     EXP-00008: ORACLE error 942 encountered
     ORA-00942: table or view does not exist
     EXP-00024: Export views not installed, please notify your DBA
     EXP-00000: Export terminated unsuccessfully
  To successfully export from a 9.2.0.1 database (select status, version,
  comp_id from dba_registry;) that is located in a 9.2.0.1 $ORACLE_HOME
  (select * from v$version;), use the 9.2.0.1 export utility, and not
  the 9.2.0.2 or higher export utility.
  Or an export with 9.2.0.6 export client from a 9.2.0.5 database will give
  the following errors on the export a partitioned table with a subpartition
  template:
     EXP-00056: ORACLE error 6550 encountered
     ORA-06550: line 1, column 48:
     PLS-00302: component 'CHECK_MATCH_TEMPLATE' must be declared
     ORA-06550: line 1, column 14:
     PL/SQL: Statement ignored
  Solution: use the 9.2.0.5 export client if your intention is to import
  back into a 9.2.0.5 or any higher release database.
3) Always use a version of the IMPORT utility that is equal to the
  version of the target database.

Limitations.
------------

The following limitations apply to the EXPORT and IMPORT utilities (see
details in the matrix below):

1. Oracle export dump files can only be read by the Oracle IMPORT utility
  because these dump files are stored in a special Oracle-binary format.
2. Every export dump file is importable into all future major, patch, and
  maintenance releases of Oracle.
3. The export dump files cannot be read by IMPORT utilities of previous
  maintenance releases and versions.  So, a version 10gR2 (10.2.0.x) export
  dump file cannot be imported by a version 10gR1 (10.1.0.x) IMPORT utility
  (possible errors: ORA-2248), and a version 9 export dump file cannot be
  imported by a version 8i IMPORT utility (possible errors: IMP-10 and
  IMP-21), and a version 8 export dump file cannot be imported by a
  version 7 IMPORT utility (possible errors: IMP-69 and IMP-21).
  In all these cases, the import will terminate with the error IMP-0
  "Import terminated unsuccessfully".
4. IMPORT can read export dump files created by EXPORT release 5.1.22 and
  higher (up to same version).
5. IMPORT cannot read export dump files created by the EXPORT utility of a
  higher maintenance releases or versions.  So, a release 8.1 export dump
  file cannot be imported by a release 8.0 IMPORT utility, and a
  version 8 export dump file cannot be imported by a version 7 IMPORT utility.
6. The Oracle6 (or earlier) EXPORT utility cannot be used against an Oracle8
  or Oracle8i or higher release database.
7. Whenever a lower version EXPORT utility runs with a higher version of the
  Oracle Server, any categories of database objects that did not exist
  in the lower version are excluded from the export.  For example,
  partitioned tables are not exported by the version 7 EXPORT utility.
  If you need to move a version 8 partitioned table to a version 7 database,
  then first reorganize the table into a non-partitioned table.

Matrix 1: Which EXPORT utility to use when importing into an Oracle8
         or a lower database release
         (always use IMPORT utility of the target database):

Matrix 2: Which EXPORT utility to use when importing into an Oracle8
         or a higher database release
         (always use IMPORT utility of the target database):

Remarks:
1) IMPORT can read export dump files created by EXPORT release 5.1.22 and
  higher (up to same version).
2) An Oracle5 or Oracle6 export dump and an Oracle7 IMPORT:
  see the Oracle Utilities Manual, Chapter 2 "Import" for special
  considerations to keep in mind.
3) To export from Oracle7 for import into an Oracle6 database: user SYS
  must run script CATEXP6.SQL on the Oracle7 database first (this script
  needs to be run only once to have the version6 views been created).
4) To export from Oracle8, Oracle8i for import into an Oracle7 database:
  user SYS must run script CATEXP7.SQL on the Oracle8/8i database first
  (this script needs to be run only once in order to create the version7
  views).
5) Only the terminal Oracle8 release (8.0.6) was supported against an
  Oracle9i database: to export from Oracle9i and import into 8.0.6,
  use the Oracle8 export utility.

Matrix 2: Which EXPORT utility to use when importing into an Oracle8
         or a higher database release
         (always use IMPORT utility of the target database):

* 휴지통에 들어있는 객체들 보기
user_recyclebin
dba_recyclebin

* 휴지통 비우기
SQL> purge recyclebin;             사용자의 휴지통 비우기
SQL> purge dba_recyclebin;      휴지통내의 모든 놈들 비우기
SQL> purge tablespace users;   users테이블스페이스의 휴지통 비우기
*purge table "휴지통내의 이름"    휴지통의 하나의 객체만 제거시

요 문서대로만 하면 쉽게 설치할수 있답니다.

ORACLE 10g Install Guide

Install 전 Check 사항

  ORACLE Version 및 Bits
  OS Version 및 Bits
  Oracle & OS 간의 호환성 check
  Oracle Patchset 유/무
  Oracle install 시 필요한 OS Patch 유/무
  X-Window 가 지원되는지 check
  Install 시 Rebooting 이 가능한지 check
         - Kernel Setting 후 Rebooting을 해야 하므로 확인해야 함.
         - 불가능할 경우, 담당자 또는 OS 엔지니어에게 Kernel setting 값을 부탁하여 미리 setting 할 수 있도록 조치를 취해 놓는다.




Oracle & OS 간의 호환성 check  SUN OS

OS	Product	Status	Addtl. Info.	Install Issue
9	10gR2 64-bit	Certified	None	None
8	10gR2 64-bit	Certified	None	None
10	10gR2 64-bit	Certified	None	None
9	10g 64-bit	Certified	Certification Note: Existing Patch Sets: 10.1.0.3 10.1.0.4	None
8	10g 64-bit	Certified	Certification Note: Existing Patch Sets: 10.1.0.3 10.1.0.4	None
10	10g 64-bit	Certified	Certification Note: Existing Patch Sets: 10.1.0.4 HTTP Server is not currently supported with Solaris 10, this is targeted for Q2CY05 Install Information: 1. Execute runInstaller with the -ignoreSysPrereqs option. 2. Select 'Do not create a starter database' when installing Oracle 10g. 3. During installation, the warning message 'SUNWsprox package not installed' can be ignored. Press Continue to resume the installation. 4. Download and install patch 4365826 from metalink.oracle.com. 5. Download and install patch 4163208 from metalink.oracle.com. 6. If you have an End User Solaris 10 distribution, install the SUNWuiu8 package prior to installing the 10g client.	None

HP-UX

OS	Product	Status	Addtl. Info.	Install Issue
11i v2 (11.23)	10gR2 64-bit	Certified	None	None
11i v1 (11.11)	10gR2 64-bit	Certified	None	None
11i v2 (11.23)	10g 64-bit	Certified	Certification Note: Existing patch sets: 10.1.0.3 10.1.0.4 In order to install Oracle 10.1.0.2 on 11iv2 (11.23): Please use the -ignoreSysPreReqs flag with runInstaller	None
11i v1 (11.11)	10g 64-bit	Certified	Certification Note: Existing patch sets: 10.1.0.3 10.1.0.4 Minimum O/S requirements: GoldQPK11i(June 2003) PHKL_29198 PHSS_28871 PHSS_28880	None

IBM UNIX

OS	Product	Status	Addtl. Info.	Install Issue
5L	10gR2 64-bit	Certified	None	None
5L	10g 64-bit	Certified	Certification Note: Existing patch sets: 10.1.0.3 10.1.0.4 AIX 5L 5.2 Maintenance level 1 or higher is required. The following APARS are required:IY43980IY44810IY45462IY45707IY46214IY46605IY51801 The following filesets must be installed and committed:bos.adt.basebos.adt.libbos.adt.libmbos.perf.libperfstatbos.perf.perfstatbos.perf.proctools	None

HP TRU64

OS	Product	Status	Addtl. Info.	Install Issue
5.1b	10g 64-bit	Certified	Certification Note: Existing Patch Sets: 10.1.03 O/S Information: Tru64 UNIX 5.1b patchkit 4 or greater is preferred. You must also edit the following parameters in the /etc/sysconfigtab file: vfs: fifo_do_adaptive = 0 vm: new_wire_method = 1 vm: vm_bigpg_enabled = 0 Note: That setting new_wire_method = 1 should increase overall performance. If you are using 5.1b patchkit 2 or less, you should set new_wire_method = 0 Misc. Information: Spike is an HP provided tool for performing code optimization after linking. Spike (V5.2-511) is now supported for Oracle version 10gR1 with Tru64 UNIX V5.1B Pathkit4. Later versions of Tru64 UNIX 5.1B patchkits are also supported. More information on Spike may be obtained at the following web site: http://h30097.www3.hp.com/dtk/spike_ov.html	None

Windows

OS	Product	Status	Addtl. Info.	Install Issue
2000	10gR2	Certified	None	None
2000	10g	Certified	Certification Note: Existing patch sets: 10.1.0.3 10.1.0.4	None

OS	Product	Status	Addtl. Info.	Install Issue
XP	10gR2	Certified	None	None
XP	10g	Certified	Certification Note: Existing patch sets: 10.1.0.3 10.1.0.4	None

OS	Product	Status	Addtl. Info.	Install Issue
4.0	10g	Desup:OS	Certification Note: Existing patch sets: 10.1.0.3	N/A

ORACLE 10g 설치하기
1. Kernel Configuration 설정하기
SUN OS	# vi /etc/system       set shmsys:shminfo_shmmax=0xffffffff       set shmsys:shminfo_shmmin=1       set shmsys:shminfo_shmmni=500       set shmsys:shminfo_shmseg=64       set semsys:seminfo_semmap=100       set semsys:seminfo_semmni=100       set semsys:seminfo_semmns=2500       set semsys:seminfo_semmnu=2500       set semsys:seminfo_semmsl=300       set semsys:seminfo_semopm=100       set semsys:seminfo_semume=2500       set semsys:seminfo_semvmx=5324638
HP-UX	# sam   =>   kernel configuration => configurable parameters  => '변경할 parameter 선택‘                => 메뉴(tab key)  => actions  => modify configurable parameter => '아래지정된 핵사 값으로 변경후 enter'   maxdsiz           o x 1 0 0 0 0 0 0 0 (268,435,456)   maxdsiz_64bit     o x 0 0 0 0 0 0 3 f f b f f f f f f f (4,396,970,769,279)   maxssiz_64bin     o x 0 0 8 0 0 0 0 0 (8,388,608)   maxtsiz_64bit      o x 0 4 0 0 0 0 0 0 (67,108,864)   shmmax            o x 2 0 0 0 0 0 0 0 (536,870,912) # shutdown -f      --- (Y/N)에서 N를선택, 새로운 환경적용
HP Tru64	# vi /etc/sysconfig vm:        vm-maxvas=524288000        vm-mapentries=20000        vm-vpagemax=65536        vm-page-free-target=768 ipc:        shm-max=524288000 proc:        max-per-proc-data-size=524288000        per-proc-data-size=524288000        max-per-proc-address-space=524288000        per-proc-address-space=524288000        max-proc-per-user=2048        max-threads-per-user=16384        task-max=1024        maxusers=2048        per-proc-stack-size=33554432 socket:        somaxconn=32767        sominconn=32767 inet:        tcbhashsize=1024        ipport_userreserved=65535
IBM-AIX	# smit aio     --- Asynchronous IO 설정      "Change/Show Characteristics of Asynchronous I/O"      "State to be configured at system restart"       defined --> available 로 setting 후 # shutdown -Fr    ---  SYSTEM REBOOT
Windows	설정할 Kernel Parameter  없음.
2. Group, User 등록하기 (각 Platform 마다 명령어는 틀릴 수 있음)
# groupadd -g GROUP_ID dba      .   ex) #groupadd -g 101 dba
		# useradd -g Group_ID -u User_id -d ORACLE_HOME Directory -s SHELL ORACLE_ACCOUNT     ex) #useradd -g 101 -u 1001 -d /oracle/app/oracle/product/10.2.0 -s /bin/ksh ora10g     ex) #chown -R ora10g:dba /oracle      => /oracle directory에 권한 부여하기
3. profile 작성하기
ksh, sh 일 경우 : .profile csh      일 경우 : .cshrc $ vi .profile umask 022   export ORACLE_BASE=/oracle/app/oracle   export ORACLE_HOME=$ORACLE_BASE/product/10.2.0 export ORACLE_SID=ORA10g   (instance_name을 지정한다)   export TMPDIR=$ORACLE_BASE/tmp   export TMP=$ORACLE_BASE/tmp   export DISPLAY= hostname:0.0   (runInstaller를 띄우기 위해 Display를 잡아준다)   export TNS_ADMIN=$ORACLE_HOME/network/admin   export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data   export NLS_LANG=American_america.KO16KSC5601 (DB Character set 지정)   export LD_LIBRARY_PATH = $ORACLE_HOME/lib:$ORACLE_HOME/lib32:/usr/lib   export PATH=$ORACLE_HOME/bin:/bin:/usr/bin:/sbin:/usr/ccs/bin:.:$PATH <HP-UX 의 경우 추가사항>   export SHLIB_PATH = $ORACLE_HOME/lib:$ORACLE_HOME/lib32:/usr/lib < AIX 의 경우 추가사항>   export LIBPATH=$ORACLE_HOME/lib:$ORACLE_HOME/network/lib:/usr/lib   export LINK_CNTRL=L_PTHREADS_D7
4. CD-ROM Mount 하기
sun, linux, windows  -  auto mount IBM          cd-rom device 찾기        # lsdev -c | grep cd        mount 하기        #  mount -rv cdrfs /dev/cd0 /cdrom HP-UX       cd-rom device 찾기       # ioscan -fnC disk             mount 하기       # vi /etc/pfs_fstab        /dev/dsk/c5t2d0 /cdrom pfs_rrip xlat=unix 0 0       # nohup /usr/sbin/pfs_mountd &       # nohup /usr/sbin/pfsd &       # /usr/sbin/pfs_mountd &       # /usr/sbin/pfsd  &       # /usr/sbin/pfs_mount /cdrom HP Tru64      cd-rom device 찾기      # hwmgr -v dev
5. Oracle Software 설치하기
1) $ /cdrom/disk1/runInstaller 실행. 2) Oracle Inventory => Install log 저장 위치    dba 권한을 가져야 한다.    next 선택  -> 3) pop-up 창에 뜬 orainstRoot.sh 파일을 root user로 실행한다.    oraInst.loc 파일을 생성하며, /etc 나 /var/opt/oracle 에 생성된다.   4) Oracle Software 가 설치될 위치를 선책한다.    next 선택   -> 5) 설치하고자 하는 Type 선택    Enterprise Edition    Standard Edition    Custom 6) 주로 Custom을 선택하여, 필요한 Product 만 설치한다.     next  -> 7) Product Languates를 선택하여, 필요한 language를 선택한다.    English, Korean 선택    OK 선택 후 Next  -> 8) 자동으로 환경 설정을 check 한다.    Next  -> 9) 필요한 Product 만을 선택하여 설치를 한다.    Next  -> 10) 새로 설치이기 때문에 무시하고 Next 선택 11) Operation System Groups을 모두 dba 로 권한 부여한다.      Next  -> 12) Database 설치할 것인지를 선택하는 부분.     주로 No를 선택하고, 수동으로 DBCA를 실행한다. 13) Summary 부분.     확인하고, 틀린 사항이 있으면, Back 하여 수정한다.     Next 하여, Oracle Software 설치 완료 한다. 14) 100% 될 때까지 약 1시간 미만의 시간이 소요된다.
6. Oracle DB 설치하기
1) $ dbca 실행       아래와 같은 Database Configuration Assistant를 띄운다. 2) Create a Database 선택 3) 각 환경에 맞는 Database Template를 선택한다.    주로 Custom Database를 선택하여 설치한다. 4) Database Global Database Name 과 SID를 입력    주로 Single 일 경우, Database Name 과 SID를 동일 이름으로 입력한다. 5) Management Options 선택 부분으로 사항에 맞게 Setting 한다.    주로 Default 로 선택하고 넘어간다. 6) 각 계정별 패스워드 설정.    하나의 패스워드 지정 또는 각 계정 마다 별도의 패스워드 부여 가능하다. 7) Database Storage Options 선택 화면.    File System    Automatic Storage Management (ASM)    Raw Devices        주로 Single 일 경우 File System 으로 선택한다. 8) Database File Locations    Database 물리적인 controlfile, redo_log, datafile 들의 위치를 지정해 준다. 9) Recovery Configuration    Flash Recovery Area의 물리적 위치를 지정해 준다. 10) Database Content     각 필요한 Components를 선택한다. 11) Initialization Parameters     Memory 영역으로 SGA 영역에 대한 설정 화면이다. 12) Initialization Parameters      DB_BLOCK_SIZE 설정과 Processes 값을 지정      그외의 모든 파라메터에 대해 설정을 하고자 할 경우, All Initializtion Parameters 선택하여 수정한다. 13) Initialization Parameters        Character Sets 설정한다. 14) Initialization Parameters        Connection Mode 선택        -  Dedcated Server Mode        -  Shared Server Mode 15) Database Storage            각 파일들의 위치와 Size를 지정한다. 또는 필요한 파일들을 추가/삭제 가능.      Controlfile      Datafile      Redolog 16) Creation Options      Scripts 로도 저장해 놓을 수도 있다. 17) Summary를 보고 설정된 값으로 설정되었는지 확인한다. 18) DB Creation 화면으로 100% 까지 Error 없이 끝나야 한다.
7. 설치 환경 체크하기
7-1)  DB startup & shutdown          $ sqlplus "/as sysdba"          SQL> startup          $ sqlplus "/as sysdba"          SQL> shutdown immediate
7-2)  Listener start & stop          $ lsnrctl start LISTENER          $ lsnrctl status LISTENER    => Listener 의 상태를 check 한다.          $ lsnrctl stop LISTENER          ex)          $ORACLE_HOME/network/admin/listener.ora                    ORA10G =          <-- LISTENER_NAME               (DESCRIPTION_LIST =               (DESCRIPTION =                  (ADDRESS_LIST =                    (ADDRESS = (PROTOCOL = TCP)(HOST = ns)(PORT = 1521))                   )                )             )           SID_LIST_ORA10G =            (SID_LIST =               (SID_DESC =                 (SID_NAME = XXX)                 (ORACLE_HOME = /usr1/oracle/app/oracle/product/9.2.0)               )           )
7-3)  sqlplus          $ sqlplus username/password          SQL> show user;
7-4)  sql*net 접속          $ tnsping TEST          $ sqlplus username/password@TEST                          ex)           $ORACLE_HOME/network/admin/tnsnames.ora                           TEST =     <-- TNS_ALIAS                   (DESCRIPTION =                          (ADDRESS_LIST =                                (ADDRESS = (PROTOCOL = TCP)(HOST = ns)(PORT = 1521))                           )                           (CONNECT_DATA =                                 (SID = XXX)                            )                    )