Enfsuite64 Admin Database PDF

Enfinity Suite 6.
Database Setup Guide
This document covers the feature set delivered with Enfinity Suite 6.4. The information contained in this document is subject to change without notice at any time.
These materials are subject to change without notice. These materials are provided by Intershop Communications AG and its affiliated companies (Intershop Group) for informational purposes only, without representation or warranty of any kind, and Intershop Group shall not be liable for errors or omissions with respect to the materials. The only warranties for Intershop Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
This document and all of its parts are protected by copyright. All rights, including those of duplication, reproduction, translation, microfilming, storage on electronic media and processing in electronic form are expressly reserved.
Intershop and Enfinity are trademarks or registered trademarks of Intershop Communications. All other company, product and brand names are trademarks or registered trademarks of their respective owners.
Copyright 2005-2010 Intershop Communications. All Rights Reserved.
2010-01-31
Document ID: EMS-LIB-64-51-01
Table of Contents
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify Content of Installation DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
7 7 7 9 9 9
Chapter 2 Database Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . 13 Linux x86-64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Solaris SPARC 64-Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Solaris x86_64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Windows (x64) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Creating an Enfinity Suite 6 Database . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Database Setup Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Testing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Log On as Sysdba. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Check Character Set Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Check Database Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Stop and Restart the Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Perform Project-Specific Database Adjustments . . . . . . . . . . . . . . . . 29 Preparing the Database for Data Replication . . . . . . . . . . . . . . . . . . . . . 29 Local Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Remote Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Manual Update of Network Configuration Files . . . . . . . . . . . . . . . . . . . 33 Manual Database Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Create New Instance Manually Using Scripts . . . . . . . . . . . . . . . . . . . 34 Prepare Existing Instance for Enfinity Suite 6 . . . . . . . . . . . . . . . . . . . 37
CHAPTER
Introduction
About this Guide
Typographical Conventions
About this Guide

This guide explains how to set up an Oracle 10g or 11g database for Enfinity Suite 6.4 on SUSE Linux Enterprise Server, Red Hat Enterprise Linux, Sun Solaris and Microsoft Windows. The guide also mentions the installation of the Oracle client, through which the Enfinity Suite 6.4 application servers communicate with the Oracle database.
Typographical Conventions
The following typographical conventions are used throughout the guide:
Cross-references References to other parts of this guide and to other documentation appear in italics. Commands All commands to be typed at command prompts appear in Courier font. Reserved or Special Words Names of files, directories, or cartridges appear in italics.
This guide uses the <Placeholder_Name> syntax to denote the Enfinity Suite 6 installation directory (<IS.INSTANCE.DIR>), the location of the Shared File System (<IS.INSTANCE.SHARE>) as well as various other directory, group and user names, IDs etc. See the Enfinity Suite 6 Installation Guide for your operating system for a complete list of placeholders. Example code, attribute names, methods and database table names appear in Courier; for example, init(). In addition, the # sign refers to the number of an Enfinity Suite 6 instance.
Chapter Overview
Before installing Enfinity Suite 6, you have to install and configure an Oracle database for Enfinity Suite 6. Installing the Oracle software and configuring a database includes the following steps, where each step is covered in a separate section of this guide: 1. Installing the Oracle Database Software, on p. 13 This section specifies the required software packages to be installed for all supported operation environments, and points to the corresponding Oracle documentation.
NOTE: Intershop recommends to install the database server on dedicated host(s), whereas a database client is to be installed on every Enfinity Suite 6 application server host.
Chapter 1: Introduction
Page 7
Chapter Overview
About this Guide
2. Creating an Enfinity Suite 6 Database, on p. 18 This task is performed using the Enfinity Suite 6 Suite database setup. Note that technically, the term database refers to the physical collection of files which make up the database (such as data files, redo log files, and control files), whereas instance refers to the processes (and the respective memory structures) operating on the database. Using the Oracle server software, the Enfinity Suite 6 database setup program creates a database and an instance operating on this database.
NOTE: To simplify the discussion, this chapter uses the term database to refer
both to the files that hold the data and to the processes and memory structures that operate on top.
In addition to the installation sequence, this section describes tests to make sure the database instance is working properly before proceeding with the installation. The section also provides hints regarding manual execution of tasks performed by the database setup, as well as a discussion of special settings necessary to prepare a database for local and remote data replication scenarios.
Page 8
Before You Start
System Requirements
Before You Start

System Requirements
Enfinity Suite 6.4 requires Oracle 10gR2 (10.2.0.4.0) or 11gR2 (11.2.0.1.0).
NOTE: At the date of editing this guide, the newest available Oracle 11g version for
Microsoft Windows was 11.1.0.7.0. Intershop therefore recommends to use Oracle 10gR2 (10.2.0.4.0) on Windows platforms.
The patch level mentioned is the most recent patch available at the time of the release. If you need to use higher patch levels, contact Intershop to make sure that these patches do not interfere with Enfinity Suite 6. See the document system_requirements.pdf in the /docs/pdf directory on the installation DVD for details on supported operating systems, service levels and for additional software and hardware requirements.
Verify Content of Installation DVD

