Wednesday, 14 January 2015

Scheduling concurrent program in Oracle Apps R12

How to scheduling concurrent program in Oracle AppsR12.

Many times you may want to run a concurrent program at a specific time on some specific days of a week. Remembering the schedule and submitting the programs manually may not be feasible all the times. Oracle E- Business suite conveniently let’s you schedule a program to run on a specified time and date. When you schedule, the program will automatically be kicked off at the specified time.
Now let us see how we schedule a concurrent program in Oracle Apps.

1. Go to the respective responsibility where the concurrent program to be scheduled exists. Then go to View > Requests and click on “Submit a New Request”


2. Select “Single Request” and click on OK button


3. Enter the concurrent program name to be scheduled and the respective parameters and click on Schedule button.

 4. This will open up the Schedule window.


5. Schedule options: The below are the available scheduling options, we will see what they mean.

(i) As Soon as Possible: Selecting this option will kick off the concurrent program immediately.

(ii) Once: Selecting this option lets you specify at what time and date you want to kick off the concurrent program. The concurrent program will be submitted only once at the specified time and date.


(iii) Periodically: Lets you schedule the program at the specified interval like once a month/week/day/hour/minute.


Description of the fields and their importance:

Start At: Enter the date and time when you want to start the schedule

End At: Enter the end date for the schedule. Leaving this blank will run indefinitely.

Re-run every: Specify the interval you want to run like for example – every 1 day or every 2 months.

Apply the interval: How do you want to apply the interval from the start of the prior run or from the completion of the prior run.

Increment date parameters each run: Use this when one of the parameters for your program is a date.
If you check this, the date parameter will be incremented for each run.
If not checked, the date given in the parameter will not increment, it will remain the same as entered while scheduling for every run.

Apply a Saved Schedule: If more than one program has to be scheduled in a similar fashion, instead of entering the schedule details for each and every program, you can save the schedule and apply the same schedule for the remaining programs.

(iv) On Specific Days: Use this if you want to run the program for example on 5th day of every month or on Tuesday of every week,. This option lets you choose on what days of every month you want to run a program.


6. Once you specify the interval/frequency you want the program to run, click on OK button. (I have set it to run once a day at 2:00 P.M starting from 23-Feb-2014 till 26-Feb-2014 as seen in the below screenshot)


7. Click on Submit button.

 8. Upon querying for the request in the requests window, you see our program with status scheduled. When it’s time, the program will be executed.

This is how you schedule a program to run at a specified frequency or interval.

9. At any point of time, if you need to change the schedule, you can select the scheduled request and click on View Details button.

Then click on Schedule button. Here you can change the schedule as per your wish.


10. If you wish to cancel a scheduled request, select the request in the Requests window and click on Cancel Request in Requests window.

This will prevent the program from running. If you see the below screenshot, status is cancelled.

Create New User In Oracle ERP R12

Create a New User

Responsibility: System Administrator
Navigation: Security > User > Define

Enter user name > sujeet_jha
password > ****** enter again same password ***** white color appear..
person >company information,mail id,
Effective Date >
from= Active date by default, 
To= Expire date if u want that select expire date also.

Responsibility > system Administrator

 save it...

Monday, 5 January 2015

Nautilus cannot display ntfs External hard drive

Error:-Nautilus cannot display "/mnt/NTFS1

I am trying to mount 2TB External Hard-disk on Linux.

Steps Follow:-

[root@sujeet~]# mkdir -p /mnt/ntfs1

[root@sujeet ~]# fdisk -l |grep NTFS

/dev/sdb1 1 243198 1953480704 7 HPFS/NTFS

