Uninstall Oracle 10gR2 On Solaris 5.10

To uninstall Oracle 10gR2 from Solaris 5.10, please do the followings

1. Remove all database, by running dbca.
2. Stop aall oracle running process : A. Database Control : $ORACLE_HOME/bin/emctl stop dbconsole B.Oracle Net listener : $ORACLE_HOME/bin/lsnrctl stop C. iSQL*Plus : $ORACLE_HOME/bin/isqlplusctl stop D.Ultra Search : $ORACLE_HOME/bin/searchctl stop
3. Start Oracle Universal installer locating at $ORACLE_HOME/oui/bin/runInstaller.
4. In the Welcome window, click Deinstall Products.
5. In the Inventory screen, select the Oracle home and the products that you want to remove, then click Remove.

installation of Oracle Text on 10g

This article lists the steps for manual installation of Oracle Text 10gR1 and 10gR2, verification and uninstalling Oracle Text installation.If you create an Oracle database using the Database Configuration Assistant (DBCA) Text is installed by default and you do not need to perform the installation steps described in the Manual installation section.

Instead installation you need to grant permission to the oracle user that use oracle text.

Create User:

CREATE USER myuser IDENTIFIED BY myuser_password.

Grant Roles:

GRANT RESOURCE, CONNECT, CTXAPP TO MYUSER;

Grant EXECUTE Privileges on CTX PL/SQL Packages:

There are ten Oracle Text packages that enable you to perform actions ranging from synchronizing an Oracle Text index to highlighting documents. For example, the CTX_DDL.SYNC_INDEX package enables you to synchronize your index.

GRANT EXECUTE ON CTX_CLS TO myuser;
GRANT EXECUTE ON CTX_DDL TO myuser;
GRANT EXECUTE ON CTX_DOC TO myuser;
GRANT EXECUTE ON CTX_OUTPUT TO myuser;
GRANT EXECUTE ON CTX_QUERY TO myuser;
GRANT EXECUTE ON CTX_REPORT TO myuser;
GRANT EXECUTE ON CTX_THES TO myuser;

Oracle Text is available for no extra Licensing in all four database editions:

1. Oracle Database Standard Edition One.
2. Oracle Database Standard Edition (SE).
3. Oracle Database Enterprise Edition (EE).
4. Oracle Database Personal Edition.

Manual installation of Text 10gR1 (10.1.0.x) and 10gR2 (10.2.0.x)

1. You must install Oracle Data Mining (ODM), feature available in Oracle Database Enterprise Edition (EE), before you install Oracle Text in order to use the SVM classifier and the KMEANS clustering. All other functions should work without ODM installed, including RULE classifier and TEXTK clustering.
2. Oracle Text makes use of a "Knowledge Base" for English and French, which is loaded from different files provided on the second CD, known as the "Oracle Database 10g Companion CD". The Knowledge Base is required to use any of the theme-based features in Oracle Text. Therefore, if you install from the main CD only, theme functionality will not be available. For information about how to install products from the Companion CD, refer to the "Installing Oracle Database 10g Products from the Companion CD" section.

If you created your database manually or you want to install Text later, then follow these steps.


Note: In SQL*Plus we use '?' instead of $ORACLE_HOME

1. Text dictionary, schema name CTXSYS, is created by calling following script from SQL*Plus connected as SYSDBA:

SQL> connect SYS/password as SYSDBA
SQL> spool text_install.txt
SQL> @?/ctx/admin/catctx.sql CTXSYS SYSAUX TEMP NOLOCK

Where:
CTXSYS - is the ctxsys user password
SYSAUX - is the default tablespace for ctxsys
TEMP - is the temporary tablespace for ctxsys
LOCK|NOLOCK - ctxsys user account will be locked or not

2. The next step is to install appropriate language-specific default preferences. There is script which creates language-specific default preferences for every language Oracle text supports in /ctx/admin/defaults directory, such as English(US), Danish(DK), Dutch(NL), Finnish(SF), French(F), German(D), Italian(IT), Portuguese(PT), Spanish(E), and Swedish(S). They are named in the form drdefXX.sql, where XX is the international license plate code.
To manually install US default preferences, for example, log into sqlplus as CTXSYS, and run 'drdefus.sql' as described below:

