Database 12.1.0.2 Certified with EBS 12.2 on Additional Platforms

Oracle EBS Techstack Blog: Database 12.1.0.2 Certified with EBS 12.2 on Additional Platforms 

Oracle Database 12c Release 1 (12.1.0.2) is now certified with Oracle E-Business Suite Release 12.2 (12.2.2 and higher) on the following additional platforms:

• HP-UX Itanium (11.31)
• IBM AIX on Power Systems (64-bit) (6.1, 7.1)
• IBM: Linux on System Z (RHEL 5,6, SLES 11)^*

^* This is a 'database tier only' or 'split tier configuration' certification where the application tier must be on a fully certified E-Business Suite platform.
 

References

• My Oracle Support Document ID 1926201.1- Interoperability Notes Oracle EBS 12.2 with Oracle Database 12c Release 1
• My Oracle Support Document ID 1594274.1- Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes
• My Oracle Support Document ID 1349240.1- Database Preparation Guidelines for an Oracle E-Business Suite Release 12.2 Upgrade
• My Oracle Support Document ID   396009.1- Database Initialization Parameters for Oracle Applications Release 12
• My Oracle Support Document ID 1626606.1- Using Oracle 12c Release 1 (12.1) Real Application Clusters with Oracle E-Business Suite Release R12.2
  
• My Oracle Support Document ID 1585696.1- Using TDE Column Encryption with Oracle E-Business Suite Release 12.2
• My Oracle Support Document ID 1926686.1- Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12.2 on Oracle Database 12c Release 1 (12.1.0)
• My Oracle Support Document ID 2011169.1 - Using Transportable Database to migrate Oracle E-Business Suite Release 12.2 Using Oracle Database 11g Release 2 or 12c Enterprise Edition
• My Oracle Support Document ID 1367293.1- Enabling SSLor TLS in Oracle Applications Release 12.2
• My Oracle Support Document ID 1926203.1- Export/Import Process for Oracle EBS 12.2 Using Oracle Database 12c Release 1
• My Oracle Support Document ID 1926202.1- Using Oracle EBS 12.2 with a Database Tier Only Platform on Oracle Database 12c Release 1
• Please refer to the platform specific Oracle Database Installation Guides for operating system and other prerequisites.
• Please refer to Oracle Database 12c Release 1 (12.1.0.2) New Features Guide 12c Release 1 (12.1) and Oracle Database Administrator's Guide for more information regarding the "Database In-Memory" feature.

Related Articles

• Database 12.1.0.2 Certified with E-Business Suite 12.2
• Oracle Database 11.2.0.4 Certified with E-Business Suite 12.2
• Database 12.1.0.2 Certified with E-Business Suite 12.1

Oracle WebLogic clustering installation and Configuration on Linux (OEL64bit)

Step by Step Oracle WebLogic clustering installation and Configuration on Linux (OEL64bit)

Example Install Steps for a WCC 11g Multi Node Cluster using WLS Pack/Unpack and Web Tier (Doc ID 1359930.1)

Install WebLogic 10.3.4 or 12C

The following actions should be performed by the "root" user.
Make sure the "/etc/hosts" file contains correct entries for both the "localhost" and real host names.
[oracle@weblogic1 oracle]$ cat /etc/hosts
# that require network functionality will fail.
127.0.0.1               localhost.localdomain   localhost
192.168.88.133  weblogic1.muthu.com     weblogic1
192.168.88.134  weblogic2.muthu.com     weblogic2
[oracle@weblogic1 oracle]$
Create the directories in which the Oracle software will be installed.
[root@weblogic1 ~]# mkdir /oracle
[root@weblogic1 ~]# oracle:oinstall /oracle
[root@weblogic1 ~]# chmod -R 775 /oracle

Install the JRockit

Installation

Run the installer as the "oracle" user.

[oracle@weblogic1 oracle]$ java -d64 -jar wls1034_generic.jar