[root@sujeet ~]# mount -t ntfs-3g /dev/sdb1 /mnt/ntfs1/
[root@sujeet ~]# mount -t ntfs-3g /dev/sdb1 /mnt/ntfs1/ -o force
[root@sujeet ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 30G 990M 27G 4% /
/dev/sda11 6.8G 404M 6.1G 7% /var
/dev/sda10 6.8G 147M 6.3G 3% /tmp
/dev/sda9 6.8G 144M 6.3G 3% /opt
/dev/sda8 6.8G 145M 6.3G 3% /home
/dev/sda7 20G 4.7G 14G 26% /usr
/dev/sda15 3.9G 73M 3.7G 2% /usr/local
/dev/sda6 2.9G 0 2.9G 0% /dev/shm
/dev/sda3 175G 32G 135G 19% /u02
/dev/sda2 611G 405G 175G 70% /u01
/dev/sda1 996M 74M 871M 8% /boot
tmpfs 2.9G 0 2.9G 0% /dev/shm
df: `/mnt/ntfs1': Resource temporarily unavailable <ERROR>

RPM install on system as per requirement:-

[root@sujeet ~]# rpm -qa |grep fuse*

[root@sujeet ~]# /sbin/service nfs restart
Shutting down NFS mountd:                                  [FAILED]
Shutting down NFS daemon:                                  [FAILED]
Shutting down NFS quotas:                                  [FAILED]
Starting NFS services:                                     [  OK  ]
Starting NFS quotas:                                       [  OK  ]
Starting NFS daemon:                                       [  OK  ]
Starting NFS mountd:                                       [  OK  ]

Every thing fine for my side but still facing issue.. Hard drive mount in Read only mode...

Solution :-

Need to change Hard drive file system NTFS to EXT3.

Linux Hard Disk Format Command

How do I format a hard disk under Linux operating system from a shell prompt?

Format External Hard drive NTFS to EXT3 file system through Linux command.

[root@sujeet ~]# fdisk -l|grep NTFS

/dev/sdb1               1      243198  1953480704    7  HPFS/NTFS
/dev/sdc1               1      243198  1953480704    7  HPFS/NTFS <My External Hard drive>

[root@sujeet ~]# mkfs.ext3 /dev/sdc1
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
244187136 inodes, 488370176 blocks
24418508 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
14904 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848

Writing inode tables: done                           
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 32 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[root@sujeet ~]#

[root@sujeet ~]# mkdir /disk1

[root@sujeet /]# mount  /dev/sdc1   /disk1

/]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5              30G  999M   27G   4% /
/dev/sda11            6.8G  412M  6.1G   7% /var
/dev/sda10            6.8G  144M  6.3G   3% /tmp
/dev/sda9             6.8G  144M  6.3G   3% /opt
/dev/sda8             6.8G  145M  6.3G   3% /home
/dev/sda7              20G  4.7G   14G  26% /usr
/dev/sda15            3.9G   73M  3.7G   2% /usr/local
/dev/sda6             2.9G     0  2.9G   0% /dev/shm
/dev/sda3             175G   32G  135G  19% /u02
/dev/sda2             611G  405G  175G  70% /u01
/dev/sda1             996M   74M  871M   8% /boot
tmpfs                 2.9G     0  2.9G   0% /dev/shm
/dev/sdb1             1.8T  1.4T  309G  83% /media/disk
/dev/sdc1             1.8T  196M  1.7T   1% /disk1 <External Hard-drive>

If you unmount /dev/sdc1 after that again try to mount than got error.

Edit the /etc/fstab file and add an entry for the new drive. For my example,

[root@sujeet~]# vi /etc/fstab

/dev/sdc1   /disk1     ext3    defaults        1 1

save it.

[root@sujeet ~]# mount /disk1


Saturday, 3 January 2015

chkdsk command

How to Check Disk from the Command Line to Find and Fix Errors?

You can run Check Disk from the command line or within other utilities. At a command prompt, you can test the integrity of the G drive by typing the following command: 

chkdsk G:

To find and repair errors that are found in the G drive, use the following command:

chkdsk /f G: 

Note that Check Disk can’t repair volumes that are in use. If the volume is in use, Check Disk displays a prompt that asks if you want to schedule the volume to be checked the next time you restart the system. Click Yes to schedule this.

The complete syntax for Check Disk is this:

chkdsk [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] 

The options and switches for Check Disk are used as follows:
Volume Sets the volume to work with.
filename FAT/FAT32 only: Specifies files to check for fragmentation.
/F Fixes errors on the disk.
/V On FAT/FAT32, this displays the full path and name of every file on the disk. On NTFS, this displays cleanup messages, if any.
/R Locates bad sectors and recovers readable information (implies /F).
/L:size NTFS only. Changes the log file size.
/X Forces the volume to dismount first if necessary (implies /F).
/I NTFS only. Performs a minimum check of index entries.
/C NTFS only. Skips checking of cycles within the folder structure.

Starting and Stopping NFS

Starting and Stopping NFS

To run an NFS server, the portmap service must be running. To verify that portmap is
active, type the following command as root:

[root@sujeet ~]# /sbin/service portmap status

If the portmap service is running, then the nfs service can be started.
To start an NFS server, as root type:

[root@sujeet ~]# /sbin/service nfs start

To stop the server, as root type:

[root@sujeet ~]# /sbin/service nfs stop

The restart option is a shorthand way of stopping and then starting NFS.
This is the most efficient way to make configuration changes take effect after
editing the configuration file for NFS.

To restart the server, as root type:

[root@sujeet ~]# /sbin/service nfs restart

The condrestart (conditional restart) option only starts nfs if it is currently running.
 This option is useful for scripts, because it does not start the daemon if it is not

To conditionally restart the server, as root type:
[root@sujeet ~]# /sbin/service nfs condrestart

To reload the NFS server configuration file without restarting the service,
 as root type

[root@sujeet ~]# /sbin/service nfs reload

By default, the nfs service does not start automatically at boot time.
To configure the NFS to start up at boot time, use an initscript utility,

such as /sbin/chkconfig, /sbin/ntsysv, or the Services Configuration Tool program.

How To Restart Linux NFS Server

[root@sujeet ~]# service nfslock stop
Stopping NFS locking:                                      [  OK  ]
Stopping NFS statd:                                        [  OK  ]

[root@sujeet ~]# service nfs stop
Shutting down NFS mountd:                                  [  OK  ]
Shutting down NFS daemon:                                  [  OK  ]
Shutting down NFS quotas:                                  [  OK  ]

[root@sujeet ~]# service portmap stop
Stopping portmap:                                          [  OK  ]

[root@sujeet ~]# umount /proc/fs/nfsd

[root@sujeet ~]#service portmap start
Starting portmap:                                          [  OK  ]

[root@sujeet ~]# service nfs start
Starting NFS services:                                     [  OK  ]
Starting NFS quotas:                                       [  OK  ]
Starting NFS daemon:                                       [  OK  ]
Starting NFS mountd:                                       [  OK  ]

[root@sujeet ~]# service nfslock start
Starting NFS statd:                                        [  OK  ]

[root@sujeet ~]# mount -t nfsd nfsd /proc/fs/nfsd

Automatically Start the NFS Server

To start the NFS service automatically at the boot time, enter:
# ntsysv

Start / Stop / Restart portmap Service under RHEL

Type the following commands:
[root@sujeet ~]# /etc/init.d/portmap stop
Stopping portmap:                                          [  OK  ]

[root@sujeet ~]#/etc/init.d/portmap start
Starting portmap:                                          [  OK  ]

[root@sujeet ~]# /etc/init.d/portmap restart
Stopping portmap:                                          [  OK  ]
Starting portmap:                                          [  OK  ]

Start / Stop / Restart NFS Service under RHEL / CentOS Linux

[root@sujeet ~]# /etc/init.d/nfs start
[root@sujeet ~]# /etc/init.d/nfs stop
[root@sujeet ~]# /etc/init.d/nfs restart

Friday, 2 January 2015

Oracle database upgrade to 12.1.0

Upgrade Path for Oracle Database to Oracle 12c Release 1 (12.1)

Minimum version of the database that can be directly upgraded to Oracle 12c Release 1 (12.1)

Source DatabaseTarget Database 12.1.x 12.1.x or higher 12.1.x

The following database versions will require an indirect upgrade path:

Source DatabaseIntermediate Upgrade Path for Target DatabaseTarget Database ----> or higher ----> 12.1.x ----> or or higher ----> 12.1.x (or earlier) ----> or later direct upgrade version ----> 12.1.x (or earlier) ----> or later direct upgrade version ----> 12.1.x (or earlier) ----> --> or higher ----> 12.1.x

 For example:
  •  If you are upgrading from or, then you must first upgrade to Oracle Database 11g Release 2 (
  •  If you are upgrading from,,, or, then you must first upgrade to or later.
  •  For release, you must first upgrade to an intermediate Oracle Database release, as follows: -> or -> 12.1
To locate the patch-id of a patch-set refer to:
Note 438049.1 : How To Find RDBMS patchsets on My Oracle Support
Note 753736.1 : Quick Reference to Patchset Patch Numbers

Upgrading Oracle Database to 12.1.0 steps


There are different ways of upgrading to the latest release of Oracle database and Oracle provides multiple methods to upgrade. Few are listed below:
  • Database Upgrade Assistant (DBUA)
  • Manual Upgrade
  • Transportable Tablespaces
  • Datapump export/import
  • Oracle Streams
  • Oracle GoldenGate
I chose DBUA to upgrade my test database as it was the simplest and quickest of all. Below are the database environment details prior to upgrade:


 Server details below

OS : OEL 5.4 (64 bit)
Database : (64 bit)

Note:- Before starting the up-gradation process, take the complete backup of database.

1)Take cold backup of database
[oracle@sujeet ~]$ cd $ORACLE_BASE
[oracle@sujeet oracle]$ ls
admin cfgtoollogs checkpoints diag fast_recovery_area oradata product
[oracle@sujeet oracle]$ cd oradata/

[oracle@sujeet oradata]$ ls
[oracle@sujeet oradata]$ cd PROD/

[oracle@sujeet PROD]$ ls
control01.ctl redo01.log redo03.log system01.dbf undotbs01.dbf
example01.dbf redo02.log sysaux01.dbf temp01.dbf users01.dbf

[oracle@sujeet PROD]$ cd ..
[oracle@sujeet oradata]$ ls
[oracle@sujeet oradata]$ cp -R PROD/ PROD_backup

2) Stop the Listener
[oracle@sujeet admin]$ lsnrctl stop PROD
LSNRCTL for Linux: Version – Production on 04-DEC-2014 11:32:26 Copyright (c) 1991, 2014, Oracle. All rights reserved.

The command completed successfully

3) Create directory structure for 12c ORACLE_HOME
[oracle@sujeet product]$ mkdir -p /u01/app/oracle/product/12.1.0

4) export ORACLE_HOME to 12c
[oracle@sujeet 12.1.0]$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0

5) Copy ( winscp or scp ) 12c software to /home/oracle

6) Launch Oracle 12c runinstaller
[oracle@sujeet database]$ pwd

Note: open new terminal & run xhost + command as a root user before running ./runInstaller 

[oracle@sujeet database]$ ./runInstaller

Un-check “I Wish to receive security updates via My oracle support” and click Next

Click Yes
Select “Skip Software Updates” and click Next.

select “Upgrade an existing database” and click Next

select “Upgrade an existing database” and click Next

Select your language and click Next

Select “Enterprise Edition” and click Next

Fill the details for ORACLE_BASE and software location and click Next

Select the OSOPER grouop (Optional) and click Next

If you satisfy with the summary click Next

 Now Oracle Database 12c installation starts

Run the scripts as root user
[root@sujeet ~]# /u01/app/oracle/product/12.1.0/
Performing root user operation for Oracle 12c
The following environment variables are set as:
ORACLE_HOME= /u01/app/oracle/product/12.1.0
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file “dbhome” already exists in /usr/local/bin. Overwrite it? (y/n)
The file “oraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
The file “coraenv” already exists in /usr/local/bin. Overwrite it? (y/n)
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.

Now product-specific root actions will be performed.

Click OK after completion of running that script.

 [root@sujeet ~]# netca

 Click next
Fill the Listener Name and click Next

 Click Next

Select the port number and click Next

Select No and click Next

 click next

 Click Finish

Now start DBUA (Database Upgrade Assistant)

Select “Upgrade Oracle Database” and click Next

Click Next

 click on that “Pre Upgrade Utility Checks” – severiy

You might see this error, safely ignore this error because this is a test machine.

 Choose Ignore from Action menu and click Next

 Check the file locations and click Next

Select “Configure Enterprise Manager (EM) Database Express and click Next


 Click Next

Select listener and click Next

Choose ” I have my own backup and restore strategy” and click Next

Click Finish

Oracle Database upgrade in progress,
Pre-Upgrade steps will complete in seconds but Database Upgrades Steps takes at-least 90 min of time based on your machine performance and post upgrade steps will take just 5 mins.

After finishing all up-gradation steps click on “Upgrade Results”

click “close”


After successfully completion of upgradation click “close”

 Oracle Database upgradation from 11g to 12c completed successfully.

Check it out the version of the upgraded database
[oracle@sujeet database]$ sqlplus / as sysdba
SQL*Plus: Release Production on Thu Jul 4 21:07:50 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release – 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> select banner from v$version;
Oracle Database 12c Enterprise Edition Release – 64bit Production
PL/SQL Release – Production
CORE Production
TNS for Linux: Version – Production
NLSRTL Version – Production