SQL> connect CTXSYS/password@tns_alias
SQL> @?/ctx/admin/defaults/drdefus.sql
SQL> spool off

If you have installed Oracle Data Mining (ODM) before Text you will see in the text_install.txt logfile ORA-955 errors for public synonyms, e.g. dm_svm_build, which can be ignored. We have a dummy package that mimics the API in CTXSYS schema, and we attempt to create public synonyms to it. Now, if ODM has been installed, these public synonym creates fail and the public synonyms point to ODM objects, which is what we want.


Text 10gR1 (10.1.0.x) and Text 10gR2 (10.2.0.x) Installation verification

1. Check to make sure that all Text objects were created in CTXSYS schema and correct version is installed
2. Check to make sure that there are not invalid objects for CTXSYS.
You should get: "no rows selected". If there are then you can compile each invalid object manually.


connect SYS/password as SYSDBA

set pages 1000
col object_name format a40
col object_type format a20
col comp_name format a30
column library_name format a8
column file_spec format a60 wrap
spool text_install_verification.log

select comp_name, status, substr(version,1,10) as version from dba_registry where comp_id = 'CONTEXT';
select * from ctxsys.ctx_version;
select substr(ctxsys.dri_version,1,10) VER_CODE from dual;

select count(*) from dba_objects where owner='CTXSYS';

-- Get a summary count
select object_type, count(*) from dba_objects where owner='CTXSYS' group by object_type;

-- Any invalid objects
select object_name, object_type, status from dba_objects where owner='CTXSYS' and status != 'VALID' order by object_name;

spool off


Steps to Deinstall Oracle Text Manually

Before deinstalling Oracle Text, it is best to first drop all Text Indexes built in schemas other than CTXSYS. Text dictionary, schema name CTXSYS, is removed by calling following script from SQL*Plus connected as SYSDBA:

SQL> connect SYS/password as SYSDBA
SQL> spool text_deinstall.log
SQL> @?/ctx/admin/catnoctx.sql
SQL> drop procedure sys.validate_context;
SQL> spool off

Review the output file text_deinstall.log for errors.
Deinstallation of Oracle Text is complete.

*** Note ***
ORA-04043 for dropping sys.validate_context can be ignored, as in base release version this procedure was owned by ctxsys and needs to be owned by sys.

Related Posts:

1. Introduction of ORACLE TEXT
2. Find Text index size

Oracle Database Cloning using DBCA

The "Template Management" section of the Database Configuration Assistant (DBCA) can be used to clone databases. The following method creates a clone of an existing database including both the structure and the data:

1. Start the Database Configuration Assistant (DBCA).
2. On the "Welcome" screen click the "Next" button.
3. On the "Operations" screen select the "Manage Templates" option and click the "Next" button.
4. On the "Template Management" screen select the "Create a database template" option and select the "From and existing database (structure as well as data. you can also chose structure only )" sub-option then click the "Next" button.
5. On the "Source database" screen select the relevant database instance and click the "Next" button.
6. On the "Template properties" screen enter a suitable name and description for the template, confirm the location for the template files and click the "Next" button.
7. On the "Location of database related files" screen choose either to maintain the file locations or to convert to OFA structure (recommended) and click the "Finish" button.
8. On the "Confirmation" screen click the "OK" button.
9. Wait while the Database Configuration Assistant progress screen gathers information about the source database, backs up the database and creates the template.

By default the template files are located in the ORACLE_HOME/assistants/dbca/templates" directory.

Now move the template into your destination machine and start DBCA. install database using that template

Manually configure the Oracle 10g EM dbconsole

Overview

When you choose to create a preconfigured database during the Oracle 10g installation, you can select the Oracle Enterprise Manager (OEM) interface that you want to use to manage the database. The following options are available:

Database Grid Control
This option is available only if an Oracle Management Agent is installed on the system. When the Installer detects an Oracle Management Agent on the system, it allows you to choose this option and specify the Oracle Management Service that you want to use to manage the database. If an Oracle Management Agent is not installed, you must choose to use Database Control to manage the database. However, if you install Oracle Management Agent after you install Oracle Database, you can then use Grid Control to manage this database.

Database Control