Enter the middleware home ("/oracle/Middleware") and click the "Next" button.

 

 Either enter your support details, or attempt to uncheck the security updates checkbox. The box doesn't actually uncheck, but presents you with a warning dialog. If you click the "Yes" button, indicating you don't want updates, you are returned to the same screen with the box still checked. Click the "Next" button anyway.

Accept the Custom setup by clicking the "Next" button

Uncheck the Oracle Coherence Accept the default selection by clicking the "Next" button.

Accept the default JDK selection by clicking the "Next" button.

Accept the default product installation directories by clicking the "Next" button.

If you are happy with the summary information, click the "Next" button and wait while the installation completes.

On the installation complete screen, uncheck the "Quickstart" checkbox and click the "Done" button.

 

Login to node 2 copy middleware binaries from Node 1 to Node2
[oracle@weblogic2]$ scp –pr oracle@weblogic1:/oracle/Midd* .
Once the installation is complete on both machines, come back to this article to create the clustered domain.
Creation of a clustered domain can be done from the administration console, the command line or the configuration wizard. In my opinion, using the configuration wizard is the quickest way to get the job done. Start the configuration wizard.
[oracle@weblogic1 bin]$  sh /oracle/Middleware/wlserver_10.3/common/bin/config.sh

 Accept the "Create a new WebLogic domain" option by clicking the "Next" button.

 Select the desired product support and click the "Next" button.

Enter the appropriate domain name and locations, then click the "Next" button.

Enter the administrator credentials and click the "Next" button.

Select the desired server start mode and JDK, then click the "Next" button.

Select the "Administration Server" and "Managed Servers, Clusters and Machines" options, then click the "Next" button.

Enter the fully qualified machine name, desired port and SSL configuration, then click the "Next" button.

Add the managed servers for the domain. When you are finished, click the "Next" button.

Add a cluster entry, remember to add the appropriate cluster address. This can be a comma-separated list of "IP/DNS_Name:port", a DNS name that maps to multiple IP addresses or the local machine if all servers run on one machine. Click the "Next" button.

Associate the managed servers with the cluster and click the "Next" button.

Click the "Machine" tab and add the machines used by the cluster. Click the "Next" button.

Assign the managed servers to the machines in the cluster and click the "Next" button.

Check the configuration summary, the click the "Create" button.

Wait while the domain is created, then click the "Done" button.

Start the node manager and Domain on First Node

[oracle@weblogic1 ]$ nohup $WL_HOME/server/bin/startNodeManager.sh &

Consider setting some of the node manager properties on both servers in the "$WL_HOME/common/nodemanager/nodemanager.properties" file. For example.
 [oracle@weblogic1 nodemanager]$ vi /oracle/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties
StopScriptEnabled=true
CrashRecoveryEnabled=true
StartScriptEnabled=true
SecureListener=false
################### Node -2 ####################################
[oracle@weblogic2 bin]$ sh setWLSEnv.sh
 [oracle@weblogic2 nodemanager]$ vi /oracle/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties
StopScriptEnabled=true
CrashRecoveryEnabled=true
StartScriptEnabled=true
SecureListener=false
################# Node -1 ##########################
Start the new domain on the first machine.

[oracle@weblogic1 ]$ nohup /oracle/Middleware/user_projects/domains/muthu_domain/startWebLogic.sh &

Create a Boot Identity File

[oracle@weblogic1 AdminServer]$ mkdir -p /oracle/Middleware/user_projects/domains/muthu_domain/servers/AdminServer/security
 [oracle@weblogic1 ]$ vi /oracle/Middleware/user_projects/domains/muthu_domain/servers/AdminServer/security /boot.properties
