jre was not found in oracle.swd.jre/bin/i386/native_threads/jre

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.

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)

GLIBC_2.0 not defined in file libc.so.6

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

emctl not starting Timezone mismatch agentTZRegion

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

ORA-12162: TNS:net service name is incorrectly specified

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

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

EXP-00056: ORACLE error 600 encountered

Problem: While performing full export of production database, the following error is encountered:

. . exporting table            WF_NOTIFICATION_OUT
EXP-00056: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [kopi2_readlen083], [], [], [], [], [], [], []

Solution:

Cause:

Bug 3041387 ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KOPI2_READLEN083]

ORA-600 [kopi2_readlen083] can occur while enqueueing an object with an immediate embedded NULL.

This issue is fixed in Oracle Server 9.2.0.5 (Server patch set release) and in Oracle Server 10g.

Patch 3041387 is also available on Metalink.

Fix:

Please apply Oracle Server patch 3041387.

Metalink Reference:

Doc ID: 279647.1: Workflow Notifications Show Ora-00600 With Argument [Kopi2_readlen083] With Oracle Server 9.2

RC-50004: Fatal: Error occurred in ApplyDatabase: Control file creation failed

Problem:

When cloning the database tier of Illuminat HRMS Production, the process fails on 70% with error:

Beginning database tier Apply - Wed May 27 10:12:21 2009
Log file located at /u0/oracle/TEST2/test2db/9.2.0/appsutil/log/TEST2_ebusinesstest/ApplyDBTier_05271012.log
RC-50004: Fatal: Error occurred in ApplyDatabase:
Control file creation failed
ERROR while running Apply...
 ERROR: Failed to execute adclone.pl
 Please check logfile.
Log file /u0/oracle/TEST2/test2db/9.2.0/appsutil/log/TEST2_ebusinesstest/ApplyDBTier_05271012.log showed:
---------------------------------------------------------------
                   ADX Database Utility
---------------------------------------------------------------
getConnectionUsingAppsJDBCConnector() -->
    APPS_JDBC_URL='null'
    Trying to get connection using SID based connect descriptor
getConnection() -->
    sDbHost    : ebusinesstest
    sDbDomain  : illuminatnm.com
    sDbPort    : 1523
    sDbSid     : TEST2
    sDbUser    : APPS
    Trying to connect using SID...
getConnectionUsingSID() -->
    JDBC URL: jdbc:oracle:thin:@ebusinesstest.illuminatnm.com:1523:TEST2
    Exception occurred: java.sql.SQLException: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
    Trying to connect using SID as ServiceName
getConnectionUsingServiceName() -->
    JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ebusinesstest.illuminatnm.com)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=TEST2)))
    Exception occurred: java.sql.SQLException: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
    Trying to connect using SID as ServiceName.DomainName
getConnectionUsingServiceName() -->
    JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ebusinesstest.illuminatnm.com)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=TEST2.illuminatnm.com)))
    Exception occurred: java.sql.SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092864)(ERR=12514)(ERROR_STACK=(ERROR=(CODE=12514)(EMFI=4))))
    Connection could not be obtained; returning null
-------------------ADX Database Utility Finished---------------
adcrdb.sh started at Wed May 27 10:54:18 AST 2009
The environment settings are as follows ...
       ORACLE_HOME : /u0/oracle/TEST2/test2db/9.2.0
        ORACLE_SID : TEST2
          TWO_TASK :
              PATH : /u0/oracle/TEST2/test2db/9.2.0/Apache/perl/bin:/u0/oracle/TEST2/test2db/9.2.0/bin:/usr/bin:/usr/sbin:/u0/oracle/TEST2/test2db/9.2.0/jdk/bin:/usr/ccs/bin:/bin:/usr/bin/X11:/usr/local/bin:../jre/1.3.1/bin:/u0/oracle/testdb/9.2.0/Apache/perl/bin:/usr/kerberos/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:.
   LD_LIBRARY_PATH : /u0/oracle/TEST2/test2db/9.2.0/lib:/usr/X11R6/lib:/usr/openwin/lib:/u0/oracle/TEST2/test2db/9.2.0/ctx/lib
Executable : /u0/oracle/TEST2/test2db/9.2.0/bin/sqlplus
The log information will be written to
        /u0/oracle/TEST2/test2db/9.2.0/appsutil/log/TEST2_ebusinesstest/adcrdb_TEST2.txt
