Problem: After installing Oracle 9.2.0.4, netca and dbca fail with error:
jre was not found in:
/u01/app/oracle/oracle.swd.jre/bin/i386/native_threads/jre
Solution: Change directory to:
/u01/app/oracle/oracle.swd.jre/bin/i386/native_threads
Then create symbolic link to jre:
ln -s java jre
netca can now be launched.
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.
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)
Problem: While installing Oracle 9.2.0.4 on Oracle Enterprise Linux 4 Update 4, the following error appears:
Error occurred during initialization of VM
Unable to load native library: /tmp/OraInstall2009-08-31_01-27-21PM/jre/lib/i386/libjava.so:
symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
Solution: Apply patch 3006854.
Metalink Reference:
Subject: RUNINSTALLER FAILS ON RED HAT 3 TRYING TO INSTALL ORACLE9I
Doc ID: 264178.1
Problem: When starting emctl for first time after reboot on Linux, the following message appears:
Timezone mismatch: The agentTZRegion value (GMT) in /u01/app/oracle/product/10.2.0/db_1/localhost.localdomain_ORCL/sysman/config/emd.properties does not match the current environment TZ setting().
The dbconsole cannot run with this mismatch.
Solution:
Run:
emctl resetTZ agent
Then run:
emctl start dbconsole
You may need to stop the agent (but it says it is not running):
emctl stop agent
Problem: When attempting to log on to SQL*Plus as ”/ as sysdba’, the following error appears:
ERROR: ORA-12162: TNS:net service name is incorrectly specified
Solution: Set ORACLE_SID=ORCL
export ORACLE_SID=ORCL
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:
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)
PeopleSoft Demo Installation (FSDEMO)
This FSDEMO installation shall be a plain-vanilla installation (without MP5).
PeopleSoft Sys Installation
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:
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:
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.
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
Recent Comments