username=weblogic
password=password
[oracle@weblogic1 muthu_domain]$ nohup /oracle/Middleware/user_projects/domains/muthu_domain/startWebLogic.sh &
Stop Adminserver and Node manager
Transfer Domain to Second Machine
[oracle@weblogic1 oracle]$ export DOMAIN_HOME=/oracle/Middleware/user_projects/domains/muthu_domain
[oracle@weblogic1 oracle]$ cd $WL_HOME/common/bin/
[oracle@weblogic1 bin]$ sh pack.sh -managed=true -domain=$DOMAIN_HOME -template=/oracle/weblogic1.jar -template_name=muthu_domain
<< read domain from "/oracle/Middleware/user_projects/domains/muthu_domain"
>>  succeed: read domain from "/oracle/Middleware/user_projects/domains/muthu_domain"
<< set config option Managed to "true"
>>  succeed: set config option Managed to "true"
<< write template to "/oracle/weblogic1.jar"
....................................................................................................
>>  succeed: write template to "/oracle/weblogic1.jar"
<< close template
>>  succeed: close template
[oracle@weblogic1 bin]$
Copy the resulting jar file to the second machine.
[oracle@weblogic2 oracle]$ scp -pr oracle@weblogic1:/oracle/weblo* .
oracle@weblogic1's password:
weblogic1.jar                                 100%   43KB  43.0KB/s   00:00
[oracle@weblogic2 oracle]$
Unpack the configuration on the second machine. Remember to amend the DOMAIN_HOME environment variable to match your domain
[oracle@weblogic2 oracle]$ mkdir -p /oracle/Middleware/user_projects/domains/muthu_domain
[oracle@weblogic2 ~]$ export DOMAIN_HOME=/oracle/Middleware/user_projects/domains/muthu_domain
[oracle@weblogic2 ~]$ cd /oracle/Middleware/wlserver_10.3/common/bin/
 [oracle@weblogic2 bin]$ sh unpack.sh -domain=$DOMAIN_HOME -template=/oracle/weblogic1.jar
<< read template from "/oracle/weblogic1.jar"
>>  succeed: read template from "/oracle/weblogic1.jar"
<< set config option DomainName to "muthu_domain"
>>  succeed: set config option DomainName to "muthu_domain"
<< write Domain to "/oracle/Middleware/user_projects/domains/muthu_domain"
...............................................................................................
>>  succeed: write Domain to "/oracle/Middleware/user_projects/domains/muthu_domain"
<< close template
>>  succeed: close template
[oracle@weblogic2 bin]$
Restart the domain on the first machine. Wait until it is fully started before continuing.
[oracle@weblogic1 logs]$ nohup /oracle/Middleware/user_projects/domains/muthu_domain/startWebLogic.sh &
Enroll Second Machine
On the second machine, start WLST.
[oracle@weblogic2 bin]$ . $WL_HOME/common/bin/commEnv.sh
[oracle@weblogic2 bin]$ sh $WL_HOME/common/bin/wlst.sh
CLASSPATH=/oracle/Middleware/patch_wls1034/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/java/lib/tools.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/modules/features/weblogic.server.modules_10.3.4.0.jar:/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:
PATH=/oracle/Middleware/wlserver_10.3/server/bin:/oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/oracle/java/jre/bin:/oracle/java/bin:/oracle/Middleware/wlserver_10.3/server/bin:/oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/oracle/java/jre/bin:/oracle/java/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/oracle/bin
Your environment has been set.
CLASSPATH=/oracle/Middleware/patch_wls1034/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/java/lib/tools.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/modules/features/weblogic.server.modules_10.3.4.0.jar:/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/oracle/Middleware/utils/config/10.3/config-launch.jar::/oracle/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/oracle/Middleware/wlserver_10.3/common/derby/lib/derbytools.jar::
Initializing WebLogic Scripting Tool (WLST) ...
Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> connect ('weblogic','welcome123','t3://weblogic1.muthu.com:7001')
Connecting to t3://weblogic1.muthu.com:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'muthu_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/muthu_domain/serverConfig> nmEnroll('/oracle/Middleware/user_projects/domains/muthu_domain','/oracle/Middleware/wlserver_10.3/common/nodemanager')
Enrolling this machine with the domain directory at /oracle/Middleware/user_projects/domains/muthu_domain ...
Successfully enrolled this machine with the domain directory at /oracle/Middleware/user_projects/domains/muthu_domain.
wls:/muthu_domain/serverConfig> disconnect()
Disconnected from weblogic server: AdminServer
wls:/offline> exit()
Exiting WebLogic Scripting Tool.
[oracle@weblogic2 bin]$
Check the "$MW_HOME/domain-registry.xml" file contains an entry like the following. If it doesn't, add it manually.