To check the content of the Enfinity Suite 6 installation DVD, you can verify a checksum (contained in file checksum.xml on the DVD) against the content of the installation DVD. To verify the checksum: 1. Insert the installation DVD into your DVD-ROM drive. The DVD should be mounted automatically to a mount point (<mount_point>) such as /media/cdrom or /media/dvd. 2. Navigate to the root of the Enfinity Suite 6 installation DVD. 3. Run the following Java command (all on a single line).
java -cp . Checksum -checksumfile checksum.xml -mode verify -basedir / mnt/iso -exclude checksum.xml,Checksum.class
If the test fails, contact INTERSHOP to get help.
Page 9
CHAPTER
Database Setup
Installing the Oracle Database Software

The installation of the Oracle database software is not part of the Intershop database setup program but is performed by the Oracle Universal Installer. For installation options and details on individual installation steps, refer to the respective Oracle documentation, which can be found on the Oracle CD and on the Oracle Web site. When installing the Oracle database software, be aware of the following issues: By default, the Oracle Universal Installer runs in the operating environments native language. To disable the installation session translation, set NLS_ENABLED = FALSE in the oraparam.ini file, located in the /install sub directory of the Oracle installation package. For the Oracle 10gR2 and 11gR2 Database Server, perform a Software Only installation. The minimum required database editions are Standard Edition or Standard Edition One. For newly created Oracle 11gR2 databases, the passwords are case sensitive by default. As the database sessions of the Enfinity Suite 6 application servers ignore these settings by default, you must either adjust the key intershop.jdbc.password in <IS.INSTANCE.SHARE>/ system/config/cluster/orm.properties, or set sec_case_sensitive_logon=false in your databases init.ora file.
The client setup process includes the installation of network configuration files (<ora_home>/network/admin/*.*). Note that these files will not be used by Enfinity Suite 6. Enfinity Suite 6 uses <IS.INSTANCE.SHARE>/system/config/oracle/*.* via setting the TNS_ADMIN environment variable. However, it is recommended to install the network configuration files as this makes it possible to test immediately whether the client can connect to the database. Enfinity Suite 6 communicates with the Oracle database in the dedicated server mode. This means that each client session is served by a dedicated server process (or thread). For the Oracle 10gR2 and 11gR2 Database Client, perform a custom installation, selecting the following components: Oracle Database Utilities SQL*Plus Oracle JDBC/THIN Interfaces Oracle Net
On Linux/Solaris: Due to a public Oracle defect, you must manually adjust file permissions after installing the Oracle 10gR2 Database Client executing (as root)
chmod -R 755 <oracle_home>
The following sections specify the required software packages for the supported operation environments.
Chapter 2: Database Setup
Page 13
Linux x86-64
Linux x86-64
The supported Linux platforms include the 64bit versions of SUSE Linux Enterprise Server 10 (SLES 10) and Red Hat Enterprise Linux 5 (RHEL 5). The Oracle software to be installed is the same for both SLES 10 and RHEL 5.
Oracle 10gR2 The packages to be installed are 10201_database_linux_x86_64.cpio.gz for the server, 10201_client_linux_x86_64.cpio.gz for the client, and p6810189_10204_Linux-x86-64.zip as required patch set for both server and client.
The corresponding documentation includes Oracle Database Quick Installation Guide 10g Release 2 (10.2) for Linux x86-64, Part Number B15668-02, May 2008 Oracle Database Client Quick Installation Guide 10g Release 2 (10.2) for Linux x86-64, Part Number B15670-01, September 2005.
NOTE: When installing Oracle 10gR2 on SLES 10, launch the Oracle Universal
Installer as oracle using ./runInstaller -ignoreSysPrereqs.
Oracle 11gR2 The packages to be installed are linux.x64_11gR2_database_1of2.zip and linux.x64_11gR2_database_2of2.zip for the server, and linux.x64_11gR2_client.zip for the client.
The corresponding documentation includes Oracle Database Quick Installation Guide 11g Release 2 (11.2) for Linux x86-64, Part Number E10860-04, November 2009 Oracle Database Client Quick Installation Guide 11g Release 2 (11.2) for Linux x86-64, Part Number E10861-03, November 2009.
Page 14
Solaris SPARC 64-Bit
Solaris SPARC 64-Bit
Oracle 10gR2 The packages to be installed are 10gr2_db_sol.cpio.gz for the server, 10gr2_client_sol.cpio.gz for the client, and p6810189_10204_Solaris-64.zip as required patch set for both server and client.
The corresponding documentation includes Oracle Database Quick Installation Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit), Part Number B28053-01, February 2006 Oracle Database Client Quick Installation Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit), Part Number B15693-02, November 2005.
Oracle 11gR2 The packages to be installed are solaris.sparc64_11gR2_database_1of2.zip and solaris.sparc64_11gR2_database_2of2.zip for the server, and solaris.sparc64_11gR2_client.zip for the client.
The corresponding documentation includes Oracle Database Quick Installation Guide 11g Release 2 (11.2) for Solaris Operating System (SPARC 64-Bit), Part Number E10863-01, November 2009 Oracle Database Client Quick Installation Guide 11g Release 2 (11.2) for Solaris Operating System (SPARC 64-Bit), Part Number E10864-01, November 2009.
Page 15
Solaris x86_64
Solaris x86_64
Oracle 10gR2 The packages to be installed are 10201_database_solx86_64.zip for the server, 10201_client_solx86_64.zip for the client, and p6810189_10204_Solaris86-64.zip as required patch set for both server and client.
The corresponding documentation includes Oracle Database Quick Installation Guide 10g Release 2 (10.2) for Solaris Operating System (x86-64), Part Number B15705-01, February 2006 Oracle Database Client Quick Installation Guide 10g Release 2 (10.2) for Solaris Operating System (x86-64), Part Number B15707-01, February 2006.
Oracle 11gR2 The packages to be installed are solaris.x64_11gR2_database_1of2.zip and solaris.x64_11gR2_database_2of2.zip for the server, and solaris.x64_11gR2_client.zip for the client.
The corresponding documentation includes Oracle Database Quick Installation Guide 11g Release 2 (11.2) for Solaris Operating System (x86-64), Part Number E16362-01, November 2009 Oracle Database Client Quick Installation Guide 11g Release 2 (11.2) for Solaris Operating System (x86-64), Part Number E16363-01, November 2009.
Page 16
Windows (x64)
Windows (x64)
NOTE: At the date of editing this guide, the newest available Oracle 11g version for
Microsoft Windows was 11.1.0.7.0. Intershop therefore recommends to use Oracle 10gR2 (10.2.0.4.0) on Windows platforms.
Oracle 10gR2 for Windows Server 2003 The software to be installed is Oracle Database 10g Release 2 (10.2.0.1.0) for Microsoft Windows (x64) and includes the following packages: 102010_win64_x64_database.zip for the server, 102010_win64_x64_client.zip for the client, and p6810189_10204_MSWIN-x86-64.zip as required patch set for both server and client.
Oracle 10gR2 for Windows Server 2008 The software to be installed is Oracle Database 10g Release 2 (10.2.0.4.0) for Microsoft Windows Vista x64 and Microsoft Windows Server 2008 x64 and includes the following packages: 10204_vista_w2k8_x64_production_db.zip for the server, and 10204_vista_w2k8_x64_production_client.zip for the client.
The corresponding documentation for both installations is the Oracle Database Quick Installation Guide 10g Release 2 (10.2) for Microsoft Windows (x64), Part Number B15682-04, January 2009.
Page 17
Prerequisites
Creating an Enfinity Suite 6 Database

This section describes how to create a database for Enfinity Suite 6 using the Enfinity Suite 6 database setup program. As already mentioned in section Installing the Oracle Database Software, on p. 13, the term database is used slightly simplified in this guide to refer both to the database (a collection of files) and the instance operating on the database. Hence, creating the database includes (among other things) creating special tablespaces and associated data files required by Enfinity Suite 6, such as IS_TEMP, IS_USERS, IS_INDX, and IS_INDX_CTX, and also involves creating appropriate parameter files (such as an init.ora file) to work with this database.
Prerequisites
Before creating an Intershop database instance, ensure that the target machine meets the necessary system requirements. The machine must have at least 2 GB of disk space. The Oracle database server software must already be installed.
Database Setup Process

To create a database for Enfinity Suite 6, proceed as follows: 1. Log on. On Windows, log on as administrator or as user with administrative rights. On Linux/Solaris, log on as root.
2. On the Enfinity Suite 6 Installation CD (Server CD), launch the setup wizard. Use the executable or script located on the installation CD in /setup/database. On Windows, execute the setup.exe. On Linux/Solaris, export the DISPLAY variable to your X client, then run
# ./install.sh -gui
This opens the Welcome Page (Figure 1).
Page 18
Figure 1: Welcome page
Click Next to continue.
NOTE: On Linux/Solaris, you can run the Enfinity Suite 6 database setup in text
mode, instead of using the GUI mode. To use text mode, start the installation with ./install.sh -text.
3. Provide settings for Oracle dba user and group (Linux/Solaris only) and for home and installation directories. Linux/Solaris only: Provide oracle as dba user and oinstall as dba group. The installation directory <ora_install> is used to unpack scripts, templates, log files, and other resources.
NOTE: The name of the installation directory must not contain any
whitespace characters.
The Oracle base directory (<ora_base>) is the root directory for Oracle software components. It includes the Oracle home directories for all installed Oracle product components. The Oracle home directory (<ora_home>) is the home for Oracle software users and has been set during database server software installation.
Page 19
Figure 2: System Parameters
Click Next to continue. 4. Provide settings for database host and service. The Database Service Name (<DB.NAME>) defines the name under which the database is known to a domain. The Database Hostname (<SYSTEM.DB.HOSTNAME>) is obtained from the local host where the setup program is executed. The Database Domain name (<DB.DOMAIN>) is drawn from the sqlnet.ora file (NAMES.DEFAULT_DOMAIN). It has been set by the Net Configuration Assistant and cannot be modified in the panel. The Database Listener is a server-based process that provides basic network connectivity for clients and external processes. The standard port is 1521. If you set a different port number, you have to provide it when installing the Oracle client and when configuring the database connection during Enfinity Suite 6 setup.
NOTE: In addition, you should check the listener.ora in the <ora_home>/

network/admin to make sure to use the same port.
The System Identifier (SID) [<DB.SID>] is a non-ambiguous term for a specific database instance. The SID must not consist of more than eight (alphanumeric) characters.
Page 20
Figure 3: Database Parameters
CAUTION: Database service name and SID must be unique on the database
server.
Click Next to continue. 5. Select User/Schema Structure. The database setup program provides two options: Single Database Account This creates a single database user/schema and is suitable for a single machine installation. This option is assumed in the remainder of this section. Two User Accounts This option provides additional panels to support advanced deployment scenarios. The additional settings are described in detail in Preparing the Database for Data Replication, on p. 29.
Figure 4: User Account Creation
Page 21
Select Single database account and click Next to continue.
NOTE: The following description continues with Single Database Account. See
Preparing the Database for Data Replication, on p. 29 for additional settings
necessary when creating two users/schemes.
6. Enter user name and password. The settings provide the values for the system parameters <IS.AS.DB.CONNECTION.USER> and <IS.AS.DB.CONNECTION.PASSWD>.
Figure 5: User Account Details
Click Next to continue. 7. Specify Net configuration settings. On this panel, you can choose to update Oracle network configuration files and execute SQL scripts immediately after generation It is recommended to have both tasks executed automatically unless otherwise forced. See Manual Update of Network Configuration Files, on p. 33, and Manual Database Creation, on p. 34, for information of manual execution of these tasks in case you deselect a check box.
Page 22
Figure 6: Net/SQL Options
Select both checkboxes and click Next to continue. 8. Overwrite existing network configuration files.
Figure 7: Overwrite existing network configuration
9. Define location of installation components. The database setup program provides two options: Default Locations This means that all database files (data files, redo log files, control files, etc.) are written into a single directory <ora_base>/<sid>/oradata. With the settings assumed so far (for Windows), the location for the database files would be
D:\oracle\isorcl1\oradata
If you accept the default location, click Next to continue with Step 10, on p. 24.
Page 23
Locations for Custom Installations If you want to define custom locations, you are first presented with panels to define the locations before proceeding with Step 10, on p. 24.
Figure 8: Specify OFA settings
Click Next to continue. 10.Select the language. This setting provides the default for Oracle Text. Possible values are, for example, AMERICAN or GERMAN.
Figure 9: Specify NLS settings
Page 24
11.Verify all settings and click Start to start the installation process.
Figure 10: Verify setup settings
Click Start to continue. During the installation, a panel is displayed providing information on the component currently installed and the overall installation progress. Successful installation is confirmed by the summary panel as shown in Figure 11.
Figure 11: Installation summary
Note that at the end of the setup process, the setup program starts the Oracle listener. If this fails, an according note is displayed in the summary panel.
Page 25
Testing the Database
In this case, check the listener configuration file listener.ora, located in <ora_home>/network/admin: for a corresponding address entry in the LISTENER section
(ADDRESS = (PROTOCOL = TCP)(HOST = <db_host>)(PORT = 1521))
and for a corresponding SID entry in the SID_LIST_LISTENER section

(SID_DESC = (GLOBAL_DBNAME = <DB.NAME>) (ORACLE_HOME = <ora_home>) (SID_NAME = <DB.SID>) )
In addition, you may check the listener.log for possible errors. For more details on testing the database, refer to Testing the Database, on p. 26.

After creating the Enfinity Suite 6 database instance, perform the following tests to make sure that the Oracle database is working properly.
Log On as Sysdba
The command
sqlplus "sys/intershop as sysdba"
will open the SQL*Plus prompt and log on as sysdba. On Windows Open a command prompt, change to the <ora_base> directory (D:\oracle in the example below) and proceed as follows:
NOTE: Make sure to adjust settings for ORACLE_HOME and ORACLE_SID to your
installation.
D:\oracle>set ORACLE_SID=ISORCL1 D:\oracle>set ORACLE_HOME=D:\oracle\product\10.2.0\db_1 D:\oracle>set PATH=%ORACLE_HOME%\bin;%PATH% D:\oracle>sqlplus "sys/intershop as sysdba" SQL*Plus: Release 10.2.0.4.0 - Production on Mon Jul 25 08:42:30 2005 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Release 10.2.0.4.0 - Production SQL>
You can leave SQL*Plus with the command exit.
Page 26
On Linux/Solaris Adjust the settings for ORACLE_BASE, ORACLE_HOME, ORACLE_SID and PATH for the user oracle, for example:
ORACLE_SID=ISORCL1 ORACLE_BASE=/opt/oracle ORACLE_HOME=$ORACLE_BASE/product/10.2.0/db_1 PATH=$PATH:$ORACLE_HOME/bin
NOTE: For details about further Oracle Database and operating system environment
variables, refer to the corresponding Oracle Database Administrators Reference.
Once the settings have been adjusted, switch to user oracle and proceed as follows:
$ sqlplus "sys/intershop as sysdba" SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jul 25 10:35:25 2008 Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to: Oracle Database 10g Release 10.2.0.4.0 - Production SQL>
You can leave SQL*Plus with the command exit.
Check Character Set Settings

Log on as sysdba (see Log On as Sysdba, on p. 26) and issue the following statement:
SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%'; PARAMETER VALUE -----------------------------------NLS_CHARACTERSET AL32UTF8
The character set must be set to AL32UTF8.
Page 27
Check Database Users

Log on as sysdba (see Log On as Sysdba, on p. 26) and issue the following statement:
SQL> select username from dba_users; USERNAME -----------------------------CTXSYS OUTLN DBSNMP INTERSHOP SYS SYSTEM DIP WMSYS
Check that the users INTERSHOP and CTXSYS are returned. Exit SQL*Plus.
Stop and Restart the Listener

Stop Listener On Windows, open a command prompt and change to the Oracle base directory. On Linux/Solaris, log on as user oracle. Issue the following command:
$ lsnrctl stop
The command returns the following output:

LSNRCTL for 32-bit Windows: Version 10.2.0.4.0 - Production on 25-JUL-2008 Copyright (c) 1991, 2008, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) The command completed successfully
Restart the Listener Issue the following command:

lsnrctl start
The command returns the following output:

LSNRCTL for 32-bit Windows: Version 10.2.0.4.0 - Production on 25-JUL-2008 12:48:34 Copyright (c) 1991, 2008, Oracle. Starting tnslsnr: please wait... TNSLSNR for 32-bit Windows: Version 10.2.0.4.0 - Production System parameter file is <ora_home>\network\admin\listener.ora Log messages written to <ora_home>\network\log\listener.log Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROCipc))) All rights reserved.
Page 28
Preparing the Database for Data Replication
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<db_host>)(PORT=1521))) Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) STATUS of the LISTENER -----------------------Alias LISTENER Version TNSLSNR for 32-bit Windows: Version 10.2.0.4.0 Production Start Date 20-JUL-2008 12:48:37 Uptime 0 days 0 hr. 0 min. 2 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File <ora_home>\network\admin\listener.ora Listener Log File <ora_home>\network\log\listener.log Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROCipc))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<db_host>)(PORT=1521))) Services Summary... Service "isdb1.world" has 1 instance(s). Instance "ISORCL1", status READY, has 1 handler(s) for this service... The command completed successfully
Make sure the service (isdb1.world in the example above) has started properly. In case of errors, check the listener log file in <ora_home>/network/log/listener.log.
Perform Project-Specific Database Adjustments

Based on your individual project-specific needs, you may need to tune several database details. This may include, for instance, adapting the context index to your locale, recreating the stopword list, etc.
NOTE: For details about specific database settings, refer to the Intershop Technical
Paper Enfinity Suite 6 Database Tuning.

The database setup program provides means to automatically prepare the environment for a data replication scenario connecting a source and a target system. The database setup creates user/schemes for source and target system creates the database link connecting target and source system
NOTE: Apart from preparing the database, additional tasks are necessary to set up a
data replication scenario. See the Administration and Configuration Guide for details. The Administration and Configuration Guide also describes how to create the database link manually in order to connect existing installations for data replication.
Page 29
The workflow and the specific options to use when preparing a database for data replication depend on the data replication scenario. Two general data replication scenarios can be distinguished.
Local Data Replication The local data replication scenario assumes a single instance for both the source and the target system. The database setup creates two database users/schemes in the database: one schema for the source system and one for the target system. Workflow and settings are described in Local Data Replication, on p. 30. Remote Data Replication In the remote data replication scenario, two different instances are used, possibly residing on different hosts. In this scenario, the database setup program needs to be executed twice. See Remote Data Replication, on p. 32, for details.
Local Data Replication

This section describes how to proceed in case the database is prepared for a local database replication scenario. Proceed as follows: 1. Proceed from Step 2 to Step 5, as described in section Database Setup Process, on p. 18.
NOTE: The parameters entered on the panel in Figure 2, on p. 20 are interpreted

to refer to the live system.
2. On the User Account panel, select Two User Accounts.

Figure 12: Creating two user accounts
Page 30
3. Provide User details for source and target system. Use default names and password or modify settings if necessary.
Figure 13: Defining user accounts for source and target system
Click Next to continue. 4. Provide Parameters for the Source System. The following parameters must be entered: Database Hostname: <STAGING.EDIT.DB.HOSTNAME> Database Domain: <STAGING.EDIT.DB.DOMAIN> Database Listener Port: <STAGING.EDIT.DB.LISTENER.PORT> Database System Identifier: <STAGING.EDIT.DB.SID> Database User Name: <STAGING.EDIT.DBCONNECTION.USER> Database User Password: <STAGING.EDIT.DBCONNECTION.PASSWD>
NOTE: For the target system, the setup assumes the values provided in Step 4,
on p. 20 (also see Figure 2, on p. 20). In case of local data replication, source and target system use the same database. Therefore, make sure the settings provided for the source system in this panel are identical with the settings for the target system, provided in Step 4, on p. 20.
Using these parameters, the Intershop database setup program creates the necessary database link between the source and the target system.
Page 31
Figure 14: Defining the source system configuration
Click Next to continue. The setup now continues with Step 7, on p. 22.
Remote Data Replication

This section describes how to proceed in case the database is prepared for a remote data replication scenario, in which source and target system use two separate instances that reside on different hosts. When preparing the database for a remote data replication scenario, the database setup program must be run twice: first on the source system system, then on the target system. 1. Run the database setup on the source system, using the process described in Database Setup Process, on p. 18. The database setup program creates a database instance and a user/ schema for the source system. 2. Run the database setup on the target system, using the process described in Local Data Replication, on p. 30. Take care of the following issues: Database parameters entered on the panel in Figure 2, on p. 20, refer to the target system. Database parameters entered on the panel in Figure 14, on p. 32, refer to the source system. Database user name and password for the source system provided on the panel in Figure 14, on p. 32, must be identical to the database user account and password generated on the source system in Step 1, on p. 32.
Page 32
Manual Update of Network Configuration Files
Manual Update of Network Configuration Files

CAUTION: Manual update of network configuration files requires experience with
Oracle administration.
This section describes how to manually update the network configuration files. This is necessary, for example, if you have chosen not to update the Oracle network configuration automatically during the database instance creation process (see Figure 6, on p. 23). A manual update affects the following files: sqlnet.ora tnsnames.ora listener.ora
The files are located in the <ora_home>/network/admin directory.
NOTE: The manual update only affects these files on the server-side.
Proceed as follows: 1. Go to the <ora_home>/network/admin directory and open the sqlnet.ora configuration file. 2. Check the following entries in the sqlnet.ora file. NAMES.DEFAULT_DOMAIN The value (e.g., world) identifies the database domain name (<DB.DOMAIN>) of your system (see Figure 2). NAMES.DIRECTORY_PATH The value must include TNSNAMES, as illustrated by the sample below:
NAMES.DIRECTORY_PATH= (HOSTNAME, TNSNAMES, EZCONNECT)
3. Open the tnsnames.ora file in the <ora_home>/network/admin directory. 4. In a data replication scenario, add the entry ISEDITING.<STAGING.EDIT.DB.DOMAIN> to the tnsnames.ora file. Add the following entry at the bottom of the file. Replace the place holders with values appropriate for your environment.
ISEDITING.<STAGING.EDIT.DB.DOMAIN> = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <STAGING.EDIT.DB.HOSTNAME>) (PORT =<STAGING.EDIT.DB.LISTENER.PORT>)) (CONNECT_DATA = (SID = <STAGING.EDIT.DB.SID>) ) )
Page 33
Manual Database Creation
5. Locate the <ora_home>/network/admin directory and open the listener.ora file. An example file which is already configured is shown below. Note that the settings for <DB.NAME>, <DB.DOMAIN>, <SYSTEM.ORACLE.HOME> and <DB.SID> vary depending on the system environment and the platform. Adjust these settings according to your system.
# LISTENER.ORA Network Configuration File: <ora_home>/network/admin/ listener.ora # Generated by Oracle configuration tools. LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC)) ) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <db_host>)(PORT = 1521)) ) ) )) SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = isdb1.world) (ORACLE_HOME = <ora_home>) (SID_NAME = ISORCL1) ) (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = <ora_home>) (PROGRAM = extproc) ) ))
6. Stop and restart the Listener for changes to take effect. See Stop and Restart the Listener, on p. 28.

CAUTION: Manual database creation is recommended for experienced users
only. Instead of creating a database instance manually, you can run the database instance setup program again.
Create New Instance Manually Using Scripts

This section describes how to manually create a new database instance for Enfinity Suite 6 using the SQL scripts provided by the Enfinity Suite 6 database setup. You need to execute the database setup at least once to be able to access the scripts. During the setup process, uncheck the option Execute SQL scripts after generation (see Figure 15, on p. 37). This installs the scripts that you can then execute manually afterwards.
Page 34
The SQL scripts reside in the directory <ora_install>/database. The directory <ora_install>/database/templates contains configuration file and SQL script templates with placeholders for all configuration parameters. During the installation, these placeholders are substituted by real values. The files with real values are copied to the directories <ora_install>/ database/<DB.SID>/config and <ora_install>/database/<DB.SID>/script. For each SQL script executed, a log file is created in the <DB.SID>/log directory.
Table 1 provides an overview of all configuration files and executable SQL files.
Table 1: Configuration files and executable SQL files for database creation
<IS.INSTALL.DIR>/database
./templates/config/ init.ora listener.ora sqlnet.ora tnsnames.ora
Description
Template configuration directory Parameter template file Contains settings that control the operation of the Net Listener. Contains settings that control various aspects of Nets operation Translates net service names to specific server addresses and instance names. Entry of the database link template Template script directory Batch file/script to create directories, services, and to set the administrator password Main batch file/script to wrap the SQL command sequences SQL file to create the database, the system table space, and redo-log files SQL file to create table spaces This script only creates table spaces that are not Intershop-specific. Intershop-specific table spaces are created by the script INTERSHOPcreateTablespacesISH.sql SQL file to create a catalog SQL file to install Oracle Text. SQL file to alter user-default table spaces SQL file to set grants
tnsnames.ora.db.link ./templates/script DBconfigure.bat, DBconfigure.sh
INTERSHOP.bat, INTERSHOP.sh INTERSHOPcreateDB.sql INTERSHOPcreateTablespaces.sql
INTERSHOPcreateCatalog.sql INTERSHOPcontext.sql INTERSHOPalterTablespace.sql INTERSHOPgrantsToSystem.sql
Page 35
<IS.INSTALL.DIR>/database
INTERSHOPsetSystemPasswords. sql INTERSHOPcreateUserEditing.sql INTESHOPcreateUserLive.sql
Description
SQL file to set system passwords SQL file to create source system database user SQL file to create target system database user. This script is also invoked in case the system works with a single user/schema only. SQL file to create database link SQL file to create Intershop-specific table spaces. Table spaces that are not Intershop-specific are created by the SQL script INTERSHOPcreateTablespaces.sql SQL to perform additional Oracle installation tasks, such as installing SQL Plus help files.
INTERSHOPcreateDBlink.sql INTERSHOPcreateTablespacesISH. sql
INTERSHOPpostCreation.sql
In order to create a new database instance manually using the scripts, proceed as follows: 1. Log on. On Windows, log on as administrator or as user with administrative rights. On Linux/Solaris, log on as root user.
2. Run the Enfinity Suite 6 Database Setup to create the scripts and SQL files for the new database instance. To create a set of SQL files for a new database instance, make sure to deselect the option Execute SQL scripts after generation on the panel Net and SQL Script Options (see Figure 15). The setup creates the new <DB.SID> directory, copies the SQL files and replaces all placeholders with values appropriate for your installation.
Page 36
Figure 15: Net and SQL Script Options
3. Change to the template directory of the new database instance. Change to <ora_install>/database/<DB.SID>/script. 4. Linux/Solaris only: Run the DBconfigure.sh script as root. 5. Linux/Solaris only: Switch to user oracle.
# su - oracle
6. Run the INTERSHOP.bat file (Windows) or INTERSHOP.sh script (Linux/Solaris). The batch file/script invokes all SQL scripts in the directory.
NOTE: Instead of running the Enfinity Suite 6 database setup, you can create the template directories for the new database instance (in <ora_install>/database/ <DB.SID>) and copy the scripts manually. In this case, make sure to replace all placeholders in the scripts with values appropriate for your installation.
Prepare Existing Instance for Enfinity Suite 6

CAUTION: The procedures described in this section must be performed as
sysdba.
This section describes how to prepare an existing database instance for use with Enfinity Suite 6. Preparing the database instance requires to

create the tablespaces required by Enfinity Suite 6 create the Enfinity Suite 6 database user(s).
Page 37
Before You Start Before you start creating tablespaces and user accounts, check whether your database instance meets the following requirements: The character set has to be set to AL32UTF8. See Check Character Set Settings, on p. 27. Oracle Text must be installed. To test this, check whether the database user CTXSYS exists. See Check Database Users, on p. 28.
Create Tablespaces Enfinity Suite 6 requires the tablespaces IS_TEMP, IS_USERS, IS_INDX and IS_INDX_CTX. All tablespaces are referenced in the orm.properties file (located in <IS.INSTANCE.DIR>/share/system/config/cluster) by the key intershop.jdbc.tablespaces.
IS_TEMP and IS_USERS are also referred to when creating the database user
(see Create Database User, on p. 38).
NOTE: Make sure the physical locations, directories and filenames meet your needs.
Spread the files over several controllers/disks to improve the I/O performance. Redo log files and their copies should be placed on dedicated, fast disks.
The sample below illustrates how to create the tablespaces. Note that the placeholder <path> must be replaced with path settings appropriate for your system.
CREATE TEMPORARY TABLESPACE IS_TEMP TEMPFILE '<path>/IS_TEMP_01.dbf' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 2M; CREATE TABLESPACE IS_USERS DATAFILE '<path>/IS_USERS_01.dbf' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE IS_INDX DATAFILE '<path>/IS_INDX_01.dbf' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE IS_INDX_CTX DATAFILE '<path>/IS_INDX_CTX_01.dbf' SIZE 1G REUSE AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
Create Database User At least one database user is required. The database user needs to be provided later on when installing Enfinity Suite 6. It is referenced in the orm.properties file (located in <IS.INSTANCE.DIR>/share/system/config/ cluster) by the key intershop.jdbc.user.
Page 38
More complex Enfinity Suite 6 deployments may require additional database users. For example, in data replication scenarios, an additional database user is required for the source system, referenced in the staging.properties file (located in <IS.INSTANCE.DIR>/share/system/config/cluster) by the key staging.editing.schema.name. The example below illustrates how to create the database user INTERSHOP.
DEFINE AUSER='INTERSHOP' CREATE USER &AUSER IDENTIFIED BY &AUSER DEFAULT TABLESPACE "IS_USERS" TEMPORARY TABLESPACE "IS_TEMP" PROFILE DEFAULT ACCOUNT UNLOCK; GRANT "CONNECT","RESOURCE","CTXAPP" TO &AUSER; ALTER USER &AUSER DEFAULT ROLE ALL; REVOKE UNLIMITED TABLESPACE FROM &AUSER; ALTER USER &AUSER QUOTA UNLIMITED ON IS_USERS; ALTER USER &AUSER QUOTA UNLIMITED ON IS_INDX; ALTER USER &AUSER QUOTA UNLIMITED ON IS_INDX_CTX; GRANT GRANT GRANT GRANT GRANT GRANT GRANT GRANT GRANT GRANT GRANT GRANT CREATE CLUSTER TO &AUSER; CREATE DATABASE LINK TO &AUSER; CREATE SEQUENCE TO &AUSER; CREATE SYNONYM TO &AUSER; CREATE TABLE TO &AUSER; CREATE VIEW TO &AUSER; CREATE SNAPSHOT TO &AUSER; CREATE MATERIALIZED VIEW TO &AUSER; CREATE PROCEDURE TO &AUSER; CREATE TRIGGER TO &AUSER; CREATE TYPE TO &AUSER; EXECUTE ON CTX_DDL TO &AUSER;
Page 39
Page 40

Enfsuite64 Admin Database PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Enfsuite64 Admin Database PDF

Uploaded by

Copyright:

Available Formats

Enfinity Suite 6.

Database Setup Guide

Copyright 2005-2010 Intershop Communications. All Rights Reserved.

Document ID: EMS-LIB-64-51-01

Chapter 2 Database Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About this Guide

About this Guide

About this Guide

Before You Start

Before You Start

Verify Content of Installation DVD

If the test fails, contact INTERSHOP to get help.

Installing the Oracle Database Software

Installing the Oracle Database Software

Chapter 2: Database Setup

Installing the Oracle Database Software

Chapter 2: Database Setup

Installing the Oracle Database Software

Solaris SPARC 64-Bit

Solaris SPARC 64-Bit

Chapter 2: Database Setup

Installing the Oracle Database Software

Chapter 2: Database Setup

Installing the Oracle Database Software

Chapter 2: Database Setup

Creating an Enfinity Suite 6 Database

Creating an Enfinity Suite 6 Database

Database Setup Process

This opens the Welcome Page (Figure 1).

Chapter 2: Database Setup

Creating an Enfinity Suite 6 Database

Database Setup Process

Figure 1: Welcome page

Click Next to continue.

Chapter 2: Database Setup

Database Setup Process

Creating an Enfinity Suite 6 Database

Figure 2: System Parameters

NOTE: In addition, you should check the listener.ora in the <ora_home>/

Chapter 2: Database Setup

Creating an Enfinity Suite 6 Database

Database Setup Process

Figure 3: Database Parameters

Chapter 2: Database Setup

Database Setup Process

Creating an Enfinity Suite 6 Database

Select Single database account and click Next to continue.

Chapter 2: Database Setup

Creating an Enfinity Suite 6 Database

Database Setup Process

Figure 6: Net/SQL Options

Chapter 2: Database Setup

Database Setup Process

Creating an Enfinity Suite 6 Database

Figure 8: Specify OFA settings

Click Next to continue.

Chapter 2: Database Setup

Creating an Enfinity Suite 6 Database

Database Setup Process

Chapter 2: Database Setup

Testing the Database

Creating an Enfinity Suite 6 Database