This option is selected by default if an Oracle Management Agent is not installed on the system. However, even if a Management Agent is installed, you can still choose to configure Database Control to manage the database.

Custom installation

If you choose the Custom installation type or the Advanced database configuration option during the installation, the Installer does not display the OEM setup screens. Instead, it runs the Database Configuration Assistant (DBCA) in interactive mode, which enables you to create a custom database.

DBCA also enables you to specify the Oracle Enterprise Manager interface that you want to use. Furthermore, you can also use DBCA after the installation to configure Database Control for a database that was not previously configured to use it.

However, if you decide to setup your own Database, you must install the Database Control manually.

Setup your own Database and manually install the Database Control

The Database Control relies on various underlying technologies to discover, monitor, and administer the Oracle Database environment.

From the Database Control, you can monitor and administer a single Oracle Database instance.

The Database Control Framework consists of the Database Control and its underlying technologies:

A local version of the Oracle Management Service designed to work with the local database or clustered database.

A local Oracle Management Repository installed in the local database and designed to store management data for the Database Control.

The following steps have to be performed.



Create the Database Control Repository and setup the OC4J Application Server

Make sure, that you can connect to the Repository Database (Test it with SQL*Plus). Examples for Setup Files can be found here:

Windows
LISTENER.ORA
SQLNET.ORA
TNSNAMES.ORA

Linux
listener.ora
sqlnet.ora
tnsnames.ora

Now start the Oracle EM dbconsole Build Script ($ORACLE_HOME/bin/emca for Linux and $ORACLE_HOME\Bin\emca.bat for Windows).

$ emctl stop dbconsole -- stop EM
$ emca -repos drop -- drop EM repository
$ emca -repos create -- create EM repository
$ emca -config dbcontrol db -- configure dbcontrol
$emca -r auto configure

$ emctl stop dbconsole -- stop EM
$emca -repos recreate -- recreate EM repository
$emca -deconfig dbcontrol db -- deconfigure dbcontrol
$emca -config dbcontrol db -- configure dbcontrol

Oracle 10g Installation in Solaris 10

This guide describes how to quickly install Oracle Database 10g on Solaris 5.10 systems. Though it is a complete installation guide , you are requested to follow the installation manual provided by ORACLE

Install Solaris

During installation of Solaris, create two additional partition named 'ORACLE' and 'ORADATA' which contain Oracle base directory and Oracle datafile directory respectively. The Swap partition must be grater than 400MB (2GB recommended or Double of current RAM size)
(You can install Oracle in one partition but above arrangement has been followed in most software projects)

Log In to the System as root

Before you install the Oracle software, you must complete several tasks as the root user. If you are installing the software from an X Window System workstation or X terminal:

• Start a local terminal session, for example, an X terminal (xterm).

Check the Hardware Requirements

Requirement Minimum Value

• Physical memory (RAM) 512 MB (524288 KB)
• Swap space 1 GB (1048576 KB) or twice the size of RAM
• Disk space in /tmp 400 MB (409600 KB)
• Disk space for software files 2.5 GB (2621440 KB)

To ensure that the system meets these requirements, follow these steps:

1. To determine the physical RAM size, enter the following command:
   # /usr/sbin/prtconf | grep "Memory size"
2. To determine the size of the configured swap space, enter the following command:
   # /usr/sbin/swap -s
3. To determine the amount of free disk space available in the /tmp directory, enter the following command:
   # df -k /tmp
4. To determine the amount of free disk space available on the system, enter the following command:
   # df -k
5. To determine whether the system architecture is 64-bit, enter the following command:
   # /bin/isainfo -kv

Check the Software Requirements

The system must meet the following minimum software requirements:

• The version of Solaris must be Solaris 8 or Solaris 9.
• The following packages must be installed:
  1. SUNWarc
  2. SUNWlibms
  3. SUNWi1of
  4. SUNWbtool
  5. SUNWsprot
  6. SUNWi15cs
  7. SUNWi1cs
  8. SUNWhea
  9. SUNWsprox
  10. SUNWlibm
  11. SUNWtoo
  12. SUNWxwfnt

To ensure that the system meets these requirements, follow these steps:

1. To determine which version of Solaris is installed, enter the following command:
   # uname -r
   5.8
   In this example, the version shown is Solaris 8 (5.8). If necessary, see your operating system documentation for information about upgrading the operating system.
2. To determine whether the required packages are installed, enter a command similar to the following:
   # pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms \SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs \ SUNWxwfnt
   If a package is not installed, then install it. See your operating system or software documentation for information about installing packages.
3. To determine whether an operating system patch is installed, enter a command similar to the following:
   # /usr/sbin/patchadd -p | grep patch_number

If an operating system patch is not installed, download it from the following Web site and install it: http://sunsolve.sun.com

Create Required UNIX Groups and User

First of all following users and groups should be created

1. Group oinstall, dba, oper (optional)
2. . user oracle having oinstall as primary group

use the following commands to create required groups and user (as root user)

groupadd oinstall

groupadd dba

groupadd oper

useradd -g oinstall -G dba[,oper] -d /export/home/oracle -s /usr/bin/bash -m oracle

passwd -r files oracle

Now create a project for oracle so that all resources can be alloacated to this project as root user

  
projadd oracle

Create Required Directories

Create directories with names similar to the following and specify the correct owner, group, and permissions for them:
/u01/app/oracle (the Oracle base directory: u01=oracle)
/u02/oradata (an optional Oracle datafile directory : u02=oradata)
(Hear u01, u02 are the partition named oracle and oradata respectively)
Identify one file system with 2.5 GB (10 GB for Therap) of free disk space, for the Oracle base directory, and another file system with 1.2 GB (45 GB for Therap) of free disk space for the Oracle datafile directory.
To create the required directories and specify the correct owner, group and permissions for them, follow these steps:

1. Enter the following command to create subdirectories in the mount point directory that you identified for the Oracle base directory: # mkdir -p /u01/app/oracle
2. If you intend to use a second file system for the Oracle database files, create an oradata subdirectory in the mount point directory that you identified for the Oracle datafile directory (shown as /u02 in the examples): # mkdir /u02/oradata
3. Change the owner and group of the directories that you created to the oracle user and the oinstall group:
   # chown -R oracle:oinstall /u01/app/ oracle /u02/oradata
4. Change the permissions on the directories that you created to 775:
   #chmod -R 775 /u01/app/oracle /u02/oradata

Configure Kernel Parameters

Verify that the following kernel parameters are set to values greater than or equal to the recommended value shown:

Table: 1

Parameter	Recommended Value
noexec_user_stack	1
semsys:seminfo_semmni	100
semsys:seminfo_semmns	1024
semsys:seminfo_semms	256
shmsys:shminfo_shmmax	4294967295
shmsys:shminfo_shmmin	1
shmsys:shminfo_shmmni	100
shmsys:shminfo_shmseg	10
semsys:seminfo_semvmx	32767

To view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:

1. To view the current values of these parameters, enter the following commands:
   # grep noexec_user_stack /etc/system
   # /usr/sbin/sysdef | grep SEM
   # /usr/sbin/sysdef | grep SHM
2. If you have to change any of the current values, follow these steps:
   1. Create a backup copy of the /etc/system file, for example:# cp /etc/ system /etc/system.orig
   2. Open the /etc/system file in any text editor: # vi /etc/system
   3. To specify new values for the parameters, add lines similar to the following to the /etc/system file, or edit the lines if the file already contains them:
      set noexec_user_stack=1
      set semsys:seminfo_semmni=100
      set semsys:seminfo_semmns=1024
      set semsys:seminfo_semmsl=256
      set semsys:seminfo_semvmx=32767
      set shmsys:shminfo_shmmax=4294967295
      set shmsys:shminfo_shmmin=1
      set shmsys:shminfo_shmmni=100
      set shmsys:shminfo_shmseg=10
   4. Reboot the system

To view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:

1. To view the current values of these parameters, enter the following commands:
   # id -p // to verify the project id
   uid=0(root) gid=0(root) projid=1 (user.root)
   # prctl -n project.max-shm-memory -i project user.root
   # prctl -n project.max-sem-ids -i project user.root
2. If you must change any of the current values, then follow these steps:
   1. To modify the value of max-shm-memory to 6 GB: # prctl -n project.max-shm-memory -v 6gb -r -i project user.root
   2. To modify the value of max-sem-ids to 256: # prctl -n project.max-sem-ids -v 256 -r -i project user.root

