Tag Archives: Installation - Page 2

Installing PeopleTools PeopleBooks 8.49

Problem: When user clicks on PeopleTools > Web Profile > Web Profile Configuration, clicks Search > Dev, and then clicks the Help link, the following message appears:

Help cannot be displayed because no help topic was found for the help context ID "WEB_PROF_GENERAL". 
To view the PeopleSoft Online Library, click here.

Solution: The PeopleTools PeopleBooks CD was not installed.

Read more »

Upgrading 11i EBS 9i Database to 10g

This document shows how to upgrade the 9i database in 11i E-Business Suite to 10g on Linux.

Metalink Reference:

Doc ID:  362203.1 (Subject:  Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0))

Section 1: Upgrading an 11i Database to Oracle Database 10g Release 2 (10.2.0)

Ignore steps 1 – 5 in the Metalink document.

Begin at Step 6.

Step 6:        Prepare to create the 10.2.0 Oracle home

Download Oracle Database 10g Release 2 (10.2.0.1.0) Enterprise/Standard Edition for Linux x86

10201_database_linux32.zip (668,734,007 bytes) (cksum – 2737423041)

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

http://www.oracle.com/technology/documentation/database10gr2.html

http://www.oracle.com/technology/support/metalink/index.html

Step 7:        Install the base 10.2.0 software

Install Oracle Database 10g Release 2 (10.2.0.1.0) Enterprise/Standard Edition for Linux x86

Refer to chapter 3, Oracle Database Installation Guide 10g Release 2 (10.2)

Unzip 10201_database_linux32.zip

Create directory: /u01/oracle/visdb/10.2.0

Ensure OS meets requirements for 10g

Set ORACLE_HOME=/u01/oracle/visdb/10.2.0

Set ORACLE_SID=VIS

Begin installation (./runInstaller)

  • Advanced installation
  • Choose Enterprise Edition installation type
  • Do not upgrade existing database
  • Install database software only

Note: You may need to increase the swap file to 4GB before installing 10g.

Step 8:        Install Oracle Database 10g Products from the 10g Companion CD

Refer to section 3.5, “Installing Oracle Database 10g Products” in the Oracle Database Companion CD Installation Guide

Unzip 10201_companion_linux32.zip

Ensure OS meets requirements for 10g (should be in place)

Set ORACLE_HOME=/u01/oracle/visdb/10.2.0

Set ORACLE_SID=VIS

Begin installation (./runInstaller)

  • Oracle Database 10g Products 10.2.0.1.0 (not Oracle HTML DB or Oracle Database 10g Companion Products)
  • Choose the 10g Home

Step 9:        Perform 10.2.0.4 patch set pre-installation tasks

Oracle® Database Patch Set Notes

10g Release 2 (10.2.0.4) Patch Set 3 for Linux x86

Metalink Doc ID: 316900.1

Download patch 6810189 (p6810189_10204_Linux-x86.zip)

Unzip p6810189_10204_Linux-x86.zip

Ensure OS meets requirements for 10g (should be in place)

Set ORACLE_HOME=/u01/oracle/visdb/10.2.0

Set ORACLE_SID=VIS

Stop all processes (dbconsole, iSQL*Plus, database listener)

Backup Oracle Inventory, Oracle database, Oracle Home

Begin installation (./runInstaller)

  • Oracle Database 10g Products 10.2.0.1.0 (not Oracle HTML DB or Oracle Database 10g Companion Products)
  • Choose the 10g Home

Perform 10.2.0.4 patch set pre-installation tasks

On the database server node, as the owner of the Oracle 10g file system and database instance, unzip and extract the 10.2.0.4 patch set file for your platform. Read the patch set notes (usually README.html). Make sure you thoroughly understand the upgrade and patch set installation process before you begin. Check OracleMetaLink or contact Oracle Support Services to determine any known issues with the patch set and its interoperability with Oracle E-Business Suite.

Perform the tasks in the “Preinstallation Tasks” section of the patch set notes (if they apply to your system).

Step 10:   Perform 10.2.0.4 patch set installation tasks

On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in the “Installing the Oracle Database 10g Patch Set Interactively” section of the patch set notes. Make sure that:

The ORACLE_HOME environment variable points to the new 10.2.0 Oracle home.

The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin).

The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.

The PERL5LIB environment variable points to the directories where the new perl libraries are located (usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl version>)

You use the runInstaller (UNIX/Linux) or the setup.exe executable (Windows) provided in the patch set to run OUI.

Step 11:    Create nls/data/9idata directory

Run: perl $ORACLE_HOME/nls/data/old/cr9idata.pl script

Modify set10g.env:

export ORA_NLS10= ORACLE_HOME/nls/data/9idata

Step 12:   Apply additional 10.2.0.4 RDBMS patches

Download from Metalink and apply:

6880880 or the latest OPatch version.

6521934

6600051

7496636

7497678

cd $ORACLE_HOME

unzip /u01/patches/p6880880_102000_LINUX.zip

You do not have a current session, please log in before visiting this URL

Problem: After installing 11.5.9 Vision instance, the E-Business Suite logon appears, and the user is able to log on as SYSADMIN/SYSADMIN. However, after logging on, the following message appears:

You do not have a current session, please log in before visiting this URL

When trying to troubleshoot the issue with aoljtest.jsp, the user is able to login, but when trying to access all the tests, the following message appears:

"This page can only be accessed through aoljtest.jsp"

Solution:

The domain name of the machine had only one component (localdomain). This was changed to cia.org.tt (at least two components) and the instance wiped and reinstalled.

adalnctl.sh: exiting with status 127

Problem: After installing 11.5.9 Vision instance, the apps listener exits with status 127.

Solution: Apply operating system patch 3830807

Metalink Reference:

Subject:  Attempt To Start Listener Exits With Status 127

Doc ID:  299810.1

Error in invoking target install of makefile ins_plsql.mk

Problem:

While installing Oracle 9.2.0.4 on Oracle Enterprise Linux 4 Update 4, the following error appears:

Error in invoking target install of makefile
/u01/app/oracle/plsql/lib/ins_plsql.mk

Solution:

Applied patch 4198954 (COMPATIBILITY PACKAGES FOR ORACLE ON RHEL 4)

Applying patch 4198954 resolved the installation error.

Insufficient privileges to write to the specified path in component Database Configuration Assistant 9.2.0.1

Problem: While installing Oracle 9.2.0.4 for Linux, the following error appears in RunInstaller:

Error: You do not have sufficient privileges to write to the specified path. In component Database Configuration Assistant 9.2.0.1.0. Installation cannot continue for this component.

Solution: Export ORACLE_BASE:

export ORACLE_BASE=/u01/app/oracle

Exporting ORACLE_BASE resolved the issue.

Subject: Linux 9.2.0.4 Installation – Error: You do not have sufficient privileges to write to the specified path in Database Configuration Assistant Component (Doc ID: 267171.1)

PeopleSoft HR 8.9 Installation Steps

Hardware/Software Specifications

Server Hostname

Server Description IP Address
GLWEBAPP GL Web & App Server 10.x.x.x
GLDBASE GL Database Server 10.x.x.x

The machines that were used in the installation of the PeopleSoft test environments were Dell PowerEdge 2950.

The operating system for both servers was Microsoft Windows Server 2003 R2 Enterprise Edition Service Pack 2.

The GLDBASE machine shall house only the database server software (Microsoft SQL Server 2005).

The GLWEBAPP machine shall house all the other server software:

  • File Server (PeopleTools)
  • Application Server (Tuxedo)
  • Web Server (IBM WebSphere)
  • Batch Server

These two servers were accessed remotely using Remote Desktop Connection. Local administrator accounts were set up on these two machines. The username for these accounts were ProjAdmin1, ProjAdmin2 and ProjAdmin3.

Installation Sequence

