Documente Academic
Documente Profesional
Documente Cultură
DMAR1-PE-200006H-Updated
Copyright
Copyright 2000-2007, Intergraph Corporation. All Rights Reserved. Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, SmartSketch, FrameWorks, INtools, MARIAN, and IntelliShip are registered trademarks and SupportModeler and SupportManager are trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. Other brands and product names are trademarks of their respective owners.
Table of Contents
Table of Contents
Overview .............................................................................................................................6 Three-Tier Architecture ................................................................................................6
Service Packs ...................................................................................................................... 8 Internationalization ............................................................................................................. 8
SmartPlant Materials Hardware and Software Requirements ...................................10 SmartPlant Materials Application Server (iAS) .........................................................11 SmartPlant Materials Database Server .......................................................................15 Installing SmartPlant Materials Software.....................................................................17 Part 1: Oracle 10g iAS Release 2 Installation ...............................................................28 Printer Installation on SmartPlant Materials Application Server ...............................28
Pre-Installation Tasks........................................................................................................ 32 Set the User to Belong to the Administrators Group ........................................................ 33 Check Environment Variables .......................................................................................... 34 Check to see if Port 1521 is in Use ................................................................................... 34 Regional and Language Options During Installation........................................................ 35
Part 2: iAS SmartPlant Materials Specific Post-Installation ......................................75 Starting and Stopping 10g iAS ...................................................................................75 Part 3: Oracle Database Server Installation .................................................................77 SmartPlant Materials Database Server .......................................................................77
Database Server Software Installation .............................................................................. 79 Installing the Oracle 10g Database Patchset 10.2.0.2 (Patch #4547817).......................... 88 Installing the Oracle 10g Database Patchset 10.2.0.3 (Patch #p5337014)........................ 91 Installing the Oracle 10g Database One Off Patchset 10.2.0.3 (Patch # p5731535) ........ 98
Part 4: SmartPlant Materials Database Installation and Configuration .................101 Creating a SmartPlant Materials 6.2 Basic Database ...............................................101
Important SmartPlant Materials Settings in the init.ora File........................................... 102
Part 5: SmartPlant Materials Database Fresh Installation .......................................122 Installing SmartPlant Materials into an Empty Database.........................................122 Part 6: SmartPlant Materials Database Migration from 6.1.....................................127 Migrating MARIAN 6.1 SP19 to SmartPlant Materials 2007 (6.2).........................127
Backing up the Database................................................................................................. 127
Importing a Database Export Dump File..................................................................129 Prerequisites for the Migration .................................................................................130 Migrating the Database to ORACLE 10g Release 2 ................................................132 Starting the Migration of SmartPlant Materials .......................................................133
Analyzing the Schema .................................................................................................... 137
Part 7: Setting up SmartPlant Materials 2007 (6.2) License Keys............................138 Part 8: Logging On To Your SmartPlant Materials Database..................................139 Application Server Manual Installation Steps ..........................................................140 Manual Installation of SmartPlant Materials Reports Service .................................141
Maintain Settings Related to Forms-Java Classes .......................................................... 144 Copy Java-Servlet Classes and Maintain Settings .......................................................... 145 Copy the Applet JAR File............................................................................................... 145 Maintain the Registry...................................................................................................... 146 Change Keyboard Mapping ............................................................................................ 147 Map the Icons.................................................................................................................. 147 Create Path-Mappings..................................................................................................... 148 Create an Entry for the SmartPlant Materials Starter Page............................................. 148 Updating the Repository ................................................................................................. 149 Online Reference Library ............................................................................................... 150 Webhelp Server Name .................................................................................................... 150 Client Browser Issues ..................................................................................................... 150
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings ..........................153 Transferring Files to and from SmartPlant Materials in a Web Environment..........153
Comparing Client/Server to Web Environment.............................................................. 153 Downloading (Receiving) Files from SmartPlant Materials 2007 (6.2) ......................... 156 Uploading (Sending) Files to SmartPlant Materials 2007 (6.2)...................................... 170 Missing Modules for Upload/Download ........................................................................ 178
Table of Contents Part 10: Low Usage Integrated SmartPlant Materials Server ..................................179 SmartPlant Materials Integrated Server....................................................................180
Database Server Software Installation ............................................................................ 180 Installing the Oracle 10g Database Patchset 10.2.0.2 (Patch #4547817)........................ 190 Installing the Oracle 10g Database Patchset 10.2.0.3 (Patch #p5337014)...................... 194 Installing the Oracle 10g Database One Off Patchset 10.2.0.3 (Patch # p5731535) ...... 200
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant ..........................................................................................................................................257 SmartPlant Materials and Microsoft Vista .................................................................272 Vista-Specific Settings on the Application Server ...................................................272
Changes in formsweb.cfg: .............................................................................................. 272 Vista Playground in formsweb.cfg ................................................................................. 273 Vista-Specific Settings on the SmartPlant Materials Client ........................................... 273
SmartPlant Materials Installation Pitfalls...................................................................279 Known Problems during SmartPlant Materials Login .............................................279
Case 1 FRM-40735: WHEN-NEW-FORM ORA-06502 .......................................... 279
SmartPlant Materials on Citrix....................................................................................282 Citrix Server Settings................................................................................................282 SmartPlant Materials Citrix Client Installation ........................................................293 User Comments Form ...................................................................................................307 Index................................................................................................................................308
Overview
Overview
This document describes how to install SmartPlant Materials version 2007.3 (6.2.4). Note
The following name changes are taking effect in this version of the software: "MARIAN" is changing to "SmartPlant Materials" and "MLCL" is changing to "SmartPlant Reference Data".
Three-Tier Architecture
SmartPlant Materials uses three-tier-architecture technology with Oracle 10g iAS R2.
Client Tier The user accesses the application server through an HTTP request. That is, he enters a URL or bookmark in an Internet browser. The GUI (graphical user interface) is run as a Java-Applet. The Applet communicates with the application server by HTTP or a socket connection, sending user input to the application server and receiving representation instructions from the application server.
Overview Middle Tier The application server runs the ORACLE Forms and Reports modules that contain one part of the SmartPlant Materials business logic. The application server receives user input from the Client Tier and returns instructions to the user. The client and middle tiers upload and download functionality to exchange complete files from one file system to the other. The application server connects via SQL*Net to a database to receive user data or system messages, and to send requests or user data to update the database. With Release 2 of Oracle10giAS, the middle tier consists of two installations: 1. The Oracle10giAS Infrastructure installation creates a combination of a metadata repository database, single sign-on server, LDAP directory server, and management server that supports Oracle10giAS deployment. The infrastructure database contains a collection of schemas and metadata that enable Oracle10giAS components. If you use a farm of application servers to serve your users, the infrastructure server will be the capital of all application servers that connect to the infrastructure like clients to a server. 2. The Application Server installation, where SmartPlant Materials software is located. You may choose to install the infrastructure and application server on two different machines, because either you plan to have multiple application servers running a load balanced SmartPlant Materials or to improve performance. In this installation guide we assume, that you will have one application server for SmartPlant Materials and that you install infrastructure and application server on the same machine. Database Tier The database contains objects to store the SmartPlant Materials data, the user and system data itself, as well as the second part of the SmartPlant Materials business logic.
For Support or Services in the U.S., call (800) 766-7701. For Support or Services outside the U.S., contact: Intergraph SmartPlant Materials Service Center Martin-Schmeier-Weg 18 D-44227 Dortmund Germany Phone: ++49-231/72596-111 Fax: ++49-231/72596-100 E-mail: MSC-DE@intergraph.com
Overview
Service Packs
SmartPlant Materials is one of the tools in SmartPlant Enterprise and is now using the service pack versioning associated with SmartPlant Enterprise. The following table lists the service packs for 6.1 and 6.2: Version 6.1 MARIAN 6.1 Service Pack 1, 2, 3, 4, 5, 6 MARIAN 6.1.2 Service Pack 7, 8, 9, 10, 11, 12 MARIAN 6.1.3 Service Pack 13 Version 6.2 MARIAN 2007 6.2.1 Initial release MARIAN 2007 6.2.1 SP1 MARIAN 2007 6.2.2 SP2, 3
SmartPlant MARIAN 6.1.4 Materials 2007 Service Pack 14, 6.2.3 SP4, 5, 6 15 SmartPlant MARIAN 6.1.5 Materials 2007 Service Pack 16, 6.2.4 17, 18, 19, 20, 21, 22, 23, 24, 25 For more information about service packs, see the How to Install a SmartPlant Materials Service Pack document.
Internationalization
Database creation in SmartPlant Materials is done through the use of scripts, which specify the character set options. SmartPlant Materials supports a homogeneous configuration. For more information, see the Multi-Language Support document that is delivered with SmartPlant Materials.
Overview
Oracle release notes often state that you should not install patches, except when you have problems with the base version. Reference environments exist at Intergraph to reproduce problems at your site. Development is done on the recommended versions/patchsets and we have the broadest experience with this versions/patchsets. Oracle issues with newer versions/patchsets can affect Oracle functions that are important for SmartPlant Materials. Independent implementations of the latest patches on Oracle 10giAS R2 are more complicated and time consuming than using patches Intergraph recommends.
Windows-based operating system supporting Microsoft Internet Explorer 5.x, 6.x, or 7.0. To run the Vista operating system, you must install a Java Add-On, and you must have Administrative access on the client. Notes Configure the application server and database server to be in the same domain. The computers should also be physically close to each other. The application server must have a fixed TCP/IP address. During installation, turn off virus scanners and virtual machine services. Restart these services after the installation.
Intergraph highly recommends the following minimal configuration for SmartPlant Materials application server: the SmartPlant Materials Database Server must be installed on a single, dedicated server without other production applications running on the same server hardware.
You will have to run two servers minimum as the 10giAS (SmartPlant Materials application server) and the 10g Database (SmartPlant Materials database server) will not be supported by Intergraph to run on a single machine. The application server and database server cannot be on the same machine, and other applications cannot be run on the SmartPlant Materials servers. To use SmartPlant Materials with Redwood Cronacle, your server must be supported by Redwood. In order to avoid port conflicts with Oracle iAS, no other web servers (IIS or others) should run on a SmartPlant Materials application server. The configuration is tightly related to the number of concurrent users working on the system. Refer to ORACLE documentation for detailed information.
Pentium 4 double processor XEON, 3 GHz or higher 4 GB RAM on the Application Server (1 GB RAM for infrastructure, 3 GB for application server) 80 GB hard disk for SmartPlant Materials and Oracle (approximate) DVD-ROM drive access, either locally or through a network connection Note All products and components except OracleAS Infrastructure are certified on AMD64 and Intel EM64T processors.
Printer for iAS Install the default printer before invoking the Oracle Universal Installer (OUI). You can use any printer supported by the operating system.
SmartPlant Materials Hardware and Software Requirements Other System Requirements The following table shows other system requirements. J2EE and Web Cache Memory1 Disk Space Space in TEMP directory Total pagefile size (virtual memory) Notes
(1) If you plan to install OracleAS Infrastructure plus either Business Intelligence and Forms or Portal and Wireless on the same computer, you need to have at least 1.5 GB of memory and 2.0 GB total pagefile size. (2) The OracleAS Infrastructure includes OracleAS Identity Management and OracleAS Metadata Repository. You can install the data files for the OracleAS Metadata Repository database on a disk that is different from the disk where you are installing OracleAS Infrastructure. If you do this, make sure the disk for the data files has at least 1.6 GB of free space. (3) 55 MB of free space in the TEMP directory are required to run the installer in addition to the 256 MB of space required for the installation. Oracle recommends 3.3 GB free space on hard disk for infrastructure, 1.6 GB for application server, 1 GB swap pagefile on hard disk for infrastructure, 1 GB for application server, and additionally 300 MB temp directory space. Warning
Important Settings
If your virtual memory is set to a value of less than 1 GB, the installation will stop with an error, complaining about lack of space.
Disk space for each of both installations must be available on a single drive. Oracle 10g iAS R2 does not support spanning the installation over multiple drives. Of course, you may install infrastructure and application server instance on two different drives, for example, infrastructure on C:\ and application server on D:\.
Oracle 10giAS Release 2 (10.1.2.0.2) for Microsoft Windows (Internet Application Server Enterprise Edition). Application Server 10g Release 2 (10.1.2.0.2) CD Media Pack B23149-14 10g (10.1.2.0.2) Quick Installation Guide B15908-01 10g (10.1.2.0.2) for Microsoft Windows (32-bit) (CD 1 of 3) B24453-01 10g (10.1.2.0.2) for Microsoft Windows (32-bit) (CD 2 of 3) B24454-01 10g (10.1.2.0.2) for Microsoft Windows (32-bit) (CD 3 of 3) B24455-01 P5174901 (You can download the patch from Oracle Metalink) Note The installation process was tested on an English Windows 2003 Server R2 installation. Total Pagefile size (Virtual Memory) 1.5 GB. Oracle requires a static IP before installation of 10g iAS. On the ORACLE Application Server, we require Excel 2002 SP3 or 2007. Excel is required for all Import/Export features of SmartPlant Materials. Microsoft Windows XP is supported for J2EE and Web Cache middle tier without OracleAS Infrastructure 10g Important
Media Packs
Installation Prerequisites
Microsoft Excel
You can install other Oracle Application Server installation types on Windows XP (the installer displays a warning, but allows you to continue), but they are not supported on Windows XP.
Microsoft Windows 2000 with Service Pack 3 or higher Microsoft Windows Server 2003 (32-bit) Important SmartPlant Materials is installed with an infrastructure and Windows XP is not officially supported by Oracle.
SmartPlant Materials Hardware and Software Requirements The Oracle Application Server is not supported on Windows operating systems that include Terminal Services. For example, Windows 2000 with Terminal Services is not supported. Oracle provides 32-bit and 64-bit versions of Oracle Application Server for Windows. The 32-bit version runs on Intel x86, AMD64, and Intel EM64T processors. For additional information, visit OracleMetaLink at http://metalink.oracle.com. Additional Information for the Application Server
To install and configure the SmartPlant Materials Discoverer Business Areas and Workbooks, you must install Oracle 10g Developer Suite Release 2 on the application server. This product is optional. To set up email functionality for SmartPlant Materials, the application server must have access to email servers. Backup software should not touch the Oracle 10iAS or Oracle infrastructure directories.
The SmartPlant Materials Database Server must be installed on a single, dedicated server without other production applications running on the same server hardware. You must run two servers minimum as the 10giAS (SmartPlant Materials application server) and the 10g Database (SmartPlant Materials database server) will not be supported by Intergraph to run on a single machine. To use SmartPlant Materials with Redwood Cronacle, your server must be supported by Redwood. The configuration is tightly related to the number of concurrent users working on the system. Refer to ORACLE documentation for detailed information. Pentium 4 double processor XEON, 3 GHz or higher 4 GB RAM 80 GB hard disk space for Oracle 200 GB hard disk for the SmartPlant Materials database files or more (Raid 5 recommended) DVD-ROM drive access, either locally or through a network connection
Hardware Recommendations
Supported Database Servers Oracle 10g Database Server Standard Edition Release 2 (10.2.0.1.0) Media Pack v4 for Windows B23862-01 Media for SmartPlant Materials Installation
Oracle Database Quick Installation Guide for Microsoft Windows B14318-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 1 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 2 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 3 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 4 of 6) B24558-01
10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 5 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 6 of 6) B24558-01 Patchset 4547817 (p4547817_10202_WINNT.zip. You can download the patch from Oracle Metalink) Patchset 5337014 (p5337014_10203_WINNT.zip You can download the patch from Oracle Metalink) Patchset 5731535 (p5731535_10203_WINNT.zip You can download the patch from Oracle Metalink) Note
The installation process was tested on an English Windows 2003 Server installation.
The installation of SmartPlant Materials on a Windows system must be performed as a local administrator or member of the local admin group.
Insert the SmartPlant Materials Installation CD-ROM. If the CD does not start automatically, run the CD_Browser.exe file. If any problems with the CD-browser occur, you can also start the SmartPlant Materials setup routine by running the setup.exe directly. Note
If you are using SmartPlant Enterprise, insert Disk 2 of the SmartPlant Enterprise 2007 DVD set.
Installing SmartPlant Materials Software Click one of the following CD-Browser options.
SmartPlant Materials Installation Guide. Opens the PDF file. This requires Acrobat Reader, version 7. Adobe Reader Installation. Starts the installation of Adobe Reader, version 7. Install SmartPlant Materials 2007. Starts the software installation of SmartPlant Materials 6.2. SmartPlant Materials 2007 (6.2) New Features. Opens the corresponding PDF file. This requires Acrobat Reader. Browse SmartPlant Materials Online Reference Library. Starts the Online Reference directly from the CD-ROM. Requires Internet Explorer. Our Web Site. Opens a link to Intergraph SmartPlant Materials web site. Requires Internet Explorer.
Click SmartPlant Materials Installation Guide to review or print installation instructions in this PDF file. (If you do not have Adobe Reader version 7 installed, click Adobe Reader Installation first.) Click Install SmartPlant Materials 2007 to start the installation.
Click Yes to start the Acrobat Reader version 7 installation. If you have Adobe Reader installed, you do not receive this prompt. Adobe Reader is required to view the license agreement. If not already installed, you will be prompted if you wish to install Adobe Reader now. In this case, follow Adobes installation instructions. After successful installation, you can continue with the License Agreement step of the SmartPlant Materials installation.
Choose your installation folder or leave the default directory, and click Next afterwards.
The SmartPlant Materials install wizard will now prepare your machine for the installation.
Click Next.
Enter your name and the name of your company, and then click Next.
Installing SmartPlant Materials Software The Complete setup type installs SmartPlant Materials completely. If you choose the Custom setup type and click Next, you can select the specific features of the SmartPlant Materials software that you want to install. The setup procedure asks for a disk drive and folder in which to install SmartPlant Materials. Important
Click Change, and specify an installation path that does NOT include spaces, for example, c:\marian. Do not use the default installation destination. Oracle Application Server requires an installation path that does not contain any spaces.
Click Next. Choose from the available features, and click Next. The features are:
Online Reference Library installs necessary resources for the SmartPlant Materials Online Reference Library. Select this feature also if you want the Online Reference Library to be available from the SmartPlant Materials application server. SmartPlant Materials 2007 Application Server files contains all necessary components to set up the application server for SmartPlant Materials. Note that the Online Reference Library is not included automatically. SmartPlant Materials 2007 Database Server files contains all necessary components to set up the SmartPlant Materials database. SmartPlant Materials 2007 MTI files contains all necessary files to set up the Tool for Integration. PDMS macros installs some additional macros to load PDMS files into SmartPlant Materials.
Name the program folder in which SmartPlant Materials will be installed, and click Next to continue.
Installing SmartPlant Materials Software When the installation process is complete, the following screen appears. Click Finish to end the installation program.
Depending on the version of MS Windows Installer currently installed on your machine, it might be necessary to reboot your system after the installation. In this case, you will be prompted to do so. If MS Windows Installer is already present in the required version, you wont be prompted at all.
Click Next.
You will find this default printer in the Printers and Faxes on the Control Panel when this configuration has finished successfully.
Pre-Installation Tasks
The TEMP system environment variable should point to a folder with a minimum of 800 MB of free space. Oracle requires a static IP before installation of 10g iAS Release. Intergraph recommends installing iAS on a machine with no other prior Oracle installations, so that this is the first Oracle home. Intergraph strongly recommends a configuration where the database and the application server are on separate machines. SmartPlant Materials web-enabled software is built on ORACLE 10g iAS, but the SmartPlant Materials installation process does not need Oracle 10g iAS preinstalled. Please install SmartPlant Materials (client) before installing the application server, so you can complete all manual post installation steps described in this manual. If you have iAS installed without SmartPlant Materials, you dont need to uninstall the iAS. Just install SmartPlant Materials and complete the post-installation steps that configure the application for the use with SmartPlant Materials. SmartPlant Materials database-server installation requires a running Oracle 10gR2 database. The database-server installation is a second step after the installation with InstallShield. The 10g iAS installation does not require the installation of SmartPlant Materials on the database, nor does it require the installation of the database tier at all. Intergraph recommends the installation of the database server, but if you have iAS installed without the database tier, you dont need to uninstall the iAS.
The user must be listed directly in the Administrators group. The user cannot belong to the group indirectly (for example, by being a member of a group that is part of the Administrators group). To check if you belong to the Administrators group:
Windows 2000 or Windows XP: On the desktop, right-click My Computer, and then click Manage.
Windows 2003: On the desktop, right-click the local computer icon, and then click Manage. 2. On the left side, expand Local Users and Groups, and click Users.
3. On the right side, right-click the user, and click Properties. This displays the Properties dialog box. 4. On the Properties dialog box, click the Member Of tab. If you are not a member of the Administrators group, get an administrator to add you to the group or log in as a user who is a member of the Administrators group.
How to Set Environment Variables This section describes how to set environment variables in Windows: 1. Display the System Control Panel.
Windows 2000: Click Start > Settings > Control Panel > System.
Windows 2003: Click Start > Control Panel > System. 2. Select the Advanced tab. 3. Click Environment Variables. 4. To change the value of a variable, select the variable, and click Edit.
Oracle Application Server requires minimum versions of some system files in the Windows system directory (typically, C:\Windows\system32 or C:\Winnt\system32). When you run the installer for Oracle Application Server, the installer checks the Windows system files on your computer. If it finds old versions of these files, and the files are in use by other processes, then it prompts you to exit the installer and run wsf.exe to install the latest Windows system files. (If it finds old versions of the files, but the files are not in use by other processes, then it just replaces the files and you do not have to run wsf.exe.) You can find wsf.exe in the same directory as the installer. To run wsf.exe, which you need to do only if prompted by the installer, perform these steps: 1. Start wsf.exe, which starts up Oracle Universal Installer to install the Windows system files. CD-ROM (assumes E: is the CD-ROM drive): E:\> wsf.exe DVD-ROM (assumes E: is the DVD-ROM drive): E:\> cd application_server E:\application_server> wsf.exe 2. At the Welcome screen, click Next. 3. On the File Locations screen , specify the following information: Destination Name: Enter a name for the Oracle home for wsf. Destination Path: Enter any full path. The installer installs the files in the proper system directories, regardless of the value you enter in this field. Click Next. 4. Warning: System Reboot Required screen If you see this screen, the installer will reboot your computer automatically at the end of this installation to complete the Windows system files installation. Save and close applications (other than this installer) that you have running on your computer. Click Next. 5. At the Summary screen, click Next to start installing the Windows system files. 6. At the End of Installation screen, click Exit to exit the installer.
Part 1: Oracle 10g iAS Release 2 Installation 7. If the installer displayed the "Warning: System Reboot Required" screen during installation, the installer will now reboot your computer. If not, please reboot your computer before continuing.
Click Next to reboot the machine. 8. After Windows restarts or at the end of the Windows System Files installation, restart the Oracle10g iAS installation.
Infrastructure Installation
Starting the Oracle Universal Installer (OUI)
If the autorun feature is active, the welcome-screen automatically pops up when you insert the CD. If not, start the setup.exe from the root directory of your installation CD. After the welcome screen appears, click Next. The load procedure requires that the machines virtual memory be set to 1024MB.
The Oracle Universal Installer will check the OS, display properties, and CPU speed, and then you see the OUI welcome screen.
Choose your first Oraclehome, which will become the home where your Oracle infrastructure instance will be stored. This is recommended to be done on a separate server for better performance. Anyway, we want to place it on the same machine, so please define C:\Oracle\oraInfra as your first Oraclehome on this application server. The home name must be within 16 characters and may only contain alphanumeric and underscores. Do not use blanks in the Home name or for the path. Please choose your first Oraclehome, which will become the home where your Oracle infrastructure instance will be stored.
Under Available Languages, click English to be your preferred language, and then click OK.
Click Oracle Application Server Infrastructure 10g (the second, middle option). Click Next. Click Identity Management and Metadata Repository (the first option).
Click Next. OUI displays a progress bar in the upper left corner.
Set the Administrator privileges as shown above, and then click Next.
Click Automatic for the port configuration, and then click Next.
Fill in the OCA fields similar to what is shown above, and then click Next.
Enter a password, and write it down for possible later usage. We have chosen manager1 as the password on this reference environment.
Rename the global database name to INFRA, and specify a database file location using the browse button to create a new oradata-directory in the infrastructure home.
Use the same password for all accounts. Enter a password and confirmation. Write down this password for possible later usage.
Specify an Instance name and enter the ias_admin password. This password will be used later to log on to the administration web pages. Click Next.
Your installation summary appears. Click Install to start the Infrastructure installation.
A progress window appears during the installation. This installation procedure will take a while. You can switch to the database server installation during this time on your second server.
Click Exit to end the installation of the first Oraclehome for the Infrastructure.
Click Yes. Now you can reach the new Infrastructure environment via an internet address, for example : http://dor-msc-as62:18100. To reach this link from inside Windows 2003 Server, you may have to change the security options of Internet Explorer to medium level.
A logon dialog box appears. Use ias_admin and your password to enter the Enterprise Manager web site.
iAS Installation
Installation of Oracle 10g Business Intelligence and Forms
This part of the installation will create a new Oraclehome including the Forms and Reports services, which are needed for the SmartPlant Materials installation.
Run setup.exe from Disk 1 again to invoke the Oracle Universal Installer (OUI).
Click Next.
Specify an new Oraclehome named oraIAS. Important: Do not use the existing Oraclehome for this installation. Click Next.
Under Available Languages, click English to be your preferred language, and then click OK.
Click Oracle Application Server 10g, the first option. Click Next.
Click the following options on the screen, and then click Next:
Oracle Application Server 10g Discoverer Oracle Application Server 10g Reports Services Oracle Application Server 10g Forms Services
You must check Reports and Forms. Intergraph recommends that you also select Discoverer to minimize possible later configuration, even if you arent using Discoverer now. Selecting Reports and Forms is sufficient if you are never going to use Discoverer. Refer to the SmartPlant Materials Discoverer documentation.
Enter your hostname (server name) and port 389 for the OID. Click Next.
Enter a password for orcladmin, and make sure that you remember it. Click Next.
Select your Metadata Repository, and click Next. The Metadata Repository is stored in the Infrastructure database, which was already created in your first Oraclehome.
Specify an Outgoing Mail Server, and click Next. If you dont know this information, request it from your local network administration team. This information may be used for Reports configuration. You can leave this field blank and configure this later.
Specify an Instance Name for your IAS-Instance, and enter the password. Click Next.
The product summary appears next. Click Install to start the installation.
Click Yes to exit the Oracle Universal Installer. To check the new services that were created during the IAS-Installation, open the OracleoraIASASControl service.
This is the Enterprise manager. Enter ias_admin as the username, and use the password you defined during installation.
You will now have two standalone instances displayed in OEM. Click the name of the IAS instance, not the INFRA instance, to have all components displayed. The linked page appears.
If there are errors here, click Restart all to start the components. Pass the warning and confirmation window. All components should be displayed as running afterwards.
Possible Errors
On the ias_home page in EM, the CPU usage and MEM usage sections may report a problem:
"The underlying data for the CPU usage chart is unavailable". "The underlying data for the memory usage chart is unavailable.
The problem is related to the locale settings, namely the decimal character (must be '.' for use in java). The problem is that the program used to collect the operating system statistics (in Windows) is sensitive to the locale settings used. But as the EM is launched as a service using LocalSystem as logon credentials, you have to go to the registry to modify the settings. Go to 'My Computer\HKEY_USERS\.DEFAULT\Control Panel\International', and modify the sDecimal setting to '.'.
The screen above displays to let you know that the forms service is running properly.
This is the Enterprise manager. Enter ias_admin as the username, and use the password you defined during installation.
You will now have two standalone instances displayed in OEM. Click the name of the IAS instance, not the INFRA instance, to have all components displayed.
Part 1: Oracle 10g iAS Release 2 Installation The linked page appears.
Click Yes when you are prompted to really stop this Application server.
Part 1: Oracle 10g iAS Release 2 Installation The Components appear as follows:
Set the Oracle environment variable C:\5174901>set oracle_home Environment variable oracle_home not defined C:\5174901>set oracle_home=C:\oracle\as_10gR2 Set the path variable to the opatch-directory. C:\5174901>set path=%path%;C:\oracle\as_10gR2\opatch Execute the patch installation C:\ 5174901>opatch apply
If you see the message above, your patch installation has finished successfully.
Before you start this configuration tool, all chapters before must be completed and all Services must be started. Please use the Oracle Enterprise Manager (OEM) to check these prerequisites. If you want to configure all settings manually, you may skip this chapter and perform all actions without using the wizard.
1. Specify your download folder name. 2. Enter your SmartPlant Materials database name (if it exists, the default is MAR62).
Part 1: Oracle 10g iAS Release 2 Installation 3. Choose a name for the reports server, which will be installed by the wizard. Warning
Choose a reports server name that does not exist on the network. If the reports server you use exists, the installation wizard will fail as shown on the next page.
4. Set the number of reports to run in parallel. The default is 20 reports. 5. Replacing FMX-files should be checked (forms_m_map will be set to yes in this case).
The wizard starts the configuration of your application server. This may take a few minutes.
Click Next.
A log file of this configuration is saved and will be stored in the %SPMat%\bin\mitfoas\log directory.
After the wizard has finished and if the database on the Database Server is already installed completely, you can click the link above to start SmartPlant Materials.
With Oracle 10g iAS, you can start and stop the Instances using shortcuts in the Oracle program groups as shown above. We have linked them to the desktop.
The SmartPlant Materials Database Server must be installed on a single, dedicated server without other production applications running on the same server hardware. You must run two servers minimum as the 10giAS (SmartPlant Materials application server) and the 10g Database (SmartPlant Materials database server) will not be supported by Intergraph to run on a single machine. To use SmartPlant Materials with Redwood Cronacle, your server must be supported by Redwood. The configuration is tightly related to the number of concurrent users working on the system. Refer to ORACLE documentation for detailed information. Pentium 4 double processor XEON, 3 GHz or higher 4 GB RAM 80 GB hard disk space for Oracle 200 GB hard disk for the SmartPlant Materials database files or more (Raid 5 recommended) DVD-ROM drive access, either locally or through a network connection
Supported Database Servers Oracle 10g Database Server Standard Edition Release 2 (10.2.0.1.0) Media Pack v4 for Windows B23862-01 Media for SmartPlant Materials Installation
Oracle Database Quick Installation Guide for Microsoft Windows B14318-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 1 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 2 of 6) B24558-01
10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 3 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 4 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 5 of 6) B24558-01 10g Release 2 (10.2.0.1.0) for Microsoft Windows (32-bit) DVD (Part 6 of 6) B24558-01 Patchset 4547817 (p4547817_10202_WINNT.zip. You can download the patch from Oracle Metalink) Patchset 5337014 (p5337014_10203_WINNT.zip You can download the patch from Oracle Metalink) Patchset 5731535 (p5731535_10203_WINNT.zip You can download the patch from Oracle Metalink) Note
The installation process was tested on an English Windows 2003 Server installation.
2. Select Custom as the type of installation you want to perform, and then click Next. 3. Type a name and location for a new Oracle Home. You can use the Browse button to find the applicable location on your machine. When you have entered the necessary information, click Next to continue.
Warning
When defining a new Oracle-Home, do not use any old values. Use the Ora10g and path name provided to simplify the installation process and eliminate the need to edit SQL scripts, which are available as samples on the SmartPlant Materials CD in the following folder: \program files\Intergraph\MARIAN6\samples. Name: Path: Ora10g %drive%\oracle\Ora10g
(If you choose a different drive letter or path for your installation, you must edit the SQL scripts provided on the SmartPlant Materials CD accordingly.)
- Select Oracle Database 10g 10.2.0.1.0. - Select Oracle Database 10g 10.2.0.1.0. - Select Oracle Enterprise Manager Console DB 10.2.0.1.0. - Disable Enterprise Edition Options 10.2.0.1.0. - Select Oracle Net Services 10.2.0.1.0. - Select Oracle Net Listener 10.2.0.1.0. - Select Oracle Connection Manager 10.2.0.1.0.
Part 3: Oracle Database Server Installation - Select Oracle Call Interface (OCI) 10.2.0.1.0. - Deselect Oracle Programmer 10.2.0.1.0. - Select Oracle XML Development Kit 10.2.0.1.0. Scroll down for further options.
Oracle Services for Microsoft Transaction Server Oracle Counters for Windows Performance Monitor
Click Next when all Components have been chosen, as described before. Select the components as shown in the illustrations for installation. Click Next to open the next window.
Click Next.
4. Select No when asked if you want to create a new database, and then click Next to continue. Important
Click No when asked to create a database. You can create the SmartPlant Materials database by using sample scripts provided to you on the SmartPlant Materials CD.
Part 3: Oracle Database Server Installation Note Creating a database automatically is not recommended at this time. You will do this task later in the SmartPlant Materials installation because of some special database settings that are necessary for proper installation. If you are familiar with this task, or you are an OracleDBA, you can create the database using your own scripts as you did in former SmartPlant Materials installations (review sample init.ora in this case).
Write down the http-links shown above for later usage. You can also look in the file %ORACLE%\ora10g\install\portlist.ini to check the assigned ports later. 5. Click Exit to leave the Oracle installer.
Continue with the installation of the Patchset 10.2.0.2 before creating the database.
Before you start this procedure, stop all ORACLE-Services under Control Panel > Services.
Stop the Oracleora10gSQL*Plus service in order to proceed with the patch installation.
Click Next.
Warning
Define your existing Oracle-Home. Do not use any other values that may be displayed here. Name: Ora10g Path: %drive%\oracle\Ora10g
Click Install.
Click Exit.
Click Yes to exit the installer. The Oracle database software installation is finished.
Click Next.
Specify your Oracle 10g database home. Do not use the default displayed values. Click Next.
Click Install.
Click Yes.
Installing the Oracle 10g Database One Off Patchset 10.2.0.3 (Patch # p5731535)
Patch Installation Instructions
Follow these steps: Cleanly shut down all processes running from the ORACLE_HOME. Go to the directory where you downloaded the patch: > cd 5731535 Set the ORACLE_HOME clear environment variable to the correct Oracle home that needs to be patched.
> set ORACLE_HOME=<Oracle Home Path>
Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:
> opatch apply
Inspect the opatch-<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors. This marks the end of the Oracle database software installation.
The Oracle Software 10g 10.2.0.2.0 must be installed as described when performing the next steps. A database was not created when using the Oracle Installation Wizard; it will be done using the manual steps as described below. Intergraph highly recommends the usage of the prepared sample scripts and all initialization parameters used in the provided init.ora file (%MARIAN%\samples\oradata\MAR62\pfile\init.ora). Changes to the default recommended settings should not be done without consultation of the SmartPlant Materials Service Center as changes to the settings may harm the SmartPlant Materials functionality. Tips Create the folder structure by copying files from the SmartPlant Materials CD to your database installation. On the CD, navigate to \program files\Intergraph\MARIAN2007\samples\oradata, and copy the files. Remove write protection after the files are copied. To simplify this task, work at the top level of the folder structure (for example, D:\). The oradata folder contains the standard folder structure for the SmartPlant Materials database files. By using a standard folder structure, supporting the SmartPlant Materials installation will be much easier, and you can manipulate the database more easily.
All files used to create the database will be stored in the scripts folder of this tree. Note
The <MAR62> that is used in our sample scripts represents the Oracle SID and can be anything that you need. You should change this to a value to fit your needs (for example, MAR62). We recommend that it have no more than six characters. For consistencys sake, rename the MAR62 folder to match the sid-name. Throughout the following steps, <MAR62> represents the Oracle SID name.
Some initialization parameters are very important and should not be changed in the SmartPlant Materials database instance. compatible=10.2.0.2.0 utl_file_dir=C:\oradata\MAR62\utl hash_join_enabled=TRUE java_pool_size=50M shared_pool_size=130M max_enabled_roles=80 (minimum) O7_DICTIONARY_ACCESSIBILITY=TRUE dispatchers="(PROTOCOL=TCP) (SERVICE=dbnameXDB)" open_cursors=1200 Job_queue_processes=10 recyclebin=OFF
Part 4: SmartPlant Materials Database Installation and Configuration The parameter file that is placed in %\oradata\MAR62\pfile\ holds the database settings for the database creation. Note that using the sample scripts will create an spfile in folder \%ORACLE-Home%\database from the specified parameter file. This spfile stores the database parameters, which will be used by the startup command, if no other parameter file is specified. Now you have modified the following three files and completed all preparations to create the new instance: File create10g_MAR62.ba t Folder %\oradata\MAR62\script s check check check
execute create10g_MAR62.bat
Log files of the database creation process are written to %\oradata\MAR62\logs. First of all, the new service will be created.
Part 4: SmartPlant Materials Database Installation and Configuration Then, the database files are created in the c:\oradata\mar62\dbf folder.
Depending on the performance of your server, this will take some time (maybe an hour or even more).
Click Next.
Click Next.
Click Next.
Click Finish. The Net Configuration Assistant window will terminate now.
Part 4: SmartPlant Materials Database Installation and Configuration Open the Services tab, and click Refresh. Check to see if the Oracleora10gTNSListener has been created and is started.
Now you can enter SQL*Plus to connect to your new database. You can perform this test as user SYS.
Part 4: SmartPlant Materials Database Installation and Configuration The following graphic shows an example of an unsuccessful tnsping followed by a successful tnsping. To check if your configuration has succeeded, please open a command window and enter the following command: C:\tnsping MAR62
Skip this section if you have used the database creation script from the SmartPlant Materials CD (Create10g_MAR62.sql).
If you have used the recommended Create10g_MAR62.sql and initmar62.ora, go to the Applying the SmartPlant Materials DTD Files section. Open SQL*Plus as SYS and perform the following steps: 1) Define the XML directory Create or replace directory XMLDIR AS 'C:\oradata\MAR62\utl\'; Example: SQL> connect sys/password@database Connected. SQL> create or replace directory XMLDIR AS 'D:\oradata\utl\'; Directory created. 2) Apply grant on XMLDIR to public grant read,write on directory XMLDIR to public with grant option;
Part 4: SmartPlant Materials Database Installation and Configuration Example: SQL> grant read,write on directory XMLDIR to public with grant option; Grant succeeded. 3) Display the defined Oracle directories select * from ALL_DIRECTORIES; Example: SQL> select * from ALL_DIRECTORIES; OWNER DIRECTORY_NAME DIRECTORY_PATH ----------------------------------------------------------------------------------------SYS XMLDIR C:\oradata\MAR62\utl To activate the FTP port inside the database, do the following in SQLPLUS as SYS: 4) Check to see if a dispatcher is configured in the pfile/spfile. For example: dispatchers='(PROTOCOL=TCP) (SERVICE=MAR62XDB)' Restart the database and listener to enable Oracle XML DB protocol access in case you had to add the dispatcher. 5) Check if the XDB option is already installed correctly: select comp_name, status, version from DBA_REGISTRY where comp_id='XDB'; Example 1: SQL> connect sys/manager1@msc62 Connected. SQL> select comp_name, status, version from DBA_REGISTRY where comp_id='XDB'; no rows selected Example 2: SQL> select comp_name, status, version from DBA_REGISTRY where comp_id='XDB'; COMP_NAME STATUS VERSION ----------- ----------------------------------------------------Oracle XML Database VALID 10.2.0.2.0
Part 4: SmartPlant Materials Database Installation and Configuration 6) Install CATQM If the output is no rows selected, you will have to proceed as follows: Log on to SQL*Plus as user SYS and execute catqm.sql as described below. The catqm.sql file creates the tables and views needed to run the XDB system. Run this script like this: Example: SQL> show user USER is "SYS" SQL> @catqm.sql password xdb temp You can determine whether or not Oracle XML DB is already installed. If it is installed, then the following information is true:
User XDB exists. To check: SELECT * FROM ALL_USERS where username like 'X%';
For a manual installation or un-installation of Oracle XML DB, see Chapter 28, "Administering Oracle XML DB". (http://downloaduk.oracle.com/docs/cd/B19306_01/appdev.102/b14259/appaman.htm#g645751) Unlock the Database user XDB, and change the password. alter user xdb account unlock; alter user xdb identified by xdb;
Check to see if the XDB option is installed correctly: select comp_name, status, version from DBA_REGISTRY where comp_id='XDB'; 7) Configuring the current FTP port select extractvalue(dbms_xdb.cfg_get(), '/xdbconfig/sysconfig/protocolconfig/ftpconfig/ftp-port') "FTP-Port" from dual;
If the returned port number is 0, you can set it to port 21 as follows: You can copy these instructions line by line as shown in the hardcopy below. DECLARE newconfig XMLType; BEGIN SELECT updateXML(DBMS_XDB.cfg_get(), '/xdbconfig/sysconfig/protocolconfig/ftpconfig/ftp-port/text()',21) INTO newconfig FROM DUAL; DBMS_XDB.cfg_update(newconfig); END; / COMMIT;
Part 4: SmartPlant Materials Database Installation and Configuration Note This is the end of the installation scripts section.
2. Start a command window and go to the directory where the SmartPlant Materials dtd files are located.
Part 4: SmartPlant Materials Database Installation and Configuration The graphic below shows the commands and responses explained in this step. Connect via ftp to the database server: DOS>ftp <your-db-server> Log on as user XDB with the oracle password for xdb
Enter the following commands: bin <ENTER> mput *.dtd <ENTER> Answer y (Yes) to the questions shown in the example graphic. To test the result type: dir <ENTER> This shows you the uploaded dtd files.
Type quit or bye to exit the ftp program. 3. Disable the ftp server, and execute the following in SQLPLUS as SYS: DECLARE newconfig XMLType; BEGIN SELECT updateXML( DBMS_XDB.cfg_get(), '/xdbconfig/sysconfig/protocolconfig/ftpconfig/ftp-port/text()',0) INTO newconfig FROM DUAL; DBMS_XDB.cfg_update(newconfig); END; / COMMIT; You can use the prepared scripts ftp_disable and ftp_enable to manage your active ftp (%\oradata\MAR62\scripts\useful\specials).
Part 4: SmartPlant Materials Database Installation and Configuration Use the following SQL*Plus statement to see if your DTD files were uploaded to the database (please connect as SYS): SELECT a.path FROM path_view a where path like '%.dtd'; As a result, you will get a list of available datatype definitions.
SmartPlant Materials schema M_SYS will be created with an initial password of manager. Press Enter.
Press Enter.
Press any key to begin importing data. Continue pressing any key on the following screens until all data is imported.
Leave the SQL*Plus session by typing exit, and check the log files for errors during installation. The files are located in the installation folder and in the UTL-Directory (\\ORADATA\MAR62\utl). It is a best practice to keep these log files for later analysis. Therefore, we recommend that you not use the same migration directory twice in order to not overwrite existing log files by newer migrations on different databases. This installation step is complete. Next, you can install the licenses for the software. For information about licensing, please refer to the SmartPlant Materials License Handling Guide, available from the Online Reference Library.
For successful migration, you need the Oracle 10.2.0.2.0 import and export tool programs, and the loadjava utility installed on your client PC (or on the machine you use to perform the migration). Additionally, the Oracle Java Virtual Machine (JServer JVM) needs to be correctly installed on the database server. If you currently have installed a version other than MARIAN 6.1 SP19, you must first migrate to MARIAN 6.1 SP19 or higher before you can migrate to SmartPlant Materials 6.2.x. These migration procedures are not part of the SmartPlant Materials 6.2.x CD-ROM. Contact the SmartPlant Materials Service Center to get the related migration procedures.
Part 6: SmartPlant Materials Database Migration from 6.1 7. Perform a full cold backup, using redundant backup media (that is, do not use the same tape or hard disk that will contain the export dump file created during the migration). Make sure to include all data files, all control file mirrors, all archived and online redo log files, and the instance initialization files. 8. Store all backup media in a safe place. 9. Perform the client-tools exp and imp to test both tools, because the SmartPlant Materials installation wizard will use them.
The dump source must be at least MARIAN 6.1 SP19. 2. Run the following import command: imp system/your_password@sid file=dump_file.dmp log=log_file.log full=y ignore=y commit=y buffer=60000000 3. Invoke SQL+, connect as M_SYS, and install the following packages: 00_coresys62.sql 1st_grmsys62.sql 4. As SYS in SQL+, run c:\your_Oracle_Home\rdbms\admin\utlrp.sql. 5. Now, run the following scripts: 2nd_re_comp62.sql, 3rd_grmar62.sql, and 4th_grmlogin62.sql. 6. As M_SYS in SQL+, run 2nd_re_comp62.sql. Execute this a few times until the amount of invalid objects stops decreasing. Check the spool file invalid_objects.log for errors and db_info.log for your database settings. 7. As M_SYS in SQL+, run 3rd_grmar62.sql, 4th_grmlogin62.sql, and 5th_analyze.sql.
1. The database server must have Oracle 10.2.0.2.0 with Patch #4547817 installed. 2. You must have access to the database Sys account. 3. The database COMPATIBLE parameter must be set to 10.2.0 or later. 4. A MARIAN 6.1 Service Pack 19 installation must be present in this database. 5. The database shared pool size must be 50 MB or more. 6. The database Java pool size must be 20 MB or more. 7. The instance initialization parameter O7_DICTIONARY_ACCESSIBILITY must be set to TRUE. 8. The instance initialization parameter JOB_QUEUE_PROCESSES must be set to 0 during the migration; that is, there must not be any background jobs currently active. 9. The instance initialization parameter DML_LOCKS must be 300 or greater. 10. The instance initialization parameter OPEN_CURSORS must be 1000 or greater. 11. The SmartPlant Materials tablespaces MARIAN, M_INDEX, M_TEMP, and USERS must have sufficient free space: MARIAN: 500 MB free M_INDEX: 2400 MB free M_TEMP: 1000 MB free USERS: 50 MB free. 12. The SmartPlant Materials tablespaces must be online. 13. There must be 300 MB free space in the SYSTEM tablespace.
Part 6: SmartPlant Materials Database Migration from 6.1 14. The tablespace where this rollback segment is stored must have at least 1.4 * size of largest table segment MB free, but not less than 1200 MB. This tablespace must be created with the parameter SEGMENT SPACE MANAGEMENT MANUAL. (For further information about rollback tablespaces, refer to the ORACLE documentation). You can find sample scripts for database creation in the <MARIANHOME>\samples\oradata\MAR62\scripts\useful\migration\ folder. For successful migration, you furthermore need the Oracle 10.2.0.2.0 import and export tool programs, and the loadjava utility installed on your client PC (or on the machine you use to perform the migration). Additionally, the Oracle Java Virtual Machine (JServer JVM) needs to be correctly installed on the database server. 15. The SmartPlant Materials application schema user M_SYS must not be currently connected to the database. 16. No database logon/logoff triggers (other than the RDBMS standard ones) that could possibly interfere with the SmartPlant Materials installation must exist in the database.
It is not possible to run SmartPlant Materials 6.2 with prior ORACLE database server releases. Therefore, this is a necessary step to fulfill the migration prerequisites.
There are two migration paths: 1) Using the ORACLE Database Upgrade Assistant. 2) Importing a dump file into a newly created ORACLE 10g database. Choose the best migration path for your needs. If you decide to use the ORACLE Upgrade Assistant, you will have to install ORACLE 10g software on the server where the database to migrate resides. For more information, refer to the ORACLE documentation. If you decide to use the second migration path, the procedure can be described as follows: a. Create a dump file from your MARIAN 6.1 Service Pack 19 database. b. Transfer the dump file to your database server with ORACLE 10g installed. c. Create a database for SmartPlant Materials 6.2. Please refer to the Creating SmartPlant Materials Basic Database section for an example of how to create a database. You can find sample scripts and an init.ora parameter file to create a database for migration purposes in the following folder: <MARIAN-HOME>\samples\oradata\MAR62\scripts\useful\migration\ Replace the current files create10g_MAR62.bat, Create10g_MAR62.sql in the folder <MARIAN-HOME>\samples\oradata\MAR6\scripts\ and the parameter file <MARIAN-HOME>\samples\oradata\MAR62\pfile\initMar62.ora with the corresponding files from the migration folder. Customize the data file locations and dimensions in the scripts, if you need to. d. Start the import into the new database. After you have managed to migrate your database to ORACLE 10g Release 2 by one or the other migration path, you should backup the database before starting the migration of SmartPlant Materials.
Start the migration script by entering @ mig_marian6200.sql on the SQL*Plus command line. Follow the instructions on the screen.
Enter the database connect string, and press Enter. Enter the SYS password, and press Enter. Enter the M_SYS password, and press Enter. Enter the DISCO password, and press Enter.
Press Enter to start the migration process. During this process, an import window will open and perform some database imports automatically. Please do not close these windows. The migration will continue without any action to be taken from the users side.
After all imports have terminated, please check the log files for errors, and press Enter to continue.
When the migration is complete, check all log files for possible Oracle errors. The log files are located in the installation_logs and import folders. Logs will have the following extensions: *.log, *.lst, and *.tmp. You can safely ignore all errors that refer to index creation with a specified indexed column combination that is already indexed. It is a best practice to keep these log files for later analysis. Do not use the same folder for more than one migration but copy it for each separate database migration. To allow Java access to local files, open a SQL*Plus session, and connect as SYS. Enter the following command: EXEC dbms_java.grant_permission(M_SYS,java.io.FilePermission,<your PDB_REPORT_DEST_DB directory>,read,write,delete); Example: EXEC dbms_java.grant_permission('M_SYS','java.io.FilePermission','C:\oradata\mar62\utl' ,'read,write, delete'); PL/SQL procedure successfully completed. The path must match the PDB_REPORT_DEST_DB entered on the SmartPlant Materials screen A.60.04 DBA Settings. If you do not know this setting, you can perform this step at any time later on.
Customer CIPs are saved to the installation_logs folder during migration. You may have to modify and reapply these procedures to the new SmartPlant Materials release. The migration of your database is now finished and you can log on to your database.
SmartPlant Materials has been tested using the ORACLE cost-based optimizer mode.
Display the SmartPlant Materials web page. At the Logon screen, enter your username, password, and a database alias. Typically, you use LOGIN with the password LOGIN that was created on installation. After authentication, you can select a project / product group. The default (preinstalled) project is named M_PROJECT. Click OK.
Skip this section if you have already created a reports server using the SmartPlant Materials Application Server Wizard.
Configuring Reports Server with the Oracle Process Manager and Notification Server and Oracle Enterprise Manager 10g The best way to start, shut down, monitor, and manage Reports Server is through the Oracle Process Manager and Notification Server (OPMN) and Oracle Enterprise Manager 10g. OPMN provides a centralized mechanism for initializing, maintaining, and shutting down your Oracle Application Server components, including Reports Server. Oracle Enterprise Manager 10g, included with Oracle Application Server, provides managing and monitoring services to OracleAS Reports Services. You can conveniently monitor your Reports Servers through Oracle Enterprise Manager 10g and, if the process fails for any reason, OPMN restarts Reports Server for you automatically. During installation of Oracle Application Server, Reports Servers are automatically configured in OPMN and registered with Oracle Enterprise Manager 10g. If you add any Reports Servers after installing Oracle Application Server, you should register the new server(s) in two places:
The Oracle Process Manager and Notification Server's opmn.xml file. The Oracle Enterprise Manager 10g's targets.xml file.
To register a new Reports Server in both opmn.xml and targets.xml, run the following command line: On Windows: ORACLE_HOME\bin\addNewServerTarget.bat reports_server_name After running this command line, reload the OPMN configuration file for the change to take effect (for example, opmnctl reload). Run Reports in Parallel (Optional) Per default, the reports server allows only one report engine to be used by the reports server. This means that, if one report is running, the next report will be put in the queue and processed sequentially. We recommend to allow multiple users to run their reports in parallel. Change the maxEngine parameter from 1 to the "number of licenses" or the "number of SmartPlant Materials Installation and Migration Guide 141
Part 8: Logging On To Your SmartPlant Materials Database potential report users" in the <repservername>.conf file in <ORACLE_iAS_HOME>\reports\conf. Note that the maxEngine parameter may occur more than once, so simply change each occurrence.
Edit both files: <reports-server-name>.conf and rep_<servername_oracledir>.conf a) security b) uncomment the following lines as shown below in both conf-files:
Part 8: Logging On To Your SmartPlant Materials Database Refer to other examples in this file for the syntax to comment out the tags. In the example above, the html comment syntax is used: <!--commented text-->. Stop all services in your iAS-Home after this step.
If the default SmartPlant Materials installation path (or any other path containing a space) is used, the reports server service will start and immediately stop. Uninstall SmartPlant Materials, and then re-install it using an installation path that does not contain any spaces. Note that you have to comment the security and destination tag (as described above for the in-process report server that comes with the installation).
You can preserve the sample SNOOP-entries in the file. Copy the mar_jserv folder (directory and the contents) from <MARIAN_HOME>\java\iAS to your appropriate application folder. If you use the default OC4J application, it is <10giAS HOME>\j2ee\home\default-web-app\WEBINF\classes. Check HTTP-Server Listen to Port 80 (Optional)
Click Ports.
or
default.icons.iconpath=http://dor-mds-as06/marian_webentry
Create Path-Mappings
The SmartPlant Materials download functionality requires path mapping for virtual paths to physical paths. These mappings are carried out in the <ORACLE_iAS_HOME>\forms\server\forms.conf file. You can add mappings any time you need one. The mapping for the marian_webentry and marian_webhelpvirtual paths is required. The other mappings depend on your usage of download directories. Here is an example beginning of forms.conf:
# MARIAN Aliases Alias /marian_webentry/ "C:\<MARIAN_HOME>\web_entry/" Alias /marian_webhelp/ "C:\<MARIAN_HOME>\web_help/" Alias /marian_download/ "C:\<MARIAN_HOME>\download/"
# Virtual path mapping for Forms Java jar and class files (codebase) AliasMatch ^/forms/java/(..*) "C:\ORACLE\iAS_HOME/forms/java/$1" ...
Part 8: Logging On To Your SmartPlant Materials Database Here are two examples for SmartPlant Materials-specific configs in formsweb.cfg:
[mar62] pageTitle=MARIAN 6.2.1 - JInitiator HTMLbeforeForm=<CENTER><IMG SRC = "/marian_webentry/Marian_splash.jpg" width=500 height=300 ALT="INTERGRAPH MARIAN 2007 (c)2006"> <BR> Please be patient while MARIAN loads. <BR> Note: Closing this Browser window will end your MARIAN session.<BR> </CENTER> form=logon.fmx userid=m_login/m_login@mar62 separateFrame=True lookandfeel=Generic width=1024 height=768 workingDirectory=C:\MARIAN\fmx splashScreen=no
After you have made these entries, you can start SmartPlant Materials in your internet browser, using the following link: http://<your_hostmane>/forms/frmservlet?config=mar62 In this case, FormsServlet will read the marian_jinit-configuration and create an appropriate html-page with the applet-call. As a result, SmartPlant Materials will be started with JInitiator (and you will be prompted to install JInitiator if not yet done). If this doesnt work and the software returns an OR-000 error (a time out error), turn off the Windows Firewall in Windows XP SP2. In the <marian_home>\web_entry directory is a file named MARIAN6i.lnk. Edit the properties of this file to match your hostname accordingly.
Check your entry as you need to have SmartPlant Materials running to accomplish this task.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings Users can place document files on the client, with only the file reference stored in SmartPlant Materials. The document can be opened with an application such as Acrobat Reader or Word with a button implemented on a SmartPlant Materials screen.
Web Environment
Web environment has (in the most simple configuration) inserted a new instance between database server and client PC. While the database server remains, there is now an application server where Oracle Forms is running the application that ran on the client PC in client/server topology. The user sits at a third computer with only a browser, which is Java-enabled. This is the reason why this topology is sometimes called three-tier technology. Considering the transfer of files, files coming to and from the database server will be there independent of the architecture, while files that were coming to and from the client PC in C/S mode, are now coming to and from the application server in web mode. There is another step needed for exchanging files between the application server and browser client.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings Other files, placed on the client, are graphics that can be imported and stored within the database with a click of a button on the associated screens. This is done with Forms functionality.
The path information you typically append to the part of the URL is a virtual path, which means that it doesn't have to be physically represented on the file system. Here is the URL from above with a virtual subfolder and a file name:
http://www.intergraph.com/ppo/marian/MARIAN-us.pdf
Maintain the appropriate dba setting (A.60.04) or project defaults (A.20.11/12/13), so that SmartPlant Materials can supply the path information to the second browser window mentioned in the Overview in this section. Maintain a mapping on the application server between the physical folder and the virtual path contained in the URL.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings If you use the Oracle Internet Application Server (10g iAS) Enterprise Edition, you can define the mapping in the forms90.conf file of your Oracle 806 home. You could, for example, find it on D:\oracle\%\conf\forms90.conf. The mapping could also be made in the httpd.conf file that is the main configuration file. However, the forms server settings are also in this file and to keep the overview, it is better to do all settings in the same file. Here is a line to declare a valid mapping name (alias) for documents (for the example above):
alias /ppo/marian/ "c:\web_docs\ppo\marian/"
Note that the virtual path and the physical path end with a slash in the configuration file, independently of working under NT or UNIX platform.
The user can define the path, but it must exist on the application server. The path cannot have an ending backslash. After creating the file in the destination folder, SmartPlant Materials opens a new browser window displaying the result. Specify the DBA setting for BOM_DOWNLOAD_URL on A.60.04 to enable the web server to find the OMI file on the application server. This is a valid entry for the setting:
your_web_server/bom_downloads
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. The forms90.conf file on the application server must have a line such as this:
alias /bom_downloads/ "c:\marian\bom_downloads/"
The right-hand entry must match the BOM_DOWNLOAD_DEST, except that it has a slash at the end. The left- hand entry must match the BOM_DOWNLOAD_URL, but the server name is omitted and it has an ending slash. The PLUS_EXECUTABLE DBA setting has to be set to make the download happen. The b200144.sql script can be placed in a folder other than OMI_DOWNLOAD_DEST. The SQLPATH variable in the registry of the application server must point to it (for example, %\MARIAN61\sql\omi\utl). This must also occur in the other files (B40R01.sql, B200144B.sql, example.dat,
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings omi52.ctl, omi52.par, omi52onl.ctl, piping_g.ctl). Please also copy these files to the UTL-file directory on the database server.
The user can define the path, but it must exist on the application server. The path must have an ending backslash. After creating the file in the destination folder, SmartPlant Materials opens a new browser window displaying the result. Specify the DBA setting or OII_DOWNLOAD_URL on A.60.04 f to enable the web server to find the OMI file on the application server. This is a valid entry for the setting:
your_web_server/marian_oii_down
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_oii_down/ "c:\mar\ident_downloads/"
The right-hand entry must match the OII_DOWNLOAD_DEST, except that the backslash is replaced by a slash. The left-hand entry must match the OII_DOWNLOAD_URL, but the server name is omitted and an ending slash is added. Note that the DBA setting PLUS_EXECUTABLE has to be set to make the download happen. The script oie_*.sql has to be placed in the folder specified in OII_DOWNLOAD_DEST.
The path can be chosen deliberately, but it must exist on the application server. Append an ending backslash here.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings Then, you are prompted to download the file. Confirming, you get a new browser window that supplies the file. Specify the DBA setting for GRAPHIC_DOWNLOAD_URL on A.60.04 to enable the web server to find the image file on the application server. This is a valid entry for the setting:
your_web_server/marian_images
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there must be a line looking like this:
alias /marian_images/ "c:\marian\image_downloads/"
The right-hand entry must match the GRAPHIC_DOWNLOAD_DEST except that the backslash is replaced by a slash. The left-hand entry must match the GRAPHIC_DOWNLOAD_URL, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /qs_doc/ "d:\marian6\qs_supplier_docs/"
The right-hand entry must represent a valid folder on the application server. Most likely, it is the one defined in the project default ZP_QSD_UPP. The left-hand entry must match the QS_DOC_DOWNLOAD_URL, but the server name is omitted and an ending slash is added.
Documents (D.10.11)
The Open button opens a new browser window displaying the actual document. Specify the project default ZI_WEB_DOC on A.20.11/12/13. The value will look like this:
your_web_server/marian_docs
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_docs/ "c:\marian\docs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_DOC, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_docs/ "c:\marian\docs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_DOC, but the server name is omitted and an ending slash is added.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line like this:
alias /marian_docs/ "c:\marian\docs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_DOC, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_docs/ "c:\marian\docs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_TT, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_docs/ "c:\marian\docs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_TT, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_cecs/ "c:\marian\cecs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_CEC, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_tecs/ "c:\marian\tecs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_TEC, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_itcs/ "c:\marian\itcs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_ITC, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_coas/ "c:\marian\coa_uplds/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_COA, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_cecs/ "c:\marian\cecs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_CEC, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_cecs/ "c:\marian\cecs/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_CEC, but the server name is omitted and an ending slash is added.
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_coas/ "c:\marian\coa_uplds/"
The right-hand entry must be a local folder on the application server and must be concluded by a slash. The left-hand entry must match the ZI_WEB_COA, but the server name is omitted and an ending slash is added.
The path can be chosen deliberately, but it must exist on the application server. Append an ending backslash here. After the file is created, you are prompted if you want to download the file. Confirming, you get a new browser window, which supplies the file. Specify the DBA setting for PDMS_DOWNLOAD_URL on A.60.04 The value will look like this:
your_web_server/pdms
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /pdms/ "d:\marian6\pdms_files/"
The right-hand entry must match the PDMS_DOWNLOAD_DEST except that the backslash is replaced by a slash. The left-hand entry must match the PDMS_DOWNLOAD_URL, but the server name is omitted and an ending slash is added.
The path can be chosen deliberately, but it must exist on the application server. Do not append an ending backslash here. After the file is created, you are prompted if you want to download the file. Confirming, you get a new browser window, which supplies the file. Specify the DBA setting for PDS_DOWNLOAD_URL on A.60.04 The value will look like this:
your_web_server/pds
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /pds/ "d:\marian6\pds_files/"
The right-hand entry must match the PDS_DOWNLOAD_DEST except that a slash is appended. The left-hand entry must match the PDS_DOWNLOAD_URL, but the server name is omitted and an ending slash is added.
The path can be chosen deliberately, but it must exist on the application server. Do not append an ending backslash here. After the file is created, you are prompted if you want to download the file. Confirming, you get a new browser window, which supplies the file. Specify the DBA setting for PDS_DOWNLOAD_URL on A.60.04.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings The value will look like this:
your_web_server/pds
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /pds/ "d:\marian6\pds_files/"
The right-hand entry must match the PDS_DOWNLOAD_DEST except that a slash is appended. The left-hand entry must match the PDS_DOWNLOAD_URL, but the server name is omitted and an ending slash is added.
The path can be chosen deliberately, but it must exist on the application server. Do not append an ending backslash here. After the file is created, you are prompted if you want to download the file. Confirming, you get a new browser window, which supplies the file. Specify the DBA setting for PDS_DOWNLOAD_URL on A.60.04. The value will look like this:
your_web_server/pds
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /pds/ "d:\marian6\pds_files/"
The right-hand entry must match the PDS_DOWNLOAD_DEST except that a slash is appended. The left-hand entry must match the PDS_DOWNLOAD_URL, but the server name is omitted and an ending slash is added.
The path can be chosen deliberately, but it must exist on the application server. Do not append an ending backslash here. After the file is created, you are prompted to download the file. Confirming, you get a new browser window, which supplies the file. Specify the DBA setting for PDS_DOWNLOAD_URL on A.60.04.
your_web_server/pds
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /pds/ "d:\marian6\pds_files/"
The right-hand entry must match the PDS_DOWNLOAD_DEST except that a slash is appended. The left-hand entry must match the PDS_DOWNLOAD_URL, but the server name is omitted and an ending slash is added.
The path can be chosen deliberately, but it must exist on the application server. Append an ending backslash here. Click OK to create the file. You are prompted to download the file. Confirm and you get a new browser window that displays the file. Specify the DBA setting for PRINT_TO_FILE_URL on A.60.04. The value will look like this:
your_web_server/ptf
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /ptf/ "d:\marian6\print_to_file/"
The right-hand entry must match the PRINT_TO_FILE_DEST except that the backslash is replaced by a slash. The left-hand entry must match the PRINT_TO_FILE_URL, but the server name is omitted and an ending slash is added.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings Refer to the Downloading (Receiving) Files from SmartPlant Materials 2007 (6.2) section for background information on how a file is read on the application server. The other headings in this section explain modules. Also, see the following sections about modules that explain what you must do in special cases.
Procedure
1. To make the web server find the servlets in its repository, set the DBA setting called SERVLET_PATH on A.60.04. If you install Oracle 10g iAS as described in the installation guide, the value will be this:
your_server_name/j2ee/servlet
The first part is your real server name. It could also be a domain name such as marian.epc.com. The second part is a constant string that you simply append to your server name. It is a virtual path to the servlet classes, within the repository of the web server. Don't use an ending slash. 2. To tell the servlet where the document shall be stored, set the DBA setting for destination path information on A.60.04 . The setting name depends on the SmartPlant Materials screen you are on. Refer to Online Help to find out the name. This is an example for the value:
d:\marian552\uploaded_tags_and_terms\
You can use any path that exists on the application server. Directories that dont exist are not created during upload.
The name of your web server is followed by the string /j2ee/servlet. Don't append an ending slash. When the user gets the file from his file system, he can click the Submit button to send the file to the server. The destination path on the application server, where the file is stored, must be specified in the DBA setting named BOM_UPLOAD_DEST on A.60.04. This is a valid format for the value:
c:\mar_5\bom_uploads\
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings When the upload is finished, the user can close the additional browser window. The folder and file name of the uploaded file are automatically stored in the appropriate fields of B.40.01. The file name is concatenated with the string OMIJID and the ID of the actual OMI job.
Online Mode
The folder stored in BOM_UPLOAD_DEST has to contain the OMI- control (*.ctl) and .parameter (*.par) file that are needed by the SQL*Loader. After entering the remaining parameters on B.40.01, the user can click the Start Online button to run the job.
Batch Mode
There is a special solution when the user wants to start the import in batch mode. Normally, a user uses FTP or another program to send a file to the database server, where it is needed for batch processing. However, in this case, the database downloads the file from the application server to the file system of the database server. To activate this mode, configure the following: 1. The DBA setting for BOM_UPLOAD_URL on A.60.04 enables the web server to find the OMI file on the application server. This is a valid entry for the setting:
your_web_server/bom_uploads
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /bom_uploads/ "c:\mar_5\bom_uploads/"
The right-hand entry must match the DBA setting BOM_UPLOAD_DEST, except that there is a slash instead of a backslash at the end. The left-hand entry must match the BOM_UPLOAD_URL, but the server name is omitted and an ending slash is added. 2. The DBA setting for BOM_IMPORT_GET_FILE on A.60.04 must be Y. 3. The DBA setting for BOM_IMPORT_PATH on A.60.04 is used to find the import file on the database server, independent of a web or client/server environment. Note that the folder stored in BOM_IMPORT_PATH has to contain the OMI- control (*.ctl) and .parameter (*.par) files that are needed by the SQL*Loader. 4. Click the Start Batch button to check to see if a file with this name already exists, and download the one on the application server to the database server.
The name of your web server is followed by the string /j2ee/servlet. Don't append an ending slash. When the user picks up the file from his file system, he can click the Submit button to send the file to the server. The destination path on the application server, where the file is stored, must be specified in the DBA setting called OII_UPLOAD_DEST on A.60.04. This is a valid format for the value (with trailing backslash):
c:\mar_5\oii_uploads\
When the upload is finished, the user can close the additional browser window. The folder and file name of the uploaded file are automatically stored in the appropriate fields of B.40.01. The file name is concatenated with the string 'OIJID' and the ID of the actual OII job. The folder stored in OII_UPLOAD_DEST has to contain the OII- control (*.ctl) and parameter (*.par) files that are needed by the SQL*Loader. After entering the remaining parameters on B.40.01, click the Start Online button to run the job. Batch processing is the same as in client/server.
The name of your web server is followed by the string /j2ee/servlet. Don't append an ending slash.
Part 9: SmartPlant Materials 2007 (6.2) Module-Specific Settings When the user picks up the file from his file system, he can click the Submit button to send the file to the server. The destination path on the application server, where the file is stored, must be specified in the DBA setting called GRAPHIC_UPLOAD_DEST on A.60.04. This is a valid format for the value (with trailing backslash):
c:\mar_5\image_uploads\
When the upload is finished, the user can close the additional browser window. The folder and file name of the uploaded file are automatically stored in the appropriate fields of the screen. Concatenating the ID of the actual graphic symbol and the following strings creates the file name: 'CS' in G.10.01 'PS' in G.10.02 'CC' in G.10.03
The name of your web server is followed by the string /j2ee/servlet. Don't append an ending slash. When the user picks up the file from his file system, he can click the Submit button to send the file to the server. The destination path on the application server, where the file is stored, must be specified in the DBA setting called PDMS_UPLOAD_DEST on A.60.04. This is a valid format for the value (without trailing backslash):
c:\mar_5\pdms_uploads
When the upload is finished, the user can close the additional browser window. The folder and file name of the uploaded file are automatically stored in the appropriate fields of PDMS 20.02. The file name is concatenated with the string 'PCC' and the ID of the actual PDMS job. Click Load File to run the job.
The name of your web server is followed by the string /j2ee/servlet. Don't append an ending slash. When the user picks up the file from his file system, he can click the Submit button to send the file to the server. The destination path on the application server, where the file is stored, must be specified in the DBA setting called OPI_UPLOAD_DEST on A.60.04. This is a valid format for the value (without trailing backslash):
c:\mar_5\opi_uploads
The folder and file name of the uploaded file are automatically stored in the appropriate fields. The file name is concatenated with the string 'OPIJID' and the ID of the actual OPI job. When the upload to the application server is finished, the user can close the additional browser window. He is prompted that the file is now transferred to the database server. Specify the DBA setting for OPI_UPLOAD_URL on A.60.04 to enable the web server to find the OPI file on the application server. This is a valid entry for the setting:
your_web_server/marian_opi_up
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line that looks like this:
alias /marian_opi_up/ "c:\mar_5\opi_uploads/"
The right-hand entry must match the OPI_UPLOAD_DEST except that the trailing backslash is replaced by a slash. The left-hand entry must match the OPI_UPLOAD_URL, but the server name is omitted and an ending slash is added. Make sure that you have set the DBA setting called OPI_IMPORT_PATH on A.60.04 to point to a path on the database server. This setting is always needed whether or not you perform an upload and is the same for a web or client/server environment. Now you can import online or in batch.
The name of your web server is followed by the string /j2ee/servlet. Don't append an ending slash. When the user picks up the file from his file system, he can click the Submit button to send the file to the server. The destination path on the application server, where the file is stored, must be specified in the DBA setting called PLL_UPLOAD_DEST on A.60.04. This is a valid format for the value (without an ending backslash):
c:\marian\pll_uploads
The folder and file name of the uploaded file are automatically stored in the appropriate fields. The file name is concatenated with the string 'PLLJID' and the ID of the actual PLL job. When the upload to the application server is finished, the user can close the additional browser window. He is prompted that the file is now transferred to the database server. Specify the DBA setting for PLL_UPLOAD_URL on A.60.04 to enable the web server to find the PLL file on the application server. This is a valid entry for the setting:
your_web_server/marian_pll_upld
The name of your web server is followed by a virtual folder name. Don't append an ending slash. Note that you have to define an alias in the web server configuration. In the forms90.conf file on the application server, there should be a line looking like this:
alias /marian_pll_upld/ "c:\marian\pll_uploads/"
The right-hand entry must match the PLL_UPLOAD_DEST except that the trailing backslash is replaced by a slash. The left-hand entry must match the PLL_UPLOAD_URL, but the server name is omitted and an ending slash is added. Make sure that you have set the DBA setting called PLL_IMPORT_PATH on A.60.04 to point to a path on the database server. This setting is always needed whether or not you perform an upload and is the same for a web or client/server environment. Now you can import online or in batch.
The name of your web server is followed by the string /j2ee/servlet. Don't append an ending slash. When the user picks up the file from his file system, he can click the Submit button to send the file to the server. The destination path on the application server, where the file is stored, must be specified in the project default ZP_QSD_UPP on A.20.11/12/13. This is a valid format for the value (without trailing backslash):
d:\mar\qs_doc_upload
When the upload is finished, the user can close the additional browser window. The physical file name on the application server is concatenated with the string 'UFID' and the ID of the actual document. The extension is derived from the associated value on A.10.36.
Your module is reading/writing only on the database server. Log files on the database server can be displayed by means of a forms screen called in the associated module. To transfer files, use FTP or open a network share to access the files. Your module is reading/writing on the application server, but upload/download functionality was not yet implemented at the time this document was created, or the module did not yet exist at this time. Ask the SmartPlant Materials Service Center for detailed information.
Warnings Five users should be the maximum number of users working in this kind of low usage environment. Simultaneous SmartPlant Materials jobs may slow down the performance of other SmartPlant Materials transactions. After a reboot of an integrated server, it will take around 30 minutes to start up all services and databases needed for SmartPlant Materials. Please do not stop the startup scripts. Performance may not reach the same level as the recommended configuration described in the first chapters of this guide.
Important On this single server, 4 GB of memory are needed to host the database server and application server on one server machine.
2. Click Custom as the type of installation you want to perform, and then click Next. 3. Type a name and location for a new Oracle Home. You can use the Browse button to find the applicable location on your machine. When you have entered the necessary information, click Next to continue.
Warning
When defining a new Oracle-Home, do not use any old values. Use the Ora10g and path name provided to simplify the installation process and eliminate the need to edit SQL scripts, which are available as samples on the SmartPlant Materials CD in the following folder: \program files\Intergraph\MARIAN6\samples. Name: Ora10g Path: %drive%\oracle\Ora10g
(If you choose a different drive letter or path for your installation, you must edit the SQL scripts provided on the SmartPlant Materials CD accordingly.)
Part 10: Low Usage Integrated SmartPlant Materials Server Product Components
- Select Oracle Database 10g 10.2.0.1.0. - Select Oracle Database 10g 10.2.0.1.0. - Select Oracle Enterprise Manager Console DB 10.2.0.1.0. - Disable Enterprise Edition Options 10.2.0.1.0. - Select Oracle Net Services 10.2.0.1.0. - Select Oracle Net Listener 10.2.0.1.0. - Select Oracle Connection Manager 10.2.0.1.0. - Select Oracle Call Interface (OCI) 10.2.0.1.0. - Deselect Oracle Programmer 10.2.0.1.0. - Select Oracle XML Development Kit 10.2.0.1.0. Scroll down for further options.
Oracle Services for Microsoft Transaction Server. Oracle Counters for Windows Performance Monitor.
Click Next when all Components have been chosen, as described before. Select the components as shown in the illustrations for installation. Click Next to open the next window.
Part 10: Low Usage Integrated SmartPlant Materials Server Click Next.
4. Select No when asked if you want to create a new database, and then click Next to continue. Important
Click No when asked to create a database. You can create the SmartPlant Materials database by using sample scripts provided to you on the SmartPlant Materials CD. Note Creating a database automatically is not recommended at this time. You will do this task later in the SmartPlant Materials installation because of some special database settings that are necessary for proper installation. If you are familiar with this task, or you are an OracleDBA, you can create the database using your own scripts as you did in former SmartPlant Materials installations (review sample init.ora in this case).
Write down the http-links shown above for later usage. You can also look in the file %ORACLE%\ora10g\install\portlist.ini to check the assigned ports later. 5. Click Exit to leave the Oracle installer.
Continue with the installation of the Patchset 10.2.0.2 before creating the database.
Before you start this procedure, stop all ORACLE Services under Control Panel > Administrative Tools > Services.
Stop the Oracleora10giSQL*Plus service in order to proceed with the patch installation.
Click Next.
Warning
Define your existing Oracle-Home. Do not use any other values that may be displayed here. Name: Ora10g Path: %drive%\oracle\Ora10g SmartPlant Materials Installation and Migration Guide 191
Click Install.
Click Exit.
Click Yes to exit the installer. The Oracle database software installation is finished.
Before you start this procedure, stop all ORACLE-10g Database-Services under Control Panel > Administrative Tools > Services.
Part 10: Low Usage Integrated SmartPlant Materials Server The above screen will open followed by the Installer window.
Click Next.
Specify your Oracle 10g database home. Do not use the default displayed values. Click Next.
Click Install.
Click Yes.
Installing the Oracle 10g Database One Off Patchset 10.2.0.3 (Patch # p5731535)
Patch Installation Instructions
Follow these steps: 200 SmartPlant Materials Installation and Migration Guide
Part 10: Low Usage Integrated SmartPlant Materials Server Cleanly shut down all processes running from the ORACLE_HOME. Go to the directory where you downloaded the patch: > cd 5731535 Set the ORACLE_HOME clear environment variable to the correct Oracle home that needs to be patched.
> set ORACLE_HOME=<Oracle Home Path>
Ensure that the directory containing the OPatch script appears in your PATH setting. Enter the following command to run OPatch:
> opatch apply
Inspect the opatch-<timestamp>.log file generated in %ORACLE_HOME%\cfgtoollogs\opatch for any errors. This marks the end of the Oracle database software installation. Please continue with Part 1: Oracle 10g iAS Release 2 Installation, or follow the next pages to install the application server on the same machine.
Click Next.
Click Next.
You will find this default printer in the Printers and Faxes on the Control Panel when this configuration has finished successfully.
The user must be listed directly in the Administrators group. The user cannot belong to the group indirectly (for example, by being a member of a group that is part of the Administrators group). To check if you belong to the Administrators group:
Windows 2000 or Windows XP: On the desktop, right-click My Computer, and then click Manage.
Windows 2003: On the desktop, right-click the local computer icon, and then click Manage. 2. On the left side, expand Local Users and Groups, and click Users.
3. On the right side, right-click the user, and click Properties. This displays the Properties dialog box. 4. On the Properties dialog box, click the Member Of tab. If you are not a member of the Administrators group, get an administrator to add you to the group, or log in as a user who is a member of the Administrators group.
Part 10: Low Usage Integrated SmartPlant Materials Server How to Set Environment Variables This section describes how to set environment variables in Windows: 1. Display the System Control Panel.
Windows 2000: Click Start > Settings > Control Panel > System.
Windows 2003: Click Start > Control Panel > System. 2. Select the Advanced tab. 3. Click Environment Variables. 4. To change the value of a variable, select the variable, and click Edit.
Oracle Application Server requires minimum versions of some system files in the Windows system directory (typically, C:\Windows\system32 or C:\Winnt\system32). When you run the installer for Oracle Application Server, the installer checks the Windows system files on your computer. If it finds old versions of these files, and the files are in use by other processes, then it prompts you to exit the installer and run wsf.exe to install the latest Windows system files. (If it finds old versions of the files, but the files are not in use by other processes, then it just replaces the files and you do not have to run wsf.exe.) You can find wsf.exe in the same directory as the installer. To run wsf.exe, which you need to do only if prompted by the installer, perform these steps: 1. Start wsf.exe, which starts up Oracle Universal Installer to install the Windows system files. CD-ROM (assumes E: is the CD-ROM drive): E:\> wsf.exe DVD-ROM (assumes E: is the DVD-ROM drive): E:\> cd application_server E:\application_server> wsf.exe 2. At the Welcome screen, click Next. 3. On the File Locations screen , specify the following information: Destination Name: Enter a name for the Oracle home for wsf. Destination Path: Enter any full path. The installer installs the files in the proper system directories, regardless of the value you enter in this field.
Click Next. 4. Warning: System Reboot Required screen If you see this screen, the installer will reboot your computer automatically at the end of this installation to complete the Windows system files installation. Save and close applications (other than this installer) that you have running on your computer. Click Next. 5. At the Summary screen, click Next to start installing the Windows system files.
7. If the installer displayed the "Warning: System Reboot Required" screen during installation, the installer will now reboot your computer. If not, please reboot your computer before continuing.
Click Next to reboot the machine. 8. After Windows restarts or at the end of the Windows System Files installation, restart the Oracle10g iAS installation.
Infrastructure Installation
Starting the Oracle Universal Installer (OUI)
If the autorun feature is active, the welcome-screen automatically pops up when you insert the CD. If not, start the setup.exe from the root directory of your installation CD. After the welcome screen appears, click Next. The load procedure requires that the machines virtual memory be set to 1024 MB.
The Oracle Universal Installer will check the OS, display properties, and CPU speed, and then you see the OUI welcome screen.
Part 10: Low Usage Integrated SmartPlant Materials Server Choose your first Oraclehome, which will become the home where your Oracle infrastructure instance will be stored. This is recommended to be done on a separate server for better performance. Anyway, we want to place it on the same machine, so please define C:\Oracle\oraInfra as your first Oraclehome on this application server. The home name must be within 16 characters and can only contain alphanumeric and underscores. Do not use blanks in the Home name or for the path. Choose your first Oraclehome, which will become the home where your Oracle infrastructure instance will be stored. Click Next to continue.
Under Available Languages, click English to be your preferred language, and then click OK.
Click Oracle Application Server Infrastructure 10g (the second, middle option). Click Next. Click Identity Management and Metadata Repository (the first option).
Click Next. OUI displays a progress bar in the upper left corner.
Set the Administrator privileges as shown above, and then click Next.
Click Automatic for the port configuration, and then click Next.
Fill in the OCA fields similar to what is shown above, and then click Next.
Enter a password, and write it down for possible later usage. We have chosen manager1 as the password on this reference environment.
Rename the global database name to INFRA, and specify a database file location using the Browse button to create a new oradata-directory in the infrastructure home.
Use the same password for all accounts. Enter a password and confirmation. Write down this password for possible later usage.
Specify an Instance name, and enter the ias_admin password. This password will be used later to log on to the administration web pages. Click Next.
Your installation summary appears. Click Install to start the Infrastructure installation.
A progress window appears during the installation. This installation procedure will take a while. You can switch to the database server installation during this time on your second server.
Click Exit to end the installation of the first Oraclehome for the Infrastructure.
Click Yes. Now you can reach the new Infrastructure environment via an internet address, for example : http://dor-msc-ms01:18100. To reach this link from inside Windows 2003 Server, you may have to change the security options of Internet Explorer to a medium level.
A logon dialog box appears. Use ias_admin and your password to enter the Enterprise Manager web site.
iAS Installation
Installation of Oracle 10g Business Intelligence and Forms
This part of the installation will create a new Oraclehome including the Forms and Reports services, which are needed for the SmartPlant Materials installation.
Run setup.exe from Disk 1 again to invoke the Oracle Universal Installer (OUI).
Click Next.
Specify an new Oraclehome named oraIAS. Important: Do not use the existing Oraclehome for this installation. Click Next.
Under Available Languages, click English for your preferred language, and then click OK.
Click Oracle Application Server 10g, the first option. Click Next.
Click the following options on the screen and then click Next:
Oracle Application Server 10g Discoverer Oracle Application Server 10g Reports Services Oracle Application Server 10g Forms Services Important You must check Reports and Forms. Intergraph recommends that you also select Discoverer to minimize possible later configuration, even if you arent using Discoverer now. Selecting Reports and Forms is sufficient if you are never going to use Discoverer. Refer to the SmartPlant Materials Discoverer documentation.
Enter your hostname (server name) and port 389 for the OID. Click Next.
Enter a password for orcladmin, and make sure that you remember it. Click Next.
Part 10: Low Usage Integrated SmartPlant Materials Server The Metadata Repository is stored in the Infrastructure database, which was already created in your first Oraclehome.
Specify an Outgoing Mail Server, and click Next. If you dont know this information, request it from your local network administration team. This information may be used for Reports configuration. You can leave this field blank and configure this later.
Specify an Instance Name for your IAS-Instance, and enter the password. Click Next.
The product summary appears next. Click Install to start the installation.
Click Yes to exit the Oracle Universal Installer. To check the new services that were created during the IAS-Installation, open the OracleoraIASASControl service.
This is the Enterprise manager. Enter ias_admin as the username, and use the password you defined during installation.
You will now have two standalone instances displayed in OEM. Click the name of the IAS instance, not the INFRA instance, to have all components displayed. The linked page appears.
If there are errors here, click Restart all to start the components. Pass the warning and confirmation window. All components should be displayed as running afterwards.
Possible Errors
On the ias_home page in EM, the CPU usage and MEM usage sections may report a problem:
"The underlying data for the CPU usage chart is unavailable". "The underlying data for the memory usage chart is unavailable.
The problem is related to the locale settings, namely the decimal character (must be '.' for use in java). The problem is that the program used to collect the operating system statistics (in Windows) is sensitive to the locale settings used. But as the EM is launched as a service using LocalSystem as logon credentials, you have to go to the registry to modify the settings. Go to 'My Computer\HKEY_USERS\.DEFAULT\Control Panel\International', and modify the sDecimal setting to '.'.
Part 10: Low Usage Integrated SmartPlant Materials Server You may be prompted to install an ActiveX control. Install the Oracle JInitiator.
Part 10: Low Usage Integrated SmartPlant Materials Server Click Next.
Click OK.
The screen above appears to let you know that the forms service is running properly.
This is the Enterprise manager. Enter ias_admin as the username, and use the password you defined during installation.
You will now have two standalone instances displayed in OEM. Click the name of the IAS instance, not the INFRA instance, to have all components displayed. The linked page appears.
Click Yes when you are prompted to really stop this application server.
Part 10: Low Usage Integrated SmartPlant Materials Server The Components appear as follows:
Set the Oracle environment variable C:\5174901>set oracle_home Environment variable oracle_home not defined C:\5174901>set oracle_home=C:\oracle\oraIAS Set the path variable to the opatch-directory. C:\5174901>set path=%path%;C:\oracle\as_10gR2\opatch Execute the patch installation C:\ 5174901>opatch apply
Part 10: Low Usage Integrated SmartPlant Materials Server If you see the message above, your patch installation has finished successfully. Next steps: Install the SmartPlant Materials software as described in the Installing SmartPlant Materials Software section. Please skip to the Creating a SmartPlant Materials 6.2 Basic Database section to continue the installation. Then, go to the SmartPlant Materials 2007 Application Server Wizard section.
In %MARIAN%\samples\oradata\MAR62\scripts\useful\specials\, you will find a file named sqlnet.ora, which needs to be copied to all your Oracle-homes. Because there are three homes existing in an integrated environment, please copy the sqlnet.ora to all three Oracle homes <%ORACLE_HOME%>\network\admin.
Part 10: Low Usage Integrated SmartPlant Materials Server Modify tnsnames.ora in all 3 three Oracle homes <%ORACLE_HOME%>\network\admin as follows:
MAR62.WORLD = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(Host = your_servername )(Port = 1522))) (CONNECT_DATA = (SID = MAR62))) LISTENER_DB10G.WORLD = (ADDRESS = (PROTOCOL = TCP)(HOST = your_servername)(PORT = 1522)) tnsnames_integrated_environment.ora is stored as a sample in %MARIAN%\samples\oradata\MAR62\scripts\useful\specials\
Important
Please watch out that this configuration uses Port 1522 because the application server has already blocked this port for the Infrastructure database. Please do not delete/replace the existing tnsnames-files because there are entries that may be missing if you just replace these files. Please prepare a backup of any file before you modify the values.
Part 10: Low Usage Integrated SmartPlant Materials Server Use the Net Configuration Assistant from the Oracle 10G programs menu.
Click Next.
Use a Listener name that is different from LISTENER. We recommend to name it DB10G so that it is different from the existing Listener for the application server.
Part 10: Low Usage Integrated SmartPlant Materials Server Click Next.
Select Use another port number, type 1522, and click Next.
Click Next.
Click Finish. The Net Configuration Assistant window will terminate now.
Part 10: Low Usage Integrated SmartPlant Materials Server Open the services tab, and click Refresh. Check to see if the Oracleora10gTNSListener has been created and is started.
The installation of Low Usage Integrated SmartPlant Materials Server concludes with this step. Please continue with Logging On To Your SmartPlant Materials Database, and follow the standard installation for further configuration procedures.
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
This chapter describes how to upgrade an existing Oracle 10.2.0.2 database to 10.2.0.3.0. The software installation is decribed in Part 3 of this guide. After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home: Note
If you do not run the Oracle Database Upgrade Assistant script as described in this section, then the following errors appear:
ORA-01092: ORACLE instance terminated. ORA-39700: database must be opened with UPGRADE option.
Log in with administrator privileges. Set the values for the environment variables ORACLE_HOME, ORACLE_SID, and PATH. For single-instance installations, if you are using Automatic Storage Management, start the Automatic Storage Management instance. For Oracle single-instance installations, start the listener as follows:
C:\> lsnrctl start
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
Run Oracle Database Upgrade Assistant either in the interactive or noninteractive mode: Interactive mode: Start the Oracle Database Upgrade Assistant: From the Start menu, select Programs, then Oracle - HOME_NAME, then Configuration and Migration Tools, and then Database Upgrade Assistant to start the Oracle Database Upgrade Assistant.
Complete the following steps displayed on the Oracle Database Upgrade Assistant screen:
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
On the Databases screen, select the name of the Oracle database that you want to update, and then click Next.
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant Note
On the Recompile Invalid Objects screen, select the Recompile the invalid objects at the end of upgrade option, and then click Next.
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant If you have not taken the backup of the database earlier, on the Backup screen, select the I would like to take this tool to back up the database option, enter the Path, and then click Next.
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant On the Summary screen, check the summary, and then click Finish.
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
At the End of upgrade screen, click Exit, and then click Yes to exit from the Oracle Database Upgrade Assistant.
Check the SYSTEM Tablespace Size If JServer is part of the installation, ensure that there is at least 50 MB of free space allocated to the SYSTEM tablespace or autoextend space in your SYSTEM tablespace prior to upgrading. Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE initialization parameters
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows: 1. Start the OracleService SID service and Oracle Listener service from the Control Panel by selecting Administrative Tools and then Services. 2. Start the database with the NOMOUNT option:
SQL> STARTUP NOMOUNT
3. If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
SQL> SHOW PARAMETER PFILE;
This command displays the name and location of the server parameter file or the initialization parameter file. 4. Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE SQL> SHOW PARAMETER JAVA_POOL_SIZE
5. If the system is using a server parameter file: If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant 6. If the system uses an initialization parameter file, if necessary, change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora). 7. If you use Automatic Shared Memory Management, ensure that the value of the SGA_TARGET initialization parameter size is at least 50 MB greater than the sum of the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters. 8. Shut down the database:
SQL> SHUTDOWN
If you do not run the catupgrd.sql script as described in this section and you start up a database for normal operation, then ORA-01092: ORACLE instance terminated. Disconnection forced errors will occur, and the error ORA-39700: database must be opened with UPGRADE option will be in the alert log.
Log in with administrator privileges. For single-instance installations, start the listener as follows:
C:\> lsnrctl start
For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
C:\> sqlplus /NOLOG SQL> CONNECT SYS/SYS_Password AS SYSDBA
Enter the following SQL*Plus commands: 268 SmartPlant Materials Installation and Migration Guide
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
SQL> SQL> SQL> SQL> STARTUP MIGRATE SPOOL patch.log @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catupgrd.sql SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script. This list provides the version and status of each SERVER component in the database. If necessary, rerun the catupgrd.sql script after correcting any problems. Restart the database:
SQL> SHUTDOWN SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
Note
When the 10.2.0.3 patch set is applied to an Oracle Database 10g Standard Edition database or Standard Edition One database, there may be 42 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect database operation. Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following:
BIN$4lzljWIt9gfgMFeM2hVSoA==$0
Due to the hardware limitations on an Integrated Server Environment , you must start all Oracle services with a batch file. Set all Oracle-Services listed below to Manual on the Services tab:
Please copy the start_as.cmd and sleep.exe files to drive c on your application server:
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
Note
After a reboot of an Integrated Server, it will take around 30 minutes to start up all services and databases needed.
Upgrading a Release 10.2 Database to 10.2.0.3 using Oracle Database Upgrade Assistant
to
# Page displayed to users to allow them to download Sun's Java Plugin. # Sun's Java Plugin is typically used for non-Windows clients. # (NOTE: you should check this page and possibly change the settings) jpi_download_page=http://java.sun.com/products/archive/j2se/1.6.0_02/index.html # Parameter related to the version of the Java Plugin jpi_classid=clsid:CAFEEFAC-0016-0000-0002-ABCDEFFEDCBA # Parameter related to the version of the Java Plugin jpi_codebase=http://java.sun.com/update/1.6.0/jinstall-6-windows-i586.cab#Version=6,0,0,0 # Parameter related to the version of the Java Plugin jpi_mimetype=application/x-java-applet;jpi-version=1.6.0_02 # EM config parameter # Set this to "1" to enable Enterprise Manager to track Forms processes em_mode=0
SmartPlant Materials and Microsoft Vista Click Close. Click the yellow banner. Select Installation Blocked Install ActiveX Control..
You may be prompted to use the administrative account to install this ActiveX Control.
Click OK.
Click Install.
Click Accept.
Click Finish.
As a result of these installation steps, you will be able to use SmartPlant Materials on Vista clients.
Followed by:
SmartPlant Materials Installation Pitfalls Obviously, this was not done after the installation of SmartPlant Materials 6.2. Make sure that the frmall_jinit.jar delivered with SP2 (timestamp 29-Jan-2007) is copied to the <Oracle_iAS_Home>\forms\java. Then, clear the Jar cache and delete the certificate on the clients. To do this task, start the JInitiator from the Control Panel, select the Cache tab, and click Clear JAR Cache.
Then, select the Certificates tab, select Intergraph Corporation, and click Delete. When you start SmartPlant Materials again, you will be prompted to grant the Intergraph certificate. After login to SmartPlant Materials, the error messages shouldn't occur anymore, and the menu should appear properly.
Click the Data Execution Prevention tab , and check Turn on DEP. Use the Citrix Access Management Console to add SmartPlant Materials:
Expand Citrix Access Management Console > Citrix Resources > Presentation Server > CitrixFarm, and right-click Applications to create a new folder.
Click Next.
Add the following entry to the Command line box: "C:\Program Files\Internet Explorer\iexplore.exe" http://your_server/forms/frmservlet?config=jinit_md Add the following value to the Working directory box: %HOMEDRIVE%%HOMEPATH% Click Next.
Click Next.
As a result of the configuration, you will see SmartPlant Materials in the Applications tree. Please go to the next section to configure the Client side.
http://www.citrix.com/English/SS/downloads/details.asp?dID=2755&downloadID=6 80150&pID=186
After downloading the software, you will see the screen above.
Click Next.
Click Install.
You may have to restart the Client after the last installation step.
Please log on to Citrix with your username, password, and name of the Citrix-Server.
You will be prompted to enter your username, password, and domain again.
Did you find any errors? Is the information clearly presented? Do you need more information? If so, where? What features did you like most about this document?
MSC-DE@intergraph.com Intergraph (Deutschland) GmbH SmartPlant Materials Service Center Martin-Schmeier-Weg 18 D-44227 Dortmund Germany Phone ++49-231/72596-111 Fax ++49-231/725969-100
Index
Index
analyzing schema, 137 application server hardware requirements, 11, 180 software requirements, 11, 180 architecture, 153 three-tier, 6 batch mode, 172 client files, 153 Client Installation, 17 client tier, 6 codelists, 166 printing, 166 Comm Eval Cklsts, 162 commercial evaluation checklist, 164 copying issues, 150 database Java pool size, 130 database server installation, 79, 180 database servers system requirements, 15, 77 database shared pool size, 130 database tier, 7 databases backing up, 127 creating, 101 documents, 160 attached, 160 displaying to users, 159 external, 159 sets, 160 downloading files from SmartPlant Materials, 153, 155, 156 exporting graphic, 158 OII, 158 OMI, 157 external documents, 159 files application server, 155 application text files, 155 client, 153, 154 created for PDMS, 165 created for PDS, 166 database server, 155 database server text files, 155 server, 153, 154 uploading with servlets, 145 graphic export, 158 import, 173 hardware requirements, 11, 180 database servers, 15, 77 iAS hardware and software requirements, 11, 180 Ident Tech Eval Cklsts, 162 IE5 using, 152 importing graphic, 173 linelist, 176 OII, 173 OMI, 171 OPI, 175 PDMS, 174 inquiry commercial evaluation, 163 installation process (fresh install), 122 instance initialization parameters, 130 issues copying, 150 pasting, 150 printing screen, 150 Java-Applet, 6 key mapping, 147 licensing, 138 Linelist import, 176 log files, 136 material groups, 162 message lines removing, 151 middle tier, 7 migration, 127 database server, 133 prerequisites, 130 modes batch, 172 Online, 172 modules missing, 178 MS JVM using, 152 OII export, 158 import, 173 OMI export, 157 import, 171 Online mode, 172 OPI import, 175 Oracle
Index
9.2 installation, 79, 180 Oracle Home, 80, 182 Patchset 8.1.7.2.1, 88, 91, 190, 194 pasting issues, 150 PCD printing, 166 PDL printing, 168 PDMS import, 174 PMC printing, 167 POs attached, 164 closeout activities, 163 print screen issues, 150 printing associated codelists, 166 codelists, 166 PCD, 166 PDL, 168 PMC, 167 screen data to a file, 168 Quote Detail Tec Eval, 164 receiving files from SmartPlant Materials, 153, 155, 156 recommendations database servers, 15, 77 hardware, 11, 180 software, 11, 180 remote quotation, 177 removing message line, 151 requirements database servers, 15, 77 hardware, 11, 180 software, 11, 180 schema analyzing, 137 sending files to SmartPlant Materials, 154, 155, 170, 171 server files, 153 servers database, 15, 77 SmartPlant Materials installation, 17 software requirements, 11, 180 system requirements, 11, 180 database servers, 15, 77 terms, 161 attached, 161 tests servlets, 64, 242 text, 161 attached, 161 three-tier-architecture, 6 tiers client, 6 database, 7 middle, 7 uploading files to SmartPlant Materials, 154, 155, 170, 171 Web environment, 154 Web server enabling, 156