Log In as the oracle User and Configure the oracle User’s Environment

You run the Installer from the oracle account. However, before you start the installer you must configure the environment of the oracleuser. To configure the environment, you must:

1. Set the default file mode creation mask (umask) to 022 in the shell startup file.
2. Set the DISPLAY, ORACLE_BASE, and ORACLE_SID environment variables.

To set the oracle user’s environment, follow these steps:

1. Start another terminal session.
2. To determine the default shell for the oracle user, enter the following command:$ echo $SHELL
3. Open the oracle user’s shell startup file in any text editor:$ vi .profile
4. Enter or edit the following line in the shell startup file, specifying a value of 022 for the default file creation mask: umask 022
5. Save the file and exit from the editor.
6. Reboot
7. Enter commands similar to the following to set the ORACLE_BASE and ORACLE_SID environment variables:
   $ ORACLE_BASE=/u01/app/oracle
   $ ORACLE_SID=sales
   $ export ORACLE_BASE ORACLE_SID
8. Enter the following commands to ensure that the ORACLE_HOME an TNS_ADMIN environment variables are not set:
   $ unset ORACLE_HOME
   $ unset TNS_ADMIN
9. To verify that the environment has been set correctly, enter the following commands:
   $ umask
   $ env | more

Verify that the umask command displays a value of 022 and the environment variables that you set in this section have the correct values.

Install Oracle Database 10g

After configuring the oracle user’s environment, start the Installerand install the Oracle software, as follows: $ /cdrom/cdrom0/runInstaller
The following table describe the recommended action of each installation screen

Table: 2

Screen	Recommended Action
Welcome	Click Next.
Select Installation Method	The Basic Installation option is selected by default. Specify the directory path of the Oracle home. Ensure that the UNIX DBA group “oinstall” is selected. If you want to create a starter database, then specify a name and password for it. Then, click Next.
Specify Inventory Directory and Credentials	This screen is displayed only during the first installation of Oracle products on a system. Specify the full path of the Oracle Inventory directory as “/oracle”. Ensure that the operating system group selected is “dba”. Then, click Next.
Product-Specific Prerequisite Checks	Verify that all of the prerequisite checks succeed, then click Next. Oracle Universal Installer checks the system to verify that it is configured correctly to run Oracle software. If you have completed all of the preinstallation steps in this guide, all of the checks should pass. If a check fails, then review the cause of the failure listed for that check on the screen. If possible, rectify the problem and rerun the check. Alternatively, if you are satisfied that your system meets the requirements, then you can select the check box for the failed check to manually verify the requirement.
Specify Oracle Datafile Directory	Specify the full path of the Oracle Oracle Datafile directory as “/oradata”.
Summary	Review the information displayed on this screen, and then click Install.
Install	This screen displays status information while the product is being installed.
Configuration Assistants	This screen displays status information for the configuration assistants that configure the software and create a database. When the message is displayed at the end of this process, click OK to continue.
Execute Configuration Scripts	When prompted, read the instructions and then run the scripts(root.sh, Root.sh) mentioned on this screen. Click OK to continue.
End of Installation	The configuration assistants configure several Web-based applications, including Oracle Enterprise Manager Database Control. This screen displays the URLs configured for these applications. Make a note of the URLs used. The port numbers used in these URLs are also recorded in the following file: oracle_home/install/portlist.ini To exit from Oracle Universal Installer, click Exit and then click Yes.

After Installation

1. open the file /var/opt/oracle/oratab in your favourite editor. at the end of this file all the databases are listed like this orcl:/oracle/app/oracle/oracle/product/10.2.0/db_1:N
2. Replace N by Y
3. if you install 2 database then you’ll have 2 such lines in this file .if the lines contain N at the end. It means this database won’t be started during system bootup. change it to Y as above and save the file.
4. Open the oracle user’s shell startup file in any text editor: $ vi .profile
   add $ ORACLE_HOME= oracle home path
   $ ORACLE_SID= database SID
   $ export ORACLE_ SID ORACLE_HOME
5. save and exit the editor and reboot
6. congratulation you complete the installation process successfully.