The following steps were performed in this sequence to install the PeopleSoft Demo instance:

 PeopleSoft Demo Installation (FSDMO)

  1. Install SQL Server [ok 10-Nov-08]
  2. Install PeopleTools 8.49 on Database Server [17-Nov-08]
  3. Install PeopleTools 8.49 on Application Server [ok 11-Nov-08]
  4. Install Application (Financials) on Database Server [ok 17-Nov-08]
  5. Install Application (Financials) on Application Server [ok 11-Nov-08]
  6. Install Tuxedo (Application Server) [ok 11-Nov-08]
  7. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 17-Nov-08]
  8. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 12-Nov-08]
  9. Install IBM WebSphere (Web Server) [ok 11-Nov-08]
  10. Create Database Manually [ok 18-Nov-08]
  11. Shutdown, Backup Database After Creating
  12. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08] [reinstall WebLogic 28-Nov-08]
  13. Create Application Domain [ok 18-Nov-08]
  14. Install PeopleTools PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  15. Install Application PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  16. Create Process Scheduler [ok 18-Nov-08]
  17. Apply Maintenance Pack 5 (Financials)

PeopleSoft Demo Installation (FSDEMO)

This FSDEMO installation shall be a plain-vanilla installation (without MP5).

  1. Install SQL Server [already installed]
  2. Install PeopleTools 8.49 on Application Server [ok 15-Dec-08] [E:PSOFTFSDEMO]
  3. Install PeopleTools 8.49 on Database Server [ok 15-Dec-08] [D:PSOFTFSDEMO]
  4. Install Application CDs (Financials) on Database Server [ok 15-Dec-08]
  5. Install Application CDs (Financials) on Application Server [ok 15-Dec-08]
  6. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 15-Dec-08]
  7. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 15-Dec-08]
  8. Install Tuxedo CD (Application Server) [already installed in E:bea]
  9. Install IBM WebSphere CD (Web Server) [already installed in E:IBMWebSphere]
  10. Create Database Manually [ok 18-Nov-08]
  11. Shutdown, Backup Database After Creating
  12. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08] [reinstall WebLogic 28-Nov-08]
  13. Create Application Domain [ok 18-Nov-08]
  14. Install PeopleTools PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  15. Install Application PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  16. Create Process Scheduler [ok 18-Nov-08]
  17. Apply Maintenance Pack 5 (Financials)

PeopleSoft Sys Installation

  1. Install SQL Server [ok 10-Nov-08]
  2. Install PeopleTools 8.49 on Database Server [17-Nov-08]
  3. Install PeopleTools 8.49 on Application Server [ok 11-Nov-08]
  4. Install Application (Financials) on Database Server [ok 17-Nov-08]
  5. Install Application (Financials) on Application Server [ok 11-Nov-08]
  6. Install Tuxedo (Application Server) [ok 11-Nov-08]
  7. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 17-Nov-08]
  8. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 12-Nov-08]
  9. Install IBM WebSphere (Web Server) [ok 11-Nov-08]
  10. Create Database Manually [ok 18-Nov-08]
  11. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08]
  12. Create Application Domain [ok 18-Nov-08]
  13. Install PeopleTools PeopleBooks [ok 18-Nov-08]
  14. Install Application PeopleBooks [ok 18-Nov-08]
  15. Create Process Scheduler
  16. Install Crystal Reports (on Workstation)
  17. Install Change Assistant
  18. Apply Maintenance Pack 5 (Financials)

Precedence

The SQL Server software must be installed before the PeopleTools.

PeopleTools Product Patch must be installed before PIA.

Step 1: SQL Server Installation

The Microsoft SQL Server 2005 DVD was staged (that is, copied) to D:stagingSQLServer2005 on the GLDBASE machine. After staging, setup.exe from D:stagingSQLServer2005Servers was run.

By default, the following required components were installed prior to installing SQL Server:

  • .NET Framework 2.0
  • Microsoft SQL Native Client
  • Microsoft SQL Server 2005 Setup Support Files

These components were installed to C:Program FilesMicrosoft SQL Server by default.

The other SQL Server components were installed to D:Program FilesMicrosoft SQL Server. These components are:

  • Database Services
    • Data Files
    • Replication
    • Full-Text Search
    • Shared Tools
  • Client Components
    • Connectivity Components
    • Management Tools

The Microsoft SQL Native Client (SNaC) must also be installed on the GLWEBAPP machine in which PeopleTools is installed. To do so, share the D:staging directory on GLDBASE (10.18.14.31). From GLWEBAPP, navigate to \10.x.x.xstagingSQLServer2005Servers. Then run setup.exe.