Creating the control file for TEST2_ebusinesstest database ...
SQL*Plus: Release 9.2.0.3.0 - Production on Wed May 27 10:54:18 2009
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
Connected to an idle instance.
ORACLE instance shut down.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area  581506100 bytes
Fixed Size                   451636 bytes
Variable Size             402653184 bytes
Database Buffers          167772160 bytes
Redo Buffers               10629120 bytes
Control file created.
Database altered.
Tablespace altered.
Database altered.
Database closed.
Database dismounted.
ORACLE instance shut down.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area  581506100 bytes
Fixed Size                   451636 bytes
Variable Size             402653184 bytes
Database Buffers          167772160 bytes
Redo Buffers               10629120 bytes
Database mounted.
BEGIN dbms_backup_restore.zeroDbid(0); END;
*
ERROR at line 1:
ORA-01119: error in creating database file
'/u0/oracle/TEST2/test2db/9.2.0/dbs/MISSING00395'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 3284
ORA-06512: at line 1
ORACLE instance shut down.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area  581506100 bytes
Fixed Size                   451636 bytes
Variable Size             402653184 bytes
Database Buffers          167772160 bytes
Redo Buffers               10629120 bytes
Control file created.
Database altered.
Tablespace altered.
Database altered.
old   2:     '/u0/oracle/TEST2/test2db/9.2.0/ctx/lib/libctxx9.&libext'
new   2:     '/u0/oracle/TEST2/test2db/9.2.0/ctx/lib/libctxx9.so'
Library created.
old   2:     '/u0/oracle/TEST2/test2db/9.2.0/lib/libqsmashr.&libext'
new   2:     '/u0/oracle/TEST2/test2db/9.2.0/lib/libqsmashr.so'
Library created.
old   2:     '/u0/oracle/TEST2/test2db/9.2.0/lib/libordim9.&libext'
new   2:     '/u0/oracle/TEST2/test2db/9.2.0/lib/libordim9.so'
Library created.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.3.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.3.0 - Production
exit_code=0
Checking for errors ...
ORA-01119: error in creating database file
ORA-27037: unable to obtain file status
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 3284
ORA-06512: at line 1
The database has not been successfully created. Shutting down the instance ...
SQL*Plus: Release 9.2.0.3.0 - Production on Wed May 27 10:57:56 2009
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
Connected.
ORACLE instance shut down.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.3.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.3.0 - Production
.end std out.
.end err out.
---------------------------------------------------------------
                   ADX Database Utility
---------------------------------------------------------------
getConnectionUsingAppsJDBCConnector() -->
    APPS_JDBC_URL='null'
    Trying to get connection using SID based connect descriptor
getConnection() -->
    sDbHost    : ebusinesstest
    sDbDomain  : illuminatnm.com
    sDbPort    : 1523
    sDbSid     : TEST2
    sDbUser    : APPS
    Trying to connect using SID...
getConnectionUsingSID() -->
    JDBC URL: jdbc:oracle:thin:@ebusinesstest.illuminatnm.com:1523:TEST2
    Exception occurred: java.sql.SQLException: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
    Trying to connect using SID as ServiceName
getConnectionUsingServiceName() -->
    JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ebusinesstest.illuminatnm.com)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=TEST2)))
    Exception occurred: java.sql.SQLException: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
    Trying to connect using SID as ServiceName.DomainName
getConnectionUsingServiceName() -->
    JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ebusinesstest.illuminatnm.com)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=TEST2.illuminatnm.com)))
    Exception occurred: java.sql.SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092864)(ERR=12514)(ERROR_STACK=(ERROR=(CODE=12514)(EMFI=4))))
    Connection could not be obtained; returning null
-------------------ADX Database Utility Finished---------------
RC-00118: Error occurred during creation of database
Raised by oracle.apps.ad.clone.ApplyDatabase
StackTrace:
java.lang.Exception: Control file creation failed
        at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:469)
        at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:314)
        at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:290)
        at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:131)
        at java.lang.reflect.Constructor.newInstance(Native Method)
        at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:68)
        at java.lang.Thread.run(Thread.java:479)

Solution:

The cloning process omits two files that were created since the last adpreclone.pl run. Therefore, run preclone scripts (adpreclone.pl) on the production instance before copying files.

[amazon asin=0070077290&template=iframe image&chan=default]    [amazon asin=1453742735&template=iframe image&chan=default]    [amazon asin=0615238440&template=iframe image&chan=default]