[oracle@weblogic2 Middleware]$ vi /oracle/Middleware/domain-registry.xml
  <domain location="/oracle/Middleware/user_projects/domains/muthu_domain"/>
 Check the "$WL_HOME/common/nodemanager/nodemanager.domains" file contains an entry like the following. If it doesn't, add it manually.
[oracle@weblogic2 nodemanager]$ vi $WL_HOME/common/nodemanager/nodemanager.domains
muthu_domain=/oracle/Middleware/user_projects/domains/muthu_domain
[oracle@weblogic1 nodemanager]$ vi /oracle/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties
StopScriptEnabled=true
CrashRecoveryEnabled=true
StartScriptEnabled=true
SecureListener=false
If the node manager is not already started on this server, start it now.
[oracle@weblogic2 bin]$ nohup $WL_HOME/server/bin/startNodeManager.sh &
Check Node Manager on Each Machine
Check the node manager is reachable on each machine.
    Log in to the administration server (http://weblogic1.muthu.com:7001/console).
    In the "Domain Structure" tree, expand the "Environment" node and click on the "Machines" node.
    In the right-hand pane, click on the first machine (weblogic1).
    Click on the "Monitoring" tab. Be patient. This may take a little time the first time you do it.
    If the status is "Reachable", everything is fine.
    Repeat for the second machines (weblogic2).
Start Up
Provided the node manager is up on all servers, you can now start/stop the managed servers on both machines from the command line. The following example shows how you might do this.
$ # Start the services on each server.
[oracle@weblogic1 bin]$  nohup $WL_HOME/server/bin/startNodeManager.sh > /dev/null 2>&1 &
# Start the managed servers from any server.
 [oracle@weblogic1 bin]$ nohup /oracle/Middleware/user_projects/domains/muthu_domain/startWebLogic.sh > /dev/null 2>&1 &
[oracle@weblogic1 bin]$ nohup /oracle/Middleware/user_projects/domains/muthu_domain/bin/startManagedWebLogic.sh ms1_cluster > /dev/null 2>&1 &
[oracle@weblogic1 bin]$ nohup /oracle/Middleware/user_projects/domains/muthu_domain/bin/startManagedWebLogic.sh ms2_cluster > /dev/null 2>&1  &

Database platform migration from Windows-64bit to Linux-64bit

Step by step oracle database platform migration from Windows-64bit to Linux-64bit :

To convert the database from one platform to another, the endian format of both databases should be the same.  So as a first step, check the v$transportable_platform view for both platforms.

SQL> select a.VERSION,a.INSTANCE_NAME,b.PLATFORM_NAME from v$instance a, v$database b;

VERSION           INSTANCE_NAME    PLATFORM_NAME
----------------- ---------------- --------------------------------

11.2.0.1.0        prod             Microsoft Windows x86 64-bit

SQL> select platform_name from v$db_transportable_platform;

PLATFORM_NAME
-------------------------------------
Microsoft Windows IA (32-bit)
Linux IA (32-bit)
HP Tru64 UNIX
Linux IA (64-bit)
HP Open VMS
Microsoft Windows IA (64-bit)
Linux x86 64-bit
Microsoft Windows x86 64-bit
Solaris Operating System (x86)
HP IA Open VMS
Solaris Operating System (x86-64)

11 rows selected.

It is seen from the output that both the Windows and Linux operating systems are in the little endian format.  So in this case, RMANcan be easily used to convert the whole database.

start database with mount stage and open database with the read only option
----------------------------------------------------------------------------

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area  855982080 bytes
Fixed Size                  2180544 bytes
Variable Size             515902016 bytes
Database Buffers          331350016 bytes
Redo Buffers                6549504 bytes
Database mounted.
SQL> alter database open read only;

Database altered.

Use dbms_tdb.check_db function to check whether the database can be transported to a target platform and the dbms_tdb.check_external function to check for existence of external objects, directories and BFILEs.  Pass the name of the destination platform as a parameter to the first function.  The return type of the function is boolean, so declare a variable with boolean type and call the function as follows:

SQL> set serveroutput on
SQL> declare
  2  v_return boolean;
  3  begin
  4  v_return:=dbms_tdb.check_db('Linux x86 64-bit');
  5  end;
  6  /

PL/SQL procedure successfully completed.

If nothing was returned, then it means that the database is ready to be transported to the destination platform.
----------------------------------------------------------------------------------------------------------------
Now call the second function dbms_tdb.check_external:

SQL> declare
  2  v_return boolean;
  3  begin
  4  v_return:=dbms_tdb.check_external;
  5  end;
  6  /
The following external tables exist in the database:
SH.SALES_TRANSACTIONS_EXT
The following directories exist in the database:
SYS.ORACLE_OCM_CONFIG_DIR, SYS.DATA_PUMP_DIR, SYS.XMLDIR, SYS.DATA_FILE_DIR,
SYS.LOG_FILE_DIR, SYS.MEDIA_DIR, SYS.SS_OE_XMLDIR, SYS.SUBDIR
The following BFILEs exist in the database:
PM.PRINT_MEDIA

PL/SQL procedure successfully completed.

SQL>

Run the convert database command to convert the whole database to the Linux platform.
------------------------------------------------------------------------------------

C:\Users\muthu>rman target /

Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jul 21 18:40:46 2015

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PROD (DBID=297504150)

RMAN> convert database new database 'PRODNEW'
2> transport script 'c:\app\transport.sql'
3> db_file_name_convert 'C:\app\oradata\prod'
4> 'c:\app'
5> to platform 'Linux x86 64-bit';

Starting conversion at source at 21-JUL-15
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=14 device type=DISK

External table SH.SALES_TRANSACTIONS_EXT found in the database

Directory SYS.ORACLE_OCM_CONFIG_DIR found in the database
Directory SYS.DATA_PUMP_DIR found in the database
Directory SYS.XMLDIR found in the database
Directory SYS.DATA_FILE_DIR found in the database
Directory SYS.LOG_FILE_DIR found in the database
Directory SYS.MEDIA_DIR found in the database
Directory SYS.SS_OE_XMLDIR found in the database
Directory SYS.SUBDIR found in the database

BFILE PM.PRINT_MEDIA found in the database

User SYS with SYSDBA and SYSOPER privilege found in password file
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00001 name=C:\APP\ORADATA\PROD\SYSTEM01.DBF
converted datafile=C:\APP\SYSTEM01.DBF
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00002 name=C:\APP\ORADATA\PROD\SYSAUX01.DBF
converted datafile=C:\APP\SYSAUX01.DBF
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00003 name=C:\APP\ORADATA\PROD\UNDOTBS01.DBF
converted datafile=C:\APP\UNDOTBS01.DBF
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00005 name=C:\APP\ORADATA\PROD\EXAMPLE01.DBF
converted datafile=C:\APP\EXAMPLE01.DBF
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00004 name=C:\APP\ORADATA\PROD\USERS01.DBF
converted datafile=C:\APP\USERS01.DBF
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:00:01
Edit init.ora file C:\APP\PRODUCT\11.2.0\DBHOME_1\DATABASE\INIT_00QCKDEH_1_0.ORA. This PFILE will be used to create the database on the
target platform
Run SQL script C:\APP\TRANSPORT.SQL on the target platform to create database
To recompile all PL/SQL modules, run utlirp.sql and utlrp.sql on the target platform
To change the internal database identifier, use DBNEWID Utility
Finished conversion at source at 21-JUL-15

RMAN> exit

While performing the convert database command, RMAN does not convert and transfer redo log files, controlfiles, password files and temporary tablespaces to the destination platform.

RMAN converted all datafiles to the destination platform type.  Now copy the parameter file transport.sql script, which is located at the $ORACLE_HOME/dbs directory, that is used to create the database and all datafiles to the destination host.

Perform the following prerequisite actions on the destination host before running the transport.sql.
----------------------------------------------------------------------------------------------------

[root@prodnew /]# mkdir oracle
[root@prodnew /]# chown -R oracle:oinstall oracle/
[root@prodnew /]# chmod -R 755 oracle/
[root@prodnew /]# su - oracle
[oracle@prodnew ~]$ mkdir -p /oracle/product/11.2.0/admin
[oracle@prodnew ~]$ mkdir -p /oracle/product/11.2.0/admin/adump
[oracle@prodnew ~]$ cd /oracle/product/11.2.0/dbs/
[oracle@prodnew ~]$ cp -r /oracle/*.DBF /oracle/product/oradata/

Move all datafiles to the necessary folder. Edit parameter file and convert paths from Windows syntax to the Linux syntax:
---------------------------------------------------------------------------------------------------------------------------
diagnostic_dest=/oracle/product/11.2.0/admin
control_files=("/oracle/product/oradata/control01.ctl", "/oracle/product/oradata/control02.ctl")
db_recovery_file_dest=/oracle/product/11.2.0
audit_file_dest=/oracle/product/11.2.0/admin/adump
local_listener=LISTENER_PROD

[oracle@prodnew dbs]$ vi initPRODNEW.ora  ----- Copy init file from Windows to linux then change the parameter
[oracle@prodnew dbs]$ cd ../network/admin/
[oracle@prodnew admin]$ vi listener.ora   ----  Copy listner file Windows to linux then change the parameter
[oracle@prodnew admin]$ vi tnsnames.ora   ----  Copy tnsname file Windows to linux then change the parameter
[oracle@prodnew admin]$ lsnrctl start

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 22-JUL-2015 00:20:35

Copyright (c) 1991, 2009, Oracle.  All rights reserved.

Starting /oracle/product/11.2.0/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 11.2.0.1.0 - Production
System parameter file is /oracle/product/11.2.0/network/admin/listener.ora
Log messages written to /oracle/product/11.2.0/admin/diag/tnslsnr/prodnew/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=prodnew.muthu.com)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                22-JUL-2015 00:20:36
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /oracle/product/11.2.0/network/admin/listener.ora
Listener Log File         /oracle/product/11.2.0/admin/diag/tnslsnr/prodnew/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=prodnew.muthu.com)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@prodnew admin]$ tnsping PRODNEW

TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 22-JUL-2015 00:20:39

Copyright (c) 1997, 2009, Oracle.  All rights reserved.

Used parameter files:


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = PRODNEW.muthu.com)))
OK (50 msec)

Edit transport.sql script and correct paths of datafiles, controlfiles and trace directories.
---------------------------------------------------------------------------------------------

CREATE CONTROLFILE SET DATABASE "PRODNEW" RESETLOGS  NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
LOGFILE
  GROUP 1 '/oracle/product/oradata/REDO01.LOG'  SIZE 50M BLOCKSIZE 512,
  GROUP 2 '/oracle/product/oradata/REDO02.LOG'  SIZE 50M BLOCKSIZE 512,
  GROUP 3 '/oracle/product/oradata/REDO03.LOG'  SIZE 50M BLOCKSIZE 512
DATAFILE
  '/oracle/product/oradata/SYSTEM01.DBF',
  '/oracle/product/oradata/SYSAUX01.DBF',
  '/oracle/product/oradata/UNDOTBS01.DBF',
  '/oracle/product/oradata/USERS01.DBF',
  '/oracle/product/oradata/EXAMPLE01.DBF'
CHARACTER SET AL32UTF8
;

Now check all changes made above once more, export the ORACLE_SID environment variable and run the transport.sql command from SQL*Plus:
---------------------------------------------------------------------------------------------------------------------------------------

[oracle@prodnew dbs]$ export ORACLE_HOME=/oracle/product/11.2.0
[oracle@prodnew dbs]$ export ORACLE_SID=PRODNEW
[oracle@prodnew dbs]$ export PATH=/oracle/product/11.2.0/bin:$PATH
[oracle@prodnew dbs]$ sqlplus "/as sysdba"

SQL*Plus: Release 11.2.0.1.0 Production on Wed Jul 22 00:21:17 2015

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup nomount
ORACLE instance started.

Total System Global Area  855982080 bytes
Fixed Size                  2218152 bytes
Variable Size             503318360 bytes
Database Buffers          343932928 bytes
Redo Buffers                6512640 bytes
SQL> CREATE CONTROLFILE SET DATABASE "PRODNEW" RESETLOGS  NOARCHIVELOG
    MAXLOGFILES 16
  2    3      MAXLOGMEMBERS 3
  4      MAXDATAFILES 100
  5      MAXINSTANCES 8
  6      MAXLOGHISTORY 292
  7  LOGFILE
  GROUP 1 '/oracle/product/oradata/REDO01.LOG'  SIZE 50M BLOCKSIZE 512,
  8    9    GROUP 2 '/oracle/product/oradata/REDO02.LOG'  SIZE 50M BLOCKSIZE 512,
  GROUP 3 '/oracle/product/oradata/REDO03.LOG'  SIZE 50M BLOCKSIZE 512
 10   11  DATAFILE
 12    '/oracle/product/oradata/SYSTEM01.DBF',
 13    '/oracle/product/oradata/SYSAUX01.DBF',
 14    '/oracle/product/oradata/UNDOTBS01.DBF',
  '/oracle/product/oradata/USERS01.DBF',
 15   16    '/oracle/product/oradata/EXAMPLE01.DBF'
CHARACTER SET AL32UTF8
 17   18  ;

Control file created.

SQL> alter database open resetlogs;

Database altered.

SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/product/oradata/temp01.dbf' size 500M;

Tablespace altered.

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup upgrade
ORACLE instance started.

Total System Global Area  855982080 bytes
Fixed Size                  2218152 bytes
Variable Size             503318360 bytes
Database Buffers          343932928 bytes
Redo Buffers                6512640 bytes
Database mounted.
Database opened.
SQL> @@ ?/rdbms/admin/utlirp.sql

-- The following step will recompile all PL/SQL modules.
-- It may take serveral hours to complete.

DOC>#######################################################################
DOC>#######################################################################
DOC>   utlirp.sql completed successfully. All PL/SQL objects in the
DOC>   database have been invalidated.
DOC>
DOC>   Shut down and restart the database in normal mode and run utlrp.sql to
DOC>   recompile invalid objects.
DOC>#######################################################################
DOC>#######################################################################
DOC>#

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area  855982080 bytes
Fixed Size                  2218152 bytes
Variable Size             503318360 bytes
Database Buffers          343932928 bytes
Redo Buffers                6512640 bytes
Database mounted.
Database opened.
SQL> @ ?/rdbms/admin/utlrp.sql

SQL> select a.VERSION,a.INSTANCE_NAME,b.PLATFORM_NAME from v$instance a, v$database b;

VERSION           INSTANCE_NAME    PLATFORM_NAME
----------------- ---------------- -------------------
11.2.0.1.0        PRODNEW          Linux x86 64-bit

SQL>