Allow the required components to install (.NET Framework 2.0, Microsoft SQL Native Client and Microsoft SQL Server 2005 Setup Support Files). Continue the installation and install the Connectivity Components on GLWEBAPP.

Step 2: File Server (PeopleTools) Installation

It was necessary to install up the SQL Server Connectivity Components on the GLWEBAPP because the SQL Server Connectivity Program Directory must be specified as part of the installation.

The seven PeopleTools CDs were staged to the E:stagingCDImages

Note that you MUST install PeopleTools on both nodes.

The following values/options were set as part of the PeopleTools installation on the peoplesoft4hr node:

Variable Value
PeopleSoft (PeopleTools) License code z66smq-22c7mc-3w444e1-2is234-81p1f7
Type of Database Non-Unicode Database
Peoplesoft Application Server Checked
Peoplesoft Batch Server Checked
Peoplesoft Database Server Checked
Peoplesoft File Server Checked
Peoplesoft Web Server Checked
PS_HOME Drectory Name E:PSOFTHR900
ERP Connectors? No
Connectivity Program Directory C:Program FilesMicrosoft SQL Server80Toolsbinn
Install PeopleTools Icons? Yes
PeopleTools Program Group Folder PeopleTools 8.4
Environment Hub machine name Peoplesoft4hr
Environment Hub Port Number 8000
PeopleTools (Product Installation) Checked
PeopleTools System Database Checked
PeopleTools Language Pack Not checked
PeopleTools Language Development Kit Not checked

Step 3: Application Installation

To install the PeopleSoft Enterprise Human Resources Management System and Campus Solutions 9.0 (HR) application, the disk was obtained from the CD. It was unzipped (“exploded”) and staged to the F:stagingcd849-HR directory, in the disk1 directory.

To install the Financials application, navigate to F:stagingcd849-HRdisk1 directory and run setup.exe

The following values/options were entered

Variable Value
PeopleSoft (HRMS) License code
Type of Database Non-Unicode Database
PeopleSoft Application Server Checked
PeopleSoft Batch Server Checked
PeopleSoft Database Server Checked
PeopleSoft File Server Checked
PeopleSoft Web Server Checked
PS_HOME Directory Name E:PSOFTFS900

Step 4: Application Server (Tuxedo) Installation

The Tuxedo 9.1 CD (Windows version) was staged to E:stagingCDImagescd849-Tuxdisk1 on the GLWEBAPP server. To install Tuxedo, run pstuxinstall.exe. This brings up a console interface (as opposed to a GUI wizard).

The following prompts appeared when psstuxinstall.exe is run:

1 file(s) copied.

1 file(s) copied.

BEA Home being defaulted to C:\bea  (y/n)? [y]: n

Please provide a BEA Home: E:\bea

Tuxedo 9.1 will be installed to E:\beaTuxedo9.1  (y/n)? [y]: <Enter>

TListen port being defaulted to 3050  (y/n)? [y]: <Enter>

Accept default TListen password ‘password’  (y/n)? [y]: <Enter>

Are you happy with your selections (y/n)? [y]: <Enter>

Tuxedo 9.1 is being installed on your system….

Tuxedo 9.1 base install completed.

Stopping Tuxedo 9.1 Services…

The TListen 9.1 (Port: 3050) service is stopping..

The TListen 9.1 (Port: 3050) service was stopped successfully.

The BEA ProcMGR V9.1 service is stopping.

The BEA ProcMGR V9.1 service was stopped successfully.

Patch installation completed.

Please note that you must reboot your system before using any Tuxedo 9.1 or PeopleSoft applications.

Press any key to continue…

After installing Tuxedo, the GLWEBAPP server was rebooted remotely.

Step 5: Web Server (WebSphere) Installation

The two IBM WebSphere CDs (Windows version) were staged to the E:stagingCDImagescd849-WebSphere directories, in the disk1 and disk2 directories.

To install IBM WebSphere, navigate to disk1 and run installWAS.bat.

Install to E:IBMWebSphereAppServer

For Environments, choose None, then click Yes to accept the choice.

In the Summary screen, click Next.

Uncheck the Create a new WebSphere Application Server profile, and then click Finish.

Step 6: PeopleTools 8.49.15 Product Patch Installation

Check Customer Connection (now Metalink3 at http://metalink3.oracle.com) for the latest PeopleTools 8.49 Product Patch. As at this time, the latest PeopleTools Product Patch for version 8.49 is 8.49.15.

Download this patch 84915.exe from:

ftp://ftp.peoplesoft.com/outgoing/ptools/84915/84915.exe

(The password for 84915.exe is ‘MisterEd’)

Run 84915.exe and unzip the file to E:stagingCDImages. It automatically creates the cd84915 directory and unzips the file.

From E:stagingCDImagescd84915disk1, run setup.exe. It updates PS_HOME (E:PSOFTFS900) with the updated files.

Step 7: Pure Internet Architecture (PIA) Installation

To create the PIA, change directory to E:PSOFTFS900PsMpPIAInstall and run setup.exe

Install PIA to the IBM WebSphere web server, located in E:IBMWEBSPHEREAppServer.

Application name and web site name should be set to the name of the environment e.g. fsdmo. Create a Multi Server installation, not a Single Server installation.

Note that the port numbers for http and https must not be consecutive.

Web Profile Name, User ID and Password should remain the default.

The Report Repository should be set to E:psreports.

The installation process takes about ten minutes to complete.

PeopleSoft HR 8.9 Installation Checklist

1. Install SQL Server

2. Install SQL Server Native Client

3. Stage PeopleTools 8.49 CDs on F:stagingpt-849

4. Install PeopleTools 8.49 on peoplesoft4hr (E:PSOFTHR900)

5. Install Application (Human Resources) on peoplesoft4hr

6. Install Database Manually

7. Task B-1: Running Server Configuration Scripts

8. Task B-2: Creating a Database

9. Task B-3: Configuring ODBC Data Source

10. Task B-4: Running ADDOBJ.SQL

11. Task B-5: Setting Up Connect ID

12. Task B-6: Creating Data Mover Import Scripts

13. Task B-7: Running Data Mover Import Scripts

14. Task B-8: Updating Database to Latest PeopleTools Release

15. Task B-8-2: Updating PeopleTools System Tables

16. Task B-8-3: Updating PeopleTools Database Objects

17. Task B-8-5: Deleting Obsolete PeopleTools Database Objects

18. Task B-8-6: Altering PeopleTools Tables

19. Task B-8-7: Updating PeopleTools System Data

20. Task B-8-8: Running PeopleTools Conversions

21. Task B-9: Running Additional Data Mover Scripts

22. Task B-11: Running VERSION Application Engine Program

23. Task B-12: Changing the Base Language

24. Task B-13: Running SQR Reports

25. Task B-14: Checking the Database

26. Task B-15: Cleaning and Backing Up the Database

27. Shutdown, Backup Database After Creating

28. Install Tuxedo (Application Server)

29. Install BEA WebLogic 9.2 Web Server

30. Install PIA

31. Create Application Domain

32. Install PeopleTools PeopleBooks

33. Install Application PeopleBooks

34. Create Process Scheduler

35. Install COBOL compiler (and license)

36. Execute PTPATCH.DMS using Data Mover (8.49.15)

37. Apply project PATCH849 using Application Designer

38. Run DDDAUDIT, SYSAUDIT to verify system ok, troubleshoot if necessary

39. Shutdown all servers and backup PS_HOME

Enterprise FSCM9.0 PeopleBooks Not Appearing

Problem:

After installing Enterprise FSCM 9.0 PeopleBooks and bouncing PeopleBooks web server, they do not appear in the list of PeopleBooks.

Solution:

Enterprise FSCM 9.0 PeopleBooks installed to wrong directory. It should be installed to the htmldoc directory:
E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warhtmldoc

PIA Installation on IBM WebSphere Hangs on 20%

PIA Installation on IBM WebSphere Hangs on 20%

Problem:

When installing new PIA on IBM WebSphere, the installation hangs for several minutes at 20%

Solution:

Installation takes a long time to complete. If the timeout is not long enough, the installation may fail. (Applying MP5 appears to have resolved this). Else, manually increase the timeout.